Jellyfin Forum
SyncPlay - Printable Version

+- Jellyfin Forum (https://forum.jellyfin.org)
+-- Forum: Support (https://forum.jellyfin.org/f-support)
+--- Forum: Troubleshooting (https://forum.jellyfin.org/f-troubleshooting)
+--- Thread: SyncPlay (/t-syncplay)

Pages: 1 2


RE: SyncPlay - douglasparker - 2024-04-18

(2024-04-18, 08:13 AM)niels Wrote: The unfortunate part is that we want to fix it but most of the server team members don't have the time to invest in it or don't care about the feature (which is fine). I'd love to fix all the SyncPlay issues myself but I also don't have that time (I'm primarily the maintainer for the Android apps, all other stuff I do are "extras").

I completely understand.

If there is any way I can help with extensive debugging, please let me know- ideally when someone has free time to actively work on it that way both of our time is respected.

If there is a way to fund development in this area, also let me know. I am certain there are many users that would be willing to make significant financial contributions to get SyncPlay working well for everyone.

I am really interested in what is different between people that have it working very well vs those who experience horrible bugs with SyncPlay. I feel like being able to determine what that is will really help with finding a solution.

I've personally tried with very very high end machines for the Jellyfin host, so I am personally at a loss.
I'm talking 32 dedicated threads and up to 192 GB of RAM, with very large PCIE 4.0 NVMe SSDs.

At first I was wondering if it was a difference in web server that reverse proxies to Jellyfin, but if I recall correctly I had issues with SyncPlay when using IP:PORT directly as well.


RE: SyncPlay - niels - 2024-04-18

Personally I think the way to improve SyncPlay is to:

1. Document how it currently works, including the HTTP API, WebSocket API and implementation details
2. Map all known issues to this architecture (simply said; find out what part of the code causes the issue)
3. Figure out what changes we need to make, which most likely means to redesign large parts of SyncPlay
4. Write a jellyfin-meta issue with a proper proposal and design suggestions
5. Implement said changes

This would require at least 1 dedicated developer that is willing to dive into the Jellyfin server code, and team members approving of the proposal starting from the 4th step.