apt

@Glenn Stanton @Terry Kelley Thank you for the advice! But, not only faders can do modulations. Actually I use a breath controller. Recording vibrato with a breath controller is a common thing. It gives much more humanity to the resulting sound. I think this "limit" is truly not necessary. It narrows the use of automation in the level of software. IMO, "Real-world faders cannot move that fast" shouldn't be the reason to do this limitation in a DAW. It would be better if this can be decided by the user.

@Noel Borthwick Here's a more obvious example. I recorded a vibroto that's not so deep, and the smoothing process completely ruined the vibrato.

Thanks for the reply! But usually it removes so many nodes that the recorded envelopes are not accurate, especially when you want to record "vibrato", or some complex, detailed modulation to the synth. I really think it would be better if we can choose to save or not to save CPU. And this feature is already added to the freehand envelope drawing. I use "manual" vibrato a lot and also make EDM in Cakewalk. This is an important feature and I really hope to see it in Cakewalk.

Could you please also add this feature to "automation recording" and "convert MIDI CC to envelopes"? Now the envelopes are always automatically smoothed a lot, and the smoothing cannot be turned off. I've mentioned the issues here: Thank you!

Oh, it works! Many thanks!!

When I record an automation envelope, what I actually draw is something like this: (this is what I see while recording) But when I stop recording, I get this. It seems that Cakewalk always does a lot of "trunc" to the recorded envelope. Usually what we want is like the first image. I have searched a lot but it seems that there is no solution for that yet. So my request is a switch (maybe) to turn off the "trunc" process and just leave the recorded envelope alone, or an option to change the "resolution" .

In Studio One, if Snap is on, you can still hold SHIFT and draw notes freely regardless of the Snap setting. This would not turn off the Snap. It just temporarily ignore the Snap while holding SHIFT. This can be very convenient while drawing or adjusting a lot of notes in PRV. Hoping to see this feature in Cakewalk!

In many sample libraries it requires a "negative delay" to the midi track (e.g. -100ms). For example, using Strings Staccato, there is an "attack" before the "rhythmic start point" of a note. If you simply set the sample start to that rhythmic start point, it would be unnatual. The only way to both keep the piano roll tidy and hear the notes in rhythm, is to apply a negative offset to the midi track. But it seems that the "time +" in Cakewalk's midi tracks is by "midi time" (ticks), not by ms. In most cases, it's okay to manually convert ms to ticks according to the tempo. But if I have severe tempo changes in the project, the absolute time offset would not be consistent. For example, this is a tempo change cueve which is common as a transition between two sections: If there's a midi track with time offset by ticks, and you do this, the notes that begin at the 8->120 jump would come out much earlier than expected. In Cubase and many other DAWs, you can apply an absolute time offset to midi tracks. Hoping to see this feature in Cakewalk.

It's true that this feature is somewhat not easy to implement... But what made me post this thread was that Cubase and many other DAWs can do this. Maybe I should make a feature request... As for why it is needed... For example, using Strings Staccato, there is an "attack" before the "rhythmic start point" of a note. If you simply set the sample start to that rhythmic start point, it would be unnatual. The only way to both keep the piano roll tidy and hear the notes in rhythm, is to apply a negative offset to the midi track. Anyway, thank you!

Thanks for the reply! Actually I firstly found this problem when I did tempo changes like this, which is common as a transition between two sections: If there's a midi track with time offset by ticks, and you do this, the notes that begin at the 8->120 jump would come out much earlier than expected.

In many sample libraries it requires a "negative delay" to the midi track (e.g. -100ms). But it seems that the "time +" in Cakewalk's midi tracks is by "midi time" (ticks), not by ms. I know it's okay to manually convert ms to ticks according to the tempo, but if I have tempo changes in the project, the absolute time offset would not be consistent. So, is there a way to delay midi tracks by absolute time in Cakewalk?

I've just tried, and there's no difference.

It is build 155

Thank you for the update! But I still have menu issues on multi-monitor system. I have 2 monitors, monitor 1 scaled at 200% and monitor 2 scaled at 100%. I put the main window on monitor 1, and the piano roll window on monitor 2, and then the menus in the main window still got wrong like this: