I feel mpvqml could be a lot more useful, if you allowed more of the regular mpv configuration possibilities for the user. There are probably plenty of settings that can't really be utilised due to the qml wrapping, but especially a lot of backend settings could be modified.
The most interesting thing it would allow me to do, currently, would be to set script-opts=ytdl_hook-ytdl_path to somewhere in the config or data dirs where the app can see my remote yt-dlp wrapper. It works fine if it's in $PATH and I start mpvqml without sailjail, but would be nicer if it could be kept jailed without losing the functionality.
I feel mpvqml could be a lot more useful, if you allowed more of the regular mpv configuration possibilities for the user. There are probably plenty of settings that can't really be utilised due to the qml wrapping, but especially a lot of backend settings could be modified.
The most interesting thing it would allow me to do, currently, would be to set
script-opts=ytdl_hook-ytdl_pathto somewhere in the config or data dirs where the app can see my remote yt-dlp wrapper. It works fine if it's in$PATHand I start mpvqml without sailjail, but would be nicer if it could be kept jailed without losing the functionality.