Too many people are making my point for me. You're arguing about bugs in implementations, and in some cases just misunderstandings of terminology, rather than anything inherent in the file format or the libraries used to work with those file formats.
If you are going to argue for a particular file format or library: learn the details of the format and the library and argue those points. Don't bring in "well, my 10 year old app can't read this one file, so the format must be crap", because it really isn't true or relevant. Just because some software (or titler) vendor won't fix their file format implementation bugs without being clubbed over the head by users, that doesn't mean that the problems cannot be fixed or that there is anything in the format or library itself preventing interoperation. There will always be some company that has an intern implement their file formats and doesn't want to fix them. And there will be companies that take shortcuts that come back to haunt your workflow. Unfortunately, that's life. Please, please, please stick to facts about the formats and libraries. Leave the ignorance and historical accidents out of it. Chris -----Original Message----- From: [EMAIL PROTECTED] on behalf of Deke Kincaid Sent: Fri 2/23/2007 9:25 AM To: [email protected] Subject: Re: [Openexr-user] Questions for more experienced users Exactly. I have to write out tiffs one way for Prman, another way for Mental Ray, another way for Flame/Inferno, another way for anyone on Shake for windows. Shake on Linux/Mac is the only one that seems to be able to read and write all different versions. It's frustrating, ie, I don't use tiff unless they force me to (which unfortunatly the current job exclusively uses). -deke _______________________________________________ Openexr-user mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/openexr-user _______________________________________________ Openexr-user mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/openexr-user
