Sorry if I sounded critical, not my intention...I've been watching the Falconchristmas activity and it's been nuts.
Just checked FalconChristmas forum: Yesterday I moved over the show to the Pi 2 Quad core....after testing last night (after hours) there appears to be very little delay: 100 - 150 ms. Unless you know what to look for, it's invisible!
Thanks to all!
Here's CaptianMurdoch's response to the delay issue:
I have a ToDo item to rework the MultiSync code to add a "open" step. Currently the master just tells the remotes to start playing and they do their best to start in sync. I want to add an "open" before the "start", so that everyone gets a chance to open the files first then the start message comes.
It sounds like your video files are taking a while to start up. Sometimes different encodings can make the files take longer to start. If your video files have long distances between keyframes and the encoding method requires both keyframes to properly decode the video frame in the middle then it can delay startup since omxplayer has to read in a larger amount of data and decode more frames before actually starting to play the video. You might try re-encoding one of your video files with a shorter distance between keyframes and also turn off 'B' frames if they are turned on.
Other possible solutions include making sure that the USB drives on the Remote are as fast as possible, using a quad-core Pi rather than a single-core Pi, making sure that there are no other channel outputs on the Pi that is running video, and removing any fseq files from the Pi running video. If your have the fseq files on the video player Pi, then it will also be reading in the fseq data which can cause USB bus contention and slow down video startup.[/b
