GIGANTIC!! ADC bug

[masterplan]

Try this in PT9:
(I'm on 9.0.2)

1. Take a VI with separate outs.
Eg Battery, Kontakt or Superior Drummer or something else of Your choice.

2. Record like a kick playing quarter notes.

3. Quantize the kick 100%

4. Assign the kick to a separate out.

5. Create a Bus in PT with its input set to the Plug In out of the VI.

6. Put a high latency plug in on the bus.
Eg Waves Linear Phase stuff or similar high latency plug in.

7. Listen to it together with the PT Click or something similar in audio.
Very accurate.

8. NOW, put another VI track or MIDI track in Rec.
OFF!! Very bad too!

If you instead put an Audio track in Rec this doesn't happen.
That leads me to believe this is a Gigantic Bug!
This prevents You from recording any Midi related stuff if You use any separate outs from Your VIs.

Can we have this fixed in PT10 please.
Yup, You're in a hurry!

Peer

[muhis1]

Here we go again!!!! Unbelievable!!

As far as I can remember it was fine in like 9.0!!!???

What's the problem Avid?

A bug like that makes it impossible to
record softsynths......again!!

Veeery good!!....or maybe not!?

[Rubicon]

Putting a inst. track or midi track into record turns off ADC temporarily. I believe this is stated in the docs. Been this way forever. Lots of old threads on this.

Disable high latency plugs during recording or use a similar low latency plug to avoid this issue.

Rubi

[masterplan]

Thanks Rubi.

But no.
This issue hasn't been there before.
Other ADC related issues yes, but not this one.
In PT8 the ADC was suspended on the same track that you rec armed, which caused all kinds of timing weirdness when trying to punch in etc.
See the Huge ADC bug thread that went on for ages.
But that was fixed in PT9.
But now we got this one instead.

DTS, care to give it a try?


Peer

[KMcK]

http://protools.ideascale.com/a/idea...cussionID=1088

[Rubicon]

Sorry I didn't help, master plan.

[masterplan]

[DigiTechSupt]

This issue has been covered several times here on the DUC. I'll dig up the threads and repost them in the next day or two.

The problem is many-fold and there's no quick fix. It's high on our priority list, however the amount of work necessary to truly fix this is significant.

You'll get more from the other threads that I'll link you to where all of this was discussed previously.

[Craig F]

Originally Posted by DigiTechSupt

This issue has been covered several times here on the DUC. I'll dig up the threads and repost them in the next day or two.

The problem is many-fold and there's no quick fix. It's high on our priority list, however the amount of work necessary to truly fix this is significant.

You'll get more from the other threads that I'll link you to where all of this was discussed previously.

maybe they should bet pinned?

[muhis1]

......