Resume not working on HD recordings?

[Sheik Yerbouti]

It looks like resume is not working for HD channels, at least not for the recording I made last evening. Logs attached. For testing I started watching the recording, skipped 10 minutes and stopped it. Next I chose resume from the menu and it started at the beginning. I have no resume problems on my SD recordings, but haven't tested other HD recordings.

Chris

[mvallevand]

Chris,

I don't think this is really related to HD as much as it is caching of the file makes things speed up to expose a bug in mvpmc2

Code:

2009-10-30 14:25:58.977    VERBOSE    [6]    Playback started: E:\Recorded TV\Keuringsdienst van waarde\Keuringsdienst van waarde_20091029_20302100.ts
2009-10-30 14:25:59.255    VERBOSE    [7]    Request 200000 bytes (file size:4576932192   file location: 200000)
2009-10-30 14:25:59.380    VERBOSE    [7]    Request completed. 200000 bytes sent
2009-10-30 14:26:03.581    VERBOSE    [6]    Got Media-Progess message. PTS now:0  time: 0   (000000460a10d60000)
2009-10-30 14:26:04.614    VERBOSE    [6]    Got Media-Progess message. PTS now:45000  time: 1   (000000460ac09e0000)

2009-10-30 14:26:36.275    VERBOSE    [6]    Playback started: E:\Recorded TV\Keuringsdienst van waarde\Keuringsdienst van waarde_20091029_20302100.ts
2009-10-30 14:26:36.556    VERBOSE    [7]    Request completed. 200000 bytes sent
2009-10-30 14:26:37.026    VERBOSE    [6]    MVPSetPlaybackPosition() request to set position to: 621 seconds
2009-10-30 14:26:38.037    VERBOSE    [6]    Got Media-Progess message. PTS now:0  time: 0   (000000ffffffffffff)
2009-10-30 14:26:40.338    VERBOSE    [6]    Got Media-Progess message. PTS now:1175064791  time: 26112,5509111111   (000000460a10d60000)

mvpmcx2 is reporting a PTS of -1(000000ffffffffffff) which internally I used to show that the file is not ready, it should wait until it is valid before GBPVR see this.

This should be easy enough fix but I have a question for you now. Are you running this with the beta? With the beta I expect that first reported PTS to be zero not (000000460a10d60000)

Martin

[Sheik Yerbouti]

Chris,

I don't think this is really related to HD as much as it is caching of the file makes things speed up to expose a bug in mvpmc2

Code:

2009-10-30 14:25:58.977    VERBOSE    [6]    Playback started: E:\Recorded TV\Keuringsdienst van waarde\Keuringsdienst van waarde_20091029_20302100.ts
2009-10-30 14:25:59.255    VERBOSE    [7]    Request 200000 bytes (file size:4576932192   file location: 200000)
2009-10-30 14:25:59.380    VERBOSE    [7]    Request completed. 200000 bytes sent
2009-10-30 14:26:03.581    VERBOSE    [6]    Got Media-Progess message. PTS now:0  time: 0   (000000460a10d60000)
2009-10-30 14:26:04.614    VERBOSE    [6]    Got Media-Progess message. PTS now:45000  time: 1   (000000460ac09e0000)

2009-10-30 14:26:36.275    VERBOSE    [6]    Playback started: E:\Recorded TV\Keuringsdienst van waarde\Keuringsdienst van waarde_20091029_20302100.ts
2009-10-30 14:26:36.556    VERBOSE    [7]    Request completed. 200000 bytes sent
2009-10-30 14:26:37.026    VERBOSE    [6]    MVPSetPlaybackPosition() request to set position to: 621 seconds
2009-10-30 14:26:38.037    VERBOSE    [6]    Got Media-Progess message. PTS now:0  time: 0   (000000ffffffffffff)
2009-10-30 14:26:40.338    VERBOSE    [6]    Got Media-Progess message. PTS now:1175064791  time: 26112,5509111111   (000000460a10d60000)

mvpmcx2 is reporting a PTS of -1(000000ffffffffffff) which internally I used to show that the file is not ready, it should wait until it is valid before GBPVR see this.

This should be easy enough fix but I have a question for you now. Are you running this with the beta? With the beta I expect that first reported PTS to be zero not (000000460a10d60000)

Martin

No, it's not the beta. BTW, the beta also doesn't resume, but you probably know that already.

Chris

[mvallevand]

It looks like there might a bug in GBPVR on processing the Resume from the Recordings menu. In testing I get this

Code:

Got Media-Progess message. PTS now:5696691  time: 126.593133333333   (0000000056f2900000)
Got Media-Progess message. PTS now:5741736  time: 127.594133333333   (0000000057a2850000)
Got Media-Progess message. PTS now:5785280  time: 128.561777777778   (00000000584c9d0000)
PlaybackPositionManager.storeLastPlaybackPosition(C:\movies\CSI NY\CSI NY_20090921_00050107.mpg, 127)

MVP playback requested: C:\movies\CSI NY\CSI NY_20090921_00050107.mpg (longname)
MVPSetPlaybackPosition() request to set position to: 127 seconds
Got Media-Progess message. PTS now:0  time: 0   (000000000000000000)
Got Media-Progess message. PTS now:0  time: 0   (0000000057eec50000)
Got Media-Progess message. PTS now:45045  time: 1.001   (00000000589eba0000)
Got Media-Progess message. PTS now:90090  time: 2.002   (00000000594eaf0000)

The jump does happen but GBPVR does not update the timeline and future resumes will be wrong. From the Video Library it works as expected.

Martin