Toggle blink followed by long press

Morningstar Gear MC3/6/8 MIDI Controllers
1

Wondering if anyone can help with this.
For the life of me, I’m sure the logic works in theory but…

I have a simple toggle on/off, set to blink. Works fine on it’s own.
Positions 1 and 2 are on press to premit additional long press actions.

Part of the long press actions contain the same actions that are in position 2.

So what I think should happen is:
The ‘press’ happens first, so the toggle either blinks or stops blinking depending on the starting position.
Then the ‘long press’ happens, which include a) my position 2 actions and b) forcing the toggle state to engage.

So if I do a long press, the preset should always end up enaged (at least I think), but that’s not what happens. If it started off blinking, it ends up not doing and vice versa. The relevant actions all happen, just not the toggle state.
Driving me bonkers.

Anyone have any experience of this?
Thanks,
A

2

Can you share a screenshot of the editor for that preset?

3

Hi, a screenshot would be helpful.

Some hints beforehand:

  • If you combine press and long press actions in a preset, i’d advise you to use release actions instead of press actions to avoid misreadings
  • turn off toggle mode, use the ‘toggle preset’ message type with your press actions instead
  • use the ‘set toggle’ message type with your long press actions

I hope that helps

4

Thanks @james and @GuitarWolf for the hints.

1
11736×897 106 KB

Screenshot 2023-02-16 112634
Screenshot 2023-02-16 1126341496×795 56.9 KB

This is the logic in my head, and the order that I think things should happen in:

  1. Press: switches toggle
  2. Long Press: does various items to get everything into a known state (turns a load of HX stomp blocks to bypass, sets the HX block’s assocoiated MC6 toggles to the corresposnding state, bypasses a MIDI pedal, puts an ML5 into a specific preset). Also, this is where I switch the above toggle to engage, irrespective of the initial state coming out of the Press action).
  3. Release: nothing happens becasue nothing is on release.

So to me, becuse the last thing that happened is the long press, and the long press enages the preset, then I think it should blink, but it doesn’t. It’s always static no matter what the toggle state is coming out of the press. All the other actions (including the toggle states of other presets) all work as expected.

I think I understand the logic of that if it’s using a button that isn’t set to toggle. I did try release, otherwise using the same actions as per the screenshot, but I got the same unexpected behaviour as above.

  • turn off toggle mode, use the ‘toggle preset’ message type with your press actions instead

I’m not sure I’ve entirely thought this point though, but I feel like doing this would potentially allow my toggle to get out of sync, whereas the access to POS1 and POS2 always let you get bck to a known state that’s no more that one click away (I think!?).

  • use the ‘set toggle’ message type with your long press actions

Yep, doing that anyway.

5

If you turn ‘toggle mode’ on, any action will toggle the preset. A ‘set toggle’ + ‘engage’ will set the preset to pos2 and the long press action will toggle the preset after all messages have been executed. That’s why you end up in pos1. If you turn toggle mode off and programm a ‘toggle preset’ to your release actions you can avoid that the long press toggles the preset.

Just programm a message with:
‘Release’
‘Toggle Preset’
‘Pos both’

FYI: messages paired with a release action won’t be triggered after you performed a long press. There is another action type called ‘long press release’ that will do that.

1 Like
6

Thanks so much for the help, really apprecaited!
I’ll confess I don’t understand the logic still, but that does indeed work.