Animation + cause interlace issue

[Kevin Camp]

or, if you wanted to render progressive, in the interpret footage settings (select footage in project window, the choose file>interpret footage>main) you should set the option for ‘preserve edges’. then render with field render off (which is normally the default in the render settigns).

Kevin Camp
Senior Designer
KCPQ, KMYQ & KRCW

[Laurie Turner]

Thank you, but still no luck. I tried both ways and both ways together. Still has the interlace issue. I thought maybe it had to do with my keylight settings, but i don’t think so because her lips when she talks looks interlaced too.

[Kevin Camp]

are you playing the rendered file in ae, or in another piece of software? if it’s in another piece of software, try importing back into ae and see if you have the same problem. if it is in ae, make sure that ae is interpreting the footage correctly, particularly the field options.

also, what are your render settings and output module settings (from the render queue).

Kevin Camp
Senior Designer
KCPQ, KMYQ & KRCW

[Laurie Turner]

Funny, when play it just as a QT mov on it’s own I see the interlace. I put the mov file in Final Cut Pro and the interlace is gone. I guess that means I am alset.

render setting is Animation + Millon, MOV

[Laurie Turner]

oh no Dave, I wasn’t using FCP to composite. Just to test to see if my mov output looked interlace in FCP. We are actually going to use the alpha in Flash to go over a webpage. I never use FCP for composite. that’s what AE is for

[Paul Mcdonald]

I’m getting EXACTLY the problem described in the original post. All the variables are the same. A few of us at work have had a look at all my settings and I’m not so sure its just operator error.

In AE CS4 I bring in my source footage (16×9 Uncompressed 10bit progressive material), interpret it correctly, do my keying using Keylight 1.1, and render out using my standard uncompressed export module. In this case I wanted to render out the keyed material as both RGB plate on black and separate greyscale transparency matte. The material looks fine in my comp, well as fine as my keys usually look! – no fields and clean key edges. When I hit render it renders out at half resolution. The edges go to pieces bigtime. I also tried the Animation+ option with identical results. The render looks this way when I bring it into FCP and interpret it correctly.

I don’t get this issue if I have a solid behind my keyed footage. If I reduce the opacity of that solid it comes back. I also tried to cheat it by remapping the key to the RGB channels, adding a black solid behind the now greyscale key and rendering that out as a lumakey but no luck – the quality drops on render.

I’ve triple checked all my output settings. Quality is best, resolution full and field render off. We’re at a loss to understand what it causing it. We only recently upgraded to CS4 and did not have any issues with prior versions. I think Keylight is somehow causing or related to the issue – I rendered out 32bit material the other day with no issue. Love to hear other peoples take on the problem.