-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conflicts with mpv-discord due to ipc socket #11
Comments
I have created a PR in mpv-discord (tnychn/mpv-discord#46). Setting |
Thanks for your advice on configurable socket name :D |
Please update the readme with the new socket parameter as well |
Yes, thanks for reminding! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently, this plugin works inconsistently with mpv-discord due to the two plugins overriding the socket name.
mpv-discord names the socket to
mpv-discord-{pid}
while this plugin names it tompvsocket_{pid}
, perhaps there should be configurable option to change this format. Instead of sending the pid to the program, send the socket name instead and letnotify_media.lua
format it first with the pid in. That way, I can ideally set something likesocket_path=mpvsocket_{pid}
in the conf file.The text was updated successfully, but these errors were encountered: