Noel Borthwick

How do you know whether we will solve it or not before you have even given us a case to try and reproduce? We need to understand exactly what is happening in your case. We routinely use Waves plugins and I deal with the Waves engineering team directly and they have not reported this to be an issue as well. If it is related to a specific workflow that triggers this we need to understand exactly what is causing it. The best way to to get to the bottom of this is to work with us directly.

Not at all. The only change is that you now have a choice to auto apply the selected workspace when loading a project or not. Unlike screensets workspaces are global, so we thought it was best for the user experience to give the user control over whether they should be applied automatically or not. This was in response to some users getting confused with why per project settings didn't appear to save (they were actually saved as before but the currently selected workspace would override them on next open of the project. This is no other behavior change.

@Olaf thanks for talking the time to document your issues. We are definitely concerned with the essentials more than anything else so would like to work with you to get to the bottom of some of your problems. Some of them appear to be third party issues since they are not the norm. Contact me via pm and we can look at some of these problems in more detail.

Plugins are the same ones that were bundled with SONAR at this point. The main reason for inclusion was that they are used in FXchains so the fact that they have dated UI is secondary. At some point we may update them but they perform well and sound good. With FXChains you can re-skin them to your taste.

It doesnt do that intentionally since the user is meant to see the location. You shouldn't leave that option on by default.

Thanks for the feedback. You are certainly a workspaces power user We had a lot of new users getting confused by workspace auto applying so defaulting to that being manual is less troublesome. If you can send me some details on how you utilize workspaces it may help us down the road.

@reevant if you send a dump file I can take a look and see where its hanging. Send me a download link.

If you prefer the workspace to auto apply then why not turn on the 'Apply Workspace on Project Load’? If you want it on a case by case basis then just apply the workspace manually. Workspaces are designed to be global not per project...

Hmm no idea what your issue was. I even checked with the Waves developers and they said that Ovox is backwards compatible and there should be no issues. If you encounter it again share the project and we can send it to Waves. If its system specific you will have to work with them directly.

That's a completely different issue and is not something we have control over. If the new ovox had a different vst ID from the old one it won't load automatically if older projects referenced the old version. This is not a Cakewalk problem. If you insert it in a project and save and reload it does it work? If so the original problem is fixed.

@KevMany issues with mono interleave were fixed in the 05 release. Can you share your project file that has the issue? Without seeing the signal flow and plugins we can't investigate the cause of what you are seeing.

Its still crashing? I have a confirmation from Waves QA that the 05 release solved the Ovox crash on load issue. Can you share a project please and a dump file?

Your analogy to print has no bearing on software development. Any piece of software this size has bugs. In its broadest definition a bug is an unintended behavior of the app. Many issues in a DAW running plugins are caused by bugs in the plugins or third party components so its not always straightforward to determine root cause. Hence we need dump files and the actual projects. And to answer your question I would say that 90% of the issues we fix are preexisting so yes they did exist in SONAR. CbB is vastly improved and more stable than SONAR ever was and it gets better every month since we are have been committed to aggressively fixing problems. Seeing a long fix list of bugs is a good thing for any software. Would you prefer that we don't list our fixes?

You cannot have two versions of Melodyne simultaneously installed. So if you have V5 Cakewalk will automatically use it. You can verify by looking at the about menu as HIBI noted.

There was a problem with Ovox but in the last update we worked around the crash so it should be fine in the latest release. Any Melodyne crashes should be reported to Celemony support directly.

@Tomoko Mikamimaybe you had a corrupted install. How did you initialize windows?

@Tomoko Mikami Thanks for sending your dump file. It appears to be crashing in some Windows message processing stuff so that's strange. So just CTRL-Clicking a MIDI clip on the track will crash for you? Can you reproduce this in any project or only one specific one? Also check if clicking on any clip causes this. If its project specific please share the project file with instructions on how to reproduce. Also can you try dragging some MIDI from the media browser to the same track and see if that works ok?

@Tomoko Mikami which release of Cakewalk are you using? Also can you please send us a crash dump file so we can see what exactly is crashing.

In the next release we will be issuing some of the missing plugins from effects chains we ship with CbB. That was an oversight.

Click on your original message first and then click and hold (long press) on the title of the message to edit it.

This is not a Cakewalk problem. You likely have an incorrect melodyne 5 install. Its not necessary to manually install the VST3 plugin. The Celemony installer should automatically do it. In fact they only support the VST3 as of V5 as far as I know. The first thing to check is to create a region effect on a NEW project. If that is making a region effect with the old version of melodyne then you have the old melodyne installed for sure. The VST3 is normally found here C:\Program Files\Common Files\VST3\Celemony\Melodyne. Please don't manually copy files since that is not recommended. Run the uninstaller for Melodyne and after that make sure you install the latest version they sent you in the default locations. If you still have problems contact Celemony support and they will help you out.

@Jon White Lynx is quoting some misguided stuff from Steinberg. Cakewalk was doing MMCSS way before Steinberg was even aware of it. We allow the user to set the MMCSS thread priority in the host because we want to match the priorities to our other threads - otherwise you end up with priority inversion. If the app sets the priority and the driver attempts to set it the call will fail. All software needs to be resilient and handle these situations and all other drivers I have seen handle this. The original Lynx issue was because the driver was failing to check this. If the driver sets the priority the host should ignore the failure code and everything works normally. In any case its a user choice to disable MMCSS from the host level. Its provided to improve performance with drivers that are unaware of MMCSS (which is most drivers)

Not real time but you can use the BandLab integration within Cakewalk to work on collaborative stuff with others. Its actually rare that while producing you want to do it actually in real time as opposed to sendin g stuff back and forth. Bandlab supports revisions so its actually quite useful in this regard since it saves prior versions of the project.

@Marco Marujo You are using 32 bit UAD plugins? Its not recommended. If you use the 64 bit versions you will not have this issue. Or does UAD1 not support 64 bit?

You can turn it off in either not for your test, Turn off mmcss in Cakewalk. Also please report back on testing the same project with a different audio interface. Testing different software with the same hardware at best shows differences in performance of the driver rather than the DAWs. The mmcss issue is a great example of that.