Promidi

Unless the reason for the laptop is mobility, you might want to consider a desktop or a tower instead.... i7 or i9 4 core or above CPU, 16 to 32gb ram and SSDs all round. Try for a dedicated graphics card as some plugins use the GPU for their GUIs. Having it configured property for DAW use is actually more important that the hardware these days.

When you're saving, are you saving as MIDI files or as Cakewalk by Bandlab (*.CWP) files ? On that list of things you mention, MID files would not contain those items. To save those items, you need to save as a native CWP file.

Can you do another screenshot - this time showing the bus settings, including the inspector.If the Focusrite is properly installed and selected in preferences, it should show up in the drop down.

Are you changing General Bindings? Are you wanting to use the CTRL key with the row of numbers on the top of the keyboard or the numerical keypad on the right of the keyboard? They have separate names in the keybinding settings. The numerical keypad key are actually called Ctrl+Num 1 (to 9) in keybindings. Also, are you using a lense at all? Some versions of CbB had issues with Keybindingd when a lense is used. I believe this was fixed with later releases. Also are you using the latest CbB?

I have reassigned CTRL 0 to 9 to select different screensets and this has worked correctly for me for quite a while now. I use Ctrl+2 for every session. I am using the latest Cakewalk by Bandlab (2019.9 Build 70)

Contact cleaner

Do they seriously believe any sane person would ever pay $US155.00 (The full price after Jan 2, 2020) for a synth that does not have velocity?

The deal breaker for this synth for me is no velocity.

Press pause on your computer keyboard.

My system images my system drive every Wednesday and Saturday at 4:00am. It take a whole 12 minutes onto an external USB3 drive..

Cakewalk by Bandlab does indeed support Aftertouch MIDI events. Both Key and Channel Aftertouch is supported. AD2 can respond to Aftertouch MIDI events for choking the cymbals. However, AD2 responds to Key aftertouch events for this but does not respond to Channel aftertouch. To choke a given cymbal, you need to send a key aftertouch event on the same note that triggered the cymbal to do the choke. For example to activate a Cymbal 6 followed by a Cymbal 6 choke you need to send the following (as viewed in Event List view) Note G5 KeyAft G5 {any value} I am not sure if the Roland TD 11kv can be configured to send Key Aftertouch events when you grab the cymbal. I looked in the user guide and the word aftertouch does not appear anywhere in there. Another way is by hitting the black key immediately to the right of the note that triggers the given crash symbol. So using the above example, the choke can be activate with a G# You will have to check the Roland TD 11kv manual to see how to configure what gets sent when you grab the cymbal. Maybe you can use notes instead of Key Aftertouch. I hope this helps

My system drive is a 500g Samsung EVO 960 with 137gb used

Just tried it here. Both muting and soloing in the Track View, performed the correct respective change in the Synth Rack. I tried it with Rapture Pro, AAS Ultra Analog VA-3 and Glitchmachines Palindrome I am using Cakewalk by Bandlab 2019.9 Build 70

It is actually.....

Works for me..

Try updating Cakewalk by Bandlab without it......

With MIDI prepare buffer, your mileage will vary.... I found in my case that 750 prevented issues I was having with intermittent or hanging dropped notes. It's purely a matter for experimentation to see what works best for you and your system. However, there are probably many people on here who have found that 250 causes intermittent issues Try increasing that buffer size from 128 to say 256 or even 512. Mind you 512 might become noticeable when playing it realtine from your MIDI controller. I have mine set to 256 and that still allows seamless real-time playback with VSTis to my ears.

What about buffer size? I also have never had issues with tempo changes with VSTis

What sample rate, bit depth and buffer size are you using?

The default of 250ms is a little on the low side..... Try increasing it. I have mine set to 750ms. I use tempo changes all the time in my tracks and never have stuttering. Mind you, I am using external synths. Do you have any tempo based delays on that Kontact instrument?

I downloaded "Theme from Mission Impossible" and opened it up in CbB. The SYSEX data is definitely there. It's in track 1 right at the beginning. What I do when looking for SYSEX data in a MIDI file is I select all tracks. The open event list. If present, the SYSEX is at the start, but sometimes it can appear in the middle of the track. I do this at times with the MIDIs I create. You can use the event manager (Under the view menu on the Event List window) to restrict the view to just SYSEX data. As sysex does not contain channel information, it can be in any track.

What is your MIDI prepare buffer set to?

The fact that, in Event list view, CbB replaces with blanks really long patch names as they appear in instrument definition files. I have contacted Bandlab support about this but they have not addresses this issue yet.

ASUS monitor connected with HDMI should be irrelevant. Have you tried updating your video drivers. The fact that Java had issues indicates a system issue rather than with BA. (note: Oracle Java is not required for Bandlab assistant. Maybe you're thinking of JavaScript - which is a different thing) I have always just downloaded the BA installer directly from here: https://www.bandlab.com/download/assistant/windows Of course, when you install BA, make sure the BA process is not currently running by using Task Manager and checking for the presence of "BandLab Assistant.exe" under processes.

I've used SYSEX MIDI messages for the last 20 years with Sonar and Cakewalk products (up to CbB 2019.9 Build 70) to control an external XG device. In all that time I have never had an issue. First this was with an internal PCI card (SW1000XG) that responds to SYSEX. Now it's via a USB to MIDI converter (Roland Um-One Mark II) to an SW1000XG in a second PC. SYSEX data has always been sent and recognised by the intended equipment. Note: With CbB, I found that I needed the MIDI driver mode to be set to MME rather than UWP. UWP always gave me issues of missed data - especially sysex.