Promidi

In the MIDI track, where you would normally tell the MIDI track what synth or MIDI port to send the MIDI data to, select Amplitube 5 on the drop down menu. This is assuming you have enabled “Enable MIDI input” on the Amplitube 5 Plugin window.

Works fine here. Enable “Enable MIDI input” on the Amplitube 5 Plugin window menu (on the down arrow next to VST2 or VST3). Then create a MIDI track with the Express MK2 on its input. Then route the MIDI track to Amplitube 5. Make sure input echo is enabled on that MIDI track.

IKM Product manager 1.0.8 Is fine here, with latest Malwarebytes Premium and latest defs.

Extremely likely. Not according to the release notes. There is no mention, in the 2023.09 Build 62 release notes, that 2022.11 needs to be installed prior to upgrading. See: https://www.bandlab.com/products/cakewalk/whats-new

Personally, I would simply purchase a sustain pedal that has a polarity switch, like the M-Audio SP-2

Also, remember that each piano takes around 20 gig. So that’s 160 gig for the lot. Also, like I said on another post, I would want to make sure I can't make these sounds already with what I already have before I bite.

As long as it does not generate sounds that we can pretty much do with with what we already have. This is what I always consider when a vendor spruiks their new offering. On the other hand, must resist GAS!

I have never worried about actual bank or patch numbers. I simply let the Instrument Definition file take care of that for me. As long as the MIDI track is routed to the MIDI port that the SW1000XG is connected to, and the correct MIDI channel is selected, it just works. Also, in Preferences - MIDI - Instruments, I point the respective Output/Channel to the correct instrument (All except for 10 is “Yamaha SW1000XG”, 10 is “Yamaha SW1000XG Drums”) I have never had to enter actual numerical data to selected Banks and Patches. I also always use the patch browser (which is populated using information contained in the Master,ins file, which itself has data inserted by importing the Instrument Definition file). If I ever imported MIDI data that contains its own Bank/Patches MIDI events I would just delete those and then enter new ones that I know work for the SW1000XG.

I use combination Bank/Patch changes on an SW1000XG MIDI card (which has over 1200 patches) and these patch change events are sent correctly here on 2023.09 Build 62. I use the SW1000Xg Instrument Definition file that I have always used, and the patch names on the downdown still match and play correctly. The correct Bank/patch is always selected on the SW1000XG part at the Bank/Patch change in a given CbB track (or at the beginning from the Bank/patch setting of the track). Something else must be going on here. Is there a way for you to verify what MIDI events CbB is actually sending when a Bank/Patch change is required? Maybe find a way to route the MIDI to a utility like MIDI-OX Note: My Bank Selection Method is set to “Normal”. For any of my MIDI only projects, each MIDI track’s settings are set to their specific MIDI channel.

That is actually a SIT (Simple Instrument Track).

It's amazing the number of vendors who send you emails for products that they know you already own. .....and yes, I believe RC20 is worth it. (although BF is just around the corner - might be a deeper discount then)

My book discussing clocks finally arrived......... It's about time!

I would simply write a CAL script to do this. Personally, I would write the script to move all of the MIDI events to be close to a given time, but with a random shift of the the time position of the events. That way you do not risk overloading the synth with dense MIDI data. I would write the CAL script to move selected events so they randomly congregate around NOW. As you have never used CAL before, you might not know how to do this. Here is a script that shifts all selected controller event to a random position within 50 ticks of the NOW cursor. (do (forEachEvent (if (== Event.Kind CONTROL) (do (= Event.Time Now) (+= Event.Time (random -50 50)) :this line can be removed if you do want the events at the exact time rather than randomly shifted ) ) ) )

Note: requires the full version of Kontakt 5.6.8 or newer

I am going to assume that you have tried pressing “Pause” on on your PC keyboard.

Or a new beginning.....

NDAs would cover BETAs, not Early Releases.

Numerically, what version of Cakewalk are you running?

The only reason I use CPA9 on Windows 10 is to edit CAL scripts and Studioware panels. But open in Windows 10 it does. Note: I am running Windows 10 as a user that has administrative privileges. (Yeah, I know, I should not be doing this blah blah - but I am as careful as I can be))

When you say “keybindings in preferences causes a crash immediately”, do you mean that a crash dialogue box appears, or do you mean that the preferences dialogue box disappears? I ask this because for a while, sometimes on my system, opening Customisation - Keyboard Shortcuts (Advanced) causes the preferences dialogue box to disappear. I have to do another left mouse click to bring up the keybinding screen. Sometime I have to press the P key to bring up the keybinding screen. However, I have never had an actual crash dialogue box from going into the Keyboard Shortcuts dialogue. This is on Cakewalk by Bandlab 2023.09 Build 55.

Yes.

Looks like this issue has now been solved. I can now access all my older product downloads.

Looks like this issue has now been solved. I can now access all my older product downloads.

Make sure the folders as defined in Preferences - File - Folder location matches the actual locations of your templates. (2nd item down)

Getting ready for BBA3 perhaps?