[TRLC-DK1] Batch validator passes but one camera stream is shorter by a few seconds for builders labs (advanced)
TRLC-DK1 discussion on validators passing while one camera stream is still shorter, hidden temporal inconsistencies, and advanced audit strategies.
A frustrating DK1 QA problem appears when a batch validator reports success, yet one camera stream is still a few seconds shorter than the others. Basic checks pass, but sequence trust is already damaged.
How are you diagnosing DK1 cases where the batch validator passes but one camera stream is still shorter by a few seconds?
Please share how you detect hidden duration mismatches, which audits reveal temporal inconsistency that basic validation missed, and what rules you use to repair, relabel, or reject the affected data.
If you reply, include one exact mismatch symptom and one exact audit or validator extension that exposed it.
The best replies explain whether the short stream showed up in duration stats, sync plots, or replay behavior.
If one duration audit or validator extension caught the issue reliably, share it. Searchers often need that higher bar.
It also helps to say how much mismatch you tolerate before rejecting the run.