Helge, will this reduce the likelihood of cpu overload errors while real time rendering?
It seems to me that glitches and overloads have been an ever increasing problem since I moved (from XP) to Windows 7. I use a lot of external plug and UAD plugins; I’ve often wondered if the situation will improve when UAD finally moves to 64 bit…
There are multiple graphs with multiple plugins and multiple DAWs being tested. All show exactly the same thing: OSX is not a good OS for audio. Steinberg have confirmed this right here in this thread:
Anyway, we are off-topic. I just wanted to give some background info for the people that were asking why Steinberg mention that the new ASIO Guard would help so much for Cubase on OSX.
All good, no drawbacks?
What about real time recording of mutes/automation to the tracks NOT having the low buffer?
2056 samples is 46.621 ms in 44.1kHz. You certainly can feel that…sluggish faders and mutes perhaps.
When you click a mute button the screen on a non-compensated track, won’t the click be registered/performed 50ms later in such a scenario?
If there is an audio buffer by definition anything you do to the audio, like muting a track, will happen with the latency caused by the buffer. It is impossible to do anything else. The audio that you are trying to manipulate is already in that buffer. Also, what you are hearing is late compared to where the play head is in the DAW so the automation is written with that same latency.
Thank you for enlightening me, Alistair!
I knew there had to be a trade off…perhaps that’s why writing realtime automation in Logic often feels sluggish compared to Cubase?
Well, it seems we can turn this feature on or off, so we still have the choice.
I don’t know about Logic but if I have my latency set any higher than 10 or 12 ms in Cubase or Pro Tools (which effectively is a bit more than that), the fader/knob automation I write in realtime from a control surface will feel and be late.
Well, it seems we can turn this feature on or off, so we still have the choice.
I am guessing we will be able to put the tracks we want to automate in monitoring mode and have the low-latency response for those tracks. Of course you can’t do that with all tracks or it defeats the purpose of the ASIO Guard but still, it should help and as you say, we can always turn it off if it doesn’t suit what we are doing.
If one has a powerful enough machine as it is using 6.5.3 and has never experienced dropouts or latency issues before, what other performance enhancements would ASIO-Guard offer those users?
I am hoping I can mix large projects with plenty of external inserts and UAD plugs and NEVER have to see another cpu overload error when I try to export the mix…which sometimes occurs even when the asio meter shows less than 25%!
This alone would be worth the price of the upgrade to me.
For this feature, I will upgrade. It’s a shame that they don’t make it retro-active to v6.5 so that we can test it to assure ourselves that it does what we anticipate. CS.
I would agree with you if this was about the audio interface buffer. However, the Bulletproof ASIO Guard is a different kind of buffer, acting ‘behind the scenes’. So until we see the release of C7, I think any assumptions about control delay cannot be substanciated.