Hauppauge Colossus HD-PVR

[SHS]

Originally Posted by sacrament055

FYI, I am running the latest Hauppage drivers now and they seem no better from what I've seen. I was able to reproduce the same issue SHS mentioned again after about 15 to 20 "recordings/channel changes".
I've opened a case with Sage and they originally responded by asking if I've tried the latest beta and I have now answered that it didn't help. We'll see what happens but I'm hoping since they said Colossus was supported as part of this release that they will fix it.

Ture but are you going sitting there recording lots little show at 30 mins each now are you?.
Rigth now I think there good enough with 1.2.29291 beta
On plus side DD works more soild for me under HDMI unlike with some pass drivers which didn't make me very happy at all over all and all day recoding work good so far where in the pass the system would lockup or even crash&reboot with 10/12 hours that was with mix recording.
The only downside with SageTV are every day reboot which I can live with but perf that didn't have to do that.

[spacecadet]

How are you guys managing to install 1.2.29291? When I download it from the Hauppauge support site, the zip file does not include the setup EXE or the INF files. What am I missing?

[sacrament055]

Originally Posted by spacecadet

How are you guys managing to install 1.2.29291? When I download it from the Hauppauge support site, the zip file does not include the setup EXE or the INF files. What am I missing?

I kept the setup file and replaced the individual drivers/folders with the new ones.. seemed to work for me.

SHS -
I just did some channel surfing not tons of small recordings but that is the equivalent as every channel change starts a new recording so if you have people that surf tv at home it will reproduce this problem. Daily reboots are helpful but don't solve the problem in that case.

[SHS]

Channel surfing, Channel hopping or Channel zapping is not good idea that what your Electronic Program guides/TV guides/TV listings is for.

[SWKerr]

I have been using the 1.2.29291 driver on the test box I am using for WMC for the last few days. This is a single Colossus setup with a DirecTV H20 with Component\optical. I changed back to the HD-PVRs awhile back on the SageTV server. (Still have a Colossus in it just not using it.)

I have had a audio issue with the Colossus with something along the lines of 1 out of 10 recording not having valid audio. This is pretty much the same problem I had with SageTV.

The latest driver did not seem fix my problem. I also had a hard lockup after about two days of heavy recording. I changed the delay on the IR Blaster to 9000 (3x standard) but it does not appear to help the issue.

I don't have a tool that tells me if there is audio in the corrupt files they just don't play back. In SageTV they would be jumpy but would would kind of play. I think it is the same issue for both.

[SHS]

Originally Posted by SWKerr

The latest driver did not seem fix my problem. I also had a hard lockup after about two days of heavy recording. I changed the delay on the IR Blaster to 9000 (3x standard) but it does not appear to help the issue.

You want change start record delay not the IR delay
Reset Tuner Control - Remote Control Option back to
3
None
None
600
800
2

Close SageTV then open the Sage.properties notepad find the line video_capture_device_name=Hauppauge Colossus Capture look just above that for this delay_to_wait_after_tuning=0 change 0 to 6000 that give you a 6 sec delay that solve audio issue with DD ends up as AAC with HDMI and Optical.

I don't have a tool that tells me if there is audio in the corrupt files they just don't play back. In SageTV they would be jumpy but would would kind of play. I think it is the same issue for both.

I have scane that issue where it would not play in anything in pass drivers but with latest drivers I get that ocen in moonblue and it will not playback in SageTV but will in 3rdparty like VideoLan or WMP sometime if I restart SageTV Client it work.

[panteragstk]

I found something strange yesterday. I had a total of 3 recordings in a row that were all marked aac incorrectly. They were 3 30min shows back to back. The first had no audio. The last two played back perfectly. Weird.

[mistergq]

I am going back to the HD PVR. I am working with Hauppauge for one problem. This past Wednesday, my Colossus disappeared from STV and Arcsoft. It appears that a windows DLL has become corrupted.

Overall, I am just sick of the audio/video sync issue with fios and commercials either being in SD or local commercials. I was debating about this move for awhile, especially with Monday Night Football on ESPN, but with this last problem, and after a couple of hours trying to fix it, I decided to go back to the HD PVR.

[sacrament055]

Out of curiosity I know I read on the HD-PVR threads that you can modify sage settings to give higher quality recording options, does that apply to Colossus as well (does it even work?)

Thanks,

[SHS]

Originally Posted by sacrament055

Out of curiosity I know I read on the HD-PVR threads that you can modify sage settings to give higher quality recording options, does that apply to Colossus as well (does it even work?)

Thanks,

Yes it works

[Wrx4me]

Since I have had the Colossus, the 1.2.29291 driver has been the best so far. I am now able to run my Colossus with optical audio along with my 2 HD-PVR's without my server locking up as it did before.

The clincher for me was to increase the colossus channel change delay to 8000. I was able to run the colossus all weekend with DD 5.1 and no lockups. Of course I still have my nightly reboots going which helps.

[Skirge01]

I installed the Colossus on my test system using the 1.2.29287 drivers and immediately was able to reproduce the stuttering bug after about 10 channel changes.

@Wrx4me: Have you tested that at all with the 1.2.29291 drivers? I was planning to give them a shot this weekend.

Has anyone had any luck with Hauppauge support regarding this issue? It seems to be talked about quite a bit, but not much in the way of support's responses.

[sacrament055]

Originally Posted by Skirge01

I installed the Colossus on my test system using the 1.2.29287 drivers and immediately was able to reproduce the stuttering bug after about 10 channel changes.

@Wrx4me: Have you tested that at all with the 1.2.29291 drivers? I was planning to give them a shot this weekend.

Has anyone had any luck with Hauppauge support regarding this issue? It seems to be talked about quite a bit, but not much in the way of support's responses.

Yes I reproduced the stuttering with the newest driver. Just like you said I changed channels a few times (somewhere between 15 and 20) before it started stuttering.

As has been pointed out in this thread before it appears to be related to interupts not being released when a recording ends so you need to restart the sagetv service to free them back up. If you don't do heavy recording or channel surfing you can get by with nightly reboots but this is still not an ideal solution.

I have a case opened with SageTV and they told me they would forward my findings to Hauppage. I have not opened a case with Hauppage directly though.

[Wrx4me]

Originally Posted by Skirge01

I installed the Colossus on my test system using the 1.2.29287 drivers and immediately was able to reproduce the stuttering bug after about 10 channel changes.

@Wrx4me: Have you tested that at all with the 1.2.29291 drivers? I was planning to give them a shot this weekend.

Has anyone had any luck with Hauppauge support regarding this issue? It seems to be talked about quite a bit, but not much in the way of support's responses.

Well, because I have 3 Hauppauge tuners (5 total) When I change channels a different tuner often picks up that request so rarely does my colossus handle mutiple channel changes since it is third on the tuner priority list.

I will test in the tuner setup screen and see if multiple channel changes causes stuttering even though that wasn't my main issue.

I still get high memory utilization which is taken care of by the nightly service restarts. I am just happy I can now get DD 5.1 on my colossus without locking up my server with the spinning icon.

[SHS]

sacrament055
proper line
mmc/python2_encoding/Colossus\ Max\ Constant\ Rate=videobitrate\=20000000|vbr\=0|outputstreamtype\=1
mmc/python2_encoding/Colossus\ Max\ Variable\ Rate=videobitrate\=13500000|vbr\=1|peakvideobitrate\=20000000|outputstreamtype\=1

[Skirge01]

Originally Posted by sacrament055

I have a case opened with SageTV and they told me they would forward my findings to Hauppage. I have not opened a case with Hauppage directly though.

I'm not so sure I'd rely on SageTV support at this point in time. Perhaps we need to try and duplicate it in the Hauppauge software. If we can, then Hauppauge wouldn't be able to point the finger at SageTV being the culprit. I'll see about doing just that this coming weekend.

[panteragstk]

Originally Posted by Skirge01

I'm not so sure I'd rely on SageTV support at this point in time. Perhaps we need to try and duplicate it in the Hauppauge software. If we can, then Hauppauge wouldn't be able to point the finger at SageTV being the culprit. I'll see about doing just that this coming weekend.

That's exactly what they'll ask you to do. At least they asked me to use showbiz to reproduce my issue.

[Skirge01]

Originally Posted by panteragstk

That's exactly what they'll ask you to do. At least they asked me to use showbiz to reproduce my issue.

That was my experience when I contacted them during my first foray into the HD-PVR realms, so I fully expected that. This time, I'm not doing it on a production system, so I can keep messing with drivers and any other software they want me to, without worrying about the live system breaking.

[metzz71]

+1 for going back to HDPVR

[sacrament055]

Originally Posted by SHS

sacrament055
proper line
mmc/python2_encoding/Colossus\ Max\ Constant\ Rate=videobitrate\=20000000|vbr\=0|outputstreamtype\=1
mmc/python2_encoding/Colossus\ Max\ Variable\ Rate=videobitrate\=13500000|vbr\=1|peakvideobitrate\=20000000|outputstreamtype\=1

Thanks