David Baay

The feature referenced by scook applies only to clip automation and fades. Cakewalk does not change the waveform display with changes to a track's Gain control. If that's what your talking about, I presume the videos you've seen are showing some other DAW.

Had not gotten around to actually listening to anything other than the click track. ;^)

Soloing by muting only audio outputs and not MIDI works better because the synths driven by those other MIDI tracks are still rendering audio so that when you unsolo the soloed track, the rest of the audio comes back in fully intact without dropped notes from note-ons or controllers that got 'muted'. MIDI event 'chasing' can address that to an extent, but not as well as just leaving the rendering process running, and muting the audio output. But nothing has changed with regard to these other 'odd' behaviors as far as I can tell. Muting a MIDI track still allows live-input to pass to the output though the MIDI meter doesn't show it.

I think my issue was due to Melodyne (Editor) having become deactivated since I last used it. I was subsequently able to get a tempo by dragging the clip, but only one average for the whole section. I then trimmed it, duplicated it a couple times, and bounced the three copies together, and got a more typical result with multiple chnages over several measures. But I still prefer Set Measure/Beat At Now for its precision, control and flexibility at the cost of a bit more time and effort. I have been wondering why you break up the clips and process sections separately. Though I don't like the way Melodyne places tempo changes in general, I've not found that it has any particular trouble with long clips with variable tempos.

If Kontakt is inserted in the FX bin of the audio track, try moving it to the Synth Rack. Using the FX bin to host a synth is a legacy configuration that is still supported for backward compatibility, but is not the preferred configuration and has been known to cause stuck notes. If that's not it, I dunno... When I first saw the post, I suspected Zero Controllers When Play Stops was not enabled to zero CC64 (Sustain) which is a pretty common issue with piano synths, I know you've already checked that, but it might still be worth pressing/releasing your sustain pedal to see if it stops the notes.

I have not used the drag-to-timeline feature for a while - certainly not since the new tempo track feature was introduced. I'm finding that it's not working in the current release at all with any audio file - no errors or hangs, but no tempo changes are generated. Possibly the last time you used it successfully was in an earlier release...?

The Melodyne component used to extract the tempo info may be having trouble with that - insufficient data - and the algorithm might be stuck in a loop if that condition wasn't anticipated. Or, similarly, Cakewalk may be having trouble with the limited set of data it's getting from Melodyne. I'll check out the bundle in a bit.

You might try Bounce to Clip(s) each of the split clips so you have a separate audio file for each instead of a slip-edited copy referencing the original file. It may be there is some issue with processing the slip-edited clips.

Check the Track Inspector for the Battery 4 track for sends.

The PRV shows some CC1 - Modulation event(s) have been entered/recorded. I'm not sure how SI Drums responds to CC1, but CC1=0 might be silencing the synth. If the Mod events weren't added intentionally, try deleting them.

Of course not, but it is in this case.

And make sure the To/By switch is on 'To'.

I have seen artifacts like this in the past, but your case may be a side-effect of the new waveform outlining feature. I've been noticing some added 'noise' in near-flatline audio that I think is related to this. You can try turning it off: View > Display > Show Waveform Outlines.

New projects will use the pan law set in the template from which they're created. It is possible to set a pan law with no project or template open, but that will only be the default if you start the new project using the 'No Tracks or Buses' (used to be called [Blank]) 'template'.

With Groove Clips, you don't set the tempo of the clip directly; you set the 'Beats in Clip' value, and Cakewalk calculates the original tempo based on the absolute length of the clip and that number of beats you specify. Cakewalk guesses the number of beats in the clip when you import it, but may get it wrong.

This is not correct. It's always been a quirk of Pan Law that it's not in the Project section of Preferences but it is, in fact, a per-project/template setting,

Hmmm... your screenshot shows Auto-echo enabled on the MIDI track labeled Vocal, and the output is TTS-1, but there's no forced output Channel set. It's not necessary to set this if you're changing output channels channels on your keyboard to play and record the parts for different instruments, but it's easier to just leave the keyboard set to a fixed output channel (usually 1), and use the track's output channel to determine which channel of TTS-1 responds to each track. If recorded MIDI is playing back on the track that has input echo enabled, real-time echoed MIDI should also be heard, so I'm not sure exactly what the problem is, but I recommend you set appropriate output channels on all tracks pointing to TTS-1. I would also recommend you set the Input on MIDI tracks to the specific port and channel of your keyboard rather than Omni - All. I wouldn't expect this to solve the immediate problem, but it's a best practice, and will prevent confusion later if and when you have other sources of MIDI coming in (from external hardware or MIDI-generating plugins).

To clarify this a bit, the fixed visual time reference in Cakewalk is the MBT scale, and the Now cursor travels faster or slower across the bars and beats according to the tempo. If audio is not deliberately enabled to follow tempo changes, the visual length of the clip will change such that it takes the same amount of time for the Now cursor to traverse the clip at the new tempo. The behavior is actually the opposite of what Mark said - audio clips shrink when the project tempo is lowered and stretch when it's raised.

Notwithstanding that MIDI-OX shows Note Offs being received, I suspect the combination of a generic MIDI-USB cable, generic Windows MIDI driver, and ancient (c. 1988) keyboard is resulting in malformatted/mis-timed MIDI messages that Cakewalk is not able to process properly. If the MIDI-USB cable has a dedicated driver available, you can try installing that. Otherwise, I would recommend upgrading to a 'real' MIDI interface, and or finding a newer used keyboard with built-in USB interface.

Ctrl+Alt+V to bring up the Paste Special dialog. Start time is part of the default dialog; click the Advanced button to see more options. You might also want to see the documentation on 'Use Paste Special Options on Paste' under Preferences > Editing to get the default behavior you prefer (i.e. whether changes to Paste Special options persist as the default for regular pasting or are applied only when using Paste Special).

Based on your last update, and that the issue seems Kontakt-specific, this probably isn't applicable, but FWIW: Time+ is a control in MIDI and Instrument tracks that allows you to offset the rendering of MIDI earlier or later by a specified number of ticks to tweak the timing. I have previously reported that Freeze will fail to process events at the beginning of a track that has a negative Time+ offset is in place. I haven't checked to see if it was ever fixed. The workaround is to destructively apply the offset by zeroing the Time+ control and sliding the MIDI earlier by the same amount before freezing.

Negative Time+ offset on the Instrument track?

Because your original post said "So why is cakewalk stretching the note instead of moving it leaving you ending up with broken information. "

That's precisely why Audiosnap uses stretching instead of 'moving' audio. Stretching lets you move the transient without creating overlaps. This is more important when you're working with audio that has pitched sounds sustaining across transients at a significant level. Drums, and rhythmic bass/guitar with short sustains are the only types of audio that really lend themselves well to the split-and-move approach. Stretching audio (especially by variable amounts from one transient to the next) is an imperfect science, and is dependent on the quality of transient detection which is also an imperfect science. I hear tell that some other DAWs do this better in general, but have never really heard side-by-side examples of the same audio stretched in the same way by someone with expertise in both DAWs to be able to judge. But I do know that results from Cakewalk can be pretty wildly variable depending on the nature of the material and how much work you put into massaging the transient markers and choosing the best algorithm for the material.

Good suggestions; this should move to the Feedback forum. One element of this existed in the old tempo list implementation; if you focused the tempo list by selecting a tempo, the Now time would go to that point, and the border around the selection would move down the list during playback. It would also follow navigation by keyboard shortcuts, but clicking anywhere outside the tempo list pane would change focus, and the border around the current tempo would be lost. So it was minimally useful, but I did notice this feature was lost in the new implementation.