msmcleod

Have you tried deleting AUD.INI from %APPDATA%\Cakewalk\Cakewalk Core ?

I think this is still the standard, but they've also come out for a standard wiring of 3.5mm TRS jacks for MIDI (maybe 2.5mm too). But an adapter would be simple enough to get.

Jesse's just confirmed, the "Download Stems" command has now been added to BandLab Assistant:

Awsome - thanks Jesse.

Yeah, this was reported in this thread: Looks like they're going to release a fix later this week.

Looks like there's an update to BandLab Assistant today. It's now at 5.03. There doesn't seem to be any visible differences between it and 5.02, so must be under the hood stuff.

I can recommend the Focusrite Scarlett 6i6, which is around £175. This gives you 4 analog ins and outs, plus a SPDIF in / out. Also look at the Focusrite Scarlett 2i4, which gives you 2 ins and 4 outs, at £139.

I setup the following configuration: Behringer ADA8000 -> (ADAT) -> Yamaha i88x -> (ADAT) -> Focusrite 18i20 I couldn't perceive any difference in latency between a hardware synth plugged into the ADA8000 and it plugged directly into the 18i20. I tend to be far more sensitive to latency when using piano sounds, so I was using a piano sound on my JV1010 and hardware monitoring enabled on the 18i20. This was to remove any latency introduced by the USB audio drivers. I couldn't perceive any latency at all with this setup. On the other hand using a VSTi piano, a latency of 6ms was obvious. A 2ms latency with a VSTi, not so much. What I didn't think to try was splitting the signal, so basically record the same thing through the ADA8000 and a direct connection to the 18i20 at the same time. The next time I get a chance to try this, I'll report my findings.

Actually, if the thin version was simply a copy of what you see in the channel strip, but just for the current track & it's bus it would probably work. That way you'd have: Very Thin PC - same as "Narrow Strips" in channel strip Thin PC - same as normal channel strip Full PC - normal ProChannel

List of ids up to and including Sonar X3 below.

The ones that are not assigned are likely to be ones that have been deprecated & removed over the years. Remember this list started it's life over 30 years ago. Quite a few commands have come and gone, and been replaced by others. There are definitely duplicates. I saw several examples of the same command id mapping to more than one item in the drop-down list. This is simply because it's the same command is accessible from more than one menu or screen. As far as the highest number goes, 1250 seems to me to be more in line with what I've seen in the .kbn files. Also be careful not to count the CAL scripts or StudioWare mappings. They are handled completely differently, and don't have a corresponding command id. e.g.: Kx00520F=RANDTIME.CAL Kx00390F=GENERAL MIDI.CakewalkStudioWare

For live emulation of an acoustic I use a Roland VG88. I've also recorded with it, but it's not quite as convincing. For live though, it's great. Another good plugin for guitar modelling is Peavey Revalver, although it is limited in how far it'll go. So electric to acoustic is ok; the other way around, not so much. It works best at using one electric to emulate another. I'm no guitar virtuoso, so I've used it on guitar solos to mix a live guitar with the crazy fast sections played on Shreddage II. I model both my own guitar and shreddage II, then put them through the same destination model so they sound the same.

If you open up the .kbn file, each key binding is represented by two numbers, separated by an = e.g.: Kx004103=1 The first number represents the key pressed - e.g. Kx004103, in this case "A". Part of the number at least, seems to be based on the keyboard codes: https://docs.microsoft.com/en-us/windows/desktop/inputdev/virtual-key-codes The first four digits are the key code (e.g. 0041 is "A" ) corresponding to the codes in the link above. The last two digits are the shift state, so: Kx004103 A Kx00410B A + CTRL Kx004107 A + SHIFT Kx004113 A + ALT Kx00410F=A + CTRL + SHIFT Kx00411B=A + CTRL + ALT Kx004117=A + ALT + SHIFT The number after the "=" is the shortcut command id. CommandIds.h within the Cakewalk Surface Control SDK has the definition for each of the shortcut command IDS: https://github.com/Cakewalk/Cakewalk-Control-Surface-SDK/blob/master/Framework2/CommandIDs.h Unfortunately the list stops at Sonar X3, but you should be able to work out the missing ones by creating a temporary keymap and cross referencing them with the id's in the .kbd file created.

I agree with @Base 57 . This definitely sounds like a plugin not authorised. You say you cloned your drive? It's likely Addictive Drums needs re-authorising. It gets upset at the smallest thing - even major windows updates. Just fire up the XLN Online Installer, remove your computer and re-add it again.

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