2011-09-04, 01:19 AM
I can see in your logs that your skips aren't that accurate. I compared here on similar sized recordings, but couldnt replicate the problem.
For example, in your logs:
In my logs, my skips typically come out +/- 500ms or so.
Hopefully your timing.info will shed some light.
If you can reproduce it when skipping in a short recording of say 10 minutes, then we might look at getting you to upload that file, and the timing.info, so I can replicate the exact scenario here.
For example, in your logs:
Quote:2011-09-03 18:37:14.001 [DEBUG][1] Current position is: 1807.44396972656
2011-09-03 18:37:14.001 [DEBUG][1] Asking for position: 1867.44396972656
2011-09-03 18:37:14.003 [DEBUG][1] Using timing.info, jumping to time 1867.443970 (offset 2479243044)
2011-09-03 18:37:14.235 [DEBUG][1] After skipping position reports as: 1756.61804199219
In my logs, my skips typically come out +/- 500ms or so.
Quote:2011-09-04 13:05:52.317 [DEBUG][1] Current position is: 2387.98510742188
2011-09-04 13:05:52.317 [DEBUG][1] Asking for position: 2447.98510742188
2011-09-04 13:05:52.318 [DEBUG][1] Using timing.info, jumping to time 2447.985107 (offset 1197684832)
2011-09-04 13:05:52.379 [DEBUG][1] After skipping position reports as: 2448.11010742188
Hopefully your timing.info will shed some light.
If you can reproduce it when skipping in a short recording of say 10 minutes, then we might look at getting you to upload that file, and the timing.info, so I can replicate the exact scenario here.