HDPVR and channel change bug

[DreadFury]

Hey everyone, LONG TIME lurker here.

I read quite awhile ago here on the forums about the known bug with the HDPVR and channel changes locking up the HDPVR and services.
(sub said something along the lines of forgetting to finish a routine in the code)


sub -

You said you have fixed this problem already and the fix would be available in the next release.

I have been waiting patiently, but I now am compelled to leave "lurking" status and join "posting" status on the forum, to ask:

Will the new version be out anytime soon?
if not, would it be possible to release the fix for the HDPVR as a patch?

The fact that it locks the unit up and requires a reboot (sometimes an entire server reboot as well as the unit itself) has destroyed the waf on my setup.

Unfortunately, trying to tell the wife not to change channels is hurting the waf even more..


any help?


Thanks a million sub, your hard work is appreciated far and wide, I hope you never get sick of hearing about it. =)

[whurlston]

I can't really speak for sub but from past experience, as he gets closer to a new release, his current state of code is usually incompatible with the current release. This is why we don't usually see patches just prior to new releases.

[sub]

Will the new version be out anytime soon?

Yes, not too long (two or three weeks).

Unfortunately it wasnt a GB-PVR fix though. In the HDPVR firmware at the time, the some of the time line clocks were reset during a channel change (or something similar), leading to playback seeming to stop. Hauppauge indicated at the time that they were in the process of fixing it, and it was going to be resolve in a subsequent release. I'm not sure where they got to with that.

The fact that it locks the unit up and requires a reboot (sometimes an entire server reboot as well as the unit itself)

Thats certainly not the problem I was talking about. The problem would cause the video decoder and audio decoder to sit around waiting for the next packet with timestamp 'x', but the clock had reset so the packets had some incorrect timestamp on them. It definitely wouldnt require a reboot.

There was another firmware issue that effectively store the device encoding while the IR Blaster was in use, but that was a short term lockup.

Some tips from the past that helped stability though, it was best to use an external IR Blaster rather than the one on the HD-PVR. Also, try to set your cable box to output a fixed video standard, ie always 1080i or always 720p, rather than have it change standards from channel to channel.

[DreadFury]

I can't really speak for sub but from past experience, as he gets closer to a new release, his current state of code is usually incompatible with the current release. This is why we don't usually see patches just prior to new releases.

I understand and agree, that's why I decided to wait it out, at first.
However, after several weeks with my new expensive toy, 3 tv's "half-working", and a very unimpressed woman wondering what I spent that money for, I have been driven to ask, on the outside chance it was a simple, patchable fix for v1.3.11.

*fingers crossed* =)

[DreadFury]

Yes, not too long (two or three weeks).

Unfortunately it wasnt a GB-PVR fix though. In the HDPVR firmware at the time, the some of the time line clocks were reset during a channel change (or something similar), leading to playback seeming to stop. Hauppauge indicated at the time that they were in the process of fixing it, and it was going to be resolve in a subsequent release. I'm not sure where they got to with that.

Thats certainly not the problem I was talking about. The problem would cause the video decoder and audio decoder to sit around waiting for the next packet with timestamp 'x', but the clock had reset so the packets had some incorrect timestamp on them. It definitely wouldnt require a reboot.

There was another firmware issue that effectively store the device encoding while the IR Blaster was in use, but that was a short term lockup.

Some tips from the past that helped stability though, it was best to use an external IR Blaster rather than the one on the HD-PVR. Also, try to set your cable box to output a fixed video standard, ie always 1080i or always 720p, rather than have it change standards from channel to channel.

I am not using the HDPVR blaster (supposedly the new drivers fixes this tho), i am using a MCE remote because of reported problems.

This is what I'm referring to:
http://forums.nextpvr.com/showthread.php...vr+channel

it causes the HDPVR to hang on channel change, even WITHOUT a remote.

[sub]

Ah, timeshift channel change. Yes, thats fixed. Unfortunately Whurlston is correct above - I'm not in a position to make patches to 1.3.11 anymore. My build has moved on and is incompatible. Sorry.

[DreadFury]

ahh, well I'll be eagerly waiting!
Think of me if you need a beta tester! xD

Thanks again, sub.