site_archiver@lists.apple.com Delivered-To: pro-apps-dev@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@apple.com
_______________________________________________ Do not post admin requests to the list. They will be ignored. Pro-apps-dev mailing list (Pro-apps-dev@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@revisionfx.com
-- Darrin Cardani dcardani@apple.com _______________________________________________ Do not post admin requests to the list. They will be ignored. Pro-apps-dev mailing list (Pro-apps-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/pro-apps-dev/site_archiver%40lists.ap... This email sent to site_archiver@lists.apple.com