My nooby thread

[MusicMadness]

Hello everyone,
From last couple of days I'm another happy user of Pro Tools. Basically, nearly happy, as I experienced 2-3 crashes and can't figure 2 issues:
1. When soloing/muting/arming selected channels using SHIFT+S/M/R the only affected channel is the one selected by cursor in edit window even if I work in mixer window.
2. Sometimes loop playback doesn't work and it keeps playing after selection ends, then after last clip ends and then to infinity... I tried with different recording settings but for now I only mix already recorded material. I can't figure how to make it works so every time the problem occurs I have to reload session.
3. Online bounce ends with end of last clip despite of effects that still plays. Is it any way to extend rendering for this couple of seconds without putting empty clip at the end of the session?
4. Offline bounce creates files much longer than demanded, eg. for 15 sec of music in session it gives >60sec mixdown.
I've read several topics but haven't find the solution so I might use some some help. Cheers

[Carl Kolchak]

Look for "Link Edit & Timeline selection" in the manual - that sounds like the root of most of your problems & it's easy to accidentally hit the shortcut, and disable it / enable it, which has probably happen here :

Shift + /

Bounces are determined by the timeline selection, not the edit selection, so if you have reverb tails, you need to extend the selection until they have reached silence.


Sent from my iPhone using Tapatalk

[MusicMadness]

Hi, I have another issue. In my session there are 2 tracks which are automation-proof. I mean in read mode they don't change values and in latch mode they're not writing. When using automation preview and move a fader on Command 8 the automation type background doesn't switch to green and stays white. Every other track reacts properly. Any ideas what could went wrong?

[Stig Eliassen]

Originally Posted by MusicMadness

Hi, I have another issue. In my session there are 2 tracks which are automation-proof. I mean in read mode they don't change values and in latch mode they're not writing. When using automation preview and move a fader on Command 8 the automation type background doesn't switch to green and stays white. Every other track reacts properly. Any ideas what could went wrong?

With the Track View Selector set to volume, is it greyed out?

[Stig Eliassen]

Command-click to toggle it.

[MusicMadness]

Originally Posted by Stig Eliassen

With the Track View Selector set to volume, is it greyed out?

Automation curves look ok. I can write automation by pencil tool but tracks seem not to react on it.

Originally Posted by Stig Eliassen

Command-click to toggle it.

Command-click where?


I imported session data from one of my previous sessions and after importing Volume Automation and Settings it works properly however I don't know what settings exactly I have to change. Unfortunately, there are many more tracks which don't response and I can't restore settings for all of them. It's only about volume automation, pan and mute are ok. Do you know where I can change the automation settings manually for selected tracks? In Preferences -> Mixing I can't see anything like that.

[Stig Eliassen]

1) Command+4 (numpad) to check that volume is auto-enabled

2) Click the track view selector (it defaults to waveform/clips) and select volume. Is that box greyed out?

[MusicMadness]

Got it! Yes, the boxes were greyed out, I didn't notice. Thank you very much

[Stig Eliassen]

Originally Posted by MusicMadness

Got it! Yes, the boxes were greyed out, I didn't notice. Thank you very much

That's great!

[MusicMadness]

Guys, I'm affraid I cannot configure my Pro Tools properly. I tried to run Steven Slate's demo session but theres often an communitcate that Pro Tools ran out of CPU power AAE-9173. I got through recommendations about optimizations, I use Buffer size 1024 samples and my CPU is stressed in ~40% but the chart jumps from time to time to 80-90% and every operation during playback eg. scrolling tracks or adding a new plugin causes that error. Is there any way to improve stability of cpu performance?