AbleSet 3.0.0-beta.15

  • Added a Stop Description which can be displayed in the gap following a song that has auto stop
  • Added an option to always keep playing when jumping to queued songs
  • Added a /setlist/isInActiveSectionLoop OSC value
  • Added support for toggling the autoReEnableAutomationOnSongJump setting via OSC
  • Added a proper error message to the lyrics view in multi-file project mode when the current project file isn’t part of the multi-file project folder
  • Addressed Live displaying a warning dialog about audio stopping when jumping to the next song in multi-file projects
  • Fixed “cannot read property length of undefined” error in multi-file projects
  • Fixed loop indicator flashing sometimes when the playhead jumps to the beginning of the loop again
  • Fixed color and padding issues with sections in the setlist view
  • Fixed delays when sending OSC from multiple OSC tracks at once
  • Fixed delays when sending multiple OSC commands to external addresses

You can download this beta here:
Mac (Intel): https://ableset.app/download/mac/3.0.0-beta.15
Mac (Apple Silicon): https://ableset.app/download/mac-arm64/3.0.0-beta.15
Win: https://ableset.app/download/win/3.0.0-beta.15

5 Likes

How do we notate these descriptions?

For now, you can only enter these descriptions in the setlist editor, there’s no locator notation for it yet. Would you prefer to do it as part of the locator notation?

1 Like

Loving stop descriptions, great addition!

2 Likes

But locator notation would be a gladly welcomed option to work with! Thank you :slight_smile:

1 Like

I think the easiest way to implement this would be to allow writing the stop description into the STOP or SONG END locator, e.g. SONG END {Short Break, Tuning}. What do you think?

3 Likes

For things like notating a water break etc, I currently use song locaters so I can add colors and description (and I like having that formatting gap in between the songs). To do things like that directly in the editor is great to clean up my sessions - but I think I would do it in the session during the build, and then in the editor if there are changes/notes pre or mid show, which happens.

1 Like

Hello Leo,

thank you very much for beta15.

Please excuse my delayed response — I have been quite busy with Oktoberfest preparations.

The new canvases are fantastic!

However, I am still experiencing issues with RTF import:

  • If there are import issues, they are displayed.
  • If there are no issues, nothing happens within the setlist in Ableset.

I have recorded several screencasts to demonstrate these problems.

In addition, another issue has reappeared:
When a song automatically loads as the next item in the setlist and the bandleader changes to a different song, the structure of the auto-loaded song remains visible while the lyrics of the newly selected song are shown.

This can be quite confusing.

It usually works correctly for about 20 iterations, but then the issue occurs again. At this point I am unable to reproduce it consistently.

The problem has appeared on different MacBooks, routers, and iPads. Interestingly, Android devices always display the correct structure.

This might possibly be related to a refresh issue in Safari.

Would it be possible to add a global default behavior for what happens at the end of each song? Similar to the “Stop after each song” option in Setlist View. Ideally this wouldn’t replace the per-song setting, just allow setting a preferred default (e.g. “Stay at End”).

I think you would be able to find something like that in settings

1 Like

I checked settings but couldn’t find it, that’s why I suggested it :slightly_smiling_face:

1 Like

this is the setting section I think could help to set global default behavior for what happens at the end of each song

1 Like

@Michael_Sommerer that’s super strange, thank you for reporting these issues! Could you DM me the RTF files again, along with a log package, so I can check if I can reproduce this issue on my end?

@agustinvolpe there’s a setting called “Auto-Jump to the Next Song” on AbleSet’s settings page which controls this behavior. By default, this is disabled, but when you enable it, AbleSet will automatically jump to the next song upon reaching a STOP or SONG END locator :slight_smile:

Oh duh! Sorry for the confusion. My bad.

Stop descriptions are brilliant! Any chance there could be a toggle in there to display the length of the set between the current and previous stop descriptions?

So in an hour long set, the first stop description 10 minutes in would say -10:00, then another stop description 30 minutes in would say -20:00, and so on. I think that would be a great addition which also resolves a feature request: Set ‘Delimiters’ (Very much hoping for something like this because I literally had my calculator out at the last gig trying to work out how long we had left in the first set :joy: )