"LOCATE CONTROLLER ASSIGNMENT" function

[peedeebee]

Finding the assignments that have been made to a given controller has been one of the most time-consuming program editing tasks for me on the Kronos.

What if there was a feature that allowed you to 'jump' to the assignment of a controller.
For example, in program mode, moving the ribbon controller while holding the 'locate' button takes you to the place where the ribbon controller has been assigned. And if multiple assignments have been made to the controller, you could 'page thru' all of that controller's assignments by repeatedly moving the controller while holding the locate button.
My Kurzweil had a function like that and it was a huge timesaver.

[apex]

i agree. I initially suggested this on the m3. def needed. the roland fantom g has his functionality. and the yamaha motif actually has a page where it shows all of its controller destinations.

[jeebustrain]

yea - that's one thing I really like about my Alesis Fusion. there is a "mod" page that shows all routing (whether it be to things like LFOs or physical controllers) in one handy list. It's really easy to get a handle of all of the custom assignments (or change them).

[HardSync]

I really wish I had software coding skills. Because I think it would be possible to program an app to load up a PCG, select a program within it, and automatically scan for all AMS destinations, including effects and the control surfaces, and see what if anything is assigned to them. And then it could generate a diagram or list based on it all. Dealing with AMS Mixer routings would probably be the hardest part.

For any of you who can code and might want to do it, there are some useful AMS routing diagrams in the Parameter Guide starting on pg 1081, which would probably help in the determining how to write the software.

[ed_f]

I really wish I had software coding skills. Because I think it would be possible to program an app to load up a PCG, select a program within it, and automatically scan for all AMS destinations, including effects and the control surfaces, and see what if anything is assigned to them. And then it could generate a diagram or list based on it all. Dealing with AMS Mixer routings would probably be the hardest part.

For any of you who can code and might want to do it, there are some useful AMS routing diagrams in the Parameter Guide starting on pg 1081, which would probably help in the determining how to write the software.

Interesting you say this. I have implemented some basic functions like this in my PCGed program. There is a ton of information in a PCG file. I would be interested to hear more about what you think would be useful.

[jimknopf]

Finding the assignments that have been made to a given controller has been one of the most time-consuming program editing tasks for me on the Kronos.

What if there was a feature that allowed you to 'jump' to the assignment of a controller.
For example, in program mode, moving the ribbon controller while holding the 'locate' button takes you to the place where the ribbon controller has been assigned. And if multiple assignments have been made to the controller, you could 'page thru' all of that controller's assignments by repeatedly moving the controller while holding the locate button.
My Kurzweil had a function like that and it was a huge timesaver.

+ 1

And I already asekd a while ago, that we can simply deactivate any controller per patch, with a simple button click in the program/combi pages. It is extremely tedious and uneffective to hunt all possible controller assignments through various subpages of programs and combis.

I for one would decativate the ribon control in many or most patches, because it constantly comes in my way while using pitch bend/modulation, as soon as I touch it (which happens quite frequently with a ribbon placed directly below a pitch/modulation stick).