added static ipc support and configurabe dynamic ipc support #4
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Added support for configuring weather a dynamic or static ipc socket should be used, with the abilitu to configure where
the dynamic ipc socket should be created. It would potentially also make sense to enable configuring the path of the static
ipc socket, though that seems less usefull to me since that is typically set to /tmp/mpvsocket.
I tested this on linux, in combination with SVP, and as long as both are configured the same way
(either both use /tmp/mpvsocket or both use /tmp/mpvSockets/$PID), they work flawlessly with each other.
I did not test on macos or windows, as I currently dont have these OS available to me.
macos should work out of the box, though windows might be tricky.