 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Mael wrote:
> There is a limitation in the current Read_HDR_Image function : image width
> must be < 2048 (with no test so if it s bigger => crash). It could easily
> be corrected but i do not plan to release any new mlpov version, so you'll
> have to wait for a megapov with high dynamic range images support (or
> recompile mlpov with a buffer size > 2048)
Hi Mael,
Do you *know* that the next release of MegaPov will have HDR support? It
would be very very nice!!
Andreas
--
http://www.render-zone.com
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Mael <mae### [at] hotmail com> wrote:
> (or recompile mlpov with a buffer size > 2048)
Is it really necessary to have fixed buffer sizes?
Having fixed buffer sizes (and specially if without range checks) is
the most common cause of program crashes and security holes (even though
the latter is not an extremely important issue in the case of POV-Ray).
Nowadays there shouldn't be any reason to use fixed buffer sizes.
--
plane{-x+y,-1pigment{bozo color_map{[0rgb x][1rgb x+y]}turbulence 1}}
sphere{0,2pigment{rgbt 1}interior{media{emission 1density{spherical
density_map{[0rgb 0][.5rgb<1,.5>][1rgb 1]}turbulence.9}}}scale
<1,1,3>hollow}text{ttf"timrom""Warp".1,0translate<-1,-.1,2>}// - Warp -
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
> > (or recompile mlpov with a buffer size > 2048)
> Is it really necessary to have fixed buffer sizes?
no.. (ok, so recompile mlpov with a dynamic buffer :)
the Read_HDR_Image in mlpov is mostly cut&paste from vrpic (a gtk+ hdr
viewer) source
M
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
"Mael" <mae### [at] hotmailcom> wrote in news:3e68813c$1@news.povray.org:
> I tried resizing a lightprobe with hdrshop then render it with
> map_type 7 on a sphere but no crash. What was the size of the image ?
Then it was probably because of the buffer limitation (is it only for image
width?). I mistyped and made an image 1600X2400 and it worked, while the
opposite didn't.
>
> There is a limitation in the current Read_HDR_Image function : image
> width must be < 2048 (with no test so if it s bigger => crash). It
> could easily be corrected but i do not plan to release any new mlpov
> version, so you'll have to wait for a megapov with high dynamic range
> images support (or recompile mlpov with a buffer size > 2048)
>
> M
I am sorry to hear that you will not release a new version. MlPov was a
sensation in the Terragen community. Recompiling is beyond me, I am afraid,
so: Anyone knows whether MegaPov will actually support HDR images?
Helen
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
> I am sorry to hear that you will not release a new version. MlPov was a
> sensation in the Terragen community. Recompiling is beyond me, I am
afraid,
http://195.221.122.126/tmp/mlpov83-win-bin.zip
changes in this version
-hdr_patch: no more image width limit
-hdr_patch: uses 3x less memory (keep original r,g,b,e and compute float
value when the image is used instead of computing floats at parse time)
-hdr_patch: uses the EXPOSURE parameter in the hdr header (not really
tested..)
-finish_maps: attempt to fix problems concerning transformations
I don't know if next megapov will include HDR but if so I hope it'll have a
better read function than mlpov's one (parse of informations in the header,
more robust when errors..), and support for output of HDR image..
M
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
"Mael" <mae### [at] hotmailcom> wrote in news:3e6a11f1@news.povray.org:
> http://195.221.122.126/tmp/mlpov83-win-bin.zip
That was fast!
Thank you very much.
Helen
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Mael,
Thank you for continuing your efforts on MLpov. It is a
real gift to the POV-Ray community.
Harold
"Mael" <mae### [at] hotmailcom> wrote in message
news:3e6a11f1@news.povray.org...
> > I am sorry to hear that you will not release a new version. MlPov was a
> > sensation in the Terragen community. Recompiling is beyond me, I am
> afraid,
>
> http://195.221.122.126/tmp/mlpov83-win-bin.zip
>
> changes in this version
> -hdr_patch: no more image width limit
> -hdr_patch: uses 3x less memory (keep original r,g,b,e and compute float
> value when the image is used instead of computing floats at parse time)
> -hdr_patch: uses the EXPOSURE parameter in the hdr header (not really
> tested..)
> -finish_maps: attempt to fix problems concerning transformations
>
> I don't know if next megapov will include HDR but if so I hope it'll have
a
> better read function than mlpov's one (parse of informations in the
header,
> more robust when errors..), and support for output of HDR image..
>
> M
>
>
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On Fri, 07 Mar 2003 13:09:28 +0100, Andreas Kreisig <and### [at] gmxde> wrote:
> Do you *know* that the next release of MegaPov will have HDR support?
Yes, he knows it.
ABX
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 7 Mar 2003 16:21:09 -0500, Helen <rem### [at] nospamhotmailcom>
wrote:
> Anyone knows whether MegaPov will actually support HDR images?
Yes, somebody knows it will.
ABX
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
ABX wrote:
> On Fri, 07 Mar 2003 13:09:28 +0100, Andreas Kreisig <and### [at] gmxde>
> wrote:
>> Do you *know* that the next release of MegaPov will have HDR support?
>
> Yes, he knows it.
Oh - and is he willing share his knowledge? ;-)
--
http://www.render-zone.com
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
