New Hauppauge Beta Drivers for IVAC15/16 Combination

[Deadbolt]

Are these drivers different than the ones that Narflex posted?

[carlgar]

yes, see post #10 for one problem that they fixed.

[zz5]

Yes, they are.

22037 - current official drivers.
22077 - the ones Narflex posted.
22162 - these drivers.

Based on the numbering, these look to be a significant change.

[Opus4]

carlgar: I think stanger89 was simply offering another option for consideration that would get the window completely out of the way & I was confirming that a hw decoder can work that way, since he said he wasn't 100% sure about it. That option obviously doesn't _resize_ the window, so it couldn't be a solution for that problem.

- Andy

[carlgar]

sorry if I misunderstood the postings. I had the impression you were giving me work arounds. I will probably report this as a problem next week and see what Frey has to say about it.

[stanger89]

My understanding is that when using the TV-out of the 350 (at least with the OSD enabled) it forces the window to 720x480 (the same size as the TV-out) and there's no way around it. I believe this is to eliminate having to draw the UI/OSD twice, or something to that effect.

[carlgar]

If that is the case then they should be some type of warning when you try to enable the UI. Even with that limitation it seems that you would be able to disable the UI to regain the ability to resize the TV screen. That has to be bug or oversight somewhere in the logic. It is just not clear where or what the problem is. I personally bought the computer to work for me, so I really don't care how often it has to do something as long as it saves me time and effort and the program still works correctly.

[Opus4]

Originally posted by carlgar
sorry if I misunderstood the postings. I had the impression you were giving me work arounds. I will probably report this as a problem next week and see what Frey has to say about it.

I think it _was_ a work around since it was a way to get around the problem for a time being, so I don't think you misunderstood it.

And, reporting it is probbaly the best way to see if something can be done about it to actually solve it.

- Andy

[mikejaner]

mikejaner, did you have the colorbar problem with the 22037 drivers? Did these drivers fix your colorbar problem?

No, the 22037 drivers did not have colorbars for me. They went away, after the first reboot, which is when SageTV made the registry entry. I upgraded the drivers, rather than removed them this time, and the colorbars did not appear, like in the last beta drivers from a week or so ago.

[carlgar]

There still appear to be some problems in the drivers. I just had a 100% CPU lockup, does not appear to be same as I had before. The first sign of trouble was when I went to view a program, it played for a few seconds then stopped. I tried several, some had already been viewed, same problem. I then went to disable the 350 TV out and UI to isolate the problem. I believe it was the 350 TV-out I just disabled when I got the 100% CPU lockup.
When I rebooted the system I got a new hardware message for a Multimedia Video Controller. No idea what this is about but attempted to install automatically, install failed. SageTV appears to now be working properly again. The 350 TV out stuff was still enabled when I restarted SageTV.

[carlgar]

I just encountered another problem while viewing a program, both 350 TV out and the monitor program froze. The timeline indicatior was still moving forward. I have now gone back to 1.4 for reliability.

[kny3twalker]

the new hardware message for a Multimedia Video Controller
means you have to install the drivers again
you should not do automatic unless you have burnt these drivers to a CD/DVD and have it in your CD/DVD rom
you should do the advanced installation
and use the drivers again
I would try to update the drivers again to make sure your computer is using these new drivers if it is then it will say so when you try to update them
if you need more info on the drivers installation
check out the FAQs
I wrote a detailed explaination in there(sure you can do it just fine though)

[carlgar]

The first thing I did was to try to reinstall the drivers, but got message drivers not found. Thats when I tried the auto. I don't think it is the cards themselves, they all seem to be installed properly and SageTV 1.4 sees all of them. I do not check with 2.0 before removal but suspect it saw all 3 also.

[kny3twalker]

The first thing I did was to try to reinstall the drivers, but got message drivers not found.

how doing an advance installation then browsing for the folder with the system files
and unchecking all other options
then next until finish

or did you let windows search for the drivers itself?

what other multimedia video controller do you have?

does the device manager have the correct version when you look at the properties?

and all three card do not have an exclaimation right?

if everything looks good and recordings are good
I guess I would not worry about it too much either

[carlgar]

I tried the normal installation of telling the system where the drivers where. When it cannot find the drivers it is usually because the device it wants is not there. That is when I concluded that it was not one of my cards that it found.
I have no exclaimation points for any of my devices. However, I am now also encountering some problems with 1.4 while viewing files. I have see this type of problem before which switching between 2.0 and 1.4.

[carlgar]

I have more information concerning the new lockup issues with these drivers. While using SageTV 1.4 I encountered another problem where the screen froze. I believe this one is related to using too many or too fast of skip with the Hauppauge remote. Anyway in the process of trying too view another program I got another 100% CPU lock up. Again I had to reboot and got the new hardware found error. This time I looked at the device manager to see what it was complaining about, it was my first 250 card which has the remote sensor. The other 2 cards were fine. I then tried to reinstall these drivers again it failed. I then completely powered down the system and bought it back it. This time everything came up fine.

If case anyone thinks it may be heat related, I have case wide open.
Room temp is 76.7 degrees Fahrenheit
Processor Zone 102 degrees Fahrenheit
System Zone 1 is 91 degrees Fahrenheit
System Zone 2 is 97 degrees Fahrenheit

[carlgar]

I now believe most if not all of the problems were caused by an incompatable hcwi2c32.dll file. I need this file to get the Hauppauge remote to work and believe it should be included with the drivers. I was using the same version (2.7.20296.0) that I had used for the Narflex drivers. I now have version (2.8.21121.0) which I extracted from the SHS site. I have been running SageTV 1.4 for serveral hours with only 1 minor issue.

[carlgar]

Is anyone else having problems with these drivers using a 350 with tv out enabled?

I just got the following error when I tried viewing a new program after the tv and monitor froze.
There was a problem with time control in DirectShow
Failed pausing the directshow filter graph
Errcode=0x8007045d

[laurenglenn]

Originally posted by carlgar
Is anyone else having problems with these drivers using a 350 with tv out enabled?

I just got the following error when I tried viewing a new program after the tv and monitor froze.
There was a problem with time control in DirectShow
Failed pausing the directshow filter graph
Errcode=0x8007045d

Not me. In fact, my OSD is actually now working! I still can't believe it. Not to rub it in, but I'm almost afraid to change any settings in fear that it will crash again.....

What I did was to disable the onboard audio, turned off the Hauppauge Remote program, and then updated the drivers without using the Hauppauge Remove files. When it was updating, the colorbars went away and when I rebooted SageTV, I turned on the UI and it hasn't crashed yet....

Lauren

[mikejaner]

I've been up for about 40 hours with these new drivers and the 350 output enabled with no problem.