Mixer Groups and Canva Buttons

Support
1

Hi all, I’m having troubles with the Mixer Groups and making canvas button work.

First: I name my group “Collin” so I type in Ableton “Guitars +G:Collin” . But now the mixer only shows the letter C. This happens for all my groups. And groups with the same beginning letter get together in the same group, vor example Guitars and GoldKeys are now both in the group called just “G”. How do I avoid that? Is there a setting that I am not aware of?

Second, I tried to make a button on a canvas to toggle the groups mute.

So I set osc command /mixer/Collin/mute toggle

But nothing happens.. I tried sending a test message /notify/big all “test” 2000, and this worked. So I think my synthax maybe wrong?

Thanks for the help!

Please fill out these values to make it easier to troubleshoot:

  • OS and Version: Sequoia 15.5
  • Version of AbleSet: Beta 28
  • Version of Ableton Live: 12.3
2

Hey @FAster77,

For Mixer Groups, the group tag needs to be UPPERCASE in the Ableton track name so AbleSet reads it correctly as a full group name.

So instead of:

  • Guitars +G:Collin

Use:

  • Guitars +G:COLLIN

That should stop AbleSet from collapsing it to just “C”, and it will also prevent different groups starting with the same letter from being treated as the same group.

Your /notify/big test confirms OSC is reaching AbleSet. In this case, the issue is the group name casing on the OSC side.

For OSC control, the group name in the address is lowercase, so this is the one you want in the OSC Command on Press field:

/mixer/collin/mute toggle

Also, AbleSet exposes the group mute state as:

  • /mixer/[group name]/muted

So you can make the button reflect state with a dynamic background color like this:

${osc("/mixer/collin/muted") ? "green-900" : "green-500"}

On the button’s edit menu → Background Color → enable Dynamic → paste the expression above.

Here’s a the actual button you can import into your Canvases folder (inside any project folder you may be running) and test:

Collin.json (654 Bytes)

Hope that helps!

1 Like
3

Hey @agustinvolpe , thanks a lot!

That helped with both problems. And the option to have the color reflect the state is pretty neat.

1 Like
4

Hey!
I have made a button to mute a group (G:MEDLEY_LIVE) like the one discussed here, and the toggle mute functionality on press - /mixer/medley_live/mute toggle - is there, but I can’t for the life of me get the dynamic background color to work - I have toggled on Dynamic colour, and written the following code: ${osc(“/mixer/medley_live/muted”) ? “red-800” : “green-700”}

Is the underscore causing something, or did I miss something else?

Best regards

5

Hey @Thomas_Lyng_Poulsen,

The underscore and the OSC path are both fine, and the template is logically correct. The most likely culprit is smart quotes.

Make sure the quotes inside the Canvas field are straight quotes:

${osc("/mixer/medley_live/muted") ? "red-800" : "green-700"}

Try pasting that expression in your dynamic color field and let me know if that works on your end!

6

Hey Augustin, thanks for the suggestion! I copy-pasted your exact code to ensure straight quotes, but unfortunately, it still doesn’t work. Both Ableton and AbleSet are on the latest versions.

A few debugging details I’ve found - assisted by Gemini, because I am not much of a programmer myself:

  1. The OSC command /mixer/medley_live/mute toggle works perfectly and toggles the group in Ableton.

  2. However, when I try to just read the status using ${osc("/mixer/medley_live/muted")}, it returns null instead of a boolean or 1/0.

  3. The exact group name in Ableton is Medley Live +G:MEDLEY_LIVE (I’ve also tried lowercase).

Since it returns null, it seems like AbleSet isn’t actually storing/broadcasting the status for this specific custom mixer path, even though it accepts the command to toggle it. Any ideas?"

7

Hey @Thomas_Lyng_Poulsen,

Could you try a hyphen instead of an underscore?

${osc("/mixer/medley-live/muted") ? "red-800" : "green-700"}

Let me know if that does it!

8

I just ran into the same issue! If the group name is two words or more you need to use underscores instead of spaces in Ableton, when you are referencing that group name using Javascript, it will only recognize the name if it’s separated by hyphens like Agustin’s above example:

${osc(“/mixer/medley-live/muted”) ? “red-800” : “green-700”}

If you are trying to reference that group in an OSC message (not wrapped in Javascript) then it wants an underscore:

/mixer/medley_live/mute toggle

I don’t suppose there’s a longterm fix for that besides just having to format everything differently depending on the context?

9

Thank you for reporting this! I’ll fix this in the next beta, so both underscores and dashes work :slight_smile:

1 Like
10

Tried hyphenating, and it isn’t working on my end - but I had an epiphany, and just removed the divider - medleylive now works with the visual feedback I want.

11

Hey @Thomas_Lyng_Poulsen,

This has been addressed in the latest beta.
Give it a try and let me know how it works on your end.

I’m looking forward to your reply!