streamlink: Unable to use --player-fifo with MPV
Streamlink 2.0.0 mpv 0.33.0-76-g93066ff12f Copyright © 2000-2020 mpv/MPlayer/mplayer2 projects
streamlink --player-fifo https://www.twitch.tv/channelName best
[cli][info] Found matching plugin twitch for URL https://www.twitch.tv/channelName
[cli][info] Available streams: audio_only, 160p (worst), 360p, 480p, 720p, 720p60, 1080p60 (best)
[cli][info] Opening stream: 1080p60 (hls)
[cli][info] Creating pipe streamlinkpipe-1140
[cli][info] Starting player: "c:\Programs\MPV\mpv.exe"
error: Failed to start player: "c:\Programs\MPV\mpv.exe" (Process exited prematurely)
[cli][info] Closing currently open stream...
Works normally without FIFO
About this issue
- Original URL
- State: closed
- Created 3 years ago
- Comments: 36 (20 by maintainers)
There seems to be an issue with Streamlink’s named pipe implementation on Windows. Neither MPV nor VLC is able to read from it. The named pipe implementation is working fine on *nix. https://github.com/streamlink/streamlink/blob/164b2579262a72bb291bd641309b703556878332/src/streamlink/utils/named_pipe.py
@Kein This thread was closed and tagged with “does not meet requirements” because you were (still) not able to provide a proper debug log with the necessary details, which the issue template is explicitly asking for. Remember that this is a free open source software project with volunteers working on it in their free time for fun, and the more details you provide, the easier it is for reproducing and fixing bugs. I’m giving you the first and last warning to watch your tone and not harass/insult any maintainers or contributors here.
@Kein I literally quoted what you wrote in a previous comment. I also didn’t say you did say it worked on Windows, I asked where you it says it works with named pipes because I couldn’t remember where it was in the docs.
Anyway, it does work on Windows with MPV - you just need the correct incantation.
@bastimeyer We can update the documentation to include a footnote for VLC and MPV using named pipes on Windows. We could also detect if the user is using named Pipes and Windows and direct them to the documentation notes with an
INFOlog message or something.The way that Named Pipes have been handled by these players has changed over time, and this has been a frustrating issue to debug…