Chris Chamberlain
Forum Replies Created
-
thank you Walter for your insight, much appreciated.
I didn’t adopt your solution, but would consider it for next time.
For anyone browsing this thread, I was able to render the particles as a separate animation, then bring that back in, and then used a mask effect then worked.
I believe the real reason why particles and its attendant mask, both sourcing within the same layer, cannot be done – may be done to technical insufficiency of the app itself. Perhaps a later version of AE can do this, but I can’t (yet) confirm this.
Warm regards,
Chris
-
appreciate your post Ridley, although I didnt understand the 1.8 figure.
Still the sugg to batch change the resolutions in Photoshop to 132ppi was helpful, and allowed me to complete my animation just fine ! So THANK YOU ! But relevant is the fact that the batch changes must be accompanied *without resampling* (this was just left unchecked if anyone is following this thread).
Still Ive become aware that Maya 2013 does not have the PPI output limitation that AE does, it will handle whatever number you feed it. Autodesk calls this attribute “resolution units”.
Warm regards,
Chris
-
yes is the short answer however – that would imply up-rezzing in PS of the AE-exported files, which will lower overall quality.
Photoshop has this same function “Save for Web….” (ie, outputting to the old standard of 72ppi) but if one simply uses the “Save As” dialogue the pixels per inch attribute will not be affected.
Just for the record, last nite I tried the same PNG export problem on AECC, to no avail, it too unfortunately also de-rez’s the PNG file quality.
When I find a workaround, I will update here…. perhaps Nuke or Motion do not suffer this issue….
Warm regards,
Chris
-
as Ive said, the steps to reproduce the problem mean that 132ppi goes in, and 72ppi comes out.
The actual document dimensions dont bear on this matter….
Warm regards,
Chris