Jeremy Allen
Forum Replies Created
-
Jeremy Allen
March 24, 2011 at 9:58 pm in reply to: continuously rasterized layers in a precomp still coming up softOK, that definitely looks like low quality / aliasing..
As Michael said earlier, you will need to Collapse Transformations on the comp. If that kills the 3D-ness of the comp, make sure it is a 3D layer, and then make sure any layers inside that comp are also 3D and have collapse transformations checked.
Let me know if you still have problems..
———————————————
8core MacPro, 3.0 GHZ, 10GB RAM, OSX 10.5.8C4D 11.5
AE CS5
FCP 7.0.3 -
Jeremy Allen
March 24, 2011 at 9:12 pm in reply to: continuously rasterized layers in a precomp still coming up softThe top screen doesn’t really look perfectly crisp to me.. And the softness looks more like DoF blur than low quality. With DoF enabled and a focus distance of 2666, you can’t expect it to be crisp when you are that close to it, unless you have keyframed the focus distance to match the distance between the camera and the word.
So the obvious question, does it look better when you disable DoF, or move the focus distance closer to the word?
———————————————
8core MacPro, 3.0 GHZ, 10GB RAM, OSX 10.5.8C4D 11.5
AE CS5
FCP 7.0.3 -
Jeremy Allen
March 24, 2011 at 5:36 pm in reply to: continuously rasterized layers in a precomp still coming up softBecause you say “out of focus”, is “Depth of Field” enabled on the camera? Double-click the camera in the comp layers to see its settings..
———————————————
8core MacPro, 3.0 GHZ, 10GB RAM, OSX 10.5.8C4D 11.5
AE CS5
FCP 7.0.3 -
Maybe Redgiant’s Echospace plug-in?
Or maybe precomp an icon shrinking, repeat and offset in time?
———————————————
8core MacPro, 3.0 GHZ, 10GB RAM, OSX 10.5.8C4D 11.5
AE CS5
FCP 7.0.3 -
Funny, that tutorial is pretty much exactly what we’re looking at here 🙂
But I think we’re gonna need to see more of that footage to make a proper analysis 😉
———————————————
8core MacPro, 3.0 GHZ, 10GB RAM, OSX 10.5.8C4D 11.5
AE CS5
FCP 7.0.3 -
Jeremy Allen
February 28, 2011 at 7:01 pm in reply to: macro shots, shallow DOF, canon 5D and compositingLike you said, shooting macro will produce that shallow DoF, but you can try to minimize it by throwing as much light on it as possible so you can close the aperture down. Maybe that will help some..
———————————————
8core MacPro, 3.0 GHZ, 10GB RAM, OSX 10.5.8C4D 11.5
AE CS5
FCP 7.0.3 -
Dave, it’s pretty obvious he wants the text to look like it’s being pulled by a truck.. 😉
———————————————
8core MacPro, 3.0 GHZ, 10GB RAM, OSX 10.5.8C4D 11.5
AE CS5
FCP 7.0.3 -
Sincere thanks for your time Walter, but I’m having some issues with your suggestion..
I made a test project, placed the transition in a bin in the project browser with the related transition footage and alpha mattes and saved it. Then I moved the project and footage to my laptop. Upon opening the project, I get the missing footage dialog. After reconnecting the footage, I try to use the transition but the footage is also missing from the transition. So then I have to drag the footage and alpha mattes back into the transition, essentially recreating each one.
Have you been able to share a custom transition without the recipient having to rebuild each transition? Please let me know if I’m doing something wrong..
Thanks again!
———————————————
8core MacPro, 3.0 GHZ, 10GB RAM, OSX 10.5.8C4D 11.5
AE CS5
FCP 7.0.3 -
Oh and also, yes, I’m using the render queue.
Thanks again for your time and advice!
———————————————
8core MacPro, 3.0 GHZ, 10GB RAM, OSX 10.5.8C4D 11.5
AE CS5
FCP 7.0.3 -
Thanks for the replies..
Todd: I had not installed the update, but the problem remains after I did install it per your suggestion.
If I turn off the multi-cpu rendering, everything works just fine. With multi-cpu’s rendering, it still does exactly what I described before.
As a test, I rendered a really simple comp with some particles. It literally took 6 seconds without multi-cpu, and about 9 minutes with multi-cpu on.
I also noticed sometimes I get a “unable to connect to background processes” when doing a ram preview. I hit “0” on the numberpad and AE renders the preview but it never plays and I see that message in the Ram preview controls area. If I hit “0” again it will play the rendered frames as normal. Really strange.
Cory: For this project I’m rendering mostly AE generated graphics and effects. Some light particles but nothing too complicated really..
———————————————
8core MacPro, 3.0 GHZ, 10GB RAM, OSX 10.5.8C4D 11.5
AE CS5
FCP 7.0.3