How to Verify J-Cuts and L-Cuts in MP4 Exports

Краткое содержание

Pixel’s announcement explains how to verify J-cuts and L-cuts in exported MP4 video using three 5.75-second reference edits. It highlights picture changes at 2.917 and 2.125 seconds, matching decoded audio hashes, and waveform checks to distinguish picture edits from shifted or re-encoded audio.

DEV Community

How to verify a J-cut or L-cut in an exported MP4

Someone asks for a small revision to an interview. “Let me hear the answer, but stay on the listener for another half second.” The new MP4 sounds plausible. How do you tell whether the editor held the picture or slid the entire voice track? We made three 5.75-second reference exports at Valmera from the same exchange in the Sintel trailer. You can download all three and run the checks below. The reference renders use FFmpeg. The dialogue is the control: every version has the same decoded audio. File Audio edit Picture edit Straight cut 2.625 s 2.625 s J-cut 2.625 s 3.250 s L-cut 2.625 s 2.000 s Listen to the first word of the answer The line is “I'm searching for someone.” The audio edit occurs at 2.625 seconds. The first word comes around 2.8 seconds. That gap matters in an editing brief. “Hold for half a second after the first word” and “hold for half a second after you change audio takes” give different picture edits. Pause each file at 2.917 seconds. The straight cut has moved to a wide view. The J-cut still shows the close-up while the answer is underway. Now step back to 2.125 seconds. The L-cut shows the dark opening of the incoming shot while the question is still audible. That darkness is present in the source trailer. Compare the sound in the files If you control the export, encode the approved audio once and mux it into each picture version. Decode the audio to the same PCM format before comparing the files: for cut in straight j-cut l-cut; do
printf '%s ' "$cut"
ffmpeg -v error -i "$cut.mp4" -map 0:a:0 \
- c:a pcm_s16le -f hash -hash sha256 -
done
All three hashes match. The MP4 file hashes differ because their pictures differ. If an editor re-encodes audio for each export, a different PCM hash on its own does not tell you whether speech moved. Compare the timing of a short waveform passage before the join and again after it. Our source check compares seven 100-ms windows, including one on either side of the audio edit. See the measurements and exact file hashes. Check the picture against the source clock At 24 fps the straight cut switches takes at output frame 63, counting the first frame as zero. The J-cut switches at frame 78. The L-cut switches at frame 48. When the second take is visible, its source frame is the output frame plus 90. At output frame 70 the straight cut therefore shows source frame 160, while the J-cut still shows source frame 70. You can extract that moment without relying on a player's rounded time display: ffmpeg -v error -i j-cut.mp4 -vf "select=eq(n\,70)" -frames:v 1 frame-70.png
For your own interview, check one later word where the new speaker's mouth is visible. An editor can place the first transition correctly and still slip the rest of the sentence. Download the source, rebuild script and trial brief. For a separate example produced through Valmera, the four-second B-roll edit changes the picture on the word “green” while the presenter keeps speaking. Watch the recorded edit. Footage from Sintel, © Blender Foundation, CC BY 3.0. Valmera trimmed, resized and rearranged the excerpt and extracted the comparison frames. This tutorial was prepared with AI assistance.
How to Verify J-Cuts and L-Cuts in MP4 Exports
Powered by Readybot.io

Последнее от Pixel

Incident Response: Look Beyond the Red Alert

Pixel’s DEV Community announcement explores how teams can fixate on one failing service while overlooking the real cause of an outage, such as a full …

Sach: AI Fact-Checks WhatsApp Forwards in India

Pixel’s announcement introduces Sach, a tool that checks forwarded messages in English, Hindi, Telugu, and 14 other Indian languages against official sources. It gives cited …

Java 25 Removes SecurityManager: What to Fix

Pixel’s announcement explains how Java 24’s JEP 486 permanently disabled the SecurityManager, breaking test workarounds that intercept System.exit. It recommends returning exit codes or throwing …

Why a Java HPA Got Stuck at 20 Kubernetes Pods

Pixel shares how a Spring Boot pricing service autoscaled to 20 Kubernetes pods and stayed there because the JVM retained committed heap memory after traffic …