brundlefly

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.

The screenshot from LatencyMon shows the root of the problem: "Highest reported DPC routine execution time... ndis.sys..." Disabling Wi-Fi in BIOS or possibly just "auto-discovery" in Windows as metallus suggested is likely to resolve this. Bluetooth drivers can be even more problematic, and should be disabled in BIOS if/when not in use.

I can't repro that. Copying frozen audio is the same as copying any audio; it just creates a new clip that references the same audio file. If the track configuration is the same (gain, interleave, panning, volume, output routing, sends, automation, etc.), it will sound identical to the frozen audio, and null with it when phase-inverted. If it sounds different, some track parameter is likely not matching.

This is a longstanding issue, not related to the OP's case since instruments and freezing are involved. Freezing a mono synth output adds 3dB regardless of pan law.. It has been that way for a long time, and has not been fixed despite being reported by many. Bouncing to tracks does not have the same effect, so either you want to freeze your instruments before you start mixing or leave them 'live' all the way through the bounce/export of the final mix. I think the OP's case is almost certainly related to particular FX that do not behave consistently from one playback to the next - i.e. they have some randomness built-in as scook suggested. That, or possibly there is some issue with the the way they interact with Cakewalk with regard to reporting and storing parameter values.

Or record to separate lanes of the same track.

+1 for Set Measure/Beat At Now. It's basically a non-graphical, keyboard-shortcut-based version of the drag-timeline-beats-with-mouse feature that you would like to have. Very precise and flexible, allowing you to make adjustments only where necessary at whatever level of detail you desire. Using keyboard shortcuts will speed the process, and avoid having to use the mouse at all unless Tab to Transient misses the mark: - Shift+M opens the Set Measure/Beat At Now dialog; you set one point for every execution. ( I have 'S' assigned because I use it so much). - Type the Measure number if necessary, Tab to the Beat and type that number if necessary, and Enter to OK. - Start by Setting the downbeat that should be 9:01 to establish an initial, average tempo; after that, SM/BAN should 'guess' pretty accurately which beat you're setting. - You can set beats in any order, and go back to set more as needed to get as tight as you want; enable the playback metronome to hear how it's going. - Do not delete or modify tempo changes that SM/BAN inserts; if you get something wrong, Ctrl-Z (Undo) as many times as necessary go back to where it was good. - Use PageUp/Down to move by measures and Tab to Transient (Shift+Tab to go backwards) to zero in on beats you want to set. (again, I have modified shortcuts so Ctrl is not needed for 'paging' by measures). - Use Spacebar to start/stop playback (a lot of people seem to use the transport buttons with their mouse which I find very slow and awkward) - Note that you can enter fractional beats (as decimals, not ticks) to set a transient that's not on a beat - e.g. beat 4.5 is the last eighth of a 4/4 measure. EDIT: Forgot to mention... since the project is multi-track, whichever clips(s) is/are selected is what Tab-to-Transient will use to set the Now time. Audiosnap does not have to be enabled for Tab-to-Transient to work.

Onboard audio and many soundcards do this when the Input/Source selected in the soundcard's mixer app is 'What You Hear' or 'Stereo Mix'; it needs to be 'Line' or 'Mic'. If your pedal has an included mixer/control panel app, check for that.

Try enabling Non-Destructive MIDI Editing in Preferences. Both enabled and disabled have their quirks; pick your poison.

I don't know about that. Playback is basically a matter of reading a file, but also subject to whatever clip properties are associated with that file. It seems likely the file itself was fine, but something about the clip properties was breaking/silencing playback. Cakewalk owns the creation, storage, and interpretation of its own clip properties so this could well be on the Bakers. To test this hypothesis, I would import the original audio file into a new project rather than copying the clip from one project to another. Unless you've 'cleaned' the project folder, that original file should still be there. Even if that still failed, it would be enlightening to know what it is about the file that's confusing Cakewalk. and might still lead to some kind of fix .

Only other thing I can think of is some automation weirdness. Is there any track or clip automation that might be getting copied over to the new track?

Doubt I posted about it. Just reported directly to the Bakers.

Wrong thread.

Sorry, but this is not consistent with telling people to read carefully which is insulting when delivered as an order with an exclamation point to someone who is clearly reading - and writing - more carefully than you are.

Not sure what you're getting at here. First, off, I never use Ctrl+Delete, and it did not work for me; I had to use the context menu. Redo is not available until I first Undo, so I did both, and both seemed to work fine...?

This is likely a big factor in this case - not enough reports to make it a priority. I had forgotten about it myself because I only stumbled on it the one time. It just sounded familiar enough that I looked back through my old bug reports to find it.