Hauppauge Colossus HD-PVR

[sleonard]

I'm showing the same as you, Stanger. 1.0.29046.0 on the Colossus Encoder Device. If I look at the driver details the file version of the individual *.sys files shows 1.0.29073.0

I followed Hauppauge's instructions to the letter.

If I try to update the driver DM tells me I have the latest already.

S

[phareous]

I just installed the latest drivers. Immediately I found the sound cutting out on HDMI. I changed the Dish Receivers from Dolby Digital/PCM to just PCM and that fixed it. It seems to be working fairly well now except it will skip a few frames every 10 seconds or so which is quite noticeable (sound continues just fine). I also have a very narrow blue line on the left of the screen.

Anyone seen similar issues with the skipping frames or the blue line?

[Wakecrash]

Originally Posted by stanger89

New driver versions.

Those of you who have the latest drivers installed (and working) could you look up in device manager and see what version is reported for Driver Version. I've got the following:
Colossus Capture Device: 1.0.29073.0
Colossus Encoder Device: 1.0.29046.0

I can't seem to get the new drivers to work worth a crap, and I'm suspicious that the Encoder driver isn't getting updated

Then again, that is what the .inf's say....

I have the same on both Colossus. It has been working today. I did add my HD-PVR back in today, one colossus showed a black screen, however unplugging and plugging the HDMI cable resolved that problem

[texneus]

I'm a bit late to the game since I updated some of my hardware while I was at it and did a fresh windows 7 install. I had the original drivers installed but updated yesterday before setting up Sage.

I DO NOT see what others are. Both my drivers are 1.0.29073.0 and dated 3/14/2011. However, I might also add that I did not follow Hauppauge's direction. Rather than uninstall the drivers as instructed, I ran the HW Clear program from the CD and rebooted before installing the new drivers.

Unfortunately, I seemed to have experienced the 'recording in slow motion' after previewing a few dozen channels in channel setup, followed by a BSOD with a stop 0x000000A error when I closed SageTV to reboot the Pea Sea. All seems well at the moment though...

Did anyone notice the color/brightness adjustments in the capture setup? I don't think anyone mentioned this before. That's a nice feature! Is that new with the SageTV beta or something in the drivers?

[swyman18]

I downloaded the new drivers on 3/15 and was seeing the same issues where they did not seem to get updated after following the instructions. For the heck of it, I re-downloaded the zip archive again on 3/17, and I noticed that some of .inf and .cat files within the archive were updated with later dates from the first time I downloaded. I ran the install, and now the two devices show the new version in Device Manager.

They must have posted a new archive sometime on 3/17, so anyone who is having issues may want to try downloading them again.

[Wakecrash]

I follow Swyman's instructions and now both devices show the new version.

[sleonard]

Originally Posted by Wakecrash

I follow Swyman's instructions and now both devices show the new version.

Same here.

S

[stanger89]

Originally Posted by swyman18

I downloaded the new drivers on 3/15 and was seeing the same issues where they did not seem to get updated after following the instructions. For the heck of it, I re-downloaded the zip archive again on 3/17, and I noticed that some of .inf and .cat files within the archive were updated with later dates from the first time I downloaded. I ran the install, and now the two devices show the new version in Device Manager.

They must have posted a new archive sometime on 3/17, so anyone who is having issues may want to try downloading them again.

Yeah, they definitely did. I just downloaded the zip again, and did a compare and 9 files are different (beyond just the date), and there's one new file in the newer archive.

[PLUCKYHD]

Originally Posted by stanger89

Yeah, they definitely did. I just downloaded the zip again, and did a compare and 9 files are different (beyond just the date), and there's one new file in the newer archive.

You know that is just wrong they should change the version number at least rather than try to sneak it in. Also tell people on the website the previous version was bad/wrong.

[SHS]

As for the hcwD1enc.inf and hcwD1e64.inf having the wrong ver number that not a big deal if windows report the a diff ver you should be looking at real ver under drivers detarils any way and as for all 4 Digital Signatures Security Catalog files they are just update VeriSign Time Stamping so the developer made a rookie mistake.

[Wakecrash]

SHS, I susect the issue was more than time stamps and version numbers. My system was locking up multiple times per day and HDMI seemed to lose sync. I tried reloading the drivers previous to 3/17 with same results. Since I downloaded and installed today I have had zero issues.

[SHS]

Originally Posted by Wakecrash

SHS, I susect the issue was more than time stamps and version numbers. My system was locking up multiple times per day and HDMI seemed to lose sync. I tried reloading the drivers previous to 3/17 with same results. Since I downloaded and installed today I have had zero issues.

Wakecrash Windows 32bit and 4GB DRAM is a bad idea, It is well know to cuase problem and cuase performance problem.
The problem 32-bit OS can only allocate up to 4 GB of memory and must don't take in to count to including there video card and any all other device that have build in memory, so if you want better utilize full 4GB+ of ram you're better off using a 64-bit OS.
I don't see that HDMI lose sync problem.
How ever we see this has and chamge in few days after Install then today.
I did hex edit compare there no diff real in main code the only diff I see is in Digital Signatures code which alway start last at last 12 to 13 line and one small change from r. to y(space) at 00140 line

[Ender]

I am in the process of re building my server. My question is, with the HD-PVR, if one uses the optical input, the remote is inoperable on all Hauppauge devices. Since i use the 45 button remote, and wish to use either HDMI input, or optical for the audio. Is this issue still present with the colossus?

[babgvant]

Originally Posted by SHS

Wakecrash Windows 32bit and 4GB DRAM is a bad idea, It is well know to cuase problem and cuase performance problem.

The only "issue" I'm aware of is that you don't get 4GB of RAM because

Originally Posted by SHS

The problem 32-bit OS can only allocate up to 4 GB of memory and must don't take in to count to including there video card and any all other device that have build in memory

So depending on what else you have in the box you only get 3.2-3.5GB. Which for HTPC use is more than enough.

Originally Posted by SHS

so if you want better utilize full 4GB+ of ram you're better off using a 64-bit OS.

Unless you want FW tuning. Considering the use case for this card it is a pretty good reason to go w/ x86.

[stanger89]

Originally Posted by babgvant

The only "issue" I'm aware of is that you don't get 4GB of RAM because

Some Hauppauge driver do or did have problems in 4GB systems.

[babgvant]

Originally Posted by stanger89

Some Hauppauge driver do or did have problems in 4GB systems.

Pretty sure that wasn't limited to x86 systems w/ 4GB (i.e. it didn't work right on x64 either)...

[tvmaster2]

I am still getting the problem of stripped Colossus audio when a HD PVR recording begins - with NEW drivers.
Can't believe I am the only one who has this problem, but that's what it appears to be

[Wakecrash]

Thanks for the feed back all, I have still been having some lock up problems I need to sort out. I thought the new drivers fixed but they did not. I will do some memory testing and remove a stick to see if that helps will I need to reload drivers after removing a stick?

[Clift]

Originally Posted by babgvant

Unless you want FW tuning. Considering the use case for this card it is a pretty good reason to go w/ x86.

This is the reason why I use 32-bit Windows.

[PLUCKYHD]

Originally Posted by Clift

This is the reason why I use 32-bit Windows.

I am running mine on 64 bit w7 with 8gb of ram without issue was only running 4th up toll Thursday.Of course I don't need FireWire