Support for frame-percent synchronisation, e.g.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 moving seen files to a /seen/ folder, etc.Allow for various settings to be changed at runtime.If it happens, it will probably not be until Syncplay 2: Introducing a generic event hook system ( #202).Detachable chat overlay as an option ( #258).Option to add info columns to the playlist (length, path) ( #307).Probably adds too much complexity to be worth it: Allowing rooms to have a custom playback rate.See this forum thread for a discussion of KODI/XBMC suppor, issue #197 for a discussion on MPC-QT support, issue #218 for a discussion of PotPlayer support, and issue #144 for a discussion of IINA support, issue #62 for a discussion of BOMI support. It has been reported that SMPlayer may be controllable via mpris 2 but this yet to be investigated. Last we checked, SMPlayer and PotPlayer lack the APIs / API Features that Syncplay needed to synchronise playback. 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.Support for more languages – We can help people who want to help us translate Syncplay into their language!.Would need someone to come on board to develop: Conversation & event logging – See issue #201.Get paths for Media Players on Windows via registry.
If you’re a developer then please chat on #Syncplay on about which features you could help developer, or e-mail You can suggest an idea by raising an issue on our GitHub page. However, at present Syncplay 1.x only has one active core developer, so things might take a while. We’ve got lots of great ideas for Syncplay, many of which have been helpfully suggested by our user.
0 kommentar(er)
