Hauppauge HD-PVR & Colossus Support (4 Viewers)

[op48mo1]

I'm back with more information. I did a complete reinstall of the OS and MediaPortal, and now my card is detected. But I'm having no luck getting a video stream out of it. After several hours of futzing, may I share some logs with you? Thanks!

-Henry

P.S. Sorry about the smileys below...

[edit: Deleted inappropriate log quote.]

 

[mm1352000]

Hi again Henry

Okay looks like we're making progress!
First, let me say that when you post logs it is best to use the watchdog (instructions and info in our wiki -->here<--). It gives us as a community a fuller picture of what is happening when a problem occurs. Having the full set of logs might well be the difference between being able to figure out the problem immediately or spending hours...

With that said, I *think* what is happening in this case is that you're using the latest driver but you haven't completely patched 1.2.0b with the required patches. First, install the updated patch that I put together from -->here<--. After that, since you're using the latest driver you're going to need the patch that is attached to the first post. Just copy that TVLibrary.dll over top of the one from the bigger patch. If you still have problems after that then let me know.

mm

 

[op48mo1]

Thanks for the speedy reply, mm. I'm the tech lead for a 24x7 online service and I know how much work it is to support a software product! Also, please pardon me for not reading the instructions about how to report bugs.

I stayed up until nearly 4:00AM futzing with this thing. Did several complete reinstall/patch cycles of MediaPortal with no improvement. The watchdog throws an exception at startup complaining about missing file MediaPortal.xml. I created an empty file which allowed it to start, but only some of the logs were collected. Did some research, but couldn't quickly determine if the missing XML file is to blame. When I have some time, I will manually archive and post the logs.

I also plan to try installing the card in another machine to see if that makes a difference. I'll get back to you when I have more information.

Have a good weekend!

-Henry

Ah, forgot to mention, I'm running the *latest* latest driver, 29192, I think. Looks like they updated it sometime in the past few days. No idea if that makes a difference. I tried to find a copy of 29168 online, but to no avail...

 

[mm1352000]

The watchdog throws an exception at startup complaining about missing file MediaPortal.xml.

That is the MediaPortal preference file. If that doesn't exist then I'd imagine something must have gone wrong during install. Having said that, it has been more than 1.5 years since I've done a fresh install. You may need to run MediaPortal configuration or MediaPortal itself first to create the XML file...

I also plan to try installing the card in another machine to see if that makes a difference. I'll get back to you when I have more information.

Cool - I'll keep an eye on the thread.

Ah, forgot to mention, I'm running the *latest* latest driver, 29192, I think. Looks like they updated it sometime in the past few days. No idea if that makes a difference. I tried to find a copy of 29168 online, but to no avail...

As long as Hauppauge haven't changed the service ID for the "channel" within the digital stream produced by the Colossus then the procedure I described above should be appropriate for 29192 and any future drivers.

mm

 

[op48mo1]

OK, hopefully I've done this right. This is on a different machine, fresh install. As always, your help is appreciated...

-Henry

 

[mm1352000]

Hi again Henry

If you're using the DLL from the first post then I'm stumped on this one. It looks like the same PMT problem I mentioned earlier. At this point I can only suggest going back to the older driver. Someone here is bound to have a copy.

WileECoyote: any ideas? BTW, I committed all the fixes that are in the All_Colossus... patch as well as the fix for the new Colossus driver.

mm

 

[WileECoyote]

Hi again Henry

@WileECoyote: any ideas? BTW, I committed all the fixes that are in the All_Colossus... patch as well as the fix for the new Colossus driver.

mm

Hmmm... I see the patch has been downloaded 28 times, has anyone else had issues? Unfortunately we rarely hear back when things work well

Cool, so all the work we've done will be in the next release. Thanks mm!!!

 

[mm1352000]

@everyone: does anyone have an HDPVR or Colossus working with a multiseat setup? Alternatively, has anyone else had problems with a multiseat setup?

mm

Yes, I randomly face the same issue with my Colossus, mostly after waking my media center from standby. By now, I was not able to identify a pattern, though, and I asdumed this might be codec-related.

G.

I've asked around about this issue a little and gathered a few suggestions.

First, you want to be using a static IP on the TV Server. If the server gets assigned a new IP address when it wakes from sleep then it can mess up the DB and TV Server.

Second, disable anything IPv6 related. IPv6 is not supported yet and apparently it plays havoc with multi-seat setups.

Third, if the tuner (or in this case, the Colossus or HDPVR) doesn't behave well after waking from sleep then you can schedule a script containing devcon commands that restart the driver to run when the server resumes from sleep/hibernate.

That is all that I have for now. I really need to find some time to dive into the multiseat related code...

mm

 

[WileECoyote]

I need to go back and read the last few pages, but I do not have any client issues. I have a server in the main room (that I also use as a client) and I have three other clients. None have any issues with live TV or recorded TV. Mabye mine works because I have a static IP, IPv6 is already disabled, and the server never goes into standby (it runs 24 x 7.)

 

[GoldenEye]

@everyone: does anyone have an HDPVR or Colossus working with a multiseat setup? Alternatively, has anyone else had problems with a multiseat setup?

mm

Yes, I randomly face the same issue with my Colossus, mostly after waking my media center from standby. By now, I was not able to identify a pattern, though, and I asdumed this might be codec-related.

G.

I've asked around about this issue a little and gathered a few suggestions.

First, you want to be using a static IP on the TV Server. If the server gets assigned a new IP address when it wakes from sleep then it can mess up the DB and TV Server.

Second, disable anything IPv6 related. IPv6 is not supported yet and apparently it plays havoc with multi-seat setups.

Third, if the tuner (or in this case, the Colossus or HDPVR) doesn't behave well after waking from sleep then you can schedule a script containing devcon commands that restart the driver to run when the server resumes from sleep/hibernate.

That is all that I have for now. I really need to find some time to dive into the multiseat related code...

mm

Thanks a lot, mm! I am very impressed by your support quality and your dedication for the project. Here are some comments to your suggestions:

- I am already using a static IP on the TV server. So, this should be good.
- I have now disabled the IP 6 protocol by unchecking the "internet protocol v 6 (TCP/IPv6)" entry in the Windows 7 network properties dialog of my server.
- My server is running 24x7, so no standby/resume issues.

Expect me to report back within a week or so to confirm whether the IPv6 setting changes had some effects.

Thx again, G.