Re: [Openexr-devel] Established deep data file extension?

[Jon Wadelton]

The deep readers are independent of the regular readers so its fine to
use .exr for both.  That being said the file chooser can't currently
work out whether to create a DeepRead or regular Read if the filename
just has an .exr extension.  A different file extension would help us
here to create the correct read without having to open up the file and
peek at the headers.

Longer term Nuke may want to do something cleverer when opening exr
files in general.  It could for instance loop through all the parts
within the file and produce different DeepReads or Reads per part
instead of just assuming there is one type of data per file.

On Sat, Jul 21, 2012 at 2:29 AM, Christopher Horvath
<address@hidden> wrote:
> The Nuke mechanism for finding Deep files works by extension at the moment,
> so it will be hard if they're not called something like .dexr or .dsxr or
> something different from .exr (I think, but of course the Foundry folks here
> can correct me)
>
>
>
> On Fri, Jul 20, 2012 at 12:25 AM, Christian Bloch <address@hidden> wrote:
>>
>> Completely agree.
>>
>> As somebody who was watching EXR usage grow in the photography field, and
>> actively pushing for it, I think a standardized secondary extension will be
>> very helpful. Otherwise it runs into the danger of turning into a minefield
>> like TIF. Fine when it's optional, but it should not grow wild.
>>
>> DXR and SXR sound logical to me, but your point about the audible
>> similarity and possible miscommunications is a good one. It's just that I
>> wouldn't know anything better. ODZ just sounds like an oddball. I've already
>> forgotten what it stands for…  The good part about the *XR notation is, that
>> I can stumble over a forgotten file like that in 5 years and will remember
>> that it's a flavor of EXR, and if I happen to have no VFX software here I
>> can rename it and have a peek in a (thankfully already) huge amount of
>> programs.
>>
>> Blochi
>>
>>
>> On Jul 19, 2012, at 10:07 PM, Peter Hillman wrote:
>>
>> > Now's the chance to define what that is, so we only end with one
>> > alternate extension. The argument about if and where that alternative 
>> > should
>> > be used is a different discussion, isn't it?
>>
>>
>> _______________________________________________
>> Openexr-devel mailing list
>> address@hidden
>> https://lists.nongnu.org/mailman/listinfo/openexr-devel
>
>
>
>
> --
> I think this situation absolutely requires that a really futile and stupid
> gesture be done on somebody's part. And we're just the guys to do it.
>
> _______________________________________________
> Openexr-devel mailing list
> address@hidden
> https://lists.nongnu.org/mailman/listinfo/openexr-devel
>



-- 
Jon Wadelton, Nuke Product Manager.
The Foundry, 6th Floor, Communications Building
48 Leicester Square London, WC2H 7LT,
Tel: +44 (0)20 7968 6828 •  Fax: +44 (0)20 7930 8906•  Web: www.thefoundry.co.uk

The Foundry Visionmongers Ltd • Registered in England and Wales No: 4642027