Re: v2.0.0.0 (GM) release announcement

--===============5153045841929537261==
Content-Type: multipart/alternative; boundary=089e013c7204ed57a304d9f67178

--089e013c7204ed57a304d9f67178
Content-Type: text/plain; charset=ISO-8859-1

Yes, thank you Piotr and all else involved for all your work and effort.
This was quite the journey.. I almost want to say an unexpected one :)

S


On Wed, Apr 10, 2013 at 9:19 AM, Christopher Horvath
<[email protected]>wrote:

> Whoo hoo!!!!!
>
> Congratulations, everyone! This is great.
>
>
> On Tue, Apr 9, 2013 at 2:10 PM, Piotr Stanczyk <[email protected]> wrote:
>
>>  Hi All,
>>
>> Tuesday, April 9th, 2013
>>
>> OpenEXR v2.0.0 has been released and is available for download.
>>
>> The release includes a number of new features that align with the major
>> version number increase. Amongst the major improvements are:
>>
>>    1. *Deep Data support* - Pixels can now store a variable-length list
>>    of samples. The main rationale behind deep images is to enable the storage
>>    of multiple values at different depths for each pixel. OpenEXR 2.0 supports
>>    both hard-surface and volumetric representations for Deep Compositing
>>    workflows.
>>    2. *Multi-part Image Files* - With OpenEXR 2.0, files can now contain
>>    a number of separate, but related, data parts in one file. Access to any
>>    part is independent of the others, pixels from parts that are not required
>>    in the current operation don't need to be accessed, resulting in quicker
>>    read times when accessing only a subset of channels. The multipart
>>    interface also incorporates support for Stereo images where views are
>>    stored in separate parts. This makes stereo OpenEXR 2.0 files significantly
>>    faster to work with than the previous multiview support in OpenEXR.
>>    3. *Optimized pixel reading* - decoding RGB(A) scanline images has
>>    been accelerated on SSE processors providing a significant speedup when
>>    reading both old and new format images, including multipart and multiview
>>    files.
>>    4. *Namespacing *- The library introduces versioned namespaces to
>>    avoid conflicts between packages compiled with different versions of the
>>    library.
>>
>>
>> Further information regarding the release, as well as tarball downloads,
>> please visit:
>>   http://www.openexr.com
>>
>> For the developer community: the source code has been tagged as "
>> v2.0.0.GM" and the master branch is now pointing to this.
>>   https://github.com/openexr/openexr
>>
>>
>> Many thanks for your continued support in making OpenEXR a success.
>>
>>
>> Piotr Stanczyk
>>
>> _______________________________________________
>> Openexr-devel mailing list
>> [email protected]
>> 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
> [email protected]
> https://lists.nongnu.org/mailman/listinfo/openexr-devel
>
>

--089e013c7204ed57a304d9f67178
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Yes, thank you Piotr and all else involved for all your wo=
rk and effort. This was quite the journey.. I almost want to say an unexpec=
ted one :)=A0<div><br></div><div style>S</div></div><div class=3D"gmail_ext=
ra">
<br><br><div class=3D"gmail_quote">On Wed, Apr 10, 2013 at 9:19 AM, Christo=
pher Horvath <span dir=3D"ltr">&lt;<a href=3D"mailto:[email protected]"=
 target=3D"_blank">[email protected]</a>&gt;</span> wrote:<br><blockquo=
te class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc so=
lid;padding-left:1ex">
<div dir=3D"ltr">Whoo hoo!!!!!<div><br></div><div>Congratulations, everyone=
! This is great.</div></div><div class=3D"gmail_extra"><br><br><div class=
=3D"gmail_quote"><div><div class=3D"h5">On Tue, Apr 9, 2013 at 2:10 PM, Pio=
tr Stanczyk <span dir=3D"ltr">&lt;<a href=3D"mailto:[email protected]" targ=
et=3D"_blank">[email protected]</a>&gt;</span> wrote:<br>

</div></div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;bo=
rder-left:1px #ccc solid;padding-left:1ex"><div><div class=3D"h5">




<div>
<div style=3D"direction:ltr;font-size:10pt;font-family:Tahoma">Hi All,
<br>
<br>
Tuesday, April 9th, 2013<br>
<br>
OpenEXR v2.0.0 has been released and is available for download.=A0 <br>
<p>The release includes a number of new features that align with the major =
version number increase. Amongst the major improvements are:</p>
<ol>
<li><strong>Deep Data support</strong> - Pixels can now store a variable-le=
ngth list of samples. The main rationale behind deep images is to enable th=
e storage of multiple values at different depths for each pixel. OpenEXR 2.=
0 supports both hard-surface and
 volumetric representations for Deep Compositing workflows.</li><li><strong=
>Multi-part Image Files</strong> - With OpenEXR 2.0, files can now contain =
a number of separate, but related, data parts in one file. Access to any pa=
rt is independent of the others, pixels from parts that are not required in=
 the current operation
 don&#39;t need to be accessed, resulting in quicker read times when access=
ing only a subset of channels. The multipart interface also incorporates su=
pport for Stereo images where views are stored in separate parts. This make=
s stereo OpenEXR 2.0 files significantly
 faster to work with than the previous multiview support in OpenEXR.</li><l=
i><strong>Optimized pixel reading</strong> - decoding RGB(A) scanline image=
s has been accelerated on SSE processors providing a significant speedup wh=
en reading both old and new format images, including multipart and multivie=
w files.</li>

<li><strong>Namespacing </strong><font face=3D"Verdana, Arial, Helvetica, s=
ans-serif">- The library introduces versioned namespaces to avoid conflicts=
 between packages compiled with different versions of the library.</font></=
li>

</ol>
<br>
Further information regarding the release, as well as tarball downloads, pl=
ease visit:<br>
=A0 <a href=3D"http://www.openexr.com" target=3D"_blank">http://www.openexr=
.com</a><br>
<br>
For the developer community: the source code has been tagged as &quot;<a hr=
ef=3D"http://v2.0.0.GM" target=3D"_blank">v2.0.0.GM</a>&quot; and the maste=
r branch is now pointing to this.<br>
=A0 <a href=3D"https://github.com/openexr/openexr" target=3D"_blank">https:=
//github.com/openexr/openexr</a><br>
<br>
<br>
Many thanks for your continued support in making OpenEXR a success.<span><f=
ont color=3D"#888888"><br>
<br>
<br>
Piotr Stanczyk<br>
</font></span></div>
</div>

<br></div></div>_______________________________________________<br>
Openexr-devel mailing list<br>
<a href=3D"mailto:[email protected]" target=3D"_blank">Openexr-devel=
@nongnu.org</a><br>
<a href=3D"https://lists.nongnu.org/mailman/listinfo/openexr-devel" target=
=3D"_blank">https://lists.nongnu.org/mailman/listinfo/openexr-devel</a><br>
<br></blockquote></div><span class=3D"HOEnZb"><font color=3D"#888888"><br><=
br clear=3D"all"><div><br></div>-- <br>I think this situation absolutely re=
quires that a really futile and stupid gesture be done on somebody&#39;s pa=
rt. And we&#39;re just the guys to do it.
</font></span></div>
<br>_______________________________________________<br>
Openexr-devel mailing list<br>
<a href=3D"mailto:[email protected]">[email protected]</a><br=
>
<a href=3D"https://lists.nongnu.org/mailman/listinfo/openexr-devel" target=
=3D"_blank">https://lists.nongnu.org/mailman/listinfo/openexr-devel</a><br>
<br></blockquote></div><br></div>

--089e013c7204ed57a304d9f67178--


--===============5153045841929537261==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Openexr-devel mailing list
[email protected]
https://lists.nongnu.org/mailman/listinfo/openexr-devel

--===============5153045841929537261==--