May 2008 - Pro-apps-dev - lists.apple.com

filter plugin getting unexpected frame numbers
by Steve Christensen 23 May '08

23 May '08

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com I also included a couple of test lines: testStart = [timingAPI startTimeForEffect:self]; testDuration = [timingAPI durationForEffect:self]; renderInfo.frame = 6 effectTime = 6 effectDuration = 300 testStart = 240 testDuration = 300 renderInfo.frame = 1806 effectTime = 1806 effectDuration = 3901 testStart = 0 testDuration = 3091 Any ideas if I'm doing something wrong, if it's a FC bug or what? steve _______________________________________________ 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 seeing something weird in both FCP and FCE. I am working on a filter plugin that changes over time, so I'm getting the clip- relative frame number and the clip duration in order to calculate the fraction "done": timingAPI = [_apiManager apiForProtocol:@protocol(FxTimingAPI)]; effectTime = [timingAPI inputTimeForFilter:self fromTimelineTime:renderInfo.frame]; effectDuration = [timingAPI durationOfInputToFilter:self]; Everything behaves correctly in most cases, but I've run into one case where I get very unexpected numbers. Here's what I'm doing: 1. Launch FCE/FCP with a new project. 2. Drag a clip onto the timeline so it starts at about the 01:00:00;08 second mark. 3. Move the playhead so it's a few frames into the clip. 4. Click once on the clip so it's selected. 5. Locate my plugin in the list and drag it onto the clip. I have a breakpoint set in -renderOutput:withInput:withInfo: which gets hit at this time. I see: This is what I expect. I continue execution then switch back to FC. If I double-click on the clip, my plugin breakpoint gets hit once again, this time with the following values: This email sent to site_archiver(a)lists.apple.com

1 0

Re: FCP 6.0.3 and FxCustomParameterAction updates
by Pauli Ojala 23 May '08

23 May '08

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com -- Pauli Ojala Lacquer oy/ltd pauli(a)lacquer.fi _______________________________________________ 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 23.5.2008, at 23.38, Darrin Cardani wrote: On May 23, 2008, at 1:03 PM, Pauli Ojala wrote: I tried rewriting my FxPlug parameter+event code following your model, but with this new version I now have an unfortunate problem: render triggering doesn't work in Motion 2.x anymore. My old code did work in Motion 2. (It originally took some weird voodoo to get it working reliably there, which made the code a mess... That's why I was eager to do a rewrite.) FloatingWindow isn't useful as a comparison because it simply crashes Motion 2.1.2. (Looks like it goes into an infinite loop in CFRelease; I didn't have time to do any debugging yet.) I wish I could simply decide not to support Motion 2, but the previous version of Final Cut Studio is so widespread that it doesn't seem like a realistic option. Any ideas on how to get FloatingWindow working on Motion 2 would be greatly appreciated. Well, the most straightforward thing to do would be to detect whether you're in Motion 2 and use the old code path that worked if you are, otherwise use the newer code path. Is that possible to do? I suppose it is. The old code path is weird and contrived, the result of experimental voodoo years ago; I was hoping to do a complete housecleaning of the FxPlug code and finally throw it away, but looks like I'll have to keep it in the attic for now. FxHostCapabilities' methods -hostIsMotion and -hostVersionNumber is the proper way to detect the old host, right? This email sent to site_archiver(a)lists.apple.com

1 0

Re: FCP 6.0.3 and FxCustomParameterAction updates
by Darrin Cardani 23 May '08

23 May '08

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com On May 23, 2008, at 1:03 PM, Pauli Ojala wrote: Hi, Pauli, 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… thank you very much for providing the FloatingWindow FxPlug sample. I've had the users that were reporting problems with our plugin in FCP 6.0.3 run the sample, and it works as expected for them, so the problem is clearly in our FxPlug code. Were you able to reproduce the problem with my bars & tone steps? My guess is that this what your users are hitting. Even if not, someone is bound to hit it eventually. Yes, I can reproduce that (parameter updates only happen if the clip is open in the viewer). But actually this limitation doesn't bother me too much -- at least it's consistent and easy to explain. What these users are seeing with our plugin is more fatal, no updates at all except in special circumstances (switching from FCP to another app and back, and other strange cases). They do report that your FloatingWindow works, so there's clearly something rotten in my code. I tried rewriting my FxPlug parameter+event code following your model, but with this new version I now have an unfortunate problem: render triggering doesn't work in Motion 2.x anymore. My old code did work in Motion 2. (It originally took some weird voodoo to get it working reliably there, which made the code a mess... That's why I was eager to do a rewrite.) FloatingWindow isn't useful as a comparison because it simply crashes Motion 2.1.2. (Looks like it goes into an infinite loop in CFRelease; I didn't have time to do any debugging yet.) I wish I could simply decide not to support Motion 2, but the previous version of Final Cut Studio is so widespread that it doesn't seem like a realistic option. Any ideas on how to get FloatingWindow working on Motion 2 would be greatly appreciated. Well, the most straightforward thing to do would be to detect whether you're in Motion 2 and use the old code path that worked if you are, otherwise use the newer code path. Is that possible to do? This email sent to site_archiver(a)lists.apple.com

1 0

Re: FCP 6.0.3 and FxCustomParameterAction updates
by Pauli Ojala 23 May '08

23 May '08

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com Hi, Pauli, -- Pauli Ojala Lacquer oy/ltd pauli(a)lacquer.fi On 23.5.2008, at 17.08, Paul Schneider wrote: - Paul On May 23, 2008, at 9:24 AM, Pauli Ojala wrote: Paul, Best regards, Pauli -- Pauli Ojala Lacquer oy/ltd pauli(a)lacquer.fi On 14.5.2008, at 21.14, Paul Schneider wrote: Hi, Pauli, Thanks, - Paul <FloatingWindow.zip> On May 14, 2008, at 8:18 AM, Pauli Ojala wrote: Pauli Ojala _______________________________________________ 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 _______________________________________________ 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… thank you very much for providing the FloatingWindow FxPlug sample. I've had the users that were reporting problems with our plugin in FCP 6.0.3 run the sample, and it works as expected for them, so the problem is clearly in our FxPlug code. Were you able to reproduce the problem with my bars & tone steps? My guess is that this what your users are hitting. Even if not, someone is bound to hit it eventually. Yes, I can reproduce that (parameter updates only happen if the clip is open in the viewer). But actually this limitation doesn't bother me too much -- at least it's consistent and easy to explain. What these users are seeing with our plugin is more fatal, no updates at all except in special circumstances (switching from FCP to another app and back, and other strange cases). They do report that your FloatingWindow works, so there's clearly something rotten in my code. I tried rewriting my FxPlug parameter+event code following your model, but with this new version I now have an unfortunate problem: render triggering doesn't work in Motion 2.x anymore. My old code did work in Motion 2. (It originally took some weird voodoo to get it working reliably there, which made the code a mess... That's why I was eager to do a rewrite.) FloatingWindow isn't useful as a comparison because it simply crashes Motion 2.1.2. (Looks like it goes into an infinite loop in CFRelease; I didn't have time to do any debugging yet.) I wish I could simply decide not to support Motion 2, but the previous version of Final Cut Studio is so widespread that it doesn't seem like a realistic option. Any ideas on how to get FloatingWindow working on Motion 2 would be greatly appreciated. Can you elucidate a bit as to why the getAPI call is necessary here, and why one must check for its return value before proceeding? I'm only getting the current value of the parameter so I can increment it to get the new value. Getting the value first shouldn't be necessary. You do have to make sure you are assigning a new value to the parameter (one that is not identical to the old value). Also, I notice you're releasing the value returned from the get method. Is it always the case that -getCustomParameterValue retains the object before returning? That doesn't seem intuitive (I had expected that the setter retains but the getter doesn't, like standard Cocoa classes). You're right - that was a mistake on my part. Values returned from - getCustomParameterValue shouldn't be released. It looks like FCP is incorrectly returning retained references from - getCustomParameterValue; I've filed a bug. Motion does NOT return a retained reference from getCustomParameterValue. thank you very much for providing the FloatingWindow FxPlug sample. I've had the users that were reporting problems with our plugin in FCP 6.0.3 run the sample, and it works as expected for them, so the problem is clearly in our FxPlug code. The only significant difference is in the -forceRerender method. I have a few questions concerning your implementation, more specifically this section: ---- NSNumber* oldValue = nil; if ([getApi getCustomParameterValue:&oldValue fromParm:kParamID_Button]) { NSNumber* newValue = [NSNumber numberWithInt:[oldValue intValue] + 1]; [actApi startAction:self]; [setApi setCustomParameterValue:newValue toParm:kParamID_Button]; [actApi endAction:self]; } [oldValue release]; ---- My old version didn't call -getCustomParameterValue at all, it just went straight ahead with the actionAPI/setAPI calls. I guess that's probably why my code started failing. Can you elucidate a bit as to why the getAPI call is necessary here, and why one must check for its return value before proceeding? Also, I notice you're releasing the value returned from the get method. Is it always the case that -getCustomParameterValue retains the object before returning? That doesn't seem intuitive (I had expected that the setter retains but the getter doesn't, like standard Cocoa classes). The FxPlug API reference doesn't seem to make any mention of the retain/release policy for these methods. If it's right that - getCustomParameterValue always retains, my code has been leaking a scary amount of parameter value objects... I'd encourage you to add a big warning about this in the documentation! there were very few FxPlug-related changes in Final Cut 6.0.3, and I'm not aware of any that might have caused a difference in our behavior here. I wrote a very simple FxPlug filter that manages its own floating Cocoa window, with a button in the window to trigger a redisplay. It seems to work correctly in 6.0.3. I've attached it - if it works on your systems, perhaps you can spot a difference between this plugin and what you're doing? Also, when you say "we're receiving reports", do you mean that you've tested your plugin in 6.0.3, and something that always used to work now always fails? Or do you just mean that some of your customers are reporting problems? Hello, I'm hoping someone on the FCP FxPlug team might be able to give some insight into a problem that our users have been experiencing. Our plugin Conduit uses a private Cocoa window for its nodal effect editor UI. When the user modifies something in the editor window, we use FxCustomParameterActionAPI and FxParameterSettingAPI to set a new value for a custom parameter on the FxPlug instance. Ever since Motion 2.0, this method has worked fine for triggering a render in the host application. This way we don't need to run the editor modally; the user can keep the window open while moving around on the host app's timeline, which is very convenient. Now we're receiving reports that the FCP 6.0.3 update has broken this behaviour. Apparently the Viewer doesn't update anymore in response to events in our editor window. However, one user mentioned that switching from FCP to Finder and then back to FCP does trigger the expected render in the Viewer in FCP. So it sounds like the problem might be some fairly trivial bug somewhere -- as in the viewer not getting the equivalent of [- NSView setNeedsDisplay:] after the FxPlug parameter has been modified...? This email sent to pschneider(a)apple.com This email sent to site_archiver(a)lists.apple.com

1 0

Re: Timecode Generator formating?
by Patrick Sheffield 23 May '08

23 May '08

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=a9vuGCbcBA5db9YObyPOt4hQxXT10MPxgZAdT3+lpQvQ9TiCdCTim860rLz6g4j7; h=Received:In-Reply-To:References:Mime-Version:Content-Type:Message-Id:Cc:Content-Transfer-Encoding:From:Subject:Date:To:X-Mailer:X-ELNK-Trace:X-Originating-IP; http://pistolerapost.com/viewing/tcgen2.zip freebie that gives you controls over fonts, etc... Patrick On May 23, 2008, at 9:37 AM, Lance Drake wrote: Hi Pro-Apps people, Thank you, _______________________________________________ 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… Does anyone have an info-vector to how the size and location of the FCP timecode-generator overlay which gets added as a filter? Here's a link to how things look for me now: http:// www.glorioski.com/images/timecode.jpg It does not seem that there are any controls - that I can find - which would allow font/font-size changes or locating the position of the rectangle in the frame. Maybe there's a third party plug-in which could be used in place of the FCP built-in timecode-generator filter? Lance Drake _______________________________________________ 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.net This email sent to psheffield(a)earthlink.net This email sent to site_archiver(a)lists.apple.com

1 0

Re: XML Import question
by Helena Ju 23 May '08

23 May '08

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com Hey Andreas! Hope that helps! Helena On May 23, 2008, at 11:50 AM, Rainer Standke <lists(a)standke.com> wrote: Hi Andreas, Rainer On May 22, 2008, at 10:22 , Andreas Kiel wrote: Thanks Martin, Andreas On 22.05.2008, at 18:07, Martin Baker wrote: Hi Andreas Martin www.digital-heaven.co.uk The hottest tools for the coolest apps ------------------------------------------------------ LifeShaker: The humble to-do list. Redone. www.funkycloud.com/lifeshaker ------------------------------------------------------ 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 ===== Martin, Greg's suggestion does not work. -eryk On May 15, 2008, at 8:28 AM, Gregory Clarke wrote: Hi Martin, Hope this helps, Greg e.g. <bin> <uuid>A6768142-B28F-4F4B-A855-478E279D45FF</uuid> <updatebehavior>addifnotfound</updatebehavior> <name>imports</name> <children> <clip id="myclip.motn"> <uuid>B14825AB-79AD-4A4E-A7D5-79364B30FDDA</uuid> <updatebehavior>add</updatebehavior> <name>myclip.motn</name> ... </clip> </children> </bin> Any thoughts? ================== On 22 May 2008, at 16:43, Andreas Kiel wrote: Hi all, Regards Andreas _______________________________________________ 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/martin%40digital-heaven… Andreas Kiel Spherico Nelkenstr. 25 D-76135 Karlsruhe Tel.: +49 (0)721 183 9753 eFax: +1 650 897 8094 eMail: kiel(a)spherico.com http://spherico.com/filmtools -- workflow tools for FCP P Please don't print this e-mail unless you really need to. _______________________________________________ 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/lists%40standke.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/hju%40apple.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… Multiclips need a master multiclip to function properly, so if you haven't included the master multiclip ( it is shared across instances unless the angles are ordered differently) for the multiclip instances in a seqence, we create one for you. For a given multiclip in the timeline you can choose View > Reveal master multiclip and the create master multiclip should be selected in the browser. it looks to me like it automatically creates that bin when it imports a sequence containing multiclips. You might just want to not import your original clips. I just searched for your question, but it seems to be different from my "problem" - which may be a "feature". If you got a sequence just one multiclip and several edits and export this sequence as XML and re-import -- then FCP will create a bin automatically with all the multiclips of the sequence named "Multiclips" and I don't have any idea how the real relation of those clips in the bin and the clips in the sequence does work or is fool prooved. If I'm understanding correctly, I think this related to the question I asked last week. The short answer is that you can't add objects to a bin that already exists. I've filed it as a bug and got a duplicate bug number back so someone else got there first (possibly Eryk!) Here's the short answer - the only way add a clip to a bin is to replace the entire bin and its contents. This behavior is documented in the Final Cut Pro XML Interchange document. Personally, I've always considered this state of affairs to be a bug. Reading the spec, it doesn't look like the updatebehavior tag will do what you want it to. Here's the description of addifnotfound: • Adds the imported component to the project provided the tar get component is not found. If the target component is found, do es nothing. Which will do nothing in your case because the bin is found! I guess the way to achieve what you want is to append your clips' XML to the children tag of the appropriate bin. Then I'm guessing that setting the bin's updatebehavior to "replaceoradd" will replace the old bin with the new bin containing the original and extra clips. I'm trying to add a new clip to a specific bin (three levels deep) in an existing project and not having any success. I've stripped it back to a simple clip inside a single bin but still can't get the results I'm looking for. The "imports" bin already exists at the top level of the project open in FCP but when I import this, the myclip.motn file doesn't get added to the bin. Maybe somebody has an idea for me with the following: I have build an app which collects some data from external sources and then creates an FCP project out of this. The project is a multiclip project, which includes some bins and a multiclip sequence. The app is running fine and FCP imports without any errors and everything looks as expected - expect one thing. During import FCP creates a new bin "Multiclips" where the multiclips from the sequence are stored again. Is there any way to prevent FCP from doing that? It's bit confusing to have the multiclips twice in the project. Or is there something wrong with my XML? This email sent to martin(a)digital-heaven.co.uk This email sent to lists(a)standke.com This email sent to hju(a)apple.com This email sent to site_archiver(a)lists.apple.com

1 0

Re: XML Import question
by Rainer Standke 23 May '08

23 May '08

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com Hi Andreas, Rainer On May 22, 2008, at 10:22 , Andreas Kiel wrote: Thanks Martin, Andreas On 22.05.2008, at 18:07, Martin Baker wrote: Hi Andreas Martin www.digital-heaven.co.uk The hottest tools for the coolest apps ------------------------------------------------------ LifeShaker: The humble to-do list. Redone. www.funkycloud.com/lifeshaker ------------------------------------------------------ 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 ===== Martin, Greg's suggestion does not work. Personally, I've always considered this state of affairs to be a bug. -eryk On May 15, 2008, at 8:28 AM, Gregory Clarke wrote: Hi Martin, Hope this helps, Greg e.g. <bin> <uuid>A6768142-B28F-4F4B-A855-478E279D45FF</uuid> <updatebehavior>addifnotfound</updatebehavior> <name>imports</name> <children> <clip id="myclip.motn"> <uuid>B14825AB-79AD-4A4E-A7D5-79364B30FDDA</uuid> <updatebehavior>add</updatebehavior> <name>myclip.motn</name> ... </clip> </children> </bin> Any thoughts? ================== On 22 May 2008, at 16:43, Andreas Kiel wrote: Hi all, Regards Andreas _______________________________________________ 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/martin%40digital-heaven… Andreas Kiel Spherico Nelkenstr. 25 D-76135 Karlsruhe Tel.: +49 (0)721 183 9753 eFax: +1 650 897 8094 eMail: kiel(a)spherico.com http://spherico.com/filmtools -- workflow tools for FCP P Please don't print this e-mail unless you really need to. _______________________________________________ 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… it looks to me like it automatically creates that bin when it imports a sequence containing multiclips. You might just want to not import your original clips. I just searched for your question, but it seems to be different from my "problem" - which may be a "feature". If you got a sequence just one multiclip and several edits and export this sequence as XML and re-import -- then FCP will create a bin automatically with all the multiclips of the sequence named "Multiclips" and I don't have any idea how the real relation of those clips in the bin and the clips in the sequence does work or is fool prooved. If I'm understanding correctly, I think this related to the question I asked last week. The short answer is that you can't add objects to a bin that already exists. I've filed it as a bug and got a duplicate bug number back so someone else got there first (possibly Eryk!) Here's the short answer - the only way add a clip to a bin is to replace the entire bin and its contents. This behavior is documented in the Final Cut Pro XML Interchange document. Reading the spec, it doesn't look like the updatebehavior tag will do what you want it to. Here's the description of addifnotfound: • Adds the imported component to the project provided the target component is not found. If the target component is found, does nothing. Which will do nothing in your case because the bin is found! I guess the way to achieve what you want is to append your clips' XML to the children tag of the appropriate bin. Then I'm guessing that setting the bin's updatebehavior to "replaceoradd" will replace the old bin with the new bin containing the original and extra clips. I'm trying to add a new clip to a specific bin (three levels deep) in an existing project and not having any success. I've stripped it back to a simple clip inside a single bin but still can't get the results I'm looking for. The "imports" bin already exists at the top level of the project open in FCP but when I import this, the myclip.motn file doesn't get added to the bin. Maybe somebody has an idea for me with the following: I have build an app which collects some data from external sources and then creates an FCP project out of this. The project is a multiclip project, which includes some bins and a multiclip sequence. The app is running fine and FCP imports without any errors and everything looks as expected - expect one thing. During import FCP creates a new bin "Multiclips" where the multiclips from the sequence are stored again. Is there any way to prevent FCP from doing that? It's bit confusing to have the multiclips twice in the project. Or is there something wrong with my XML? This email sent to martin(a)digital-heaven.co.uk _______________________________________________ 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/lists %40standke.com This email sent to lists(a)standke.com This email sent to site_archiver(a)lists.apple.com

1 0

Re: Timecode Generator formating?
by Morten dotmac 23 May '08

23 May '08

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com http://www.cgm-online.com/eiperle/cgm_screenshots_v3_e.html look at CGM Timecode/Reel On May 23, 2008, at 6:37 PM, Lance Drake wrote: Hi Pro-Apps people, Here's a link to how things look for me now: http://www.glorioski.com/images/timecode.jpg Thank you, Lance Drake _______________________________________________ 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/mortenschmidt%40mac.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… Does anyone have an info-vector to how the size and location of the FCP timecode-generator overlay which gets added as a filter? It does not seem that there are any controls - that I can find - which would allow font/font-size changes or locating the position of the rectangle in the frame. Maybe there's a third party plug-in which could be used in place of the FCP built-in timecode-generator filter? This email sent to mortenschmidt(a)mac.com This email sent to site_archiver(a)lists.apple.com

1 0

Timecode Generator formating?
by Lance Drake 23 May '08

23 May '08

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com Hi Pro-Apps people, Here's a link to how things look for me now: http://www.glorioski.com/images/timecode.jpg Thank you, Lance Drake _______________________________________________ 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… Does anyone have an info-vector to how the size and location of the FCP timecode-generator overlay which gets added as a filter? It does not seem that there are any controls - that I can find - which would allow font/font-size changes or locating the position of the rectangle in the frame. Maybe there's a third party plug-in which could be used in place of the FCP built-in timecode-generator filter? This email sent to site_archiver(a)lists.apple.com

1 0

Re: FCP 6.0.3 and FxCustomParameterAction updates
by Paul Schneider 23 May '08

23 May '08

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com Hi, Pauli, - Paul On May 23, 2008, at 9:24 AM, Pauli Ojala wrote: Paul, Best regards, Pauli -- Pauli Ojala Lacquer oy/ltd pauli(a)lacquer.fi On 14.5.2008, at 21.14, Paul Schneider wrote: Hi, Pauli, Thanks, - Paul <FloatingWindow.zip> On May 14, 2008, at 8:18 AM, Pauli Ojala wrote: Pauli Ojala _______________________________________________ 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 _______________________________________________ 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… thank you very much for providing the FloatingWindow FxPlug sample. I've had the users that were reporting problems with our plugin in FCP 6.0.3 run the sample, and it works as expected for them, so the problem is clearly in our FxPlug code. Were you able to reproduce the problem with my bars & tone steps? My guess is that this what your users are hitting. Even if not, someone is bound to hit it eventually. Can you elucidate a bit as to why the getAPI call is necessary here, and why one must check for its return value before proceeding? I'm only getting the current value of the parameter so I can increment it to get the new value. Getting the value first shouldn't be necessary. You do have to make sure you are assigning a new value to the parameter (one that is not identical to the old value). Also, I notice you're releasing the value returned from the get method. Is it always the case that -getCustomParameterValue retains the object before returning? That doesn't seem intuitive (I had expected that the setter retains but the getter doesn't, like standard Cocoa classes). You're right - that was a mistake on my part. Values returned from - getCustomParameterValue shouldn't be released. It looks like FCP is incorrectly returning retained references from - getCustomParameterValue; I've filed a bug. Motion does NOT return a retained reference from getCustomParameterValue. thank you very much for providing the FloatingWindow FxPlug sample. I've had the users that were reporting problems with our plugin in FCP 6.0.3 run the sample, and it works as expected for them, so the problem is clearly in our FxPlug code. The only significant difference is in the -forceRerender method. I have a few questions concerning your implementation, more specifically this section: ---- NSNumber* oldValue = nil; if ([getApi getCustomParameterValue:&oldValue fromParm:kParamID_Button]) { NSNumber* newValue = [NSNumber numberWithInt:[oldValue intValue] + 1]; [actApi startAction:self]; [setApi setCustomParameterValue:newValue toParm:kParamID_Button]; [actApi endAction:self]; } [oldValue release]; ---- My old version didn't call -getCustomParameterValue at all, it just went straight ahead with the actionAPI/setAPI calls. I guess that's probably why my code started failing. Can you elucidate a bit as to why the getAPI call is necessary here, and why one must check for its return value before proceeding? Also, I notice you're releasing the value returned from the get method. Is it always the case that -getCustomParameterValue retains the object before returning? That doesn't seem intuitive (I had expected that the setter retains but the getter doesn't, like standard Cocoa classes). The FxPlug API reference doesn't seem to make any mention of the retain/release policy for these methods. If it's right that - getCustomParameterValue always retains, my code has been leaking a scary amount of parameter value objects... I'd encourage you to add a big warning about this in the documentation! there were very few FxPlug-related changes in Final Cut 6.0.3, and I'm not aware of any that might have caused a difference in our behavior here. I wrote a very simple FxPlug filter that manages its own floating Cocoa window, with a button in the window to trigger a redisplay. It seems to work correctly in 6.0.3. I've attached it - if it works on your systems, perhaps you can spot a difference between this plugin and what you're doing? Also, when you say "we're receiving reports", do you mean that you've tested your plugin in 6.0.3, and something that always used to work now always fails? Or do you just mean that some of your customers are reporting problems? Hello, I'm hoping someone on the FCP FxPlug team might be able to give some insight into a problem that our users have been experiencing. Our plugin Conduit uses a private Cocoa window for its nodal effect editor UI. When the user modifies something in the editor window, we use FxCustomParameterActionAPI and FxParameterSettingAPI to set a new value for a custom parameter on the FxPlug instance. Ever since Motion 2.0, this method has worked fine for triggering a render in the host application. This way we don't need to run the editor modally; the user can keep the window open while moving around on the host app's timeline, which is very convenient. Now we're receiving reports that the FCP 6.0.3 update has broken this behaviour. Apparently the Viewer doesn't update anymore in response to events in our editor window. However, one user mentioned that switching from FCP to Finder and then back to FCP does trigger the expected render in the Viewer in FCP. So it sounds like the problem might be some fairly trivial bug somewhere -- as in the viewer not getting the equivalent of [-NSView setNeedsDisplay:] after the FxPlug parameter has been modified...? This email sent to pschneider(a)apple.com This email sent to site_archiver(a)lists.apple.com

1 0