Noel Borthwick

@ceez can you reproduce that scan issue with B3-X? I'd like to send you a newer version of the scanner that work's around that issue to see if it solves it for you.

@Jay MarshallDid you have a plugin that forces mono on the matter bus? If you have a copy of the problem project please share a link and I can take a look as to why that might happen.

If you post a video reproducing the issue, it might help troubleshoot.

Can you post some steps please?

Most likely your issue is that your tracks were going to a master bus which has its interleave switched to mono. If you do that track pans will no longer work until you switch the bus out of mono interleave. The fact that it got solved by creating a new master attests to this.

Without knowing your signal flow its hard to tell but I bet your issue is electrical grounding. For a long time I had a lot of issues with noise from my guitar processor going into my audio interface and had a hard time isolating the source. Depending on your house and quality of the power lines it can be hard to eliminate. Dimmers on the circuits can also cause noise to get into the power lines. In my case I got rid of it by using ferrite cores on all my cables and also using this hum eliminator device. Some PC's are notoriously bad at letting electrical noise get through into your audio interface from. Also ensure you have a common ground for all your plugged in devices.

If you are planning on deleting data from tracks then mix scenes won't save that info so you would have to first save an independent version of the radio edit project. However once you open the radio edit project file you can certainly create and use mix scenes to quickly switch between your original mix and variations of the radio edit mix. You will get the best of both worlds that way.

If you look in the event list do you see the pedal off event recorded?

Which driver mode are you using? This looks like CbB cannot open the audio device and its failing. Have you tried WASAPI Shared mode and also MME?

Something important that nobody mentioned is that Cakewalk projects are both forwards and backwards compatible. This is another plus that Cakewalk DAW's have always had. Not only can you open an old cakewalk file in the latest version, but you can open a newly created project in even a 10 year old version of SONAR and it will get most of the project data. New features added after that version would be lost obviously - for example if you loaded a melodyne project in SONAR X1 it wouldn't know how to read region effect data. So if you own a fully paid for version of a prior product you can always open files there in a pinch. It should be an easy experiment to check that your files open in an old version such as X3 or 8.5

Do the transport buttons look grayed out or just don't respond when clicked?

One thing I can assure you is that Cakewalk is the only DAW that can open project files that date back 20 years We still maintain compatibility with the old .wrk format. I just fixed a couple of issues with loading some old files in the last version.

Yes we finally fixed the talent bug!

@Colin Nicholls you just noticed this? It broke in Feb 2016 lol. Its all good. We've squashed hundreds of bugs that pre existed, some dating back over 15 years. There is another nice one coming up in the next release that existed all the way back to 2003.

I think a redux of the new take management 2.0 might be cool. There are numerous changes that now facilitate using lanes for assembly esp when using the new customizable smart tool. Users from the old 8.5 layers workflow can now use lanes to organize their data prior to doing comping.We had a few video's in the 07 feature overview that might provide food for thought. Some other topics might be utilizing mix recall, using lenses to customize for different workflows (tracking, vs mixing vs beat making etc)

Great, so has this been resolved by a UVI update? If so please mark this as RESOLVED.

You can create presets to do whatever you want so you don't lose anything other than the confusion of seeing all the options every time you export The only thing you can't do from the control bar is selecting specific buses. Everything else can be handled via presets. Its pretty common these days for export options to be simplified via presets and have an advanced mode for when you need more control.

The simplest way to export today in CbB is to use the new export control bar rather than the expanded export dialog. For most users, using the presets in the control bar is all that is needed and it is much simpler to use. It also allows you to bypass selection and export the entire project, something that is not available via the dialog.

Nobody can answer questions about the future with certainty - if we could we'd all be rich We can look to the past though and make educated predictions. Cakewalk was shut down and was acquired by BandLab. It's now alive and better than ever, right? When Gibson shut us down the contingency plan was if all else failed and there was no succession, the last version of the software would be permanently unlocked. We even prepared the mechanism to do that in the last month of ownership. Fortunately it never came to that. Its pretty rare to see mature products completely go extinct. Most products that made it this far are still around in some incarnation.

The main purpose of video in Cakewalk is to allow you to write music to picture. Its not for editing video. You can export the video from Cakewalk with audio embedded but compared to a dedicated video application there are few options for control over the video metadata and codec/bitrate.

As the thread says VST3 does support program changes but it is very poorly supported by plug-in vendors. Most don't implement it at all and many who try and implement it do it poorly. In 2019.09 we added support for program changes via a new Preset parameter that can be automated. This is unique to CbB since other DAW's don't allow this. You can even assign this to a widget in the inspector to change the program change value from CbB. This will only work if the plugin actually implements VST3 program changes properly.

Some pix from day 1 posted

Load balancing is not designed to improve latency. It requires at least 128-256 samples to function. While tracking at low latency its best to leave it off. Its more intended to use while mixing when you have lots of expensive plugins and don't require about low latency, esp in the case where some tracks or buses have many plugins in series, as is often the case when mastering.

There are no plans for BandLab to charge for the core application. Meng has said on many occasions that BandLab believes in removing barriers to music creation. We may charge for add on's at some point. That is expected and the error code will reflect that.

Do you have the same OS on the two machines? Sometimes these bugs esp if they involve memory corruption can be hellish to track down since they may not show up on one system but show up repeatedly on another. It could also be hardware specific / graphics driver related etc. I have seen crashes with ozone in prior versions when changing presets but not in this version.