For the Fusion scripting TDs out there, here are two sample fuses that can be used to explore workflows for direct fuse based media I/O using the Fuse API's
These sample fuses allow you to read and write out jpg/exr/png/bmp/raw/fusepic images. This workflow supports a wider range of image formats and is much simpler to master then the more complex approach of creating an EXRIO based fuse like the LifeSaver node.
An example use case for needing both the GetFrame and PutFrame functions inside a single fuse node would be to run media from your compositing timeline on the fly through an external command line graphics tool (like Torch, Imagemagick, OpenCV, potrace, etc...) and then to be able to load the content automatically back into a Fusion comp node flow. All of the Fusion related code would work inside a single self-contained fuse node and be transparent to the end user.
Note: Fusion 16 and Resolve 16 are required to use the
clip:PutFrame() function since the clip() open and close commands were inoperable in earlier Fusion versions.
REG_Unpredictable = true, to the fuses based upon PeterLoveday's suggestions.
A Fusion 9+/Resolve 15+ compatible fuse example that loads an image from disk using GetFrame(). The Filename control supports the use of PathMaps. The "Static Frame" control allows you to load either a (static) single image, or an image sequence.
A Fusion 16+/Resolve 16+ compatible fuse example that saves an image to disk using PutFrame(). The Filename control supports the use of PathMaps.