Releases: yuv420p10le/plex_loadfile_hook
Releases · yuv420p10le/plex_loadfile_hook
v1.4
- Hooks only trigger on Plex and Plex HTPC now.
- Fixed seeking errors when debugging is enabled.
- Hook callback now calls the
mpv_command_ret
function rather thanmpv_command_string
. This allows mpv to set the playlist index accordingly to what Plex sets for the IPC. With this fix, the player will minimize (and return to the Plex interface) once playback ends, rather than stay with the player opened with the video file being unloaded.
v1.1a
- Enabled TLS verification when not connecting to
*.plex.direct
domains, like default Plex does.
v1.1
- Replaced API communication with a safer method.
- Added support for
*.plex.direct
URLs.- rcombs added
resolve-hosts
to the ffmpeg fork used at Plex for their stripped down mpv build. - The functionality does not exist in upstream mpv, as upstream mpv uses upstream ffmpeg; and that patch was declined.
- The setting is used by Plex to resolve plex.direct URLs to their IP addresses by appending this to
loadfile
:stream-lavf-o=resolve_hosts=[<ip_address>.<hash_goes_here>.plex.direct:<ip_address>]
- Then to support https for the
*.plex.direct
hostnames, they also import their custom CA database fromresources/cacert.pem
. - For whatever reason,
loadfile <url>
straight up bypasses the certificate mismatch when the path contains a valid video stream from the Plex Media Server.. I don't understand why nor do I care that much, but it's clearly not working as intended, as we are not supposed to even send the request to the host when the certificate is invalid. This allows me to just replace the Plex request to the mpv api so that it loads from thehttps://<plex server ip>:port/...
rather than thehttps://<ip>.<hash>:port/...
URL, and we get a working stream withoutresolve-hosts
and the custom CA database!
- rcombs added
v1.0
Initial commit.