msmcleod

As to why... I really can't add much more to what @Creative Sauce says about it. The whole first half of his video is on why you might need them. Obviously if the VST's you use don't support any sort of key-switching, then you probably don't have a need for them. Both videos cover how to create your own maps.

@Creative Sauce's and @Xel Ohh video's pretty much cover 90% of it. Is there anything specific you're unsure about? https://youtu.be/8miZoWXxz3Q https://youtu.be/owkYPMuhcQo

@Herve Maratrey - what you might want to try, is forcing Cakewalk to use your integrated graphics rather than your NVIDIA and see if this improves things. I've had to do this with my laptop, due to incompatibilities with some plugins. You should be able to do this from your NVIDIA control panel:

Can you PM me a copy of your project ? - I can't reproduce any crash or hang.

It shouldn't be... the only condition for keyswitches being in the same clip is when the articulation generates more than one event (e.g. CC n 127 at start, CC n 0 at end) . In this case, both events need to be in the same clip. It any case, it shouldn't crash or hang. We'll look into it.

%APPDATA%\Cakewalk\Cakewalk Core

It isn't clear from your gif / conditions what exactly you were doing to get this behaviour. I've tried to replicate what you're doing, but can't. Can you detail the steps one by one from a new project?

Unfortunately I don't know the cause. I did chat to @Noel Borthwick about it at one point, but we never got around to investigating it further. As this only affects a handful of plugins, it's highly likely its something in the plugin itself - maybe it's doing something in its main processing loop it shouldn't be, or making a bad assumption about what threads are doing what. This is the kind of thing that normally requires an in-depth debugging session with the plugin developer.

I'm not sure tbh - the reason I used it with JBridge was because I was getting clips & pops on even the highest buffer settings. Switching to JBridge allowed me to run at a buffer of 64 (and on small projects, 32). So latency was negligible. If JBridge introduced any further latency, it would be in the scale of microseconds rather than milliseconds.

You can do this already using JBridge by clicking the "Use JBridge Wrapper" in the plugin options (assuming you have JBridge of course) I do this for the UJAM Virtual Guitarist series.

I understand the problem, but if I perform exactly the same steps as you have, MIDIOX always shows both MSB & LSB being sent when the Bank Select method is set to "Normal". You could try forcing the method to always use normal by adding the following to your .ins file:

Manually copying/pasting DLL's around is likely to cause issues with upgrades. I suggest you change the locations within Native Access itself so that things are installed to the required location: Alternatively, just add the default Native Instrument path to your VST path within CbB's VST Settings:

When using either BitBridge or JBridge, the 32 bit plugin is run in a completely separate process. As this is outside of CbB's internal engine, it won't be included in its performance measurements for the engine, or indeed "Overall App Performance". It will however be included in "System Performance"

It looks like the expression automation is living in the audio track rather than the MIDI track. You can fix this by doing the following: SHIFT + Click on the beginning of the expression curve (which will change the filter to show this envelope) CTRL + A to select all the envelope nodes, then CTRL + X to cut them Split the instrument track Select only the MIDI track, making sure the now time is at zero CTRL+V to paste the envelope back into the MIDI track Select both tracks and "Make Instrument Track" If you then SHIFT+Click the automation lane icon, you'll see your expression curve in the correct place I'm curious as to how it got in to this state, so if you do come across it again please note down exactly what you did and let the team know the steps to reproduce.

You can do both of these by using "Extract Keyswitches" in the 2020.11 Update 1 Preview.

I'm not seeing this issue, either with setting the bank/program in the inspector, or by using the patch browser. In both cases, both MSB & LSB, plus the program change are being sent: I take it you have definitely set the MIDI Output channel in the inspector? As the instrument file mapping is per output device/channel, you need to set the channel output - leaving it as none will mean nothing gets sent out:

FWIW... The MIDI standard specifies that any Note On message with a velocity of 0 should be treated as a Note Off. The main reason for this is a thing called "running status". Normally, a note MIDI message consists of three bytes: Byte 1: Note On Command/MIDI Channel Byte 2: Key number Byte 3: Velocity All command messages have a value > 127, so any receiving equipment can tell the difference between a command and a parameter ( because parameter values are always less than 128 ). Once you've sent the first note on message, as long as all subsequent notes are on the same channel you can skip sending the command and just send the key & velocity. Having velocity 0 being the same as Note Off means you can effectively send both Note On and Note Off messages in this way. So if you're just playing notes on the same channel, this reduces the data being sent by 1/3rd. This is particularly useful for controller keyboards sending notes out on a single channel over a standard MIDI cable at 31.25Kbits, or older equipment with small buffers receiving the data.

can you post a copy of your ins file? I had a similar issue with the Yamaha XG ins file, and a small edit to the ins file sorted it.

If double clicking on an articulation map does nothing, then it has detected no differences between the articulation map on disk, and the one in your project. Could you post copies of both the original map (use export to save it) and the one you're trying to update it with?

Use Manage Presets, and define it there.

Don't uninstall SONAR X1 though... you'll want to keep all the freebies that came with it. Just install Cakewalk alongside it.

Are you sure it's not related to musical vs absolute time? For example, say my project is at 120bpm and my clip is at measure 5, but set to absolute time ( 8 seconds in ) Changing the tempo to 240bpm, means my clip STILL plays at 8 seconds in, but on the time rule it's now at measure 9.

Cubase actually has this functionality - they call it "Remotes". It basically allows you to map any MIDI key to any articulation note (regardless of what the real articulation is). We deliberately left this out for the time being as: 1. Part of the point of having articulations is that you don't have to play them in real time; and 2. There were other complexities involved, and we didn't want the scope to creep. There is another complexity in that you don't have an articulation lane until you've added an articulation from a map... So in addition to supporting re-mapping real-time MIDI input to articulations, we'd also need to provide a way of choosing an articulation group up-front before you start recording. Of course all this is possible... it's just a matter of time, resource & priorities. However, in the next update you will be able to extract articulations from an existing MIDI data. So if you've recorded your articulations in real-time (or you've got an older project with your key-switches in the main MIDI clip), you'll be able to convert them to articulations.

The button is here:

Follow will use the MIDI Channel of the articulation itself, rather than being fixed to a specific MIDI channel, so you just set it on the articulation itself: