Yes, in openexr even version number=stable and odd=unstable.

-deke

On Wed, Mar 14, 2012 at 06:30, Ivan Busquets <[email protected]> wrote:

> Hi,
>
>
> I've never heard 1.7 called unstable. It's been out for nearly 2 years
>> without the need for an update.
>>
>
> Yes, I wasn't implying that 1.7 is unstable. I was just saying that 1.6.1
> is the latest stable release "by definition", as stated here:
>
> http://www.openexr.com/downloads.html
>
>
> Other than that, I don't claim to know the design reasons for staying on a
> particular version. My point was that there are compatibility concerns that
> could play a role in that decision, specially considering that most vendors
> (afaik), have not moved to 1.7 either.
>
> With regards to 4:2:0 support, you should definitely get in touch with
> support. What I meant was that this is most likely not due to outdated exr
> libraries, but to an oversight (or intentional decision to leave it out) in
> the exrReader code.
>
> Hope that clarifies my previous answer a bit. :)
>
> Cheers,
> Ivan
>
> On Tue, Mar 13, 2012 at 2:58 PM, fnordware <
> [email protected]> wrote:
>
>> **
>> *ivanbusquets wrote:*
>> 1.6.1 is the latest stable release, and there are other reasons not to
>> move to 1.7, like the fact that exr files with long channel names are not
>> backwards compatible.
>>
>>
>> I've never heard 1.7 called unstable. It's been out for nearly 2 years
>> without the need for an update.
>>
>> I looked and you are right, 1.7 was the first actual release to support
>> the long file names, although the feature was added to the OpenEXR
>> repository in 2008. Since Nuke supports channel names longer than 32
>> characters, I'd think they'd be eager to support it in EXR instead of
>> clipping the name or whatever they do. But even if you choose not to write
>> long-channel EXRs, there's no excuse for not being able to read them.
>>
>> Between this and the 4:2:0 thing, I think it's Nuke that's the bottleneck
>> for compatibility now.
>>
>>
>> Brendan
>>
>> _______________________________________________
>> Nuke-users mailing list
>> [email protected], http://forums.thefoundry.co.uk/
>> http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
>>
>
>
> _______________________________________________
> Nuke-users mailing list
> [email protected], http://forums.thefoundry.co.uk/
> http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
>
_______________________________________________
Nuke-users mailing list
[email protected], http://forums.thefoundry.co.uk/
http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users

Reply via email to