Noel Borthwick

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.

@bdickens I sent you a PM. This is unfortunately beginning to look like something is corrupted with your Windows update settings. I had this happen on one of my machines a year ago and the only thing that fixed it finally was a reinstall of Windows despite Microsoft trying to fix it in several sessions. However you can try and do a service call with them since it may be fixable. Explain to them that their webview installer is failing and you cannot do windows updates.

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.

Jon sent you a link. The edge update service as I understand it is to keep the edge runtime up to date. This is a critical part of the edge runtime that needs to be periodically patched by MS to deal with malware and other exploits. Why it phones home to check for updates often I'm not sure about. Perhaps this is a question more suited to Microsoft. In any case its not trying to force install edge or anything like that. The edge webview redist requirement will go away in a future version of Windows 10 because Microsoft has indicated that its a temporary solution. At that time our installer won't need to install it anymore for Win10 that is.

I thought my reply clarified that were not installing anything that doesn't work on Win7 as per Microsofts documentation and our tests showed. We don't need to ask for permission to install libraries that are necessary for the function of our application. We don't test on machines that are tweaked to disable windows components and if things break due to that its not something to blame Cakewalk for. The link to a rollback installer is right in the first para of the main release notes.

We don't control what Microsoft installs within its redistributables. It uses components that are part of edge but its not the edge browser itself. . So if you don't like that I'm sorry there isn't anything we can do to solve that. If you want to keep using Win7 an unsupported OS by both Microsoft and Cakewalk, its your call. However we don't have the bandwidth to support it and you will almost surely have more problems going forward. That said there are plenty of other people running the last update even on Win7 with no such issues. This is incorrect. Webview is supported by Microsoft even on Windows 7. Windows 7, 8, 10 support Support for a consistent user experience across Windows 7, 8, and 10. >> CbB still crashes when it tries to load sample libraries that it loaded just fine prior to the update. What sample libraries? Is it crashing when loading a plugin? If so the crash site may not be in Cbb but in a plugin that has incompatibilities. As I said above save the crash dump and send a link. There are instructions in my sig to do this.

Please read my post above. Are you indeed running Win7? If not please follow the steps in my sig to capture a dump and send a link. If its hanging we can tell whats causing it normally.

Firstly were not installing edge so lets debunk that theory. Its a webview component that is REQUIRED by cakewalk to do single sign on to BandLab both for activation and future integration. It does work on Windows 7 and was tested by QA. WebView is not the same thing as Edge. We have clearly indicated many times that we don't actively support Win 7 any more and allow installation as a courtesy. The installer even tells you this! If you are still using Win7 and installing updates you can still revert to a the prior version if you have issues.

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