B-Roll Import With Mismatched Frame Rates and No Proxies
An editor is assembling a 7-minute promotional piece on a laptop with 16 GB of RAM and a 512 GB SSD that has 60 GB free. The A-camera footage is 4K at 23.976 fps in a compressed codec, about 180 GB total. The B-roll was shot on a phone at 1080p and 59.94 fps, about 40 GB. The editor's sequence is set to 4K at 23.976 fps. The editor imports all footage, places several phone clips on the timeline, and notices playback stutter, fan noise, and frequent beachballing. The phone clips also show visible judder when slowed to match the sequence. The editor has a deadline in two days and asks whether to transcode, use proxies, or change the sequence.
1. Diagnose the performance problem and recommend a workflow that fits the two-day deadline and the 60 GB free space.
Read the worked answer
The stutter and beachballing point to the laptop decoding compressed 4K footage while also handling 59.94 fps phone clips in a 23.976 sequence, with little free disk for caches. The immediate fix is a proxy workflow: generate lower-resolution proxies for the 4K A-camera and the phone clips and edit against those, keeping the originals online for the final conform. Proxies are far smaller than the 180 GB of originals, so they fit in the 60 GB free space if the editor clears caches and stores proxies on the internal drive while originals stay on an external drive. Transcoding everything to an intermediate codec would consume more space than is available and would not fit the deadline. The editor should also close other applications and confirm the sequence is using the proxies.
2. How should the 59.94 fps phone footage be handled in a 23.976 sequence to reduce judder?
Read the worked answer
The phone footage should be conformed deliberately rather than dropped onto the 23.976 timeline and slowed arbitrarily. Because 59.94 is 2.5 times 23.976, a simple speed change produces uneven motion. The editor should either use the phone clips at normal speed where possible, apply a proper frame-rate conversion with optical flow or frame blending only where the shot allows it, or retime the clip with a speed that divides cleanly and check the result. For shots where judder remains visible, the editor should shorten the clip, cut around the worst motion, or choose a different take. The editor should judge the result at full playback speed on the target display, not frame by frame, because judder perception depends on motion and display.
3. What should the editor verify before exporting the final 7-minute piece?
Read the worked answer
Before export, the editor should confirm that proxies have been disabled or that the sequence is set to use originals for the final render, so the export uses full-resolution media. The editor should verify the sequence settings match the delivery spec: 4K at 23.976, correct audio sample rate and channel layout, and correct color space. The editor should check that no phone clip was left with an unintended speed change or frame-blend artifact, and should watch the full 7 minutes on the target display for sync, judder, and level problems. The editor should also confirm free disk space for the export and a backup copy, since a failed export late in the deadline would be costly.