apt

I came up with a temporary solution, with the outdated CAL script, to zero the Time+ and Key+ of all tracks, so that I can export a clean midi file.

I'm posting it here for those who have the same problem.

(do
    (int nTrk)

    (= nTrk 0)
    (while (< nTrk 256)
        (do
            (TrackTime+ 0 nTrk)
            (TrackKey+ 0 nTrk)
            (++ nTrk)
        )
    )
)

10 hours ago, Promidi said:

Sounds like a good feature request.   (same with Key+)

You might want to consider posting this here:

https://discuss.cakewalk.com/forum/8-feedback-loop/

Okay. I have posted it for a feature request. Hope they can see it and consider adding this feature. 🙂

Actually it's me that requested for the absolute Time+ feature 2 years ago... I think this is vital for orchestral media composers, but it seems that there aren't many orchestral composers using Cakewalk (or Sonar) . So maybe they don't care much about this...

There's a new feature in 2024.11 allowing us to set Time+ with miliseconds, which makes this far more useful. We can use a negative Time+ to compasate the "latency" of sample libraries, which is more and more common in today's libraries. The Key+ is useful too. For example, some sample libraries move the piccolo an octave down. We can use Key+ to move it back to its actual pitch.

But unfortunately, Key+ and Time+ are not groupable by far. If we want to set the Time+ for multiple tracks, we will have to set them one by one. Same with Key+.

It would be great if we can have a feature to set the Time+ and Key+ of multiple tracks together (for example, making them quick groupable). Or just add a groupable switch to turn on/off them.

Many thanks.

43 minutes ago, msmcleod said:

Time+ has always been applied when exporting as MIDI - all we've done is allow you to specify in milliseconds as well as ticks.

MIDI Export / Save As is effectively a bounce operation, so the result is "what you hear".

Even if we offered an option to bypass the Time+, we'd get users that complain that they needed the delay on one track but not another.

By far the easiest way to get around this is to:

1. "Save As"  myproject-nodelay
2. Open that project and set all the Time+ to zero
3. Export your MIDI from that project.

 

Okay, I see. Thanks for your reply!

But could you please make it possible to set the Time+ of multiple tracks together, for example, make quick grouping (ctrl+click) available for this? For now I have to adjust them one by one...

We finally get the absolute time offset feature for midi tracks! That's really cool!

I use this feature to compensate the "latency" of each sample library. But if I export midi, the time offset would be "applied", causing a messy midi file:

   ---->   

So is there a way to export the midi file, but ignoring the time offset?

On 2/13/2024 at 12:51 AM, msmcleod said:

We've added a new feature to the new Sonar that will allow you to create Articulations that delay notes either positively or negatively ( +/- 1000 ) in either ms or ticks. You can also decide whether to include a note's end time in the delay, or retain its original end time.

Using articulations rather than a track-wide setting allows you much greater flexibility.   For example, orchestral strings with a slow attack playing legato could have a negative delay on the start time but when you switch to pizzicato, there is no delay.  You could even have different delay times for different octaves if required.

For simpler cases where you want everything on the track delayed, just draw the articulation over the whole track duration.

 

Thank you very much! We finally will get this feature in Cakewalk/Sonar! And I'm also excited for the great flexibility!

Could you please also consider adding a track-wide setting? That would be very useful for those who make orchestral templates. Many instruments just need a constant delay time. With track-wide delay setting, we can just add the delay in the templates and don't need to draw an articulation every time. (Drawing articulations in a template could make it messy)

Many thanks!

I'm glad that more and more people are requesting this.  And thank you Bakers for trying to make this feature available!

What makes me think it's possible is that many other DAWs, such as Cubase, Studio One, and even Reaper, have this feature, and they are all good to use.

I don't know how they implemented this feature. But maybe you can take them as references.

Many thanks.

12 hours ago, Esteban Villanova said:

In the meantime this free plugin can be used for negative delay: https://dmgaudio.com/products_trackcontrol.php

Thanks for sharing! That is a good temporary solution.

However, such third-party plugins all have a big problem in Cakewalk - they also delay the "input monitoring" signals of the tracks that don't have a nagative delay. This causes a very big latency when recording notes by the keyboard :( 

That "Live Input PDC override" option doesn't help. Because it also bypasses the PDC of the existing MIDI data on the recording track, causing that track playing ahead of other tracks...

So we still hope that Cakewalk can add this must-have feature ASAP. Studio One has just added this in their version 5.2 or so. Now almost every other DAW has this feature!

Please consider adding this! Many thanks!!

19 hours ago, Mark MoreThan-Shaw said:

I bounce all my orchestral libraries to audio when I'm nearing completion and eyeball the Waveform to get them in the best place.

You surely can fix all the latency and any other imperfections in the stage of mixing... But nowadays most DAWs have that feature, so many sample libraries now have a quite noticable latency, for several hundreds of milliseconds, in order to get more realistic sound. It is very annoying  to compose and program with that latency, isn't it?  

I'll second this request.

However, AFAIK many of them have been requested for many years in this forum, but it seems that the Bakers are not interested in them...

I'm glad that someone else also found it necessary...

I made this request last year, and I believe there were several requests for this in the old forums many years ago. But unfortunately there's no official reply yet

I'm an orchestral composer and have been using Sonar/CbB for over 10 years. Cakewalk has so many great features that can make my workflow efficient. But it's truly disappointing that this necessary feature has not been added into Cakewalk for so many years, while almost every other modern DAW has it...

I think many people don't know there is a feature like that, and how much it can speed up their workflow. Therefore not many people are requesting for it...

@Noel Borthwick @msmcleod Dear Bakers, could you please consider adding this necessary feature for orchestral composers? Thank you very much!

Could you please consider adding this feature to CbB?

I think this is a necessary feature in modern composing workflow, and many people including me rely on this so much... There's even a sticky thread in the VI-Control forum titled "Negative Track Delay Database / Spreadsheet"...

Many other DAWs, like Cubase and Studio One, can do this. I really hope to see this feature in CbB!

Many thanks!

I'm using 2021.09 build 145.

Every time I export the project as MP3, the bitrate is set to 256, no matter which I selected last time.

Is there a way to change this default setting, or let it remember the last bitrate I select?

Thanks!

This bug could be annoying while using Ripple Edit. But it was not fixed in the 2021.09 release. 

Anyone encountered the same issues? Is there anything wrong with my Cakewalk settings?

I'm glad that this was fixed for the drum grid pane  However, Alt+Scroll is still not working in the Velocity and CC pane.

Hoping to see this to be fixed soon. Thanks!

I set a time selection with a note's "tail" included.

If I delete this time selection with Ripple Edit on, the MIDI CC under the whole note would be deleted (not just the CC under the selected tail):

1 minute ago, Terry Kelley said:

Well, you've posted it in the feature request forum so let's see what the developers say about it. They seriously entertain useful features and improvements.

Thank you for discussing with me! I've been using Cakewalk for nearly 10 years. I've tried several other DAWs but Cakewalk just fit me best.  There are only a small number of things which I think could be better.  So I decided to post some FR's and bug reports hoping to help make Cakewalk better.

1 minute ago, Terry Kelley said:

At some point the faders need to be faders and not amplitude modulation at a fast rate. But you are certainly free to want them to act in a specific way. Noel's point about processing load is valid (in my opinion) and should be left to a plugin.

One of the reasons why I posted this thread is that, this feature is already avaliable to the free-hand tool while drawing envelopes. It's just been introduced in the 2021.6 update:

So I think processing load also shouldn't be a problem. Anyway, it's not a bad thing to let smoothing be an optional process and give more freedom to the user, isn't it?

@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. 

27 minutes ago, Noel Borthwick said:

This is completely normal behavior. What you see when drawing is just a preview of the mouse drawing nodes. The actual recorded automation removes redundancy nodes but the net effect will be the same with fewer redundant nodes because they are converted to curves.

There is no  reason to have extra nodes and they would use excess CPU.

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.

6 minutes ago, Heinz Hupfer said:

Hi?

There's a secondary Snap setting, when holding the "n " key. Set this to 1 tick and you can switch from your normal snap setting to "none" temporarily. 

Greetz?

Bassman. 

 

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.