Noel Borthwick

ARA will make it into Next at some point but we can’t give you a timeline. There are some more pressing features that have more general use that are needed prior to that.

The settings should be saved as part of your project. However if you are overriding it with a workspace then it will revert to whatever is in the workspace. To verify don’t use a workspace and save and reload your project,

I like to fix a bug for Christmas - glad it’s sorted. Merry Christmas Since nobody was able to reproduce it I suspect it’s something within your project. I’ve seen some bizarre issues in the past where certain plugin copy protection schemes were locking project files intermittently. Not impossible that your issue was similar. Auto save is now deferred by a few seconds after the change is detected.

I sent you a build to evaluate.

It would appear that somehow autosave is trying to sneak in and save before the bounce fully completed. What are your autosave settings? I can't say with certainty since I cannot reproduce this, but I've made some changes that may prevent this from happening. Also made some improvements to auto save for next version.

This is your exact problem. Irrespective of whether you use it or not ASIO4All and similar variants like this "built in" driver, cause complex problems and interfere with other drivers loading at startup because they lead to sample rates being changed abnormally. If you don't use those wrapper drivers just find and delete them (or rename them so that Sonar never sees them). You have 3 of them installed - god help you with that! Getting rid of them will also speed up startup of Sonar. In the drivers page you must unselect both inputs and outputs before you can select a different driver.

Alternatively, you can force switch to WASAPI. With Sonar closed open regedit and double click and change the "Core" value listed below to 3d On next restart Sonar will use WASAPI shared mode. If that opens fine, the issue is one of your ASIO drivers that get enumerated at startup. Nothing has changed in this area in 5 years so if the issue just started, its exposing the incompatibility now. We have not supported non-native ASIO drivers for years because they have problems with switching sample rates and interfere with other devices being enumerated as well. Contact your vendor for a native ASIO driver if you aren't sure how to resolve it.

This is an audio driver issue not a redist problem. If you are using a non native asio driver that is your problem. Use WASAPI shared mode and not ASIO mode if the driver hangs when starting Sonar. We don't support ASIO4All and its variants.

Its literally explained in the first post on this thread. Generally if running the latest redist installer didn't resolve your issue then you have some other issue. Are you using an ASIO driver like ASIO4All or a variant of that? If so that is likely the cause for your hang.

Generally, most promo's tend to be for new customer acquisition. Also, it requires a bunch of backend work to implement promo's that extend existing customer subs , so most companies don't do it this way.

This is not an error. There were different tiers for the BandLab sale and indeed just a few licenses at $0.99 so that's not a typo. If you had bought in at the right time you would have got it at that price. Its important to note that this promo is a general Bandlab offer - its not directly targeting Cakewalk users. It's very common marketing technique for companies to have holiday promo's like this. Google does volume limited promo's like this all the time as well.

Rolling back is not going to solve anything if the problem is external. If you post a crash dump file we can tell you why its crashing.

There has already been a dedicated thread for redist issues for ages. We don't need more threads. This is a Windows problem not a Cakewalk issue. Its happening to other apps as well. All we can do is guide users to solve the problem themselves. All our latest installers automatically attempt to repair the redist. There isn't anything further we can do. If anyone has problems beyond this I suggest contacting Microsoft support.

Although sonar can have very long projects in absolute time, there are limitations to musical time. This is an area that can be improved. PS. when we adopted wav64 as a wave file format back in Sonar 7 we tested really long projects. I remember testing files that were a month long and running test recordings for many days.

Have you actually tried the same project in cbb? If you can share a link to the project file with us we'll take a look.

That's the assigned project file song title. You can change it from the media browser.

I believe mpeg 4 audio files should import into Sonar as long as windows sees the codec. What problem specifically are you seeing.

Its 100% backwards compatible. It just won't import old bugs However, there is no good reason to uninstall the old cbb. The footprint is quite small and its handy if you ever need to compare how something works as compared to the old version.

After further investigation, we are in the process of updating our installers to auto repair a broken redist installation. This should help alleviate ongoing issues with corrupt redists. If you have the problem, please download and run our latest redist installer which now attempts to restore a broken C++ redist installation. Our main Sonar and Next installers (as well as CbB installer) should be also updated shortly with similar capabilities. Also read the main article on this for more information.

After further investigation, we are in the process of updating our installers to auto repair a broken redist installation. This should help alleviate ongoing issues with corrupt redists. If you have the problem, please download and run our redist installer which now attempts to restore a broken C++ redist installation. Our main Sonar and Next installers should be also updated shortly with similar capabilities.

Those redists themselves look good to me. I have no idea why they got affected. You may want to update the screenshot by expanding to show the version number.

Please don't do a clean install. Its the last resort and in many cases, it causes more setup issues than it solves. If you installed other apps my money is on them installing old buggy versions of the Microsoft redist installers. This is why Microsoft released a universal redist installer that we now use.

I had one user who had that issue and I had him search for Visual C++ and first remove all resists, then run the latest Sonar install (or our redist installer) which installs the latest redist as well as the proper Microsoft legacy redist installer. That was the only thing that fixed it for him. As I said, I don’t know what is causing this. Its very odd if its breaking and you aren’t aware of any installers that were explicitly run, The only thing I can think of is maybe Windows update did something. I would use the feedback app in Windows and report this to Microsoft. Its crazy how brittle their visual studio redist has become over the last year.

Don't do a clean install of Cakewalk it's definitely not required in this case. This is almost 100% a case of damaged or mismatched redistributables. I really have no idea why this is happening, but my only explanation is some other software is installing bad versions of the redists. Please follow the instructions in this link and first remove all the redists and then run the latest Sonar installer or use our redist installer to put back the latest good versions.

I misspoke. Actually, you can use Quick group along with permanent groups as long as you start the operation from a control that is not permanently grouped. Quick grouping and permanent grouping are two different operations. Permanent grouping is when you assign a bunch of controls to predefined groups (A, B, C...) and set up their relationships to each other via the group and group manager menu items. Quick grouping is a temporary state where it auto groups controls for selected tracks and operates on them. Since the key is CTRL for this you cannot engage quick grouping from an already permanently grouped control since the modifier acts as an override in this case. We can't use shift either since shift is used for accurate editing mode.