Promidi

What have you tried so far?

I have CAL script that can do this. Then I assign that CAL script to a keybinding.

Yeah, I tried that here multiple times , but do dice..... I take it you didn't have to say any magic words for it to work.....? There might be some obscure set of circumstances that get it to work....... Should just work straight out of the box. I wonder what support will say?

Confirmed here. Maybe drop a note Cakewalk support here: https://help.cakewalk.com/hc/en-us/requests/new?ticket_form_id=360000025633

CAL scripts can do that

Select the SI-piano track, then Press “ i ” to open the inspector. In the inspector, down the bottom, you need to set the input of that track to your midi-keyboard (Under “In/Out”)

With Cakewalk closed, see if renaming ctrlsurface.dat does the trick. This file is in the following folder: %APPDATA%\Cakewalk\Cakewalk Core

Oh now I'm getting it, you want everyone else to do your leg work for you.......

Like I said...Install the trial.

According to Arturia’s website, all their synths require Windows 8.1+ or above..... so it looks like that’s a no. If you want to know for sure..... then install a trial of one of the instruments. Even if it does happen to install and appear to work and you run into issues, you will not get any support. Really, in this day and age, you really should be using Windows 10 or above (Many programs are now off limits to Windows 7 users)

Are you sure there are no effects on the master bus? What about the pro-channel for the master bus - any effects in there? You might have configured Cakewalk to add a default Bus Pro-channel configuration when a bus is created.

I simply edit the KBN files is a standard text editor. That being said, the only reason I have ever needed to edit the KBN files is to delete duplicate entries and crop up from time to time. These duplicate entries can prevent the intended binding from working. Other than that, CbB is really the best place to edit actual bindings. KBN files only contain codes anyway - The only human readable text in KBN files are where keys are bound to CALs and Studioware panel. All other functions are just numbers.

That’s good to know. (Sometimes it’s hard to keep up with all the changes) I uninstalled Edge Webview2 Runtime. Opened up CbB, Signed out from Bandlab (from Help menu) From CbB I then signed back onto Bandlab. As Firefox 99 Beta 5 is my default browser, this is what opened with the login challenge. I entered my Bandlab credentials and this was accepted and CbB signed in So I can now ditch Edge Webview2 Runtime and have Firefox as my default browser without it affecting my ability to sign into Bandlab from Cakewalk.

Some people way not wish to change their default browser to Edge. This is why the Microsoft Edge Webview2 Runtime is included with the Cakewalk install, so that Cakewalk can internally log on to Bandlab to activate. See:

Contact Cakewalk Support https://help.cakewalk.com/hc/en-us/requests/new?ticket_form_id=360000025633

That looks like a Windows issue rather than a Cakewalk issue. I have never had the issues that you have described. If you go Start + Run appwiz.cpl, is “Microsoft Edge Webview2 Runtime” listed there. This component is required for Cakewalk to handle logging on into BandLab to authorise without the need for BandLab assistant. This is installed along with Cakewalk by Bandlab since 2021.1

These prices makes me wonder if anyone ever buys them at MSRP

The uninstall information for many programs (including Cakewalk) is stored in the registry I think you have bigger issues if Windows 10 crashed and Cakewalk BandLab will no longer show up in the uninstall. You might want to see if you (or who ever you get to look at your PC) can find out the reason for the crash. It could be a hard drive on its way out. You can use the Windows System Event Viewer to check for hard drive issues. You might find other warning or error events there as well that might give you a clue. It could even be a faulty driver that crashed Windows You could attempt a system restore (Start Run rstrui). But, personally, I would want to sort out what caused the Windows 10 crash first before trying to uninstall and reinstall Cakewalk.

When ever I find a plugin that is just a single file (.DLL or .VST3), I simply place that file in a folder listed in Preferences | File |VST Settings > VST Scan paths. If it's a DLL file I place it in a VST2 path. If it's a VST3 file, I place it in a VST3 path (Which is usually C:\Program Files\Common Files\VST3) Then I do a scan - either from the Preferences | File |VST Settings dialogue or from Cakewalk Plug-in Manager. Because I use Custom Plug-in Menu Layouts, I use the Cakewalk Plug-in Manager to place that plugin name (which I can always find) in my custom Plug-in Menu Layouts. For me, this works every single time.

Oh ok

I ditched Bandlab Assistant ages ago. It it no longer needed. Just use the web installer to install the vastly superior Cakewalk by Bandlab. https://downloads.bandlab.com/cakewalk/setup/CakewalkSetup.exe

One thing you might want to try is to download the beta drivers for the scarlet range. The release notes speciality mentions Cakewalk by Bandlab http://beta.focusrite.com I have a PC configured as per signature and I do not experience dropouts while recording.

Title says it all See: https://www.kvraudio.com/forum/viewtopic.php?t=578991

In the LABS GUI: Are both sliders up? Is the MIDI Channel correct. Or does it work if MIDI Channel is set to “ANY” (Top and centre) Is LABS Volume up ((Top to the right)

Have you enabled EnableWin10DPIAwareness=1 in Cakewalk.ini ? This can be edited in Preferences | File | Initialisation File