Preparation becomes evidence

Try it.
Observe it.
Keep the lesson.

Use this record while completing the production workflows on your editing computer. A selection records your observation; the website does not operate or test the software for you.

A useful first milestone

One short film.
A repeatable route.

Try a 30-second excerpt with one graphic, one scene and a saved Resolve project. Then use the same packet to make a revised version.

Choose your route. Direct scripting, an available Astra tool or a deliberate manual step may each be useful. Record which one you tried and what actually happened.
0 of 8 tests recorded
01

Find the available controls

Try: Read the version, edition, active project and available integration actions.

Look for: A useful report appears and the current project stays unchanged.

A useful edge case

A control is unavailable: record a manual route or the setup needed before relying on it.

02

Prepare the production packet

Try: Choose a short owned clip, audio, a graphic and a timing plan.

Look for: Paths resolve, source copies remain intact and frame rate and clip ranges are explicit.

A useful edge case

Move a test file temporarily. Assembly should report the missing asset rather than quietly dropping it.

03

Assemble a disposable timeline

Try: Create a test project, import copies and place a few clips at chosen frames.

Look for: The actual tracks, source ranges and markers match the plan.

A useful edge case

Run again. Choose whether it updates generated material or creates a new revision; check for duplicates.

04

Import a Blender scene

Try: Render a small numbered frame range and bring it into Resolve.

Look for: Frame count, duration, crop and a diagnostic colour frame look right in the edit.

A useful edge case

Interrupt the render and check whether the missing frames can resume without losing completed work.

05

Bring in a graphic

Try: Render one original Herk composition. Then try a minimal timeline exchange if useful.

Look for: The imported title is readable and timing agrees at the chosen frame rate.

A useful edge case

Test a transition and a missing media reference. Record which properties survive the exchange.

06

Check the delivered file

Try: Watch the complete draft and listen through every join.

Look for: Captions, crop, words, deliberate pauses and sound support the chosen intention.

A useful edge case

Inspect cut boundaries and the phone crop. Compare the exported duration with the timing plan.

07

Reopen and reproduce

Try: Save the project backup, sources, manifest and review notes.

Look for: A second run can rebuild the assembly from the packet, with identifiable revisions.

A useful edge case

Reconnect the media from a different folder and record what still needs a local path.

08

Try a council session

Try: Begin with a clearly labelled synthetic session and five fictional advisers.

Look for: The panel, arguments, disagreement and choice replay with the right attribution.

A useful edge case

Supply a quotation with the wrong source ID. Source verification should flag the mismatch.

Notes autosave in this browser when storage is available. Export a copy if you want to keep or share it.

Keep technical and creative review connected

A completed command
is one observation.

A useful delivery also needs the picture, words, sound and meaning to work for the intended audience.

Picture and words

Inspect cuts, crop, contrast, missing frames, caption timing and the first moments of a face shot.

Sound and rhythm

Listen for clipped words, unexpected gaps, distortion and changes to deliberate musical or thinking pauses.

Meaning and reuse

Check the source of factual claims, the intended permissions and whether the saved packet helps you make another version.