Re: [Openexr-devel] Photoshop Plug-In Source posted to CVS

[Paul Schneider]

It just has the simple exposure and gamma controls that you find in 
EXRViewer.  It also produces 16-bit integers, not 8-bit.  Of course, 
the current version of Photoshop isn't very useful in 16-bit mode, but 
the hope is that for most images, 16-bit integer pixels will give you 
enough room to do what you need.  If you need to paint, and you're 
willing to throw away data, once the 16-bit ints are in Photoshop, you 
should be able to do whatever tricky levels adjustment or log encoding 
you deem best for downsampling to 8 bits.

It's also hoped that this code will serve as good reference for those 
wishing to provide EXR support for other packages.  It also 
demonstrates how to use the CodeWarrior and Visual Studio projects that 
were posted awhile ago, which might be helpful.

I forgot to mention that the source comes with html documentation 
describing how to use the plug-in, which is aimed at end users and will 
be available on openexr.com once we get our network issues straightened 
out.  This doc tries to make it clear that you will lose data if you 
bring an image into Photoshop, and offers some suggestions for 
minimizing the loss.  It's far from foolproof, but we're hoping that 
this tool finds its way into the hands of folks who understand how to 
make use of it despite its limitations.  I'm also hoping that things 
like this will convince Adobe to beef up Photoshop's 16-bit 
capabilities, to be honest.

- Paul

On Friday, May 16, 2003, at 09:44 AM, Charles Henrich wrote:

> How does it handle conversion from float to 8 bit int?
>
> > I've posted the source for a Photoshop File Format plug-in that reads 
> > and
> > writes OpenEXRs to the CVS tree.  It's in a module called "Photoshop".
> > We're having trouble with Savannah's site, so we haven't made the 
> > built
> > plug-ins available for download yet, but I'd appreciate it if a few 
> > of you
> > would grab this, try to build it, and let me know how it goes.  There 
> > are a
> > few serious limitations with this plug-in; the most glaring is that it
> > doesn't work with sequences correctly in After Effects.  If anyone 
> > would
> > like to volunteer to fix this up, or make an AEIO based on this code, 
> > get in
> > touch with me.
>
>        Charles Henrich                                   
> address@hidden
>
>                          http://www.sigbus.com/~henrich