Feature req: Ability to rename MIDI CC in automation envelopes and PRV

[GreenLight]

When using many MIDI CC envelopes it can sometimes be difficult to tell them apart.

It would be nice if custom names could be assigned to MIDI CC envelopes, see suggested screenshot #2.

Thanks for a great product!

Edited March 28, 2021 by GreenLight
Better topic name

[Promidi]

This can be done globally. Under "Controller names", "Standard" in Define instruments and Names, you can customise the list as shown below.

It would be nice if this can be done per VST synth, however.

[Jim Fogle]

Per VST or effect would be much better.  Not all VSTs or effect use controllers in the same manner.  A good number of controllers are not assigned in the midi standard but are used in VSTs or effects.

[GreenLight]

On 6/10/2019 at 11:12 AM, Promidi said:

This can be done globally. Under "Controller names", "Standard" in Define instruments and Names, you can customise the list as shown below.

It would be nice if this can be done per VST synth, however.

Thanks for the great tip, Promidi!

I know there is a MIDI CC standard, but the parameters a MIDI CC controls are often unique per project anyway, at least for me. Any given parameter on any given VST synth could be MIDI learned to (almost) any MIDI CC number, so pre-defining global parameter names is not really feasible.

Assigning a name to an envelope would probably be most convenient when creating the envelope.

[GreenLight]

Any more takers for this?

This would really simplify working with MIDI CC's! Imagine being able to set a custom name for a MIDI CC, like so:

[GreenLight]

@Promidi Is it something like this you're after? ?

Remembering what CC52 or CC38 does can be hard... ?

[msmcleod]

@GreenLight - why not just rename your automation lane?

[GreenLight]

14 minutes ago, msmcleod said:

@GreenLight - why not just rename your automation lane?

Thanks for the tip @msmcleod that's something I had never realized/considered! ?

It would be awesome though to be able to rename the "mouseover name" of MIDI CC's, since I rarely expand the automation lanes... I usually edit them in the main track using the Edit Filter. And it would also take effect in the menu:

But still a great tip, thanks! ?

Edited March 28, 2021 by GreenLight
Added image

[Promidi]

Because I want to use the CC Controllers in the PRV. (I use the Transform a lot, for eg)

[GreenLight]

2 minutes ago, Promidi said:

Because I want to use the CC Controllers in the PRV. (I use the Transform a lot, for eg)

Exactly, I do that a lot too. ?

So custom MIDI CC names would have to be visible there as well.

[GreenLight]

Could you guys please consider this? ?

It would be so nice to be able to set custom names for the CC:s in the PRV below:

Keep up the great work! ❤️

[GreenLight]

This would still be awesome!

And I noticed a few similar requests have popped up recently:

 

 

[chris.r]

On 4/28/2022 at 7:35 PM, GreenLight said:

Could you guys please consider this? ?

It would be so nice to be able to set custom names for the CC:s in the PRV below:

Keep up the great work! ❤️

The whole controllers pane would benefit from a slight overhaul. It's got huge potential but it's still too clunky to work with at the current stage. For example when I'm doing a Hammond organ track, there will be often 20-30+ controllers working hard at the same time! I encounter some troubles in doing even basic things like selecting and moving quickly around small parts of different controller events separately (chunk of events of one controller, then another and so on). Something like time selection but for just a single controller lane is missing or if I'm missing it, please let me know. Also I still couldn't figure out how to simply and quickly select all events at once from just a single controller line, without fiddling heavily with the cursor which is nearly impossible especially if there's both data at zero and max in it, or reaching for 'select by filter' menus. Double clicking on the empty space in the corresponding controller lane would have been very handy or at least adding a context menu.

Another thing I noticed is that once the controller data amount in the project crosses some critical mass the cpu will start getting punished unreasonably high when doing the edits. I first noticed it years ago in Sonar Platinum and have changed PCs to more powerful since but the issue still exists just less noticeably.

If you would like to ask me why I'm still getting bothered with CC events instead of MIDI envelopes the answer is that I still don't trust them much enough as I think they still need more debugging. Oh not even mention how the transform tool, ctrl/shift modifiers and interpolation would be missing!  

Edited January 7, 2023 by chris.r