-
non square pixel issues with graphics
Ok, I’m working on an HD project and am using AE 6.5 Pro.
The footage was shot on a Panasonic VariCam @ 23.976 fps and @ 29.97
both are Non-Square (1.33:1) pixels 1280 x 720 DVCPRO HD 720p60
Seems like the panasonic shoots rectangular wide pixels and then Final Cut or other programs recognize that and squish it down a bit and make the pixels square in the end.
problem is After Effects seems ok with importing and expoting the footage as is, BUT i can’t seem to create non-square graphics for this footage. I’ve either had to put the footage into a Square Pixel Comp and scale down the footage width 25% and work on top of that or work by scaling up my square pixel graphics to match the non square comp.
What do you guys do when you work in HD with Non-Square footage? Has anyone run into this problem?
I’m also using Synth Eyes to track some of the shots and am having trouble with the non square pixels in that too!
Please Help!
-justin!
-
3 Replies
-
HI there,
I’ve found the easiest thing to do is to set the interpretation in AE to see the footage as square 1280×720 and go from there. I’ve tried to modify the interpretation txt file to do this but mostly have to tweak the CMD-F footage interpretation within AE and work square from then on.
I find this particular pixel aspect system unusual. It’s 960×720 with a 1.33 ratio out of FCP, but no matter what AE seems to recognise that it is 1280×720. If the interpretation rules looked at it and called it 960×720 with 1.33 aspect then it would fit straight into a square 1280 comp.
The real thing in AE I guess is consistency. If you are not combining graphics then AE’s native interpretation would be fine, but I think working square is a lot easier. I’ve asked around and am waiting fro some feedback as to whether there are any issues with using square pixels.
-
Ah, I think I cracked it.
try putting :
# Varicam exported from FCP is 960×720
1280, 720, *, *, * = 100/100/”Varicam”, *, *, *at the bottom of the interpretation rules.txt file (mac, there is a similar file for PC in the app folder)
This forces the square interpretation which would save some time.
thanks to Stu Maschwitz for this, orphanage AE guru and creator of eLin. https://prolost.blogspot.com/
-
THANK YOU!!!! that worked perfectly! Adobe should be notified about this- and just put that in with the standard interpretation txt file.
thanks again!
-justin!
Reply to this Discussion! Login or Sign Up