Open jcaesar opened 1 year ago
This error should occur when the device you're streaming abruptly rejects the stream. Most likely the format that ffmpeg is sending is not what the TV is expecting, or is not supported by the TV. Perhaps web
is the wrong transcode target for your TV.
That was my first hypothesis, but I finally got some time to look around:
webb
and chromecast
. With vp8
, the TV immediately displays a "Unplayable file" message-forceTranscode
) that can also be streamed from other servers (minidlna/rygel)foo.dms.json
containing {"Title":"Foo","Resources":[{"MimeType":"video/x-matroska","Command":"cat file-that-plays-without-transcoding.mkv"}]}
and confirmed that it doesn't play (I get the same failed: signal: broken pipe
but no spinner from the TV, just an immediate exit from the playback menu.-logHeaders
, it seems there are two subsequent requests, the second containing Range: bytes=7075-
.Could the range request pose a problem? [Edit:] Looking at the response, there's no Content-Range
, so I'll make that my prime suspect.
Hm yes, I don't remember the specifics (I started this project nearly 12 years ago), but I doubt range requests are supported for on-the-fly transcodes if that is what it is doing. Range requests should work fine for static files.
I'm running with
-forceTranscodeTo web
and the log is just full ofThe ffmpeg tail shows
This would indicate to me that dms isn't reading the data - how would I debug this?
[Edit:] This seems to only happen when trying to play files from my Panasonic TV. Hmm.