This is a fork of https://github.com/samcm/synclounge with improved stability and features like direct stream and direct play support. Some of the configuration is different than the main version, so that documentation may not always apply here.
I run an instance of this version at https://synclounge.ttshivers.com which you are free to use.
- Simplified room creation and joining process
- Better web player (same as what Plex web uses)
- Direct play and direct stream support
- Native subtitle support
- Skip next / previous controls to easily navigate episodes in a show
- Better high bitrate support with no more "appendBuffer" errors
- Skip intro / auto skip intro
- Auto Host (Anyone can start playing new content rather than just the host)
- Sound / desktop notifications for chat
- Major rewrite / cleanup of sync logic
SyncLounge (Previously PlexTogether) is a tool to sync Plex content across multiple players in multiple locations.
SyncLounge aims to keep multiple viewing sessions in sync regardless of whether the clients are in the same room or across the globe. To do this SyncLounge utilizes a middle-man server to communicate between each of the SyncLounge clients. Users choose their Plex client, decide on a SyncLounge Server and Room name and join up. Your friends/family can do the same. Whoever joins the room first will become the host.
The host has complete control over a room. Commands they send to their client will be sent through to other people in the room (Play, Pause, Seek etc). If the host starts playing something different, SyncLounge will search all of your available Plex Media Servers for an equiavalent copy, even if it is not from the same Plex Media Server as the Host.
- Syncing between Plex Clients over the Internet
- SyncLounge Player
- Plays content directly within SyncLounge.
- Built specifically for syncing.
- Settings to tune SyncLounge to your environment
- Client Polling Interval - Sets how frequently SyncLounge will poll the client for new information.
- Sync Flexability - Sets the acceptable distance away from the host in milliseconds.
- Sync method:
- Clean seek - Seeks straight to where the host is.
- Skip ahead - Seeks 10 seconds ahead, pauses and then resumes 10 seconds later.
- Plex Media Server blocking - allows you to restrict the servers SyncLounge searches for content.
- Autoplay content
- SyncLounge will automatically search all of your available Plex Media Servers for content that is similar to the Host.
- Plex Media Server Browsing - find, search and fling content to Plex Clients from within SyncLounge.
- Metadata fetching from Plex Media Server
- Chat to others in your room
- Password locked rooms
- Invite others via generated short link
- Movies and TV Shows (Music not supported)
Head to the website
Theoretically, all Plex Clients that implement the Plex Client Protocol will work. As some clients have this implemented slightly differently, compability with SyncLounge may vary. If you have access to one of the untested clients please let us know so we can update our list below.
Some low powered clients may be hard to achieve a perfect sync with (for example: Raspberry Pi clients).
- Plex Web Player (Chrome/Safari/Firefox)
- Plex Media Player
- Plex Home Theater
- OpenPHT
- Rasplex
- Roku
- Android
- Nvidia Shield
- iOS (iPhone & iPad)
- AppleTV
- Xbox One
- Xbox 360
- PS3
- PS4
This fork has diverged some from the main SyncLounge repository, so not all the documentation for it is applicable here.
By default, it listens on port 8088. All the paths are relative, so you can use a reverse proxy at any subdirectory or subdomain without any additional configuration to SyncLounge. In this version, the webapp and socket server are combined so you only need to proxy that one port if you are using a reverse proxy.
Using the Docker image is the easiest path because it works out of the box. You can get it running immediately by
docker pull ttshivers/synclounge
docker run -p 8088:8088 ttshivers/synclounge:latestYou can use environment variables to change any of the default configuration.
Make sure you have nodejs installed.
sudo npm install -g syncloungeThen you can run it:
synclounge
If you want to change any of the default configuration, you can either use environment variables with the same name, use command line arguments, or use a config file and run synclounge like synclounge --config_file /path/to/config.json
If you want to run SyncLounge behind Nginx, here is an example configuration
map $http_upgrade $connection_upgrade {
default upgrade;
'' '';
}
server {
listen 80;
listen [::]:80;
listen 443 ssl http2;
listen [::]:443 ssl http2;
# TODO: Replace this with your domain
server_name somesubdomain.yourserver.com;
# TODO: include your ssl certs and parms, etc
location / {
# TODO: Replace this with your container address or localhost
proxy_pass http://containeraddress:8088;
proxy_http_version 1.1;
proxy_socket_keepalive on;
proxy_redirect off;
proxy_set_header Host $host;
proxy_set_header X-Forwarded-Host $server_name;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Proto $scheme;
proxy_set_header X-Forwarded-Port $server_port;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection $connection_upgrade;
proxy_set_header Sec-WebSocket-Extensions $http_sec_websocket_extensions;
proxy_set_header Sec-WebSocket-Key $http_sec_websocket_key;
proxy_set_header Sec-WebSocket-Version $http_sec_websocket_version;
}
}
To make synclounge run at a subfolder, all you need to do is change your reverse proxy configuration.
map $http_upgrade $connection_upgrade {
default upgrade;
'' '';
}
server {
listen 80;
listen [::]:80;
listen 443 ssl http2;
listen [::]:443 ssl http2;
# TODO: Replace this with your domain
server_name somesubdomain.yourserver.com;
# TODO: include your ssl certs and parms, etc
# TODO: replace "somefolder" with your desired subfolder
location /somefolder/ {
# TODO: Replace this with your container address or localhost.
# Important: keep the trailing slash
proxy_pass http://containeraddress:8088/;
proxy_http_version 1.1;
proxy_socket_keepalive on;
proxy_redirect off;
proxy_set_header Host $host;
proxy_set_header X-Forwarded-Host $server_name;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Proto $scheme;
proxy_set_header X-Forwarded-Port $server_port;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection $connection_upgrade;
proxy_set_header Sec-WebSocket-Extensions $http_sec_websocket_extensions;
proxy_set_header Sec-WebSocket-Key $http_sec_websocket_key;
proxy_set_header Sec-WebSocket-Version $http_sec_websocket_version;
}
}
The FAQ, Self-Hosting, Development, Contributing, and other documentation has been move to docs.synclounge.tv! Head there for more information!
samcm - Developer
gcordalis - User Interface
Brandz - Design
TheGrimmChester - Developer/Tester
MagicalCodeMonkey - Developer/Tester
Starbix - Docker Support
kg6jay - Tester
Twitter: SyncLounge
SyncLounge is licensed under MIT License. See the LICENSE.txt file.
SyncLounge is in no way affiliated with Plex Inc.
Using Material Design libraries provided under CC-BY 4.0