Capture a real workflow with a visible result
Martius desktop capture operates a supported software task, records the approved interaction and brings the local clip into the video project. Define the question the demo answers, a known starting state and the result the viewer should see.
Use the desktop app’s supported workflow and permission settings for the environment. A supplied screen recording can also be imported as local footage. Label the source accurately; a mock interface remains an illustration, even when it looks convincing.
Prepare a bounded task
Use an approved test account and demonstration data that can appear in the film. Set the product version, required permissions and starting state. State which actions are allowed and where the task should stop for your attention.
Example: open a demonstration project, select a scene, resolve its comment and show the changed headline. Stop when the workspace or labels differ. Recording permission does not authorize changing unrelated accounts, spending money or publishing a project.
- Approved application or workflow and product version
- Known start, required access and cleared test data
- Allowed actions and expected visible outcome
- Unexpected states that require review
Check what becomes visible in the recording
Inspect names, messages, files, browser tabs and notifications before starting. Review the captured clip afterward for information that should not leave the organization. A local recording can still expose private material if you later publish the resulting video.
Keep credentials outside the creative brief. Supply the necessary authorized environment through the desktop workflow, and stop capture if unrelated sensitive content appears.
Connect the capture to the actual script
Put the recorded action beside the narration that explains it. Use current interface labels and leave time for the result to register. Mark omissions or accelerated footage when they could change a viewer’s expectations.
A supplied clip, actual Agent capture and authored interface animation have different origins. Preserve that distinction in the project and published explanation. Edited elapsed time is not a valid performance measurement by itself.
Keep the source recording local and versioned
The original recording stays on your device alongside the product materials and editable project. Record the product version, capture date and relevant source reference. The approved export is a separate file linked to the project revision.
When an interface changes, recapture the affected sequence and review related narration, titles, captions and presenter passages. Reuse approved footage only when it still describes the current product.
Handle unsupported or changed environments deliberately
Desktop operation is scoped to the supported workflow, permissions and known environment. If a task stops on an unexpected state, inspect it before proceeding or provide a new approved recording. Do not interpret a stopped operation as completed footage.
Physical products and on-site services still need real photographs or footage supplied by the team. Desktop capture records a software environment; it does not replace filming equipment or a real-world procedure.
Questions about this workflow
Can Martius capture a software demo?
Yes. Use the supported desktop workflow, approved permissions and a defined task with a known start and visible result. The captured clip becomes a local source in the project.
Can I use an existing screen recording?
Yes. Import an approved local clip and retain its recording date and product version. Identify it as supplied footage rather than an Agent operation record.
Does capture mean Martius can operate every application?
No. Use the supported workflow and permission scope shown in the desktop app. Unexpected states need attention; capture is not permission for arbitrary actions.
Does the recording get uploaded to a cloud workspace?
Original recordings and editable projects stay local. Only selected finished deliveries and required metadata leave after you approve publishing; model requests have a separate data boundary.