Skip / fast forward not working - random intervals and direction

[johnsonx42]

megaupload?

[imilne]

Or dropbox perhaps?

Iain

[aseibert]

The test recording is available at http://dl.dropbox.com/u/40452767/Channel...001030.zip. If you need the logs, I attached them to my previous post.

[aseibert]

Actually, it appears that it will be a couple of hours until that dropbox link is available. It's still uploading. Thanks for the dropbox suggestion btw.

[mvallevand]

Your file may have lost the timing.info metadata. Can you upload it for testing?

Martin

[sub]

Yep, we'll need that too. (it would have been lost when you zipped)

[aseibert]

Here's the timing info for that dropbox file.

[mvallevand]

Jumping with ctrl-right (60 sec default) the worst jump was under .7 seconds off.

Code:

2011-09-05 08:32:59.066    [DEBUG][1]    Asking for position: 65.2570037841797
2011-09-05 08:32:59.069    [DEBUG][1]    Using timing.info, jumping to time 65.257004 (offset 90635928)
2011-09-05 08:32:59.086    [DEBUG][1]    After skipping position reports as: 65.661003112793
2011-09-05 08:33:00.845    [DEBUG][1]    Asking for position: 127.392997741699
2011-09-05 08:33:00.845    [DEBUG][1]    Using timing.info, jumping to time 127.392998 (offset 185630636)
2011-09-05 08:33:00.883    [DEBUG][1]    After skipping position reports as: 127.546997070313
2011-09-05 08:33:02.579    [DEBUG][1]    Asking for position: 190.214004516602
2011-09-05 08:33:02.579    [DEBUG][1]    Using timing.info, jumping to time 190.214005 (offset 269090228)
2011-09-05 08:33:02.619    [DEBUG][1]    After skipping position reports as: 190.61799621582
2011-09-05 08:33:04.211    [DEBUG][1]    Asking for position: 252.348999023438
2011-09-05 08:33:04.211    [DEBUG][1]    Using timing.info, jumping to time 252.348999 (offset 367123956)
2011-09-05 08:33:04.252    [DEBUG][1]    After skipping position reports as: 253.126998901367
2011-09-05 08:33:05.806    [DEBUG][1]    Asking for position: 314.843017578125
2011-09-05 08:33:05.806    [DEBUG][1]    Using timing.info, jumping to time 314.843018 (offset 459672596)
2011-09-05 08:33:05.833    [DEBUG][1]    After skipping position reports as: 314.950988769531
2011-09-05 08:33:07.276    [DEBUG][1]    Asking for position: 376.682006835938
2011-09-05 08:33:07.276    [DEBUG][1]    Using timing.info, jumping to time 376.682007 (offset 538955016)
2011-09-05 08:33:07.322    [DEBUG][1]    After skipping position reports as: 377.070007324219
2011-09-05 08:33:08.659    [DEBUG][1]    Asking for position: 439.707000732422
2011-09-05 08:33:08.660    [DEBUG][1]    Using timing.info, jumping to time 439.707001 (offset 620404512)
2011-09-05 08:33:08.719    [DEBUG][1]    After skipping position reports as: 440.31298828125
2011-09-05 08:33:10.220    [DEBUG][1]    Asking for position: 502.075988769531
2011-09-05 08:33:10.220    [DEBUG][1]    Using timing.info, jumping to time 502.075989 (offset 703318904)
2011-09-05 08:33:10.261    [DEBUG][1]    After skipping position reports as: 502.760009765625
2011-09-05 08:33:11.448    [DEBUG][1]    Asking for position: 564.523010253906
2011-09-05 08:33:11.449    [DEBUG][1]    Using timing.info, jumping to time 564.523010 (offset 762669564)
2011-09-05 08:33:11.478    [DEBUG][1]    After skipping position reports as: 565.036010742188
2011-09-05 08:33:12.909    [DEBUG][1]    Asking for position: 622.114990234375
2011-09-05 08:33:12.909    [DEBUG][1]    Using timing.info, jumping to time 622.114990 (offset 820386692)
2011-09-05 08:33:12.953    [DEBUG][1]    After skipping position reports as: 622.257019042969

2, 3 and 4 minute jumps were just as good

Code:

2011-09-05 08:45:44.014    [DEBUG][1]    Current position is: 7.01999998092651
2011-09-05 08:45:44.014    [DEBUG][1]    Using timing.info, jumping to time 247.020004 (offset 357973432)
2011-09-05 08:45:44.045    [DEBUG][1]    After skipping position reports as: 247.042999267578
2011-09-05 08:45:56.980    [DEBUG][1]    Current position is: 255.748001098633
2011-09-05 08:45:56.980    [DEBUG][1]    Using timing.info, jumping to time 435.747986 (offset 613547400)
2011-09-05 08:45:57.015    [DEBUG][1]    After skipping position reports as: 436.006988525391
2011-09-05 08:46:02.041    [DEBUG][1]    Using timing.info, jumping to time 201.187012 (offset 286788360)
2011-09-05 08:46:06.772    [DEBUG][1]    Current position is: 207.138000488281
2011-09-05 08:46:06.772    [DEBUG][1]    Using timing.info, jumping to time 327.138000 (offset 476843576)
2011-09-05 08:46:06.806    [DEBUG][1]    After skipping position reports as: 327.165008544922
2011-09-05 08:46:10.789    [DEBUG][1]    Current position is: 332.501007080078
2011-09-05 08:46:10.789    [DEBUG][1]    Using timing.info, jumping to time 452.501007 (offset 636677416)
2011-09-05 08:46:10.849    [DEBUG][1]    After skipping position reports as: 453.042999267578

Martin

[aseibert]

From my log (attached in a previous post):

2011-09-04 09:38:59.727 [DEBUG][1] User is trying to skip.
2011-09-04 09:38:59.727 [DEBUG][1] Current position is: 339.442993164063
2011-09-04 09:38:59.727 [DEBUG][1] Asking for position: 399.442993164063
2011-09-04 09:38:59.728 [DEBUG][1] Using timing.info, jumping to time 399.442993 (offset 561716364)
2011-09-04 09:38:59.965 [DEBUG][1] After skipping position reports as: 358.600006103516

About 41 seconds off

[sub]

I tested skipping with this file and timing info, and like Martin my skips were very good. In my case they ranged from about .2 - .6 of second off the requested spot.

With the attached patch, can you create a c:\temp directory, and a HKEY_LOCAL_MACHINE\Software\NPVR\LogSlipFile=1 (DWORD) registry setting, then reproduce the skipping problem, then zip and attach the npvr.log and c:\temp\reader.log?