How to get track mute state back into Ableset

Support
1

Hello! I’m trying to create a button/label in Ableset that reflects the mute state of a track. The issue I’m running into is with the +GUIDE feature, which doesn’t always enable the expected tracks reliably. Because of this, I’d like to have a visual indicator that shows whether the track with +LOOPGUIDE or the one with +GUIDE is currently active.

2

Hey @Onassis,

Thanks for reporting this!
The +GUIDE and +LOOPGUIDE flags should definitely be muting and unmuting reliably — if that’s not happening, it sounds like something unexpected is going on.

To help investigate:

  • Could you share a short screen recording showing the behavior?
  • And a quick look at how your Live session is set up (track names, flag placement, etc.) would be really helpful too.
  • Also, what version of AbleSet are you running?

You can also see +GUIDE and +LOOPGUIDE in action in the official tutorial: https://youtu.be/0eNheFYAh6w?t=628

As for the visual indicator, you could add your guide and loop guide tracks to dedicated track groups using the +G flag. For example:

My Guide Track +GUIDE +G:guide
My Loop Guide Track +LOOPGUIDE +G:loopguide

Once they’re in a group, AbleSet’s Mixer will show their mute state natively, and you can also read it in a Canvas dynamic label with:

${osc("/mixer/guide/muted") ? "active" : "inactive"}

Let me know what you find, I’m looking forward to your reply!

1 Like
3

Hey @agustinvolpe!

Sorry for the late reply — I was out this week. It’s not a bug at all; it just doesn’t update when jumping while paused from a loop to a different section. I only do that during rehearsals anyway, so it’s not really an issue, I just wanted to have a visible reference.

The OSC you shared worked perfectly :raising_hands:
Thank you so much!

1 Like