-
Motion Blur on Precomped Illustrator Art
Hello,
Just upgraded to AE CS3 from 6.5. I’m running on an Intel Mac 10.4.11, AE 8.0.1.8.
I’ve noticed that if I import vector art from Illustrator as a comp, enable continuously rasterize and motion blur for the layers in that comp, and then precomp this layer, with collapse transformations enabled in the new comp, motion blur doesn’t seem to work properly. Instead of getting a blur, I get two ghosted frames. This is both with Fast Preview set to off and in Adaptive Resolution. If I enable OpenGL, it displays with motion blur (albeit with a fair amount of banding), but I don’t want to use OpenGL for my final renders.
I opened up 6.5 and I didn’t have this problem there, it properly rendered with motion blur. I skipped 7, so not sure what that result would be.
Here are some sample renders of a test frame:
CS 3: https://www.davidheidelberger.com/ae/test_cs3.jpg
6.5: https://www.davidheidelberger.com/ae/test_65.jpgI’ve also noticed that if I take an Illustrator layer and just scale it up in a comp with continuously rasterize and motion blur enabled, that works properly.
Is there some step or setting that I’m missing or has CS 3 broken this kind of motion blur.
Thanks,
– David -
4 Replies
-
try going to the advanced tab in composition settings and increase the number of samples for motion blur
-
Does it blur properly if collapse transformations is turned off for the comp?
-
Thanks for the suggestions. I set Samples Per Frame as high as it would go to 64 and Adaptive Sample Limit to its max, 128. No change.
Unchecking Collapse Transformations does introduce the proper motion blur, but obviously loses the benefits of vector-based scalability.
Finally, I think I may have found a solution, although I don’t know why it works, and I’m not sure if it would have an adverse effect on certain projects. I set all my layers in my precomp to 3D layers and that made the motion blur work properly. I’m not sure what, if any, problems this could cause in a project where the nested comp is placed in a 3D environment, but at least for 2D projects, this is a workaround.
Is anyone else able to duplicate this problem or does it work fine for you?
– David
-
All I can say is be sure to read the release notes. Lots of things changed.
bogiesan
This is my standard sigfile so do not take it personally: “For crying out loud, read the freakin’ manual.”
Reply to this Discussion! Login or Sign Up