Hauppauge Colossus HD-PVR

[panteragstk]

Originally Posted by Rico66

That's not a Colossus problem, it's just Sage. You can playback/record SD Colossus recordings outside of Sage just fine.

I can't. The have the exact same issues as sage does. Non issue for me because my 1600 has the extra tuner.

[texneus]

Originally Posted by panteragstk

No problem. I don't use the colossus for SD material. It REALLY doesn't like sd.

What problem(s) are you seeing? I'm recording/viewing SD material just fine with the colossus.

[texneus]

Originally Posted by panteragstk

I honestly think the STB is to blame. It seems to be the only variable in the colossus equation. Maybe there was no issue because it was a constant audio stream? I'd test a blu-ray player locked at 720p with the same audio config as your stb and see if it happens. I bet it doesn't.

I'm convinced it is a local head end issue. The drift only happens when they (FiOS in my case) insert local commercials into the feed, resulting in a loss of audio sync of about 1/8 second each time the feed is interrupted. Several others have reported the same thing. Specifically I think this happens when the audio stream is interrupted or changes formats (though I have not dug into this any further).

Naturally, anything producing a constant audio stream, be it blu-ray, dvd, a channel with no commercials, or a channel that does not have local commercials inserted will not show a problem.

[Rico66]

Originally Posted by texneus

I'm convinced it is a local head end issue. The drift only happens when they (FiOS in my case) insert local commercials into the feed, resulting in a loss of audio sync of about 1/8 second each time the feed is interrupted. Several others have reported the same thing. Specifically I think this happens when the audio stream is interrupted or changes formats (though I have not dug into this any further).

Naturally, anything producing a constant audio stream, be it blu-ray, dvd, a channel with no commercials, or a channel that does not have local commercials inserted will not show a problem.

Yes, that's what I've seen as well. I do get audio out of sync, if the commercials are inserted into the programming.

But the whole thing may well be driver related as well. In my case I've found exactly one driver version that doesn't cause any AAC/AC3 issue (=recording with no audio) at all (I'm using 29168). Any other driver that I've tried will have the no audio issue at some stage (the newer ones are especially bad, as I've lost audio after just one channel change...).
I can live with the slight out of sync, as it's mainly happening during sports, where it's only noticable when the commenators are shown in picture.

[panteragstk]

Originally Posted by texneus

What problem(s) are you seeing? I'm recording/viewing SD material just fine with the colossus.

Mostly audio issues. Not sync issues, but for some reason the speed of the audio has slowed down. Very strange.

[panteragstk]

Originally Posted by texneus

I'm convinced it is a local head end issue. The drift only happens when they (FiOS in my case) insert local commercials into the feed, resulting in a loss of audio sync of about 1/8 second each time the feed is interrupted. Several others have reported the same thing. Specifically I think this happens when the audio stream is interrupted or changes formats (though I have not dug into this any further).

Naturally, anything producing a constant audio stream, be it blu-ray, dvd, a channel with no commercials, or a channel that does not have local commercials inserted will not show a problem.

Yep. The way the commercials are inserted and the way the audio stream is presented to the colossus are what cause the issues. I guess DirecTV does it in a way that the colossus likes. I have zero issues with sync. It has never been an issue. The ONLY issue I've ever had other than SD is it would mistake ac3 for pcm and attempt to encode to aac. That hasn't happened in a long time.

[sacrament055]

Is there any way to improve the issue shs mentioned with stuttering after a few hours worth of recording? I've seen this but wasn't home when it happened so I'm curious how much experimentation has been done with this. Does a single 3+ hour recording stutter or does it have to be several smaller recordings that tie up more interupts and that's what leads to the problem. I noticed all recordings that showed this problem were listed as AAC audio although I also had recordings that were listed as AAC that played back fine.

For the record I submitted a bug with SageTV bug report link to see if they can correct the interupt problem or at least advise a way to minimize it.

[SHS]

Well it want try out this set new of drivers
http://www.shspvr.com/ftp/download/c..._1.2.29287.zip
So far seem be work well
But I haven't had free time to really push them with 30 min recording for 5+ hour

[KeithAbbott]

Also looks like there is a new 29291 beta driver out today.

[SHS]

Originally Posted by KeithAbbott

Also looks like there is a new 29291 beta driver out today.

That just figger

[sacrament055]

I noticed you guys posted this last night so I'm curious if anybody installed them yet?

[panteragstk]

To be honest, I've got a solid system. The only way I'd install a new driver was if hauppauge found a way to lock onto the audio stream better so I can lower my delay to record time. 10 sec channel changes can be annoying.

[sacrament055]

Originally Posted by panteragstk

To be honest, I've got a solid system. The only way I'd install a new driver was if hauppauge found a way to lock onto the audio stream better so I can lower my delay to record time. 10 sec channel changes can be annoying.

Got it. I did notice the notes for the latest beta on Hauppages's site indicate a fix for BSOD issue with SageTV so it's good to see they're still fixing things for Sage.

When you say 10 seconds, are you rounding up or did you find that 8 seconds wasn't enough delay?

[SHS]

Originally Posted by sacrament055

I noticed you guys posted this last night so I'm curious if anybody installed them yet?

The one's I posted I all ready had them install for about 6 days now

[tvmaster2]

Originally Posted by sacrament055

Got it. I did notice the notes for the latest beta on Hauppages's site indicate a fix for BSOD issue with SageTV so it's good to see they're still fixing things for Sage.

When you say 10 seconds, are you rounding up or did you find that 8 seconds wasn't enough delay?

is that the Blue Screen that happens when changing channels with different resoltions, or a windows BSOD? Have they fixed the resolution blue-screen yet to your knowledge, aka where if changing from a 480i to a 1080i channel or back again causes your screen to go blue

[sacrament055]

Originally Posted by tvmaster2

is that the Blue Screen that happens when changing channels with different resoltions, or a windows BSOD? Have they fixed the resolution blue-screen yet to your knowledge, aka where if changing from a 480i to a 1080i channel or back again causes your screen to go blue

I believe the reference in their notes was to a quad Colossus Sage Server blue screen. Not sure if this could have some relation to the CPU interupts mentioned by SHS though.

I just got My Colossus late last week and a haven't seen the bluescreen you described yet.

[tvmaster2]

Originally Posted by sacrament055

I believe the reference in their notes was to a quad Colossus Sage Server blue screen. Not sure if this could have some relation to the CPU interupts mentioned by SHS though.

I just got My Colossus late last week and a haven't seen the bluescreen you described yet.

If I lock my receiver's output to 720p, then Colossus could handle the change, but when Colossus saw 1080i switching to 480i it barfed.

[panteragstk]

Originally Posted by sacrament055

When you say 10 seconds, are you rounding up or did you find that 8 seconds wasn't enough delay?

Literally 10 seconds. I still got incorrectly flagged audio when it was set to 8 sec. Hasn't happened since I upped it to 10. I'll let you know if it continues to work well.

I may try these drivers if I ever have another issue. I just don't want to run HWCLEAR and have to reinstall all of my hauppauge drivers. I plan to have at least 3 colossus' soon so I may have to.

[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.

[TechBill]

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.

Darn I had hopes but glad to see someone else is reporting this issue too so hopefully somewhere there will be a fix and nightly reboots is no longer needed


Bill