We have a long weekend here in NZ (starting tomorrow, my time), so will have some time to do more testing on my 3B+ and reconnect my RPi4 and test that as well.
Just need to get my wife away from in front of TV and out of the house for a couple hours!
I started my weekend a bit early and have run some more tests.
Let me start by saying @M1ck that unfortunately, you are not going mad.
My RPi 4 does exactly the same thing as yours when hitting play very soon after startup sound.
My RPi 3 did not do this, it wonât respond to the play button icon being mashed unmercilessly for 30 seconds after startup sound then pops a notification that âConfig has been updated, player restarted successfullyâ. Pushing play after this message plays normally and inter song info and timers work correctly.
For me this issue, whilst annoying (as itâs not behaving perfectly) is not a big deal as I leave my RPi on 24x7 and if/when I do restart, I usually create a new queue before listening so am unlikely to encounter it very often.
Lastly I can confirm that my GUI timer differences happen on both RPis with and without the statemachine.js editsâŚI obviously didnât notice this previously and is also not a big issue.
dmonds
OT
Not because of the rugby is it ? Be nice if they did that here 
.
.
.
I have just done a fresh install (3,546) on my RPi 3B+. It basically does exactly the same as my RPi4, maybe when it jumps is a little later if the same tracks are loaded up.
But if its true that yours is unresponsive for 30 seconds after the startup sound then that may explain why its not happening.
Are you running WiFi or ethernet to your Pi ?
Ethernet
Tested two albums with the first track shorter than the second (after restarting the system): I confirm that version 3.569 fixed the problem!
Its the other way around, the first track longer than the second the problem happened.
.
As Ive posed above if the difference in track length is quite large then the artwork changes to the next track very early and the seek bar jumps to the end.
Although this still happens with this latest release (3.569), I would consider it a serious improvement on what was happening before.
Its the other way around, the first track longer than the second the problem happened.
Right, youâre correct. I wrote the wrong thing, but I had that in mind. 
Okay, so the problem is not completely solved, but yes, itâs a good step forward.
Thanks to Volumio team and you for your efforts!
Now⌠It could be considered more of a characteristic quirk.
Just tested 3.569.
Exact same problem as 3.512 for me on RPi 4B.
Iâll check and re-apply the fix to statemachine.js and see what happens.
Initial testing of 3.601 suggests this problem is fixed.
@M1ck ⌠are you in a position to upgrade and retest on your system?
