JoseC

The Walking Thread! ??

If you are using the VST3 version, try with VST2. I had problems with the Spitfire free BBC orchestra library where it would not load the VST3 version, but works fine with the VST2.

You can use the VCV rack bridge plugin. Insert it in as FX in an audio track with output to an Aux track, and record that. It is deprecated and is not included in the new VCV versions downloads, but it still works with them. You need to download the last VCV version that included it. I don´t remember now which it is, but it should not be too difficult to find out.

Yes! That was happening here and I almost went crazy until I found that the count-in was the culprit.

I saw that too. It was scary, for a moment I thought that Cakewalk was gone again, this time without warning.

Thanks, I´ll have a look.

That takes even longer, because then I need to unfreeze (thaw?) the track to keep on working on it. I just want an option for the track in the Bounce to Tracks dialog to persist, so I can sample things to it on the fly, without having a new track by default every time.

Sorry if this is obvious, but have you checked whether the "Out" of the keyboard goes to the "In" of the interface? I am assuming that we are talking about actual DIN midi cables. This is probably the number one reason why midi does not work in my system after changing something, no matter how I thought that I made sure that I plugged everything correctly.

Currently the Bounce to Track dialog defaults to "New Track". When I am sampling soft synths I want all bounced clips to go to the same track. Then I can drag them to the browser from there. I have a keyboard shortcut for Bounce to Tracks, but I have to select the track every time, because CbB always wants to create a new one. It would be nice to be able to choose between creating a new track, or setting an existing one as default. This way, bouncing a clip is a matter of two key clicks. I know that I could freeze the synth and drag the clip to the browser, but I find the Bounce to Tracks dialog options more flexible.

I have spare hardware out ports, so what I do is to set an unused port as output for those tracks. I think, but I am not sure, that this has been adressed somehow in a recent update. If not, my suggestion is that you create an extra loopMIDI port, label it accordingly an use it for that purpose.

Also check that the guitar link sample rate and bit depth match the project.

What @Johnsaid. Do not uninstall anything. Just check your ASIO buffers. You DO have an ASIO audio interface, don't you?

What sense would it make for every clip having its own name if all become the same as the Tracks's? Sorry, I don't get it.

Glad to hear that. I went crazy until I found out. In my case, It was recording the synth´s audio too early, cutting the first transient. This only happens when you are recording an external synth using an already recorded midi track. Since a count in, or even the metronome, is not needed for that, it is not much of a problem, but it is a sneaky one. I haven´t found any other situation where this matters.

Have you tried recording the audio without a metronome count in? It may sound crazy, but might make a difference. I was having sync problems while recording to audio external synths with the midi already recorded, until I found out that everything was fine if there was no count in. Of course it was not needed, but I had it enabled by default and somehow it was throwing things out of sync if on. Worth a try, I guess.

Did you check the output port in the Sysex View? I use Sysex since always and it works fine. If the setup file that you are sending is the same as always, it should work as always. The most obvious reason for it not to work is that you are sending it out of the wrong port. All that about "standards" makes no sense. Cakewalk just sends the sysex info, doesn´t care about its content. Patch/Bank change formats are a whole different kind of midi message that has nothing to do with sysex.

He is using a virtual MIDI cable

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

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?