Hi !

Simple question :  How to create a QT de-interlaced in Avid ?

Here's what I've done with no results :

-Select the sequence to export in the bin

-File/export :

- Quick Time Movie

- Custom

- Format options :Animation,  Kfr 30, Size: de-interlace source video

- 1920x1080 size to fit

- 601/709

-Even (lower field)

-Native dimensions

What am I doing wrong ?  The QT is still interlaced, I see ''the comb effect'' in the movements.

Thanks for your help !

Yesterday I had to sent a film of mine to a festival that wanted 1080 25p HDV (?!?) or 720 25p.

I have tried many things and at the end I took the Sorenson route.

I applied to the film a 720 25p preset and Squeezed it.

Now I don't have a way to test if this is progressive but it seemed better than anything else I've tried.

Thanks !  To ''take the Sorenson route'', you've made a QT ref and created a QT in Sorenson ?

Nope because my film was an m2t (HDV transport).

I imported the m2t and then I apllied the preset.

It gives me a way to explore.  If Avid can't do pregressive, maybe sorenson !

Thanks ! 

First I tried and drop the 1080 50i to a 1080 25p timeline.

But that was not HDV but HD (DnxHD) full raster. No problem till then.

I exported as DNxHD codec but I was unsure that they could be able to read the file if they do not have Avid codecs at their system...

My own workflow, when using interlaced source files, is to deinterlace before bringing into Avid MC. Ther's a lot of methods available that allwork very well. VirtualDub has a deinterlace plugin, as does Cineform NeoHD.

Thanks !

cuervo:

My own workflow, when using interlaced source files, is to deinterlace before bringing into Avid MC. Ther's a lot of methods available that allwork very well. VirtualDub has a deinterlace plugin, as does Cineform NeoHD.

And, of course, there are Avids own timewarp filters with lots of quality settings to select between, you select source - interlaced and target - progressive

This is one of the great things about QT7's QT Pro features. In QT Pro, you just export a movie, get the movie's properties, go to the video tab and check the "Deinterlace" box. Restart the movie and bingo, a deinterlaced QT.

In my case you miss a thing though. DNxHD could not be read by a festival if they don't have Avid codecs.

You should find a way that the file will be compatible with them. If it's only for progressive it's fine, you could

do this inside MC as well. But they wanted a raw mpeg2 (even TS) 1080p or 720p on a DVD disk so they could

download it to their servers.

BLKDOG:

This is one of the great things about QT7's QT Pro features. In QT Pro, you just export a movie, get the movie's properties, go to the video tab and check the "Deinterlace" box. Restart the movie and bingo, a deinterlaced QT.

I tried what you said, but I'm not seeing any difference in the actual resulting video when I play the file in QT.

Using QTPro7, I opened a movie with obvious interlacing artifats -- the movie is a QT created from a 29.98fps Avid project that used 24fps footage with 3:2 pull down.  In QTPro, I went to the QT "Movie Properties" page, selected the "video" track, selected the "Visual Settings" tab, and checked "deinterlace."  I saved the new movie and closed and re-opened it in QT.  The result was exactly the same -- absolutely NO difference in the visual result.

Does the QT Pro "deinterlace" option not effect the interlace artifacts you get from 3:2 pulldown?

Thanks,

Larry

If you are seeing field banding after deinterlacing the movie then you have a field order issue or a pixel stretching problem. If the fields were properly displayed, there would be no artifacting.  Tell us the project type from which you are exporting and the frame size and codec to which you are exporting and maybe we can find the problem.

Deinterlacing has always been problemmatic for me. In high horizontal motion areas, I've always experienced that sawtooth artifacting(combing) from the very real difference in field data due to the horizontal motion. Removing this combing is very difficult, especially when image motion is extreme. It may well be that you'll see this comb artifacting, even if the field order is correct and the deinterlacing has been applied.

Another solution, in this case, is to throw away one field and only use either the odd or even field. Unfortunately in this case, you'll cut your resolution in half.