Does ANYONE have the UI working via the 350 out?

[chako]

Just trying to see if there is anyone who can use the complete package. I'm using 2.0.12 beta version of Sage.

I want to use my PVR-350 output to TV WITH onscreen UI ON THE TV SET.

In my case, once I enable the UI, everything seems to work fine for a few seconds and then it locks up. I can close Sage and start again without a reboot.

I used the new feature that disables the preview window ('never' setting) and I can move around all the menus without any trouble. I can go on for as long as I want through all the setup menus, favorites, etc.. you get the point.

Problem.. Once I watch ANYTHING, live tv or recorded, within about 10 seconds, Sage will lock up again.

If I don't use the onscreen UI, but just use the TV output so video and sound (no UI) are sent to my TV, it works flawlessly.

Again, here's my question, does anyone have the whole thing working without lockups every few minutes?

Thanks!

[Crashless]

I do, check my post in the other thread you asked this question.

[krutaw]

Originally posted by chako
I want to use my PVR-350 output to TV WITH onscreen UI ON THE TV SET.

In my case, once I enable the UI, everything seems to work fine for a few seconds and then it locks up. I can close Sage and start again without a reboot.

I thought you were off your rocker when I first read that, but after doing some testing, you're 100% right. This is *EXACTLY* the problem I'm having. I disabled the OSD through the PVR-350 and it's like a rock now. WOW!

Filing bug report right now.

[chako]

Crashless,

Yes, I saw your other post where you spoke of your success. Thanks for the help. Once I posted that message, it prompted me to start a thread since I suspect there are several people with this issue and I hope we can get it resolved. I filed a bug report after the first beta. I just wanted to make sure I wasn't alone.

Krutaw,

Glad you're having a little more success with it now. It's not as convenient without the UI enabled, but very solid... and yes... I AM off my rocker.

[mikejaner]

I have the 350 out working rock solid with the OSD enabled. I even have two tuners(which WAS a biatch to get working with 350 out), and and MCE remote working with Girder.
I have a suggestion. I built a machine from the ground up this week, and it improved the stability of the software tenfold, as opposed to the test machine I was using, which hasn't been rebuilt in at least a year.

mikejaner

[krutaw]

Originally posted by mikejaner
I have the 350 out working rock solid with the OSD enabled. I even have two tuners(which WAS a biatch to get working with 350 out), and and MCE remote working with Girder.
I have a suggestion. I built a machine from the ground up this week, and it improved the stability of the software tenfold, as opposed to the test machine I was using, which hasn't been rebuilt in at least a year.

mikejaner

I'm still wondering if it's just something that I've setup incorrectly. Could you post your properties file so those of us that are having problems can take a swing at it with your settings?

[Crashless]

Here's my properties file.

My specs:
Windows 2000 service pack 4
one pvr 350
sage 2.0.12
dishnetwork
los angeles

dedicated PC

[krutaw]

Originally posted by Crashless
Here's my properties file.

My specs:
Windows 2000 service pack 4
one pvr 350
sage 2.0.12
dishnetwork
los angeles

dedicated PC

Okay, so that proves it. It's not a setting, per se, in SAGETV 2.0. I wonder if there's a possibility of different hardware versions betwixt the PVR-350's?

[Crashless]

I have no idea. It could be a driver version thing I suppose. But I wasn't aware of more than one 350 h/w revision.

Maybe we should take a poll on chipsets and 350 UI working/not working. As well as slot position.

I would start it but I don't have a wide enough knowledge of chipsets to make an effective poll.

I have a Nforce2 chipset, using slot 2, and my 350 UI works.

[krutaw]

Originally posted by Crashless
I have no idea. It could be a driver version thing I suppose. But I wasn't aware of more than one 350 h/w revision.

Maybe we should take a poll on chipsets and 350 UI working/not working. As well as slot position.

I would start it but I don't have a wide enough knowledge of chipsets to make an effective poll.

I have a Nforce2 chipset, using slot 2, and my 350 UI works.

Do you think it's videocard related? Just asking because you mentioned the chipset of what I thought would be your videocard.

[Crashless]

Nope, Nforce2 is a chipset for AMD processors. But I AM using a Gforce440MX AGP graphics card.

[sonoman]

I have tried the 350 in each of the 3 pci slots available. Tried each of the 3 rendering filters available both with and without 3d acceleration. Tried both the intervideo NonCSS video decoder and the Cyberlink SP decoders. I have tried all of the above with each of the betas and all but the very latest (1.8.22035) drivers.

I always get the same result as Chako when the UI out is enabled. As soon as I have video the TV freezes and then the video on the pc monitor freezes. I noticed in the log something about an inactivity timeout at the time this happens.

I am going to try a clean install of Windows 2000 again when I get the time and try this all again.


Motherboard: Asus P4P800-VM with Intel 865G chipset
CPU: Pentium 4 2.6Ghz 400Mhz fsb
Memory: 512MB DDR 400
Video Card: Matrox G550
Sound Card M-Audio Revolution
(1) PVR 350
HDD: 250GB Western Digital
IR: Actisys IR-200L
OS: Windows 2000 SP4
DirectX 9B

[krutaw]

Originally posted by sonoman
I have tried the 350 in each of the 3 pci slots available. Tried each of the 3 rendering filters available both with and without 3d acceleration. Tried both the intervideo NonCSS video decoder and the Cyberlink SP decoders. I have tried all of the above with each of the betas and all but the very latest (1.8.22035) drivers.

I always get the same result as Chako when the UI out is enabled. As soon as I have video the TV freezes and then the video on the pc monitor freezes. I noticed in the log something about an inactivity timeout at the time this happens.

I am going to try a clean install of Windows 2000 again when I get the time and try this all again.


Motherboard: Asus P4P800-VM with Intel 865G chipset
CPU: Pentium 4 2.6Ghz 400Mhz fsb
Memory: 512MB DDR 400
Video Card: Matrox G550
Sound Card M-Audio Revolution
(1) PVR 350
HDD: 250GB Western Digital
IR: Actisys IR-200L
OS: Windows 2000 SP4
DirectX 9B

I have the exact same problem, and have tried everything that Sonoman mentions, and here are my details: (sorry I stole your format Sonoman):

Motherboard: Intel 845 chipset
CPU: Pentium 4 1.7 ghz
Memory: 512MB
Video Card: Nvidia GeForce MX420 (PCI)
Sound Card: SoundMax intergrated
(1) PVR 350
(1) PVR-250
HDD0: 40GB Western Digital
HDD1: 40GB Western Digital
HDD2: 30GB Western Digital
HDD3: 40GB Western Digital
IR: Hauppauge Silver through PVR-350
OS: Windows XP SP1
DirectX 9B

[mikejaner]

BTW, the new drivers work too.

I would try the following:
Download the latest CD (1.8.22035) and run a hcdclear.exe. Then uninstall the card(s). In your case Andy, remove your 250 for this. Then reboot windows and when it detects the card and asks for the drivers, point it to the cd in whatever folder you unzipped it to. Then run the setup from the cd and install at least WinTV and the IR drivers along with the Intervideo codec. Then go into sage and change the local playback codec to the Non-CSS one, not that it matters with local playback disabled. Let me know if this helps.

mikejaner

[krutaw]

Originally posted by mikejaner
BTW, the new drivers work too.

I would try the following:
Download the latest CD (1.8.22035) and run a hcdclear.exe. Then uninstall the card(s). In your case Andy, remove your 250 for this. Then reboot windows and when it detects the card and asks for the drivers, point it to the cd in whatever folder you unzipped it to. Then run the setup from the cd and install at least WinTV and the IR drivers along with the Intervideo codec. Then go into sage and change the local playback codec to the Non-CSS one, not that it matters with local playback disabled. Let me know if this helps.

mikejaner

I'll try that when I get home.

[pcuoco]

I have OSD working on the 350 out with and it's rock solid, with the exception of the picture shifting left after being put to sleep for awhile.

I'm running a dedicated Sage box, Sage Beta .12, XP SP1, an Old Asus P3B-F Mobo, with a PIII 650, 512MB Ram, and Matrox G400 video card.

Video renderer is set to default (used to use overlay in 1.4 with G400 out), disabled software decode, and enabled GUI on 350. It works great, an PQ is fantastic.

I also just rebuilt this machine just prior to the first V2 beta with a clean XP install. I never re-installed Sage 1.4, I just went straight to the Beta.

Hope this helps with the trouble shooting.


Paul

[krutaw]

Originally posted by pcuoco
I have OSD working on the 350 out with and it's rock solid, with the exception of the picture shifting left after being put to sleep for awhile.

I'm running a dedicated Sage box, Sage Beta .12, XP SP1, an Old Asus P3B-F Mobo, with a PIII 650, 512MB Ram, and Matrox G400 video card.

Video renderer is set to default (used to use overlay in 1.4 with G400 out), disabled software decode, and enabled GUI on 350. It works great, an PQ is fantastic.

I also just rebuilt this machine just prior to the first V2 beta with a clean XP install. I never re-installed Sage 1.4, I just went straight to the Beta.

Hope this helps with the trouble shooting.


Paul

Okay, that's it. I'm gonna rebuild the sagetv on an older box.. perhaps even an AMD. I want my OSD!

[chako]

Amen to that. I'm breaking open my old 350 mhz amd box. With HW encoding and decoding, maybe it will work great.

[EnderW]

I can't seem to find the option to Disable Local Playback. I can find every other option that you guys are talking about, except for that one.

I am using a 350 with beta 2.0.13

[eggs]

I am just a beginner, but it sure looks like Intel chipsets are having disproportionate # of problems with Sage. My MB uses VIA KT333 chipset and AMD CPU and has been relatively stable with both 13 and 14. Hopefully this chipset problem will be resolved eventually...