ADC Bug in PTHD 9

[JSR]

wow....we must have been working in tandem.

traced the problem back to a aux track that mistakenly had a bus send on it set to the same input as the aux track. removed send, Dly went off.

all is good.

[holden]

FYI, the session doesn't need to be at 96kHz for the problem to arise.

[SessionKat]

Quick curiosity why you're purposely setting a feeback loop on an aux track?

-tv

[holden]

Originally Posted by SessionKat

Quick curiosity why you're purposely setting a feeback loop on an aux track?

-tv

Suppose you want an echo effect where successive echos are increasingly band-limited (low-pass and high-pass filtered). Feedback within the delay plug-in itself will only become reduced in volume with successive iterations (echos). But if you put an EQ on the aux along with the delay and use a send to create the feedback, then each successive echo will become increasingly band-limited. That way the echos evolve in frequency (like real echos).

You can elaborate on this example by having other plug-ins along with the delay, for instance EQ and distortion, on the aux, so that successive echos are increasingly filtered and distorted.

Kenny Gioia details this technique in one of his instructional videos, "Using Mono Delays" in his PT Tips & Tricks series. The trick is valuable whenever you are using a time-based effect as it gives you many more choices for processing the feedback than you would have with any single time-based effect plug-in.

[SessionKat]

Good stuff! Does turning delay comp OFF on that track resolve this workflow issue?

-tv

[holden]

Originally Posted by SessionKat

Good stuff! Does turning delay comp OFF on that track resolve this workflow issue?

-tv

No. Disabling ADC on the aux track does not turn off the red Dly indicator.

Try it yourself on a session containing only one mono aux track with a send bus pointing back to the aux track's input. Inactivate ADC for that track. The aux track is the only track in the session, yet the red Dly light is still on.

[SessionKat]

Clarity has finally arrived:

In PT 9 we now notify user of delay compensation feedback loops per the red "dly" (try holding mouse over "dly" and you'll see the details of the condition)

Red "dly" = a delay compensation state that we do not handle. Before PT 9, Pro Tools did not have the smarts to detect the feedback chain. Now it does.

Hope this clears this up.

-tv

[day_tripper]

Originally Posted by SessionKat

Clarity has finally arrived:

In PT 9 we now notify user of delay compensation feedback loops per the red "dly" (try holding mouse over "dly" and you'll see the details of the condition)

Hope this clears this up.

-tv

unfortunatly most of the included session templates have effects sends that loop back to themselves through other effects. So that light is always on - not sure what to suggest as it makes it hard to tell when i actually exceed the sample limit - a red "F"? EG:reverb track>delay send>delay track>reverb send.

[boabyd23]

I done a test and found using the profire 2626 on a 48khz session my adc longest was the 4k region and lowest was 1k

I put my session to 192khz and the highest samples per channel are 16383 and lowest is 4095.


The playback engine buffer size also increases to 2k samples the more I go up in sample size.


Pretty cool.

[Brandonx1]

What do you know. Double the sample rate doubles the ADC. I did not know that. I work in post and only work at 48k.

Secondly, you are creating a feedback loop. So PT can't compensate for that, it's impossible. That is why the ADC is red.

Hope this helps.
Best