Wiki · Learning path / Workflow / Evaluation
Autograph first verification project checklist
This page defines a small first project for evaluating Autograph without turning the test into a vague demo reel. The goal is not to prove that Autograph can replace After Effects, Nuke, Fusion, Flame, or Blender. The goal is to test the specific surfaces that matter for an Autograph-centered workflow: responsive motion design, 2D/3D layout, EXR/color handling, OpenFX plugins, Red Giant/Universe access, import/export behavior, and final render reliability.
Build one deliberately boring test piece
Create a 10-second composition with a title card, one animated SVG or PSD graphic, one short video plate, one alpha element, one imported still sequence if available, one EXR or HDR element if the workstation has suitable material, and one simple 3D object or USD asset. Render at least two aspect ratios from the same design. A boring verification piece is better than a polished example because failures are easier to see.
What the project should test
- Responsive composition: Build one layout and render two delivery formats, such as 16:9 and 9:16, without duplicating the design by hand.
- 2D animation: Animate text, vector shapes, and at least one imported SVG or layered image.
- Compositing: Combine a plate, a graphic element, a keyed or alpha-bearing element, and a simple look adjustment.
- Color and image pipeline: Check whether EXR, ACES, and OCIO-related settings preserve expected values through preview and final render.
- Plugin surface: Load at least one native modifier, one Universe or Red Giant OFX tool if licensed, and one third-party OpenFX plugin if installed.
- 3D surface: Import or create one simple 3D element, then confirm camera, depth ordering, textures, lighting expectations, and render speed.
- Output: Export the same project to the exact formats used by the studio or client, then compare the result to the interactive view.
Pass/fail criteria
The project passes as a first evaluation only if the file can be reopened, previews remain responsive enough for iterative work, renders match the expected look, alpha and color are not silently damaged, plugin licensing is clear, and the two aspect ratios do not require separate rebuilds. Any failure should be recorded with version numbers, operating system, GPU, source format, output format, plugin build, and a still frame that shows the issue.
What not to conclude from the test
A successful first project does not prove that Autograph is ready for long-form editorial, heavy shot finishing, high-volume EXR compositing, or a facility pipeline. It only proves that the tested workstation, media types, plugin set, and delivery path are viable enough for a deeper project-specific trial. Conversely, one failed plugin or one color mismatch should not be read as a total product failure unless it affects the exact work the artist needs to deliver.
Useful next pages
Sources checked
- Maxon Autograph product page - public feature surface for responsive compositions, GPU effects, OpenFX, Red Giant/Universe access, EXR, ACES, OCIO, PSD/SVG import, OpenUSD, and Filament, checked 2026-06-30.
- Creative Bloq coverage of Autograph and Cavalry becoming free - independent coverage summarizing Autograph as a free layer-based motion graphics and VFX app with responsive design, GPU effects, USD, OpenEXR, ACES, OCIO, OpenFX, and third-party plugin support, published 2026-04-16 and checked 2026-06-30.
- Open Effects Association - OpenFX context for treating plugin support as a host-and-plugin compatibility surface rather than a universal guarantee, checked 2026-06-30.