I think that autosave function is used 90% of the time as a test renders.
If the frame stamp is checked, in the autosave renders I don’t see it. Not very useful…
Is it a bug or it’s a “feature”? If it’s a feature, I would like to have an option to turn off/on the Frame stamp also in the BAK.
Thanks
when the stamp is included, somebody complains, when the stamp is not included, somebody else complains… 
Autosave function is to prevent data loss in case something crashes, and in these situations you do not want the stamp, so I will keep without the stamp
Oook! I understand! =) But, a checkbox (ON-OFF) for… everybody? =)
I was about to write that just adding the apropriate render element “CInfo_RenderStamp” would easily solve this but it´s like this: all render elements get stored in the autosave exr but not the renderstamp render element? For what reason?
Edit: It´s not even part of the exr when using exr dump from cVFB. But it is present when doing a cVFB “Save All”
Complaining 
Good Luck
it is because the renderstamp can be extracted without the need to store entire new render pass (it is saved as EXR metadata). We are working on a standalone viewer that will be able to extract it
Ah, thanks, yes. That´s also the reason the stamp does not affect VFB memory at all.
ProEXR lists the Corona EXR attributes very well btw. Would be nice to see all
corona.stats.*
corona.colorMapping.*
corona.renderstamp
metadata also in EXRs saved by Max some day, would be very usefull. If that´s even possible.
Good Luck
Will this viewer be able to do denoising (i think it was mentioned somwhere, but i can’t find it). That would be amazing. Tried to denoise 6k pano today, but max crashed due to insufficient ram. Standalone app would be godsend in such scenario.
yes, thats the plan