Re: image formats for rendering, etc.
Re: image formats for rendering, etc.
- Subject: Re: image formats for rendering, etc.
- From: Peter Litwinowicz <email@hidden>
- Date: Wed, 06 Jun 2007 17:32:00 -0700
- Thread-topic: image formats for rendering, etc.
Title: Re: image formats for rendering, etc.
Oh, that's an interesting question. I'm pretty sure Motion won't give you an 8-bit image in that case. It will probably just display a black frame. I wonder if that's even been tested. Hmmm.... I'll try it tomorrow and see what happens.
Okay, if it doesn’t deprecate the image, let me know and I’ll file an official feature request.
FCP:
Let's say I return FALSE for both canDoSOftware and canDoHardware in frameSetup when passed an r408 image. Does that mean that the frame simply won't get rendered, or will an RGBA image be tried?
I'm just wondering if we have to support all image formats, or whether we can support just SOME of them and have the others be redirected to the formats we support. And if formats get redirected (say YUV+A float to RGBA float), can we get a decision tree that tells what what will go on internally within FCP/Motion?
I don't know whether I've asked these questions before (I think I did), but the answers have eluded my mind and the docs don't fill me in.
If you don't want to support r408 or r4fl, set their entries to "NO" in your -properties method. Then you should never receive them, and instead you'll get RGB images.
Okay, good to know (and I think Paul told me this, and has just told me again!)... This needs to be in the docs. The doc says that there is a properties method, but doesn’t go into details about WHICH properties we can return). This information should not be left to example programs or the reference HTML docs (because that’s just a list of routines).
All the settable information should be in some detailed doc... Something that’s more detailed than the FxPlug SDK 1.2 Overview.pdf and more coherent than the reference manual (the html pages with all the calls/protocols laid out).
Is there such a document and I’m just missing it?
And then there's this question: if my input image is given in a particular format, will all clipwells for the plugin ALSO be converted to the same format, or do they each have their own formats we need to deal with?
In Motion, since all images are RGB, you only have to worry about bit depth, and we take care of that for you by promoting everything to the same bit depth. I'm not sure about FCP.
Okay, good to know. So I get floating point images within Motion if the image that my effect is applied to is 8 bit, and the image in my clipwell is floating point (can this happen with Motion? I’m unclear whether floating point/8Bit is a project setting or a per-clip setting). Can this go into the doc?
Pete
_______________________________________________
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