JoseC

He is using a virtual MIDI cable

Open the Sysex View and check that the sysex data are being sent to the right port .

From the Release Notes: "The previous Large mode for the Select module is now the Medium mode."

I am not a big jazz fan, but first thing that comes to mind is Around Midnight, when Coltrane comes in.

Not quite. https://www.statista.com/statistics/442354/music-genres-preferred-consumers-usa/

Once you have the Alesis connected via MIDI, you need to assign the .ins definition file to the port and channel(s)it is attached to. Go to Preferences>Midi>Instruments, click on the Define button, and it will open the "Define Instruments and Names" dialog. Click the Import button, and navigate to find the Alesis.ins file. Import that, close the dialog and now in the Instruments right column you should be able to find your Alesis. Link it to its port and channel in the left column, and you are set. Now when you open the Patch and Bank selectors in any MIDI track with output to that port and channel(s), your instrument´s patches should appear listed, the drum names should appear in the PRV, if available in the .ins file, and the CC numbers will also appear in the PRV assigned to the actual controller names.

I can not check now, but I think that this might be saved with a track template. I tend to insert instruments with track templates, so they come with their color, icons and even favourite presets.

As @scook says above, that behavior can be changed. Anyway, if I understood correctly, the OP complains about the FX windows closing every time he starts or stops the transport, not only VST but Pro Channel FX as well.

If you want to see clip borders clearly in the PRV you can if you change the clip´s background color. That shows in the PRV. If you are using Tungsten, clip´s default background color is about the same as the PRV background, that is why you cannot see it. What you can not do at the moment is hiding the other clips. Your problem with looped clips is a matter of design. In CbB you can roll a groove clip across a few bars and edit some bars without changing all the repetitions. That is very useful if you want to make variations. If you want to change all of them you need to do what you show in your animation, that BTW can be done faster if you hit CTL-L to unloop it and then again to loop it , and then roll it out again. Not a big deal for me, but of course to each their own. If you do not want to do that, you have other option, that is using linked clips. Linked clips will reflect any change that you make in one of them, and you do not need to have them one after the other, not even in the same track.

That is exactly what the Arranger Track is for. What is wrong with it?

I cannot reproduce that. Plugins stay open here until I close them, no matter what I do. Same with Pro Channel FX. Maybe you could describe step by step what you do, including your screens setup, if you open the Console View docked, floating in the same monitor, or in a second monitor.

What do you mean?

They do stay open here.

That is why CbB is great for sampling, just freeze and drag to the browser.

Personally what I find confusing is not seeing what is beyond the clip boundaries in the editor. I much prefer things as they are in CbB, where I do not need to create a midi container and all I have to do is to add notes to the track. Anyway, I get what you mean, maybe a "Show only selected clips" option could be added to the View menu in the PRV.

A screenset.

Sure. I had the VST preferences to show only VST3 if both are available. I had not found this problem until now.

Same version. I found that VST2 loads fine, and it seems to behave, but VST3 kills CbB here.

I installed Spitfire Audio BBC Orchestra Discovery yesterday, and it crashes or hangs CbB when I try to load it. It works fine in Ableton. Attached is the minidump. Untitled_01142021_130249.dmp

I have been playing around with this trying to reproduce your problem, but I can´t. I have tried with commercial Acid files from a Sony sample library and they import as they should, where they should, no matter what I do, either from the browser or Windows file Explorer. Same with .rex files.

Well, I have never seen that and I have been using Cakewalk since Pro Audio 9. Anyway, I am intrigued. I don't really use to drag loops from the Windows Explorer, but rather from Cakewalk's browser. I am away for the weekend now, so I cannot check that. Does it do the same if you drag from the browser?

That is what ACT is for,

How did you do that? Those markers on the timeline are not stretch markers, just regular timeline markers. I have never seen that dragging a loop to the arranger creates a marker, much less name it. No wonder that they do not move with the audio. Dragging either acidized or Rex files clips here does not do anything of the sort. BTW, they should import where you want them if you set your snap accordingly.

Do you have something, hardware OR software with a sequencer or arpeggiator that might be starting when you start the transport?

All the global buttons (Latch, Loop, Retrigger..) are midi learnable. Right click on them. Do notice also that in Cakewalk, "scenes" would be columns, not rows. Their header buttons are also learnable.