Support for loading native mpv configuration files

[c-v-ya]

Hey!

I've been using Supersonic and noticed that it currently doesn't pick up the user's native mpv configuration files (mpv.conf). While the player works great out of the box, many users have carefully tuned configs. For me it's proxy settings that are currently ignored.

I believe adding support for this would significantly improve the experience for power users without affecting the default behavior.

The Proposal:
Allow the player to automatically load the mpv.conf from the standard system paths, ensuring a consistent experience between the standalone mpv and this project.

I have already implemented a working prototype locally that covers:

• Linux/macOS: Loading from ~/.config/mpv/
• Windows: Loading from %APPDATA%/mpv/
• Cross-platform stability: Verified that local player settings still take precedence (or complement) the config file where necessary.

I’d love to contribute this back to the project. Would you like me to open a PR for this?

Best regards,
Constantine

[dweymouth]

I'm not sure this makes sense, especially since we might not be using MPV forever - see #360. What makes more sense I think is to expose the functionality that you need as Supersonic config, either in the UI or even only accessible in the config file if it's something quite niche.

[c-v-ya]

Understood, that makes sense. Keeping it backend-agnostic is definitely the better approach for the long term.

I'll look into implementing proxy support directly within the Supersonic configuration instead. I'll see what I can do and will follow up if I have a solid PR ready.