Jonathan Sasor

We now have an in-house repro for this issue. Adding the plugin after inserting the track template is the specific nature of the bug. It's now logged on our end. I can't guarantee that a fix will make the pending 2019.07 release, but we'll definitely look into it soon.

If a newer build than the Early Access one is released, you'll see the "an update is available!" Notification in CbB and you can download and install from BandLab Assistant without having to uninstall Early Access.

To participate, all you need to do is grab the link in the first post, and download/install. It requires the most recent (2019.05) update to be currently installed first. If you need to roll back to 2019.05, you then run the uninstaller for Cakewalk, then reinstall from BandLab Assistant.

Drum Replacer can trigger its own samples internally or you can use it to convert parts to MIDI and use any drum synth.

Make sure you've got the dip switches on the console set for separate operation, but it should work, provided you've got the driver installed and you set the surface up in the Preferences.

Are you using new projects with stock templates or an existing projects/custom templates? If you're changing the metronome and getting different effects, do you currently have a count-in set for it?

I'm going to add a quick point before I lock this, (as this thread has run its course). Any DAW system has a lot of moving parts. There's definitely cases where things can be system-specific. We put a lot of effort into trying to replicate issues as closely as possible. We also do our best to work with users directly to resolve problems when necessary. As I mentioned in my previous post, the best way to resolve problems with Cakewalk is to contact us. If there's a system-specific issue, we can help troubleshoot those problems. If we find an issue with Cakewalk, we'll make sure it's in the system and we'll fix it as resources allow. Any major issues like data loss or stability always get high priority. This forum also offers a great opportunity for users to help each other, and we definitely keep an eye on things here as well, but its always best to contact support directly when it comes to troubleshooting issues. They're always happy to help.

Just to chime in here, when it comes to Scott's plugin settings disappearing, it's possible he's having issues related with using VST2 and VST3 of the same plugin instances. I haven't used Fab Filter in a while, but I regularly work with a number of different third party plugins (including Waves) and have not seen that issue myself. If there's a concrete case where we can see a problem with Cakewalk not retaining settings with a project, we would fix that ASAP. Sometimes problems like this are on the plugin side, and we frequently will work with third party developers to troubleshoot where any potential breakdown is happening. As for his spacebar issue, that's the first I've heard of it. It sounds like possibly he was doing something on his system that was preventing Cakewalk from having the proper focus for the shortcuts to work. We are always interested in resolving pain points for users. If something doesn't seem right, we recommend you contact us. A lot of times, something on the system might just need to be adjusted, and we can help with that. Otherwise we can verify any potential issues and fix them. We're always working to make Cakewalk by BandLab be the best program it can be.

When you initially install CbB (or any previous Cakewalk program), it defines shared user paths in the Registry. If you do a clean install, you'll be able to reinstall and define those paths to another drive. If you simply want to move your project/content folders, you can adjust the settings in the Preferences on the Folder Locations and Audio Data tabs.

By default when you create a new project, it will use the global audio folder until you save the project. Then it will give you the options to setup a project folder and copy the audio there.

Yeah, that's a very out of date system if they're getting that error. They'll likely need to do a whole slew of Windows updates depending on which version they have.

This fix is working properly on our end. It deals with the tab name for synths with their UI docked in the multidock. If you insert a synth, then dock the plugin UI in the multidock, then change the name of the synth in the Synth Rack, the tab name should now update.

This might be a silly question, but when you go into the sample rate settings on the Octa-Capture itself, what is it currently set to? Octa-captures can cause CbB to throw that message if the project sample rate and the device don't line up. You can get the details on how to set it on the device here.

If you're trying to get the plugin to read your audio as you're playing it, make sure you have "Input Echo" enabled on your track.

If the task doesn't shut down, that's typically related to the audio driver.

Project files are fixed at whatever sample rate they were originally recorded at. You can bring any audio into a new project at any sample rate you choose and it will convert to the project setting, but the projects themselves stay how they were created. Depending on the device, some will change automatically when opening a project at a different sample rate, and others require you to set the sample rate on the hardware or via the device's control panel. The device needs to match the project sample rate to play back.

Nomenclature can be a hurdle when getting going. In this case, an Instrument Track refers to a track that has a MIDI input patched to a virtual instrument (soft synth) with an audio output. It's a streamlined combination of the old method that required having a separate MIDI source and Synth Audio Output track.

You need to check what your MIDI track is going to. A MIDI track in and of itself will not produce sound as MIDI itself is only note/controller information. In the demo projects, the MIDI tracks should be routed to a virtual instrument such as the General MIDI synth, Cakewalk TTS-1. When your track routes to the TTS-1, you'll see different bank and patch options. Other synths will work via their own patch browsers. If you're using external synths, make sure you have your audio monitoring from those devices set correctly.

You can also check out performances from the BandLab booth here: https://www.bandlab.com/cakewalk_team

Simplest answer is to do a full install of SONAR Platinum first, then install Cakewalk by BandLab on top of that. This way CbB will leverage all the content that was included previously.

The 5.0.4 update resolves an issue with uploading projects from CbB to BandLab.

BitBridge is the default way that Cakewalk loads 32-bit VSTs, however we support using the third party wrapper jBridge as well (which you would need to purchase separately). In the Plugin Manager, select your 32-bit plugin, then hit the Plugin Properties button and enable the checkbox to use the jBridge wrapper.

You can find it here: https://www.bandlab.com/products/cakewalk/whats-new

Windows 7 is technically supported, but gets the least of our test resources as its not under active development from Microsoft (and hasn't been since 2015). The security patches run out January next year. Similarly, the overwhelming majority of users are running 64-bit systems. Cakewalk will still run most 32-bit plugins via Bit Bridge (or J Bridge). I'm not sure where "Cakewalk on a rental basis" is coming from... We've been delivering a free version of what was previously SONAR Platinum with all its core features intact, and improving upon that for almost a year. Once the application has authorized on your system, it's not going anywhere.