← MagnificCONTENT HISTORY
WHAT CHANGED
Update to Magnific
Snapshot Nov 3, 2026 · 06:11 UTC · version 1.1.3
Collection source: downloaded plugin package.
First saved snapshot
No earlier snapshot is available to establish a change.
Save Magnific and check future changes in Following.
Up to 10 plugins free · no card required.
Compare saved observations
Download comparison JSONFull technical diff · 0 changed fields
Full snapshot data
{
"description": "Localize finished videos with Magnific - dub speech into other languages with lip-sync, burn subtitles, caption a video in its own language, review and correct the translated lines, and adapt on-screen text and formats per market. Use it for any translate, dub, revoice, subtitle, caption, multilingual or \"make versions for Spain, Germany, Brazil...\" request on a video, including ads, brand films, explainers, courses and UGC.",
"included_files": [],
"name": "localize-video",
"skill_md_contents": "---\nname: localize-video\ndescription: Localize finished videos with Magnific - dub speech into other languages with lip-sync, burn subtitles, caption a video in its own language, review and correct the translated lines, and adapt on-screen text and formats per market. Use it for any translate, dub, revoice, subtitle, caption, multilingual or \"make versions for Spain, Germany, Brazil...\" request on a video, including ads, brand films, explainers, courses and UGC.\n---\n\n# Localize video\n\nLocalizing a master is one of the highest-leverage jobs for agencies and brands: one approved film, many markets.\nThe quality bar is native-sounding lines that keep brand terms right, mouths that match, and subtitles that read well, with a review step before paying.\n\nFollow `magnific-essentials` for pricing, project folders, waiting and delivery.\n\n## 1. What Magnific's dubbing does\n\nOne dubbing run transcribes the source, translates it, revoices it in the target language, lip-syncs the picture to the new voice, keeps the background sound, and can burn subtitles.\nSo a dubbed result is already lip-synced: do not add `video_speak` on top, which only spends credits and degrades sync.\n\n- Targets: `en`, `es`, `pt`, `ar`, `ru`, `fr`, `de`, `ko`, `tr`, `it`, `id`, `ja`, `zh` (no Hindi captions).\n- Up to 120 seconds per run. Longer videos: `video_cut` into parts at natural pauses (free), dub each, `video_concatenate` in order.\n- Subtitles only, in the original language or another: `keepOriginalVoice: true` with `withSubtitles: true`.\n- Cost (orientation): about 150 credits per second of source for the revoice, plus captions at about 4 credits per second with a 60-second minimum, doubled above 1080p and doubled again for animated caption styles. A 30-second film with subtitles is about 4,800 credits per language. Price it with `simulate_cost` for `video_dubbing`.\n\n## 2. Pick the flow for the client\n\nDubbing is not on every account yet.\nIf your tool list has neither `video_dubbing` nor `video_dubbing_preview`, tell the user and go to section 6.\n\n- **Chat apps with widgets (ChatGPT, Claude):** `video_dubbing` opens the dubbing studio inline; the user reviews lines, voice and captions there and confirms. Nothing is charged until they confirm.\n- **Coding agents and terminals (Claude Code, Codex, Cursor):** the headless flow, one run per language:\n 1. `video_dubbing_preview` with `videoUrl` (the creation identifier), `targetLanguage`, `withSubtitles`, `captionLanguage`, `subtitlePreset`. Free.\n 2. Poll `video_dubbing_preview_get` with the `previewId` until `status` is `ready`.\n 3. Review the preview (section 3).\n 4. `video_dubbing_confirm` with the same `previewId`, `videoUrl`, `targetLanguage` and options, plus `segments` for the lines you corrected, and `folderReference`. This charges and queues the dub.\n 5. `creations_wait` for the result.\nStart the previews for all languages first, then review and confirm each; they run independently.\n\n## 3. Review before paying\n\nThe preview is the only free moment to fix the dub:\n- Check `sourceLanguage` is right, and `issue`: `no_speech` (nothing to dub), `same_language` (only captions will be burned), `multiple_speakers` (several voices; say so to the user).\n- Read every translated `voiceText` and `captionText`:\n - brand names, product names and taglines: keep them as the client wants them (many brands keep the tagline in English; if the user did not say, keep it and state the assumption);\n - numbers, prices, units, dates and legal claims converted for the market;\n - natural register for the audience (formal \"usted/Sie\" versus informal \"tú/du\"), consistent across the film;\n - line length close to the source, so the revoiced line fits its time window.\n- Pass only the changed lines in `segments` (`id` plus the corrected `voiceText` and/or `captionText`).\nShow the user the corrected lines in the reply so a native speaker can approve them.\n\n## 4. Subtitles\n\n- `simple` and `plain` styles read as broadcast captions; animated styles suit social and cost double.\n- Burned captions sit at the bottom: if the film already has lower thirds or end-card text there, mention the clash.\n- To get timed captions as data (for an SRT or an edit), `video_auto_caption` returns the spoken words as timed segments for free, without changing the video, when the account has it.\n Otherwise ask `video_analyze` for the spoken words with their start and end times, and say the timings are approximate and need a check before they become an SRT.\n\n## 5. What dubbing does not change\n\n- On-screen text (titles, lower thirds, end cards, packaging) stays in the source language.\n Options: re-make the end card or text-led graphics per market; for a text-free master, add type in the edit; for designed motion graphics made with Magnific, edit the copy per language with `video_motion_edit` when the account has it.\n- Static key visuals and banners for the same campaign are localized with the `ad-campaign` skill.\n- Cultural fit of the picture (gestures, settings) is the client's call; flag anything obvious.\n\n## 6. If dubbing is unavailable or fails\n\nTell the user plainly why dubbing is not running: the account does not have it, or the error it returned.\nFallback for short pieces: take the transcript (the user's script, `video_auto_caption` when the account has it, or `video_analyze` as in section 4), translate it, voice it with `audio_tts` in a native voice for that language (`audio_voices_list` with the language in `search`), and lip-sync with `video_speak` (video plus audio); captions then need the edit.\nTell the user this is a manual chain and slower to review.\n\n## 7. Deliver\n\nOne file per language, named `<film>_<lang>` (for example `brand_film_es`), in the client's project.\nDeliver `h264` for social and review, `prores_422hq` for broadcast or a final edit.\nThe reply lists each language with its link, the corrected lines, the assumptions (tagline, register), and the credits per language.\n"
}SHA-256 of public snapshot: f86df4361339d08e948ca2974e8f9602df63afb5310e9a128ac6291c67200821