Various MIDI editing requests.

[Promidi]

I was wondering if some of the following could be added to MIDI editing.

· Mirror copy forward and backward (Yes, we can so a copy + Retrograde - but a single function would be elegant)
· Apply a time warp to notes and controllers (Yes, you can use the Transform tool, but this cannot be done on notes and controllers)
· Vertically flip controller events with the fulcrum at the halfway point between controller values
· Scale events with NOW being the anchor point. If Now outside the selection, use the central time as the anchor point.
· Scale events to the left with the anchor point being the last event selected (including note duration if present)
· Scale and shift controller events to occupy the duration of any selected notes.
· Convert linear ramps to curves with changing event times. (Transform tool modifies event times - can cause Events to bunch up)
· Shift selected controller Events so they start at the first selected note (if included in selection).

I have created Studioware Panels with embedded CAL scripts to do the above (and more).  However, as Studioware Panels with CAL scripts have been officially deprecated, a build in method of performing the above would be handy.

Edited January 14 by Promidi

[Amberwolf]

Can I put in a vote for all of the above, too?

I don't know any automatic ways of doing them, so I just do stuff like that the tedious manual way (which is often faster to completely redraw it manually ). 

 

[Promidi]

19 hours ago, Amberwolf said:

I don't know any automatic ways of doing them.

I have written CAL scripts for all of those functions I listed.

[Amberwolf]

I did see that in the OP of this thread, but guessed you probably already have them out there somewhere if you didn't post / link them here.

Are these the SW panels? 

https://www.promidi.com.au/studioware/studioware.html

(thought I'd try a google search on your username first, just in case the CALs were already out there; if they are here on the forum itself I missed finding them....) 

 

Edited Thursday at 02:59 AM by Amberwolf

[Promidi]

5 hours ago, Amberwolf said:

Are these the SW panels? 

They are indeed.

Some things to point out with many CAL scripts.

· For best results, bounce MIDI clips to one clip
· For many to work properly, set your clock to 960 PPQ (remember, this is a per project setting).
· Try not to delete events immediately after using many CAL scripts, Sonar can crash or give unpredictable results. (The panels have delete functions in them)

[Amberwolf]

16 hours ago, Promidi said:

Some things to point out with many CAL scripts.
· For best results, bounce MIDI clips to one clip
· For many to work properly, set your clock to 960 PPQ (remember, this is a per project setting).
· Try not to delete events immediately after using many CAL scripts, Sonar can crash or give unpredictable results. (The panels have delete functions in them)

Thanks!  I also saw those on the page itself; they are good cautions to observe.   

[sjoens]

19 hours ago, Promidi said:

· For many to work properly, set your clock to 960 PPQ (remember, this is a per project setting).

960 is default unless you change it.  Curious if this relates to the last post (David Baay?) on this page: http://forum.cakewalk.com/FindPost/3791895.

"SONAR/CbB always runs at 960PPQ internally. Even if you set it to something lower, it will record and play back with 960PPQ resolution and just display the rounded/quantized times."

Edited Friday at 04:06 AM by sjoens

[Promidi]

18 minutes ago, sjoens said:

960 is default unless you change it.  Curious if this relates to the last post (David Baay?) on this page: http://forum.cakewalk.com/FindPost/3791895.

"SONAR/CbB always runs at 960PPQ internally. Even if you set it to something lower, it will record and play back with 960PPQ resolution and just display the rounded/quantized times."

However, if you open an old project or a MIDI file, the clock will be changed to that of the opened file or MIDI file.

So, if you open an old project or a MIDI file and run any CAL script that includes the editing of any Event.Time parameters, you will get funky results.  The resultant events will end up not appearing where you expect them to end up.   I have learnt this the hard way many times.

[sjoens]

I took brundlefly's comment to mean the actual PPQ is unchanged, only how it's displayed is changed?  Unless files created outside Cakewalk are not affected by it's internal clock rendering when opened?