+JUMP tag only jumps to next section, I would like it to jump to the next song
SInce I have a two bar Click loop on the end of every song, I would like to place +Jump markers before this section so it continues to play songs without those Click sections, but still be able to cue this section if needed.
If i do +JUMP [SONG NAME] it does jump, but pauses the playback even though autoplay is on. On SONG END it jumps and continues playback.
Hey @Ondrej_Pernica, welcome to the forum!
Currently, the +JUMP flag only works on STOP locators, but I get the idea of having some sections you don’t want to necessarily play in your song, but need to be able to jump to just in case.
My proposal for this would be to have a separate locator called something like ALTERNATIVES or SKIPPED which you can put before the end of a song. All sections that come after it and before the SONG END locator will be seen as being part of the song, but when the playhead hits the SKIPPED locator, AbleSet will jump to the next song in the setlist.
Alternatively, I could imagine extending the automated jumps feature to allow jumping to the next song at the end of a section, e.g.
Would one of these work for you? Which one would you prefer? 
so I’m trying to do a similar thing here. I want a click-only loop for each song at its tempo available at the end of each song, before the next one. Then I can launch those click loops if needed on the fly. BUT, I want to have the end of the song with tracks behave like normal, and have a SONG END cue at the end, so it auto-fires the next song in my setlist. (or if I want it to stop and cue up the next song I would make it +JUMP) - BUT I also want to have a +JUMP at the end of the click loop, so when I release the click loop, it jumps to the next song in the setlist, but also stops, so its cued up for me. Currently, I’m not able to make it do this. The +JUMP after the loop is released will always launch back to song 1 no matter what, because I have the SONG END cue before it. I tried the SKIPPED method, but that creates a new locator separate from the song, and also +JUMP at the end of the loop just stops, it doesn’t jump to the next song. I have to believe there is a way to accomplish this! I want to set it up as my template. Thanks for any help!
I also tried setting up each click loop as a separate song marker, and that seemed to work, except the SONG END cue will just launch that click loop, when I need it to SKIP that loop and launch the next actual song. so it looked like this:
so yeah is there any way to make the SONG END cue skip a song in the setlist? like SONG END+SKIP ?? can’t find anything like that.
EDIT: FWIW, I did try making the end of song cue SONG END [SONG 3] to skip to song 3, but it doesn’t work. still just fires the click loop (which is the next song in the setlist). Tried making that cue +JUMP [SONG 3] as well, and that doesn’t work either. I have to be missing something here!
Hi,
sorry for the long delay, I did miss the notification.
Thinking about it, I would prefer to have a new flag, +SKIP.
So in my case the one bar loop at the end of each song would be named CLICK +LOOP +SKIP
When the song is playing, this part would be skipped (therefore reaching song end). But it will be avaliable in Ableset to jump to with prev/next section buttons and to be toggeled via OSC etc.
In ableset playlist view this section should be also somehow marked so it is apparent it gets skipped. Thinking about an X on both sides (similar to how looped section is ).
What do you think about this?
Hey @SETHBUILDSRIGS and @Ondrej_Pernica,
I finished implementing this feature today and will publish it soon with the next Beta of AbleSet.
You can now use two variants to denote an area of sections at the end of a song that shouldn’t be played by default.
First, as outlined here, you can use a SKIPPED or ALTERNATIVES locator. When the playhead reaches this locator, AbleSet will jump to the next song or stop playback depending on your settings.
Alternatively, you can add the +END flag to any section clip or locator to tell AbleSet that the song ends at that point and all sections coming after that are skipped.
The behavior is the same, but I felt that both variants might be helpful depending on how you like to structure your projects.
This area is visually split using a bar in the color of the section that follows it:
The remaining duration of a song, and any progress bars only take into account the time until this marker and ignore any sections that follow it.
Does this sound good to you?
I’m looking forward to your reply!
Thanks for the implementation!
The +END will work for me.
I think that it would be better to use flags only, not having functions based on locator names, just to be consistent. So the SKIPPED or ALTERNATIVE is kinda outside of the “expected behavior of the ableset” for me.
Also I think that this feature would be a lot more usable if implemented as per my last comment.
No “two ways of doing it”.
Not only to skip the last section.
Just have +SKIP flag and then you can skip any section. You can put the flag either in a section clip name or on the locator, which way you prefer. And it stays consistent with other ableset features (LOOPing etc.)
What do you think about it?
Do not get me wrong, i feel like a king having the feature made exactly for my usecase 
But when I zoomed out of my usecase, I found out that it could be made better.
It’s a bit of a balancing question. If you’d like to skip sections, you can already do that using the >>> automatic jump syntax, so adding a new +SKIP flag would be a new syntax for basically the same thing.
I could expand the automatic jump syntax to allow skipping to the next song, e.g. with something like >>> NEXT SONG, so your section could look like > Outro >>> NEXT SONG instead of the +END flag.
However, I felt that having a separate SKIPPED locator that splits the sections off at the end of a song could be a cleaner approach in some projects.
What do you think?
Oh,
I forgot of the context of current jump syntax.
Thinking about it, jumping to next song was never the request.
It is jumping to the song end that I need.
So I have adjusted my proposals:
>>> SONG END
Add >>> ability to jump to SONG END
Automatic jump syntax is currently not working when you want to jump to the end of a song, it jumps only to a specific section.
+SKIP
I still think that adding a +SKIP flag would make my project easier to read and create.
It would function the same as >>>, without the need to specify which section goes next.
It is just easier to write +SKIP to the section you want to skip, than to 1. remember section to jump to, 2. find previous section to jump from, 3. write >>> “section”.
But both >>> and +SKIP would perform the same task, with different syntaxes (and usecases, when you want to jump to last chorus from first verse, >>> is definitely easier).
Those two changes will take care of my and @SETHBUILDSRIGS projects.
And for the usecase you seemed to mention, when you have an alternative sections at the end of the song, the >>> SONG END would work also.
What do you think about it?
And by this mental gymnastic I have found a temporary solution for our cases @SETHBUILDSRIGS .
Add a 1 bar section at the end of a song “SONG END”.
Current syntax >>> SONG END will work, skipping the click loop.
Would we be able to have an option to do this before a song as well?
Like the use case of having a click loop at the end of the song handy, I also have one at the start of the song and would love Ableset to be able to ignore that too.
Being able to add +SKIP to a section could be an easy way to do that… so no matter where in the song you are, if it’s got a +SKIP it’ll just ignore it and play the section after it.
