-
Antialiasing methods are screwing up my comps!
Can somebody explain the following wierdness, which is causing me to absolutely hate Motion at this precise moment?
This is how I want the image to look:
https://www.alphageek.org/antialiasing_normal.png
This is how the image looks when I change the antialiasing method to “Best” (for my final render):
https://www.alphageek.org/antialiasing_best.png
Is there a reason why the booklet images get scaled within their bounding-boxes when I switch the AA to “Best”? It’s pretty friggen irritating…
I’m working in a DV resolution comp. The images of the booklet are 1244×1836 JPEGs.
What’s even wierder is that when I bring the Motion project into my main FCP timeline, it displays the wrong, “scaled” booklets, even if the AA method is set to “normal” in Motion.
What gives?
My system specs:
Motion 2.1.2
FCP 5.1.1 on OSX 10.4.7/Intel
2 GB system RAM (Macbook Pro), 256MB VRAM
Quicktime Pro 7.1.2
All recent Pro Apps updates installed -
1 Reply
-
Are you using 16-bit or 32-bit float rendering? The images look like they’ve been cropped because you’ve run out of VRAM on your graphics card, which could be triggered by any combination of larger image resolution, plus using Best mode, and/or enabling 16 or 32-bit rendering. Do the images need to be that size, are you zooming into them? If not, I would suggest decreasing the resolution of the images in an image editor before using them in Motion.
Reply to this Discussion! Login or Sign Up