FR - Midi Editor - Midi CC editing enhancements

[diverdee]

The ability to either/or:
A) select a midi cc range & move/cut/ copy it within the clip (so if e.g. one moves notes one can also than move any accompanying cc data to the relevant position).
B) Ability to select a particular point within the range of cc automation data & then move the automation forward (similar to how vst automation now works). Don't really know how viable this request is, but i'll put it forward anyway.
C) Similair to A) - ability to lock CC data to notes - so that when one is moved th eother follows, this would probably have to be an option.

Hope these FR's would be found useful by others.
They would definately be useful for anybody rewiring Reason to T2, if much automation of reason parameters is done from within T2.

[haydxn]

ooh, another idea.. how about a 'convert this CC data to automation' command? if you right click in the CC lane, it could then pop up the same menu that you get in the automation window to choose the automation destination. that'd be handy i reckon.

discuss these ideas!

[diverdee]

That's a good idea - but it seems like it could be quite a fundamental change - as (if u are still able to edit the automation data once converted) It is tantamount to using the vst automation system to automate midi cc data. Not that i'd complain - if that could be done (tying a vst automation line to a specific cc) it would make rewire automation very powerful. Only problem could possibly be if one has vst filters after the rewire filter that respond to specific cc's - there could possibly be conflicts then.

[IIRs]

ooh, another idea.. how about a 'convert this CC data to automation' command? if you right click in the CC lane, it could then pop up the same menu that you get in the automation window to choose the automation destination. that'd be handy i reckon.

discuss these ideas!

Personally, I would like to be able to draw MIDI controllers with the same tye of vector approach used in the automation, with options to insert controllers non-destructively at set intervals in time or value. (I think Logic can do something like this.)

Ideally, these psuedo automation curves would be compatible with normal automation to allow copy / pasting between the two.

The logical extension of this would be a function to convert recorded cc data into the new format with a line of best fit approach.. which brings us back to haydxn's suggestion.

[semiquaver]

good god, I just want to be able to edit the cc data in the first place ie. select a range of cc data and shift it, scale it, or reform it! Editing of controller data should be like editing of notes extending T's object orientedness anyhow...

[koolkeys]

I like these suggestions. My guess is that Jules has just begun on the MIDI editor. I would dare say that he probably has many things he would like to add. But only time will tell!

To me, MIDI already seems smoother and more accurate, so I'm already happy, as anything that I personally need to do can be done with ease now. I do hope it evolves though.

Koolkeys

[haydxn]

yeah, i found that the MIDI editor is remarkably more friendly to use although trying to edit the velocity of a note at the first tick of a clip is quite tricky

[koolkeys]

I think it would be useful to have an area that is blank that comes BEFORE the first tick. Doesn't Cubase or something like that have it? So when you zoomed in, the first tick wasn't all the way to the left, but rather because of the blank space, is pushed away from the edge a bit.

Koolkeys

[ambrosea]

I like the semiquaver's idea, the concept of shifting the same way the note are handled is what I'm looking for. It would also be nice if there were scale settings for given CC (which could be saved as presets) for plugins that have parameters whose range is smaller 128 (midi range) such as transpose option in some plugin only cover a range of upto 2 octave which equates to a range of 48 steps.

[ceenda]

I'd like the Line tool in the CC area to have a super fine option (the same as you get when you hold down Ctrl and use the draw tool). At the moment it only does ramps at the 'zoom snap' level, and that is next to useless.

[Madness]

jeez you guys must do a lot of midi editing...I just record my CC's with a knob, try it some time, it adds this strange element to the music, human almost!!!

[ceenda]

I just record my CC's with my knob, try it some time, it adds this strange element to the music...

But seriously. I often use Tracktion on my laptop, and don't have a MIDI controller or device to record CCs (especially CC1 for things like Garritan), so being able to draw ramps in MIDI data can be quite important.

[ceenda]

yeah, i found that the MIDI editor is remarkably more friendly to use although trying to edit the velocity of a note at the first tick of a clip is quite tricky

I really hope the Draw/Select/Line tools get full priority over IN/OUT/Play Markers/Clip Edges in a future update. This drives me mad like nothing else.

[Jerry W.]

I would like to see the ability to select a SPECIFIC CC and copy, delete, or paste ONLY that particular CC.

I would also like to customize the keyboard shortcuts for MIDI editing,. V is fine for Velocity, and N is fine for Notes, but I often use the Modwheel controller - a LOT.

a "humanize" option would be cool too. Or maybe that is in a filter or something?

My 2 cents worth.
Jerry Wickham

[jimsey]

Good stuff. I'd also love some MIDI CC automation, plus the ability to enter names for what is being automated (from the MIDI spec of the device)...!