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
Stuttery video (guessed frame durations of 'avc1' will probably be wrong!) #56
Comments
Tried
…
…
|
Uploaded the files in case you need to take a look: https://we.tl/t-wQj90Je7uN |
Here I explained the meaning/reason of One idea I had was to measure the playback length of each frame. Btw, have you also used ffmpeg to save the stream? If not, what have you used instead? |
Yes, I used ffmpeg to save the stream. I truncated the file by accident by hitting Ctrl-C twice, at which point ffmpeg exited immediately. |
Interesting. I guess it would be worth digging into ffmpeg's source, to find out what's the cause for these non-constant durations, and to reason about if recovery is possible. Btw, in case you haven't seen it, there is a simple trick to avoid corrupt files while streaming with ffmpeg. |
@anthwlock Could be the same issue or completely unrelated. I also get a stuttery result in QuickTime Player but am missing the "..guessed frame durations.." warning. Playing back in ffplay and VLC works normally. Any ideas? Do you want me to open a new issue as the warning is not present in my case? Here is a sample: https://we.tl/t-hsqhlZeGYs |
@cbenhagen yes, open another issue. Please include a working reference file, a longer video (>10s), and a detailed description on what you mean by "stuttery result". Try if using |
Will do. Yes the working file plays well. |
Running master via Docker on macOS.
The broken.mp4_fixed.mp4 file plays, but stutters throughout in QuickTime Player. VLC plays it more smoothly, but with occasional pauses in the video and the audio is a little out-of-sync.
I'm guessing the “Warning: guessed frame durations of 'avc1' will probably be wrong!” is at the heart of the issue, here.
The text was updated successfully, but these errors were encountered: