Promidi

Slight correction. Windows itself allows multiple ASIO devices installed. Any one Windows program itself cannot have two ASIO devices selected therein. (Which is why the OP's Focusrite ASIO was greyed out in CbB) If you have multiple ASIO devices, Cakewalk can use use one ASIO device. Another program (ORB Studio for eg) can use only one of the other ASIO devices. The two programs can run at the same time using their respective ASIO devices. The only stipulation is same sample rate, bit depth and (I think) buffer size for all ASIO devices.

These days, the currency can be hard drive space..... Even at $US48, the 288GB part is a bit expensive.

Same here.

Just tried it and I am not seeing that behaviour here. Can you give us more information? Are you sure you’re using track FX not clip FX

Which is what I stated.

Ah, that’s why I couldn’t find it in the manual (yeah I know, I actually read the manual). I was searching for the phrase “invert selection” or something like that.

One bug fixed that effects me is that with CbB, MIDI chase did not include any aftertouch events. With Sonar, it does (both Key and Channel). Also, the ability to set a default instrument when you add a SIT is handy too. But as you say, YMMV.

Bringing back some more colour options in Preferences would be nice. Many have been removed in Sonar that are present in CbB.

What happens if, with the selection as shown, and the Smart Tool enabled, while CTRL is pressed, you right drag a marquee around the notes you want to invert the selection of? I tried it here, and indeed, this did invert the note selection within the bounds of the resultant selection marquee.

I have to agree there. I spent a long time making my theme in CbB just how I like it. I would hate to have to give it up - which, it looks like, I will have to.. (The Bakers did say that the new Sonar would not support theming).

At what part of the installation does the error message "This software requires installation of the intelLok(R) device drivers and a reboot before running..." appear? Are you sure “This software” is refering to Cakewalk by Bandlab? If Cakewalk by Bandlab is scanning your plugin folder, and it comes cross a plugin file that requires iLok (or “intelLok” , then I believe this message would appear. There is definitely a file on you PC somewhere that is generating this message. Start looking in your plugins folder. It will ether be a DLL file or (less likely) a VST3 file. Try C:\Program Files(x86)\Steinberg\VstPlugins or any other VstPlugins folder. I can categorically guarantee that Cakewalk by Bandlab itself does not need any form of iLok to install or run.

7.5 seconds from shortcut click to product list appearing here (PC config as per sig). NA 3.90

Update via Izotope Product Portal Updates & Improvements CHANGED Minimum supported macOS version to macOS Monterey ADDED iLok Enterprise support ADDED Support for macOS Sonoma ADDED Support for Cubase 13 and Reaper 7

Interlock? Wasn't this a precursor to iLok? I have never seen CbB needing any form of iLok or Interlock. Check in Control Panel, "Programs and Features" (Start + run appwiz.cpl ) to see if you have any old plugin installed. There must be something on your PC causing this that is outside of CbB’s control. Note: Windows 10 has a known incompatibility issue with really older iLok drivers. They causes a blue screen (even in Windows safe mode. Some older SONiVOX plugins were known to cause this. The only way out of that one (short of a full Windows clean install) is to boot from a CD Windows repair software and change “TKPD.sys” driver from “boot” to “disabled”.

Feels a bit intentional...

What!!?? You didn't rename it instead?

I don't see any ads on YouTube thanks to uBlock Origin.

Another thought I had is that a higher tier of Cakewalk might actually include Roland Canvas VA. Of course, there would have to be some negotiations with Roland to allow this, and what the licence fee from each sale of Cakewalk Sonar to Roland would be.

What audio interface are you using? If you are using on board sound with ASIO4ALL, please do yourself a favour and get an audio interface that comes with native ASIO drivers. BTW rename your AUD.INI file rather than delete it. This file is found in the following folder: %appdata%\Cakewalk\Cakewalk Core

What I would do is create a RechannelMIDI=1 entry under the [WinCake] section in the Cakewalk.ini file Then after you have opened the MIDI file in CbB, select all, then bounce tracks. This combines all the MIDI clips on each given track to one clip per track. This will also rechannel all the MIDI events to match the MIDI channel if the MIDI tracks that those events are on. The MIDI tracks will retain their track separation. Don’t use Omni. Make sure your MIDI tracks are set to specific channels.

New in version 5.7.4: Fixed a potential crash when disabling the AmpliTube plugin while it contained TONEX gear. General reliability improvements.

If you have Melodyne 5 installed, then you would (should) have updated from Celemony themselves. I have Melodyne Studio 5.3.1.018 and this is the latest version. I intend to ignore the version from Cakewalk Product Centre. Melodyne updates are done from the Melodyne GUI itself and are handled by Celemony.. The Cakewalk Product Centre version would be for those who do not have any version of Melodyne installed and want to run the trial.

Actually, come to think of it, I think you’re right. If one has VSTis in a project, then those ports become available as destinations for Sysex banks in Sysex View. Unfortunately, The only VSTis that states it can receive Sysex data that I have is ShowMIDI. This is a handy utility that can show MIDI data streams, including sysex. I tried sending sysex data to ShowMIDI, using Banks. and this did not show any sysex as being received. Of course, Raw sysex Data events (not banks) will be sent to the first available port, which for many, will be a hardware port. Cakewalk probably needs a better way to handle Sysex data to VSTi, rather than using port numbers (which can change, depending on the number of VSTis in a project) But was are digressing, this topic is TTS end of life

What we also need is the ability for Cakewalk to send Sysex data to VSTis. Currently, Sysex can only be sent to physical hardware ports. Personally, I use a lot of sysex for the SW1000XG (My clients to require this). For Roland GM/GS sound modules to be properly and more fully emulated, Sysex needs to be part of the equation (with Roland or Yamaha). This is because Sysex tends to be where most of the cool stuff happens.

If you need to do a fresh install without the Cakewalk Product Centre. Mind you the Cakewalk Product Centre will do the install for you - that would probably be easier.