interlaced encoding in x264 is here

[Malow]

I did some testing using hpn's command lines. The problem is I couldn't get CoreAVC to do any deinterlacing on the resulting file. This should usually happen automatically and does with other interlaced AVC files that I've tried. Any ideas what the problem may be?

i have same prob. tried a lot of options, conf, containers, none of them do a deinterlace.

using mainconcept encoder, the interlaced content works fine with "diresctshow deinterlace"

is not a flag or somethign missing in the file? how coreavc know if is interlaced?

[Jay Bee]

i have same prob. tried a lot of options, conf, containers, none of them do a deinterlace.

using mainconcept encoder, the interlaced content works fine with "diresctshow deinterlace"

is not a flag or somethign missing in the file? how coreavc know if is interlaced?

After further testing I've found that the mainconcept encoder displays the same behaviour as x264 when set to MBAFF. So maybe the problem is with CoreAVC?

[foxyshadis]

MBAFF might be one of their big 1.2 features, then. It's a lot more complex than PAFF, unless you were to just deinterlace all of any frame that has any MBAFF blocks in it (which is kind of silly).

[Jay Bee]

MBAFF was actually the big 1.1 feature. I just had a look at the BBC HD MBAFF test clips (http://www.giusberto.ch/hdtv/) to confirm they actually are automatically deinterlaced by CoreAVC. What I found is that I couldn't tell any difference in playback between disabling deinterlacing and setting any of the deinterlacing modes, the picture looked fine either way.

Does this mean the clips aren't really interlaced? CoreAVC doesn't really support MBAFF deinterlacing? Both? Beats me.

[Malow]

if video is really interlaced, the diference shoud "pop" in your eyes.

as i only work here with interlaced video, a proper BOBed video is a must... otherway, you will have a blurred or "lined" (i dont know the word..;) ) video instead a "60fps look" smooth video...

[Malow]

I work with lots of DV footage and this will instantly be useful.

me too.

[Jay Bee]

if video is really interlaced, the diference shoud "pop" in your eyes.

as i only work here with interlaced video, a proper BOBed video is a must... otherway, you will have a blurred or "lined" (i dont know the word..;) ) video instead a "60fps look" smooth video...

Yes, the motion smoothness is the exact reason I'm interested in interlaced encoding and I often wonder why so many people don't seem to mind 25 fps jerkyness. But concerning the BBC clips I mentioned above I simply don't have the CPU power to see if they are really smooth or not. They run at about 20 fps for me so I don't know if they go up to 50 or only to 25 on faster machines.

[Sharktooth]

Well, the interlaced effect on motion is a sort of motion blur...
You dont need interlacing to "reproduce" that smooth motion effect...
Interlaced is really born as a sort of analog compression.

[Jay Bee]

Motion blur? Isn't it the opposite i.e. sharp and double frame-rate instead of blury and same frame-rate? Or do you mean blurry compared to 50 progressive fps?

What I meant is that most of the content I want to encode is inerlaced and I want to encode it without changing the resolution and that includes the temporal resolution, not just the spatial resolution. Using an advanced adaptive bobber before encoding would be one way to do this but this would need a much higher bitrate than just keeping it interlaced and letting the playback software deal with the deinterlacing.

The standard on the net seems to be to use a blend-type deinterlacer before encoding which IMO makes motion too jerky for fast-paced sports. One example would be the football torrents that were around during the World Cup, I found them hard to watch compared to live TV because the ball is just too fast for 25 fps.

[Jay Bee]

I did some testing using hpn's command lines. The problem is I couldn't get CoreAVC to do any deinterlacing on the resulting file. This should usually happen automatically and does with other interlaced AVC files that I've tried. Any ideas what the problem may be?

I found a workaround (http://forum.doom9.org/showpost.php?p=890190&postcount=1768) that makes me believe the problem is more likely to be with CoreAVC than with x264.

Neither. Field order is not specified, as it makes no difference to MBAFF compression.

Could you explain what this means? On all the deinterlacers I've tried on x264 interlaced files, switching the field order does make a difference. Also, I thought x264 does pure interlaced, not MBAFF? Thanks for any answers.