_______________________________________________
Do not post admin requests to the list. They will be ignored.
Pro-apps-dev mailing list (Pro-apps-dev(a)lists.apple.com)
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/pro-apps-dev/site_archiver%40lists.…
This email sent to site_archiver(a)lists.apple.com
Sorry to take so long to get back to you on this. It's pretty busy here right now.
I don't know of a workaround for this problem at this time. I believe that it is fixed in a future release, though I can't say when the fix will be on customers machines. Feel free to file a bug with an example plug-in that shows the problem, and I can verify that what I'm seeing is the same thing you're asking about.
Darrin
On Jun 5, 2012, at 1:11 PM, Stonewall Ballard wrote:
> From what I've read on this list, there is no way to ensure that an effect can get actual (not resampled) pixels from FCPX and know when that's happening. The FxRenderInfo scaleX and scaleY are not 1.0 when a motion effect built into a 1080p template is applied to a clip of a different size in FCPX, even though the input image to the effect may be the actual clip size. Even when the motion template is the same as the clip size, it seems that the input frames are always resampled to square pixels.
>
> I'm using temporalApi getSourceBitmap:withInfo:atTime:, expecting that this would be the most likely to give me the original pixels. It appears that this call produces frames with the same size as the normal input parameter.
>
> When I use a DV clip in a DV motion template, I get input frames of 654x480 and a frame scale of 1, 1 from a 720x480 source clip. There doesn't seem to be any way to tell that the clip has been resampled, or to prevent it from being resampled. Adjusting the FxRenderInfo scaleX for the getSourceBitmap call seems to do nothing.
>
> Any help or insights will be greatly appreciated!
>
> - Stoney
>
> --
> Stonewall Ballard
> stoney(a)sb.org http://stoney.sb.org/
>
>
> _______________________________________________
> Do not post admin requests to the list. They will be ignored.
> Pro-apps-dev mailing list (Pro-apps-dev(a)lists.apple.com)
> Help/Unsubscribe/Update your Subscription:
> https://lists.apple.com/mailman/options/pro-apps-dev/dcardani%40apple.com
>
> This email sent to dcardani(a)apple.com
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Pro-apps-dev mailing list (Pro-apps-dev(a)lists.apple.com)
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/pro-apps-dev/site_archiver%40lists.…
This email sent to site_archiver(a)lists.apple.com
>From what I've read on this list, there is no way to ensure that an effect can get actual (not resampled) pixels from FCPX and know when that's happening. The FxRenderInfo scaleX and scaleY are not 1.0 when a motion effect built into a 1080p template is applied to a clip of a different size in FCPX, even though the input image to the effect may be the actual clip size. Even when the motion template is the same as the clip size, it seems that the input frames are always resampled to square pixels.
I'm using temporalApi getSourceBitmap:withInfo:atTime:, expecting that this would be the most likely to give me the original pixels. It appears that this call produces frames with the same size as the normal input parameter.
When I use a DV clip in a DV motion template, I get input frames of 654x480 and a frame scale of 1, 1 from a 720x480 source clip. There doesn't seem to be any way to tell that the clip has been resampled, or to prevent it from being resampled. Adjusting the FxRenderInfo scaleX for the getSourceBitmap call seems to do nothing.
Any help or insights will be greatly appreciated!
- Stoney
--
Stonewall Ballard
stoney(a)sb.org http://stoney.sb.org/
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Pro-apps-dev mailing list (Pro-apps-dev(a)lists.apple.com)
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/pro-apps-dev/site_archiver%40lists.…
This email sent to site_archiver(a)lists.apple.com