new anomoly with 7.1.7 and Colossus

[KeithAbbott]

Originally Posted by Tiki

I don't know about m2ts, but I don't think Sage has provided a way to change the container to anything other that .ts.

So much for my idea of trying .m2ts or .mp4 file formats. I'd still like to verify that others are seeing the same behavior, blue screens happening periodically during recordings and/or live TV, and no blue screens when switching to a channel with different screen resolution using Channel Preview. How about it, can anyone spend 20-30 minutes of their time verifying this behavior, so I can create a Sage bug report with the knowledge that it affects more than just me? If I have no other choice, I'll lock my STB output at 720p to avoid this problem, but I'd sure rather get the underlying problem resolved than resort to a workaround.

Put a different way, Sage is more likely to address the problem if there is more than one person interested in getting it resolved.

[Rico66]

Originally Posted by KeithAbbott

One other thought, the Colossus supports .ts, .m2ts, and .mp4 file formats. I know Sage supports .ts and .m2ts files, not sure about .mp4 files. So far, I've only tried this while Sage is configured to produce .ts files, it might be worth changing the Sage/Colossus configuration to produce .m2ts files, and see if the blue screen still happens. Can anyone point me to directions on how to configure Sage to produce .m2ts files directly from the Colossus?

I doubt that this would change anything. You see the blue screen also using Windows Media Center, which actually saves the recordings into wtv files (though those are likely also based on ts and simply remuxed into this container format)

[KeithAbbott]

Originally Posted by Rico66

You see the blue screen also using Windows Media Center

So much for my theory that it is a Sage problem, that would point to it being a Hauppauge problem. Still, why would the Channel Preview in Sage not get the blue screen? Still puzzled...

[Fuzzy]

Originally Posted by KeithAbbott

So much for my theory that it is a Sage problem, that would point to it being a Hauppauge problem. Still, why would the Channel Preview in Sage not get the blue screen? Still puzzled...

It still might. When you are talking about an intermittent problem, it's hard to say when it WON'T happen.

[tvmaster2]

Originally Posted by KeithAbbott

So much for my theory that it is a Sage problem, that would point to it being a Hauppauge problem. Still, why would the Channel Preview in Sage not get the blue screen? Still puzzled...

sorry, so the blue-screen happens using Windows Media Center as well?
I will support your bug report - the resolution disruption / blue-screen happened to me today when changing from 480i channel to 1080i channel. After the blue screen, Sage locked itself into a 4x3 mode, even after a channel change to another 1080i channel. It took three or four channel changes for Sage to correct itself to the correct resolution.
Why not just include this thread in the bug report - all the Sage "big wigs" are likely reading this anyway (at least I know the admins must be, as they don't miss much).
My problems started with 7.1.7 install.

[Rico66]

Originally Posted by tvmaster2

sorry, so the blue-screen happens using Windows Media Center as well?
I will support your bug report - the resolution disruption / blue-screen happened to me today when changing from 480i channel to 1080i channel. After the blue screen, Sage locked itself into a 4x3 mode, even after a channel change to another 1080i channel. It took three or four channel changes for Sage to correct itself to the correct resolution.
Why not just include this thread in the bug report - all the Sage "big wigs" are likely reading this anyway (at least I know the admins must be, as they don't miss much).
My problems started with 7.1.7 install.

I must admit, I only saw it once on the MC side (within the one week, since I switched). But I haven't seen it regularly on the Sage side neither. As mentioned previously, it seems to be some kind of timing issue, where the Colossus (HD PVR) is not fully ready, but the recording application is already capturing.

[tvmaster2]

Originally Posted by KeithAbbott

So much for my idea of trying .m2ts or .mp4 file formats. I'd still like to verify that others are seeing the same behavior, blue screens happening periodically during recordings and/or live TV, and no blue screens when switching to a channel with different screen resolution using Channel Preview. How about it, can anyone spend 20-30 minutes of their time verifying this behavior, so I can create a Sage bug report with the knowledge that it affects more than just me? If I have no other choice, I'll lock my STB output at 720p to avoid this problem, but I'd sure rather get the underlying problem resolved than resort to a workaround.

Put a different way, Sage is more likely to address the problem if there is more than one person interested in getting it resolved.

So what's happened since the 720p lock - any blue-screens?

[KeithAbbott]

Originally Posted by tvmaster2

So what's happened since the 720p lock - any blue-screens?

Haven't locked it yet. According to SHS, a Colossus driver update is expected by the end of this month. Being the optimist that I am, I'm hoping that the blue screen problem is fixed with the update. Either that, or maybe the next beta version of Sage. In any case, if it's not resolved by late June, I'll need to lock it to 720p so that the spousal-unit can record/watch season 4 of True Blood. Nothing can get between her and Alexander Skarsgård...

[Fuzzy]

Originally Posted by KeithAbbott

Nothing can get between her and Alexander Skarsgård...

My wife has the same affliction... I don't complain, because the guy looks just like me, so I guess it's a little flattering... :-)

[Vysrany]

I too see this problem, even on the included WinTV software. I locked my STB to 1080i though, and haven't seen the problem since.

[tvmaster2]

Originally Posted by Vysrany

I too see this problem, even on the included WinTV software. I locked my STB to 1080i though, and haven't seen the problem since.

has anyone notified Hauppauge about this, or Sage?

[jptheripper]

Originally Posted by KeithAbbott

Haven't locked it yet. According to SHS, a Colossus driver update is expected by the end of this month. Being the optimist that I am, I'm hoping that the blue screen problem is fixed with the update. Either that, or maybe the next beta version of Sage. In any case, if it's not resolved by late June, I'll need to lock it to 720p so that the spousal-unit can record/watch season 4 of True Blood. Nothing can get between her and Alexander Skarsgård...

For all the back and forth, i have had my settop locked at 720p since installing the colossus. It seems to me we have narrowed down the problem (or at least one problem) to resolution/and-or/audio format changes in the stream.

[coryking]

Just chiming in that I too get these "blue screen" recordings. Worse, I am getting a ton of real BSOD's—sometimes nightly. I am wondering if the two are related (sadly I lack the time to really dive in and troubleshoot as some in this thread have done). I've noticed these blue screen recordings followed shortly (less than an hour) by a BSOD.

As for the real BSOD, it is either the colossus or another bit of faulty hardware. I need to run a ram test but otherwise the only cause would be the colossus or the older HVR1600 in the box. That or a shotty power supply (though I don't see how a $100 power supply could be shotty). It couldn't be SageTV causing the BSOD—they would have to be doing something nuts to blue screen a box.

I will try playing with that "delay" propery and see if that fixes anything. I will post back my findings.

The joys of being an early adopter of hardware that only runs on beta versions of the seemingly most important production system in your house. :-)

[tvmaster2]

Originally Posted by coryking

Just chiming in that I too get these "blue screen" recordings. Worse, I am getting a ton of real BSOD's—sometimes nightly. I am wondering if the two are related (sadly I lack the time to really dive in and troubleshoot as some in this thread have done). I've noticed these blue screen recordings followed shortly (less than an hour) by a BSOD.

As for the real BSOD, it is either the colossus or another bit of faulty hardware. I need to run a ram test but otherwise the only cause would be the colossus or the older HVR1600 in the box. That or a shotty power supply (though I don't see how a $100 power supply could be shotty). It couldn't be SageTV causing the BSOD—they would have to be doing something nuts to blue screen a box.

I will try playing with that "delay" propery and see if that fixes anything. I will post back my findings.

The joys of being an early adopter of hardware that only runs on beta versions of the seemingly most important production system in your house. :-)

I too have been getting BSOD's, which I NEVER have had a problem with any Hauppauge/Sage combo to this point. So, it's either the newest Hauppauge driver? It's obvious we all have different hardware, so it's the card/software that's responding the same way to whatever external hardware is used.
What's the best way to send a group complaint to both manufacturers?

[gplasky]

Blue screens are usually device drivers problems. You should see the offending dll or exe causing the BSOD on screen. You should also configure Windows to do a memory dump so you can analyze it for the issue. You should also have various error logs that would help. If you can't analyze them at least collect them so you can forward them to anyone trying to assist you.

Gerry

[tvmaster2]

Originally Posted by gplasky

Blue screens are usually device drivers problems. You should see the offending dll or exe causing the BSOD on screen. You should also configure Windows to do a memory dump so you can analyze it for the issue. You should also have various error logs that would help. If you can't analyze them at least collect them so you can forward them to anyone trying to assist you.

Gerry

OK, I'll check for the offending dll the next time Sage BSOD's. As far as configuring windows for a dump, that's beyond my abilities I believe.

Honestly, I don't mind doing some research to see if I can repeat the problem, but I don't have many aspirations to work for Hauppauge and Sage as an unpaid researcher. I'm not trying to be glib, it's just not my job as a paying customer - it's theirs. Let's hope they are reading these forums to improve their quality control.

[coryking]

As a follow up... Setting the delay to 8 seconds has somewhat helped with the blue screen recordings. Might try setting it to 10 seconds.

I still get BSODs and the hauppauge support folk suggest pulling my older HVR1600 and seein if that fixes it.

[KeithAbbott]

Originally Posted by coryking

As a follow up... Setting the delay to 8 seconds has somewhat helped with the blue screen recordings. Might try setting it to 10 seconds.

Did you modify the delay_to_wait_after_tuning setting to 8 seconds, or was it a different setting? I upped the delay_to_wait_after_tuning setting to 30 seconds, and was still getting blue screens approximately 50% of the time when input resolution changed (e.g. 720p -> 1080i).

I guess I should also ask if you have your cable box locked to output a specific resolution, or do you have it set to pass the source resolution?

[sleonard]

Just a quick update on my Colossus. Since the latest driver a few weeks ago, I have not had any of the Colossus driver failures that caused stuttering, choppy video and ended with a forced restart of either the service or the computer but have had two blue recordings. One live and one scheduled. I have had several bad recordings from HD_PVR's but that's not new. I have never had any BSOD's for any reason.

I am now thinking about replacing the remaining two HD-PVR's with Colossi but it will require building a new server due to a lack of PCIe x1 slots in the current system.

S

[coryking]

Originally Posted by KeithAbbott

Did you modify the delay_to_wait_after_tuning setting to 8 seconds, or was it a different setting? I upped the delay_to_wait_after_tuning setting to 30 seconds, and was still getting blue screens approximately 50% of the time when input resolution changed (e.g. 720p -> 1080i).

I guess I should also ask if you have your cable box locked to output a specific resolution, or do you have it set to pass the source resolution?

Yes, the delay_to_wait_after_tuning.

I do not have my cable box locked to a specific resolution. I plan to do what the Hauppage people say and take out the HVR1600 first. If that doesn't fix it, I'll keep the resolution fixed (or just do whatever they tell me to do next).