--- name: emberbanter-creative-control description: "Use for EmberBanter narration, installed voices, saved storyboards, short films, vlogs, scene animation, private platform handoff packs, calendar/message drafts, simultaneous services, encoder benchmarks, job history and repair or reviewed file-job replay." --- # Creative control Read [implemented contracts](../../references/creative-control.md). Discover the actual executing device, studio_status, studio_workflows and studio_voices before promising execution. Use studio_library for imported IDs. A phone ChatGPT session does not execute a local stdio server by installing this plugin. For narration, use an actually installed voice ID and reviewed plain text. Propose narration with title/text/voice_id/rate/content_reviewed. Never claim cloned voices, remote neural speech or an uninstalled language. Local speech is synthetic and must be heard before delivery. For films or vlogs, save a plan with studio_storyboard_save: title, landscape/vertical format, optional voice_id, rate and one to eight scenes with title/text/seconds/visual_id/motion/loop. Use 2–60 seconds, or 0 only with local narration. Use imported media IDs and explicit loop consent for short footage. Preserve document_id/revision on changes. Propose storyboard only after actual text/rights review. Scene text is visible; footage audio is replaced by speech or silence. This engine makes procedural scene films, not diffusion-generated photorealistic movies or Blender project edits. For platforms, use studio_platforms. Official portal links are manual handoffs, not authenticated account adapters. Prepare delivery_pack with title/topic/description/platform IDs, optional timezone-aware start_at/duration_minutes, reviewed source links and content_reviewed. It creates script/message/metadata drafts and an optional calendar import. Never call it sent, scheduled, uploaded or published. Sending real messages requires explicit recipient/content authorization through a supported connected tool. For capacity, call studio_hardware and studio_performance_plan with explicit kbps and optional measured upload. Distinguish display Hz, game FPS, output FPS and HDR. A performance proposal requires the owner's current confirmation that production is idle. Inspect each encoder result; an advertised encoder can fail. Three synthetic seconds are not sustained game/stream acceptance or a comparable render ETA. For repair, inspect studio_history and the job receipt. Preserve sources, identify cause and correct inputs. studio_replay only prepares a new exact owner review for an eligible file job. It never executes on its own, silently adopts changed inputs, or repeats OBS controls/launches/capture imports. Use a current plan when a saved revision or capability changed. Do not approve for the owner or retry ambiguous external side effects. Read actual job evidence after execution. Separate generated private files, editorial review, device rehearsal, account eligibility and external delivery. Read [brand/market research](../../references/brand-market-2026-11-17.md) for dated primary evidence. Preserve EmberBanter, Music. Games. Stories. and the Gaming/Streaming/Podcasts-only public kit. For start-to-finish setup, follow [hardware to publication](../../references/hardware-to-publish.md), verifying each actual device and account acceptance gate. Current prepared toolkit 0.8.0: follow [private OBS setup and owner rehearsal evidence](../../references/rehearsal-readiness.md). Use studio_readiness/studio_rehearsals for read-only inspection. Never submit owner attestations, approve a control, enable an OBS server or retry an uncertain mutation on the owner’s behalf. Native Windows DPAPI and rendered-device acceptance are pending while DTG is offline; do not call this laptop-installed.