In article <3F55CBF3.EFD4665F@gmx.de> , Christoph Hormann 
<chr### [at] gmxde>  wrote:

> Generating high dynamic range output from POV-Ray is not possible
> without quite intensive modifications since POV-Ray clips colors soon
> after rendering and this prevents usable HDR output.

Which is why anybody who wants to add something like this should wait for
3.5.1 source code, which contains the necessary changes to clip much later.

>> but here is the patch so far (it is released under the terms of the GPL2
>> License http://www.gnu.org/licenses/gpl.html )
>
> Note the GPL is not compatible to the POV-Ray licence.  You can for sure
> publish your patch under GPL but no one will be allowed to distribute it
> as either complete souce or binary -> it will be quite unusable in
> practice.

Indeed, the two licenses are completely incompatible.  Distributing the
source code for one or the other of course does not create any conflicts,
but distributing the source code (or binary) as a whole would surely violate
both licenses.

    Thorsten

____________________________________________________
Thorsten Froehlich, Duisburg, Germany
e-mail: tho### [at] trfde

Visit POV-Ray on the web: http://mac.povray.org

Post a reply to this message

Thorsten Froehlich wrote:
>In article <3F55CBF3.EFD4665F[at]gmx.de> , Christoph Hormann
><chr### [at] gmxde>  wrote:
>> Generating high dynamic range output from POV-Ray is not possible
>> without quite intensive modifications since POV-Ray clips colors soon
>> after rendering and this prevents usable HDR output.

oh, thats bad!

>Which is why anybody who wants to add something like this should wait for
>3.5.1 source code, which contains the necessary changes to clip much later.

ok. I think I will wait and then rewrite my patch

>Indeed, the two licenses are completely incompatible.

ok. I will change the license in the next release.

Post a reply to this message

Ruediger,
	I'm very glad to hear that you are adding OpenEXR support! I suggest you 
use the Modified BSD License for your patch, since that is the license used 
by OpenEXR itself and would then make it compatible with POV-Ray (am I 
right, Christoph or Thorsten?).

George



On Wed,  3 Sep 2003 08:31:23 EDT, Ruediger Sonderfeld <kingruedi@c- 
plusplus.de> wrote:

> Thorsten Froehlich wrote:
>> In article <3F55CBF3.EFD4665F[at]gmx.de> , Christoph Hormann
>> <chr### [at] gmxde>  wrote:
>>> Generating high dynamic range output from POV-Ray is not possible
>>> without quite intensive modifications since POV-Ray clips colors soon
>>> after rendering and this prevents usable HDR output.
>
> oh, thats bad!
>
>> Which is why anybody who wants to add something like this should wait 
>> for
>> 3.5.1 source code, which contains the necessary changes to clip much 
>> later.
>
> ok. I think I will wait and then rewrite my patch
>
>> Indeed, the two licenses are completely incompatible.
>
> ok. I will change the license in the next release.
>
>



-- 
Using M2, Opera's revolutionary e-mail client: http://www.opera.com/m2/

Post a reply to this message

George Pantazopoulos wrote:
>Ruediger,
> I'm very glad to hear that you are adding OpenEXR support! I suggest you
>use the Modified BSD License for your patch, since that is the license used
>by OpenEXR itself and would then make it compatible with POV-Ray (am I
>right, Christoph or Thorsten?).

I will change the license to a BSD Style License in the next release. At the
moment there is a bug in the OpenEXR Support.

(exrdisplay reports:

Error reading pixel data from image file "coord.exr". Error in
Huffman-encoded data (decoded data are shorter than expected).)

when this is fixed I will release a beta version under BSD Style license.

Post a reply to this message

Thorsten Froehlich wrote:
> 
> > Generating high dynamic range output from POV-Ray is not possible
> > without quite intensive modifications since POV-Ray clips colors soon
> > after rendering and this prevents usable HDR output.
> 
> Which is why anybody who wants to add something like this should wait for
> 3.5.1 source code, which contains the necessary changes to clip much later.

Is this a very recent change or have i missed something before?  I moved
clipping to just before file writing myself for MegaPOV and did not yet
see anything from 3.5.1 conflicting with it.

-- Christoph

Post a reply to this message

In article <3F571E5F.D66C7EA4@gmx.de> , Christoph Hormann 
<chr### [at] gmxde>  wrote:

>> Which is why anybody who wants to add something like this should wait for
>> 3.5.1 source code, which contains the necessary changes to clip much later.
>
> Is this a very recent change or have i missed something before?  I moved
> clipping to just before file writing myself for MegaPOV and did not yet
> see anything from 3.5.1 conflicting with it.

No, has been in there for some time now (half a year?).

    Thorsten

____________________________________________________
Thorsten Froehlich, Duisburg, Germany
e-mail: tho### [at] trfde

Visit POV-Ray on the web: http://mac.povray.org

Post a reply to this message

On Thu, 04 Sep 2003 14:07:00 +0200, "Thorsten Froehlich" <tho### [at] trfde>
wrote:
> > > Which is why anybody who wants to add something like this should wait for
> > > 3.5.1 source code, which contains the necessary changes to clip much later.
> >
> > Is this a very recent change or have i missed something before?  I moved
> > clipping to just before file writing myself for MegaPOV and did not yet
> > see anything from 3.5.1 conflicting with it.
>
> No, has been in there for some time now (half a year?).

Then I agree it wasn't sufficient amount of changes. Christoph indeed made it
"really" working for MegaPOV 1.1 and realised it optional with:

  global_settings { clip_colors off }

Quoting our manual "The default value for this switch is on which results in
the same behaviour as POV-Ray 3.5". The difference is visible and important in
case of hdr output or camera_view pigment patches.

ABX

Post a reply to this message

In article <lpaelvk0bpuhrhjh7kclg9pgah41t28his@4ax.com> , ABX 
<abx### [at] abxartpl>  wrote:

>> No, has been in there for some time now (half a year?).
>
> Then I agree it wasn't sufficient amount of changes.

The changes were to the way anti-aliasing and clipping take place such that
anti-aliased unclipped values can be processed _internally_ in a clean
manner.  They were never meant to be useful for anything else.  Of course to
get unclipped output to a file, one still needs to apply more changes.  It
is not like this would be a feature in 3.5.1.

    Thorsten

____________________________________________________
Thorsten Froehlich, Duisburg, Germany
e-mail: tho### [at] trfde

Visit POV-Ray on the web: http://mac.povray.org

Post a reply to this message

Thorsten Froehlich wrote:
> 
> >> No, has been in there for some time now (half a year?).
> >
> > Then I agree it wasn't sufficient amount of changes.
> 
> The changes were to the way anti-aliasing and clipping take place such that
> anti-aliased unclipped values can be processed _internally_ in a clean
> manner.  They were never meant to be useful for anything else.  Of course to
> get unclipped output to a file, one still needs to apply more changes.  It
> is not like this would be a feature in 3.5.1.
> 

Then i think my changes were mostly independant from this - i did
nothing more than remove the clipping were it was and applied it later. 
It is quite a hack but in general i think having the clipping just
before file writing and not earlier is a good idea (although this of
course means you have to apply it twice when display is on).  

-- Christoph

Post a reply to this message

I finally fixed the output problem (it was caused by the problem that povray
doesn't destruct the image output objects correct!)

I changed the license to the BSD License

you can download the current Version from CVS

cvs -d:pserver:ano### [at] cvssourceforgenet:/cvsroot/mdesigner login

cvs -z3 -d:pserver:ano### [at] cvssourceforgenet:/cvsroot/mdesigner co
povray_openexr

Post a reply to this message