October 2010 - Pro-apps-dev

RE: What problems do you run into when writing plug-ins?
by Bret Battey 20 Oct '10

20 Oct '10

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com Thread-index: Actwd3VzgH8PmEM/RUOcyZaAqlwuxwAANBFG Thread-topic: What problems do you run into when writing plug-ins? _______________________________________________ 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 problems do you run into when writing plug-ins?
by Darrin Cardani 20 Oct '10

20 Oct '10

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com On Oct 18, 2010, at 10:11 PM, Brian Gardner wrote: > Certainly, Image Parameters have been troublesome. > Especially, getting frames synced from timeline to > matching frames in Image parameters. > > Trying to keep them in sync through user edits > on the Timeline was very troublesome. > > I wrote a bunch of stereoscopic FxPlugs a while back. > I eventually got them working as well as the > API would allow. Some of the Dev problems were > documentation that could be misinterpreted, > which could have been disambiguated better > if there were examples to clarify. Just so you know, you can file bugs against our documentation specifying what's unclear. And of course, posting a message here saying what types of code examples you'd like to see would give me an idea of how to spend the little time I have to write examples. So let me know what needs to be clarified, and hopefully I can clarify it either in documentation or code. > Of course, eventually, after figuring it all out, > I realized that some necessary functionally > was just not in the API at all. These were not just > stereoscopic related, but missing functionality > for image parameters in general. These sound like enhancement requests. We don't get to them as quickly as I'd like, but we do often make new functionality based on enhancement requests from 3rd party developers. So file bugs and tell us how you'd like it improved. For example, in Motion 4, we made it easier to get frames at non-render times. In Motion 3, this wasn't possible because of threading issues, but after we saw how important it was to so many developers, we worked through those issues and made it work. > I have never released any of these commercially. > Mostly because I've never figured out how > to implement licensing code for FxPlugs. > So far, I've just been using them in-house > for various movies roughly over the past 5 years. > > Which might be another thing that could be addressed > into documentation. Like an example license gen/checker. That's an interesting thought, but I don't know how useful it would be. If we publish docs on how to create a license gen/checker, then people who want to crack your product's license gen code already have something to start from, and it's the same code you would have started from. But it might be worth having a discussion here about when and where in your plug-in to handle it, and how to do it in a non-obtrusive way for your legit users. 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: What problems do you run into when writing plug-ins?
by Darrin Cardani 20 Oct '10

20 Oct '10

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com On Oct 18, 2010, at 9:19 PM, Jim Tierney wrote: >>> What other problems have vexed you in the past when writing your > plug-ins? > > Not getting access to beta versions of host apps that would help us ensure > our existing plugins work. Well, that's certainly a fair assessment, but I was trying to find things that I could fix by documenting them. :-) I'm working very hard to get earlier seeds out with each new release, but it's an uphill battle. 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

high precision in fxscript (was: What problems do you run into when writing plug-ins?)
by Mattias Sandstrom 19 Oct '10

19 Oct '10

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com User-agent: Thunderbird 2.0.0.22 (Macintosh/20090605) // Copyright 2010 Mattias Sandström/Too Much Too Soon // This script is freeware, meaning you may copy and // distribute it free of charge, as long as it's kept intact, // including this message. Feel free to use the code as // inspiration for your own scripts, but don't steal. // Email me at mattias(a)beauty.se if you have any questions. // Thank you. Have fun. filter "Smart Chroma Sharpen"; group "TMTS Video"; InformationFlag("YUVaware") input dov, "Direction", popup, 2, "Horizontal (4:2:2/4:1:1)", "Both (4:2:0)" input amount, "Amount", slider, 3, 0, 10; code float w,h,k[2][3][3],i; dimensionsof(dest,w,h); image buf1[w][h],buf2[w][h],buff[w][h],thesource[w][h]; if GetPixelFormat(src1) != kFormatYUV219; setpixelformat(thesource, kFormatYUV219) ConvertImage(src1, thesource, kFormatYUV219) else thesource = src1 end if // edge detect kernels k[0]={-1,0,1,-2,0,2,-1,0,1}; k[1]={-1,-2,-1,0,0,0,1,2,1}; // start with black channelfill(buf1,0,0,128,128); // detect edges in all four directions and add together for i = 0 to 3 convolve(thesource, buf2, k[i/2], 1, 0); add(buf2,buf1,buf1,1,knone); k[i/2] *= -1; next; // blur edges to remove noise and increase width blur(buf1,buff,sqrt(amount),aspectof(dest)); // find the edges of the edges convolve(buff, buf1, k[0], 1, 128); convolve(buff, buf2, k[1], 1, 128); // copy second luma to "green" channel for vertical displace channelcopy(buf2,buf1,knone,knone,kred,knone); // restore source luma channelcopy(thesource,dest,knone,kred,knone,knone); _______________________________________________ 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… oh, and since i give away my plugins for free, here's the source if someone can figure out how to fix it. the problem is that the 128 offset is hard coded for 8 bit images so high precision just shifts the whole image a bit up and left instead of warping the edges (the "edges of the edges" map is not centered on gray but almost black), but i know of no way to tell what the offset should be, in the script or manually, not even hardcoding it to 512 (10-bit) or 32768 (16-bit) seems to work. // warp image towards its edges displace(src1, dest, buf1, 1, -amount/500, (1-dov)*amount/500, 0, aspectof(dest)); This email sent to site_archiver(a)lists.apple.com

1 0

Re: What problems do you run into when writing plug-ins?
by Mattias Sandstrom 19 Oct '10

19 Oct '10

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com User-agent: Thunderbird 2.0.0.22 (Macintosh/20090605) What other problems have vexed you in the past when writing your plug-ins? Anything you wish you had better documentation on? for fxscript that would be: everything. :-) /mattias -- http://www.mattias.nu/ http://www.imdb.com/name/nm1508285/ _______________________________________________ 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… Darrin Cardani wrote: one thing that seems to be completely undocumented is high precision rendering in fxscript. i have a filter that doesn't work at all in high precision, and i suspect it's because i'm using a convolve with a hardcoded 128 offset (needed for a displace map), but how do i handle that properly? i try converting all the buffers to yuv219 but it doesn't help, trying to hardcode the offset as 512 or 32768 doesn't help either. currently experimenting with reading chroma values from a desaturated buffer but that's some workaround for sure, and it's not quite working either. ;-) This email sent to site_archiver(a)lists.apple.com

1 0

Re: Final Cut Pro getInputImage() returning up-side-down image?
by Darrin Cardani 19 Oct '10

19 Oct '10

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com On Oct 19, 2010, at 11:57 AM, Paul Miller wrote: > On 10/19/2010 1:55 PM, Paul Miller wrote: >> In response to a button (custom UIButton view) press I'm calling >> getInputImage() to fetch the full-frame (progressive) image for the >> current frame. The returned image has an orientation of top-left, but >> it's actually up-side-down in memory. What did I do wrong? > > Oops - sorry for the C-style function format. I'm referring to the getInputBitmap method of the FxTemoralImageAPI. Hmm.... it doesn't sound like you've done anything wrong. I can't imagine a situation where we would send you an upside down image and it would be correct. Could you file a bug about this? 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/site_archiver%40lists.a… This email sent to site_archiver(a)lists.apple.com

1 0

Re: Final Cut Pro getInputImage() returning up-side-down image?
by Paul Miller 19 Oct '10

19 Oct '10

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com User-agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.9) Gecko/20100915 Lightning/1.0b2 Thunderbird/3.1.4 In response to a button (custom UIButton view) press I'm calling getInputImage() to fetch the full-frame (progressive) image for the current frame. The returned image has an orientation of top-left, but it's actually up-side-down in memory. What did I do wrong? _______________________________________________ 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… On 10/19/2010 1:55 PM, Paul Miller wrote: Oops - sorry for the C-style function format. I'm referring to the getInputBitmap method of the FxTemoralImageAPI. This email sent to site_archiver(a)lists.apple.com

1 0

Final Cut Pro getInputImage() returning up-side-down image?
by Paul Miller 19 Oct '10

19 Oct '10

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com User-agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.9) Gecko/20100915 Lightning/1.0b2 Thunderbird/3.1.4 In response to a button (custom UIButton view) press I'm calling getInputImage() to fetch the full-frame (progressive) image for the current frame. The returned image has an orientation of top-left, but it's actually up-side-down in memory. What did I do wrong? _______________________________________________ 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 problems do you run into when writing plug-ins?
by Brian Gardner 19 Oct '10

19 Oct '10

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=q+mi4sgeivDT7Gi1GjlUtI4fw8QCgctp1XDgDIR+/GpQ2nPsAH4i92/gBP87mkM+; h=Received:From:To:In-Reply-To:X-Mailer:Subject:References:Message-Id:Content-Type:Content-Transfer-Encoding:Mime-Version:Date:Cc:X-ELNK-Trace:X-Originating-IP; Hi, Darrin. Certainly, Image Parameters have been troublesome. Especially, getting frames synced from timeline to matching frames in Image parameters. Trying to keep them in sync through user edits on the Timeline was very troublesome. I wrote a bunch of stereoscopic FxPlugs a while back. I eventually got them working as well as the API would allow. Some of the Dev problems were documentation that could be misinterpreted, which could have been disambiguated better if there were examples to clarify. Of course, eventually, after figuring it all out, I realized that some necessary functionally was just not in the API at all. These were not just stereoscopic related, but missing functionality for image parameters in general. So, I've had to do stereo-3D in two passes. A "conform" pass, to merge the two streams (Left and Right cameras) into one 3-D stream. Then, the regular editing, using the merged footage. I only use Image Parameters in the Conform stage. This allows me to avoid Image Parameters completely during the regular 3-D editing of the movie. (I never edit 3-D movies in 2-D.) I have never released any of these commercially. Mostly because I've never figured out how to implement licensing code for FxPlugs. So far, I've just been using them in-house for various movies roughly over the past 5 years. Which might be another thing that could be addressed into documentation. Like an example license gen/checker. -- Brian Sent from my iPad On Oct 19, 2010, at 7:16 AM, Darrin Cardani <dcardani(a)apple.com> wrote: > I'm working on some documentation (gasp!), and am trying to think of problems that developers commonly run into when writing plug-ins. The things I've thought of so far are not properly handling non-square pixels, fields, and proxy resolution. So I'm thinking of writing some documentation on how to properly handle those and how to test your plug-ins to ensure that you're properly handling them. > > What other problems have vexed you in the past when writing your plug-ins? Anything you wish you had better documentation on? > > 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/brianrg%40earthlink.net > > This email sent to brianrg(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: What problems do you run into when writing plug-ins?
by Jim Tierney 19 Oct '10

19 Oct '10

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com Thread-index: ActvG+qLmFmLBDV/SAq0gbupmvC+VQAKHsAg >> What other problems have vexed you in the past when writing your plug-ins? Not getting access to beta versions of host apps that would help us ensure our existing plugins work. cheers, Jim -----Original Message----- From: pro-apps-dev-bounces+jim=digitalanarchy.com(a)lists.apple.com [mailto:pro-apps-dev-bounces+jim=digitalanarchy.com@lists.apple.com] On Behalf Of Darrin Cardani Sent: Monday, October 18, 2010 4:17 PM To: Pro-Apps-Dev Dev Subject: What problems do you run into when writing plug-ins? I'm working on some documentation (gasp!), and am trying to think of problems that developers commonly run into when writing plug-ins. The things I've thought of so far are not properly handling non-square pixels, fields, and proxy resolution. So I'm thinking of writing some documentation on how to properly handle those and how to test your plug-ins to ensure that you're properly handling them. What other problems have vexed you in the past when writing your plug-ins? Anything you wish you had better documentation on? 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/jim%40digitalanarchy.com This email sent to jim(a)digitalanarchy.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