Where to Get Help or Report a Bug with Syncplay

Updated

Start with the Support section and the client troubleshooting/FAQ on syncplay.pl, since most setup and playback problems are already covered there. If the issue is a genuine bug, report it at https://github.com/Syncplay/syncplay/issues, or email [email protected]. Before filing anything, confirm you are on the current release (1.7.6) and can reproduce the problem.

Check the documentation first

Syncplay's site organizes help by task, so match your problem to the right page before searching elsewhere:

Problem type Where to look
Installing on Windows, Linux, macOS Installation page (includes notes on packages and tarballs)
Client won't connect, sync drifts, UI misbehaves Client troubleshooting/FAQ
Setting up your own room server Running a server page
Understanding how syncing works The Syncplay Protocol page

The FAQ is the fastest route for common client issues. For example, if Syncplay does not load on Windows, the site notes you likely need the Microsoft Visual C++ 2015-2022 Redistributable Package (the 32-bit vc_redist.x86.exe), and that the command-line version SyncplayConsole.exe is an alternative.

Report a bug on GitHub

The GitHub issues page is the primary bug tracker. A report that gets acted on usually includes:

  • Version: state that you are running 1.7.6 (the current release).
  • Platform: Windows, Linux, *BSD, or macOS, plus the exact OS version.
  • Player: which supported player you paired with Syncplay — mpv, mpv.net, MPC-BE, MPC-HC, VLC 3, IINA, or memento. mpv (or mpv.net on Windows) is recommended for best compatibility, so mention if you are using something else.
  • Steps to reproduce: what you did, what you expected, and what happened.
  • Logs or screenshots: especially for UI problems.

One known trap worth checking before you file: on Windows 11, do not run Syncplay as Administrator, as the site warns this can cause UI issues (referenced as issues #623 and #634). If your symptom matches that, the fix is to run it normally rather than to report a new bug.

Email the team

If GitHub isn't practical, write to [email protected]. The site asks that you check the Support section first so the problem can be resolved without a round trip. Email suits questions that aren't clearly bugs, such as installation confusion or feedback.

What not to expect from these channels

These are volunteer-run support routes for a free, Apache 2.0–licensed project. There is no stated response-time guarantee, and the site's own framing is community help plus bug tracking — so include enough detail in your first message to make a reply useful. Donations via PayPal are mentioned on the site as a way to support the project, but they are not a support channel.