"Kenneth" <kdw### [at] gmailcom> wrote:
> William F Pokorny <ano### [at] anonymousorg> wrote:
> > On 1/19/25 05:28, Kenneth wrote:
> > >
> > > for all of my usual .png renders in 3.8 beta 1,
> > > Ive's IC app reports them as having the correct sRGB embedded gamma.
> >
> > When I use the command:
> >
> >    p380b2 material_map_tester_kw.pov file_gamma=srgb
> >
> > [The srgb block is] not there by
> > default and should be (and for a LONG while it was. It should be there
> > in v3.7 renders, for example). Our default gamma handling in v3.8 is srgb.
> >
>
> Ah, I see what you mean now. Yes, if I leave out an explicit File_Gamma=srgb
> when running a render in 3.8 beta 1, Ive's IC reports the image as having a
> 'vanilla' 2.2 gamma instead, when it should be srgb 'by default'.
>

My apologies, Willaim: I mis-quoted your reply, which probably made my own reply
a bit confusing. It should have been the following:

[Kenneth:]
for all of my usual .png renders in 3.8 beta 1,
Ive's IC app reports them as having the correct sRGB embedded gamma.
   {because I use an explicit File_Gamma=srgb]

[William:]
When I use the command:

        p380b2 material_map_tester_kw.pov file_gamma=srgb

I get an output file size of 6638 - because the srgb block has been
added with the latter command (13 bytes larger). It's not there by
default and should be (and for a LONG while it was. It should be there
in v3.7 renders, for example). Our default gamma handling in v3.8 is srgb.

[Kenneth:]
Ah, I see what you mean now. Yes, if I leave out an explicit File_Gamma=srgb
when running a render in 3.8 beta 1, Ive's IC reports the image as having a
'vanilla' 2.2 gamma instead, when it should be sRGB 'by default'.

-----
When running 'official' v3.7.0 instead, the 'default' File_Gamma is indeed sRGB,
as you mentioned.

Post a reply to this message