-
keylight and crashing
I am using a Mac Pro dual quad with 14 Gigs of ram. In AfterEffects CS3 I am trying to chromakey SD component video recorded on Beta, captured on an Avid, and exported to me, as Meridian 1_1 compression Quicktimes. I am using Keylight.
I can get a good looking key during preview, and when I switch an unaffected top layer on and off I don’t see any change in how the video looks (except for spill suppression.) Yet when I look at the final render output, the chroma keyed footage appears soft, and there is color saturation loss, and a lot of noise visible. I have tried (Quicktime) Avid Meridian 3_1 and 1-1 compression output, and finally rendered the comp out as a pict sequence, and then rendered that pict sequence back to an Avid quicktime: in each final render the keyed footage looks soft and noisy while the background plate (from a pre-rendered uncompressed movie I made in AE) looks clean and sharp.
Another problem (hence the pict sequence renders) is that After Effects keeps crashing during the render when I am using Keylight. The source quicktimes are quite long: the shortest is about 1:30, and the longest is almost 15:00 (minutes.) At least with a pict sequence, I can pick up the render from the last frame. Is there an optimum file size for the source quicktimes? Am I trying to render files that are simply too big for AE and my computer to manage?
I have looked through the forums but haven’t found any problem exactly matching mine, and was hoping to see if anyone else has had such problems, and what their solution might have been.
Thanks
-
7 Replies
-
Dave:
Thanks for your reply. I tried a couple more test based on your comments. I rendered out a segment of the original clip to a PSD sequence. Then by mistake I rendered out a clip of the chromakey (using no compression) without using lower-field-first. It looks fine. When I rendered it again, exactly as before, except using lower-field-first, it looks blurry. I’ve tried several ways, now: PSD to uncompressed, uncompressed to uncompressed, etc., and it’s only when I used a lower-field-first output that I get the softening issue.
Have others encountered this in AE using field-rendering? I have to use field-rendering, don’t I, when using interlaced footage, to avoid field-order issues?
Thanks
-
Yes, that’s the first thing I do. That’s what’s stumping me now. If I don’t interpret it I get all kinds of problems. We use Beta to record our chromakeys (it’s cleaner than DV) but I don’t have the option with Beta to shoot progressive.
I have to interpret fields, or I get field blending problems. Assigning field order doesn’t seem to be the problem. Rendering with field order, no matter what output choice I make, seems to be my problem.
Thanks for your response.
-
*I rendered out a clip of the chromakey (using no compression) without using lower-field-first. It looks fine.”
ok, here’s what’s up, when you render a betacam out with fields off or a psd, you’re rendering out a poor man’s deinterlace from AE’s built in deinterlacer. That’s why when you reimport it back into AE and try interpreting it with fields on, you get blur. Of coarse you do, you’re trying to deinterlace deinterlaced footage!
The quicktime codec might be giving you trouble. Try a different codec and render that out fields on. Chances are, you will then successfully import it back in and it won’t be blurry. Whenever I have a problem, I render out 10 seconds of a 4:4:4: RGB uncompressed avi. That fixes 99% of problems.
-
Chris:
Thanks for your post.
I’ve tried all your suggestions. I was able to get it to output a clean, uncompressed, unkeyed clip as per your suggestion.
But when I take that clip and run it through Keylight with lower field output, whether to a Quicktime or an image sequence, I get the softening effect. I can get a better looking render when I use no field. It is crisp, but there is still detail loss because I’m missing a field. That is acceptable for this project, which is for the Internet.
But I still want to know why this process, which has worked so well before, no longer works. Also, I’m still having the other problem of AE constantly crashing while I’m rendering: I can’t leave a render queue going overnight, and I have to constantly babysit the render.
Thanks.
-
You might have image sequence settings wrong because flash only supports pre-multiplied and needs alpha channel- rgb+alpha. and there’s quality settings for image outputs like PNG(format options) which has a box for interlaced output for web viewing support.
By storing gamma information in an image, PNG’s can be transfered to mac back to pc whithout color problems, which makes me wonder why more people don’t use this fantastic image sequencer.
If those are correct, then the only other thing is keylight, update it or even try a demo of another keyer.
-
Dave and Chris:
Thanks for both your responses.
Dave: I’ve kind of run out of ideas on what it could be, hence the posts. Shooting hasn’t changed: we shoot component video on Beta to avoid DV compression. We capture in this case in Avid using Meridian uncompressed 1 to 1 codec.
At first I thought it was the latest Avid codec, but then I was having the same problem when I rendered the sequence to the uncompressed None codec in the output dropdowns.
Chris: Flash isn’t at all in the picture. I’m not rendering the chromakeys out as matte channel files, but as comps over the background with audio.
The weirdest thing is, everything looks great in the comp window. Then, the instant I hit render, I see the image go soft.
Again, thanks for the input. I’m going to have to give it a rest and get back to my scheduled tasks.
-
has anyone found a solution for that soft, blurry image problem, ’cause i have it too.
footage looks great in comp window, but as soon as i render it with animation, it is blurred. if i remove keylight, it sharp. i tried different codecs, i searched everywhere but couldn’t find a solution. i already installed the keylight update, but no help.
Reply to this Discussion! Login or Sign Up