Full Camera trail left on one cut after #1294 #1300

One exported frame still shows the Full Camera trail at a cut on v2.1.0-rc.5, despite #1294.

What happens. A Full Camera segment spans a cut. On the first frame after the cut, the webcam is smeared from its PiP corner toward full frame for one frame (1/60 s), then plays normally.

Where it was seen. Windows pass of v2.1.0-rc.5 (#1299). A project with seven cuts under Full Camera, exported at 1080p60:

• six cuts are clean;
• the cut after the trim that resumes at source 46.34986635 is ghosted. That start rounds down in f32.

Why the fix misses it. The exports of this project from rc.4 and rc.5 are byte-identical. The #1294 hold only applies when the frame's source time lands exactly on the clip's start. Here it most likely lands a hair below it. This is a guess, not checked in code. Two other starts that round down in f32 (47.293 and 9.334) were clean in both builds.

Impact. Low: one blurred frame, exactly at a cut. Not a v2.1.0 blocker.