One of my AbleSet uses is in a function band that plays multiple sets throughout a night e.g. we’ll play from 9-10, take an hour’s break, then play 11-12. Or sometimes it’s 3 x 45 minute sets.
In order to organise the setlist, I create one-bar ‘songs’ that I use as breakpoints for the end of set one and the start of set two:
This works pretty well, except I don’t know how long each set within the list is. If I played three sets, I’d know 1) the entire duration of all the songs, and 2) the duration of the final set (because that’s just the final songs remaining). But I wouldn’t know set 1’s length or set 2’s length.
My suggestion would be to create something like a ‘+DELIMITER’ flag on the AbleSet locators:
What this would do is create an entry into the setlist which does not show a song length, but rather shows you the duration of all the songs until that point. If a setlist had two of these delimiters, the second delimiter would count the duration between that and the first.
Of course, the total length displayed at the bottom would still show the entire length of all songs on the setlist.
Delimiter might not be the best term for it, but I think this would be a good feature for bands running longer sets that need to signify sections within it, or account for breaks.
Hey @LewisDavie,
That’s a great idea! There’s another feature request that’s similar to yours: A Gig has several "Sets" -- assigning songs to "Sets" (within a Setlist)
I’m planning to implement a feature that allows you to add non-song items like delimiters or notes to the setlist, but this will take a while as I’ll have to rewrite the setlist data structure from scratch.
In the meantime, please let me know if you have any further suggestions! 
1 Like
I too use a similar “faux song” as a break-point. Regarding the name “+DELIMITER,” if the only reason/function for this “+” flag is to get a “subtotal” of time for all songs within each +DELIMITER, then maybe the flag +SUBSET or +SUBTOTAL is more accurate. Yet, essentially this functionality is describing a “Set” is being described here (ie, a performance may have three “Sets”…each with a “setlist” of songs). For a moment, to ponder the future, perhaps a +SUBSET flag would, in the future, not only tally minutes of the SUBSET, but facilitate a way to visually expand/collapse entire SUBSETS of songs.
1 Like
@nevillewhitemusic - I agree that ‘subset’ is a better term than ‘delimiter’! I added the “+” flag because that’s the syntax AbleSet uses on other features (“+LOOPFULL”, “+G:GUITARS”), but yes essentially it would be creating a subtotal of all the songs between one of these subset entries and the next.
Perhaps this functionality could be integrated directly into the web UI, eliminating the need to manually add a locator using a +whatever flag in live.
2 Likes
Yes, that actually is best. My LIVEset is not in Setlist sequence. This needs to be a web UI based feature. (oh good, we can use “+whatever” for some future feature)
1 Like
