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

Re: FxPlug 1.0 and FxPlug 2.0 Bundles
by Darrin Cardani 30 Aug '11

30 Aug '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

FxPlug 1.0 and FxPlug 2.0 Bundles
by Julian Vasilkoski 30 Aug '11

30 Aug '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: FCP XML Audio Framerates
by Bruce Sharpe 30 Aug '11

30 Aug '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=ItBFJAl6xQwWM6FpUUc+6wlLdq4TJ/M61y5kSzan+qk=; b=X4Z5yUpjrjFKdQ2QY3begZv3B0nC6C/BAE9sOziBNlIBS+tyC0LZ6mdWIl+GTYokL3 v8vTb2c8wGkuuQGy7KY5GV/xLW3BYfN0gu9YlQ/hqkhkxJ3z5EO25fbRE9+vPSP/+9Et In8iezJvFWriOJeQIh7YjrTXGcKTEzIIqJhoI= _______________________________________________ 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

FCP XML Audio Framerates
by Thomas Knudsen 30 Aug '11

30 Aug '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: custom data from a Motion FCXP template observation
by Darrin Cardani 29 Aug '11

29 Aug '11

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com It's the keyed archive encoded with something that's like, but is not, uunencoding (or maybe it's MIME-like - I forget). I'll send you the details off-list because they're kind of long. Darrin On Aug 25, 2011, at 12:47 PM, Paul Miller wrote: > Well this is interesting. Any data set to a Custom parameter (a hidden one with no UI) inside Motion comes over properly to FCPX in an effect template. > > This means I could theoretically keep my code the same, but just generate effect templates for my presets rather than using my own preset browser. > > But I'd need to be able to set the custom data value in the .moef - does anyone know what the encoding is? I'm not going to do all 200 of them by hand. > > For instance, in the .moef for the custom parameter is an element for "dataValue". If I assign a [NSData] with "FOO!" in the contents, the value for dataValue in the .moef is: > > ********_*6UeMb0gOLBoA11I*E61-*I40EdM75.... and a lot more encoded goo. I'd need to generate that myself somehow so I can automate the process. > _______________________________________________ > 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: more on .moefs and published parameters
by Paul Miller 26 Aug '11

26 Aug '11

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com User-agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:6.0) Gecko/20110812 Thunderbird/6.0 I compared my edited copy to one that I manually unpublished in Motion and except for a few flags differences (I don't know why they were different) they looked substantially the same to me. As a potential work-around to not being able to unpublish the parameters by removing the relevant elements from the moef, I tried looking at the flags so I could "disable" the unused parameters. But I can't make heads or tails of the parameter flags either. The flags seem to change from save to save even. ie. in one template the flags might be 12901679120, and then if I Save As the template to a new one they might end up as 4311744528. So I'm back to needing help figuring out what to remove from the .moef to unpublish a parameter, or going through each template and unpublishing parameters one by one manually (I'm not excited about this). _______________________________________________ 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 data from a Motion FCXP template observation
by Paul Miller 25 Aug '11

25 Aug '11

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com User-agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:6.0) Gecko/20110812 Thunderbird/6.0 Well this is interesting. Any data set to a Custom parameter (a hidden one with no UI) inside Motion comes over properly to FCPX in an effect template. This means I could theoretically keep my code the same, but just generate effect templates for my presets rather than using my own preset browser. But I'd need to be able to set the custom data value in the .moef - does anyone know what the encoding is? I'm not going to do all 200 of them by hand. For instance, in the .moef for the custom parameter is an element for "dataValue". If I assign a [NSData] with "FOO!" in the contents, the value for dataValue in the .moef is: ********_*6UeMb0gOLBoA11I*E61-*I40EdM75.... and a lot more encoded goo. I'd need to generate that myself somehow so I can automate the process. _______________________________________________ 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

more on .moefs and published parameters
by Paul Miller 25 Aug '11

25 Aug '11

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com User-agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:6.0) Gecko/20110812 Thunderbird/6.0 Any ideas as to what I am missing? _______________________________________________ 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… I'm trying to figure out what edits I actually need to make the to the .moef to get parameters unpublished. In Motion I created a "template" template that has all of my parameters published. I've written a script that takes the "template" template and makes multiple .moefs from it, varying the values to create presets from a datafile (I don't want to hand-create 240+ FCP templates). For some of my presets, I don't need some of the parameters, so I want to unpublish them (by diddling the .moef). I found three places in the .moef where an unpublished parameter would "disappear" from after unpublishing it in Motion: 1. <publishSettings> contains a <target> entry for it with the "channel" attribute set to the group/parameter id. I removed this. 2. <publishSettings> also contains a <parameter> entry for the parameter with the published name and the "id" set to the creation index. I removed this. 3. Later on ion the <scenenode> there is a <parameter> entry with the name of "Published Folder", and nested in there is another <parameter> entry also with the "id" by creation order. I removed this as well. I compared my edited copy to one that I manually unpublished in Motion and except for a few flags differences (I don't know why they were different) they looked substantially the same to me. However, when I started FCPX with my modified templates in place FCP crashed. If I put back my deleted <parameter> and <target> entries everything worked find, but of course the parameter was still published. This email sent to site_archiver(a)lists.apple.com

1 0

Re: .moef parameter ids
by Darrin Cardani 24 Aug '11

24 Aug '11

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com On Aug 24, 2011, at 10:16 AM, Paul Miller wrote: >> Oh, actually, I forgot, the parameters don't have to be in order. Here's a test I just ran: > ... >> So it shouldn't be a problem. You should be able to insert a new parameter above the old one, but with a higher ID. > > I'm still a little confused - because what you just showed is that the published parameter ids are still in creation order. I wasn't talking about moving them around in the project/publish settings (though this is a nice feature), but moving them around in the code itself. It seems if I add any control TO THE CODE before any other existing controls (so I can get the order I want in the Motion inspector, and in FCP7), it will break existing moefs because the ids used in the publishSettings section are in creation order, and not the actual code-defined ids. OK, so, I've got some more information. I think what you want to do should still be possible. In the publishSettings element, you'll see target elements: <target object="xyz" channel = "./1"/> The xyz is the ID of your filter object in this document, and the "channel" attribute is the path, starting at your filter object, to the parameter you're publishing. For example, if you add the Spot Light Core Image filter to a Final Cut Effect, publish the "light position" and "light points at" parameters, and save it, you'll get these: > <target object="10283" channel="./2"/> > <target object="10283" channel="./3"/> > <target object="10322" channel="./2/200"/> > <target object="10322" channel="./2/201"/> > <target object="10322" channel="./3/300"/> > <target object="10322" channel="./3/301"/> Channel 2 is the folder containing the channels for the position parameter. 2/200 is the position's (X,Y) value as a point parameter, and 2/201 is the position's Z value as a slider. Channel 3 is the "Light points at" folder, and 3/300 and 3/301 are the (x,y) and Z parameters for it. Does that make sense? So, let's say you add a slider parameter #1 in the next version. If you want to publish it, you could output publishSettings that started with: <target object="10283" channel="./1"/> <target object="10283" channel="./2"/> <target object="10283" channel="./3"/> <target object="10322" channel="./2/200"/> <target object="10322" channel="./2/201"/> <target object="10322" channel="./3/300"/> <target object="10322" channel="./3/301"/> Or you could put it anywhere else in that list that you want. Everything should be just fine, regardless of where you put it either in the FxPlug, or in the publish settings. Am I understanding what you want to do? Does that solve the problem? Existing .moefs should continue to work fine because they don't reference the new channel, and the other channels are referenced by their path within the effect, not their creation order. 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: .moef parameter ids
by Paul Miller 24 Aug '11

24 Aug '11

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com User-agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:6.0) Gecko/20110812 Thunderbird/6.0 Oh, actually, I forgot, the parameters don't have to be in order. Here's a test I just ran: ... So it shouldn't be a problem. You should be able to insert a new parameter above the old one, but with a higher ID. I'm still a little confused - because what you just showed is that the published parameter ids are still in creation order. I wasn't talking about moving them around in the project/publish settings (though this is a nice feature), but moving them around in the code itself. It seems if I add any control TO THE CODE before any other existing controls (so I can get the order I want in the Motion inspector, and in FCP7), it will break existing moefs because the ids used in the publishSettings section are in creation order, and not the actual code-defined ids. _______________________________________________ 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