Dear @musicullum !
Do you think it is doable to store “song end action(s)” to active setlist.
Example:
Willing to start NextSong right after songXYZ in setlist “A”,
while don’t want the same when performing setlist “B” just load next song after songXYZ and standby instead. Storing this setting with SETLIST, I could pre-program / pre-decide / pre-build perfect setlist running method.
Does this makes sense?
Felician
Hi Felician,
Do you mean that some of your songs are present in more than one setlist and you want them to have a different Song End Action?
Or would you like each Setlist to have its own Song End Action, automatically applied to all the Songs this Setlist contains?
Makes perfect sense in a show. Given a different song order you may want different songs to start next or stop for chat etc.
The setting belongs to the Song, and a setlist is just a list of Songs. It would have to store a special setting for all Songs in all Setlists…that’s quite a stretch for us, though we get your point. We’ll add it to the list.
Thank you for your reply 
Please feel no pressure, and would welcome this any time in the future.
Now we are a bit closer to the Future you mentioned in December 
@musicullum, no pressure at all! Just idea came to me yesterday and it accidentally is identical to @fkalmus idea. I swear, we haven’t talked about this 
Not quite sure…we could set a Song End action for all Songs of a selected setlist. But storing for each Song how to behave related to multiple setlists ist close to impossible.
Thank you @musicullum for checking and can understand. What if I reversing the hall thing (not now, not now!!)?:
As - at least in my thinking - song end actions get relevance with current SETLIST(playlist), can you agree with this logic?
So what if the SETLIST object stores the “song end actions” for the containing songs (as some additional parameter CommaSeparated after Song#ID) instead the of songs for themselves. Yes, I know, next problem is how to save it back from Playlist to loaded SETLIST… mybe in SyncModeOnly?
Also would increase the importance to see what is set/expected (mentioned before also):
will try that
Please make this an override rather than a replacement for the current method. Maybe the song setting could be used as the initial value when it is put into the set list.
don’t worry! that is just a discussion about for later-later time. Also you’re in my head to who won’t use SETLIST, rather waiting on “dynamic" / all songs listed” SETLIST item
Of course.
I wasn’t 
.
Song end actions by default should not be stored in song at all, because the transition to next song is related to the list of songs and/or setlist.
But when moving song in the song list or setlist, the song end action of course should be linked to its song.
At the end probably (of course) we will ask for additional feature - manage song end actions in the setlist - just clicking on icons to change them in cyclic way. As an alternative to the menu command.
That’s a good point. When trying to implement “Setlist related Song End Actions” we stumbled across this.
Problem is the existing implementation. We implemented change Song actions in Setlist editor for upcoming versions, but what about existing actions? We can bind those to the actual setlist, but then again we already hear the screaming “it’s gone when I import a Song!”
We would need to clear Song actions (that includes “Start at Marker”) when exporting a Song.
I would have thought the Song End action is moot when importing - you’ve no idea where it’s going to be placed in the list, better imho to clear it.
I would program so that there could be an option - Song Actions goes with the song wherever it goes and could be added to Setlist where Song is imported/added.
Hate options
agree, agree!
Exactly, as we here seems to be agree “song actions” are much more SETLIST dependent.
I know I created that topic and that needs lots of changes in the code, but I still truely belive this logic will be future proof. And this will provide a clean structure for each SETLIST.
The only case I don’t have any idea is for people (like @CliveJ ) not using any SETLIST keeping all songs listed in PLAYLIST 
@ArthurNeeman You agreed with me,
And I think VSTLive is not equal with Nutella (give happiness to everyone). Yes, at import somg’s actions need to be set, but that will avoid accidental wrong action. And yes, maybe someone will complain why it’s not imported, but again VL is not Nutella 
Let’s let genius developers find the perfect balance to keep VL simple but intuitive as they did so far 