Autoplay is repeatedly set… AutoStarts are fired by manual selection, but not in PLAY mode (SongEnd, AutoStart)
When doing the same alternatively with “Next Song and PLAY” then it’s working okay… (but then no indicator for me, that song will be fired automatically :D)
Hi @Spork , might it happen that this one needs more time, right? 
Yes, there are many items on the list, some take more time.
Postponed this one several times, because I don’t understand the issue.
What does not work?
By…you, or VST Live?
What do you mean by that? Could you provide a repro? Thanks!
By me. Today needed to start my prog playing 4 songs (finally 5) w.o. stopping.
Set Autostart for the 4 songs visible on my screenshot. You can see the little “Autostart” icon for the songs.
But autostart “routine” is not runned after the first “Autostarted” song (that’s isn’t song dependent, but n+1 in my experience)
To repro just prepare more songs with Autostart active and let “the chain”run.
Does this makes sense?
P.S.: tricked today with “Next Song Start” actions but as Autostart has visible feedback (and next song start hasn’t) went first for “Autostart” …. But again workaround was to go with StartNextSong EndAction did the job for today
Autostart is not the same as Song End Action “Start next Song”.
It merely means that when a Song becomes selected, it will start transport. Selection occurs when clicking, or with a MIDI action (previous/next/by number), or when “Next Song” is issued.
But maybe I still don’t get it…?
I think you get it, but there is then a confusing in code:
1st AUTOSTART is working correctly as just simply as VL selects NextSong), but the “chain” is not continued afterwards (with following songs with ASt-Active)
I know there huge-amount to do, but can you just try with sandbox, 1bar (doesn matter) long songs?
Make
My experience is anywhere(!) I start: ManuallyStarted + 1 will work, but chain breaks afterwards
Does this explanation makes sense?
If any Song does not at least (Start) Next Song, there is no reason for the chain to continue.
Again, Autostart makes no difference with one exception: if “Next Song” is activated, Autostart should also start the Song, as if you had selected “Start Next Song” (instead of just “Next Song”). Apart from that, if no “Start Next Song” (or “Next Song” with Autostart) End action is set, there is no reason for VL to continue.
Exactly what set, but chain stops
Dear @musicullum ! I put together a sandbox project with v2.1.32 (MAC) and can’t repro, so at least I understand your confusion now. We both know how this should work and it works as we both belive it should work with a newly created sandbox project.
Let me try find out why it didn’t behave exactly like expected in my real-life situation. Will keep you updated!
F
Ohhh, you won’t belive me @musicullum !
If TRACKS view is opened on my 2nd monitor (you know the tiny one on my “duo laptop” and MIXER is the main-screen for LIVE), then Autostart can fail later or soon. If TRACK view is opened on main screen… everithing is as expected.
Do you have a second monitor maybe to proove my observation? this soundz me absurd. Updated to v2.1.32 and while it fails soon or later with it too, but the sandbox project fails only with 20% probability, while with LIVE project chain stops rather soon than later.
will check
yes
no.
Are you really sure you didn’t get confused? First time it was unusual but only because used to seeing the cursor. Tried many times w/o avail.
Also looked up the relevant code; the autostart flag is evaluated in exactly one place (which eventually starts transport), it is not at all connected to the track or any other view.
Thank you for testing! Surely not but will try to provide something to catch this fish at your side. Hold a “sec”, just got back to computer.
@musicullum let me know if this screen rec helped something. Configured Screenrec to see both my screens. First case TRACKS view is on the second screen. Hit PLAY… 1st SONG played, all following Autostart-enabled not. Pulled TRACKS view to main-screen, hit PLAY once, chain runs as you see. What do we missing? Exactly that happens with my LIVE project just didn’t wanted to waste time to “listen” the 1st song for minutes.
PS.: telling you a more interesting fact, doing the same test repeated, chain runs on sandbox project then. But 1. can’t repeat such thing LIVE, 2. on live project with “real tracks and real content” it fails either way.
Weird.
How exactly are your Songs configured? In particular, how is Song End Action set? You did describe it but not quite sure. Again, Autostart has nothing to do with this (except when End action is “Next Song”, then it will probably hit and make it a “Next Song and Play”).
So how exactly is Song End set for 1,2,3,4…?
Goto “NextSong@EndMarker (and wait) && AUTOSTART (2,3,4,5)
while… tested on Mac… there are more questions (why autostart isn’t initiated at all)
dropbox link
Created 4 Songs like that and could reproduce the problem, will be fixed with the next version. The “Next Song” action would locate transport w/o taking into account the Songs’ autostart state.
Why and how it was related to the 2nd monitor remains a mystery though.
Thanks for helping with this!
dear @musicullum ,
Autostart now initiated for all AS-enabled songs in serial, thank you
