LiveTV Catchup terminates after 5 seconds

[asout]

Using 1.0.8 with PVRX2 on MVP the Live TV catchup exits to the main menu after 5 seconds.

This has been mentioned in the support forum, can someone confirm its not just me...

in more detail...

1. currently Recording live tv channel
2. after xx number of minutes,select to watch the channel (starts from beginning of recording)
3. press 60(or any high number) then skip (to go forward 1 hour which will reach the end of the recording and continue playing.)
4. Now this has always in the past continued playing, but with PVRX2 it plays for 5 seconds then exits livetv.

This is a big problem for me as I have a cctv channel recording 24/7 and now i cant switch to that channel and see what is 'currently' happening on the cameras! - well just for 5 seconds


please help!

[sub]

Reproduce the problem, then zip and attach the logs and I'll take a look.

[asout]

log attached thanks.

[asout]

any news on this problem Sub?

[mvallevand]

Are you using mpvmc? Your logs look the problem in this thread

http://forums.nextpvr.com/showthread.php?t=27711

The patch that I made to the mvpmc nightly does seem to handle it.

Martin

[asout]

Using standard 1.0.8 install.....have never looked at mvpmc

[mvallevand]

Using standard 1.0.8 install.....have never looked at mvpmc

If you have a chance it would be good to know if the mvpmc dongle solves your problem. This is the file that has the fix I mentioned.

http://www.mvpmc.org/~mvallevand/dongle.zip


Martin

[asout]

Thanks I will try this dongle..... but I was hoping Sub could fix the bug, works fine in GBPVR.EXE 1.0.8 but not in PVRX2.EXE 1.0.8

[mvallevand]

Thanks I will try this dongle..... but I was hoping Sub could fix the bug, works fine in GBPVR.EXE 1.0.8 but not in PVRX2.EXE 1.0.8

Sub hasn't determined that it is a bug yet and if a client workaround fixes it, maybe it isn't. I want you to test and hopefully confirm this issue isn't only mvpmc related.

http://forums.gbpvr.com/showpost.php?p=2...ostcount=4

Martin

[asout]

Just upgraded to 1.0.16 and this bug seems to be fixed now, thanks Sub!