-
Notifications
You must be signed in to change notification settings - Fork 66
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
'Check decoder errors' improvements #435
Comments
If I remember carefully, we just |
That could work I guess if piping, but here's what it just looks like when run in the terminal - the text wrapping cuts off the timestamps - could be a terminal-specific issue in windows though:
|
Hmm… I don’t remember having encountered difficulties. I have to check what I did. |
For my own workflow, I'm going to move to using ffprobe and taking a qctools-escue xml approach - more info here: http://ffmpeg.org/pipermail/ffmpeg-user/2020-June/049011.html |
Hi - I'm currently working with HDV rips using DVHScap as the capture tool. This creates mpeg transport streams, and decoding the file with ffmpeg is an amazing way of being told where glitches are. However - using the ffmprovisr recipe - https://amiaopensource.github.io/ffmprovisr/index.html#check_decoder_errors , it's pretty difficult to find the timestamps for the errors, so I've found that adding
-loglevel debug -report
is really useful ,as the-report
gives you a text log file in your current working directory, and-loglevel debug
logs at the appropriate level to catch these errors.For example this is a snippet from the text logfile gives you a rough area (00:30:51.44) to check in a video player and you can see where the glitch is:
What do ye think - anyone have similar experiences or ways to refine this?
The text was updated successfully, but these errors were encountered: