In addition we need to know how you start the m3u playlist since there is no input from a remote/keyboard visible. In case you start the playback with a special addon or an autoexec script, please, give us more details.
The provided logs do not contain any items which correpsondent to a remote control action like a key press with the original OSMC remote control. The Annex4 Kodi driver seems to be part of the Control4 Home Assistent universum. Most possible that it communcates via the interactive.adaptive add-on within kodi but I don’t know for sure.
The problems is that we see some kind of parallel tries to open media files instead of a serial execution of the playbacks means i.e. 3 tries to open a mediafile within the same second.
I don’t know what is the reason for this:
Perhaps it’s the restore of the 4k+ based mediacenter configuration which brings an incompatibility with this special kind of software stack. Restart from scratch with a manual reconfiguration of the VeroV would should whether this is the case.
Perhaps, the used annex4 kodi driver is a different software stack now than the one with the Vero 4k. How should we know this? Who responsible for this?
Perhaps the inputstream.adaptive addon is meanwhile different (if it is used at all with this special stack)? Here
a Vero4k+ with latest/greatest OSMC lists inputstream.adaptive v21.5.11
a Vero5 with latest/greatest OSMC lists inputstream.adaptive v21.5.17
a Vero5 with current dev staging lists inputstream.adaptive v21.5.18
Is it possible to remove this Control4/Annex4 stack from the puzzle by starting the the m3u playlist from the local file system of the Vero system with the origin OSMC remote control?
We tried the Vero V originally with the remote, a local source and no control4 connection and still had the same issue.
i am wondering if the back up file is corrupt/wrong firmware and a fresh start might be helpful
The end goal is to have the files playing back from a Synology NAS. there was a problem with the previous co. integrating the 4K, could it be a specific setting for playback or perhaps a missing add-on?