Bug? Crackle/dropouts of audio while SAVING in Protools (mac) and transport is running

[jeremyroberts]

Bug? Crackle/dropouts of audio while SAVING in Protools (mac) and transport is running???

Today is my first day demoing VEPro. I am loving it. So far. But...

I am a habitual "command-S" guy. I am CONSTANTLY saving. During playback. After a take. Before a take. I save over and over and over again. And if I try to save in PT8 (mac/PPC) while VEPro is instantiated and the transport is running, I am hearing pops and clicks and dropouts only DURING the save. Yikes. At first I thought it was a flaw in VEPro and I was the happy owner of a syncrosoft dongle. But then I realized it was only while saving. If you don't save while the transport is rolling, it's not an issue, but that's no way to work.

My specs:

ProTools host: G5 2.7DP, PT 8.0cs3, session is at 44.1

VEPro slave: macBook Pro C2D 2.33; VEPro 32-bit server build 4881

PT session quite simple -- 2 tracks to VEPro, coming back on 2 pairs.

Can anyone else replicate this? Thanks,

Jeremy

[chriskard]

Hello Jeremy,

Some Instruments block processing while saving. This is the reason why you experience these clicks. I guess you are using Kontakt in VEP right now?

It should not click with Vienna Instruments inserted.

To get rid of the clicking please use the "Decouple" Feature of VE Pro. You find the Decouple button in the plugin you insert in PT. (also called Server Interface).

As soon as you use "Decouple", the VE Pro project data does not get saved with every "comman-S". However if you change somthing in VE Pro you should either save the VE Pro project separately, or "Couple" it with PT again and save your PT project, so all VE Pro data gets saved within your PT project.

best

christianK

[jeremyroberts]

 >> I guess you are using Kontakt in VEP right now?

No. Omnisphere and Trilian only.

So let me try to understand: VE Pro is trying to save patch/plugin data FROM the plugin (which lives in the VEP slave) TO protools session at every save? isn't that a bit overkill? I think this "feature" should be removed. it is FAR more important to save while transport is running without a session-ending (and client-losing) noise than any perceived benefit of bundling the save to the session.

If we are working in a master/slave environment, the saving of the slave is part of the workflow. Bringing the slave plugin data back into the master should not occur at every "save" if the noise is inevitable.

I will try to use the "decouple" technique and see if this works for me.

Thanks for the feedback.

Jeremy

[jeremyroberts]

OK, decouple eliminates the saving issue. But what am I losing now? Am I now simply required to save my files at the slave manually? is that the only thing that happens with "decouple" -- the documentation is not very clear. (page 7)

[Paul]

Hello Jeremy,

your sequencer receives all information about loaded plug-ins from VE PRO, so that you are always safe when you are loading up your song - the right Vienna Ensemble PRO instance is loaded right away. So when you are loading a setup with plug-ins that take a long time to save, saving your song (also auto-save) will slow down your workflow.

That´s when you activate "Decouple" on the Server Interface of each VE PRO individually. Now the plug-in information is NOT saved anymore with your song.

@jeremyroberts said:

Am I now simply required to save my files at the slave manually?

That is one way to do it. The other way (or: as a safety option) is to deactivate "Decouple" when you are saving and closing your song.

We know that this new approach can be confusing, I hope that more videos will help. Flexibility has its price, I guess.

Best,

Paul