-
Strange occurrance using pre-rendered element…
Hi Everybody,
Hoping for help with this one.
I’m making a graphic on my Intel MacPro tower using the beta test version of CS3. The thing is, I’m using a foreground element from an old composition that includes a CC Light Rays effect. So when I render the whole graphic, it crashes. (Keeping in mind I have to run under rosetta to even get the CC effects to show up in the first place.)
However, if I pre-render the layer with the light rays, that seems to work. Here’s where things get weird.
I am rendering the foreground element with the light rays as an lossless quicktime with alpha (using “NONE” as my compression scheme). When look at the quicktime, it looks clean.
When I import it into AE, it looks clean. But when I marry it to the background and render it using the uncompressed 10-bit 4:2:2 codec, in preparation for bringing it into Final Cut, the foreground element has acquired an artifacting that I can only describe as “pixelation”.
I’m racking my brain to try and figure out why — because while I’m rendering the composited shot, it looks clean on the frame by frame render. I use the 10 bit uncompressed codec all the time and have never noticed this pixelation before.
To give a sense of how much pixelation I’m talking about, it is as if I had shrunk the video to two thirds size and blown it back up, instead of inserting a clean, lossless pre-rendered graphic.
Any thoughts?
-
5 Replies
-
Try pre-rendering the CCRays thingy without fields and see how that looks. Work on a short segment for the test.
Cheers
Roland Kahlenberg
https://www.broadcastGEMs.com – Adobe After Effects project files
https://www.myspace.com/rorkrgbspace -
it does sound strange… but not much stranger than using a beta ae under emulation to get an effect that you had to pre-render out of a previous full version of ae 😉
as roland mentioned, it may be a field issue. are you rendering in fields? also, once you pre-render your ray effect, are you still running the powerpc version of the beta ae in rosetta or are you running the native x86 version? and, do you have the latest beta version?
Kevin Camp
Designer – KCPQ, KMYQ & KRCW -
Thanks both — I will check the fields thing tonight. If this news is correct that the full AE 8 is out today, I may not have to worry about the emulation issue! (That is, assuming that the full package of CC effects have been included this time around.)
But in the meantime, thanks for the responses.
-
it sounds like the 3rd party bundled effects are intel-mac friendly… but i haven’t been able to confirm it.
Kevin Camp
Designer – KCPQ, KMYQ & KRCW -
Sadly, the fields setting did not solve the problem. I had been rendering with fields off, so I tried tests both with even first and odd first. Unfortunately, they just made it look worse.
Anyone else have any ideas? I tried rebuilding the effect with all transformations collapsed all the way up through the chain of comps I’d used, but that didn’t seem to be the problem either.
Is it possible that the 10-bit 4:2:2 codec is at fault?
I also tried re-rendering the whole effect without pre-rendering, despite the chance of a crash. And it worked, in terms of not crashing, but didn’t work, in terms of getting rid of the pixellation.
Reply to this Discussion! Login or Sign Up