JoseC

You need to set Snap to the desired value. Then you´ll get perfectly cut notes.

Semantics are never trivial. Believe me, I should know, my GF is a foreign languages teacher

It is not that hard. An "Instrument Track" is actually a pair of tracks , one on top of the other. You can separate them and put them back together as you please with the right click menu. If I have an IT with midi data and I want to assign those data to a hardware midi output, I just split the track and route the midi to that port. The VSTi remains in the Synth rack until you decide what to do with it. If you then want to try another VSTi, you can also insert it in the Synth rack with no associated tracks and just rerout your midi and audio ins and outs to it. If you need another channel, just add it. Routing audio and midi in CbB is not any more difficult than in other DAWs. The only potentially confusing thing is understanding that an Instrument Track is actually a pair, not a single track.

Zero crossing is where the waveform crosses the Zero line. If you split audio at other places you get clicks. Unless you add a fade in.

Left, not right. @chuckebaby is saying the same as @User 905133 and I, hold and press DEL.

Actually, I tried the Press and Hold + Delete here, and it works fine. I am used to the Markers View, so I had not paid attention to that way, but as I said, it works. You need to have the cursor change to the Marker cursor. that appears when you move the Marker with the mouse, two little arrows with an "M". Keep the mouse button pressed and hit Del. Edit: I did not read to the bottom @User 905133 beat me to it.

Open the Markers View. Select your marker(s). Hit Delete, or the minus (-) icon. Done. It is very convenient to keep the MV open and floating somewhere (you do not need it streched too big), for Markers navigation. You also have the Markers module in the Control Bar, but I prefer the MV.

For those synths that don´t have front panel midi learn, a good workaround is creating knobs in the Synth Rack for the automatable parameters and adding remote control to those. CbB reloads the knobs whit the synth, but it would be great to be able to save different assignment presets, especially for programs like Reaktor, virtual modular synths, or others that can have completely different configurations, to map to controllers with limited number of knobs.

Funny when people take for granted that there is something "to fix" when they don´t get the results they expect. 🙄

Thank you for the tip, I used to use the old Geist, and I liked it, but it was too big and a little buggy. The new version is even bigger, too many things for a plugin and for an MPC kind of standalone workflow sorely needs a dedicated controller, but having a trimmed down Geist could be nice. 😀

I tried that. I downloaded a few loops directly fron Bandlab Assistant, and all of them came with a little silence at the beginning. You need to load them in a track first and trim them to make sure that they loop properly before loading them anywhere, if you want them to loop. In fact, I tried to load them in Ableton and they won´t even load. What you can drag and drop from Bandlab Assistant are .M4a files at around 100 kbps. Horrible quality, not worth the effort. The matrix is fine, I drag loops from my library , or of from Loopcloud and other quality sites all the time.

The Event List is the best view for investigating mystery midi.

Ok, I think I get what you want now. The only way that you can record two tracks without stopping the transport is arming both of them and using two separate midi controllers, each one assigned exclusively to each track, or a single midi controller that can change its output channel. I just did that without problems, using a keyboard for bass and a pad controller for drums, both to an external module. So, it is this, or briefly stopthe transport to disarm a track and arm the other. If you have two armed tracks and play the same controller, there is no way Cakewalk knows which one you want to record. For this, Input Echo is irrelevant, because that only determines what you hear. Even if you mute it, notes get recorded in both tracks. If it did not, it would be a problem for several musicians recording at the same time. And depending on the recording options, you might hear or not what you are loop recording. If you selected Comping, you would not hear what you recorded until you stop, but if you select Sound on Sound, like for recording drums one at the time, you hear all you recorded in previous passes.

There is no bug in something so basic, it is most probably a set up or a routing error. It looks like you have the Input Echo button in the track header set to On in both tracks instead of Auto. If you set it to On in both tracks, all of them sound as you play your controller. If you set it to Auto, you only hear the selected track. That would be why everything is fine when you stop playing and listen to what you recorded. Anyway, if this is not the cause, be more specific about how exactly you have your midi inputs and outputs set up, and how the Input Echo buttons are.

You can physically attach that to anything The only problem I see is that CbB will not slave IIRC, it will only be master. Or at least just midi, but no audio, which defeats the idea of triggering Cakewalk´s midi from the MPC if using VSTi is intended.

I don´t understand that, either. Can you describe more clearly what you are doing?

Works great here, provided you take into account the "Last Touched" parameter. If it is on, every time you set a new note duration by lengthening it, the "Note Draw Duration" automatically takes that value. If you want to select a previous value again you just need to click an existing note with that value. For me is faster than having to go to the top of the screen and having to click the Note Draw Duration buttons. With Last Touched off the selected value sticks perfectly here.

Funny that there is another thread where somebody seems to be incredibly annoyed by horizontal lines in the PRV.

1. Drag an audio clip from the Browser into a Matrix cell 2. Double Click in the cell opens Loop Construction View. 3. Do something to the clip in the Loop Construction View, like moving the pitch envelope. 4. Leave the LCV and play the cell in the Matrix Result: The cell does not play anymore, and you cannot retrieve the audio clip.

The main problem with the Matrix, IMO, is that most people expect it to be like Ableton Live´s Session View, find out that it is not, and just never open it again, instead of trying to find out what it actually is, and what it can be used for, which is more than it seems. Just a warning: there is a bug in the Matrix where if you double click an audio clip in the Matrix, it opens the Loop Construction editor, but as soon as you do anything to it within the editor, bad things happen, like if the Matrix cell did not recognize the clip anymore and it got lost in another dimension. You can double click a midi cell, though, and it will ask you if you want to create a Step Sequencer pattern. This works, though as I said above, you need to stop play if you want to hear changes.

But what you can do is use the Patch Browser for that. Right click in the midi track patch selection drop down menu and the Patch Browser appears. You can search your .ins file for the assigned instrument there, by text. If you do not have all presets with significant names, like EP, or Piano, just edit the .ins file and add a category prefix to the name, and search that. Like bas:Lowly or epi:PhaseyRhod, gpi:Steinway and so on. That way, if you search bas: you get all basses. Up and down arrows scroll the results AND select the patch too, so it is very convenient.

The first "bug" is just the way the Docker works. Melodyne opens docked by default. If you want to close it, close the Docker tab.

I was hoping that this update was bringing some improvement for the Matrix, but the Arranger Track is a nice surprise instead. Anyway, you can do more than it seems with the Matrix. You can drag and drop clips from tracks. You do not need to render clips, you can drag directly Instrument Track midi clips to the Matrix and they are automatically routed to their Track. With audio clips you do need to set up the loop, same as in any other program, but you can drag single shots as they are. And you can route the Matrix rows to any Console track, and use the effects there. In Ableton Live is exactly the same, you add FX in the track, not in the Session View slot. In fact, in Cakewalk you can even route several rows to the same track, something you can´t do in Live. You can create a Step Sequencer clip from a cell, and edit from there, but for some reason you need to stop the Matrix to hear the changes. Very annoying, but if you link the Matrix transport to the main transport you can manage somehow. BTW, a nice feature with the Step Sequencer is that you can experiment with the Step probability and sequence length and record the Matrix output to a track. You can leave it rolling and record multiple variations. Recording audio and midi directly would be great, but in the meantime it would be nice if they made possible to edit the Step sequencer without stopping.

You actually need to do it once if you use track templates. A track template in CbB includes all its routing. Just drag it from the browser and you are done.

Yes, I tested everything you suggested, with three synths, and the results are the same. I also tried lowering the buffer to 64 and it records only 10 ms early instead of 14 ms at 256, but it also cuts the first transient if recording starts on the beat. Just out of curiosity to see if midi input is affected, I was even testing with a groovebox synced to Cakewalk, recording its midi and audio outputs simultaneously. Same thing, no count in, at 256 samples both midi and audio line up within 1 or 2 ms, 10 ms after the beat, same results at 64 samples buffer. With a count in audio gets recorded 14ms ahead of the beat, against 10 ms at 64, and midi still 10 ms late in both cases. I am using a Tascam US2x2, latest drivers, ASIO, and a MOTU Midiexpress XT midi interface. I tried with three different synths with the same results. Timing offset is 0. Tried your suggestion of disabling that Config File parameter, but same results. Again, not much of an issue because a count in is not really needed, to record a midi track to audio, and if you want to line up everything you´ll need to slide the audio to compensate for the midi delay anyway.