Martius features
Publish approved video versions to supported destinations and keep delivery records. Prepare advertising assets, marketing outputs and SCORM, xAPI or cmi5 learning delivery.
Actual X-Pilot web app recording
Destination selection is one step in publishing. The workflow below continues through approval, transfer and confirmation.
Videos play silently when visible. Tap the film or press Space while it is focused to pause or resume. This recording has no sound.The project opens its publishing destination list.
YouTube, Udemy and Teachable appear in the recorded X-Pilot interface.
Publish
An ad placement. A product launch. A buyer conversation. A lesson inside an LMS. The destination shapes the delivery.
Read the delivery requirementsChoose the destination and its delivery requirements.
Approve the exact film, captions and accompanying message.
Confirm the selected output, account and action.
Check the destination result and keep its publication record.
Bring affected published copies into the next review.
Ad asset libraries and reviewed campaign drafts
The delivery record identifies the approved variant and its destination asset or draft. Uploading a video does not authorize campaign activation, targeting changes or spending.
Connected channels, launch pages and campaign libraries
Keep the launch film, channel versions and publication records connected. Use the scheduling or direct-posting actions supported by the selected destination; a local scheduled task and a native platform schedule have different execution requirements.
Selected hosting, sales pages and customer handoffs
Deliver the reviewed product version with the materials a buyer needs. Private access, viewing analytics and CRM behavior depend on the selected service and are not implied by a video delivery.
Product pages, help-content handoffs and selected video hosts
Deliver the film and supporting page materials together. A searchable watch page still needs a crawlable host, visible context and matching metadata; publishing does not guarantee indexing or AI citation.
LMS course packages or an authorized learning record store
Export SCORM courses, deliver xAPI-enabled activities to an authorized LRS, or use cmi5 for an LMS-launched activity. Course packaging, event recording and launch rules are distinct from the video file itself.
Training portals, LMS courses and approved internal delivery
Publish the approved procedure version and identify earlier delivered copies when it changes. Watching a video or completing an activity does not establish competence, certification or permission to perform a procedure.
Original materials and projects stay local. You approve the selected delivery copies, destination and action before anything is sent.
Martius carries a video from local source material through an editable first cut, review, export and approved destination delivery. Choose the purpose and destination in the brief so production has the right framing, message and delivery requirements.
An ad placement, a launch post, a buyer demonstration and an LMS lesson have different requirements. The shared publishing workflow keeps the selected output, account, action and confirmed result connected to the local project.
Prepare the reviewed film, captions, cover and required destination information. Inspect the selected account, placement, visibility, timing and accompanying text before authorizing the action.
Original materials and editable projects remain local. Only the delivery copies and required metadata named in the approval are sent. Local export and remote publication remain separate choices.
Keep each creative variant connected to its approved offer, eligibility, dates, call to action and landing page. Use the selected placement profile, then inspect the uploaded result after the destination processes it.
Asset upload, an ad draft, platform review and campaign activation are distinct actions. Approval of a creative does not authorize budget or targeting changes. The selected connector declares which operations it supports and which require a separate decision.
Deliver education and training through SCORM course packaging, xAPI-enabled activities or cmi5 LMS launches. Select the supported target profile, define completion and resume behavior, and confirm that the delivered activity launches and records the expected events.
A course package includes more than the media file. Learning records describe the defined activity; they do not establish competence or certification. The authored educational studio films on this site are visual references, not functioning course packages.
The publication record identifies the approved project revision, selected files, destination, remote identifiers and confirmed state. Processing, awaiting platform review, scheduled and live results remain distinguishable where the destination exposes them.
When product or procedure information changes, inspect the affected destinations and approve a new delivery. Some platforms need a new upload or URL. An interrupted or uncertain action is reconciled before a retry, with failed work visible instead of hidden behind a completed state.
Questions, answered
Yes. Prepare the destination-specific output and accompanying material, review the selected account and action, then approve the delivery. Martius records the destination’s confirmed result. Upload, scheduling, post creation and replacement depend on the selected connector’s supported operations.
Original documents, raw footage, recordings, portraits, source audio and editable projects remain on your device. Finished outputs stay local by default. Publishing sends only the selected delivery copies and necessary metadata to the destination you explicitly approve; it does not move your source library into a cloud workspace.
No. Preparing a file, uploading an asset, creating an ad draft and activating a campaign are separate actions. Any supported operation that starts delivery or changes budget, targeting or spending needs its own explicit approval.
No. SCORM packages learning content and provides communication with an LMS. xAPI defines learning-event data and communication with a learning record store, or LRS. Martius delivers through the selected supported learning profile; an MP4 alone does not implement course runtime or learning records.
cmi5 provides course structure, launch, authorization, session and reporting rules for using xAPI with an LMS. Select the supported cmi5 profile and target LMS/LRS together. Its Quartz specification refers to xAPI 1.0.3; a cmi5 label is not a claim of automatic compatibility with every xAPI version.
The project links published outputs to their approved local revisions. Create and review the new version, inspect the affected destinations and approve the supported replacement or new upload. Some services need a new asset, post or URL; a local revision does not silently change every remote copy.
Keep the delivery state and inspect the destination before retrying. Martius distinguishes incomplete work, remote processing and confirmed delivery so an uncertain outcome can be reconciled rather than automatically creating a duplicate post.
Meet Martius
Bring one product, one message, and the assets you already have.