SageTV Community  

Go Back   SageTV Community > SageTV BETA Release Products > SageTV Beta Test Software

Notices

SageTV Beta Test Software Discussion related to BETA Releases of the SageTV application produced by SageTV. Questions, issues, problems, suggestions, etc. regarding SageTV Beta Releases should be posted here.

Reply
 
Thread Tools Search this Thread Display Modes
  #41  
Old 10-30-2010, 09:51 AM
mbowling mbowling is offline
Sage Advanced User
 
Join Date: Sep 2008
Location: Cascade Mountains of Oregon
Posts: 223
Quote:
Originally Posted by Monedeath View Post
It seems to be that something in 7.0.22 is the culprit behind the broken 2250 QAM tuners in WHS.
I also upgraded from .21 to .22 and my 2250 QAM tuner would not work. I'm using Windows XP. I rolled back to .21 and the tuner is working again.
Reply With Quote
  #42  
Old 10-30-2010, 10:21 AM
bialio's Avatar
bialio bialio is offline
SageTVaholic
 
Join Date: May 2007
Location: Frisco, TX
Posts: 3,445
Same here. 21 works on XP. 22 doesn't.

btl.
__________________
PHOENIX 3 is here!
Server : Linux V9, Clients : Win10 and Nvidia Shield Android Miniclient
Reply With Quote
  #43  
Old 10-30-2010, 11:25 AM
rxnelson rxnelson is offline
Sage Advanced User
 
Join Date: Sep 2010
Posts: 121
About the same. XP. Converting from test machine to production machine and 2250 throws errors when trying to add digital tuner during setup. Continue and no channels found. Scans really fast though . Reverted to .21 and no setup errors and channels are found. Scanning takes much longer for whatever that's worth. Still need logs?
Reply With Quote
  #44  
Old 10-30-2010, 11:52 AM
heffe2001's Avatar
heffe2001 heffe2001 is offline
Sage Icon
 
Join Date: Mar 2004
Location: Conover, NC
Posts: 1,269
I rolled back to .20, and it works perfectly again (hit the wrong installer in the addins, doing an upgrade to .21 as I type).

.21 exhibits the exact same behavior on my system as .22, no QAM channels will tune. I sent the above logs to donkey as per his request (from my non-working .22). I've rolled back AGAIN to .20, and all's peachy again..
__________________
Server: AMD Phenom 2 920 2.8ghz Quad, 16gb Ram, 4tb Storage, 1xHVR-2250, 1 Ceton Cable Card adapter, Windows 7 SP1

Last edited by heffe2001; 10-30-2010 at 12:15 PM.
Reply With Quote
  #45  
Old 10-30-2010, 06:17 PM
jbrandon's Avatar
jbrandon jbrandon is offline
Sage Advanced User
 
Join Date: Oct 2009
Location: Gladstone, MO
Posts: 153
Well after reading this I checked and sure enough I can no longer view or recorded on any of the 2250 QAM tuners either. I don’t have time tonight to look up the file that was messed up several times before but I think it is about time that Sage do a little better job of source code control…

I too rolled back to .21 and all is okay again – at least for now.
Reply With Quote
  #46  
Old 10-30-2010, 06:34 PM
Monedeath Monedeath is offline
Sage Expert
 
Join Date: Sep 2009
Location: Idaho
Posts: 513
Quote:
Originally Posted by jbrandon View Post
Well after reading this I checked and sure enough I can no longer view or recorded on any of the 2250 QAM tuners either. I don’t have time tonight to look up the file that was messed up several times before but I think it is about time that Sage do a little better job of source code control…
I'm under the impression that the only difference between the WHS distributions and the Normal Windows one is that the WHS install has a different wrapper to work with the WHS installer.

As the Windows7 users run the same installer as the WindowsXP users run, they run nearly completely on the same code base, with only minimal branching going on if they're managing their code well. Same story for WHS.

So chance are what they changed to fix Windows7 was outside of the Win7 specific branch, and was enough to zap the other Windows users(at least for WinXP and WHS, haven't noticed anything about anyone on Vista).
Reply With Quote
  #47  
Old 10-30-2010, 07:47 PM
heffe2001's Avatar
heffe2001 heffe2001 is offline
Sage Icon
 
Join Date: Mar 2004
Location: Conover, NC
Posts: 1,269
Quote:
Originally Posted by jbrandon View Post
Well after reading this I checked and sure enough I can no longer view or recorded on any of the 2250 QAM tuners either. I don’t have time tonight to look up the file that was messed up several times before but I think it is about time that Sage do a little better job of source code control…

I too rolled back to .21 and all is okay again – at least for now.
If this were a release version, I'd be inclined to be a bit more angry about changes from one module breaking others, but I can't really complain since I've chosen to run a potentially non-stable Beta/RC.

As for my system, it's running fine on .20, so I'll leave it as-is until Donkey tells me to do otherwise, lol.
__________________
Server: AMD Phenom 2 920 2.8ghz Quad, 16gb Ram, 4tb Storage, 1xHVR-2250, 1 Ceton Cable Card adapter, Windows 7 SP1
Reply With Quote
  #48  
Old 10-30-2010, 08:57 PM
donkey donkey is offline
Sage Aficionado
 
Join Date: Sep 2005
Posts: 275
Here is a fix
http://download.sage.tv/users/qian/7...howCapture.dll
this HVR-2250 bug affects XP, WHS only.
Thank heffe2001 for helping test.
Qian
__________________
Qian
Reply With Quote
  #49  
Old 10-30-2010, 09:04 PM
heffe2001's Avatar
heffe2001 heffe2001 is offline
Sage Icon
 
Join Date: Mar 2004
Location: Conover, NC
Posts: 1,269
That fix worked perfectly on my system. I'm still debating loading newer versions of the 2250 drivers though. Last time I tried, the system would blue-screen whenever the 2250 was accessed by the system... It's getting my QAM stuff now tho, so maybe I should leave well enough alone..
__________________
Server: AMD Phenom 2 920 2.8ghz Quad, 16gb Ram, 4tb Storage, 1xHVR-2250, 1 Ceton Cable Card adapter, Windows 7 SP1
Reply With Quote
  #50  
Old 10-31-2010, 02:47 AM
Monedeath Monedeath is offline
Sage Expert
 
Join Date: Sep 2009
Location: Idaho
Posts: 513
Quote:
Originally Posted by donkey View Post
Here is a fix
http://download.sage.tv/users/qian/7...howCapture.dll
this HVR-2250 bug affects XP, WHS only.
Thank heffe2001 for helping test.
Qian
You would think they would have incremented that .dll file to .25 in the 9-ish builds(depending on how you want to count some of the updates that didn't increment the beta/RC's) since the file was introduced as a quick-fix.

Edit: Nevermind, they incremented to .34 in the 7.0.22 build, and it was .33 on the 7.0.21 build as I go back and double check that file. Testing the .35 version of the .dll file now.

Testing complete, had my ATSC Tuner(HVR-1850) and 4 QAM Tuners(HVR-2250s) running at the same time on 7.0.22 so the 3.0.0.35 version of the .dll fixes it. Good work.

Last edited by Monedeath; 10-31-2010 at 03:02 AM.
Reply With Quote
Reply

Tags
2250, clear qam, suddenlink


Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)
 
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
HVR-2250/SageTV 6.2 Issue Orizimo Hardware Support 1 06-05-2010 10:14 AM
WinTV-HVR-2250, USBbuirt & Dish Vip 211k issue changing channel CiscoSquaD Hardware Support 0 03-23-2010 07:25 PM
Hauppage 2250 and Clear QAM will Hardware Support 17 12-19-2009 05:56 PM
HVR-2250 (QAM) strange Capture issue wado1971 Hardware Support 3 11-29-2008 08:54 PM
HVR-950 and Clear QAM sdsean Hardware Support 3 07-22-2008 10:04 AM


All times are GMT -6. The time now is 09:49 AM.


Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2020, vBulletin Solutions Inc.
Copyright 2003-2005 SageTV, LLC. All rights reserved.