--- title: "Product update video template — Editable Source | Murmur" description: "Explain what changed, compare the old and new workflow, and show existing users their next step." canonical: "https://www.murmurtts.com/templates/video/product-update" --- [Murmur](https://www.murmurtts.com/)/[Video templates](https://www.murmurtts.com/templates/video)/Product update video template EDITABLE VIDEO PROJECT / Product update # Product update video template Explain what changed, compare the old and new workflow, and show existing users their next step. Download the editable local project and replace its story, scene visuals and voiceover with your own. [Download editable source](https://www.murmurtts.com/downloads/video-templates/product-update.zip)Read the scene transcript ZIP download · source, narration and captions · MIT template source *30.69 seconds · 1280 × 720 · 24 fpsDraftline is a fictional example. These are original motion layouts, not real app screenshots.* OPEN IT. CHANGE IT. RENDER IT. ## Inside the download - project.json, script.txt and storyboard.md for the editable story - render.py, revise.py, requirements.txt and a step-by-step README - One supplied WAV per stable scene ID in audio/ - Finished MP4 preview, poster and WebVTT captions - LICENSE, NOTICE.md and checksum manifests [Download captions separately](https://www.murmurtts.com/video-templates/product-update/captions.vtt) · [Download the preview MP4](https://www.murmurtts.com/video-templates/product-update/preview.mp4) ## How this preview was made **Narration** Kokoro · Eric (am_eric) **Generation build** Murmur 1.0.18 / build 19 development app helper **Renderer** Python/Pillow + FFmpeg **Dependencies** python 3.9.6, Pillow 11.3.0, FFmpeg 9.0.2, ffprobe 9.0.2 Rendered assets and one-line revision checks are recorded. Human listening and visual approval are not recorded. This preview used a development generation helper; regeneration with the released Murmur CLI has not been verified. THE STORY, SCENE BY SCENE ## Preview transcript & storyboard Stable scene IDs for revisions 1. 0:00–0:06`update-before` ### Feedback needed a better home **On screen:** Overlapping review comments reorganize beside the document canvas. > Feedback used to pile up around the draft. Draftline now gives every comment a clear home. 2. 0:06–0:13`update-lanes` ### New / Review lanes **On screen:** Comment cards move between Open, In review and Resolved lanes. > Meet review lanes. Move a comment from open to in review, then resolve it when the change is ready. 3. 0:13–0:22`update-context` ### Keep the context **On screen:** Selecting a comment highlights a sentence and reveals its revision history. > Select a comment to find the exact sentence and its revision history. The context stays with the conversation. 4. 0:22–0:30`update-migrate` ### Bring your current work along **On screen:** An existing draft migrates to the new board and ends with an explicit next action. > Open an existing draft and enable review lanes. Your current comments come along, so the team can keep moving. MAKE THIS PROJECT YOURS ## Customize the product update 1. 01 ### State the change for existing users Name the feature and the version or release where it becomes available. Replace Draftline’s example with a specific change and an honest description of who receives it. 2. 02 ### Make the before and after comparable Use the same task in both scenes, then show how the new workflow changes that task. Keep existing options, permissions and migration requirements clear; do not invent a speed or quality improvement. 3. 03 ### Revise the changed scene audio Keep the stable scene IDs so a corrected line maps to one WAV file. Generate the replacement narration in Murmur, replace audio/[scene-ID].wav, and render again to rebuild timings and captions. 4. 04 ### Confirm availability and the next step Update the ending with the actual place users enable or try the feature. Review differences between plans and platforms, test the adoption step, and use your own product visuals before publishing. ### Render the downloaded project From the extracted folder, the first command renders the supplied narration. Python 3.9+, Pillow and FFmpeg/ffprobe are required; dependencies are not bundled. Use a new output directory for each render. The revision commands require an available Murmur generation helper and the Kokoro/Eric preset. They were checked with a development helper; read the included README to discover your installed helper and review compatibility first. The helper creates a sibling project and preserves the other scenes’ audio. Edit project.json for app name, palette, scene titles and matching script. Interface labels/drawing logic live in render.py. Text edits need matching replacement audio. Keep stable scene IDs. ``` python3 render.py --output-dir ../render-01 python3 revise.py --scene update-lanes --text "Your new narration sentence." --output-dir ../revision-01 python3 ../revision-01/render.py --output-dir ../revision-render-01 ``` Run from the extracted project directory. Source and output directories must be distinct. Rendering supplied audio needs no Murmur installation; generating replacement narration requires a working Murmur CLI/model. Final archive was extracted and rendered in a fresh folder. Keep the stable scene ID when replacing a line. Regenerate its WAV, then render again so durations and captions follow the new audio. Listen and inspect the resulting preview before sharing it. ## Before you publish - The example interface and product are fictional. Replace names, claims and visuals with your own approved material. - The supplied project is a local source download, not a hosted video editor. Python, Pillow and FFmpeg are separate renderer requirements. - Caption timing follows scene audio. Review readable line lengths and sync after changing narration; automatic timing is not human caption approval. - The preview uses a development narration helper. Released Murmur CLI regeneration and human listening have not been verified for this package. - The template includes one landscape layout. Check a new composition and text size if you adapt it for a vertical or square export. Source license: MIT. Original template source and fictional visual layouts; see LICENSE and NOTICE.md in the archive. The source archive includes usage terms; your replacement assets and selected speech model may have separate terms. Download checksums **preview · SHA-256** `75b1e0d84f2ecd1de30f88a39aae20c3db4ca8f32f730f0d567715ec58ef4cce` **poster · SHA-256** `b6b95b2e2fb55b7675e20be862fa4edbb1c8855674f630898544acf94e7049a7` **captions · SHA-256** `61ac21673bcfdcfc6731323bcafd8fddb55750aeddb9076b79361f1b69c08e41` **download · SHA-256** `624ecbe5093841ef81116f2c21907b95aa2a3f7ace2bc360e8a7a50e4367f452` REPLACE THE VOICEOVER LOCALLY ## Your script. Your next take. Use Murmur to generate replacement scene narration on Apple Silicon with macOS 15 or later. Export WAV, place it in the project’s scene-audio folder, and use the renderer to rebuild the video. A purchased Murmur license is required; model capabilities and hardware requirements vary. Speech generation is local after setup. The video renderer and any assistant you choose have their own requirements. [Explore Murmur](https://www.murmurtts.com/#product)[CLI & MCP setup](https://www.murmurtts.com/docs/automation) [Connect Murmur to an assistant](https://www.murmurtts.com/blog/resources/connect-murmur-mcp-local-voiceover)[Build a local video workflow](https://www.murmurtts.com/blog/resources/remotion-local-voiceover-mac)[Browse all video templates](https://www.murmurtts.com/templates/video)