cross-posted from: https://poptalk.scrubbles.tech/post/2333639
I was just forwarded this someone in my household who watches our server. That's it folks. I've been a hold out for a long time, but this is honestly it.
They want me to pay to stream content that I bought from my hardware transcoded also on my hardware.
I'll say it. As of today, I say Plex is dead. Luckily I've been setting up Jellyfin, I guess it's time to make it production ready.
Edit: I have a Plex Pass. More comments saying “Just buy a plex pass” are seriously not getting it. I have a Plex Pass and my users are still getting this.
And for the thousandth person who wants to say the same things to me:
- YES I know I'm unaffected as a Plex Pass owner.
- My users were immediately angry at it, which made me angry. Our users don't understand what plex pass is, and they shouldn't have to, that's why I had it. The fact that they were pinged even though it should have kept working is horribly sloppy
- Plex is still removing functionality. I don't care that "People should pay their fair share". If Plex wants to put every new feature behind a paywall, that's completely okay. They are removing functionality.
- "But they have cloud costs". Remote streaming is negligible to them. It's a dynamic DNS service. Plex client logs in, asks where server is, plex cloud responds with the IP and port of where server is located. That's it.
- "Good luck finding another remote streaming" - Again, Plex just opens up an IP and port. Jellyfin also just opens up an IP and port (Hold on jellyfin folks I know, security, that's a separate conversation). All "remote streaming" is is their dynamic dns. Literal pennies to them. Know what actually is costing them money? Hosting all of that ad-supported "free" content that they're probably losing money on.
In short, I don't care how you justify it. Plex is doing something shitty. They're removing functionality that has been free for years. I'm not responding to any more of your comments repeating the same arguments over and over.

Jellyfin ia great! But syncplay breaks if you snease.
Remember to take your Claritin before starting a sync play session
Weird. Never had an issue with syncplay... What's your setup look like?
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.
Syncplay requires adequate hardware and network. Especially if you're trans coding at the same time. You're trans coding for 2 people at once, and depending on your setup sending to each person at different rates. It's hard to coordinate that.
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.