Jonathan Sasor

Changes within the app facilitated that BandLab Assistant was no longer able to do offline Activation for Cakewalk by BandLab. There was no bad intention involved. The new method required for this just hasn't been formally released yet.

It's possible the plugin is in a bad state and reinserting it will work. You can always save a copy of the project with a new instance and see if it works any better

@tdehan Looks like the crash is in VSCO2 Orchestra.dll that's corrupting memory. That would indicate it should open in safe mode if you choose not to load the plugins.

If the issue persists you can send us the dump file from the crash and we can check on our end.

I mean, you could do a counter-gain/volume envelope on audio that has a pre-existing fade printed on it. You'll raise the noise floor the whole time though.

Yes, Easter egg, but very much not new ?

This has been discussed enough on other threads as well, we don't need to rehash it again here. Thanks!

I'm going to lock this thread just as this same convo has run its course on... numerous other threads, nothing personal @Rickddd. When all the pricing stuff is finalized, we'll let everybody know, but as of right now (and mentioned elsewhere) the current plans we have on deck should be agreeable with most people here. We can't say much beyond that, but we just ask that people be patient. Thanks!

Those issues are beyond the scope the last drop. Its goal was to address relevant issues that people had run into that were related to the initial 2023.09 release. There were no changes to the Staff View since 2022.11. The Microsoft GS Wavetable synth issue is not internal to Cakewalk. It's an unreliable method for trying to get MIDI playback and not recommended for that reason. As for garbled audio with the TTS-1, what is the audio configuration for both playback and the project sample rate? There haven't been any changes that would impact TTS-1's performance, and we're unable to reproduce this issue on our end at a standard 44.1 KHz sample rate.

If you have a dump file for the crash we can take a look into it.

@Keni if you use the Cakewalk installer tool off the CbB product page, that will get the update.

I was simply stating I could reproduce the same behavior in the 2022.11 update, so it's not something that was introduced with the changes for new version. Let's please keep the thread on topic.

This is not new to this update, but it's not duplicating the frozen state. You're seeing the FX bin disabled there as it is on the frozen track, but since there isn't any rendered audio, the FX are just bypassed. I've gone ahead and logged this on our end.

@Sidney Earl Goodroe I understand your concerns, at the moment we just can't give specifics because things aren't totally finalized. I can tell you that as Noel has said elsewhere, the planned pricing model for Sonar will be very reasonable. We have a set target for it that I think most people will be happy with. We simply cannot speak on full details on stuff that requires all the i's dotted and t's crossed. But as its been said, this particular thread is related to the 2023.09 update, so let's try and keep focus there. Thanks!

While I would hope a pending fix from them would resolve any issues, but can we please refrain from publicly listing beta installers for third party companies here? Thanks!

If you're using a Workspace it would reset the view on reopening the project.

Can you provide a screenshot of what you're seeing?

It's likely a routing issue with the driver. Ideally you want to be using a low latency ASIO driver with Cakewalk for the best performance, but your other apps and Windows utilize the WASAPI Shared driver. Depending on your driver you might need to adjust something with the routing within the driver control itself (many ASIO devices contain a separate driver mixer panel that routes your ports in the app), alternately if you use the stock Windows driver it should behave the same in Cakewalk as it does elsewhere.

Not at the moment, Sonar isn't in open beta.

This is not likely related to the update itself. Check what your audio settings are in the Preferences and then make sure that your outputs in the project are routed to the hardware properly.

Discord is more of a chat than a forum. It kind of splits the difference between a forum and an app like Slack

They might not have been registered correctly with the update install. @Promidi's suggestion about redoing the Microsoft redists (either separately or by re-running a Cakewalk install) would be the first thing I'd try as well.

Next shows up in the Add/Remove Programs in Windows like any other Cakewalk application. The only thing Next shares with a Cakewalk by BandLab install is that it goes to C:\Program Files\Cakewalk and similar. Having a Next install has no effect on CbB and vice versa.

We haven't seen this issue on our end, but if you're experiencing a crash, please send us a dump file and we'll investigate. Thanks!