"PadMode" MIDI command to set default Modifier States

[Kaloyan]

Please consider enhancing the existing per-deck “Select Pad Mode” MIDI action to also set an Out Of The Box state in pre-built modifiers named e.g. “DeckPadMode1-4”**, so that we can use it as condition for building advanced multi-layer mappings.

This request relates to:

Expose the modifiers "condition" string in the MIDI mapping UI

I’m well aware of the “Modifiers” feature request, and that’d be super welcome, yet more complex and time consuming to implement. All I’m asking here, and as a separate request, is to have the XML “condition” string exposed and editable in the MIDI mapping UI. The functionality is there, and in the MIDI backend, we just can’t use it easily. I don’t want to have to edit the Controller Mapping XML every time I need to limit the scope of a button push in the context of the “Selected Deck” (modifie…

If done like this, it should be fairly straight-forward for implementation and backwards compatible with all existing mappings. We won’t need any UI for editing modifiers. The app will do it for us. We will then just work with the values in the mapping conditions.

Optionally, the existing “Select Deck” MIDI command in the “General” section can set state in modifier named e.g. “LeftDeckSelected=1/3”, “RightDeckSelected=2/4”, which is similar with how it’s done with modifere5-6 or the Rane Performer approach. But I suspect there will be other implications of using the existing “Deck Select” for this. Maybe a another, or new MIDI command for this would be more appropriate. Even without this, we may track Deck Selection with the PadModes “UserMode1-4”.

And the details of the request is here:

HOW TO work with Modifiers in the MIDI Mapping XML

Hello, While working on my Denon MC7000 monster controller mapping, I’ve defined a secondary/custom SHIFT+ key, and that suddenly opened up a VAST field of available buttons for extra control mappings. For many buttons, it was straight forward just press the custom SHIFT and the button, and voila - one more layer of control options is suddenly becoming available. In the case of MC7000, we have a pair of buttons on both sides that are for controlling the Views in Serato. I chose the L.PREP butt…

And specifically this post:

HOW TO work with Modifiers in the MIDI Mapping XML

Regardless if the XML editing is supported, or not, the functionality that we are asking for is here. It’s not about “more powerful”. It already is very powerful and completely sufficient. We just don’t have (or know) a way to set modifier states. But the application is very close to provide a complete Out Of the Box Support. Going over many mapping files, I see this: Most controller mappings use “modifier1-4” for the PadMode state of the 4 decks, but not all. Most controller mappings use “mo…

And it’s not about “Traktor Style modifiers”. It’s about “Djay Style Modifiers”

Cheers!

[Slak_Jaw]

Thanks for the suggestion @Kaloyan. Good ideas for sure. I appreciate the careful explanation as well. I’ve shared this along with your other post with the dev team. Thanks again!

[Kaloyan]

Thanks for facilitating this, @Slak_Jaw!

If these ideas are helpful to the team in any way, it’s worth the time spent for describing it all. The suggest approaches might be right, or not. Doesn’t matter much to me. I mostly hope that that these suggestions and perspectives will somehow assist the PM and engineering teams with the delivery of the much desired and requested mapping capabilities enhancement.

And from a certain point of view, I’m very happy to see how close the products is to deliver user-space modifiers functionality. All is pretty much in there already.

BTW, I also like how the View mode selector with the slider setting the numeric values work. It gives very good and robust usability, and seems perfectly applicable UI approach for selecting modifiers state values for both setting and filtering for state values, without exposing text fields for direct user input.