How are you using -frameSetup:::?
How are you using -frameSetup:::?
- Subject: How are you using -frameSetup:::?
- From: Darrin Cardani <email@hidden>
- Date: Thu, 15 Jan 2009 10:03:23 -0800
3rd Party Developers,
I'd like to get a feel for how developers are using the -frameSetup:::
method. I'm looking at a bug about software rendering, and it occurred
to me that the current model for -frameSetup::: is flawed.
The current situation: Motion (and I would bet FCP) currently call -
frameSetup::: once per frame right before calling -renderOutput:::.
Because -frameSetup::: is where the plugin tells the host app whether
the plugin can render in hardware or software, we don't know that
information at any other time than right before the plugin renders. So
when we try to figure out if the output is going to be small enough to
fit in VRAM, we don't yet know if the plugin will actually be using
any VRAM. (i.e. if it's software, it likely won't be.)
So in looking to the (far) future, I'm wondering if it would be a good
idea to either split apart -frameSetup::: which allows your plugin to
allocate memory and do any other necessary setup before rendering, and
asking the plugin whether it's going to render in hardware or
software, or if it would be reasonable to leave it as is, but call -
frameSetup::: (and of course -frameCleanup) in more places.
So my questions to developers are these:
1) In general, do you do much setup in -frameSetup:::? If so, what
sorts of things are you doing? (Allocating memory, pBuffers, etc? Just
doing some quick calcs?)
2) Do your filters generally work only in either hardware or software
(but not both), or do your filters generally make a decision based on
settings (like 8, 16, 32 bit rendering, frame size, etc.) to decide
whether to render in hardware and/or software? In other words, do you
generally hardcode the values for canRenderHardware/canRenderSoftware,
or is there generally logic to determine what they should be set to?
Thanks,
Darrin
--
Darrin Cardani
email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Pro-apps-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden