I have three recordings that gives this strange result, with frame counts above 2 million.
PM me about ftp details, and I will upload the smallest one; about 3 GB. I only have 5 mbit upstream, so it will take a while...
I also checked the results in older recordings:
During 2009 and 2010, the numbers in the txt file and the "Initial Commercial List" section in the log are always the same. These were made with an older version of Comskip, obviously.
More recent recordings have an added offset of between 4 and 14 frames in the txt file, compared to the values in the log file. The offset has been the same for all the "skips" in one recording, but seem to differ between recordings?
Since I discovered this "2 million frames phenomena" the other day, I've recorded several programs from that HD channel.
Most of these result in a txt file that seems ok, ie frame numbers within the file. However, comparing the txt file and the values in the log show strange results:
Code: Select all
FILE PROCESSING COMPLETE 135189 FRAMES AT 2500
-------------------
3260 8594
24837 32285
49248 56514
90141 97967
123014 130388
136341 136478
---------------------
Initial Commercial List
---------------------
0) 2173 7502 0:03:33.36
1) 23725 31159 0:04:57.91
2) 48074 55319 0:04:50.64
3) 88905 96712 0:05:13.04
4) 121746 129099 0:04:54.95
5) 135052 135190 0:00:05.48
1087
1112
1174
1236
1268
1289
The offset increases for each skip, to a point where the last skip point in the txt file is beyond the last frame: 136341, file length 135189 frames.
Another example, where the txt file results are beyond the file length:
Code: Select all
FILE PROCESSING COMPLETE 25057 FRAMES AT 2500
-------------------
50780 52603
61439 61473
---------------------
Initial Commercial List
---------------------
0) 14364 16187 0:01:12.91
1) 25023 25058 0:00:01.35
What additional processing is made after the log file is finished, and the txt file is written..?