MIDI Editor / Controller Types

[JSmith1234567]

Someone in one of the recent posts said something about being able to switch between different controller data in the MIDI Editor window by hitting a number on the keyboard.

Can someone explain how to do this?

I'm not able to make it work.

I understand the "show only" toggle-switch, but not hitting a numeric #?

Thanks!

[dix]

It's a very cool, new DP9 feature only. Nothing like it in previous versions. In DP9 search "Edit volume (modulation, expression etc)" in key commands and/or "Edit next type". CC editing in the ME has been substantially revamped overall in DP9.

[bayswater]

Someone in one of the recent posts said something about being able to switch between different controller data in the MIDI Editor window by hitting a number on the keyboard.

Can someone explain how to do this?

I'm not able to make it work.

I understand the "show only" toggle-switch, but not hitting a numeric #?

Thanks!

Press the number keys at the top of the keyboard. It will change the controller that appears in the MIDI editor.

[JSmith1234567]

I tried that and it didn't work.

Is it in "commands" or something?

Thanks!

[dix]

Actually mine were set to Shift-Number Key by default. ...again, it's a DP9-only feature. In DP9 search "Edit volume (modulation, expression etc)" in key commands and/or "Edit next type"

[bayswater]

I tried that and it didn't work.

Is it in "commands" or something?

Thanks!

Yes, it's a default in commands. You might have old custom commands that overwrote it. Look up Custom in the commands window.

[JSmith1234567]

That has got to be it.

Thanks!

[wvandyck]

Looks like it correlates with the 7 assigned controllers in Preferences>Continuous Data.
The numbers 1-7 at the top of the keyboard select the first, second, etc assigned controller, rather than CC numbers. Hitting the 3 key will select my default assignment of Breath control CC#2, 4- Porta Time CC#5 etc.

Clicking the zero key lets you directly enter any CC number you want.

Very cool!

[dix]

For those like me who elected to not import the new default key bindings, you need to assign the controllers to key commands to access.

Here's the other improvements listed in the DP9 change log

• Added commands to insert as the seven custom controller values in Preferences > Continuous Data, or any controller via a dialog. The default key bindings are the row of number of keys.
• Added commands to change the insert type, add lanes, toggle the edit layer, toggle QuickFilter and more. These commands are also available in Edit > Continuous Data.
• Moved MIDI controllers out of the Controllers submenu into the top level in the MIDI Editor's Edit dropdown. The Edit dropdown also includes any other controllers present in the master track.
• Removed the filter menu in the MIDI Editor, Drum Editor and Notation Editor. Replaced it with checkboxes (and commands) that toggle showing only the active insert type or showing the selected data type (Quick Filter).
• Activating Quick Filter switches the active insert type to one of the shown controller types if the insert type isn't visible.

...i like how it now automatically switches to Points when you view velocities.

[johncmurphy]

I really wish this were better documented.
Especially the connection between the names of the CC controllers listed under Preferences...Editing...Continuous Data and the fact hitting numbers 1 through 7 on the keyboard will toggle the corresponding automation lane ON or OFF.
It's a real time saver - once you realize it's there.

[bayswater]

I really wish this were better documented.
Especially the connection between the names of the CC controllers listed under Preferences...Editing...Continuous Data and the fact hitting numbers 1 through 7 on the keyboard will toggle the corresponding automation lane ON or OFF.
It's a real time saver - once you realize it's there.

Possibly you're referring to the fact that there are key commands to do these things that are not documented anywhere. A common piece of advice to new users is to study the Commands window to see all the things that can be controlled this way. It also gives an overview of all the things DP can do that are not obvious from skimming the manual. The Commands window could be more thoroughly documented, but that manual would probably be bigger than the use guide, and its value would diminish as you customize the commands.

[mesayre]

A common piece of advice to new users is to study the Commands window to see all the things that can be controlled this way.

This would be substantially easier if there were a reverse lookup. I often find myself digging through the window because I want to perform some function, but have to work to figure out what it's called in DP's nomenclature. If I could hit a key and just have it jump to the right place in the list to tell me what that key combo does, that would be great. It' beat through the different sections, and would really help with learning the program since there is a logic to the way they've been mapped - even if that logic is not apparent to us all the time

[bayswater]

A common piece of advice to new users is to study the Commands window to see all the things that can be controlled this way.

This would be substantially easier if there were a reverse lookup. I often find myself digging through the window because I want to perform some function, but have to work to figure out what it's called in DP's nomenclature. If I could hit a key and just have it jump to the right place in the list to tell me what that key combo does, that would be great. It' beat through the different sections, and would really help with learning the program since there is a logic to the way they've been mapped - even if that logic is not apparent to us all the time

Can be done. Go to a command that has no key binding already assigned. Edit that to use the key combination you want to look up. DP will tell you it is already assigned, and tell you what it is assigned to.