How to make a J-cut without slipping the audio

In our edit, a courier vaults over a parked car and the picture cuts to a spinning wheel on a wet street. The second pass uses the same frames. The wheel shot arrives in the sound 300 milliseconds before it appears on screen.

That is a J-cut. The next scene’s sound begins while the previous picture is still playing. The useful part is the sound you can bring in early while the rest of the track stays in sync.

Extend the audio edge and leave the picture cut in place

  1. Make the picture cut first. In this example, the outgoing shot ends at 1.500 seconds on the timeline. The incoming shot starts at 1.000 seconds in its source file.
  2. Unlink or select the incoming audio by itself. Extend its left edge so it starts from 0.700 seconds of source audio. Leave the source moment at 1.000 seconds aligned with the picture cut.
  3. Fade the incoming audio in across the overlap. Fade the outgoing sound down over the same 300 milliseconds, then play the join at normal speed.

Moving the whole sound clip 300 milliseconds earlier also shifts everything after the cut. On a speaking shot, that can put the voice ahead of the mouth. Extending just the left edge keeps the later sound anchored.

Compare at the same volume

Try the cut with and without the overlap. Check that you can still hear any line at the end of the outgoing shot. If the new sound masks it, shorten the overlap or start the fade after the last word.

Our replay script produces two three-second stereo WAVs from the same two clips. It checks that the sample data matches outside the 300-millisecond overlap. That lets you hear the timing change before the final video's mastering and end card.

Watch both passes and get the exact source files and replay script.

Field note from the SeedanceCheap team, prepared with Codex. The examples use earlier Seedance 2.5 footage with fictional adults and staged action. The 720 × 1280 sources were edited into a 1080 × 1920 demonstration using their original generated sound.

Comments

Post a Comment

Popular posts from this blog

A PowerShell string cast can shift your UTC report window

https://seedancecheap.com AI-assisted technical note from the SeedanceCheap team, with Codex. A reporting window meant to start at 16:00 UTC can accidentally start at 13:00 UTC. The trigger is a small type change: parse a UTC timestamp from JSON, cast the resulting date to a string without a zone, then interpret that string in UTC+03. We encountered this class of bug in a reporting script. The example below uses invented input and an in-memory time zone. It contains no customer records, makes no network calls and does not change your computer's time zone. The zone disappears at the string boundary With PowerShell's default ConvertFrom-Json behavior, an ISO timestamp ending in Z becomes a DateTime with Kind set to Utc . That typed value still identifies the intended instant. A later [string] cast can produce a date such as 10/16/2026 16:00:00 , which no longer says UTC. A consumer must now guess the missing zone. If it treats 16:00 as local UTC+03, the corresponding U...
Read more

Choose API funding before building a video request

SeedanceCheap.com — from our team, with Codex. We operate the AI-video service discussed here and have a commercial interest in it. This is a practical account of a change to our free, local API request builder. A free request-planning tool can still prepare a request that requires paid funding. Its interface should make that boundary clear before someone copies JSON into a terminal. Our public cookbook previously put free_trial: true into every prepared pilot. That was a safe choice against accidental paid fallback, but it left developers with an awkward path when introductory trials were paused: the only prepared example selected a trial, even if the reader intended to use existing credits. We changed the builder to require an explicit funding choice. It starts with neither route selected. The JSON preview stays empty and its download button stays disabled until the reader chooses trial or paid funding. The page still collects no API key and sends no generation request. Ca...
Read more

How to fix a missing prop in an AI video edit

Our courier kept the delivery bag through the fight. The cherry on the cake vanished in the guided remake. We wanted the blue jacket from the new take and the same cake from the original. The fix was a cut that lasts just over half a second. Try it with your own footage. Pick one prop that carries the story and write down how the viewer recognizes it. Ours was a white cake with a red cherry. Compare the prop at the moment it matters, even if the opening frames of both takes look right. Find a moment with room to cut Play the two versions separately. Pause when the prop is revealed. Look at what surrounds it too, including the grip, the sleeve and anything moving across the frame. A correct-looking cake is useless as an insert if it flashes the old jacket. In our cut, the blue sleeve opens the red bag at 0:05.75. We let that action read, then went to the cake after the old sleeve had cleared the original frame. We used source frames 263–276 inclusive, counting from zero at 24 fps....
Read more