Noel Borthwick

No once you save the project the files are committed. It would be data loss if Cakewalk removed the files because the saved project is referencing them

It is an option!

@Steevthere are no changes in the 06 release related to prochannel modules. Now that you know how to rollback can you install the latest early access build that was posted and check if there are still problems?

@Mark Bastable I need the actual minidump file not the text file. Can you please send the original file (it has a .dmp extension) BTW the reason your zip file was so big was because you had audio from multiple versions of the project file in the audio folder. If I do a save as and save to a new folder it will copy only the associated audio files. After I do that The size dropped to 81 MB which is quite normal. There is no audiosnap data here as I first thought. I don't see any obvious problems with your project. I suspect your crashes are all caused by that plugin. When you send the dump file I can get better information.

@Mark Bastable were you able to capture a crash dump yet?

It would be good to get to the bottom of what is causing the crashes. Send me a PM and I can help you with the exception severity if you havent been able to set that. Most crashes should be caught immediately in that mode. Please also try the latest early access release that was posted in case that helps with your problems. PS: received your project. We'll look at the project file and try and repro.

We posted a new early access installer that includes a fix for this issue. @bitflipper @Andres Medina please try this out and let me know if this addresses the issues with I/O's getting changed unexpectedly. AFIK the problem was only localized to track inputs when loading a synth that changes its outputs. Let me know if you still see problems with this fix. I'm confused by the statement that inputs and outputs were mismatched. Are you referring to the outputs to buses from tracks? Those should have been unchanged. Anyway let me know how it works in this release.

No problem

You probably have a ton of audio snap markers in your project. You can tell if the size of the CWP file itself is very large. If you aren't intentionally using audiosnap you can flush all audio snap markers in the project from the AS toolbar. Select all clips open the toolbar, right click the power button and choose Clear all audiosnap markers. Then when you save the project file it should reduce the size. You may also have takelanes or other data hidden that contributes to the file size. To upload you will need to use dropbox.

DXi’s are still supported by Cakewalk. TTS1 is a legacy product that is no longer maintained by roland so we don’t have the means to update it or fix problems.

Yes its a shame that they didn't test their code in Cakewalk. I will look into whether its possible to detect a mismatched output count at load time and do some internal surgery to the project. No promises because that is really convoluted to do and honestly I would prefer spending that time on other more important things. The plugin could trivially have checked if the persisted version was earlier and NOT exposed the extra output in that case.

VST doesnt spell anything out which is why there is this mess of incompatibilities. Kontakt solves this by always exposing a large pool of outputs and even though you can change assignments that is done INSIDE Kontakt and transparent to the DAW. I spoke to a dev there and he said that they never change the output routing even through the VST interfaces because its very poorly supported in DAW's.

Seriously they added a new output to the existing synth in an update? Does nobody care about backwards compatibility? I guess nobody there actually tests their plugins in Cakewalk or they would have caught this immediately. Port routing in Cakewalk is based on the counts of outputs from hardware and virtual instruments. Port are a range of integers that include the entire set of instrument outputs. When you add or remove instruments we manage that namespace of ports by adding and removing items. But if a plugin does this behind our back it will mess up the ports in the project because the numbers will be off by the number of ports added or removed.

I meant look for the most recently created wave file in the project audio folder. If recording failed for some reason halfway through the file should still be present.

You should be able to install the old version of melodyne and then upgrade it from the melodyne UI itself afik. As long as you have a legit Melodyne essential serial number it should upgrade to the latest Melodyne Essential version. If you have trouble contact Celemony support and they will help you out.

We've verified that the latest version they posted works OK now and doesn't remove files anymore.

Here are the release notes. “X64 VC Redist no longer removes runtime files when run with /installer /passive switches.”

Ha they responded to my request yesterday. Glad they posted it. We’ll test it today.

The rollback installer is listed in the first para of the release notes.

Most of the fixes you see (and there have been thousands) have come as a direct result of users submitting crash dumps or project files with demonstrable issues. Its the only way for software to improve. Bugs wont fix themselves unfortunately

They definitely goofed, so if any program installed the latest MS redist it would actually uninstall stuff the first time you ran it! The bug was the first install removed some files and the next one put them back. Windows update doesn't install that AFIK however so it would have likely been one of the programs you updated.

@Glenn StantonThe 053 installer installs the same redistributables that the 04 release did. We did not update them because there was a known Microsoft installer problem that I posted about here. My best guess is that you directly downloaded the new Microsoft redist (or waves had you download that) and that messed up your install.

Its not clear if you are asking about BandLab issues or CbB. We can't assist with problems related to the BandLab Mix editor since there is a different team managing that. Contact support to report issues with BandLab. Also there is no interaction between the bandlab software and Cbb so one cannot affect the other.

Which previous version specifically were you running earlier? Have you tried a rollback to verify that its related?

@Sidney Earl GoodroeMost likely something independent on your system changed. What was the previous version of CbB you were running - have you tried rolling back to see if its actually related to this release? What plugins specifically are taking longer to load.