Make sure it works for whomever you're sending it to. Some software may not properly identify a matte stored in z as a matte. Hopefully it's not a problem, but it should be tested in the pipeline.
I'd still like to see a proper multi-layer Saver workflow that supports more than Zip compression.
Bryan Ray http://www.bryanray.name http://www.sidefx.com
It works when you send it to another resolve, which that's what I'm doing .
We are using a regular saver node so all the compression setting for OpenEXR are present.
The only issue I have is by exporting files this way, I get zero Time Code, no options on exports for TC, and I need source TC , but you cant have everything
Thanx again !!!
Microsoft Windows 10 Pro x64 Version 22H2 AMD Ryzen 7 1800X 8cores @ 3.6 GHz NVIDIA GeForce GTX 3080ti 48.0 GB of RAM Resolve Studio v19 Beta1
If you're exporting for another Resolve in the same facility, wouldn't it be simpler to keep it all in Fusion comp, skip export, and use collaboration?
Igor Riđanović wrote:If you're exporting for another Resolve in the same facility, wouldn't it be simpler to keep it all in Fusion comp, skip export, and use collaboration?
Sometimes it has to be a single (alone) shot... Silly workflows...
BTW, thanks for the flame example... i was actually looking for that...
W10-19043.1645- Supermicro MB C9X299-PGF - RAM 128GBCPU i9-10980XE 16c 4.3GHz (Oc) Water cooled Decklink Studio 4K (12.3) Resolve 18.5.1 / fusion studio 18 GPU 3090ti drivers 512.59 studio