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

Re: FxPlug 2 Answers, etc.
by Darrin Cardani 24 Jun '11

24 Jun '11

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com Paul pointed out that since the help is online, I can now just link to it! Here's a link describing how to deal with templates: <http://help.apple.com/motion/mac/5.0/en/motion/usermanual/#chapter=11%26sec…> and here's the docs for FxPlug 2.0: <http://Developer.apple.com/library/mac/documentation/FinalCutProFinalCutExp…> Darrin On Jun 24, 2011, at 12:40 PM, Darrin Cardani wrote: > Patrick, > > Your installer should put the Final Cut Effects into either: > > ~/Movies/Motion Templates.localized > > or > > /Library/Application Support/Final Cut Pro/Templates.localized > > I'll try to write up the 32/64-bit stuff today. > > Darrin > > On Jun 24, 2011, at 12:35 PM, Patrick Sheffield wrote: > >> So - are the install procedures for the Motion project wrappers for FCX to access FxPlugs documented somewhere? >> >> i.e. once I've got working 64 bit versions (still wanna know how to do universal versions), I've still got to interface it to FCX. What should my installer do? >> >> Patrick Sheffield >> Sheffield Softworks >> >> On Jun 24, 2011, at 12:30 PM, Darrin Cardani wrote: >> >>> >>> On Jun 24, 2011, at 12:09 PM, Bob Currier wrote: >>> >>>>> 5) I'm not aware of any problems getting images in different formats. >>>>> You will never again receive images in YUV format, though. >>>> >>>> Darrin: >>>> >>>> Does that imply no over-brights except in float? Which would further >>>> imply that previews won't match final renders because previews never >>>> seem to get float pixels? >>> >>> One thing I forgot to mention is that all processing is now in float. You should never again receive an 8-bit per channel image. They'll all be either 16-bit textures or 32-bit bitmaps. >>> >>> 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/psheffield%40earthlink.… >>> >>> This email sent to psheffield(a)earthlink.net >> > > -- > 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/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

FxPlug 2: createTexture and createPBuffer
by Garrick Meeker 24 Jun '11

24 Jun '11

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com Are these documented in the missing docs? Specifically, I'd like to know if createTexture's 'pixels' argument can be NULL (when the image isn't coming from memory), and what does createPBuffer do? Obviously it's a GLuint not a CGLPBufferObj, but is this a framebuffer, renderbuffer, PBO? _______________________________________________ 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 2 Answers, etc.
by Bob Currier 24 Jun '11

24 Jun '11

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com OK, that's a bit of good news! Thanks. ----- Bob Currier rcurrier(a)synthetic-ap.com Synthetic Aperture voice: +1 949 493-3444 Helping Make Your Work Look Its Best fax: +1 949 203-2108 web: www.synthetic-ap.com On Fri, Jun 24, 2011 12:30 PM, Darrin Cardani <dcardani(a)apple.com> wrote: > >On Jun 24, 2011, at 12:09 PM, Bob Currier wrote: > >>> 5) I'm not aware of any problems getting images in different formats. >>> You will never again receive images in YUV format, though. >> >> Darrin: >> >> Does that imply no over-brights except in float? Which would further >> imply that previews won't match final renders because previews never >> seem to get float pixels? > >One thing I forgot to mention is that all processing is now in float. >You should never again receive an 8-bit per channel image. They'll all >be either 16-bit textures or 32-bit bitmaps. > >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: FxPlug 2 Answers, etc.
by Darrin Cardani 24 Jun '11

24 Jun '11

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com Patrick, Your installer should put the Final Cut Effects into either: ~/Movies/Motion Templates.localized or /Library/Application Support/Final Cut Pro/Templates.localized I'll try to write up the 32/64-bit stuff today. Darrin On Jun 24, 2011, at 12:35 PM, Patrick Sheffield wrote: > So - are the install procedures for the Motion project wrappers for FCX to access FxPlugs documented somewhere? > > i.e. once I've got working 64 bit versions (still wanna know how to do universal versions), I've still got to interface it to FCX. What should my installer do? > > Patrick Sheffield > Sheffield Softworks > > On Jun 24, 2011, at 12:30 PM, Darrin Cardani wrote: > >> >> On Jun 24, 2011, at 12:09 PM, Bob Currier wrote: >> >>>> 5) I'm not aware of any problems getting images in different formats. >>>> You will never again receive images in YUV format, though. >>> >>> Darrin: >>> >>> Does that imply no over-brights except in float? Which would further >>> imply that previews won't match final renders because previews never >>> seem to get float pixels? >> >> One thing I forgot to mention is that all processing is now in float. You should never again receive an 8-bit per channel image. They'll all be either 16-bit textures or 32-bit bitmaps. >> >> 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/psheffield%40earthlink.… >> >> This email sent to psheffield(a)earthlink.net > -- 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: FxPlug 2 Answers, etc.
by Patrick Sheffield 24 Jun '11

24 Jun '11

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net; b=N8qPNrTXpXXeUWsW2WOPgTJMwvHur7Z6a9Oohk1aQ6T1PkHK8MVPS+VFSBVVC57u; h=Received:Subject:Mime-Version:Content-Type:From:In-Reply-To:Date:Cc:Content-Transfer-Encoding:Message-Id:References:To:X-Mailer:X-ELNK-Trace:X-Originating-IP; So - are the install procedures for the Motion project wrappers for FCX to access FxPlugs documented somewhere? i.e. once I've got working 64 bit versions (still wanna know how to do universal versions), I've still got to interface it to FCX. What should my installer do? Patrick Sheffield Sheffield Softworks On Jun 24, 2011, at 12:30 PM, Darrin Cardani wrote: > > On Jun 24, 2011, at 12:09 PM, Bob Currier wrote: > >>> 5) I'm not aware of any problems getting images in different formats. >>> You will never again receive images in YUV format, though. >> >> Darrin: >> >> Does that imply no over-brights except in float? Which would further >> imply that previews won't match final renders because previews never >> seem to get float pixels? > > One thing I forgot to mention is that all processing is now in float. You should never again receive an 8-bit per channel image. They'll all be either 16-bit textures or 32-bit bitmaps. > > 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/psheffield%40earthlink.… > > This email sent to psheffield(a)earthlink.net _______________________________________________ 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 2 Answers, etc.
by Darrin Cardani 24 Jun '11

24 Jun '11

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com On Jun 24, 2011, at 12:09 PM, Bob Currier wrote: >> 5) I'm not aware of any problems getting images in different formats. >> You will never again receive images in YUV format, though. > > Darrin: > > Does that imply no over-brights except in float? Which would further > imply that previews won't match final renders because previews never > seem to get float pixels? One thing I forgot to mention is that all processing is now in float. You should never again receive an 8-bit per channel image. They'll all be either 16-bit textures or 32-bit bitmaps. 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: FxPlug 2 Answers, etc.
by Bob Currier 24 Jun '11

24 Jun '11

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com >5) I'm not aware of any problems getting images in different formats. >You will never again receive images in YUV format, though. Darrin: Does that imply no over-brights except in float? Which would further imply that previews won't match final renders because previews never seem to get float pixels? ----- Bob Currier rcurrier(a)synthetic-ap.com Synthetic Aperture voice: +1 949 493-3444 Helping Make Your Work Look Its Best fax: +1 949 203-2108 web: www.synthetic-ap.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: FxPlug 2 Answers, etc.
by Darrin Cardani 24 Jun '11

24 Jun '11

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com Pete, 1) As I mentioned to Pierre, fields aren't labeled properly in FCPX. Everything ends up getting labeled as progressive. Yeah, I know. It was found in testing, but too late to fix. I'm pushing to get the fix in the soonest possible update. FWIW, it works properly in Motion. 2) I'm not aware of any problems accessing parameters over time. Were there problems before? If you have some specific use-cases, I could check them, if they're not too complicated. 3) I'm not sure what you mean by "properly supported." But yes, fields are sent to the plug-ins separately. They are full-height. I will have to check to see whether they are line doubled or interpolated. 4) A quick test shows everything coming in at the same scale. When you have the canvas at 50%, temporal images and image well images appear to be at 50% also. 5) I'm not aware of any problems getting images in different formats. You will never again receive images in YUV format, though. 6) Yes, checkboxes and popups are animated. They use step interpolation. Hope that helps! Darrin On Jun 23, 2011, at 7:58 PM, Peter Litwinowicz wrote: > Just because API support is there doesn't mean all features work (as we > have seen before, right? :-) ). > Any known problems with working with FCP/Motion and plugins. Specifically: > 1) Accessing images over time > 2) accessing other params over time > 3) input source or output images with interlacing properly supported? If > so are images at half height or full height? And, if at full height, are > the inbetween scanlines doubled or interpolated? > 4) images all at same size for checkout? (previously, in FCP, if you > checked out an image when working at 50% resolution, the main input would > be at 50% resolution and all other clipwell inputs were at 100%) > 5) problems with getting images in formats: RGBA? YUVA? > 6) checkboxes, menus are now animated? (that's a UI question not an API > question). If so, do animated params of these types keep their previous > values before seeing a new keyframe? (that is, these types are animted as > step curves and not as linearly interpolated floating values)? > > Of course we have a vested interest in the answers to these questions... > Pete > > > On 6/23/11 9:23 AM, "Darrin Cardani" <dcardani(a)apple.com> wrote: > >> Hey all, >> I'm back in the office today. I'm going to take some time and read over >> all your questions and get you some answers today and hopefully help >> everyone find solutions that will work for you, your customers, and us. >> It's going to take me some time to get caught up, so please be patient >> with me (and everyone else who's helping me answer questions). >> >> Thanks, >> 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/pete%40revisionfx.com >> >> This email sent to pete(a)revisionfx.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/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

Re: Making FxPlugs Work in FCPX
by Peter T 24 Jun '11

24 Jun '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=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=GtXIo7Qxn/dNmIiliBs1KSSTsH9NdghAffjm2koPLIg=; b=u60ND3049W1nHH2A1xibUW/aEYnfqwpoRvJUJGFTvzhUX1GoebZctXRpN+xo146W+f tXSal5bP5fl27ipEHt0DopXCDLbWEZNPgYCoAiqy3KLxmvATtagBiOtbK3PjmUrKEhSI 5U8hWj2mvbAU9lmMwS5Qb3YCYfWVGoDwefJUo= Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=Yk9Tbxo27XGyd5xoFA16uBMV+HV8AKvH4MJ0zsb/NknGpkWUrBWKuRNv5YK8hMoqXe AH7xcRX4tii6C5pa1bWFm4P65+F5KXFC7GWi8w0k+rVBs/42EMBb5H+oiAQXg9ncBmaa mMaM9KCTcEp74tyb15o/63JfIFp3gCkXvokYo= _______________________________________________ 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: What's new in FxPlug 2.0
by Darrin Cardani 24 Jun '11

24 Jun '11

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com Pierre, Here are the issues that I'm aware of: 1) Apparently the new docs didn't make it into the SDK that we posted. I'll see about getting them to you on this list. 2) One of the new OSC methods returns an incorrect matrix when applied to text in Motion. This is minor, as I don't think anyone's using OSCs in any currently shipping product. (Are they?) I already have a fix for this ready for a future update. 3) This one will be a huge pain for you and Pete: We currently don't properly label fields correctly when running inside Final Cut Pro X. I have a fix for this one too. In the meantime, I'm exploring the possibility that you may be able to figure out the current field by getting the pixel transform matrix and examining the x and y translation. It's a hack, but may be a workable solution in the short term. 4) Some issues with examples and templates, like the one Martin mentioned yesterday. Darrin On Jun 23, 2011, at 4:24 PM, Pierre Jasmin wrote: > > > Thanks, > > Is there a list of already known issues? > > Like does addImageReferenceWithName (more then an input) maps to the Motion Templates with FCP? > (Haven't launch FCPX yet so I am not even clear yet what it means in FCPX now) > > Pierre > > > On 6/23/2011 2:18 PM, Darrin Cardani wrote: >> So, amid all the chaos of the new release, I don't think we've posted a list of what's new in FxPlug 2.0. So I'm going to highlight a few things that I think will be useful to developers to know. Later today, I'll post about building in 64-bit and backward compatibility. >> >> What's new: >> >> 1) Keyframe-able checkboxes and popup menus >> >> 2) New APIs: In particular APIs for keyframes, lights, dynamically updating parameters (including adding and removing them at any time), threading, undo, and bezier paths >> >> 3) OSCs now work in Final Cut as well as Motion, and you can now figure out pixel coordinates within your OSCs so you aren't limited to values that are percentages of the width and height >> >> 4) Improvements to existing APIs - cleaned up FxImage and subclasses to clarify which things are mutable and which aren't, fixed various bugs in many APIs, custom parameters are now interpolatable, point parameters are now relative to input image instead of output image >> >> 5) Improved documentation - clarified points that developers said were confusing, added some versioning information to make it easier to figure out when things were added to the API >> >> Let me know if you have specific questions about any of the above items. >> >> Thanks! >> 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/jasmin%40revisionfx.com >> >> This email sent to jasmin(a)revisionfx.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