How can I export midi file without the time offset?

[apt]

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?

[msmcleod]

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.

 

[apt]

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

[Promidi]

8 hours ago, apt said:

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

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/

[apt]

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

[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)
        )
    )
)

 

[Promidi]

8 minutes ago, apt said:

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.

Yes, that would do it.

I was going to point out that you can set these track parameters parameters with a CAL script. 

The above would definitely set the key and time to zero of all MIDI tracks less than 256 to zero.

You would have to remember not to accidentally save the CWP file and exit with the zero offset intact - you would lose any offsets previously set.

Maybe do an undo after running this script (and saving the MIDI) before resuming with your project.

If you were to use a CAL script to set the time offset to a non zero value, the value would only be in ticks.  If you want milliseconds, you would still have to set the unit of time for each track one by one.

Still a good and useful work around though. 

I am so glad that Sonar still allows the loading and execution of CAL scripts (and Studioware Panels for that matter)