 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
I have a problem with windows64 version 3.7 RC1:
The image in the window POVRAY not match the saved to disk.
Am I doing something wrong or is the fault of povray?.
Thanks
P.D. sorry for my english.
Images are in P.B.I.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Le 06/01/2011 09:31, zalakainz a écrit :
> I have a problem with windows64 version 3.7 RC1:
> The image in the window POVRAY not match the saved to disk.
> Am I doing something wrong or is the fault of povray?.
> Thanks
Both png seems similar to me.
The screen capture has no gamma information, whereas the rendered one
has a gamma info of .45455 (traditional 2.2) with an histogram.
May be your visualisation program has some issue with gamma handling ?
(default for png when no gamma info is provided is 2.2, IIRC)
Try rendering to another format (+FB for bmp, +FJ for jpeg) to check.
Have you checked the message log panel ?
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Le_Forgeron <lef### [at] free fr> wrote:
> Le 06/01/2011 09:31, zalakainz a écrit :
> > I have a problem with windows64 version 3.7 RC1:
> > The image in the window POVRAY not match the saved to disk.
> > Am I doing something wrong or is the fault of povray?.
> > Thanks
>
> Both png seems similar to me.
I clearly observed bands of color in the image saved to disk.
> The screen capture has no gamma information, whereas the rendered one
> has a gamma info of .45455 (traditional 2.2) with an histogram.
Sorry, too technical for me
> May be your visualisation program has some issue with gamma handling ?
> (default for png when no gamma info is provided is 2.2, IIRC)
I used photoshop and Irfanview
> Try rendering to another format (+FB for bmp, +FJ for jpeg) to check.
yes I tried to save the image to the format. hdr. exr. bmp with the same
result
> Have you checked the message log panel ?
Preset INI file is
'C:\USERS\ADMINISTRADOR\DOCUMENTS\POV-RAY\V3.7\INI\QUICKRES.INI', section is
'[800x600, No AA]'.
Preset source file is 'C:\Users\Administrador\Documents\borrar\Exp1.pov'.
Rendering using command line 'File_Gamma=sRGB Display_Gamma=sRGB'.
Rendering with 1 thread.
Parser Options
Input file: C:\Users\Administrador\Documents\borrar\Exp1.pov
Remove bounds........On
Split unions.........Off
Library paths:
C:\Users\Administrador\Documents\POV-Ray\v3.7\scenes\camera\mesh_camera\
C:\Program Files (x86)\POV-Ray for Windows v3.6\INCLUDE
C:\Windows\Fonts
C:\Program Files (x86)\POV-Ray for Windows v3.6\INCLUDE\LightsysIV
C:\Users\Administrador\Documents\POVEXPORT
C:\Users\Administrador\Documents\POV-Ray\v3.7\include
Clock value: 0.000 (Animation off)
Image Output Options
Image resolution.....800 by 600 (rows 1 to 800, columns 1 to 600).
Output file..........C:\Users\Administrador\Documents\borrar\Exp1.png, 24 bpp
PNG
Dithering............Off
Graphic display......On (gamma: sRGB)
Mosaic preview.......Off
Continued trace......Off
Information Output Options
All Streams to console..........On
Debug Stream to console.........On
Fatal Stream to console.........On
Render Stream to console........On
Statistics Stream to console....On
Warning Stream to console.......On
Parse Warning: This rendering uses the following experimental feature(s):
radiosity. The design and implementation of these features is likely to change
in future versions of
POV-Ray. Backward compatibility with the current implementation is not
guaranteed.
Parser Statistics
Finite Objects: 2
Infinite Objects: 0
Light Sources: 1
Total: 3
Parser Time
Parse Time: 0 hours 0 minutes 0 seconds (0.000 seconds)
using 1 thread(s) with 0.000 CPU-seconds total
Bounding Time: 0 hours 0 minutes 0 seconds (0.000 seconds)
using 1 thread(s) with 0.000 CPU-seconds total
Render Options
Quality: 9
Bounding boxes.......On Bounding threshold: 3
Antialiasing.........Off
Render Statistics
Image Resolution 800 x 600
Pixels: 482505 Samples: 0 Smpls/Pxl: 0.00
Rays: 5045505 Saved: 0 Max Level: 2/5
Ray->Shape Intersection Tests Succeeded Percentage
Mesh 7061303 7061301 100.00
Sphere 104548 46978 44.93
Bounding Box 174360260 54282663 31.13
Shadow Ray Tests: 2016285 Succeeded: 0
Radiosity samples calculated: 4563 (0.95 %)
discarded due to low quality: 30
retained for re-use: 4533
Radiosity samples reused: 477942
Radiosity sample rays shot: 4563000
Radiosity octree nodes: 809
Radiosity octree samples/node: 5.64
Radiosity blocks examined: 50722920
Radiosity blocks passed test 0: 50722920 (100.00 %)
Radiosity blocks passed test 1: 6464501 (12.74 %)
Radiosity blocks passed test 2: 5877733 (11.59 %)
Radiosity blocks passed test 3: 5863918 (11.56 %)
Radiosity blocks passed test 4: 5863918 (11.56 %)
Radiosity blocks passed test 5: 5678822 (11.20 %)
Radiosity blocks rejected: 45044098 (88.80 %)
Radiosity Depth 0 calculated: 4563 (0.95 %)
Radiosity Depth 0 reused: 477942
Radiosity Depth 0 rays shot: 4563000
Radiosity (final) calculated: 2058 (0.43 %)
Radiosity (final) reused: 477942
Radiosity (final) rays shot: 2058000
Pass Depth 0 Total
1 130 130
2 475 475
3 1900 1900
Final 2058 2058
Total 4563 4563
Weight 0.800
Render Time:
Photon Time: No photons
Radiosity Time: 0 hours 0 minutes 6 seconds (6.390 seconds)
using 1 thread(s) with 6.359 CPU-seconds total
Trace Time: 0 hours 0 minutes 8 seconds (8.594 seconds)
using 1 thread(s) with 8.562 CPU-seconds total
POV-Ray finished
-
CPU time used: kernel 0.42 seconds, user 15.81 seconds, total 16.23 seconds.
Elapsed time 16.13 seconds.
Render averaged 29767.44 PPS (29566.89 PPS CPU time) over 480000 pixels.
----------------------------------------------------------------------------
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
>>> I have a problem with windows64 version 3.7 RC1:
>>> The image in the window POVRAY not match the saved to disk.
>>> Am I doing something wrong or is the fault of povray?.
>>> Thanks
>>
>> Both png seems similar to me.
>
> I clearly observed bands of color in the image saved to disk.
IIRC they added dithering to the render preview window, if you want to
add the identical dithering to the saved file use the "Dither=B4" in
your ini file. Check the beta change log for further details.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
scott <sco### [at] scottcom> wrote:
> >>> I have a problem with windows64 version 3.7 RC1:
> >>> The image in the window POVRAY not match the saved to disk.
> >>> Am I doing something wrong or is the fault of povray?.
> >>> Thanks
> >>
> >> Both png seems similar to me.
> >
> > I clearly observed bands of color in the image saved to disk.
>
> IIRC they added dithering to the render preview window, if you want to
> add the identical dithering to the saved file use the "Dither=B4" in
> your ini file. Check the beta change log for further details.
Yes, that's the case. Thanks.
What I can not understand is why this option is the default in the render
window. Cause confusion.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 01/06/2011 07:36 AM, scott wrote:
>>>> I have a problem with windows64 version 3.7 RC1:
>>>> The image in the window POVRAY not match the saved to disk.
>>>> Am I doing something wrong or is the fault of povray?.
>>>> Thanks
>>>
>>> Both png seems similar to me.
>>
>> I clearly observed bands of color in the image saved to disk.
>
> IIRC they added dithering to the render preview window, if you want to
> add the identical dithering to the saved file use the "Dither=B4" in
> your ini file. Check the beta change log for further details.
..or in your distribution documentation, reference section "Output File
Dithering" heading 3.1.2.4.4
btw: the docs included with RC1 /IS/ up to date!
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Am 06.01.2011 10:40, schrieb zalakainz:
> Le_Forgeron<lef### [at] freefr> wrote:
>> Le 06/01/2011 09:31, zalakainz a écrit :
>>> I have a problem with windows64 version 3.7 RC1:
>>> The image in the window POVRAY not match the saved to disk.
>>> Am I doing something wrong or is the fault of povray?.
>>> Thanks
>>
>> Both png seems similar to me.
>
> I clearly observed bands of color in the image saved to disk.
Yup, I see those as well.
A bit of technical background here:
With the default setting, PNG can only represent 256 different shades of
grey; POV-Ray uses much higher precision internally, but when the color
values are simply rounded to the nearest representable level of grey,
what you get is color banding.
You will most probably see the same effect with POV-Ray 3.62 - with one
difference: POV-Ray 3.6 will also show the banding in the preview,
because the display has the same 256-level limitation.
The banding no longer shows in POV-Ray 3.7's render preview because it
always uses /dithering/: By adding some randomness to the rounding, the
eye can be tricked into perceiving a smooth transition between the two
color levels.
Of course POV-Ray 3.7 also supports dithering for file output, but this
is disabled by default, as it may lead to even worse problems when
printing such an image, if the dithering method does not play nice with
the printer driver. However, it can be turned on using the command-line
parameter
+TH
(This activates Floyd-Steinberg dithering by default; you can choose
between six different modes, though in practice they're all doing a
sufficiently good job.)
Alternatively, you can choose a file format with a higher bit depth
(e.g. 16-bit PNG rather than 8-bit) or the floating-point based OpenEXR
format.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Am 06.01.2011 13:06, schrieb zalakainz:
> What I can not understand is why this option is the default in the render
> window. Cause confusion.
To switch preview output dithering on or off depending on chosen file
format, bit depth and output file dithering settings would have required
a good deal of extra effort, so output dithering is always on (it's not
the default - it's simply the one and only setting there is). The only
question was whether to turn dithering on or off by default; the
decision was to leave it off for backward compatibility, in order not to
surprise the user with increased file sizes, or problems when trying to
print POV-Ray generated images.
But I do understand your confustion - the situation is not ideal as it is.
Then again, the render preview behaviour is perfectly consistent insofar
as it matches the behaviour when you choose low-quality output settings,
such as 5-bit PNG or low-quality JPEG: In that case the preview doesn't
show you the loss of quality either.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
> btw: the docs included with RC1 /IS/ up to date!
I already notticed that. Many thanks to the devlopers :)
Alain
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
