No more delay compensation when using TC PoCo or UAD1?

[Jerm]

The MIX dialog has an independent packet size setting. Is this where you are setting it?

You do not need to restart for this to take affect.

[Paul]

I had set it in the Digital Audio... Repeated the experiment with setting different packet sizes in the Mix dialog. The results were the same.

[Jerm]

Well now I have no idea.

Can you try a couple of different plug-ins to ensure that they all produce the same offset?

[Paul]

Jerm,

I'll do that tomorrow and let you know then. We're talking only about plugins from the two cards, not the native ones, right?

[Jerm]

We're talking only about plugins from the two cards, not the native ones, right?

Well, if you can find a purely software plug-in that exhibits this problem it would be easier to figure out what it is. I was referring to a different plug-in on the card to rule out the possibility that the problem is solely within the plug-in.

I have also emailed directly to TC electronics to see if they can assist in the resolution of this problem.

[Paul]

Well... I've tried different plugins from both cards and the results are the same as reported earlier (same offset). I noticed that the TC plugin MasterX3 produces more latency than other TC plugins like ChorusDelay, Megareverb and EQsat.

I also tested putting two plugins from the same card on one track, in which case the latency doubled.

All testing was done with the AU versions.

I have also found one case where latency is produced with a native plugin: NI Vokator. The funny thing is that this latency is only there when using the VST OSX version. No probs with the AU version. All other tested native plugins worked fine.

By the way, I've downloaded prerelease 6.3.2 and I'm now constantly getting this message: "43 audio processing overloads have bene detected. This may not happen if the "Audio Buffer Packet Size" in the "Device Options" of the "Digital Audio Setup" is incresed. Would you like to increase this setting now?"

I have never had this message before and the audio packet size is still the same.

[Jerm]

I also tested putting two plugins from the same card on one track, in which case the latency doubled.

It doubled from 2120 samples to 4240 samples?

I have also found one case where latency is produced with a native plugin: NI Vokator. The funny thing is that this latency is only there when using the VST OSX version. No probs with the AU version. All other tested native plugins worked fine.

By native I assume you mean "not using the card".

I have never had this message before and the audio packet size is still the same.

This is new to 6.3.2. It is informing you that you are getting glitches because your processor cannot keep up with the audio. Many things can cause this to happen. For example:

• not have enough memory
• not enough processor
• badly behaved plug-ins

and others. Of course increasing the audio packet size is essentially allocating more time for plug-ins to do their processing.

I am still waiting for a response from TC Electronics. In the meantime I will be furthering my investigation of this problem.

[Paul]

It doubled from 2120 samples to 4240 samples?

Yip.

By native I assume you mean "not using the card".

Yes. I thought 'native' was the proper term for that kind of plugin.

This is new to 6.3.2. It is informing you that you are getting glitches because your processor cannot keep up with the audio. Many things can cause this to happen. For example:

• not have enough memory
• not enough processor
• badly behaved plug-ins

and others. Of course increasing the audio packet size is essentially allocating more time for plug-ins to do their processing.

But is there really a problem then? I never had any 'real' problems with audio in the past. I think I liked it better when I didn't get this message.
If I would increase the packet size, the latency when playing virtual instruments would also rise, right?

I am still waiting for a response from TC Electronics. In the meantime I will be furthering my investigation of this problem.

"Furthering my investigation"... sounds cool...

[Jerm]

Yes. I thought 'native' was the proper term for that kind of plugin.

It was just a bit confusing since you were referring to plug-ins from the company 'Native Instruments'.

But is there really a problem then? I never had any 'real' problems with audio in the past. I think I liked it better when I didn't get this message.
If I would increase the packet size, the latency when playing virtual instruments would also rise, right?

Yes. Correct. The problem is that it is very easy to lower the latency and then later come back and have audio glitches and not remember why this is happening. Would you prefer to see an option like "Don't show this message again"?

[Paul]

Yes. Correct. The problem is that it is very easy to lower the latency and then later come back and have audio glitches and not remember why this is happening.

It's just that with my old settings, with which I now get the warning, I never really experienced any audio glitches, so I was wondering why the message was popping up.

Would you prefer to see an option like "Don't show this message again"?

That would be a pretty Microsoft kind of solution... But sometimes, even they are right... such an option would be nice I guess and it would make Scoot happy as well.

[Scoot]

That would be a pretty Microsoft kind of solution... But sometimes, even they are right... such an option would be nice I guess and it would make Scoot happy as well.

Microsoft?

I've seen them more places than that.

This isn't the info box I want to kill but maybe it could be closer to a system (I mean app) wide idea.

[Paul]

This isn't the info box I want to kill but maybe it could be closer to a system (I mean app) wide idea.

I agree. Once you know, you know.

I used to have the audio packet size set to 384. Now I've set it to 1024 and I'm still getting the warning.

[Jerm]

I think I know what this problem is. If I am right then the following steps should eliminate the latency.

1. Load the plug-in.
2. Go to digital audio dialog and change the sample rate.
3. Mix the audio.

This will probably correct the problem. Please try this and let me know. If it does fix the problem then the problem will be gone in 6.3.2.1

[Paul]

Jerm, you're right!

I changed the sample rate from 44K to 48K, then changed it back again, no more latency. After removing the plugin, I had to repeat the procedure to get everything in sync again.

Great stuff!