raspbian : master doesn't broadcast timecode when configured as a DHCP server

turingmachine / omxplayer-sync

OMXPlayer-Sync facilitates synchronization of multiple OMXPlayer instances over the network in a master/slave fashion.

194 stars 70 forks source link

raspbian : master doesn't broadcast timecode when configured as a DHCP server #73

Closed pagaille closed 5 years ago

pagaille commented 6 years ago

If those three conditions are met :

master role
DHCP server
autostarted through rc.local or systemd

then omxplayer-sync doesn't broadcast timecodes

I ended up configuring one pi as DHCP server (and slave) and another one as master (and DHCP client). Others are slave and DHCP client.

chiguire commented 5 years ago

I happen to have the same problem (reading from issue #71), except:

Statically configured network
Slave doesn't connect
Autostarted from lxsession

When I start a master and a slave (I only need two screens) manually, it works fine. If I start them from lxsession/.../autostart it won't work (only the master starts).