Getting started

Prepare Your Product Assets for Martius

Prepare product images, recordings, documents and approved facts for Martius. Keep source references, permissions and asset versions clear throughout the project.

By Martius team6 min readUpdated

Start with a focused brief and a local source folder

Name the product, audience, purpose and next step for the first video. Add the approved facts and the assets that support that message. A purposeful source package is more useful than an unexplained folder containing every file the business owns.

Martius uses your local materials. Original documents, raw photographs, video, recordings, portraits, source audio and the editable project remain on your device. Export and publishing are separate steps: finished deliveries stay local by default, and only selected copies leave after you approve a destination action.

Create an approved product information sheet

Record the current name, variant, benefit, feature wording, specifications and commercial terms needed by this task. Put the supporting source and owner beside each important statement. Mark unresolved fields instead of letting the first draft guess.

For an offer, include dates, eligibility, limitations and the landing page. For software, include the product version and current interface terminology. For a service, describe the approved process and the actual supporting evidence.

  • Product identity and relevant variant
  • Approved claims and their supporting sources
  • Offer, conditions and destination when relevant
  • Product version, date and responsible reviewer

Give each asset a purpose and an origin

Select product photos, footage, brand material and recordings that the film will actually use. Explain what each file shows and where it fits. Keep source originals for useful cropping and record usage permission for third-party content.

Separate a real product view from illustrative material. A generated setting may support the story, while a current recording establishes a particular software action. Customer quotes, logos and results need their own evidence and permission.

Prepare software and presenter sources carefully

For a software story, use an approved test environment, known start and demonstration data suitable for publication. Inspect names, messages, tabs, files and notifications before capture. Keep the recording date and product version with the clip.

For an avatar or supplied person video, record the permitted source, chosen character, voice and intended use. Bring only the portrait or audio you have permission to use. Choose presenter layout after reviewing how much space the actual product needs.

Keep creative direction separate from facts

Describe the opening, setting, emphasis, pace and sound in ordinary language. Attach a small number of references and say what each illustrates. Keep those preferences apart from product facts so you can change the treatment without losing the approved information.

For a revision, attach the approved project and specify what changed. Martius uses that reference for an impact review; you compare the updated passages and the creative sequences you want to retain.

Confirm import and delivery settings for the task

Use the supported file options and output profiles shown in the desktop app. Choose dimensions, narration language, captions, quality and destination from the task’s actual needs. A sample film’s duration or pixel size describes that sample, not every possible source or output combination.

Check media, fonts, local paths and free storage before a long render. Keep credentials out of briefs and project exports. Local source storage does not promise that every AI request runs offline.

Questions about this workflow

Do I need a finished script before importing materials?

No. Start with the audience, main message, approved facts and useful assets. Martius can organize the script and scenes from that brief; you review the result before delivery.

Do I need to upload my original source folder?

No. Originals and editable projects stay local. Publishing is a separate approval for selected finished delivery copies and required metadata.

What should I do if a file is missing?

Reconnect the expected source file and verify that it is the correct asset version. Resolve missing media before reviewing or exporting the affected scenes.

Can I include a reference image in the finished video?

Only when your permission or license covers that use. A style reference can guide the treatment without being cleared as a production asset.