Sorry for the emotions, but I am in mindf***, the only format that allows you to save channels in layers, .openExr format, it does not work to open anywhere except the blender and Krita. Krita opens it, but cannot export it to .psd. What am I doing wrong and why is it made so stupid? In 2018, where there is a zbrush, where there is a substance painter, I do not want to save each image of the channel separately, I want one file, where there will be these layers with which I can work, where I can apply various filters and effects, in programs, in which it will be easier and faster to do than in blender compositing.
Or, then i rendered all my channel, and forgot to use output file node in compositing, I cant save all chanel by pressing F3 button, it give me message somethink like “cant save multilayer image becouse have not layers” (but they there).
The fact that you call the .exr format stupid, means you might read up on it.
.exr was developed by ILM to respond to the call for more bitdepth in their image pipeline. There’s a dedicated website for it.
ILM made the whole thing Open Source, and is now a standard format for everything VFX/compositing.
The fact that you can render multiple channels into one file, doesn’t mean Krita can open these layers.
It has to have support for the channels to open them.
Even PS (at least my version) needs a plugin to open them properly into layers.
Has nothing to do with the .exr format. but more with the way the import is implemented in the app.
You can always opt to render all channels into separate files, which is also a part of the specs. Not sure if Blender will let you do this though. Haven’t tested that yet
And if it should, it’s a bug.
Honestly, the answer resembles the typical linux-user answer, which says that something is accepted as a universal format in any industry, but opening 99% of the program used by most artists, I do not see in them export or import .exr format. This is a simple fact.
“The fact that you can render multiple channels into one file, doesn’t mean Krita can open these layers.” - The fact that I just opened the file I needed in the Krita without any problems. But can’t do it in Photoshop or gimp.
Sorry, but almost every app used in VFX can handle .exr in one way or another. Loading and/or saving.
Using mulitple channels is mostly ‘restricted’ to compositing apps like Nuke, Fusion etc.
Adobe is just shitty with their implementation, and I have no idea how Krita or Gimp implemented it.
Also, I’m not sure about the OSS restriction of .exr with free software.
Look at FBX and Blender for instance.
Also remember .exr is a 16 or 32 bit format, depending on how you save it. (float or half float)
It could be that Krita can only export to 8 bit Photoshop, to keep things compatible. So you will need to convert it back to 8bit first, and then save as PSD.
It’s the same for jpeg for instance, you cannot save from a .exr directly as the bit depths are different.
And please stop with the Linux comparison, .exr is a standard for a reason.
Fundamentally, OpenEXR was designed to be a data-file format – “data” file, not “image” file. (Blender Foundation(!) then introduced the “MultiLayer” extension, which was very quickly adopted.)
“Image” files might map colors to some limited integer range, might apply gamma-correction, might do any number of things to make life easier for “stupid display devices.” Whereas “data” files, such as OpenEXR, purposely care nothing for such things. If you can put a stream of numerical data into such a file and then get exactly the same stream of data back out of it, [MultiLayer] OpenEXR has accomplished its mission.
Therefore, if you now want that OpenEXR data to be converted to another format, I think it proper to say that you should expect to “have Blender do it,” if Blender produced the original file. The compositor can do this – maybe – with nothing more than a File Input node connected to Output. But my key point is that it’s probably going to be more than that.
You’ll be thinking at this time about the particulars of this-or-that image- file format, and of the hardware that will eventually read it, as you specify exactly how Blender should utilize what is in this data- file, to produce the most-usable image output in that format for that kind of device. (In fact, on many projects you will have several different blend-files, each drawing from the same “final cut” OpenEXR master and targeting some specific deliverable-file scenario, always down- sampling to get there.)
