MRGI AUDIO / WORKFLOW FIELD GUIDE
Prepare a localized narration package
Keep script, recording, language version, and usage context together through revisions.
01 / FROM INPUT TO HANDOFF
Follow the decisions.
This walkthrough describes the intended MRGI product behavior. The browser demo illustrates a small part of the workflow; it does not run the complete application.
- 01
Align the source
- Start with
- A fictional script with timed passages.
- Work through
- Associate passages with recording intervals and identify the approved script version.
- Result
- A navigable source transcript.
- 02
Prepare a language version
- Start with
- The source and localization brief.
- Work through
- Create a reviewed adaptation and retain its relationship to the original.
- Result
- A candidate localized script and recording.
- 03
Review the delivery
- Start with
- Language, timing, and rights records.
- Work through
- Check the adaptation and intended usage before approving the output.
- Result
- A reviewed language version.
- 04
Package the variants
- Start with
- The approved language set.
- Work through
- Record source versions and production settings for each delivery.
- Result
- A traceable audio collection.
02 / INPUTS & INTERCHANGE
What travels with the work.
These are foundation formats and intended handoff contracts. Support and fidelity must be confirmed for each released build.
| Artifact | Role | Review consideration |
|---|---|---|
| Audio sources | Recording and production | Sample rate, channel layout, and plugin behavior require validation. |
| Timed transcript | Script-to-recording references | Timing corrections and text revisions should be separately tracked. |
| Localized outputs | Motion and distribution | Retain language, source, and rights context alongside the audio. |
A deliberate cross-app boundary
Use an approved Author script, deliver reviewed audio to Motion, and retain production records in Evidence.
The intended handoff should identify the selected resource, its version, the destination, and the user’s authorization. A linked application should not inherit unrestricted file access.
Explore the connected applications ↗03 / BOUNDARIES & READINESS
Know what this example establishes.
- No voice recording or synthesis occurs in the demo.
- Transcript timing does not establish semantic accuracy.
- Rights and language acceptance require qualified review.
Development status
The source foundation is imported. Transcript editing, localization workflows, and consent-aware delivery are planned.
Before a production release
Validate real-file behavior and platform support, implement the stated authorization and review rules, and document the tested acceptance scope. The interactive website is a product demonstration, not a release candidate for the application.
04 / PRODUCT QUESTIONS
The details that matter.
Will changing the transcript change the sound?
That behavior depends on the editing operation. The proposed interface should distinguish a transcript correction from a destructive audio edit.
Is voice cloning part of this preview?
No. Any future synthesis would require explicit permission, suitable rights, and a separately specified provider workflow.
Open-source foundation
Multitrack audio, DSP, automation, MIDI models, and plugin hosts exist in SoundCraft. Rights-aware localized production is the proposed MRGI focus. Read the credits and foundation mapping.
Keep exploring Audio.
Return to the product breakdown or try the local interactive example.