-
Notifications
You must be signed in to change notification settings - Fork 182
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
Error: unable to find correct codec -> premature end (~0%) #51
Comments
I repair videos on Windows 10 |
Make sure that How to uploadhttps://wetransfer.com/ offers hosting <2GB files for 7days, without registration. |
What software did you used to create those files? |
Btw, the download of the broken 2.1GB file stops at 1.1GB. I tried multiple times and with different browsers. |
I use ffmpeg to record m3u8 live link,like |
I uploaded the broken video files again. This time, I compressed them into multiple compressed packages. If you need, you can download them again |
Just to make sure.. is the following md5sum correct? |
a984f3ad141cccdaef5e850e6d96897c no.mp4 |
The metadata was packed in nal-units with nal_type=31, fixed with 907fbb5. Additionally ffmpeg3.4+ failed to decode some mp4a samples, because internal decoder state was not reset after 'gaps' in the audio-stream. These gaps may be caused by network transmission errors. This got fixed with 56aee28. Tip |
Info: version '71d1a65' using ffmpeg '3.3.4'
Info: reading ok.mp4
Info: parsing healthy moov atom ...
Composition time offset atom found. Out of order samples possible.
Info: reading mdat from truncated file ...
Error: unable to find correct codec -> premature end (~0%)
try '-s' to skip unknown sequences
Warning: guessed frame durations of 'mp4a' will probably be wrong!
Warning: guessed frame durations of 'avc1' will probably be wrong!
Info: Found 0 packets ( mp4a: 0 avc1: 0 avc1-keyframes: 0 )
Info: Duration of mp4a: (0 ms)
Info: Duration of avc1: (0 ms)
Info: pruned empty 'mp4a' track
Info: pruned empty 'avc1' track
Info: saving no.mp4_fixed.mp4
The text was updated successfully, but these errors were encountered: