Fredrik Eriksson wrote:
> The question is: Does the OpenEXR source compile *and work* as-is on those  
> platforms, or does "has been ported" simply mean "someone, somewhere,  
> knows what must be changed to make it work on platform X"?

I just installed KDE 3.4 on FreeBSD 5.4 and FreeBSD automatically installed
OpenEXR along with it (it is used by KDE, though I don't think it is a
requirement). From what I can tell it's also commonly used on Linux systems
with KDE installed (though I could be wrong on that). Either way its unix
support seems quite stable.

You may like to know that we have already interally discussed adding OpenEXR
and radiance RGBE support to POV 3.7 as experimental features. I can't say
when or even if it will happen, but we are at least considering it.

-- Chris

Post a reply to this message

On Fri, 13 May 2005 10:26:17 +1000, Chris Cason wrote:

> (it is used by KDE, though I don't think
> it is a requirement). From what I can tell it's also commonly used on
> Linux systems with KDE installed (though I could be wrong on that)

My RPM dependency tree here in SuSE 9.2 shows that kdegraphics3 and
kdelibs3 both require OpenEXR.

Jim

Post a reply to this message

Fredrik Eriksson wrote:
> 
> I didn't explicitly make it Windows only. I am just not completely sure 
> of  the portability of the libraries used, particularly the OpenEXR 
> library.

The libraries are certainly not the problem.

> If there is sufficient interest, I might make the effort to 
> clean up the  code and release the source, but otherwise I just don't 
> want to bother.

Well - if the program is working well there for sure would be interest.

Christoph

-- 
POV-Ray tutorials, include files, Sim-POV,
HCR-Edit and more: http://www.tu-bs.de/~y0013390/
Last updated 03 May. 2005 _____./\/^>_*_<^\/\.______

Post a reply to this message

Chris Cason wrote:
> 
> I just installed KDE 3.4 on FreeBSD 5.4 and FreeBSD automatically installed
> OpenEXR along with it (it is used by KDE, though I don't think it is a
> requirement).

kimgio includes read support for OpenEXR (so all KDE apps using standard 
mechanisms for loading images can read it, only in 8bit of course, if 
KDE is built with OpenEXR).  Note however konstruct (the tool to build 
KDE from source) does not install OpenEXR as a dependency so you have to 
explicitly install it before building to have it supported.

Christoph

-- 
POV-Ray tutorials, include files, Sim-POV,
HCR-Edit and more: http://www.tu-bs.de/~y0013390/
Last updated 03 May. 2005 _____./\/^>_*_<^\/\.______

Post a reply to this message

Alain <ele### [at] netscapenet> wrote:
> Think of 48bpp png as "extended dynamic range".

  I thought that the "dynamic" part referred to the fact that the
format uses floating point numbers (which can scale dynamically to
bigger ranges by changing the exponent part of the number). PNG only
uses integers which are mapped linearly, so there's no dynamicity
there.

-- 
                                                          - Warp

Post a reply to this message

Warp wrote:
> Alain <ele### [at] netscapenet> wrote:
> 
>>Think of 48bpp png as "extended dynamic range".
> 
> 
>   I thought that the "dynamic" part referred to the fact that the
> format uses floating point numbers (which can scale dynamically to
> bigger ranges by changing the exponent part of the number). PNG only
> uses integers which are mapped linearly, so there's no dynamicity
> there.
> 
I think precisely that what Alain meant was that while 48bpp offers a 
greater dynamic range than 24bpp (namely 511:1 instead of 255:1), it is 
far from being truely "high dynamic range" (the dynamic is 10e38:10e-38 
for .hdr, 65000:0.0000012 for .exr)...

-- 
Vincent

Post a reply to this message

Vincent LE CHEVALIER wrote:
> I think precisely that what Alain meant was that while 48bpp offers a 
> greater dynamic range than 24bpp (namely 511:1 instead of 255:1)

That's more likely 65535:1...

Christoph

-- 
POV-Ray tutorials, include files, Sim-POV,
HCR-Edit and more: http://www.tu-bs.de/~y0013390/
Last updated 03 May. 2005 _____./\/^>_*_<^\/\.______

Post a reply to this message

Christoph Hormann wrote:
> Vincent LE CHEVALIER wrote:
> 
>> I think precisely that what Alain meant was that while 48bpp offers a 
>> greater dynamic range than 24bpp (namely 511:1 instead of 255:1)
> 
> 
> That's more likely 65535:1...
> 

Wooops indeed, I should avoid posts on friday the 13th ;-)
Well anyway you got the idea : 255:1 < 65535:1 < 65000:0.0000012 < 
10e38:10e-38, in terms of dynamic range. While precision and 
quantization would be another issue...

Thanks for correcting anyway :-)

-- 
Vincent

Post a reply to this message

On Fri, 13 May 2005 09:16:16 +0200, Christoph Hormann  
<chr### [at] gmxde> wrote:
> The libraries are certainly not the problem.


Leaving the parts I've written myself...



>> If there is sufficient interest, I might make the effort to clean up  
>> the  code and release the source, but otherwise I just don't want to  
>> bother.
>
> Well - if the program is working well there for sure would be interest.


Depends on your definition of "well", but I see your point.

I guess it comes down to my own interest then; whether I can find the  
motivation to make the code presentable enough for release.



-- 
FE

Post a reply to this message

All right, I've tinkered enough with this thing now. I really don't feel  
inspired enough to continue work on the program right now, so I'll just  
release it as it is, in case anyone finds it useful.

For those that haven't been following this discussion, 'hdr2exr' is a  
program that converts image files to/from HDR, OpenEXR & PNG.

Source (excluding support libraries) at:
http://hem.bredband.net/b230591/hdr2exr/hdr2exr_source.zip

Precompiled Win32 binary at:
http://hem.bredband.net/b230591/hdr2exr/hdr2exr_win32.zip

Example image in all supported formats at:
http://hem.bredband.net/b230591/hdr2exr/hdr2exr_examples.zip



-- 
FE

Post a reply to this message