The "<<" Prev Song button behaves differently in the SETLIST view, vs. the PERFORMANCE view

Sorry for the long (very very detailed) text. I am really trying to make my stage experience w/ my midi pedal so EASY. So below I outline, what may seem like a little user-interface thing, but it is “a thing” to me.

The BIG arrow buttons at the bottom of the Setlist and Performance screens << (jump to previous song) and >> (jump to next song} are terrific, yet maybe there are a few rough edges, or perhaps I need some help understanding certain Ableset Settings ( I have a subset of my settings at the bottom).

Below I outline a few scenarios, and identify how the “<< prev song” button behaves different sometimes, in the SETLIST screen vs Performance screen.

Basic behavior when transport is STOPPED…NOT MOVING::::::::::

**** When the transport is STOPPED and on beat 1 of any Song (beyond song ONE)**, then hitting “prev song” will go to the “prev song” (and not play) (this is true in both the SETLIST and PERFORMANCE screens)

**** If the transport is STOPPED anywhere AFTER beat 1 in Song ONE, then**
a. In the SETLIST screen, hitting “prev song” will go to beat 1 of the SAME CURRENT SAME song (not the previous song). A little odd.
b. But in the PERFORMANCE screen, the << “prev song” button renames itself to “Go to Song Start”. This is more accurate. So, perhaps in SETLIST screen the << prev song button could also rename itself (“Go to Song Start”).

A NOTE about when TRANSPORT is PLAYING: the “prev song” buttons (both in Setlist and Performance view) seem to be disabled when the transport is MOVING WHILE IN THE 1st measure. They seem to activate at the start of measure 2 (but I didn’t do more detailed testing).

Basic behavior when transport is MOVING, anywhere AFTER the 1st measure, and setting “jumpMode” = “end-of-section” :::::::::::

1. If the transport is moving in Song ONE, anywhere in Section 1 (after 1st measure),
a. In the SETLIST screen, hitting “prev song” will go to beat 1 of Song ONE, and KEEPING PLAYING (so, whereas if this << button is hit when the transport is stopped, then it goes to beat 1 and stops, but if transport is moving, it goes to beat 1 and PLAYS…That’s ok …and actually, I think this is Ableton behavior. (but maybe there is a setting to control this?)
b. In the PERFORMANCE screen, after the 1st measure, the << button renames itself to “Restart Song”. And does exactly that. Stays on Song ONE, goes to Beat 1, and PLAYS.
c. So when on Song ONE, in Section 1, both these buttons do the same thing, but maybe the Setlist button could rename itself…like the Performance screen button.

2. Now a key difference when in Song TWO (or higher). If the transport is moving in any song other than Song one, BUT STILL IN Section 1 (and after the 1st measure):
a. In the SETLIST screen, hitting “prev song” DOES go to the “prev song”. Yay.
b. BUT, In the PERFORMANCE screen, the << “prev song” button after measure 1 (but still in SECTION 1) renames itself to “Restart Song”. And does exactly that.
c. So this button, depending on the screen view, behave DIFFERENTLY in Section 1, after measure 1! Perhaps this needs to be addressed.

3. If the transport is moving in Song 2+, anywhere BEYOND Section 1:
a. In the SETLIST screen, hitting “prev song” will NOT go to the “prev song”, instead it goes to Beat 1 of the SAME currently playing song, and PLAYS. Hmmm.
b. In the PERFORMANCE screen, the << “prev song” button renames itself to “Restart Song”. And does exactly that.
c. So this button, on both screen views, behave the SAME (even tho the Setlist view still calls this button “previous song”, it does not do that.) Perhaps the setlist button could also rename itself “Restart Song”.

Summary: There are a few rough edges. My preference would be:
(1) a button called “prev song” would always, aways, after a single touch, go to the “prev song”, regardless of where the transport is.
(2) a button called “Go to Song Start” would always go to beat 1 of the current song, regardless of where the transport is.

(btw, all this testing was in the App, not the M4L plugin).

Well, that’s all. Thanks for investing 100 hrs into reading this (too long) entry Leo.

{
“autoplay”: false,
“autoJumpToNextSong”: true,
“removePlayedSongs”: false,
“safeMode”: false,
“autoLoopCurrentSection”: true,
“alwaysStopOnSongEnd”: false,
“jumpMode”: “end-of-section”,
“syncPlayheadPosition”: false,
“showStopButton”: false,
}

Hey @nevillewhitemusic,

Thank you for your detailed explanation!

I just released a new beta that both fixes the behavior of the previous song button on the setlist page and adds a new option that allows you to always skip to the previous song instead of first jumping to the beginning of the first song.

You can find it here: AbleSet 2.8.0-beta.11

Let me know if this works for you! I’m looking forward to your feedback :slight_smile: