Deinterlacing through compressor results in striped stills.

[Rafael Amador]

Hi Johs,
De-interlacing of graphics is always a complication. The interpolated lines can break gradients or solid color surfaces.
Sorry, but no much to suggest that trying a better de-interlacer.
Have you set the de-interlacing to BEST, in Compressor?
rafael

http://www.nagavideo.com

[Josh Aderhold]

I’ve set it to better, but that’s the best I can do without Compressor either A. freezing up or B. taking a ridiculously long time.

Could a filter within FCP possibly fix the problem? Doing anything specific to the image? Certain files it might work best with? If I wasn’t getting such a horrible result from “Same as Source” I’d just go with that. But I’ve actually got complaints from my client on the quality after following the normal procedures for exporting through Compressor. And I’ve seen the results, not so good.

Now this is something that irks me as well. I’m working on another project where the typical route of exporting through compressor worked just fine.

8-bit project (HVX-200)
https://img.skitch.com/20100122-p86ta7x86321nmstu5hrwnea6m.tif

10-bit project (HDCAM)
https://img.skitch.com/20100122-nsfnudhjds4dx3d2xbnmb5b5ph.tif

My first project there, I didn’t even turn on Frame Controls, I just left it to auto and the result was fine. Where as with my 10-bit project, I follow the same procedure and it’s artifact city.

Can you possibly shed some light on why this would be?

MacBook Pro
Intel Core 2 Duo
2.6GHz
L2 Cache: 6MB
4GB Memory
Bus Speed 800MHz

[Chris Lachman]

HAD the same problem and had to delete the images and just start again. I do not believe that it is compressor but the treatment of fcp on the stills. When it happened to me it only seemed to show up on stills that I was panning on. I have done this a million times before with no issue – however – this was the first time I had used pro-res 422. It was very frustrating.

mac pro 8 core
16 gig ram
snow leopard
fca 6
using fieldsKit to deinterlace
hdv sony hdr-fx7

[Charlie Key]

Did you guys try rendering out all the stills and motion graphics from FCP to a movie, then laying it back down on then timeline, then exporting and processing through compressor.
That way, you are not working with still images at all.

[Rafael Amador]

There are millions of people every hour sending stills to Compressor without having those issues.
but things happens.
I would try de-interlacing the footage (NO Stills) in FC with the Nattress (only that works 10b in FC0, and send to Compressor ready Progressive.
We to do in Compressor (and slower) something that FC can do well?
rafael

http://www.nagavideo.com

[Josh Aderhold]

So what you’re saying is Apply all my deinterlacing in FCP with filters THEN send to Compressor so it’s progressive. Then I wont need to deinterlace and my images will now have no problem since they also won’t be deinterlacing. I’ll give it a shot. At this point I’m looking for a solution of something to add to the slides.

It really seems to be white or black that is giving me the problem. Or maybe it’s that I can only notice it on an extreme color like White or black.

Exporting to video seems like it would take too long. Too much extra work to export every slide (I have quite a few) and then reimport and throw on the timeline. I’ll give it a shot as well though. Just to see if it improves the problem.

Thanks,

MacBook Pro
Intel Core 2 Duo
2.6GHz
L2 Cache: 6MB
4GB Memory
Bus Speed 800MHz

[Rafael Amador]

You can try for free the Nattress de-interlacer.
The point is not to de-interlace the stuff that doesn’t needs to be de-interlaced (stills).
rafael

http://www.nagavideo.com

[Petter Sommer]

This worked for me:
Export the animated stills as separate quicktime movies, then reimport them into the timeline. This will also make the stills compatible with Apple Color, if you plan on doing some grading afterwards.