mkv broken in r367 about ffms2 HOT 8 CLOSED

From GBalrog on January 01, 2011 06:44:16

Backtrace.txt

Attachment: Backtrace.txt

from ffms2.

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?
Can you still reproduce it with the latest SVN revision?
It appears that the issue shows up when indexing; does it crash ffmsindex as well or is it just x264?

from ffms2.

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 ffms2.

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 ffms2.

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 ffms2.

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 ffms2.

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 ffms2.

From tgoyne on January 03, 2011 14:58:13

This issue was closed by revision r403 .

Status: Fixed

from ffms2.