Am Donnerstag, 17. Mai 2007 22:01 schrieb Stone:
On 5/17/07, Marius Heidenstecker marius@heidenstecker.de wrote:
Hi everybody,
I'm pleased to announce version 0.0.3 of my cut-a-lot-plugin.
I really like the idea behind this. Can you tell me what the recommended PTS threshhold should be for NTSC recordings? It seems like this will only work with PAL.
Best Regards.
From the readme: The PTS-threshold as a parameter defines how large a gap has to be at least in order to be marked. One PTS-tick is 1 / 90000 second. If you take 25 frames per second as the frame-rate, one frame is 1 / 25 * 90000 = 3600 PTS-ticks long. Usually there is an I-frame every 12 frames so the difference between two I-frame PTSs should be always 12 * 3600 = 43200 ticks. But never the less the difference were sometimes 43199 or 43201 in a few analyzed recordings. So I introduced the PTS-threshold. The default of 3605 ticks means the PTS-timestamp might jump one frame without being recognized.
If you take 30 frames per sec for NTSC-recordings, you will have 1 / 30 * 90000 = 3000 PTS-ticks. So you should try 3005 for the PTS-threshold. Am I right, that you talk about the gap finder? Please let me know, if that threshold worked.
Cheers,
DMH