Open gsk143 opened 8 months ago
Discord RPC seems to rely on IPC and as such I think this might be related to the issue at https://github.com/Syncplay/syncplay/issues/529 and https://github.com/iamkroot/trakt-scrobbler/issues/266
I am not aware of any satisfactory solution to that issue from 2022, and this seems like it could be considered an upstream limitation of mpv.
One potential workaround is for someone to add rich presence to Syncplay. Someone requested this at https://github.com/Syncplay/syncplay/discussions/491 back in October 2021 but to date nobody has volunteered to implement it .
The latest development build of Syncplay now creates a new IPC socket called mpvSyncplaySocket or \.\pipe\mpvSyncplaySocket that you can connect to with mpv-discord, or you can specify a different socket to use with by specifying a input-ipc-server player argument in Syncplay. See: https://github.com/Syncplay/syncplay/actions/runs/7766691704
So you should hopefully be able to get it to work with mpv and this version of Synplay by setting socket_path in /script-opts /discord.conf to the Syncplay IPC socket.
@gsk143 Please test it and let me know if it works.
From Syncplay 1.7.3 the user will need to specify the pipe name (e.g. input-ipc-server=\\.\pipe\examplepipe
) to connect to an mpv pipe. See #674 and #675 for details.
Describe the bug Application crashes when using discord RPC https://github.com/tnychn/mpv-discord
Version and platform:
This can very well be the plugin issue but wonder if something can done here![image](https://github.com/Syncplay/syncplay/assets/60306998/4f34d3b2-b754-473a-bcef-3f729f7702a2)