Noel Borthwick

Post a screenshot of your audio settings showing the inputs and outputs. Are you using ASIO mode?

@AdK StudiosThanks for checking it out. I don't think it's cpu related. Can you send me a reference project that exhibits this so we can investigate further?

Your first step should be to upgrade to the latest build and try and reproduce it there. 2019.09 is an ancient build.

@rejkmackan can you send a link to a project file that has the problem?

I enjoy that game too. I had someone once call to tell me that my Windows was compromised claiming to be from Microsoft. I said - great I work for Microsoft too. They promptly hung up ?

We’ll look into it and try and repro it. Thanks.

Im exclusively using edge these days including on an iPad where ironically it generally runs better than Safari.

This is exactly right. If you want to benefit from higher sample rates for plugins or synths you have to use the upsampling feature. You can set the plugins to Upsample on Render and they will automatically be converted only when exporting/bouncing. Increasing the export sample rate won't do much other than upsampling the final output of your mix. So no sonic advantage.

Or worse it could appear to make it better in some very isolated circumstance and hurt performance in other cases. This is how a lot of these myths originated and people blindly follow them. The other more recent thing that is being propagated is that MMCSS should not be set by the DAW and only by the driver. This has led to problems with drivers that are not coded properly to check for error codes. It would be great if the MMCSS documentation could explain the use cases better so that developers don't make mistaken assumptions.

Maybe its one of those aggressive DAW tweaks you have ?

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.