While we're on the subject - can you describe the bugs you're encountering at all Roger? Seeing as I'm moving more of my work into 16 bit, it would be good to know what to look out for (I've not encountered any so far myself). Chris
2008/6/27 Christopher Wright <[EMAIL PROTECTED]>: > I can't help with the 16/32bit image save I'm afraid, but perhaps it would >>> be possible to modify the image writer example plugin to do this? >>> >> >> I'm sure it would be but I'm a QC hacker and not an opengl / objective c >> coder so I'm hoping someone else might have already done this. >> > > Saving as 16bit png wouldn't be hard at all, provided imagekit (or > whatever) supports that -- I believe it does, but I'm not sure. > > Also, I'm not sure is placing your comp inside a "render in image" in 16 >> bit mode going to hit exactly the same rendering path and bugs as if you >> render the composition in a 16 bit context? Are they equivalent or not? >> > > Render in Image creates another context to render into -- it may not be > exactly the same path, QC-wise, but GL->16bit context path should be similar > enough to duplicate any noticed bugs. Wouldn't be difficult to whip up a > test case for this to see, would it? > > -- > [ christopher wright ] > [EMAIL PROTECTED] > http://kineme.net/ > >
_______________________________________________ Do not post admin requests to the list. They will be ignored. Quartzcomposer-dev mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/quartzcomposer-dev/archive%40mail-archive.com This email sent to [EMAIL PROTECTED]
