Burning Bridges AI guides
Burning Bridges Motion Guide: Reference Length, Frame and Audio Checks
A motion reference defines the performance. Verify the file and its permitted use before it becomes a production template.
Updated
A Burning Bridges motion-reference video edit combines a character image with a reference video. The video supplies the movement, timing and original scene; the image supplies the replacement character. The configured adapter uses Kling O3 Transformation through Kie, with one image and one video per request.
Provider documentation is capability evidence, not proof that this studio's party edit has passed a live test. No paid provider request has been submitted for this launch. Production references remain pending and generation is closed.
Make it your scene
In preparationA sharp head-and-torso photo; one subject in the frame.
Local photo preparation only. No upload, generation or charge.
Choose a performance with one clear lead
Look for a lead whose head, shoulders and torso remain visible. A reference full of rapid cuts, overlapping hands and foreground guests may make it difficult to decide whose movement should transfer. A simple take gives you a clear failure to inspect.
Use a reference you are allowed to process and publish. A clip that plays on another website is useful research evidence, but its availability does not establish permission to reuse it as a production asset. Record the source and permission internally rather than inventing a license.
Make the template length match the actual reference
The selected video-editing interface requires a source between 3 and 15.5 seconds. This studio uses integer cuts between 3 and 15 seconds, with at least 700 pixels on each side and 24 to 60 frames per second. Check the actual source file rather than assuming a playable 480p example meets these requirements. The reference, interface and quotation must agree.
Do not add an unsupported duration field to a motion request and assume it trims the clip. Prepare the right source cut before configuring the template. A new cut is a separate reference input that needs its own file, permission and audio checks.
Keep the image and performance frame compatible
Decide whether the edit is intended as portrait or widescreen before preparing the character image. The source performance must leave useful room around the action. A late crop can remove the raised arm or hide the face when it moves toward the edge.
The adapter requests 720p, 1080p or 4K while keeping the selected reference duration and frame. No free generation tier is enabled. Delivered dimensions and duration still need real-output validation; a successful API response does not prove them.
Check the source audio before requesting motion
The provider documentation says an output may retain the reference audio track. There is no sound:false field in this adapter's documented motion payload. Production configuration therefore requires a silent, approved reference rather than claiming that a prompt guarantees silence.
Inspect the downloaded MP4 as well. A source can be silent yet the resulting track still needs checking. This studio does not supply the original song; permitted music can be added after the visual edit has been reviewed.
Understand what the API receives
The request contains the subject image, template-specific video, chosen output quality, matching duration and frame, with generated audio disabled. Template IDs are persisted on jobs so a queued toast cannot silently use the full-party reference. Changing quality does not select another model or a different performance.
The reference configuration is kept on the server. The public interface receives only template names, planned length and frame, and availability. User photos and private results are not put into search files or the LLM export.
Handle uncertain submissions without paying for a duplicate
A confirmed rejected task can fail and return its reservation. A timeout after submission is different: the provider may already have accepted the request. The task should enter a review path and be checked by its original evidence rather than automatically resubmitted.
A returned video also needs file validation, a recognizable subject review and an audio check. Queue progress, an HTTP success code and a paid invoice are different evidence layers. None alone establishes that a particular party effect works.
Questions about this guide
Can I use a 29-second reference here?
The provider documents longer videos, but this launch's template and billing path is restricted to 3–15 seconds. A 29-second product would need a reviewed expansion.
Does the motion adapter guarantee a silent video?
No. Reference audio may carry through. The intended production reference must be checked as silent and the output must also be reviewed.
Why save a template ID on a job?
It preserves the requested performance when the queue runs later, allowing the worker to select the matching reference rather than falling back to another effect.
Before your next take
For a Burning Bridges motion reference, verify the lead, frame, actual duration, audio and permission together. Keep provider capability separate from real result acceptance.
Explore the studioStudio preview: video generation and checkout are not live yet.