-
Layer has weird ghosting – how to fix?!
-
hey I tried what you said (didn’t know you coudl do that with the option-drag thing – thanks!) but the noise is still there!
-
Just to make things more crazy, I downloaded and looked at your project and the noise didn’t show up for me.
I noticed the noise is transparency in your project, why not put a white solid back there and see if that gets rid of the problem. Also, render out a frame and see if the noise is in the render-perhaps it’s just in the comp window display(have no idea why that would be though).
Johnny Cuevas, Editor
Thinkck.com“I have not failed 700 times. I have succeeded in proving that those 700 ways will not work. When I have eliminated the ways that will not work, I will find the way that will work.”
—THOMAS EDISON on inventing the light bulb. -
i looked at the project, and i can’t explain the problem but i found two ways to get around the issue.
disabling dof for the camera fixed it, but if you need dof for the comp, then i also found enabling 32bpc rendering fixed it too.
i can’t explain why its producing the noise, i haven’t seen that before. i’m curious now, so i’m going to try and recreate the issue in cs4.
Kevin Camp
Senior Designer
KCPQ, KMYQ & KRCW -
interesting…. john, it seems you are on windows.
alison, are you on osx, and if so what version? i’m still on leopard — osx 10.5.8.
Kevin Camp
Senior Designer
KCPQ, KMYQ & KRCW -
Yes, I’m on windows, should have included that in my post. Wish I could help, but it’s a bit difficult when you can’t recreate the problem.
Good luck
Johnny Cuevas, Editor
Thinkck.com“I have not failed 700 times. I have succeeded in proving that those 700 ways will not work. When I have eliminated the ways that will not work, I will find the way that will work.”
—THOMAS EDISON on inventing the light bulb. -
cs4 produces the same issue… as does using much smaller proxy images or images of another file type… the two workarounds i found earlier (disable dof, or enable 32bpc rendering) are the only two i’ve found… i guess a third is to use windows…
you could build your own crude dof using expressions and fast blur on all the layers that you want to respond to dof… i don’t think it would be worth it for this, 32bpc rendering would most likely be faster than setting up expressions that set a blur level based on a given layer’s distance from the camera…
Kevin Camp
Senior Designer
KCPQ, KMYQ & KRCW -
I noticed it when I rendered… and in the whole comp (before I delieted everything) it wasn’t on transparency – it was over a layer of video… although it only shows up when I’m viewing at full res – which is why I didn’t notice before I rendered…
that’s bizzare that it isn’t there for you, though!
-
I’m on windows 7… usually a mac user, but only have PC’s at work 🙁
-
32 bit solved the issue! thanks so much, I knew one of you geniuses would find a solution!
-
Yeah, I have no idea what’s going on there, but Kevin Camp is right – it has something to do with DOF.
Using your problem file, I did find that it went away if you bump the aperature up to around 50.
Don’t know what is going on there, but you should report it to Adobe as a possible bug.
-Kevin
Mac Pro 2 x 3 GHz 6-Core Intel Xeon
32GB Memory
Dual-channel 4Gb Fibre Channel PCI Express card
Dell Display (23″ flat panel)
ATI Radeon HD 5770
AJA Kona LSi SD/HD capture card
Rourke 16 TB
Flanders 2460SOFTWARE
Mac OS X 10.6.5
FCP 7
After Effects CS5
Boris Continuum
Sapphire Plug Ins
All Trapcode Plugs
Zaxwerks Invig
Reply to this Discussion! Login or Sign Up