Hauppauge Colossus HD-PVR

[SHS]

sleonard thanks I think I may have solve the mystery to it maybe, the interrupts maybe the root to all are problem so in that case it has be Colossus drivers or some other software that the Colossus is using.
Usely the interrupts should drop back down when a capture stops but it case it not dropping so each time you start a new capture it get higher and higher.
I tested the HD-PVR all it self which had avg of 2.0/1.5 CPU Usage and when I stop the capture in SageTV or Showbiz the CPU Usage always drop back down to 0.25 CPU Usage or less and never got higher and higher after each restart, but with Colossus this is a diff story which had avg of 4.0/3.5 CPU Usage and when I stop the capture in SageTV or Showbiz the CPU Usage should have drop back down 0.25 CPU Usage but it dosen't it end up 3.50/3.00 and if you start a capture CPU Usage get higher and higher after each start and stop even SageTV start glowing in CPU Usage man that very odd I all ready talk to Hauppauge.

[TechBill]

Originally Posted by SHS

sleonard thanks I think I may have solve the mystery to it maybe, the interrupts maybe the root to all are problem so in that case it has be Colossus drivers or some other software that the Colossus is using.
Usely the interrupts should drop back down when a capture stops but it case it not dropping so each time you start a new capture it get higher and higher.
I tested the HD-PVR all it self which had avg of 2.0/1.5 CPU Usage and when I stop the capture in SageTV or Showbiz the CPU Usage always drop back down to 0.25 CPU Usage or less and never got higher and higher after each restart, but with Colossus this is a diff story which had avg of 4.0/3.5 CPU Usage and when I stop the capture in SageTV or Showbiz the CPU Usage should have drop back down 0.25 CPU Usage but it dosen't it end up 3.50/3.00 and if you start a capture CPU Usage get higher and higher after each start and stop even SageTV start glowing in CPU Usage man that very odd I all ready talk to Hauppauge.

I hope you solved it too and that hauppauge will be willing to investage this with you.

I been hoping to stop nightly reboot one of those days.

Bill

[SHS]

Originally Posted by TechBill

I hope you solved it too and that hauppauge will be willing to investage this with you.

I been hoping to stop nightly reboot one of those days.

Bill

Me to but this new drivers dose work well even knowing I have still do nightly reboot it still far better then some older one's before this.

[panteragstk]

Originally Posted by SHS

Me to but this new drivers dose work well even knowing I have still do nightly reboot it still far better then some older one's before this.

What's better? Audio issues? You say you have to reboot still, which is fine, but I'd like to know if the audio lock (aac instead of DD) issue is fixed.

[SHS]

The Video side of things I start experiencing choppy, stuttering recordings sometime much sooner then 4 hour like with 29111 or 29192
All my recording are AAC I haven't tested DD with HDMI sorry I can't used the other one my DirecTV dox dosen't have it.

[metzz71]

All, with the audio sync problem, do you have TWO Colussus cards installed?

[uberpixel]

Just one card here...

And by audio issue I would describe mine as out of sync (getting progressively worse as the recording progresses) when connected via SPDIF.

-uberpixel

[sacrament055]

Is there a common theme to the resolution you use that goes out of sync? is 1080i worse than 720p? the Stuttering SHS referred to is that more common on a particular resolution? I'd really like to get one of these but I can't bring myself to pull the trigger until I know it's possible to make it work reliably or the WAF is going to suffer a major blow.

[panteragstk]

Originally Posted by sacrament055

Is there a common theme to the resolution you use that goes out of sync? is 1080i worse than 720p? the Stuttering SHS referred to is that more common on a particular resolution? I'd really like to get one of these but I can't bring myself to pull the trigger until I know it's possible to make it work reliably or the WAF is going to suffer a major blow.

I don't have audio sync issues. I use native resolution so I have 720p and 1080i recordings. 95% of my recordings are perfect. The other 5% are incorrectly flagged as aac audio instead of dolby digital.

[metzz71]

Bottom line, the driver does not know what the f to do with a particular input stream from some STBs. I have two cards, tried one, tried 720 or 1080 stream, no dice. However, the HDPVR works just fine! this is going to be very difficult to solve when they don't have the source to work with.

[sacrament055]

Originally Posted by SHS

sleonard thanks I think I may have solve the mystery to it maybe, the interrupts maybe the root to all are problem so in that case it has be Colossus drivers or some other software that the Colossus is using.
Usely the interrupts should drop back down when a capture stops but it case it not dropping so each time you start a new capture it get higher and higher.
I tested the HD-PVR all it self which had avg of 2.0/1.5 CPU Usage and when I stop the capture in SageTV or Showbiz the CPU Usage always drop back down to 0.25 CPU Usage or less and never got higher and higher after each restart, but with Colossus this is a diff story which had avg of 4.0/3.5 CPU Usage and when I stop the capture in SageTV or Showbiz the CPU Usage should have drop back down 0.25 CPU Usage but it dosen't it end up 3.50/3.00 and if you start a capture CPU Usage get higher and higher after each start and stop even SageTV start glowing in CPU Usage man that very odd I all ready talk to Hauppauge.

Any update on this SHS?

[SHS]

Originally Posted by sacrament055

Any update on this SHS?

None thing so far an update gose

[patja]

Originally Posted by panteragstk

The other 5% are incorrectly flagged as aac audio instead of dolby digital.

I am curious if you have a method of re-flagging them as dolby digital and salvaging the recording.

[BobPhoenix]

Originally Posted by patja

I am curious if you have a method of re-flagging them as dolby digital and salvaging the recording.

For me it is just the first few seconds of the show that are truely AAC. The rest is Dolby Digital but SageTV uses that first bit as the definition of the rest of the video. I was able to remove that part of the video with a now expired option of DVDFab but the resulting video had the audio out of sync by the amount of time that was recorded as AAC at the begining. Didn't get around to adjusting the audio to put it into sync.

[panteragstk]

Originally Posted by patja

I am curious if you have a method of re-flagging them as dolby digital and salvaging the recording.

Don't waste your time. The audio was too out of sync to get it right. I got close, but it was much easier to re-record. It hasn't happened in a VERY long time. If it does again I will try to see what I can do.

[sacrament055]

Question for colossus users. I finally ordered one and wondered how much of the tweaking from tbis thread is still required to make it work correctly off a DirecTV box using hdmi? Ther was talk of modifhing sage.properties files to adjust recording delay and color as well references to some reg tweak for hauppage to sync audio... Are these things still required?

Lastly I remember mention of a sage tweak to record at a higher quality setting

Thanks

[panteragstk]

I used to have a 12 sec delay to make sure recordings were good. I think the default is 4. I've since built a new server and kept everything at the default. No issues yet. All I did was install the driver and start recording. Nothing to tweak for me using HDMI. DirecTV box set to native resolution with dolby digitial enabled. All is well.

[sacrament055]

Originally Posted by panteragstk

I used to have a 12 sec delay to make sure recordings were good. I think the default is 4. I've since built a new server and kept everything at the default. No issues yet. All I did was install the driver and start recording. Nothing to tweak for me using HDMI. DirecTV box set to native resolution with dolby digitial enabled. All is well.

Thanks, as a follow up question im curious which driver you're using?

[SHS]

Follow up

Hauppauge said they can see the issue with sage increasing the interrupt but have not been able to replicate it with other applications. In arcsoft given the same systems They do not see a difference in cpu usage for the interrupts between a colossus and hd-pvr.
So I sitting there thinking Hmm I think I know why I see a diff I was using original colossus arcsoft showbiz (3.5.17.70) and didn't update to latest 3.5.17.77 just for this reason why I didn't update because the darn thing would lock up the system when close out capture to point where I have to do a hard reset but with 3.5.17.77 I do see it that holding it cpu usage at avg 6/7 better then 3.5.17.70 so I guest we all have live every day reboot.
I most like end up going to MediaPortal later next year for now this have to do.

[panteragstk]

Originally Posted by sacrament055

Thanks, as a follow up question im curious which driver you're using?

29192