Using “+CLICK” and “+G:CLICK” Together in AbleSet 3

Support
1

Before the latest version of AbleSet, I used the “+CLICK” flag to define tracks that belong to the click group (such as the metronome, count-in, loop guide, and guide), and so these tracks respond to certain MIDI and OSC messages.

With the introduction of track groups in AbleSet 3, I also added the “+G:CLICK” syntax so I can manage them from the mixer. However, I’m not sure if it’s correct or necessary to use both. For example, my guide track name now looks like this:

GUIDE +CLICK +G:CLICK

Is this the recommended approach for syntax, or should I only use “+G:CLICK” going forward?

Thanks!

2

Hey @agustinvolpe, that’s a good concern!

AbleSet treats +CLICK as an alias for +G:CLICK so the two behave exactly the same. You can use either one, depending on your preference :slight_smile:

1 Like
3

Hey Léo,

Thanks for your response!
If +CLICK is essentially an alias for +G:CLICK and they behave the same way, I was wondering if the same logic applied to other groups.

At first, I thought that instead of using +G:TRACKS, I could just use +TRACKS, but after testing it in AbleSet, it doesn’t seem to work that way.

So, +CLICK is just an alias for +G:CLICK, but +GUIDE and +LOOPGUIDE are not aliases for +G:GUIDE and +G:LOOPGUIDE, are they?
I understand that those flags are intended for playback solo/muting/looping purposes in AbleSet, because they don’t show up in the mixer, (at least as of this version).

The reason I structured the syntax the way I did was to ensure these tracks are correctly identified and all functions are available (in this case I needed to be able to both control my guide tracks’ volume -hence +G:CLICK -, and also having it be muted when a song is looping).
Could you clarify how these flags work in this case, or if this just applies to the +CLICK flag?
Maybe I’m getting some part of it wrong.

Sorry for being such a pain😅

Thanks again!

4

Hey @agustinvolpe,

You’re correct – only +CLICK is currently available as an alias for +G:CLICK for backwards-compatibility reasons.

I could also alias +GUIDE and +LOOPGUIDE to +G:GUIDE, but I had initially decided against it as I’m not sure everyone needs a Guide group in their mixer. What do you think?

Please let me know if you have any further questions :slight_smile:

5

Hey guys,

First time writing on the forum - I usually email @leolabs but I’ll give this a try today

I think my comment is kind of relevant to this thread :sweat_smile:

I’ve come across something and I’m not sure if I’m using the mixer incorrectly, I also haven’t given this a huge amount of thought so I could be overlooking the solution but

When I solo something - for example FOH-BV - for an impromptu acapella section, my guide tracks for both +LOOPGUIDE and +GUIDE both contain +NM and when I trigger the solo they are both live and I’m hearing the cue for both Loop and leave section at the same time

Am I using this incorrecting or is Ableset potentially missing a way of recognising when a loop is active and over-riding the +NM?

I’ve just had a thought as i’m writing this that an easy fix would be to just not have a cue for the looped section but I still don’t think that would resolve the potential issue for another project?

Cheers, Addy

6

Hey @Addy_Walters, the +NM flag has the highest priority in AbleSet so it makes sure these tracks are never muted, no matter which other flags are set. This is mainly meant to be used for Lifesine and other audio signals used for redundancy, but it can be made to work for your use case as well.

To use this for your use case, group your +GUIDE and +LOOPGUIDE tracks and only add the +NM flag to the group. This ensures that the group is never muted, but tracks within the group will still get muted dynamically.

I hope this helps! :slight_smile: