Gaussian blur bug in 32bit exr render pass composition

[cgidesign]

Win 10

APhoto 2.0.4

32 bit render passes combined to a final image in APhoto

Happens with and without openCL

Cause seems to be one specific exr pass: "Volume-Test_001-Glossy direct-LPE.exr"
But why? It is a render pass like all the others.

Volume-Test_001.afphoto

Volume-Test_001-Specular indirect-LPE.exr Volume-Test_001-Transmission direct-LPE.exr Volume-Test_001-Transmission indirect-LPE.exr Volume-Test_001-Volume direct-LPE.exr Volume-Test_001-Volume indirect-LPE.exr Volume-Test_001-Beauty-LPE.exr Volume-Test_001-Diffuse direct-LPE.exr Volume-Test_001-Diffuse indirect-LPE.exr Volume-Test_001-Glossy direct-LPE.exr Volume-Test_001-Glossy indirect-LPE.exr Volume-Test_001-Specular direct-LPE.exr

[cgidesign]

Just to be on the save side:

Here is a composite made in a compositing software using similar settings and also a gausian blur. No issues here - even with the direct glossy pass.

[Chris B]

Hey cgidesign,

I've made the document from scratch using the exr's and I cannot reproduce it. However the affected layer has NaN values in it which of course transfer over to my document if I paste it in.

When you said you've tried OpenCL on and off, did you make the document from scratch or toggle it? Once the NaN values appear that's it—they're stuck and you cannot recover/fix it (to my knowledge).

I made the document from scratch with both OpenCL on and off and had no issues. 

Volume Render Test.afphoto

[cgidesign]

Thanks for testing - please check final update at bottom of post.

4 hours ago, Chris B said:

However the affected layer has NaN values in it which of course transfer over to my document if I paste it in

What does that mean? What happens if you paste it in?

4 hours ago, Chris B said:

you've tried OpenCL on and off

I have created the document with CL on -> issue happened -> saved document -> turned CL off -> restarted Aphoto -> issue still there.

4 hours ago, Chris B said:

once the NaN values appear that's it—they're stuck and you cannot recover/fix it

What does that mean? Do you say, if a document is created with CL on and this causes an issue, even when saving the document and loading it with CL off, the issue remains? Does that mean a user should never create a document with CL on because this can cause a permanent issue?

4 hours ago, Chris B said:

I made the document from scratch

Do you mind posting a screenshot of your 32-bit Preview settings?

 

This time I created the document with CL off - issue still happens.

I use "new stack" to create the document, did you do it the same way? If not, how do you create the document?

 

UPDATE:

I created the document again - this time with "open file" (first render pass) and then "place" subsequent render passes into the document. This way the issue does not happen.

Conclusion: there is something wrong with using "new stack" instead of load and place.

Can you confirm this?

[Chris B]

NaN = Not a Number. It essentially means it's missing an actual value.

I have reproduced the issue using the Stack feature so that's the bug. I will log this with the developers. So thank you very much for persisting with this!

I did build my first document using File > Open and then placed the additional EXR's on top making sure to snap and add the Add Blend Mode. I'd assumed this is what you did and didn't even try the Stack method.

[cgidesign]

Ok, thanks for confirmation - I will avoid new stack feature from now on (pity - it was the fastest way to create a pile of render passes).

[Chris B]

Just now, cgidesign said:

pity - it was the fastest way to create a pile of render passes

Absolutely. Hopefully we can work out the casuse and get it fixed.