help ! Frames being returned out of order

[halsboss]

jagabo, you're brilliant.

Used mpeg4modifier to make the AVIs packed bitstream and all problems went away opening the avis with avisynth with avisource. Even an avi I had problems with which was supposedly packed bitstream I tried to unpack then pack again and hey presto it worked just fine - go figure.

edit: moved queries to the doom9 thread.
edit2: well, more info below.

[halsboss]

It was a good idea while it lasted. I saw a packed bitstream xvid in .AVI and thought "that'll be OK" but it turned out to be a little odd. Unpacked with mpeg4modifier and repacked with it, and still had problems with it.

The only reliable way I found to get around it was via a combination of mpeg4modifier and the latest ffmpeg -
(1) unpack it with mpeg4modifier
(2) convert to a lossless ffv1 .AVI (ffmpeg handles xvid's b-frames in AVI OK by the looks, from non-packed-bitstream AVIs)
(3) then process the ffv1 AVI with avisynth.

Command lines :-

"C:\SOFTWARE\MPEG4Modifier\mmcl.exe" --unpack --always-write "input.avi" "input-unpacked.avi"   
"C:\SOFTWARE\ffmpeg\ffmpeg.exe" -y -i "input-unpacked.avi" -f avi -vcodec ffv1 -an "input-ffv1.avi"

EDIT: follow-up thread here http://forum.doom9.org/showthread.php?t=145262

Feel free to post ideas here too.

[halsboss]

ANSWER:
The Packed Bitstream AVI fix ONLY works if you use the latest XVID codec and not ffdshow's xvid decoder. It works then.

From the other thread:

Always use packed bitstream with avi and use xvid to decode instead of ffdshow. Unticking decoding xvid in ffdshow (both vfw and non-vfw) and installing the latest xvid makes the problem go away.

[jagabo]

ANSWER:
The Packed Bitstream AVI fix ONLY works if you use the latest XVID codec and not ffdshow's xvid decoder.

Interesting. Good to know.

[Ai Haibara]

Will it work if you have ffdshow set to use Xvid to decode, rather than libavcodec?

[halsboss]

I had to uninstall xvid for ffdshow to be used again. Anyway, tried all 3 ffdshow settings :-

1. disabled = virtualdub had no codec to decode, as expected
2. libavcodec = the anomalous behaviour described
3. Xvid = "good behaviour"

Anyway, decided to go back to install Xvid and disable ffdshow's xvid, just to be on the safe side.