I was surprised to see this and hence the question.
We were originally watching on the same server. But there was lag.
So I copied the file to the other server and launched the watch together from there.
The remote user didn’t change servers.
A new invite was sent, the remote user accepted.
The dashboards were showing each user on a different server.
Pausing the feed on my end paused it on their end.
If this is technically impossible, then it must be a problem with the dashboard.
Not sure what you mean by this. User’s don’t specifically pick servers. When they accept the invite, it automatically uses the server the invite came from.
I can bring it up with the team to check. This sounds more likely. It is technically impossible to use watch together with different servers.
Clients report their playback status up to the server, an independent step from streaming/downloading for playback. Reporting to the wrong server would be a weird bug, but seems more likely.
It would be interesting to look at the server’s bandwidth usage and logs during playback. It could be confirmed that way.
(Mostly commenting here to say: I’d really like a server-side dashboard of streaming/downloading/transcoding activity that didn’t rely on the client.)
I was viewing the activity. I saw bandwidth activity on both. The remote stream was SD and had low bandwidth, the local stream was 1080 so had high bandwidth. It looked in every way as if two users were on different servers both watching the movie.
I don’t understand how the Watch Together synchronization and message-passing works. Maybe all of the messaging was using one server, but the other client was (somehow) streaming from the second server. Maybe that wasn’t intended, but is an “accidental feature”.
Watch Together is controlled by the server, so it really isn’t possible to have 2 servers involved. It’s either a bug or maybe a user just hit play from that other server instead of using Watch Together.