Noel Borthwick

Are you automating a plugin parameter? Also do you see this behavior if you automate another plugin?

I tried it in incognito mode and the page loads fine here. Make sure something in your browser isn't blocking it. Its just a shortlink to the main page so I'm not sure why that wouldn't work for you.

This guide was written by @Pete Brown from Microsoft who is also an active DAW user. I thought I'd post it since it takes a common sense approach to getting the best performance from a PC, rather than some of the stuff out there with outdated nonsense that dates back to the XP days https://aka.ms/Win10AudioTweakGuide

I don’t follow. Which ASIO driver are you referring to? You are using two different USB audio devices in your test so there couldn’t have been an ASIO driver.

Yesterday we pushed an update to our installer that should prevent the waves local server from blocking our installer from completing. Anyone who tries to update again should get the new installer. This is temporary until Waves resolves it on their end.

BTW we pushed an update to our installer that detects and shuts down the Waves Local server until this is fixed by Waves. So it should at least temporarily resolve this from our end.

@Michael Richards which OS are you running? From your screenshot it looks like Win 8 or Win 7.

@Glenn Stanton What was the RTL with WASAPI exclusive? Does plugging in a manual offset make recordings line up properly?

@Michael Richards thanks for your report. We'll look into this.

If you get a crash please send the crash dump file. Thats the only way to investigate it. We can also send it to IK to follow up.

Fun fact: Back in 2000 Ron Kuper from Cakewalk had a proposal for a next generation audio driver specification for windows that was being worked on called WASABI. WASABI ultimately turned into the WDM KS spec that Microsoft released in 2000 finally allowing low latency access to audio. WASABI = WDM Advanced Streaming And Buffering Interface. I still have the archived messages from the mailing list! Its interesting that Microsoft called theirs WASAPI. Maybe someone there remembered the thread. We also had a heavily discussed plugin spec called GMPI (generalized music plugin interface). Its too bad it didn't get adopted since it was deeper than VST.

@John VereJust to clarify there is something that may have thrown off your loopback test making it look worse than it was for other driver modes. Only ASIO allows the DAW to know the roundtrip latency by querying the driver itself. (the ASIO reported latencies setting in driver settings) This latency offset is used to place recorded audio precisely on the timeline after you record audio. Cakewalk cannot automatically determine the adjustment value for other driver modes, however you can manually compute and enter this value yourself here by entering a manual offset. Also in theory there is nothing that prevents WDM (or WASAPI exclusive for that matter) from being one equivalent in performance to ASIO. The only difference being driver vendors don't put in the effort to make it work properly. On Mac OS ASIO is almost non existent because vendors just write a core audio driver. Not so on PC. PS: WASAPI is pronounced like he spoke it. Most developers don't spell it out. Same with ASIO.

Steinberg confirmed that the official update is available now. You can download it here.

@Simeon Amburgey Thanks can you confirm that their official update fixes the issue?

@chris williams can you send a link to your project? Dropout code 12 has nothing to do with the buffer size. Its caused by too buffers accumulating. We'll need a project file to reproduce this.

do have more than a few 32bit plugins.. There is a good chance that this is part of the cause of your instability. Most issues like this are caused by plugin instability. Stop using 32 bit plugins as far as possible. If the program hangs capture a dump file and send us a link and we can let you know the cause of the hang. Regarding the dropout make sure that you are running the latest version of Cbb since we fixed some spurious dropout messages. Instructions to capture a dump from a hung program are in my sig.

Please let us know if you isolate it to Ozone so we can follow up. Could it be a gainstaging issue?

CPU power should not be an issue at all with fast bounce irrespective of 64 bit, since the bounce speed is gated by the CPU power available. If there were clicks its likely one of the plugins introducing them. Perhaps you can try disabling the plugins one by one to try and find at what point the clicks stop.

Please do not report problems in this thread. Report issues in the main Cakewalk forums or directly to Cakewalk support.

No the Cakewalk sign in is a replacement for BA. We have all the functions internally to activate and update now, so once you sign in from Cakewalk you should not need to go back to BA.

Looks like you are not setting the active track correctly before pasting. A much easier way to do this operation now is to use the arranger to mark out the section you want to copy and then drag copy the section to the new point in time. It should take care of the rest.

Not presently

Likely because these are sidechainable plugins.

No it renews when it needs to which is when its in the grace period. But the auto renewal only applies if you have signed in from CbB. BandLab assistant wont do that for you.

Its not normal so worth investigating. If you can send a link to a small project that has this issue we can look into it. I doubt that it would even require sending the audio files.