-
Notifications
You must be signed in to change notification settings - Fork 104
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
mkv broken in r367 #37
Comments
From GBalrog on January 01, 2011 06:44:16 Backtrace.txt Attachment: Backtrace.txt |
From kalle.blomster on January 01, 2011 09:13:01 That's not a very helpful bug report. Does it happen with all MKV files or just a particular one? |
From GBalrog on January 01, 2011 22:06:37 I've got this error in all mkv files (I tried ~10 files) I make a mistake when i say that bug appears in r367 . I tried many versions and it seems that bug appears in r382 or r383 (I can't build r382 ). So all versions > 382 (including latest svn) are broken. Run "ffmsindex [file]" is enough to reproduce the bug. |
From r.korving on January 02, 2011 11:27:52 I have the same problem, had the error many times before with different builds but never reported it. In windows/wine there isn't a problem because ffms uses haali then. However I build ffmpeg with -enable-gpl --enable-version3, should there be more? |
From kalle.blomster on January 03, 2011 02:21:50 @GBalrog: are versions earlier than r382 working, then? @r.korving: Haali's dshow splitter is only used for Ogg and MPEG TS/PS, never for MKV. For MKV, the native Matroska parser is always used. When you say you had the error many times before with different builds, do you mean it's showed up earlier than r382 ? |
From r.korving on January 03, 2011 03:36:29 I don't know from which reversion it broke, I've only been using ffms2 on linux since about a month or so. So it could be that I started with r382 . How can I grab a certain revision so I can test it? I'll have some time tomorrow to test a few builds. Right now I'm on my own build of 2.14.01-SVN- r376 and it goes to about 30% of indexing a mkv and then jumps at lightning speed to 100% resulting in an index that doesn't know all the frames and only 1/3 of the file gets encoded by x264. |
From GBalrog on January 03, 2011 09:19:06 @kalle.bl Yep. Versions 366-381 working fine. @kalle.bl You can use "svn checkout http://ffmpegsource.googlecode.com/svn/trunk/ ffmpegsource-read-only -r [REVISION]" to grab certain revision. |
From GBalrog on January 01, 2011 06:42:23
What steps will reproduce the problem? 1. install latest ffms
2. install ffms > r367 3. encode mkv file with x264 ffms input What is the expected output? What do you see instead? error... check Backtrace.txt What version of the product are you using? On what operating system? Gentoo Linux Please provide any additional information below. check Backtrace.txt
Attachment: Backtrace.txt
Original issue: http://code.google.com/p/ffmpegsource/issues/detail?id=37
The text was updated successfully, but these errors were encountered: