I believe that the OpenEXR files that are being output from Cycles (Blender 3.6) are not being recognized correctly by my video editor due to extra metadata that Cycles is including (and I see no UI option to remove).
I am rendering a sequence to OpenEXR and compositing it in Vegas Pro 20 (not the best NLE, but I haven't transitioned to Davinci Resolve yet and need to get this project out of the way first). To save a long narrative, here are the facts:
Vegas Pro will do the following:-
- Import OpenEXR files from other sources, including very large files.
- Import OpenEXR files rendered from Eevee
- Recognize and read required metadata (resolution, bit depth, etc) from these OpenEXR files
It will not do the following:
- Import OpenEXR files rendered from Cycles engine from my sequence (same frames as Eevee mentioned above)
- Recognize and read required metadata from these files (just says "Unknown")
The above results are the same regardless of bit depth, +/- alpha channel, using CPU or GPU, or EXR compression scheme. After hours of research and analyzing the files, the only difference I can find is that the Cycles renderer adds metadata such as render time, etc:
On the other hand, Eevee's EXR output (which does import in Vegas) does not pass these metadata into the file. Since by all other metrics (resolution, bit depth, alpha, file size, etc) the Eevee EXR files are pretty much identical to the Cycles EXR files, I suspect that it is these metadata from Cycles that is tripping up my editor. Unfortunately I've tried a trial version of the newest Vegas release and it is similarly flawed. I'm also asking over on their forum, but I honestly expect to hear crickets from their tech support.
My million-dollar question is:
Is it possible to remove the extra metadata shown in the image above from OpenEXR files output from Cycles?
There is no option that I have found in the UI, and I'm not sure if there's some editable Python somewhere that controls how EXR files are written. Any help would be hugely appreciated.
It's worth noting that all of the above-mentioned files will import into Davinci Resolve. So I realize it's very likely a Vegas issue, I'm just looking for a workaround.
Edit for add'l information:
- Someone else has found that the non-working file will open in modern Photoshop but not open in Photoshop CS2, which is fairly old.
- Using ExifTool, I found there is an additional difference between the metadata of the two files. On the line for "flags:" the Cycles file has the value "long names" while the Eevee file has the value "(none)"