Apple

On Jun 6, 2007, at 5:04 PM, Peter Litwinowicz wrote:

Okay,

So there are several formats of images that FxPlug supports:

RGBA/ARGB 8 bit
RGBA/ARGB floating point
r408, YUV+A 8 bit
R4fl, YUV+A floating point

For Motion and FCP: lets say I return false for canDoSOftware and canDoHardware when given a floating point RGBA image in frameSetup. Will either Motion or FCP then try RGBA 8bit?

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.

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.

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?

References:
	>image formats for rendering, etc. (From: Peter Litwinowicz <email@hidden>)