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

Re: Motion API
by Darrin Cardani 28 Mar '08

28 Mar '08

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com On Mar 28, 2008, at 4:04 AM, Peter Krajcik wrote: 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… does anybody know if Motion API or description of motion file format (structure) is available from Apple ? There is a Motion framework in the Library/Frameworks, so something could be out ... We don't currently document it publicly. (I'm pushing to do so, but it hasn't been approved yet.) It should be fairly easy to figure out if you're familiar with how Motion works as a user. If you have questions about it, feel free to ask here, and I'll do what I can to answer your questions. This email sent to site_archiver(a)lists.apple.com

1 0

Motion API
by Peter Krajcik 28 Mar '08

28 Mar '08

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com Hello, Thank you. Peter _______________________________________________ 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 anybody know if Motion API or description of motion file format (structure) is available from Apple ? There is a Motion framework in the Library/Frameworks, so something could be out ... This email sent to site_archiver(a)lists.apple.com

1 0

Re: Importing a file in a FCP project with AppleEvents
by Eryk Vershen 27 Mar '08

27 Mar '08

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: Importing a file in a FCP project with AppleEvents
by Eryk Vershen 25 Mar '08

25 Mar '08

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

Importing a file in a FCP project with AppleEvents
by Valentin Dan 25 Mar '08

25 Mar '08

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com Thread-index: AciOhm748cAfh87nRAiRA7hdoWtUTQ== Thread-topic: Importing a file in a FCP project with AppleEvents _______________________________________________ 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: FxTexture: -textureId returns zero?
by Steve Christensen 24 Mar '08

24 Mar '08

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: FxTexture: -textureId returns zero?
by Steve Christensen 24 Mar '08

24 Mar '08

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com On Mar 24, 2008, at 8:19 AM, Steve Christensen wrote: Well, now that I know I can at least deal with it. I've filed a couple of bugs: _______________________________________________ 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 Mar 24, 2008, at 9:36 AM, Darrin Cardani wrote: I'm calling [[FxTexture alloc] initWithInfo:textureInfo] to create a FxTexture, which succeeds. When I then call -textureId, it returns zero. Yet when I call -textureId on the input texture, I get a non-zero value. Am I missing something? The documentation on FxTexture is pretty much non-existent so I don't know what I'm doing wrong or what more I should be doing. Sorry about the poor documentation. I had to actually look at the source to figure out what's going on. FxTextures are a very thin wrapper around OpenGL textures. The framework attempts to make no assumptions about what you are trying to do with the texture, so it doesn't do anything more than what you tell it. As such, there are no methods which will create the texture ID for you. Because FxTextures don't take ownership of the OpenGL resources, there's no way for it to safely do that. So what it's expecting you to do is create the texture yourself and tell it what the texture ID is. There are a couple ways you can do that. You can create the texture ahead of time by calling glGenTextures () and passing the resulting texture ID to [- FxTexture initWithInfo:AndTextureID:]. Or you can call [-FxTexture initWithInfo:] and later call [-FxTexture setTextureID:]. But whatever you do, it's up to you to create the texture ID and tell the FxTexture object about it. (You'll also need to tell it which target you uploaded the texture to by calling [-FxTexture setTarget].) Would you find it useful if we had a method which created the texture ID for you? We might be able to add something like that in the future if there's a lot of need for it. rdar://5816382 - request to flesh out the FxTexture documentation in particular and the SDK documentation in general, both headers and HTML/PDF docs rdar://5816484 - feature request to add a new initializer to FxTexture that does actually create a texture This email sent to site_archiver(a)lists.apple.com

1 0

Re: FxPlug Fx3DAPI - Plug-ins only? No Generators?
by Matt Rhodes 24 Mar '08

24 Mar '08

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com m _______________________________________________ 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 like FxGenerators don't have access to the 3D API -- is this correct? That is correct. It was an oversight. I have fixed it in a future version, but that version won't be available to the public any time soon. Sorry for the inconvenience. As you know, bug fixes have to be tested, and there wasn't time to test this fix for an earlier release. I'm hoping in the future we can seed 3rd party developers earlier to get better feedback. However, even when we've tried, the feedback from 3rd parties has been minimal. It's hard to find bugs in time to fix them when we don't get very much feedback (which admittedly is at least partly our own fault for not getting seeds to developers earlier). In other words, yeah, it sucks, and we're working on it. I've been a lousy 3rd party developer when it comes to beta testing and feedback -- so I can't complain too much. I'm sure I could have found some of these limitations before release. With previews, they are generated automatically for generators and always have been. We can do that with generators because they take no input. But with filters, it's not as easy because any given input may not be appropriate for a preview of a particular filter. For example, a photo with no green in it, won't show a green screen filter very well. And an image with no alpha won't show an effect that does something based on the alpha. I think the idea was that we want to generate a preview when possible so developers have less work to do. But there are cases where we can't do that. Maybe we should check to see if there's a preview movie and show it if it exists, and generate one if it doesn't exist? If you'd like to see that, please file an enhancement request. The logic for Generator movies makes sense -- but our Generators don't create anything by default -- but we'd like to show what it can do. I'll file a request. Thanks for the quick reply, Darrin. We really appreciate how responsive your team is with stuff like this. And we're *really* happy to see our stuff working so well in FCP. This email sent to site_archiver(a)lists.apple.com

1 0

Re: FxPlug Fx3DAPI - Plug-ins only? No Generators?
by Darrin Cardani 24 Mar '08

24 Mar '08

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com On Mar 24, 2008, at 9:32 AM, Matt Rhodes wrote: Hey Team. That makes complete sense. Personally, I love writing generators! :) 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… It looks like FxGenerators don't have access to the 3D API -- is this correct? That is correct. It was an oversight. I have fixed it in a future version, but that version won't be available to the public any time soon. Sorry for the inconvenience. As you know, bug fixes have to be tested, and there wasn't time to test this fix for an earlier release. I'm hoping in the future we can seed 3rd party developers earlier to get better feedback. However, even when we've tried, the feedback from 3rd parties has been minimal. It's hard to find bugs in time to fix them when we don't get very much feedback (which admittedly is at least partly our own fault for not getting seeds to developers earlier). In other words, yeah, it sucks, and we're working on it. The following has been our experience with Generators (vs. Plug-ins): We have several plug-ins that work more appropriately as Generators, but we keep having to back off from creating Generators because the feature sets for Generators aren't the same as for Plug-ins -- and they should be (from this developer's point of view). Are there other features which aren't available for Generators that are for Plug-Ins? The only other one I can think of is the temporal image API, which isn't available because there are no input images to Generators, so getting the input doesn't make sense. We think of Generators as Plug-ins without the need for an input layer. We need all of the features that plug-ins have to offer -- parameter interaction (we had to wait for that to work properly), preview Movies (which still aren't supported, from what I can tell), 3D API's, etc. In the past (and seemingly here as well), the feature set of Generators have taken some time to catch up to Plug-ins. This causes a perpetual cycle of "can't create a Generator because we need the new Plug-in feature." Parameter interaction should be working just fine in generators. If it's not, please file a bug. With previews, they are generated automatically for generators and always have been. We can do that with generators because they take no input. But with filters, it's not as easy because any given input may not be appropriate for a preview of a particular filter. For example, a photo with no green in it, won't show a green screen filter very well. And an image with no alpha won't show an effect that does something based on the alpha. I think the idea was that we want to generate a preview when possible so developers have less work to do. But there are cases where we can't do that. Maybe we should check to see if there's a preview movie and show it if it exists, and generate one if it doesn't exist? If you'd like to see that, please file an enhancement request. Maybe there aren't a lot of Generator developers out there, but all of our FxPlugs are Generators at heart -- and we hate telling the user to create a dummy layer just to use our Plug-in. This email sent to site_archiver(a)lists.apple.com

1 0

Re: FxTexture: -textureId returns zero?
by Darrin Cardani 24 Mar '08

24 Mar '08

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com On Mar 24, 2008, at 8:19 AM, Steve Christensen wrote: 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… I'm calling [[FxTexture alloc] initWithInfo:textureInfo] to create a FxTexture, which succeeds. When I then call -textureId, it returns zero. Yet when I call -textureId on the input texture, I get a non- zero value. Am I missing something? The documentation on FxTexture is pretty much non-existent so I don't know what I'm doing wrong or what more I should be doing. Sorry about the poor documentation. I had to actually look at the source to figure out what's going on. FxTextures are a very thin wrapper around OpenGL textures. The framework attempts to make no assumptions about what you are trying to do with the texture, so it doesn't do anything more than what you tell it. As such, there are no methods which will create the texture ID for you. Because FxTextures don't take ownership of the OpenGL resources, there's no way for it to safely do that. So what it's expecting you to do is create the texture yourself and tell it what the texture ID is. There are a couple ways you can do that. You can create the texture ahead of time by calling glGenTextures () and passing the resulting texture ID to [-FxTexture initWithInfo:AndTextureID:]. Or you can call [-FxTexture initWithInfo:] and later call [-FxTexture setTextureID:]. But whatever you do, it's up to you to create the texture ID and tell the FxTexture object about it. (You'll also need to tell it which target you uploaded the texture to by calling [-FxTexture setTarget].) Would you find it useful if we had a method which created the texture ID for you? We might be able to add something like that in the future if there's a lot of need for it. This email sent to site_archiver(a)lists.apple.com

1 0