Ideas for improvements to Syncplay

We’ve got lots of great ideas for Syncplay, many of which have been helpfully suggested by our user. However, at present Syncplay 1.x only has one active core developer, so things might take a while. If you’re a developer then please chat on #Syncplay on chat.freenode.net about which features you could help developer, or e-mail dev@syncplay.pl. You can suggest an idea by raising an issue on our GitHub page.

Bugs we’re hoping to fix soon:

  • MPC-HC / MadVR pause/unpause detection issue (#52)
  • Erroneous mpv seeks on OSX (#60)

Big features we see as important:

  • Shared playlists (#40) [currently under construction]

Tweaks and new features we expect to implement some day:

  • Chat room functionality (#54)
  • Prevent ‘ghosts’ – Use GUIDs to detect someone has reconnected via the same instance of Syncplay.
  • Allow to save configuration without running Syncplay, e.g. holding down shift toggles functionality of button
  • Allow for more control over rewind/fastforward/slow down – E.g. you press a button or check a checkbox during run-time to use/enable this feature, to prevent misdetection causing serious issues and loops, etc
  • More detail on actions in the channel notifications, e.g.:
    >[timestamp] [username] started playing [title of video] – means it started from 00:00:00 no need to indicate time
    >[timestamp] [username] paused [title of video] at [exact time of where the video paused]
    >[timestamp] [username] resumed/unpaused [title of video] from [exact time of where the video resumed]
  • Get information about currently playing file – e.g. CRC32 checksum, time left
  • Less delay between later reconnection attempts
  • Fix all unpause on new file / before connection issues
  • Better error for when Twisted is not installed

Might happen, not sure:

  • Context menu option for opening with Syncplay rather than file association (for Windows installer)
  • Bookmarks
  • Per-server favourite rooms
  • Get paths for Media Players on Windows via registry
  • Availability through more packaging systems
  • Make offsets more user-friendly
  • More style customisation options
  • Support for Syncplay:// protocol (or similar) and .sync files for easy launching with specific settings
  • More customisation of interface (e.g. floating playback buttons)
  • Allowing rooms to have a custom playback rate

Would need someone to come on board to develop:

  • Support for more languages
  • Support for additional media players – Additional media players would need to come from an individual who used that media player and was willing to maintain it, and may require modifications to the media player software itself. Last we checked, MPC-BE, SMPlayer and PotPlayer lack the APIs / API Features that Syncplay needed to synchronise playback. It has been reported that SMPlayer may be controllable via mpris 2 but this yet to be investigated. See this thread for a discussion of KODI/XBMC support.

If it happens, it will probably not be until Syncplay 2:

  • Syncplay API
  • SSL or equivalent to protect communications
  • Allow for various settings to be changed at runtime
  • Support for moving seen files to a /seen/ folder, etc
  • Support for plugins – Could allow others to develop integration with Ultros bot server, Bittlebee gateway server, Mumble, IRC, MyAnimeList, Android/iOS controllers, etc
  • Support for changing settings during runtime

Unlikely to ever happen:

  • Support for frame-percent synchronisation, e.g. for public displays – It’d be a lot of work for something which makes no difference for our core purpose, which is allowing for people to synchronise over the Internet (where VoIP latency and the inability to actually see the other screen means any small amount of latency is unimportant).
  • Support for media player’s internal playlists – We’ll use Syncplay’s shared playlists instead (#40)

1 Comment to Syncplay ideas and plans

  • Paul says:

    Unlikely to ever happen: “Unlikely to ever happen!” =) Anything is possible! Cool software. Keep up the great work!

Leave a Reply

Your email address will not be published. Required fields are marked *