Recently have become very interested in picking up a LioBox. I know a big selling point is the “hardware setilist management” capabilities. But what really stood out was the ease of navigation and very affirmative triggering feedback from the pads.
I was wondering if anyone else uses this in conjunction with Ableset? And if so, how well do they play together?
If memory serves me well, AbleSet gained support for Liobox’s cues since version 2.4. or 2.5.
It might be best to check the changelog though😅
I did see that! I was wondering more about “mergining” the best capabilities of both LioBox/Ableset.
Think I’m just going to have to take a chance on the LioBox and see how well they can be used in conjunction with each other.
How did the Liobox + Ableset combo work out in the end?
I’m considering the same…
Cheers!
Matt.
Same for me, any update ?
Hey all! I just reached out to Gooroo Controllers to ask if they’d be interested in making their controllers compatible with AbleSet and will keep you posted.
In the meantime, if there are any clashes between LIOBOX’s and AbleSet’s syntax, please let me know so I can take a look at it 
Would be perfect to use AbleSets MultiProject-Management in conjunction with LIOBOX.
can you add the support for the (stop) cue with ableset ?
Hey @YannP, I’ve just implemented this and will release it with the next beta version.
AbleSet will then automatically remove surrounding brackets from locators, so you can ignore any locator in LioBox while still having it available in AbleSet, e.g. (SONG END) or (> Chorus).
Does that sound good?
the (stop) is like your stop locator in ableset.
Can you like merge the job of those 2 type of locator ?
Does it have to be a lowercase (stop) or can it also be an all-caps (STOP) like in AbleSet? 
Only all cap for liobox
Hey @YannP, the latest beta now supports the (STOP) locator.
Let me know if it works for you