msmcleod

You might be able to do this with the Theme Editor. It's installed from the "Install Addons" dropdown on BandLab Assistant.

I meant defining your key mappings is for the most part a one-off operation.

Like I said in my post, "Changing all your key bindings, may make any help you get here that suggests key shortcuts pretty useless to you - and it'll also impair your ability to help others." IMO there's two main reasons for the key mapping: 1. To tweak what's there, e.g. add a key mapping to a CAL function or other function you may find useful in your workflow. 2. For engineers who are using your system who normally use another DAW - i.e. in %APPDATA%\Cakewalk\Cakewalk Core there are key mappings for the major DAW's that you can apply, so someone who is not used to Cakewalk can work more smoothly. There's nothing to stop you using it. I'm just saying the interface was probably designed with small tweaks in mind. I don't work for Cakewalk / BandLab and I didn't write the manual.

I agree with John here. The key binding functionality in Cakewalk is perfectly adequate. Although the more graphic method in ableton might seem nice, I suspect the sheer number of key bindings currently in Cakewalk would negate any usefulness of this type of an interface. Also bear in mind the effort required to develop such an interface for what should be (for the most part) a one off operation. I'd strongly recommend trying to learn the key bindings as they are, rather than trying to re-define them. Changing all your key bindings, may make any help you get here that suggests key shortcuts pretty useless to you - and it'll also impair your ability to help others.

IMHO since the option to save audio files alongside the project appeared, bundle files are for the most part no longer needed. Before this option appeared, the audio for all projects was stored in one global audio folder, so the option to save as a bundle made sense as it would put everything that was needed (i.e. only the audio files associated with that project) in the one package. Nowadays, you're as well just zipping up the project directory. That way you get everything, including groove clips, region fx etc.

I think the OP means this isn't happening:

The Studio Instruments package, Theme Editor and Drum Replacer are optional installs in the "Install Addons" menu on BandLab assistant. You don't need to install them. All the effects (including Breverb) are installed by the core Cakewalk installer. Studio Instruments is exactly that - just instruments.

Take a look through the threads on http://forum.cakewalk.com - there's months worth of reading regarding this!

I've found this happens when I've chosen the "wrong" detection algorithm for the job. Try changing the detection algorithm, and see if this helps. Note however, although you can switch algorithm whilst the editor is active in the MultiDock, you'll lose your previous edits. So try the various detection algorithms first, then stick to that. If you need to switch and keep your edits, bounce to clips, then create the region fx again.

I've got "Designing Audio Effect Plugin-Ins in C++" as well as the 2nd book on writing software synths. I agree that they're both excellent books, and very easy to understand. They use their own bit of wrapper software though, to design your plugins. It generates the VST / AU / AAX code from the software, giving you stubs to fill in the code with. This is a bit of a double edged sword in a way. On the one hand, it means you're not getting to learn how to write these things from scratch. But on the other, it gets you up and running VERY quickly, and makes supporting multiple plugin formats very easy. I'd highly recommend them.

I thought you might be able to use the new "MIDI Learn" function, but I can't work out how to route this to VST effect parameters. You can do it using ACT though... Craig Anderton wrote an article way back in 2007 about this: https://www.soundonsound.com/techniques/using-sonars-act-hardware-controllers

I'm seeing 40 posts per page in both Chrome and Firefox.

Sorry, just re-read your original post. It looks like you created this project in CbB - I'd assumed it was created in an earlier version of Sonar (reading too many threads today!). This won't be a 32 bit DX issue. When the error comes up, I'd go to Task Manager and right click on Cakewalk, and create a crash dump. If you put this file up on a file share somewhere and contact Noel / BandLab support, they should be able to help further.

Are the Sonitus effects 32 bit DX plugins ? I can see this causing a General Error. 64 bit Windows apps can't load 32 bit DX DLL's, and in fact it sees them as different effects as their GUID's are different.

Same here - all I see is "Download Mix", even though my BandLab project has separate audio tracks. EDIT: I can see the "Download Stems" option on the BandLab editor (in the browser), which allows me to download each track as a separate m4a file. There's no "Download Stems" option on the BandLab Assistant though, and I can't see anything to save as a blx file.

As long as the "Copy all audio with project" option is checked, Save Copy As will do it. When you enter the new name, it should prompt you for creating the new project / audio directories.

Try this:

You need to vertically resize the track by dragging the separator between the tracks:

Also worth checking out: iZotope Nectar (both full version and elements). It includes pitch correction alongside all the other vocal type effects. Waves Tune Realtime Waves Tune

Isn't General MIDI 2 nearly 20 years old now? I think the spec came out in 1999. MIDI 2.0 is a different beast, and looks pretty cool. I especially like the MIDI CI part, where controllers can actually tell your DAW what their capabilities are.

You don't need to save as a Cakewalk Bundle (cwb) - a Cakewalk project (cwp) will save exactly the same information. All a Cakewalk Bundle file does, is store any audio track data alongside the cwp in the same file, whereas a Cakewalk Project just saves the project and references the audio files on disk. As far as your patches - are you sure you're setting the all of the four MIDI options, i.e. the correct port, channel, patch and bank select details within your tracks?

On the track, make sure the Track Layout is set to something that will show the MIDI channels - e.g. ALL: On the track inspector:

For the past couple of updates, only the updated files are downloaded. For me the update process via BandLab assistant took less than 30 secs.

Note this will only appear once you've engaged ripple edit. Once it does appear though, you can toggle it on and off.

I guess you could, as long as you keep an eye on the phase. I'd recorded the guitar parts in the living room while I was doodling, so there wasn't any mics set up and I wanted to get it recorded before I forgot it (I hate getting older). As Mr Scheps says, the only thing that matters is what comes out of the speakers... if that works, then great.