> sgi would be a definite alternative, unfortunately xsi doesn't support 32-bit .sgi files.
There isn't really a floating point variation of .SGI file. It's 8 or 16-bit format as defined by SGI in the early 90s.
OpenEXR for its part doesn't support 16-bit images, it's only a 32-bit floating point. The 16-bit they do is only a compression scheme, it's not the same kind of 16-bit as TIFF or SGI 16-bit. It's like how JPEG store the image in YUV, it's an internal storage matter, something they use to compress 32-bit floating point values. So OpenEXR only support one format, float.
For Tiff, it does support all variations, but it's not necessarily obvious to centralize on it because there are many compression schemes, and due to patent issues and different versions of the library itself, the applications often can't talk to each other. Mental Ray for example won't support LZW (which is the default of Photoshop) and some other compressions, and most applications do not understand each other's floating point format because they are so new. When using Tiff, Photoshop will sometime do color adjustement for display or can create TIFF in channel format that other apps cannot interpret like CMYK. (Adobe created the Tiff format) Stuff it won't do with other files formats.
IMO, it's a good idea to use with SGI for 8 and 16 bit, and OpenEXR for float. (OpenEXR is too slow to be used for 8 and 16-bit images).
------------------
Luc-Eric Rousseau
Team Leader, User Interface
Softimage|XSI
> -----Original Message-----
> From: owner-xsi(at)Softimage.COM
> [mailto:owner-xsi(at)Softimage.COM]On Behalf
> Of Greg Smith
> Posted At: Wednesday, December 14, 2005 7:30 PM
> Posted To: xsi
> Conversation: 16 Bit Images - XSI vs Photoshop CS
> Subject: Re: 16 Bit Images - XSI vs Photoshop CS
>
>
> Aside from OpenExr, tiff is really the only other format
> supported by XSI
> that has both 16 and 32 bit support. I believe its easier to
> standardize on
> one format rather than having multiple file types. .sgi would
> be a definite
> alternative, unfortunately xsi doesn't support 32-bit .sgi files.
>
> Greg
>
>
> ----- Original Message -----
> From: "Eric Lampi" <ericlampi(at)yahoo.com>
> To: <XSI(at)Softimage.COM>
> Sent: Wednesday, December 14, 2005 4:06 PM
> Subject: Re: 16 Bit Images - XSI vs Photoshop CS
>
>
> > Any advantage using 16-bit .tif as opposed to .sgi?
> >
> >
> > E
> >
> > --- brad <brad(at)cg-soup.com> wrote:
> >
> > > Yes, we too have been seeing the same issue. Our
> > > quick fix was to run the images through the fx tree.
> > > Softimage are aware of the problem. I'll leave it to
> > > them to talk about a fix.
> > >
> > > -Brad
> > >
> > > > -------Original Message-------
> > > > Hey all,
> > > >
> > > >
> > > > Has anyone been successful recently in loading 16
> > > bit .sgi or .tif
> > > > images into Photoshop CS coming straight out of
> > > XSI ? I'm always
> > > > getting an error saying there's a problem with
> > > the 'file
> > > > format module interface'.
> > > >
> > > >
> > > > And I can't seem to figure out where the problem
> > > comes from. Has
> > > > Xsi changed anything in the way it outputs 16 bit
> > > images or is it
> > > > Photoshop CS that's changed in the way it reads
> > > 16 bit images ?
> > > >
> > > >
> > > > I can take a rendered 16bit .tif image out of XSI
> > > and load it no
> > > > problem in Shake. If I re-render it from Shake in
> > > 16bit .tif then I can
> > > > load it in Photoshop.
> > > >
> > > >
> > > > Going round'n round,
> > > >
> > > >
> > > > -=mb.
> > >
> > > ---
> > > Unsubscribe? Mail Majordomo(at)Softimage.COM with the
> > > following text in body:
> > > unsubscribe xsi
> > >
> >
> >
> > Freelance 3-D Animator, F/X Artist, Particle Man
> >
> > ---
> > Unsubscribe? Mail Majordomo(at)Softimage.COM with the
> following text in body:
> > unsubscribe xsi
> >
>
>
> ---
> Unsubscribe? Mail Majordomo(at)Softimage.COM with the following
> text in body:
> unsubscribe xsi
>
---
Unsubscribe? Mail Majordomo(at)Softimage.COM with the following text in body:
unsubscribe xsi
