July 2011 - Pro-apps-dev - lists.apple.com

Re: Custom parameters with kFxParameterFlag_CUSTOM_UI
by Darrin Cardani 18 Jul '11

18 Jul '11

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.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: http://lists.apple.com/mailman/options/pro-apps-dev/site_archiver%40lists.a… This email sent to site_archiver(a)lists.apple.com

1 0

Re: Wrapping FxPlugs in .moef
by Darrin Cardani 18 Jul '11

18 Jul '11

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com On Jul 17, 2011, at 1:12 AM, Martin Baker wrote: > We're having some roadblock issues with wrapping a custom FxPlug in a .moef and using in FCPX. > > 1. FxRenderInfo.frame returns the frame number relative to 29.97fps (regardless of the FPS of the .moef). e.g. frame 4 on a 25fps FCPX timeline is shown as frame 4.8 within the FxPlug. Using a .moef with different fps, seems to not make any difference so does assume .moefs are 29.97fps? It's not assuming anything. If you created the Final Cut Effect at 29.97, your plug-in will get information based on a 29.97 timeline, regardless of the timing in Final Cut Pro. You can think of it as being similar to how your effect renders when the user turns on Motion Blur in Motion. In that case, you get asked to render 8 times per frame (by default - more or less depending how the user set the Motion Blur), each time with a fractional frame value. > 2. The returned durationForEffect value is fixed at the duration of the .moef, regardless of the duration of the clip on the FCPX timeline. This makes it impossible to backtime FxPlug animation from the end of the clip. So a 300 frame .moef will always show up in FCPX as 300 frames duration. Correct. Your effect is not applied to the footage in FCP. It is applied to the drop zone (effect source) in Motion. > 3. hostIsFCP returns false in FCPX. > > I'm presuming all this is happening because the FxPlug has no knowledge of it's top host (FCPX), when wrapped in a .moef. Are there any workarounds? Yes that's how it works now. We're debating whether we want to change this or not. If you think you should be able to work around it, you can always ask the OS for the bundle ID of the main bundle of the currently running app. Darrin -- Darrin Cardani 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: http://lists.apple.com/mailman/options/pro-apps-dev/site_archiver%40lists.a… This email sent to site_archiver(a)lists.apple.com

1 0

Re: Custom parameters with kFxParameterFlag_CUSTOM_UI
by Peter T 18 Jul '11

18 Jul '11

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=B0yhnSV8YLtVl1j1w/u9BJoDDOhCfNSnLssymjAikpY=; b=ImA6etutPpKBStuDIVfxAfomLAysOef7SyLVv2NhfCWGT5HcYPJF4p6C0Nzu5ir8XG mX2xajn/pOhO2zOZHUx+1BLkF1mt0RH/xdnZqSwY0l7v695jOYQwurIrZ6QvYS2NuRLU dfbZMxRZWYLlcFPcQ+20+fwbJD77piNLjRYjU= _______________________________________________ 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: http://lists.apple.com/mailman/options/pro-apps-dev/site_archiver%40lists.a… This email sent to site_archiver(a)lists.apple.com

1 0

Re: Wrapping FxPlugs in .moef
by Peter T 18 Jul '11

18 Jul '11

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=g8yve8zD4ZB65Y3v+bvYZfBz2gsY4Ky68UKHtlQUnrQ=; b=pxaJtq0syL3Rmue7RVR752LyVRXsyBTh8+mhCrNizzNHHowMrICLRXdOuQOoxeKsIH 7IbQHQZg8/HwmmGDhFmkP14hHWWZtVHgnbXdWQHp9M/kF+mCm9duLVn4cSHyt5di0Hfo Qedq+H7POugjdubDRhwRvBxSijTcYXwbuxgFk= _______________________________________________ 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: http://lists.apple.com/mailman/options/pro-apps-dev/site_archiver%40lists.a… This email sent to site_archiver(a)lists.apple.com

1 0

Wrapping FxPlugs in .moef
by Martin Baker 17 Jul '11

17 Jul '11

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=sender:from:content-type:content-transfer-encoding:subject:date :message-id:to:mime-version:x-mailer; bh=cqBDLwvCr2uosfqz0B2dFr4vjz33jrJTza4GyUDddP4=; b=kZsvgQ0JzQsNiezkkkyFVafMnNZGsneqMl7yhT2OZSf5v1jUovD4s8BGEsNRuhMYoh sJBuY54PpggORP/emMLv6LbWiPQNShL2uoPExg6DwNxMAaYF0Ench/ruBdjroSutTNsD 2BQOxPeewyJLJ/4jxb8iz/2Rj+HXsKJEhvkXc= We're having some roadblock issues with wrapping a custom FxPlug in a .moef and using in FCPX. 1. FxRenderInfo.frame returns the frame number relative to 29.97fps (regardless of the FPS of the .moef). e.g. frame 4 on a 25fps FCPX timeline is shown as frame 4.8 within the FxPlug. Using a .moef with different fps, seems to not make any difference so does assume .moefs are 29.97fps? 2. The returned durationForEffect value is fixed at the duration of the .moef, regardless of the duration of the clip on the FCPX timeline. This makes it impossible to backtime FxPlug animation from the end of the clip. So a 300 frame .moef will always show up in FCPX as 300 frames duration. 3. hostIsFCP returns false in FCPX. I'm presuming all this is happening because the FxPlug has no knowledge of it's top host (FCPX), when wrapped in a .moef. Are there any workarounds? thanks Martin Baker www.digital-heaven.co.uk www.twitter.com/digitalheaven www.videospaceonline.com www.finalcutters.com ------------------------------------------------------ Digital Heaven Ltd is registered in England and Wales Company registration number: 3628396 Registered address: 55 Lynwood Drive, Worcester Park, Surrey KT4 7AE VAT registration number: GB 736 0989 03 _______________________________________________ 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: http://lists.apple.com/mailman/options/pro-apps-dev/site_archiver%40lists.a… This email sent to site_archiver(a)lists.apple.com

1 0

Re: Custom parameter values in FCP X
by Darrin Cardani 15 Jul '11

15 Jul '11

site_archiver(a)lists.apple.com Delivered-To: Pro-apps-dev(a)lists.apple.com No, it's not intentional, it's a bug. Please file it. I don't know of any workaround at the moment. Darrin On Jul 15, 2011, at 12:16 PM, Eberhard Ammelt wrote: > Hello Darrin, > > I'm trying to get around with the restrictions of custom parameters in FCP X. > It seems that setting and getting parameter values works correctly but custom parameter values are not saved with the project. > Is this intentional because custom parameters are not supported in FCP X? > Is there a workaround? > > Regards, > Eberhard > _______________________________________________ > 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: > http://lists.apple.com/mailman/options/pro-apps-dev/dcardani%40apple.com > > This email sent to dcardani(a)apple.com -- Darrin Cardani 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: http://lists.apple.com/mailman/options/pro-apps-dev/site_archiver%40lists.a… This email sent to site_archiver(a)lists.apple.com

1 0

Custom parameter values in FCP X
by Eberhard Ammelt 15 Jul '11

15 Jul '11

site_archiver(a)lists.apple.com Delivered-To: Pro-apps-dev(a)lists.apple.com Hello Darrin, I'm trying to get around with the restrictions of custom parameters in FCP X. It seems that setting and getting parameter values works correctly but custom parameter values are not saved with the project. Is this intentional because custom parameters are not supported in FCP X? Is there a workaround? Regards, Eberhard _______________________________________________ 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: http://lists.apple.com/mailman/options/pro-apps-dev/site_archiver%40lists.a… This email sent to site_archiver(a)lists.apple.com

1 0

Re: Final Cut Effect Source layer is 2px smaller than frame size
by Darrin Cardani 15 Jul '11

15 Jul '11

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com I don't think tweaking the Effect Source size will cause any problems. But feel free to file a bug about this. Darrin On Jul 15, 2011, at 4:26 AM, Martin Baker wrote: > We're in the process of packaging up our first FxPlug into a Final Cut Effect and seeing a problem in Motion 5. > > When the effect is applied in FCPX, there is a gap at the top and right. By enabling and disabling the effect, it can be seen that the effect is resizing the source image. This becomes particularly noticeable when running at proxy resolution and where the clip with the effect is over a background clip. > > Looking at the .moef file, the effect layer item is not filling the frame size and has a 2px gap at the top and right for a 1920 x1080 project. Size is set to the default 100% and position is 0,0. > > So I'm not sure whether we should tweak the Effect Source size to correct, or whether this will create problems later... > > thanks > > Martin Baker > www.digital-heaven.co.uk > www.twitter.com/digitalheaven > www.videospaceonline.com > www.finalcutters.com > ------------------------------------------------------ > Digital Heaven Ltd is registered in England and Wales > Company registration number: 3628396 > Registered address: 55 Lynwood Drive, Worcester Park, Surrey KT4 7AE > VAT registration number: GB 736 0989 03 > > _______________________________________________ > 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: > http://lists.apple.com/mailman/options/pro-apps-dev/dcardani%40apple.com > > This email sent to dcardani(a)apple.com -- Darrin Cardani 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: http://lists.apple.com/mailman/options/pro-apps-dev/site_archiver%40lists.a… This email sent to site_archiver(a)lists.apple.com

1 0

Final Cut Effect Source layer is 2px smaller than frame size
by Martin Baker 15 Jul '11

15 Jul '11

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=sender:from:content-type:content-transfer-encoding:subject:date :message-id:to:mime-version:x-mailer; bh=4+2hBu9Y7lzhhEDxpKjOW1PhK2cxSqvJzizLg3TYHsE=; b=h042byvGB+4+dCBvKcNNC8eiC9q6fG+z+4jNkkgjIFI+YX53BBJekq7sn2KNLVjT7X 0jxxfRv/QXiWzSuUeCbb71x7h2+HHWY7QKwUfOd37TJteRPyhf6xS3YrgJtDuIDBKvMI H+oYK8MZrcL2IkYckWOvoFam4SuX6D0m0iouQ= We're in the process of packaging up our first FxPlug into a Final Cut Effect and seeing a problem in Motion 5. When the effect is applied in FCPX, there is a gap at the top and right. By enabling and disabling the effect, it can be seen that the effect is resizing the source image. This becomes particularly noticeable when running at proxy resolution and where the clip with the effect is over a background clip. Looking at the .moef file, the effect layer item is not filling the frame size and has a 2px gap at the top and right for a 1920 x1080 project. Size is set to the default 100% and position is 0,0. So I'm not sure whether we should tweak the Effect Source size to correct, or whether this will create problems later... thanks Martin Baker www.digital-heaven.co.uk www.twitter.com/digitalheaven www.videospaceonline.com www.finalcutters.com ------------------------------------------------------ Digital Heaven Ltd is registered in England and Wales Company registration number: 3628396 Registered address: 55 Lynwood Drive, Worcester Park, Surrey KT4 7AE VAT registration number: GB 736 0989 03 _______________________________________________ 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: http://lists.apple.com/mailman/options/pro-apps-dev/site_archiver%40lists.a… This email sent to site_archiver(a)lists.apple.com

1 0

Re: FxPlug/Final Cut Pro X Rendering issue (32 vs. 16 bit Float textures).
by Darrin Cardani 13 Jul '11

13 Jul '11

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com Michael, This definitely sounds like a bug. Can you please file a bug with as much information as you have? Thanks, Darrin On Jul 13, 2011, at 12:49 AM, Michael Jonsson wrote: > Hi list, > > It appears there are some inconsistencies in respect to the data that > is fed down to plugins under various circumstances when called from > Final Cut Pro X. This concerns only GPU rendering. > > I see two scenarios when my plugin is called from Final Cut: > > 1. Expected behavior. > > Happens prior to rendering, say while I change parameters in my plugin > UI and if I export when NO pre-rendered data is available (say if > flush optimized media and turn background rendering OFF and export to > H.264) - In this case renderOutput:withInput:withInfo: gets called > with the following: > > FxTexture input depth = 16 > FxTexture output depth = 16 > FxRenderInfo.depth = kFxDepth_FLOAT16 > > Binding the input texture and doing a glGetTexLevelParameteriv(… > GL_TEXTURE_INTERNAL_FORMAT…) reveals that the Internal format of the > input texture handed down to renderOutput: is GL_RGBA32F_ARB. > > In my fragment shader I see the data that I expect; that is, > super-white values over 1.0 etc.. In short, everything behaves as > expected. > > Motion 5 everything behaves similar to above expected behavior both > during playback/editing and exporting. > > > > 2. Unexpected behavior. > > This is where things gets strange… This happens (only?) when the > plugin is called during background rendering. Here > renderOutput:withInput:withInfo: gets called with the following: > > FxTexture input depth = 32 > FxTexture output depth = 32 > FxRenderInfo.depth = kFxDepth_FLOAT32 > > However, glGetTexLevelParameteriv(… GL_TEXTURE_INTERNAL_FORMAT…) > reveals that the internal format of the texture is GL_RGBA8_EXT... > (8bit pr channel...) > > In addition, in my fragment shader I see mostly the same data as in > the 1st case but the over-range > 1.0 (i.e. super-white etc.) data is > being truncated/clamped to 1.0… which is not the way its supposed to > work.. I hope! :-) > > Any insights or workaround for this problem is highly appreciated. If > not, I hope its something that can be addressed in an upcoming update. > > Cheers, > Michael > Rig: MacBookPro8,2 / Radeon HD 6750M / MacOSX 10.6.8. > _______________________________________________ > 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: > http://lists.apple.com/mailman/options/pro-apps-dev/dcardani%40apple.com > > This email sent to dcardani(a)apple.com -- Darrin Cardani 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: http://lists.apple.com/mailman/options/pro-apps-dev/site_archiver%40lists.a… This email sent to site_archiver(a)lists.apple.com

1 0