September 2010 - Pro-apps-dev

Re: fxplug resize
by Shaobo Zhang 21 Sep '10

21 Sep '10

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:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=/jATiV85cQSmAI3wDL7Rb3RQKYYDBprOlkhtF/1TQgQ=; b=ldBfmHmsvpG+apaYGi+QejZj/znyq/3GgHpBFifnzhdLYjJECsjKHpB2Zev+a4H0Sp vHMFTycFxgMhc/pwFu8X9clOC77tJa8ygo1KwLoIxUIGOGKhnPXEkXYQOXE5yMNshBPI NN3DOFSUsIG4ZCk2beXYVL76L8XLsX51ZewRU= 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:content-transfer-encoding; b=BVFs7tUWKCuNuINctgmFbGyS6vnjwdgEsGrhuDiG9ACIuwiOBftXEh+cbt2XDnIXDJ yXlt4gm+KYSnB9UCoJCkIj/JRaIh2xfcKD2PaDpHXdwBETTWzDsQVRaTM/Fv09doZ/YS eHhapF+azE7RoBDfQt+rp8+x17cOSWDlM5Bh0= Thank you for your quick response. It helps a lot. On Tue, Sep 21, 2010 at 8:29 PM, Paul Schneider <pschneider(a)apple.com> wrote: > > Hi Shaobo, > > Yes, unfortunately this limitation is still present in Final Cut. Resizing the output does work in Motion. > > The SDK documentation outlines this limitation, and contains up-to-date information on the state of supported features in both Final Cut and Motion. > > - Paul > > > On Sep 20, 2010, at 11:52 PM, Shaobo Zhang wrote: > >> Hi,everyone. >> I read from a previous post in 2008 that we can not resize the output >> of a image in fxplug. Is it still the case? >> >> Thank you in advance. >> _______________________________________________ >> 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/pschneider%40apple.com >> >> This email sent to pschneider(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 resize
by Paul Schneider 21 Sep '10

21 Sep '10

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com Hi Shaobo, Yes, unfortunately this limitation is still present in Final Cut. Resizing the output does work in Motion. The SDK documentation outlines this limitation, and contains up-to-date information on the state of supported features in both Final Cut and Motion. - Paul On Sep 20, 2010, at 11:52 PM, Shaobo Zhang wrote: > Hi,everyone. > I read from a previous post in 2008 that we can not resize the output > of a image in fxplug. Is it still the case? > > Thank you in advance. > _______________________________________________ > 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/pschneider%40apple.com > > This email sent to pschneider(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 resize
by Shaobo Zhang 21 Sep '10

21 Sep '10

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:received:received:date:message-id :subject:from:to:content-type; bh=rR71tnn9Oslpq+kuKTsWcc9nBsGKHjaGAXtnZF2Mk7k=; b=UdkGojC3fk3P0ypSso1ej5WU3pDfKteLLPd2xwWgrzHksfZ8CZvaWoVzC7uo/42epQ Sx1TdwAD/+ftvpJ5pTUeC0MhZkHtPkwLIAgdB+WTkHiGiykhIU50QMCRuOcmSlbLH6Hs 4l8g0Z7MI7ux/lxZD/yiM59pp5IwgLGEt5xiY= Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=SwDp/sfC9LbZUiXP/zvtvUQGC9xUYCTe+wC88RNOtmuWgpG4RNC9AIsS4bTSVzUhea yh/uLY/0rWufc4aZw2Ld9RGXV4UnJWdDEZFsO6K6rsAGFmQvhsUCq3T+TufwgqvSEirh dGQJboJsvEjPOBaUV8TtcJsLWEm3V2riKqH1w= Hi,everyone. I read from a previous post in 2008 that we can not resize the output of a image in fxplug. Is it still the case? Thank you in advance. _______________________________________________ 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 do you want out of a path API?
by Darrin Cardani 14 Sep '10

14 Sep '10

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com On Sep 14, 2010, at 2:08 PM, Peter Litwinowicz wrote: > So there is no way to show all the splines and have them be editable by > simply selecting one of the splines in the UI . > > Then, for us, this spline feature enhancement is not really usable by us. Ah! It turns out I was mistaken. The user simply has to select both curves in the layer list, and then controls for both of them show up. So, yes, it is possible. Sorry for the confusion. (And they can select as many as they want - they're not just limited to 2.) > Oh, and we'd need open splines (are all your masks necessarily closed)? The app supports open splines, but currently not for masks (which is what I was thinking about exposing). However, our spline engineer tells me that we could set a mask spline to be open programmatically and the right thing would happen - there's just no user interface for it at the moment. It's a bit of a workaround, but would save us a lot of engineering time and make it more likely this feature would get implemented. Would that be useful to you? It would probably mean having some code in your -parameterChanged: method that just ensures that each spline the user chooses is set to be open. > We do appreciate you looking into this, but to be only be able to see one > spline at a time makes it difficult (if not impossible) for us to be able to > take advantage of the splines. I understand, and it's why I'm asking so many questions. I encourage others to give me feedback if they have strong feelings about this or any other topic I've asked about over the last year or two (keyframes, memory allocation and tracking, 3D and lighting, undo, etc.). 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: What do you want out of a path API?
by Peter Litwinowicz 14 Sep '10

14 Sep '10

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com Thread-index: ActUUOvHmwlZ6C8lFkmzQIMf/KPsYA== Thread-topic: What do you want out of a path API? User-agent: Microsoft-Entourage/12.26.0.100708 So there is no way to show all the splines and have them be editable by simply selecting one of the splines in the UI . Then, for us, this spline feature enhancement is not really usable by us. Imagine if you will a multi-spline warp. If you can only see one spline at a time, it's really awkward and difficult for the user to conceptualize the warp, because they can't see all the src (or dest) splines that are defined all at one time. Painful, and would make our product look unusable. Oh, and we'd need open splines (are all your masks necessarily closed)? We do appreciate you looking into this, but to be only be able to see one spline at a time makes it difficult (if not impossible) for us to be able to take advantage of the splines. Pete _______________________________________________ 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 do you want out of a path API?
by Darrin Cardani 14 Sep '10

14 Sep '10

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com On Sep 7, 2010, at 11:11 AM, Peter Litwinowicz wrote: > It would be helpful if we could programmatically change the drawing color of > the spline. It is also necessary to be able to programmatically make > individual splines invisible or not (for example, when warping or morphing, > you'll have two splines for each primitive: a "src" spline and a "dest" > spline, and it is necessary for the user to be able to see only one set (all > src or all dest splines) at a time. We normally have a button in our > plugin's UI where we can do internally within he plugin). I've been experimenting with this, and I'm not sure it would be useful, given Motion's current UI for splines. Let's say you have a generator or footage (this is from Motion 3, but it's the same in Motion 4) : Next you apply a couple of splines to it: Note that only the selected spline shows its control points. Next, let's say the user adds your nifty spline-using plugin to the generator: In order to change the parameters of your plugin, you have to select either the filter or the thing it's applied to, which in this case is not a mask. In order to show the splines again, you have to select one of the masks, which then causes your filter's parameters not to be displayed anymore: So hiding and showing splines programmatically won't ever be useful for a plugin to do because when the user is interacting with your plugin, the spline's on-screen control isn't drawn, anyway. And when they select the spline to manipulate it, the filter's controls go away. However, you could draw it (or not) yourself using the FxOnScreenControlAPI, if we made the path API also available to your OSC plugin. But as I've got it planned right now, you wouldn't be able to change the spline with the path API, as I was planning on making it read-only. (Once plugins can start manipulating the points, we have a lot more work to do to make sure they don't do invalid things to the splines.) So my point is, that while I could add the functionality to allow plugins to hide and show paths, I don't think it would do what you want. 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 do you want out of a path API?
by Peter Litwinowicz 10 Sep '10

10 Sep '10

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com Thread-index: ActRGc8NC0WbjGKABkey+9fIcTzsHw== Thread-topic: What do you want out of a path API? User-agent: Microsoft-Entourage/12.26.0.100708 _______________________________________________ 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 do you want out of a path API?
by Darrin Cardani 10 Sep '10

10 Sep '10

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com Pete, These are great suggestions! I have some questions about a couple of them below. On Sep 7, 2010, at 11:11 AM, Peter Litwinowicz wrote: >> One set of functions I'm not sure is useful is the functions for getting the >> length of 1 segment of a path, > > Oh, we use this all the time. In our warper, we want to align segments of a > spline to another segment of a spline. So we need to be able to evaluate > each segment of a spline independently. OK, noted. It's not too difficult to do, I just wasn't sure if people were using it as a substitute for just being able to find the point at a certain percentage of the distance along the curve. But if you need it in addition, that's do-able. > We need to be able to get each vertex, we need to be able to evaluate points > along the curve: and that includes by equal spacing in the output space, and > by equal spacing in the parameter space (which are not the same thing!). Do you find it helpful for us to also provide a method for evaluating points in parameter space? It seemed like output space was the hard case, so I was thinking we'd add that, but in the parameter space is pretty easy, so we'd let developers write that themselves. But we could add both. >> Also, do you need to know the mode of the mask? (Add, Subtract, etc.) It seems >> like in most cases you're drawing something rather than actually rendering the >> mask and applying it in some way, since that's what the app does for you. But >> if that functionality is useful, let me know. > > Oh, that is useful. Why leave it out? :-) It's just a call to implement > and query the status of the mask, right? Yeah, it's very simple. I was just questioning whether it was useful. But if it is, no problem! > We also need to be able to attach our own parameters to each spline > (checkboxes, menus, floating point sliders, etc.). We can live with each > spline getting the same set (that is, we don't need to vary the set of > params per spline, just per plugin!). Can you elaborate on this? When you say "attach our own parameters to each spline," do you mean that you have some fixed set of parameters, and you need a copy of those parameter for every spline attached to the image (or plugin)? For example, you want a checkbox, a slider, and a color well. And for each spline created, you need those same 3 parameters in 1 plugin? Is that right? > As far as UI goes, I also believe that you should attach splines to the > individual plugin instances, so there is no doubt as to "who" owns the > plugin (the masking interface of Motion, the plugin, which plugin, etc.) . > The After Effects UI model is all wrong. You should really look at the > Combustion model for the UI (Ummm, Guido should be able to help you there > :-)) Hmm.... I will definitely ask Guido about it. It's unlikely we'll be able to change the model of what masks are attached to, but I'll give it some thought and talk to both our UI people and our spline people and see what can be done. (But don't get your hopes up on this one. ;-) ) > It would be helpful if we could programmatically change the drawing color of > the spline. Oh! I never thought of that! Good suggestion. I don't even know if we have a mechanism in the app to set it internally, but it's a good idea. > It is also necessary to be able to programmatically make > individual splines invisible or not (for example, when warping or morphing, > you'll have two splines for each primitive: a "src" spline and a "dest" > spline, and it is necessary for the user to be able to see only one set (all > src or all dest splines) at a time. We normally have a button in our > plugin's UI where we can do internally within he plugin). Also a great idea! > It would be helpful if we could copy and create a duplicate of a spline, so > that when the user creates a source or dest spline, that we can > automatically create the other one. It would be useful to programmatically > copy keyframes from one spline to another (for similar reasons). It would > also be useful to delete vertices internally and add vertices > programmatically. So that if one spline of a pair has a vertex added by the > user that we can add a vertex in the corresponding place on the other spline > automatically (by us internally). This one sounds tough. Duplicating a spline with all of its keyframes probably wouldn't be too hard. But once you start adding and removing vertices, do you need to also set keyframes on those vertices programmatically? I'll need to figure out if the notification mechanism for adding and removing vertices can send notifications to plugins. I see now why you want the splines to be associated with a plugin rather than with the object the plugin is applied to. (Of course, with generators, the splines are applied to the plugin, but that's probably not too useful in your case.) > When cutting and pasting splines between plugins, you should bring along all > the per-spline params, unless it is a differing plugin... Then just > cut-and-paste the geometry portion (and with keyframes, if animated). Definitely sounds useful, but that would require actually associating some plugin data with the spline. I'm not sure how difficult that would be to do. But I'll look into it. > It would be useful for the user if you could attach trackers to control > points of the spline (trackers anyone? :-)) They can already do this! Add a mask to a layer, select the mask, then add the Behavior "Shape > Track Points" to the mask. Voila! > I'm sure I'll think of more things... Call me if you want to talk about > this. I may also do that. I wanted to discuss some of it publicly, though, in case it inspired anyone else to answer. 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: What do you want out of a path API?
by Peter Litwinowicz 07 Sep '10

07 Sep '10

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com Thread-index: ActOuBj3euzOPggq+kyg3RdEBi7mvw== Thread-topic: What do you want out of a path API? User-agent: Microsoft-Entourage/12.26.0.100708 > FxPlug Developers, > > One set of functions I'm not sure is useful is the functions for getting the > length of 1 segment of a path, Oh, we use this all the time. In our warper, we want to align segments of a spline to another segment of a spline. So we need to be able to evaluate each segment of a spline independently. For us it is necessary to be able to get "checkpoints" along the spline, and we use control points to do that.... In essence we see each segment of a spline as something to use a "primitive" to match to another segment on another spline... Not just along the whole spline itself. That said, we also need to know the length of the spline in order to evaluate at discreet points along the spline approximately a pixel apart for drawing, warping, etc. > > Looking at our internal use of paths, it seems much more frequent that we need > to get a point which is some percentage along a path. For example, if you're > doing a stroke over time, and you know you're 38% through your time, you want > to know the point that is 38% along the path. Yes, we need that too, in order to evaluate at regular distances along the spline. But we need to be able to evaluate percentages of each segment too (see above paragraph!). We need to be able to get each vertex, we need to be able to evaluate points along the curve: and that includes by equal spacing in the output space, and by equal spacing in the parameter space (which are not the same thing!). We do lots of matching up of evaluate points along a spline segment to a corresponding place on another spline segment.. And doing that in the parameter space is pretty much useless.. You want to match up things based on their distance in the output (screen space!). > > Also, do you need to know the mode of the mask? (Add, Subtract, etc.) It seems > like in most cases you're drawing something rather than actually rendering the > mask and applying it in some way, since that's what the app does for you. But > if that functionality is useful, let me know. Oh, that is useful. Why leave it out? :-) It's just a call to implement and query the status of the mask, right? > > So if you're using paths in your plugins for other platforms, please let me > know what you think of the above questions, and also if there's something > missing from other APIs that you'd like to see, let me know! We also need to be able to evaluate splines at differing points in time. We also need to be able to attach our own parameters to each spline (checkboxes, menus, floating point sliders, etc.). We can live with each spline getting the same set (that is, we don't need to vary the set of params per spline, just per plugin!). As far as UI goes, I also believe that you should attach splines to the individual plugin instances, so there is no doubt as to "who" owns the plugin (the masking interface of Motion, the plugin, which plugin, etc.) . The After Effects UI model is all wrong. You should really look at the Combustion model for the UI (Ummm, Guido should be able to help you there :-)) It would be helpful if we could programmatically change the drawing color of the spline. It is also necessary to be able to programmatically make individual splines invisible or not (for example, when warping or morphing, you'll have two splines for each primitive: a "src" spline and a "dest" spline, and it is necessary for the user to be able to see only one set (all src or all dest splines) at a time. We normally have a button in our plugin's UI where we can do internally within he plugin). It would be helpful if we could copy and create a duplicate of a spline, so that when the user creates a source or dest spline, that we can automatically create the other one. It would be useful to programmatically copy keyframes from one spline to another (for similar reasons). It would also be useful to delete vertices internally and add vertices programmatically. So that if one spline of a pair has a vertex added by the user that we can add a vertex in the corresponding place on the other spline automatically (by us internally). When cutting and pasting splines between plugins, you should bring along all the per-spline params, unless it is a differing plugin... Then just cut-and-paste the geometry portion (and with keyframes, if animated). It would be useful for the user if you could attach trackers to control points of the spline (trackers anyone? :-)) I'm sure I'll think of more things... Call me if you want to talk about this. Pete _______________________________________________ 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 Cue Pro Export..
by Glen 06 Sep '10

06 Sep '10

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:received:sender:received:date :x-google-sender-auth:message-id:subject:from:to:content-type; bh=MxVdMH4imNMJHlqTNUdFW5Ja2cXY7EngneH3on4KF3Y=; b=Hy08Rudg836SysExrYHzPfwquV2FurEKeLxFcZoxLPZa7AVdy8GuQ2U9dlO9IkXb4L rqwmrrJmMRYWxx2/tuju4tsoJQVpjN959osY3AsryfuVNC/NF1Df3PFaKfsx/RkHfldI rcc0LyTrW3gKdrvJfotOQiXBn+qDtab8P5o4g= Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:date:x-google-sender-auth:message-id:subject :from:to:content-type; b=a38w/YnEs68n8yFDXbDsiX1uQ4z+2m5x5OTwJE8HnhirhqyjKAn8GOm8w5Gyabg2W8 SW0yjeTv/Ujhvew1ZbJY7f0TYA7T9N4JRdrJ00nyGKRvsIqfkMKiLw7gj7LrYhLznwMI TWIW6WysjJv/SR4b2O42/dwM1ERhsBqrTb46U= _______________________________________________ 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