VF Autosave Render + Output Variables 2.8.4

The past half year has been packed with quiet updates but no official releases, so there's plenty to catch up on here!

• Autosave Videos — FFmpeg integration automatically compiles image sequences into ProRes, MP4, and/or a custom format when image sequence rendering completes (the best of both worlds; render to images, but still get a playable file)
• Batch Render — supports selected cameras, collections, items, and image directories, along with a batch index value that can be used to seed variations in Geometry Nodes, Materials, or drivers
• Overhaul of the preferences UI and streamlining of the feature set
• New and updated variables — there are now five categories and these new/revised variables:
  • Project
    • {viewlayer}
    • {node}
      • Requires selected object > material > node; best used with image directory batch rendering
  • Image (thanks to ZeroDean for the request)
    • {display}
    • {colorspace}
      • Blender calls this "view transform" in the UI; {viewtransform} can also be used
    • {look}
    • {exposure}
    • {gamma}
    • {curves}
    • {compositing}
  • Render
    • {engine}
      • Replaces {renderengine} for better readability in long strings (backwards compatible)
    • {duration}
      • Replaces {rendertime} for better readability in long strings (backwards compatible)
    • {rtime}
    • {rH} {rM} {rS}
  • System
    • {processor}
    • {system}
    • {release}
    • {python}
    • {blender}
      • Replaces {version} to prevent confusion with other variables (backwards compatible)
  • Identifier
    • {batch}
      • Returns the index of the current render in the batch list
      • Replaces an unreleased {index} variable, which was easily confused with the existing {serial} value
• Render completed notifications
  • Siri can read out custom details (MacOS exclusive)
  • Send emails and Pushover notifications, however...
    • Blender stores plugin preference data (including passwords!) as plain text in the local file system: please read the documentation careful before you use these features, and entirely at your own risk
• Finally, the documentation here on GitHub has been restructured and revised

While the plugin is actively used in production, there may be issues we haven't come across yet. No dedicated support is provided (this is an internal tool we're simply sharing for free), but please do create a GitHub Issue if you find any broken pieces or have suggestions.