POV-Ray : Newsgroups : povray.general : 3.5, +C corrupts PNG files Server Time
18 Nov 2024 17:17:15 EST (-0500)
  3.5, +C corrupts PNG files (Message 1 to 10 of 13)  
Goto Latest 10 Messages Next 3 Messages >>>
From: Le Forgeron
Subject: 3.5, +C corrupts PNG files
Date: 24 Jul 2002 06:53:24
Message: <3D3E7BB0.8619858B@free.fr>
I do not know if this bug has already been reported, but
at least on Windows, the use of +C corrupts images files
(at least the PNG one)

Render the attached scene with:
+KI1 +KF2 +KFI1 +KFF2 +FN

Then do it again with
+KI1 +KF2 +KFI1 +KFF2 +FN +C

Povray become unable to read its own generated files!

-- 
Non Sine Numine
http://grimbert.cjb.net/
Etiquette is for those with no breeding;
fashion for those with no taste.


Post a reply to this message


Attachments:
Download 'read.pov.txt' (2 KB)

From: TinCanMan
Subject: Re: 3.5, +C corrupts PNG files
Date: 24 Jul 2002 07:46:17
Message: <3d3e9389$1@news.povray.org>
Before you get flamed to harshly by someone else, you should not use
attachments in this group, no matter how small, use one of the binary
groups.

-tgq


Post a reply to this message

From: Jan Walzer
Subject: Re: 3.5, +C corrupts PNG files
Date: 25 Jul 2002 13:13:43
Message: <3d4031c7$1@news.povray.org>
sounds like the thing, that I reported here:

http://news.povray.org/povray.beta-test/25268/

I never got an answer to this ...


Post a reply to this message

From: Le Forgeron
Subject: Re: 3.5, +C corrupts PNG files
Date: 26 Jul 2002 06:11:47
Message: <3D41205D.52EE93AA@free.fr>
Jan Walzer wrote:
> 
> sounds like the thing, that I reported here:
> 
> http://news.povray.org/povray.beta-test/25268/

Yes, it seems to be the same.

> I never got an answer to this ...

You did not provide a scene... No scene, no gain ?


Post a reply to this message

From: Jan Walzer
Subject: Re: 3.5, +C corrupts PNG files
Date: 26 Jul 2002 07:54:08
Message: <3d413860@news.povray.org>
> You did not provide a scene... No scene, no gain ?

This is independent of a scene, isn't it?

so take this:

//----------------
sphere {0,1,pigment{color rgb 1}finish{reflection 0.8 diffuse 0.1}}
plane {y,-1 pigment {checker color rgb 1 color rgb 0}}
light_source {10, color rgb 1}
//----------------


should _THIS_ be the reason ?


Post a reply to this message

From: Philippe Lhoste
Subject: Re: 3.5, +C corrupts PNG files
Date: 26 Jul 2002 10:56:31
Message: <3d41631f@news.povray.org>

3d413860@news.povray.org...
>
> > You did not provide a scene... No scene, no gain ?
>
> This is independent of a scene, isn't it?
>
> so take this:
>
> //----------------
> sphere {0,1,pigment{color rgb 1}finish{reflection 0.8 diffuse 0.1}}
> plane {y,-1 pigment {checker color rgb 1 color rgb 0}}
> light_source {10, color rgb 1}
> //----------------

Untested, uh? Your sphere is a little on the way of sight :-)
I would made it:

sphere { <0, 0, 3>, 1 pigment { color rgb 1 } finish { reflection 0.8
diffuse 0.1 } }
plane { y, -1 pigment { checker color rgb 1 color rgb 0 } }
light_source { 10, color rgb 1 }

(I like to space my code :-)

OK, I render it as 1280x1024 AA 0.3 PNG output, stop it in the middle
(Alt+G). I add +C, restart: preview display quickly the done job and
calculate the remainder. Again, OK. The intermediate PNG images are even
displayed OK by IrfanView.
So, no problem for me on WinNT4.

Mmm, however, I got two rendered files (seemingly identical) and a message
indicating it wasn't able to open the original file, so it was creating a
new one.
This can be related to WinNT file access problem I have sometime (ie. a file
is locked even after the end of the locking program).

Regards.

-- #=--=#=--=#=--=#=--=#=--=#=--=#=--=#=--=# --
Philippe Lhoste (Paris -- France)
Professional programmer and amateur artist
http://jove.prohosting.com/~philho/


Post a reply to this message

From: Jan Walzer
Subject: Re: 3.5, +C corrupts PNG files
Date: 27 Jul 2002 12:20:52
Message: <3d42c864@news.povray.org>
> OK, I render it as 1280x1024 AA 0.3 PNG output, stop it in the middle
> (Alt+G). I add +C, restart: preview display quickly the done job and
> calculate the remainder. Again, OK. The intermediate PNG images are even
> displayed OK by IrfanView.
> So, no problem for me on WinNT4.
>
> Mmm, however, I got two rendered files (seemingly identical) and a message
> indicating it wasn't able to open the original file, so it was creating a
> new one.
> This can be related to WinNT file access problem I have sometime (ie. a file
> is locked even after the end of the locking program).

This doesn't show the prob I mean ...

Don't stop the image in the middle of the render...

Let it render once, completely!
then render it again with the +c switch ...

afterwards the original file got corrupted.


Post a reply to this message

From: Philippe Lhoste
Subject: Re: 3.5, +C corrupts PNG files
Date: 29 Jul 2002 07:05:46
Message: <3d45218a@news.povray.org>
"Jan Walzer" <jan### [at] lzernet> wrote:
> > OK, I render it as 1280x1024 AA 0.3 PNG output, stop it in the middle
> > (Alt+G). I add +C, restart: preview display quickly the done job and
> > calculate the remainder. Again, OK. The intermediate PNG images are even
> > displayed OK by IrfanView.
> > So, no problem for me on WinNT4.
> >
> > Mmm, however, I got two rendered files (seemingly identical) and a
message
> > indicating it wasn't able to open the original file, so it was creating
a
> > new one.
> > This can be related to WinNT file access problem I have sometime (ie. a
file
> > is locked even after the end of the locking program).
>
> This doesn't show the prob I mean ...
>
> Don't stop the image in the middle of the render...
>
> Let it render once, completely!
> then render it again with the +c switch ...
>
> afterwards the original file got corrupted.

Oh, I though +C was to continue rendering on an unfinished image...
Well, sorry, but the two images produced are still readable by IrfanView.
How are they supposed to be corrupted?

Mmm, did further testing... Two renderings without +C give the same file.
Between normal and +C rendering, the files are different (compared with FC
/b). IrfanView (3.70) and SlowView (0.9.9.5) read the +C files OK, XnView
(1.31) chokes on these. So there is indeed something...

-- #=--=#=--=#=--=#=--=#=--=#=--=#=--=#=--=# --
Philippe Lhoste (Paris -- France)
Professional programmer and amateur artist
http://jove.prohosting.com/~philho/


Post a reply to this message

From: Felix Wiemann
Subject: Re: 3.5, +C corrupts PNG files
Date: 29 Jul 2002 09:55:05
Message: <3d454939@news.povray.org>
Jan Walzer wrote:

> http://news.povray.org/povray.beta-test/25268/

I can confirm this. You don't even need an animation:

povray -iscene +FN
povray -iscene +FN +C

POV-Ray produces broken image files with every format except PPM (it 
doesn't recognize the existing file [1]) and BMP (can't test it on my Linux 
system).

[1] Warning: Cannot open continue trace output file. Opening new output 
file /home/felix/pov/images/scene.ppm.

-- 
light_source{0#macro L(K,H,W)sphere{H.5}sphere{K.5}sphere{W.5}cylinder{
H,K.5}cylinder{H,W.5}#end 3}union{L(0v*-2<2,-2>)L(y*-3z-v*5z*3-y)L(-y*3
0u*3)L(y*-3v*-5-z,z*-3-y)rotate-v*clock pigment{rgb.5}translate<0,2,9>}
// +KFF200 +KF720 +W120 +H90 -F -A -GA -P


Post a reply to this message

From: Jan Walzer
Subject: Re: 3.5, +C corrupts PNG files
Date: 29 Jul 2002 13:19:58
Message: <3d45793e@news.povray.org>
"Felix Wiemann" <Fel### [at] gmxnet> schrieb im Newsbeitrag
news:3d454939@news.povray.org...
> Jan Walzer wrote:
>
> > http://news.povray.org/povray.beta-test/25268/
>
> I can confirm this. You don't even need an animation:

ahh ... at least one ...

interestingly the Win-Version seems to suffer from a different,
but seamless problem (see Philippes posts)


Post a reply to this message

Goto Latest 10 Messages Next 3 Messages >>>

Copyright 2003-2023 Persistence of Vision Raytracer Pty. Ltd.