Autosave Image to Disk question

[tar_gniK]

Hello Glare team, I hope you can help me.

When I start a render, and I specify the camera/tonemap settings (for example Ektachrome 64TCD, D50 whitepoint, ev 3.0, ISO 75), those settings do not seem to carry over in the actual autosaved image.

At the very least, the camera settings and camera preset are saved, but the whitepoint is not. On other occasions, the defaults are saved. Is this intentional? I posted a question on this some time ago, but the problem (if it is one) remains.

[Pibuz]

Following this thread.

I know some time ago I was answered that autosaving also the current layerblend state was memory consuming, but still I think that old feature should be re-introduced. It was very handy.

[tar_gniK]

Still no official response? Seeing as I have paid for this software, I would have expected something at least in the way of acknowledgement of my query. Currently rendering a scene, and the problem is still there...

See screenshot below. Right is auto-saved image, which is clearly different to what I have specified. In most situations, this doesn't concern me, as I save from the GUI anyway.

On other occasions, where I have started a render, closed it (maybe if I am not happy with something), but then changed my mind, the auto-save is useful but I don't understand the point if the image generated is useless for my needs. This problem was not present in the 2.xx versions, AFAIK.

[ENSLAVER]

It is the weekend =P


I am guessing they can probably just add a checkbox for this option.

[Pibuz]

I supposed that too

http://www.indigorenderer.com/forum/vie ... =5&t=11379

[fused]

Which version of Indigo are you using?

[Pibuz]

3.4.12 at the moment.

Are you saying that you re-arranged something in the latest?

[tar_gniK]

Same as Pibuz, 3.4.12.

[fused]

I had a look at it and auto image saving *seems* to work as intended. I tested light layers, whitepoint and tonemapping.

I think what you might be running into is that the image isn't saved imediately after changing any setting, but that it's saved in fixed intervals.

This is defined by the <image_save_period> setting in the Indigo scene file, or (most likely) "Image save period" in you exporter (if available). The default value is 60 seconds.

Cheers!

[fused]

3.4.12 at the moment.

Are you saying that you re-arranged something in the latest?

I fixed the problem with layer settings being ignored in 3.4.7:

* Fixed some tonemapping changes not being applied for automatic image saving.

[Pibuz]

Very cool.
Gonna test that. Thanks!

[tar_gniK]

Thanks very much for the reply.

Just tested this further, and it seems that if you specify the camera settings within the exporter (in my case Maxigo 3.07) the auto-save is correct. However, if I change the whitepoint, the auto-save is not updated. Screenshot below: I specified Ektachrome 64TCD with E whitepoint from the exporter. I changed it within Indigo to D55, but the auto-save stays as the default.

Strangely enough, if you change the camera preset, the auto-save updates. The whitepoint does not.

I'm no expert on these things, but possibly a bug somewhere? I should add that this is irrespective of the image auto-save period.

[Pibuz]

..hmm: yes I can confirm the behaviour. The auto-save operation takes into account the settings of the export application. If I change something during the rendering, the current image state is not autosaved as I see it on the Indigo GUI.

[pixie]

Perhaps if you save the scene it helps?

[tar_gniK]

Just installed 3.4.13 from .12 and autosave works correctly. Maybe I should have tried that first.