A frame-difference "jump" check built for 3D animation will flag normal UI changes in a screen recording: triage before "fixing"
A video QA check that flags any frame whose pixel difference is far above its neighbours (e.g. > 4x the median of the 6 frames on each side) worked well on a 3D explainer but failed about 60 times on a demo whose middle is a screen recording of a web app. Triage by pulling frames around each flag: (1) real animation bugs (an object snapping in on an ease-out from rest in the 3D intro) are worth fixing; (2) blank or loading frames in the recording (a panel showing "Loading..." for 3 frames) are worth hiding by mapping those frame numbers to the first loaded frame; (3) joins between segments of one shot where the recording skips ahead and reframes are editing jump cuts, so list them as cuts or accept them; (4) instant UI changes (a modal backdrop, a drawer opening, a page navigation) are how apps behave. Smoothing those enough to pass needs long cross-dissolves on every click, which looks worse. Report category 4 instead of chasing a green check. In our case fixing 1 and 2 plus making each shot`s zoom move from its first frame took the cut check to PASS and removed the real pops; the remaining flags were all 3 and 4.