JoseC

I guess I was lucky, then. I got them all last weekend, with no problem whatsoever.

Funny how people say that some software is "unintuitive" implying that there is something wrong with it, and not considering that maybe what is not too sharp might be their own "intuition". 🙄

The Walking Thread! 😂😂

🙄

Maybe we are missunderstanding each other. You can bounce to any audio track you have, you do not need CbB to create a new track for you. My complaint is that it always suggests it by default, and that you need to change that every time:

You can actually do that if you first create the destination track where you want it and then select it every time you want to bounce the clip. The problem for me is that unlike the rest of the parameters of the dialog, this does not persist for the next time. Instead, creation of a new track is suggested by default, making you to unfold the dialog track list and choose the destination track you want every time. If it wasn´t for that, I could bounce clips with just two key presses.

I cannot seem to be able to get that behavior here. If I: 1. Select a midi clip in an Instrument Track. 2. Open the Bounce to Track Dialog In the Destination Track field I always get <#> New Track, no matter what track is current. I would like to be able to select a destination track within the dialog and make it persist every time I open it until I wish to change the destination track.

I meant the destination track.

About Bounce to Tracks dialog: would it be possible to make the chosen track to persist until changed? I often sample soft synth loops when browsing presets, make them groove clips and drag them to the browser. I use to set a track in the project for that purpose, and it is unconvenient that by default the Bounce to Tracks dialog suggests a new track.

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.

Yes. You are using it wrong. It is not designed to be used as VST, use it as ARA region FX instead.

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.