Skip to content
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

ffms2 issue causes a crash near the end #41

Closed
tgoyne opened this issue Aug 19, 2013 · 3 comments
Closed

ffms2 issue causes a crash near the end #41

tgoyne opened this issue Aug 19, 2013 · 3 comments

Comments

@tgoyne
Copy link
Member

tgoyne commented Aug 19, 2013

From josecore.jgj on February 16, 2011 05:46:31

What steps will reproduce the problem? 1. Extract the h264 stream from a m2ts Blu-ray source to an mkv file.
2. Create AVS: "ffvideosource("shikiextra01.mkv",fpsnum=24000,fpsden=1001)"
3a. Encode the file using avs2yuv. A few frames to the end avs2yuv crashes, and x264 countinues with the remaining frames extremely quickly until it finishes.
3b. Encode the file using VirtualDub with codec Huffyuv. A few frames to the end VirtualDub crashes. What is the expected output? What do you see instead? I expected an output of 3251 frames, and I get one of 3247 frames. What version of the product are you using? On what operating system? Using ffms2 2.15-mt in Windows Vista x64. With ffms2 2.14-mt the problem don't occur. Please provide any additional information below. If I try to open the corrupted Huffyuv AVI file with vdub, I get these warnings:
[!] AVI: Index not found or damaged -- reconstructing via file scan.
[!] AVI: Invalid chunk detected at 1199713928. Enabling aggressive recovery mode.
[!] AVI: Keyframe flag reconstruction was not specified in open options and the video stream is not a known keyframe-only type. Seeking in the video stream may be extremely slow.

This is the mkv of the issue (551 MB): http://www.megaupload.com/?d=4TKJLDN8

Attachment: vdubcrashinfo.txt

Original issue: http://code.google.com/p/ffmpegsource/issues/detail?id=41

@tgoyne
Copy link
Member Author

tgoyne commented Aug 19, 2013

From kalle.blomster on February 17, 2011 04:55:55

Does the same thing happen if you don't force the framerate using fpsnum and fpsden? I suspect this is Plorkyeran's fault.

Status: Accepted

@tgoyne
Copy link
Member Author

tgoyne commented Aug 19, 2013

From josecore.jgj on February 17, 2011 17:53:06

I just checked it and without forcing the fps it works fine.

@tgoyne
Copy link
Member Author

tgoyne commented Aug 19, 2013

From tgoyne on February 21, 2011 17:34:57

This issue was closed by revision r451 .

Status: Fixed

@tgoyne tgoyne closed this as completed Aug 19, 2013
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant