AbleSet 2.6.0-beta.3

Happy new year! :tada:

  • Added a setting to show/hide AbleSet in the Dock on macOS
  • Added a simple clock module to the performance view
  • Added support for ruby characters in lyrics
  • Added support for markdown and newlines in lyrics with chords
  • Added the ability to jump to lines in pinned lyrics by clicking on them
  • Added a new OSC endpoint for jumping by a number of lyrics lines
    • /lyrics/jumpByLines [track-slug] [delta]
  • Added a notification system that can be triggered via OSC
    • Notifications are displayed in all connected browsers
    • Toasts: /notify/toast [title] ([description]) ([duration])
    • Full-screen: /notify/big [message] ([duration])
  • Applied fixes from AbleSet 2.5.7

You can download this beta here:
Mac (ARM):


Happy New Year @leolabs ! Thanks for all the hard work you’ve put into Ableset! I can’t imagine doing stage tracks without it. I wish you all the best and for Ableset to continue rocketing into the future!:rocket:


Just downloaded and tried Ableset 2.6.0-beta 3. My lyrics track showing chords is not displaying correctly. FYI.

Thank you for reporting this!

Could you send me a screenshot of what lyrics look like on your end along with the project file you’re experiencing those issues with on your end? I’ll try to reproduce the issue on my end and look for a fix then :slight_smile:

Chords2 +LYRICS [small] [-900ms] +CC [top+1]


The project file is pretty big. Lyrics show fine with beta 2 version with same file. I suspect it has something to do with the change in lyrics features. Here is the track text for the lyrics track and a screen shot of the chord display.

I don’t think it is a problem with my ableton file since it works ok with the previous version of Ableset.


Hey @HoosierFarmBoy,

If you like, you can upload the project file to my support inbox which doesn’t have any file size limits. Just the .als file should suffice for me to try to reproduce the issue on my end.

I’m fairly sure this has to do with the lyrics updates in this beta, but I haven’t been able to reproduce the same issue on my end yet, unfortunately.