Automate metronome activation

Hi Michael,

Apologies for the incomplete project. Here is a complete project.
Metronome bug.zip (218.3 KB)

  1. Change your metronome settings to have MIDI CC 102 as On/Off trigger (sadly this will stop the shortcut from working properly, but that’s a different bug):
  2. Open the Midi on track “MIDI Enable/Disable” and look at the events on CC 102.
  3. Run the flexloop on bar 2.1 and press L, you’ll see the metronome will not be disabled by the triggers on bar 3.1 or 3.2, but will be at 3.4.
  4. Disable Flexloop and enable cycle.
  5. Run the loop again, exiting by pressing L, you’ll get the same behavior.
  6. Run the loop again, but now exit by deactivating the cycle (button on transport). Now the metronome is correctly disabled at bar 3.1.

The same behavior is observed when automations are used to mute/unmute the metronome.

Hopefully this helps.

Cannot at all reproduce this. Keyboard shortcut continues to function as before.
Will check with your project later, thanks for that.

Yes, it helps. We have this on our list already and are working on it, tricky one.
But we can reproduce it.
But still my keyboard shortcut works fine for metro on/off. How do you get it to not to?

2 Likes

Glad to hear you can reproduce!

But still my keyboard shortcut works fine for metro on/off. How do you get it to not to?

I double-checked just now because I was suspecting the midi track from messing with this (keeping it turned on because of active midi), but this is not the case. I removed the midi track for testing. Here’s the behavior of the metronome shortcut (default C) for the different UI options:

Shortcut works as intended:

  • Toggle

Shortcut only turns on, but won’t turn it off:

  • On/Off

Shortcut doesn’t work at all for:

  • Button
  • Slider
  • Menu
  • Dial
  • Inside

Oh, of course, that makes sense. A keyboard shortcut should always be a “Toggle” because…well, it only provides one value: 1 (or “on”). For instance, if you select “On/Off”, it will only fire once (provided metro is off), after that, all next “on” are ignored, because it is already on.

Admittedly, this may be unexpected, and the keyboard shortcut should always behave like"Toggle" independent from the UI setting. Will check if we can improve.

1 Like