Pixel Aspect on input vs. temporal
Pixel Aspect on input vs. temporal
- Subject: Pixel Aspect on input vs. temporal
- From: Stonewall Ballard <email@hidden>
- Date: Thu, 6 Nov 2008 21:03:42 -0500
In FCP 6.0.4, in a sequence set to a Pixel Aspect Ratio of NTSC-CCIR
601/DV (720x480), and a Frame size of 720x486 (CCIR 602 NTSC 40:27),
the output image info says it has a pixelAspect of 0.444444.
When the input is a 720x486 clip listed as Pixel Aspect NTSC-CCIR 601
in the browser, its imageInfo says it has a pixelAspect of 0.395062.
The same input frame fetched via the temporal API using
getBitmap:layerOffsetX:layerOffsetY:requestInfo:fromParm:atTime:
reports a pixelAspect of 0.444444. At least
getInputBitmap:withInfo:atTime: shows that same frame with a
pixelAspect of 0.395062, the same as the regular input.
Why does
getBitmap:layerOffsetX:layerOffsetY:requestInfo:fromParm:atTime:
produce a different pixelAspect than the other two methods? Is there
any way to tell what the *real* pixel aspect of that frame?
Interestingly, when I set the sequence to use square pixels, all the
pixelAspects are 0.444444.
BTW, 0.444444 is 640/720/2, while I would have expected to see
648/720/2, or 0.45. I don't see where 0.39506 comes from.
Anyone know what's going on here? Is there any way to know what the
*real* PAR of an image param is?
TIA.
- Stoney
--
Stonewall Ballard
email@hidden http://stoney.sb.org/
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Pro-apps-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden