Home › Forums › Products › Stompboxes › External Midi Control and the Control App
- This topic has 3 replies, 3 voices, and was last updated 1 year, 2 months ago by
cscotto.
-
AuthorPosts
-
-
September 25, 2023 at 6:46 am #174317
cscotto
ParticipantHi,
I have another question about using the H90 Control app with a midi controller, such as a Mastermind GT, which is what I am using. I have figured out how everything can be mapped, so I am good there. However, I have a question about the behavior of a mapped parameter to an external control.
For example, I have HS 1 (Hot Switch) mapped to a button on the controller. In H90 Control, I have mapped the mix parameter of a preset to HS1, so in the program the mix is set to 34 but the HS bumps the mix up to 60. When I press the midi controller button linked to the HS, the mix value moves up to 60. Great. I assumed however, that once I toggled the midi controller button linked to the HS that the value would return to the previous value, but it does not. The only way to get the value to return to the original 34 is reload the program. So, the question, are HSs really one way streets, you can change a value but not change it back?
This leads to a second question. Mapping a Quick Know (QK) to a midi button works fine, except it has a similar problem. If the midi controller button toggles between 0 and 127, then of course the mix value, for example, will toggle between off and all wet. The only way to have the QK work in a range is to set the midi controller to a range. That, however, make the button pretty useless for any other preset. Of course, I could map the QK to an expression pedal connected to the midi controller and have the range I want, but I would also like a way to do a simple change, like the HKs do.
Thanks
-
September 25, 2023 at 7:45 am #174318
fiddlercrabseasonParticipantre your quickknob mapping: If your controller does not allow you to bias the button min/max on a preset basis, your exp pedal idea (or knob on the controller?) might be your only path(s) to victory.
re your hotswitch mapping: Changing your source controller’s button behavior from “latching/toggle” to “momentary” should do the trick. But here again, if you can’t adjust your controller’s button behaviors on a preset basis…
-
September 25, 2023 at 8:18 am #174319
So, the question, are HSs really one way streets, you can change a value but not change it back?
They are not one way streets. What messages are you sending the HotSwitch? You only need to send a value of 127 on the same CC to toggle between states. Sending a value of zero will have no effect.
Mapping a Quick Know (QK) to a midi button works fine, except it has a similar problem. If the midi controller button toggles between 0 and 127, then of course the mix value, for example, will toggle between off and all wet. The only way to have the QK work in a range is to set the midi controller to a range. That, however, make the button pretty useless for any other preset. Of course, I could map the QK to an expression pedal connected to the midi controller and have the range I want, but I would also like a way to do a simple change, like the HKs do. Thanks
It is possible to customize these type of changes on a Program basis if, instead of mapping your controller to a Quick Knob, you map it to a specific parameter in the Parameters menu of the H90. There you can customize ranges differently for every Program. All you need to do is use the same CC# across Programs. Example: CC#15 always control “Mix” for Preset A.
-
September 25, 2023 at 8:38 pm #174340Participant
They are not one way streets. What messages are you sending the HotSwitch? You only need to send a value of 127 on the same CC to toggle between states. Sending a value of zero will have no effect.
OK, this information solved the first problem. I had the CC toggling between 127 and 0. Changing the 0 to 127 fixed the problem, so now the button presses toggle the values.
It is possible to customize these type of changes on a Program basis if, instead of mapping your controller to a Quick Knob, you map it to a specific parameter in the Parameters menu of the H90. There you can customize ranges differently for every Program. All you need to do is use the same CC# across Programs. Example: CC#15 always control “Mix” for Preset A.
I set up my mappings this way originally. The advantage I saw in mapping to QK was I could have the QK assigned to a different parameter in each preset. I will save the QK or expression pedal mappings. However, I see the advantage of what you are suggesting in that if I label the button “mix,” or example, then I can use it or the mix parameter in any preset. Just a note, unlike the HS mapping, I can set these switches to 0 and 127 and it jumps between the values I set on the parameter page.
Thanks or clearing up the first problem, and the suggestion or the second. Now I can pretty much control any parameter/setting on the H90 from my midi controller.
-
-
AuthorPosts
- You must be logged in to reply to this topic.
