Hauppauge Colossus HD-PVR

[SHS]

In that area no that still there but handel it better just not a really big improvement on the choppy video after several recordings.

[traker1001]

Originally Posted by SHS

In that area, no. that is still there, but it handle's it better. just not a really big improvement on the choppy video after several recordings.

That sucks, I keep hoping they will fix the need to reboot.

[najames]

My trusty E1 version HD-PVR went belly up after 3yrs and 1mo, I just went to CompUSA and got a Colossus.

I used the HWClear to remove all old Hauppauge drivers and let WHS 2011 find them and install what was needed for the Colossus. I have only set up the video source in SageTV and verified it is working and the USB-UIRT is changing channels on the Cisco RNG150.

Do you reboot the computer often with the Colossus or restart SageTV? If you reboot it, how often do you do it?

I am using the 30079 drivers. I noticed a slight hickup after about 5 seconds on a channel change, other than that it seems to work ok.

[panteragstk]

Most of us generally reboot every night. I do it every other day because I have a crappy sata controller that won't let my computer restart properly.

[Tiki]

I re-boot manually, once per week (usually on Sunday).

I tried not re-booting at all, but found that things went down-hill fast after about 2 weeks. After running into problems 2 or 3 times, I started the weekly re-boots, and haven't had any problems since.

Prior to adding the Colossus, I never did a regular re-boot.

On a (somewhat) related note - I keep most of my stuff on a UPS. So, for example, my HD-PVR and HDHomerun stay powered-on continuously, even when I re-boot my PC. I found that since I added the Colossus, my HD-PVR will crap out every 3 months (literally to the day) and must be re-booted to fix. I'm going to try cycling power to the HD-PVR periodically to see if it prevents that problem.

[spacecadet]

Originally Posted by panteragstk

Most of us generally reboot every night. I do it every other day because I have a crappy sata controller that won't let my computer restart properly.

I use both a Colossus and the USB HD-PVR with my Sage system and I do not reboot every night. I reboot every 2-3 weeks (probably for reasons completely unrelated to the HD-PVR devices).

[nyplayer]

I reboot maybe once a month ... and only setup a reboot when I am available to monitor reboot. I too have had reboots get stuck for various reasons.

[najames]

Great, I could live with rebooting once per week on the weekends, but not nightly. Wife records stuff at any time 24/7 with some favorites though. The Colossus worked for about 15 min, I'll bet until it hit the first commercial, resolution probably changed and the recording stopped. I need to get into the STB and see if I can set it to only output 720P perhaps.

This seems to be lot of jacking around after using the HD-PVR that would run for months at a time without any problems/reboots. I have a window to test the Colossus, if I can't get it to work reliably I'll be forced to return it and get another HD-PVR. I hate returning stuff.

[panteragstk]

Interesting that you guys don't reboot all that often. I just started it because it seemed that everything stayed nice and stable if you did that. Like I said, I've stopped because of my crappy (free) SATA controller. Everything works just fine, but I still reboot once a week or so.

What driver version is everybody on?

[najames]

I'm having a very bad experience so far with the Colossus, need some help and get it running or it will need to exchange it for another HD-PVR.

My E1 HD-PVR is sitting here in pieces, it quit working. It isn't recognized by the OS and the USB port will show an error (43), same results on 2 systems. It had worked flawlessly for 3 years. Nothing looks wrong internally, no fry marks or anything, top of the board was very clean.

I have a new system as listed in my signature, I am running WHS 2011 (64 bit), Sagetv 7.1.9.256. My Comcast Cisco RNG150 STB is set to output 720p. I am using Component + spdif connections. I ran HWCLEAR before letting WHS2011 update 30079 drivers for the Colossus. I have 4x2TB non-pooled drives for SageTV recordings, they do spin down however. Last night it recorded a couple half hour test shows ok, then failed on a 2 hour recording. Nothing was listed in SageTV, just a system message that it failed. The server was even rebooted before the 2 hour recording, verified the Sage service was running. It was also scheduled to record a movie this morning at 7:45am. It recorded the first 16min perfectly, then stopped recording. Colossus is installed in the x16 "primary video card" slot and a 2port Sata card in the "seconday video card" slot.

FYI - I have noticed that if I remote desktop into the server it will hose up recordings too. No backups or anything was happening at the time of failed recordings.

I'm stumped other than reinstalling or using Win7 instead of WHS. Ideas???

I've read through the first 43 pages of this thread and will continue to read so I can follow progress with the Colossus.

In case anyone needs it, I'm attaching my USB-UIRT CiscoRNG150.ir file (had to name it with TXT on the end so I could upload it), it has worked fine.

[skiingwiz]

Originally Posted by najames

My E1 HD-PVR is sitting here in pieces, it quit working. It isn't recognized by the OS and the USB port will show an error (43), same results on 2 systems. It had worked flawlessly for 3 years. Nothing looks wrong internally, no fry marks or anything, top of the board was very clean.

In my experience (it's happened to both my HDPVRs) this is a power supply gone bad. Hauppauge support will replace it free of charge. (Other than having to pay to ship the bad one to them.)

[najames]

Thanks skiingwiz,

I don't think the HD-PVR power supply is bad, I have one with the exact same specs on my working Sipura VOIP box and tried it with the same failed results.

I am using a second computer to test SageTV/Colossus with now using WIn7 x64. I have several recordings scheduled later, we'll see if it works on a totally clean Win7 PC vs WHS 2011.

Update: I couldn't get the Colossus to record decently with my Comcast RNG150, tried it on 2 systems, WHS 2011 and Win7 x64. HDMI didn't work, it said "it is not HDCP compliant, use component cables". I tried component with both optical and stereo, but recordings would either be "no signal" (the vast majority) or incomplete (most seemed to fail after around 16min). I rarely return anything but I got another HD-PVR (now F2 version) and hope it lasts at least another 3 years+ like the last one. Sigh.

Jim

[equalize]

Huappauge just posted 30151 drivers.

[SHS]

Originally Posted by equalize

Huappauge just posted 30151 drivers.

Cool I hope work better then last one

[KeithAbbott]

Originally Posted by SHS

Cool I hope work better then last one

If I had a nickel for every time we've said that about the latest and greatest Colossus driver...

[SHS]

Originally Posted by KeithAbbott

If I had a nickel for every time we've said that about the latest and greatest Colossus driver...

I would all ready been rich by now but you forget the some of the problem are in sagetv which never get fix and no word on weather not google plan on a PC DVR software and as it is Windows Media Center is DOA all ready.
At lease hauppauge make use of real time traslation encoding and hoplee we see thet standalone real time transcoding encoder

[HeLLx]

Hello I would like to know if anyone has a tutorial explaining how to make the recording .Mp4 because only I can do in .Ts

[sacrament055]

Ok I know I'm a bit late to this but from the latest Colossus driver

Release notes for colossus_30151_release:

Fix for video freeze after 10-20 minutes.
Added display of source info to property page.
Added SrcInfo property set.
Added h264 property set.
Changed audio sample rate and bit rate property values.
Added parameter checks to property pages.
General cleanup of bit rate handling.

The bold above caught my attention. Anyone tried these drivers yet? wonder if that's related to the sage issue we've seen.

[KeithAbbott]

Originally Posted by SHS

but you forget the some of the problem are in sagetv which never get fix

Which problems are you referring to? I'd like to know, so that I can decide whether a Colossus will ever work reliably for me or not.

Originally Posted by sacrament055

Release notes for colossus_30151_release:

Fix for video freeze after 10-20 minutes.
Added display of source info to property page.
Added SrcInfo property set.
Added h264 property set.
Changed audio sample rate and bit rate property values.
Added parameter checks to property pages.
General cleanup of bit rate handling.

The bold above caught my attention. Anyone tried these drivers yet? wonder if that's related to the sage issue we've seen.

I won't be able to try the new drivers until late August, after True Blood season 5 is finished. Can't risk having problems recording Alexander Skarsgård for my wife's weekly fix...

[SHS]

Originally Posted by sacrament055

Ok I know I'm a bit late to this but from the latest Colossus driver

Release notes for colossus_30151_release:

Fix for video freeze after 10-20 minutes.
Added display of source info to property page.
Added SrcInfo property set.
Added h264 property set.
Changed audio sample rate and bit rate property values.
Added parameter checks to property pages.
General cleanup of bit rate handling.

The bold above caught my attention. Anyone tried these drivers yet? wonder if that's related to the sage issue we've seen.

Keep in mind that I'm using HDMI with DirecTV which I'm going to have change to component video as well know some channel are get display error HDCP not supported on this display carp for now it only seem be the moive channel but that may change.
As for new 1.5.30151 ver it seem to work better then last few one's that for sure, No choppy video after several recordings now it seem to back to about 6 hours mark then it be come choppy video unlike some other ver where it was choppy video with in few hour's if not rigth way some times.
It maybe best to just stick with 1.2.29192 or what ever working for you.