Jonathan Sasor

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!

If you're not seeing the sign in page, check if you have your default browser running somewhere. It sounds like there's something stopping the webpage launching with the sign in. Note that you have to use a sign in page that was opened by Cakewalk for it to work.

Odd, I just verified it's still working on Win 8.1 on our end. Possible there's something else going on with your other system locally, but we specifically built the updated Command Center with the old compiler so that there wouldn't be any compatibility issues from subsequent updates.

Command Center should be fine on Windows 7/8. We just recompiled it with the old compiler to update it for the new back end locations. Windows 8 went EOL at the beginning of the year, so the new Sonar will only be officially supported on Win 10 and above, but odds are likely fine it'll be fine on Win 8.1, at least for a while. Win 7 can't do the graphics stuff... display scaling there is a nightmare comparatively. In either case it doesn't really make much sense on our end to put the time into doing OS specific testing on operating systems that aren't supported by Microsoft at this point.

That's just a benign dialog that can sometimes appear with the updated version of Command Center. It's a known issue, but you can simply close the dialog.

Either version of Melodyne should work, but from experience, 5 is way more stable. The VST3 version is what loads as the ARA effect in Region FX. If it's in the VST3 folder, then check it's not being excluded.

That's correct, the Cakewalk Installer here will grab the full version of the latest installer if you're installing onto a new system. As with the update downloads, copies are placed in the Windows Downloads folder.

The Cakewalk Installer on the site will grab whatever version of the installer is necessary for your system. If it's 2022.11 or later, it'll use the updater. If it's a clean system or an earlier update, it will use the full installer version.

There's no change from the Early Access update. You're already up to date. Build 29.09.0.062 is the release version.

PM sent

Shift + drag also works horizontally as well to constrain the drag from moving to a different track.

Once upon a time they were staging platforms for testing various web changes. The legacy.cakewalk.com is the main page for the previous site.

I'd suggest using https://legacy.cakewalk.com/Command-Center instead, but the 1.1.8.1 version of Command Center is the correct one. We had to shift some server end stuff which required a new version of Command Center so it could phone home correctly.