Jonathan Sasor

All that means is we want you to be on the latest build.

It should be in a Cakewalk subfolder within the Downloads folder in Windows. It seems like it might have been a blip when the installer was just trying to launch the app, particularly if it was when you hit "Finish". If the app is displaying that you're on build 417, it's likely you're fine. That error shouldn't be related to anything actually updating for the app components. If there's any problems, you might want to just make sure there's nothing unusual going on in Windows like a pending update or anything and then restart and try the installer again if necessary.

When exactly did you see this message? Was it during the installation itself or when the app was launching/already open after the install? Do you see it on subsequent launches of the app?

It's a reminder that the current lease period will expire in that amount of time based on what we've received from the back end. You're fully activated, it is just saying "if you want to stay activated beyond that, you'll need to renew before that time". It might be worth tweaking the language, we'll look into it.

There won't be new feature development in CbB, but there will likely be an occasional maintenance update as needed.

If you have specific issues, make a formal bug report and include relevant details on how to reproduce it.

Likely the file still being in use by windows. Try rebooting and run the installer again. If you downloaded through the app, the installer will be in your Windows Downloads\Cakewalk folder.

That's inherited from older versions you've installed previously. We don't add anything for Landr for new installs.

There's a number of themes that come stock with Sonar right now, including ones based on CbB's Tungsten and Mercury, but there's potential to make things more customizable in the future. Old themes themselves are not compatible with the way the new UI works.

Figured out what the repro is, it only happens when the dock is the full screen width rather than the default width. It's logged on our end. Thanks!

So long as it's configured properly the FaderPort 16 should work fine with Cakewalk. I'm sure @msmcleod could give you some pointers, but I run the Faderport 8 with the standard MCU mode and it runs fine on my end.

We'll have some more formalized places to discuss Sonar coming, but for now you can continue to post about it here. Also note there is "Report a Problem" link in the Help menu.

That's how it's been since that feature was implemented. The goal was to have audible playback of midi files for people without external MIDI gear. If you have ports enabled, the MIDI has somewhere to go and we assume you've set up for external monitoring, per that type of workflow.

It only auto loads tts1 if there's no physical midi ports enabled. So if you have a port checked, it won't load it with a midi file.

Please share what your current display configuration is including the number of displays, what their resolution is, and what scaling is being applied.

It would be highly unlikely. That's been thoroughly tested and we have not had any reports through the ongoing beta process about any conflicts.

Cakewalk Sonar still uses Shared Utilities. Sonar installs alongside Cakewalk by BandLab the same way CbB installs alongside SONAR Platinum.

I couldn't repro a problem rescanning in SONAR X3. It sounds like you might have a particular plugin that was causing the scanner to fail.

It's not as if TTS1 was removed because we don't think GM is a viable workflow. Plus as I said, the MS Wavetable synth isn't something that's ever been a part of the app itself. We simply expose whatever MIDI ports are available in Windows. There have been no changes in the app to remove that. We definitely would like to have some kind of alternative in the future. Personally, I wouldn't want to rely on a GM player for backing tracks. There's much better sounding alternatives, but obviously that's subjective on a few levels.

Product Center downloads to wherever your user Downloads folder in Windows is.

The MS Wavetable synth was never in the app itself. It may show up depending on what driver mode you're in, but it's not really a great solution. The synth is part of Windows. It functions exactly the same as if you were using a physical external MIDI module, but without an obvious way on how to pump that back into the app if you needed. TTS-1 was requested to be removed by Roland. In any case, we were not able to maintain it as it's Roland's source code, and it's been noted for having increasing stability issues as time has gone along. You're definitely right about very quickly feeling like you're in 1998. Not too many people use that kind of workflow these days. Not unless you're working with hardware modules.

They go to the Downloads folder in Windows, which is the same place that the in-app updates go.

If you're on build 098 for CbB, Product Center should see that it is currently installed. It's possible you might need to refresh in CPC. Product Center was updated yesterday to build 051 so the auto-update is expected there.

The 2024.02 update has now been formally released to all. Thanks to everyone for their participation in Early Access!

Hi Folks, Please note that the installer has been updated to 29.09.0.096. This build features an improved sign in workflow. Thanks!