That is why i keep most media as AVC/ACC mp4s. So to avoid transcoding. All video is 1080p or less. On a 1 Gb line.

Jellyfin on arch behind nginx. I connect with VPN, through NAT or on the local network. What else to say? I have noticed that syncplay is significantly more reliable through nginx. Not sure why that is. But it is still fragile. I’ve had this issue unresolved so long that I am just living with it. If it works, great. If it doesn’t, then i don’t use it.

Clients: firefox, jellyfin client, chrome, android client. The issue is pretty consistent across them all.

I mostly keep 8bit AVC/ACC, 2-channel mp4s. Some h265 as well. I have not noticed a pattern. Syncplay seem agnostic to encodings and filetypes.

I get the feeling that i am far from alone on this issue. There are threads out there.

Jellyfin ia great! But syncplay breaks if you snease.

Gonna require some more wise investments in open source and free software. Which require awareness from decision makers.

How well does jellyfin work on a rpi? How many simultaneous 1080p users with AVC\ACC media can it do? Active cooling?

As I understand it, the establishing of the connection is reliant on a relay server. So this would not work on a local network without a relay server and would, by default, try to reach a server on the internet to make connections.

rsync is indeed fiddly. Consider SFTP in your GUI of choice. I mount the folder I need in my file browser and grab the files I need. No terminal needed and I can put the folders as favorites in the side bar.

I think his school teachers, diagnosing him as retarded, were spot on.