Closed pagaille closed 5 years ago
What version was installed on Stretch? Do I understand correctly, that you resolved the autostart issue by switching to Jessie? Sync did work with manual startup on sretch?
The version in numbers, e.g. 0.3.7.
omxplayer_0.3.7~git20170130~62fb580_armhf.deb
I opened a case on it's GitHub repo as well.
0.3.7 was the version on stretch? Well if it works when started manually it is most probably not an issue with omxplayer itself.
Maybe I should have opened two different issues. Indeed, the second issue is probably linked to some new rules regarding network access to autostarted app introduced in Stretch (?)
The .service file was the following :
[Unit]
Description=Synchronised omxPlayer service
After=network.target
[Service]
#master :
ExecStart=/home/pi/omxplayer-sync/omxplayer-sync -muv -b /home/pi/omxplayer-sync/video.mp4
WorkingDirectory=/home/pi/
StandardOutput=syslog
StandardError=syslog
SyslogIdentifier=omxplayer-sync
User=pi
[Install]
WantedBy=multi-user.target
I move the second issue to another thread.
Consider that Raspbian Jessie is not supported by Raspberry Pi 3 Model B+. There are ways to make it work on the Internet, but I couldn't make it work. I'm stuck with Stretch for this model.
Here is the description what you have to do to make Jessie work on RPi3 B+:
Two issues related to Raspbian Stretch :
At the time of writing, the latest omxplayer found on doesn't install itself on Raspbian Stretch because of an unmet dependency (libssl1.0.0). I didn't find an easy workaround.
Installing the default packaged version of omxplayer (apt-get install omxplayer) is possible and works, but there is an additional issue regarding network connectivity (and therefore synchronisation) when autostarted, wether through systemctl or by adding a line to /etc/rc.local. Looks like the master is not able to broadcast the timecode information, even while the network is up.
Just to save others time, I lost a bunch of it on this :-) --> Use Raspbian Jessie :-)
Anyway thanks for that nice work !