|
 |
"Jan Walzer" <jan### [at] lzer net> 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
|
|
