--stream-dump failure #1382
Comments
|
Could it be that with normal playback, it's first searching channels or so? There is such a code path: if opening the demuxer fails (i.e. recognizing file format, checking whether there's video data at all), then it switches channels until it finds something that works. But since the demuxer is out of the loop with --stream-dump, this part is skipped. So, maybe check whether you got the right channel. |
|
@wm4 Thank you for responding and the good work on mpv. |
|
Actually, you're using Then I don't know what's wrong. Can you maybe post a log when playing from pvr normally? (Also, I didn't know someone is still using |
|
<Also, I didn't know someone is still using pvr://.> Here's what I get when running pvr:// normally: |
|
If I don't use the -v switch at start up, the error common to both --stream-capture and --stream-dump is this: Capture apparently works past this error, but dump doesn't. |
|
Yeah, looks like this is what's happening. Usually, such a read failure would also make the demuxer quit, but maybe something retries reading for some reason. Maybe it would be better to fix the read error. The code looks a bit suspicious (and uses a timeout). But since I can't test pvr myself, I could at best do some trial&error. |
|
Thanks @wm4. If there is anything you would like me to try or test on my machine please let me know, I'd be most happy to help in any way I can. |
ghost
pushed a commit
that referenced
this issue
Dec 26, 2014
An attempt to find out what's wrong with issue #1382. I don't even know why a timeout would be needed; for robustness with broken devices maybe?
|
Can you retry git master? I have no idea if it helps. |
|
@wm4: Thank you, my man, that did it. The read error doesn't occur any more and --stream-dump works now. Thank you so much! Would you like to see the log? It's all green now. :) |
|
Probably not necessary. Still, a very strange timeout (and also strange that it fixes this). Well, if it works, good enough. |
ghost
closed this as
ghost
pushed a commit
that referenced
this issue
Jan 24, 2015
An attempt to find out what's wrong with issue #1382. I don't even know why a timeout would be needed; for robustness with broken devices maybe?
ghost
pushed a commit
that referenced
this issue
Jan 25, 2015
An attempt to find out what's wrong with issue #1382. I don't even know why a timeout would be needed; for robustness with broken devices maybe?
This issue was closed.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When I try --stream-dump, I only get this:
I'm using version 0.7.2-1 on Arch Linux and --stream-capture works.
The text was updated successfully, but these errors were encountered: