interlaced MJPEG is loaded incorrectly

[Malcolm]

Hi,

i have a problem with interlaced MJPEG-captures in avisynth 2.50. I'm using the Morgan-MJPEG codec.

when i open my interlaced capture in avisynth via DirectShowSource(), the image is fine.
correct interlaced capture (JPG) (http://home.graffiti.net/hansahansb/doom9/heimflyer_1.jpg)

when i open my interlaced capture in avisynth via AVISource(), the image looks like all odd (or even) lines are discarded.
incorrect interlaced capture (JPG) (http://home.graffiti.net/hansahansb/doom9/heimflyer_2.jpg)

So i guess, there's a problem with the vfw-decoder but not with the DirectShow-Decoder. Or is it because of avisynth (2.50)?
I really don't want to use DirectShowSource() because it brings some problems and limitations.
Does anybody has a quick tip or solution for me? Is there a way to decode the capture with a different MJPEG-Codec (vfw)? Or mybe the problem occurs later in avisynth? Mybe because of YV12? Can i force avisynth / the MJPEG-codec to open the capture in YUY2?

Thank you for your help!

bye,
Malcolm

[Schlumpf]

I just wanted to add that I had the same problem with the newest Coedec from Morgan. It remained interlaced, no matter what I threw at it (ComplementParity,SwapFields and all the other stuff I could dig up in the Avisynth Documentation dealing with Interlace.)
I could bypass this problem by selcting "support interleave" (IIRC) in the compressor options, but that made the codec slower and increased the bitrate quite a bit.

BTW: It showed me these Interlacelines, although I was dealing with a progressive source....strange.

[sh0dan]

Yes - it seems like morgan has faulty YV12 output. It seems like they fielddouble instead of delivering properly interlaced material. (Probably just a pointer error, where so they copy the same field twice) :(

If you have registered I'm sure they will have a look at the problem and fix it.

Meanwhile, use:
AVISource("file.avi",pixel_type="yuy2")
converttoyv12(interlaced=true)

and the newest CVS binary.

[UPollaehne]

I experience the same problem with the Morgan MJPEG codec and hope that they will fix this.

@Malcolm: Did you send a mail to Morgan so that they get knowledge of the problem?

@Schlumpf: I also have set support interleave and do experience the problem. BTW: Some time ago I tested without interleave support and it seemed to me that this stored only one field of the two.

@sh0dan: Do I always need to give interlaced=true? I mean is this also necessary for TV captures of movies that are not interlaced and not combed? (I am just asking since there could be some hidden issue with not giving the parameter in the above cases)

[sh0dan]

Oh right - the image isn't interlaced. Sorry for that one - must have been the topic that diverted me. ;)

[sh0dan]

Reminds me - isn't UV swapped - or was that only in older versions?

[akabob]

Malcolm,

maybe u could try PICVideo MJPEG instead of Morgan's one. I haven't experienced this kinda problem with Avisynth 2.5

Regards

[UPollaehne]

@sh0dan: Yes, UV is swapped in addition to the other issue (version 3.0.0.9).

[Malcolm]

Thank you all very much for your help!

@Sh0dan,
Is the AVISource-parameter 'pixel_type' only available in the newest CVS binary of avisynth?

I caputured a b&w Movie, so the UV swapping doesn't matter to me!! :o))

bye,
Malcolm

[sh0dan]

No - pixel_type has been present in all v 2.x versions.

Made a post at the morgan forums.

[sh0dan]

Found this in their docs:

Support Interleave
Apply only if height is more than 288.

If checked, decompress and display 2 interleaced fields per frame.

If unchecked decompress and display only the first field (odd lines). Odd lines are duplicated to fill even lines.


Seems worth a shot!

[giom]

We have done a beta release wich corrects the reported bugs.
If you want to test it, download it here: http://www.morgan-multimedia.com/ubb/forum1/clicks_db/download.asp?file=m3jpegV3beta.exe

Thank for reporting those bugs.

Regards

Thread about this topic on MM forum : http://www.morgan-multimedia.com/ubb/new/topic.asp?TOPIC_ID=230&FORUM_ID=1&CAT_ID=1&Topic_Title=YV12+output+broken%2E&Forum_Title=Morgan+MJPEG+codec+Forum%2Ecom

Giom.

[sh0dan]

It's really great - finally we have a good capture format that allows to work in YV12!

Morgan strikes back! :cool:

[Malcolm]

Thank you guys!!

Greetings,
Malcolm

[Boulder]

Should 'support interleaved' be enabled when capturing in YV12?

[UPollaehne]

@Boulder: It should always be enable as long as you want the full frame and not only one field. Without interleave support the codec simply discards one field.

[Boulder]

Is there something wrong with my setup?

YUY2:
http://www.cc.jyu.fi/~camneely/yuy2.jpg

YV12:
http://www.cc.jyu.fi/~camneely/yv12.jpg

I find it strange that the YV12 capture doesn't have any combing artifacts whereas the YUY2 has. The settings were the same, I only switched format from YUY2 to YV12 between the captures. Or am I just totally confused - again:D