This beta includes a complete rewrite of AbleNet which should make it more stable overall and fix issues with M4 Macs. While I tested this thoroughly in my setup, there might still be bugs, so please be careful if you’re using this in a production environment.
Replaced AbleNet with an improved version that uses TCP instead of UDP and should work reliably in more network scenarios
This should also fix scenarios where one host can see the other but not the other way around
Added an automatic switch to an alternative computer if AbleSet loses its connection to Live
Added a drift indicator to the AbleNet page that flashes for each beat and displays a bar to easily see how far apart the playhead is from the other hosts
Added a progress view to the “empty setlist” screen while project files are being parsed
Added the ability to toggle device-specific settings using OSC
e.g. /devices/setSetting all performance.showSectionProgress toggle
Added missing OSC commands to the autocomplete menu
Addressed multi-file parsing hanging in some cases
Reduced the amount of logs for noisy incoming OSC messages
Ableset 3 is a huge upgrade for how I use it vs Ableset 2.
I’m having a hard time getting the quick-play to work right. Normally, I can use the quick play sections to jump around in a song during live performance; I can pick a different section and it will auto jump once it finishes the section I’m in. Right now I can only use quick play when the song is not actively plating. Is this a setting that I am missing? I also have not figured out a way to use quick play in the new canvas mode yet. Everything else works great!
One other small wish: Can the next section update when I am jumping? If normally the song goes from chorus to bridge, but I select verse with quick play, can the next section say verse instead of continuing to say bridge? An update to the Guide tracks would compliment this nicely, something more dynamic where the guide track would also follow this. This is all to make Ableton more flexible during live playback.
For your second request about the next section showing the queued jump, I’m assuming you’re referring to the canvas, as performance view already displays this. In the canvas, you can use something like this:
Hey Leo! Not sure if I’m missing something or not cause I’m new to osc but it seems the label for previous song in the setlist
${osc(“/setlist/previousSongName”)}
doesn’t work in canvas.
I previously used the stream deck which has that label capability.
Hi, I have been trying out the latest beta and am loving the new features. Canvas is awesome.
I have a couple of questions pls…
The beta seems very slow in just about all things, noticeably slower than my 2.x version. Is this due to debug code in the beta? Will it improve when finally release?
How do I set the colour of a section in Canvas? I would like to set the Current Section Name text to a different color to the ‘Next Section Name’. When in edit mode I click on the blob of colour and get a long OSC command. No idea what to change or set it to.
Many thanks
Hey @GuitarMark, thank you for your kind words, I’m glad you like the new features!
Regarding your questions:
This is something I heard from others as well, but I haven’t been able to reproduce this on my end yet, unfortunately. Do you only notice this sluggishness on AbleSet’s own windows, or also when you open AbleSet in a browser?
If this happens in AbleSet’s own floating window, could you follow the steps in this post to send me a performance measurement so I can check what might be causing this issue?
The “Next Section” element template uses a dynamic expression to define the color of the label based on the color of the next section. If you’d like to use a static color instead, you can disable the “Dynamic” toggle above the expression which gives you a regular color picker instead.
I have also noticed AbleSet 3.0.0 being very laggy in my normal browser, Mozilla Firefox. It’s basically unusable, so I use Chrome for AbleSet. The stable version of AbleSet does not have these issues in Firefox.
Hmm, I am using Safari on lates version of MacOS. Maybe I will give Chrome a go as well to see if that improves it for me too. That might help Leo identify what is making it slow.
Hey @s1ah, thank you for reporting this! If you notice AbleSet being laggy in Firefox again, could you send me a screen recording along with a performance profile so I can take a closer look?
Here’s how to create one with the required information:
You can either download the file and upload it to my support inbox or upload it directly to the Firefox Profiler and DM me the link to it. I’ll check what might be causing this lagginess then.
Hey @GuitarMark, thank you for letting me know about this! If you notice this again, could you DM me a screen recording of how AbleSet behaves in Safari? I’m wondering if this has to do with the code that’s running inside the browser or if it’s more related to the communication with AbleSet.
Oh, @s1ah and @GuitarMark, could you also DM me a copy of the Ableton project file you’re experiencing these lags with? I wonder if it has anything to do with that
