Noel Borthwick

If the last time you used cakewalk was 20 years ago then you should be prepared to have a bit of a learning experience. Have you used any current generation music software? Everyone has installers with optional components although some integrate it directly into the program (which is a good thing) Prior to BandLab acquiring Cakewalk we had an installer called command center which was similar in principle to bandlab assistant though more sophisticated. It also allowed to install optional components (many more than what we do now) Bandlab is the company that owns Cakewalk. To use the software the requirement is to create an account that established you as a user. Bandlab is also a powerful cloud platform for recording and sharing music using mobile devices it the web. It has over 20 million users. There is no requirement to use that if you don't need it but it's free and available to any Cakewalk user. In short by default we install the bare minimum for Cakewalk to run to save bandwidth. There is zero bloatware.

This wouldn't be a Cakewalk problem. All fast bounce does is render audio faster than realtime. If the plugin isn't handling this it would be something the plugin vendor needs to investigate on their end.

If you are able to capture a dump we can normally tell what operation is hanging.

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.

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.

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.

@Jon White I understand frustration when things dont work right, but you are making some pretty wild assumptions here. Because something doesn't work as expected the problem isn't always the DAW. DAW's live in a complex ecosystem of hardware, software, plugins and drivers. We have thousands of users (including complete noob's) with no issues like what you describe. This is not to say that the problem may not be in Cakewalk, but your troubleshooting so far isn't conclusive at all. Many plug-in and driver vendors test their stuff exclusively on Mac's, and perform poorly under certain conditions in Windows. They also choose to test in only a subset of DAW's out of familiarity or resource constraints. As a result a symptom that shows in one DAW may not show up in others depending on how the DAW communicates with the device. This doesn't automatically make it a DAW problem does it? You mentioned using Lynx. Are you running their latest drivers? Very recently they had a bug with MMCSS which would cause major issues when the DAW had MMCSS enabled. I reported this and it was fixed by them. Turn off MMCSS in preferences and see if that helps. If not, try playing the same project with a different audio interface (preferably USB) if you can find one. You can also use the onboard audio device for the test. If the problem goes away that would typically isolate the issue to the audio interface driver. If you indeed find this, let us know and I can follow up with Lynx who we communicate with often. PS generally, don't use WASAPI mode with pro audio devices. Most pro audio drivers completely suck with WASAPI since they never test with it.

@JoeGBradford thanks. I looked at the crash dump and it appears to be a different issue. Iris is crashing independently of the app since the crash dump doesn't even implicate Cakewalk. As far as I can see it has something to do with Iris crashing when loading its resources. It may be an install problem. You should follow up with iZotope on this since its not within our control. ------------ BUCKET_ID_PREFIX_STR: APPLICATION_FAULT_INVALID_POINTER_READ_ FAILURE_PROBLEM_CLASS: APPLICATION_FAULT FAILURE_SYMBOL_NAME: iZIris2.dll!Unknown FAILURE_ID_HASH_STRING: um:invalid_pointer_read_c0000005_iziris2.dll!unknown FAILURE_ID_HASH: {118841e1-6bcb-ef9d-fb0e-9ac068247613} Followup: MachineOwner --------- 0:000> kp 20 # Child-SP RetAddr Call Site 00 00000000`00147258 00007ffd`538376ad ntdll!NtGetContextThread+0x14 01 00000000`00147260 00000000`22f700b8 ntdll!LdrpLoadResourceFromAlternativeModule+0x2bd 02 00000000`001473d0 00000000`00000028 0x22f700b8 03 00000000`001473d8 00000000`00000000 0x28

@billp your scan log looks OK. I'll troubleshoot with you via PM since its do difficult to do on the forum. Please check for a message.

I didn't realize you posted a video. The app is closing when trying to load TyrellN6 so try skipping that synth in safe mode and see if it loads. Also check if the default sample rate matches the project sample rate as suggested earlier.

@Stephen LathamWhich synths are you loading in the project? Does the application crash or does it appear to hang? Also what sample rate did you create that project at - is it different from the default sample rate for new projects that you have set in preferences | Audio?

@JoeGBradford what is your case number? I can look at it.

Some clarifications. There is nothing wrong with your VST scanner version. 6.0.3.0 is the correct one. If you have the scan button grayed out its likely because something (antivirus, registry corruption, or personalization failing) has messed up the app install and the app doesnt have the path to the VST scanner anymore. Look in HKEY_CURRENT_USER\Software\Cakewalk Music Software\Cakewalk\Cakewalk VST X64 for a value of VSTScanPath. It should point to C:\Program Files\Cakewalk\Shared Utilities\VstScan.exe If not, you can redo the personalization for Cakewalk. To do that, launch Cakewalk while holding down the CTRL key. This will show the personalization dialog. Click OK and let it finish. After that VST scan should be accessible again.

Is your default sample rate set to the same sample rate that the project containing Iris is set to? If not, loading the project will crash Iris. This specific issue is a bug in Iris. Cakewalk first initializes iris at the the default sample rate and later changes to the project sample rate. Iris crashes when loading its state at the default sample rate. The good news is that I have already addressed this from our side for the next release even though its technically not a bug - all other plugins handle this. I will be reporting this to iZotope as well. You can resolve it for now by setting your default sample rate to be the same as what you used in the project containing Iris.

Have you taken a look at the release notes for the 05 release? We fix scores of issues every release (most of which are preexisting and some which are workarounds for problems not even directly caused by Cakewalk) If you don't consider that progress I'm not sure what to say. We are not aware of any of the issues you list. There is no way to know if they are fixed until you actually try running the latest release. If you have concrete ways to demonstrate them in the current release then log them specifically. If they are issues within our control we do our best to address them.