Remote Playlist Start - Didn't

[Bshaver]

So, configuring a master playlist on FPP1, with remote start events of playlists on FPP2 (standalone mode).

I have a STOPRemote playlist event as the first event of the Master playlist as to reset the remote PI from doing anything.

Following that I have a RDS event that sends text to my RDS radio,

The third event I have a Remote Playlist Start event to Run a playlist that will repeat every 15 seconds sending messages to my BetaBrite sign.

It appears that the execution and the receiving of the messages at the Remote Pi caused the Message Playlist (3rd event on the master) to not execute.  The message was sent from the master, but it was received/processed out of order on the remote.

I put in a 2 second pause event between the 'remote stop' and the 'remote start' in the master and this seemed to fix it.

I have the remote PI just running a repeat playlist now sending message to my BetaBrite while most of the work is doing on the master.

I have also found that if you send a Remote Start Playlist, and then send another remote start playlist a few seconds later, the second just causes the remote to stop and not load the second requested playlist. .. Is it possible to have the playlist web service call eject the current playlist and start the new one? Or is it necessary to do the stop first, and then start?

Thanks
Ben

[CaptainMurdoch]

Are you using any synced sequences or video between the two systems?  If not then set then both to standalone player mode.  The php code could use some enhancements to check to see if a playlist is running before trying to start another one so we can stop the first then start the new one.

[Bshaver]

Ok. I'll do that. One is Master, and the other just stand alone. I can change both to stand alone.. I'll test it and report back.

Thanks
Ben

[CaptainMurdoch]

I was thinking you might have the second one in Remote mode which could possibly cause conflicts with events if you had the same ID's on both.  That shouldn't be an issue if your second is in standalone mode because it should only process event messages from the master if it is in Remote mode.

We do need to make the playlist state machine, commands, and error messages more robust, that is why you are seeing the odd behaviour when you send two starts.

[Bshaver]

I started the playlist, in standalone mode and witnessed the same behaviour on the remote PI also in stand alone mode.

I still have to stop the remote playlist, then wait a couple of seconds and then send the new playlist. I run the remote playlist in repeat = checked mode because it is handling my BetaBrite sign and I want the message to scroll every x seconds.

Thanks.

Ben