So based on what I have gathered about smart CODECs, one way they save space is to make the GOP (group of pictures) longer, dynamically, sometimes several seconds long, based on how idle the scene.
But when you burn the picture with ts before recording, since the second is changing more or less every second, does that make the GOPs get shorter than they would otherwise?
Maybe it’s not enough pixels being changed to really affect the calculation. But I’m sure in some night scenes at least, it must be the thing that changes the most frame to frame.
Thoughts?
