Chaos Corona Forum
Chaos Corona for 3ds Max => [Max] I need help! => Topic started by: Hussein052 on 2016-09-12, 12:46:00
-
Hello, i seem to have a problem in loading the EXR in Photoshop, the EXR file does not load in Photoshop by all ways , i.e by drag and dropping or importing via batch script, nothing happens, however all other file formats seem to be working fine in terms of importing. any advice would be appreciated.
-
you can use PROEXR photoshop plugin , or ArionFX ...
-
Can you show your EXR save window in 3ds Max?
There were some problems with opening EXRs in PS (error message), but it was solved some time ago.
-
Sorted.. reinstalled Photoshop..seemed to be a bug in Arionfx for photoshop
-
Hi there
In most cases Arion FX does open EXR's without any problem.
But whenever your EXR is 13K or larger, Arion will crash. I did not investigate from which resolution Arion Fx is crashing, but 11K is no problem.
What you could do in case you still want to use the EXR which Arion Fx can't handle, is temporally renaming both Arion Plugin files to another extension. And the EXR will open in Photoshop.
-
Resurrecting this ancient thread because this has been an on-going issue lots of us in the studio have been having. It seems pretty random, with some EXRs opening in some versions of Photoshop just fine, but not others. We're all rendering to 16-bit Half Float EXR. Is there anything else we should be checking over?
Current work-around is opening the EXR in Corona Image Editor and outputting again as EXR which fixes it.
-
As a follow-up to this, rendered something overnight last night - the beauty pass, refraction and zdepth EXRs open up just fine in Photoshop, but the reflection pass and wire colour EXRs don't open.... so I guess it's nothing to do with output file format I would have to say? Must be some extra/different info stored in certain passes that is breaking these files.
-
Hi Alex,
maybe you could attach a zipped wirecolour (assuming it will be the smallest one) EXR that does not open?
Good Luck
-
Hey Frood. Can't send these as they're client work but I might be able to cook something up that breaks...
-
That would be even better. Mean a scene + result to investigate/compare. Not that I'm saying myself could do it but if you want to solve that issue and want to have the support team to have a look, there may be no other way.
Good Luck
-
I have used the dropbox uploader to share some EXRs rendered last night that show this issue (broken EXRs.zip). The two main renders renders for cam6 are broken but all the other elements, and all other output EXRs from the long list are all perfect. Interestingly, if you browse these EXRs in bridge you can immediately see that the broken EXRs don't show any resolution data, or colour profile. Something is going wrong with the output... but just to remind, as soon as you open it in CIE you can see it fine, and export to another EXR without issue. And also, all these EXRs (per camera anyway) were output by the same machine during the same rendering session.
-
I have used the dropbox uploader to share some EXRs rendered last night that show this issue (broken EXRs.zip). The two main renders renders for cam6 are broken but all the other elements, and all other output EXRs from the long list are all perfect. Interestingly, if you browse these EXRs in bridge you can immediately see that the broken EXRs don't show any resolution data, or colour profile. Something is going wrong with the output... but just to remind, as soon as you open it in CIE you can see it fine, and export to another EXR without issue. And also, all these EXRs (per camera anyway) were output by the same machine during the same rendering session.
Hi Alex and sorry for the delay. Can you explain what exactly is broken? What we should be looking at? All files open fine for me here (Photoshop 2020) and I can't see any glitches. Maybe it really is Photoshop fooling around?
Also, have you tried removing all render elements and adding them back? This is known to sometimes fix broken output.
-
I have used the dropbox uploader to share some EXRs rendered last night that show this issue (broken EXRs.zip). The two main renders renders for cam6 are broken but all the other elements, and all other output EXRs from the long list are all perfect. Interestingly, if you browse these EXRs in bridge you can immediately see that the broken EXRs don't show any resolution data, or colour profile. Something is going wrong with the output... but just to remind, as soon as you open it in CIE you can see it fine, and export to another EXR without issue. And also, all these EXRs (per camera anyway) were output by the same machine during the same rendering session.
Hi Alex and sorry for the delay. Can you explain what exactly is broken? What we should be looking at? All files open fine for me here (Photoshop 2020) and I can't see any glitches. Maybe it really is Photoshop fooling around?
Also, have you tried removing all render elements and adding them back? This is known to sometimes fix broken output.
Hey :)
Did you view them in Bridge also? The broken EXRs don't generate thumbnails, and often don't seem to show the actual resolution either. There's 100% an issue with the files - if it was an issue with a specific version of Photoshop the files themselves wouldn't show any issues, I think. I think that certain versions of Photoshop might be able to process these files, but it's a certainty that somehow those particular EXRs were somehow written incorrectly. The max elements setup isn't broken - you could resubmit this same job to Deadline and have it render on the same machine and it would randomly save those elements just fine but others not. It seems truly random - I suspect something is going wrong during the writing process, perhaps autosave is kicking in? I remember that once upon a time corona autosave would crash a render sometimes. Maybe this is a similar thing?
It's strange if nobody else is experiencing this at all.
-
It's a completely random issue. The only fix I've found is installing Proexr or ExrIO for Photoshop. My preference is Proexr
-
Just checking in here if devs are actively looking into this? It truly seems to be something related to the writing of the specific EXRs, and totally random. Anecdotally, we have also experienced that a render over Deadline might come out fine, but the same render done + saved manually out of the buffer can result in a "broken" EXR.
We have managed to find out that photoshop v 18.x seems to open these broken files fine, but v 21.1/21.2 doesn't open them. That tells us there's an issue with the files themselves.
Not to put too fine a point on it but this is a huge pain in the arse on a daily basis as we're unable to mass-load EXRs in a stack and it's slowing production considerably. Moving everyone to an old version of photoshop is far from ideal too as the new versions have some really useful tools.
-
Quick notes from what we know so far
- The problem files all open fine using Exr-IO (https://www.exr-io.com/) which is free, and resolves lots of problems that Photoshop has with EXR files
- The problem files do not open in PS using its native Open
- The problem files do open fine in After Effects
- The problem files do not show "Color Mode RGB" or "Color Profile sRGB IEC61966-2.1 (linear)" in the Bridge when looking at the info for the files (compared to the ones that work)
- Saving to EXR is handled by Max rather than Corona
- The CIE can load the broken ones just fine (a further suggestion that it is Photoshop's Open that is broken - same with the fact earlier Photoshop versions load it, newer ones don't)
- Our EXR write (our code) is done from the CIE when saving to EXR, and as noted once a "broken" one is loaded into the CIE and saved from the CIE to EXR, it works fine in Photoshop (and shows the color profile etc in the Bridge)
Would using Exr-IO be a possibility? I use it all the time, due to known issues that Photoshop has with 32 bit files and EXRs. We'll let you know if we uncover anything else!
-
In addition to using the Exr-IO plugin, you can also try saving from 3ds Max to our CXR format and then converting to EXR using the Corona Image Editor. This can be done manually, or using the batch script: https://coronarenderer.freshdesk.com/support/solutions/articles/12000030886#batch
I am curious if you would get corrupted CXR files this way as well.
-
Thanks chaps!
We can test EXR-IO, definitely. But if it results in extra steps for loading into PS (preventing stack loading) then we're back at square 1. I'll be honest though, we're definitely not going to be moving the studio to saving CXR and then converting to EXR via batch. It would slow us down even more, and add a tonne of wasted file storage into the issue.
Cheers,
-
Hi! I think you can avoid extra steps, there's a setting in EXR-IO as to whether to show the dialog on load or not. I never have to change anything in the dialog, so that could be turned off, and then it should just open in PS without anything additional popping up or getting in the way - but definitely test it out on one computer first, make sure it's non-disruptive to workflow, and check it does resolve the issue! Let us know :)
We'll also let you know if we uncover anything else as to the cause of it all (though it may all be in the black boxes of Max EXR file saving or Adobe EXR file opening :( )
-
(PS - the CXR save and batch convert was not meant as a workflow, just as a test case/diagnostic step to see if it avoided the broken files, since it is going through our EXR save code and not Max's)
-
Cheers Tom. EXR-IO seems to work ok. Good work-around for now, thanks! Hopefully one day a true fix can be found.
Cheers,
-
Great to hear!
Unfortunately I think anything else is outside of our control. We did some more digging, and the info we have is that the problem EXRs do not have the Chromacites attribute in them. Since this is from the code in Max's save to EXR, that is outside of our control.
Following on from that, EXR standards say that anything loading a file without a chromacities attribute should assume a default - but it looks like Photoshop's Open is not doing that, and generating an error instead. Again, outside of our control unfortunately.
It would seem that After Effects, Exr-IO etc. are all doing the correct "assume a default if there is no chromacities attribute" which is why they don't have an error. This means the problem lies (as far as we can see) in either Max's save, Photoshop's Open, or most likely a combination of both as mentioned with Max failing to add an attribute on save, and Photoshop throwing a wobbly when that happens.
BTW, if you can test the "save to CXR and batch rename to EXR" and you DO find a problem, then that would lie in our code saving to EXR - then we'd have to look some more :)
Hope this helps!