Delay Compensation bug in PT11 with AOS plug-ins (fixed in PT 11.2.1)

[Eric Lambert]

Originally Posted by roberts

When I talked to Avid about this at Namm I was told that is was not a priority issue.

Certainly the conversation didn't end with those words as no official would ever end a discussion regarding software bugs saying that your concern is not a priority. They'd soften the blow with something. But with what, I couldn't guess. Please tell us what other information they provided - how they explained that such a serious issue was "not a priority."

[Eric Lambert]

Originally Posted by stargazer

Please try my suggestion above (and below in bold) and report back.

I haven't installed my copy of PT11 yet, but in v10 it works for me if I

Uncheck the second and third boxes in
Preferences/Midi - Delay Compensation for External Devices.

I don't think it's a bug, but we need to see an update in which PT can tell the difference between midi tracks for internal vs external devices.
Maybe this is a remnant from an ancient version, when the developers presumed that all midi in a session was intended for external sources.

I'll give this a try and report back.

Still, ProTools has had issues with Delay Compensation every since its earliest days. I can't remember a time when it worked as advertised with much consistency. We're too often restarting in order to get DC to work again. Years and years and years have passed and they're not repairing this "feature."

[surstromming]

Originally Posted by Eric Lambert

I'll give this a try and report back.

I´ve already tried that and it didn't help unfortunately.

Best regards,
Markus

[Eric Lambert]

Is this only an issue with Strike -- I just tried duplicating the issue with Superior Drummer and I couldn't get it to fail. Playback is tight. I'm using PT 11.1.2 with OSX 10.9.2.

I don't have Strike installed and can't try that but I did give Omnisphere a go and it plays properly as well.

[surstromming]

Originally Posted by Eric Lambert

Is this only an issue with Strike -- I just tried duplicating the issue with Superior Drummer and I couldn't get it to fail. Playback is tight. I'm using PT 11.1.2 with OSX 10.9.2.

I don't have Strike installed and can't try that but I did give Omnisphere a go and it plays properly as well.

No, it´s not an issue just with Strike.
The problem for me is with EZdrummer and NI different Abbey Roads Drummer.
I don´t have Superior so I can´t confirm on that.
But it probably is problems with other VI as well.

How did you set it up to test it?
Did you for example put 3 maximizer on one of the tracks that you are sending one of Superior channel to?

Regards,
Markus

[Eric Lambert]

OK so I did get it to fail eventually, after adding more plugins. And once it failed I had to restart ProTools to get it to work again. Merely closing the session and reopening didn't cut it. BUT... it does now work, even with the amount of plugins which caused it to fail in the first place.

I'll keep playing around and try to find some useful consistencies.

[surstromming]

Originally Posted by Eric Lambert

OK so I did get it to fail eventually, after adding more plugins. And once it failed I had to restart ProTools to get it to work again. Merely closing the session and reopening didn't cut it. BUT... it does now work, even with the amount of plugins which caused it to fail in the first place.

I'll keep playing around and try to find some useful consistencies.

Hi,

Could you maybe post a screenshot of your mixer, how you have it set up when testing this?

Because even restarting PT won´t get this to play in sync for me.
And I don't think it has for other users either.
The only workaround that I know of is in the link below, and that has been confirmed by Avid to another user who was in contact with Avid in post #26 on that page.

Read about the workaround here:
http://duc.avid.com/showthread.php?t=348977&page=3

Best regards,
Markus

[Eric Lambert]

For years I've suspected that DC gets buggy when it's toggled during playback. It can happen when playback is stopped, too, but it seems more likely to occur if PT is being asked to compensate, or ignore compensation, while things are running. So I never toggle during playback, as is done in that video where there's an obvious timing problem.

Is that related to the reason why I'm not getting timing errors? Maybe. Doubtful, but at this point who knows?

I'll dive back in at some point and post a screenshot then.

[surstromming]

Originally Posted by Eric Lambert

For years I've suspected that DC gets buggy when it's toggled during playback. It can happen when playback is stopped, too, but it seems more likely to occur if PT is being asked to compensate, or ignore compensation, while things are running. So I never toggle during playback, as is done in that video where there's an obvious timing problem.

Is that related to the reason why I'm not getting timing errors? Maybe. Doubtful, but at this point who knows?

I'll dive back in at some point and post a screenshot then.

What video are you referring to when delay compensation is toggled during playback?
I don´t see the user in the first post in this thread toggling delay compensation?

I have never toggled that either.
So I don´t think that is the reason at all.

I have tried many times to open the exact same session in PT10 and then everything is ok.
But opening the same session again in PT11, it´s not.

And Avid is obviously aware that ADC don´t work in a multi-out VI setup in PT11.
The question is if they are ignoring it, which at this point seems to be the case.
But I really hope it´s not and that they are working on a fix.

Regards,
Markus

[musicman691]

Originally Posted by surstromming

Hi,

The issue is about tracks that are coming live from a multi-out VI.
Audio tracks (even when set to a Aux) have the ADC working as it should.
The first video in this thread is showing exactly what the problem is.

The thing is that ADC is working perfectly with multi-out VI in PT10, but not in PT11.

Hope that clear things up?

Best regards,
Markus

Yes it does. It wasn't clear if the problem was solely in live tracks from a multi-out vi or after they were rendered to audio and the vi inactivated. I tend to work with multi-out vi's rendered out to audio before I do any plugin processing so I should be good then.