Indigo Renderer Forum

Hey folks...

I just had an Issue using Resume rendering, where the resumed Image get worser than the original one.
Also the Color get darker... here an animated GIF to show what I'm talking about:



This is an Dermis/Epidermis Skin Test I'm rendering atm, resumed after a 43h marathon for another 6h.
As you can see it will still need some more days :-/

After recognizing this, I closed the rendering, and executed the same .bak I used to start this resume rendering before,
so it started again from the 43h image, and now the resuming seems rendering fine!

You can get the whole Package with boath igs, igi and meshes etc. zipped here (8,5MB)

Also, on the subject of resuming, I'd like to see the elapsed time log output corrected.
how about something like
?

also, the samples/sec is calculated incorrectly because of indigo not knowing the current total elapsed time.

+1 dougal2!!!!
Ono....pleeease......

yeah especially samples per second is wrong and you cant calculate youself when a continued render may reach 2000 samples for example.

cant be that hard to save timing/spp things in the igi file !!!

Yep. Problems here too using version 1.0.5.2.

After resuming my render, indigo seems to move the original image about 10 pixels or so. Every shadow and line appear twice after a certain time...

Have to start all over agian .

ViennaLinux wrote:yeah especially samples per second is wrong and you cant calculate youself when a continued render may reach 2000 samples for example.

cant be that hard to save timing/spp things in the igi file !!!

I'd like to see something like exif data in the produced image files with all the interesting informations like the used settings, indigo version, rendertime, etc., how about that?

Hey Phoenix...

Just create a cmd file with the following text:
place this cmd file inside your Indigo render folder and just drag&Drop your png's inside it, to read all metadata.
(a separate txt file gets generated with all the infos!)

Good idea ZomB, but it will not work this way because the "WorkingDir"
will be wrong. It should be like this instead ...
Fill in your Path to indigo and get ready.




take care
psor

Oh, I'm really sorry... I forgot to remove the /d.
So the correct code is:
As I adviced this cmd file is to place inside your indigo render folder,
so a simple ..\ jumps into the main Indigo folder where the indigo_console.exe is.

No need for absolute paths psor... it works this way fine!

Sorry to say that ZomB, but it doesn't work here!

And if I check what happens, then I clearly see, that the shell
tries to change the directory from my home directory instead
the Indigo "render" directory, so "..\" does not work in this
case. Maybe I'm missing something mate! ;o))

edit: btw. I think it is better to use "%~n1" instead of "%~s1".

Anyway, this works for sure, at least for me. Of course you guys can
use what works for you!



take care
psor

Is this what you need?

Indigo Renderer v1.0.5, Windows 32-bit Release build.
SSE present.
SSE2 present.
SSE3 present.
------------ Metadata --------------
Indigo version used: Indigo Renderer v1.0.5, Windows 32-bit Release build.
bidirectional: 1
height: 600
hybrid: 0
large_mutation_prob: 0.40000
max_change: 0.01000
max_num_consec_rejections: 500
maxdepth: 10000
metropolis: 1
num_samples: 2206610000.00000
num_threads: 1
ray_origin_nudge_distance: 0.00001
render time elapsed: 2041.05246
samples_per_pixel: 4597.10417
samples_per_sec: 1081113.80677
scene_file_path: C:\Program Files\indigo_v1.0.5.2\default.igs
super_sample_factor: 2
width: 800

Qualia wrote:Yep. Problems here too using version 1.0.5.2.

After resuming my render, indigo seems to move the original image about 10 pixels or so. Every shadow and line appear twice after a certain time...

Have to start all over agian .

I'm still interested, why this happens to you. Never did happen to me tho.





take care
psor

Qualia wrote:Is this what you need?

Indigo Renderer v1.0.5, Windows 32-bit Release build.
SSE present.
SSE2 present.
SSE3 present.
------------ Metadata --------------
Indigo version used: Indigo Renderer v1.0.5, Windows 32-bit Release build.
bidirectional: 1
height: 600
hybrid: 0
large_mutation_prob: 0.40000
max_change: 0.01000
max_num_consec_rejections: 500
maxdepth: 10000
metropolis: 1
num_samples: 2206610000.00000
num_threads: 1
ray_origin_nudge_distance: 0.00001
render time elapsed: 2041.05246
samples_per_pixel: 4597.10417
samples_per_sec: 1081113.80677
scene_file_path: C:\Program Files\indigo_v1.0.5.2\default.igs
super_sample_factor: 2
width: 800

Thank you ZomB, psor and Qualia!

Indeed this is an approach of what I have in mind and I didn't knew that some kind of metadata support was included meanwhile.

But I was thinking about something closer to the informations that most digicams link to the pictures shot by them.

And as we use a virtual camera in Indigo, especially the informations about the camera parameters like the white point, f-stop, sensor width, exposure duration and so on could be also very useful in my opinion.

And if it even would be stored as EXIF metadata you could use it the same way like the EXIF informations from a real camera. For example you can use IrfanView with the hotkey [E] to easily show/view it.

I hope I was able to state my idea?!

Phoenix wrote:

Qualia wrote:I hope I was able to state my idea?!

Yes, I got what you mean!

But ATM Indigo only stores "simple" PNG metaData.... no Exif.
But you could bump this thread, to request Camera Settings being saved in the MetaData, this is quite a very good idea!!!

hah, I've got exactly the same problem with resuming. I run Indigo on Wine, don't sure it's important here.
I tested it on two scenes. the render was in progress for several hours, then I stopped it and - after resume - rendered longer. only a few pixel changed, compared to the image I used to resume, while the sample per pixel rate was 4x bigger
I'll try how Indigo behaves after system hibernation and restart. it's builtin function doesn't work for me...