You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is not a bug report, feature request, or plugin issue/request.
I have read the contribution guidelines.
The wiki currently states that quicktime does not work but I've gotten it to work using this .streamlinkrc:
player=/usr/bin/open
player-args=-W -n -a 'Quicktime Player' {filename}
player-passthrough=hls
Works by passing the hls stream as an m3u8 file and then using 'open' on the file with the application parameter set to Quicktime. I think this would be useful info for the wiki.
By using the player-passthrough=hls parameter, you are bypassing Streamlink and instead passing through the HLS stream URL to the player and using it as its first launch parameter. This means that the Player will do all the downloading and buffering on its own. Streamlink won't do anything and will just wait until the player gets closed. It's the same as running this:
# launching the player executable directly
/path/to/player "$(streamlink --stream-url URL QUALITY)"# or macOS specific app launcher
open --wait-apps --new -a "Some Player.app" --args "$(streamlink --stream-url URL QUALITY)"
Quicktime Player doesn't support reading from stdin, which makes it useless in combination with Streamlink (the regular way).
@bastimeyer has been kind enough to explain why Quicktime doesn't support Streamlink so I'm going to close this as there isn't anything for us to document in relation to Streamlink itself.
Issue
The wiki currently states that quicktime does not work but I've gotten it to work using this
.streamlinkrc
:Works by passing the hls stream as an m3u8 file and then using 'open' on the file with the application parameter set to Quicktime. I think this would be useful info for the wiki.
Additional comments, screenshots, etc.
Love Streamlink? Please consider supporting our collective. Thanks!
The text was updated successfully, but these errors were encountered: