Wiki · Autograph / Render delivery / Review workflow

Autograph render review and delivery checklist

Published 2026-07-04 · Wiki · Render delivery / Review / Workflow

A small production checklist for checking Autograph renders before they leave the artist workstation for review, edit, color, comp, client approval, or archive.

Why this page exists

Autograph can combine motion graphics, compositing, OpenFX plug-ins, multi-channel EXR, ProRes, ACES/OCIO-managed color, and OpenUSD-based 3D scenes in one project. That makes render output a workflow boundary: a shot may look correct in the project but still fail review or handoff because of color, alpha, naming, frame range, codec, or versioning assumptions.

Before rendering

• Confirm the target: review movie, editorial handoff, final comp plate, social format, archive, or technical test. Do not use one output preset for every purpose.
• Record frame range and frame rate: include handles if the file is going back to editorial or comp, and note whether retiming or time remapping is already baked.
• Check format responsibility: EXR sequence for high-bit-depth comp handoff, ProRes or another movie format for fast review, and stills only when a still approval is actually enough.
• Freeze external dependencies: plug-in versions, OCIO config, USD assets, textures, fonts, linked media, and any network paths that could change after the render.

Color and view transform checks

• Write down whether the render is scene-linear, display-referred, or a review encode with a view transform baked in.
• If ACES or OCIO is involved, note the config name, input interpretation, working space, display, and view used for the approval render.
• Do not treat a browser, chat upload, or video-hosting preview as a color reference unless that is the actual delivery surface.
• For EXR handoff, confirm that utility passes such as depth, normals, motion vectors, matte IDs, and cryptomatte-like data are not accidentally transformed as display color.

Alpha, premultiplication, and edges

• Render at least one alpha-bearing test frame over black, white, and a saturated checker or plate background.
• Record whether the output is straight or premultiplied alpha. A clean-looking preview can still produce dark or bright fringes in the next host.
• Check motion blur, glow, light wrap, deflicker, and retiming effects at the matte edge. These are common places where transparency errors appear.
• For editorial review movies, do not assume alpha survived unless the codec/container is explicitly meant to carry it and has been tested in the receiving app.

Version naming

• Use a stable pattern: project, sequence, shot, task, version, frame range, and purpose. Example: show_seq010_sh020_mograph_v004_review_1001-1120.mov.
• Never overwrite an approved render with a same-name file. If the pixels changed, the version should change.
• Keep source project version and render version aligned, or write the exception in the notes.
• Put experiments in an explicit test folder. Do not let test renders look like delivery candidates.

Review package minimum

• One review movie or frame sequence.
• One thumbnail or representative still for quick identification.
• One short text note with frame range, color/view assumption, alpha state, plug-ins used, and known issues.
• For final handoff, include the exact source references needed to reproduce the render: project file, external assets, OCIO config if not standard, USD package if used, fonts, and plug-in/version notes.

Practical rule

A render is not only an image. It is a contract between Autograph and the next person or system. Treat color, alpha, frame range, file naming, codec, source dependencies, and version notes as part of the output, not as admin afterthoughts.

Useful next pages

• Autograph EXR channel and data-pass checklist
• Autograph OpenUSD scene handoff checklist
• Autograph retiming, motion blur, and deflicker plugin checklist

Sources checked

• Maxon Autograph product page — checked 2026-07-04. Used for Autograph feature context: motion graphics, compositing/VFX, OpenFX, multi-channel EXR, ProRes, ACES/OCIO workflow, Red Giant/Universe access, OpenUSD-based 3D environment, and Filament rendering.
• OpenEXR Technical Introduction — checked 2026-07-04. Used for EXR as a high-dynamic-range, multi-channel production image format and for channel/pass handoff context.
• OpenColorIO documentation — checked 2026-07-04. Used for color-management context around configs, displays, views, and transforms.
• ACES documentation — checked 2026-07-04. Used for ACES color-managed pipeline context and the distinction between scene-referred working data and display/view output.