![]()  | 
	
		
			
  | 
	|||||||
| 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. | 
![]()  | 
	
	
| 
		 | 
	Thread Tools | Search this Thread | Display Modes | 
| 
		 
			 
			#1  
			
			
			
			
			
		 
		
	 | 
||||
		
		
  | 
||||
| 
		
	
		
		
			
			 
				
				Capture Error in playback
			 
			
			
			I am having a problem were each time I start the SageTV Service the first time I go to view Live TV I get a capture error -4,0x80004002.  I hit stop, and go back to Live TV and everything works fine.  This is really anoying and I have found no solution at this point.  I have upgraded the PVR 250 drivers to the latest version, I have upgraded to the latest Sage Beta. 
		
		
		
		
		
		
		
		
	
	Config: Windows 2003 Server Dual CPU AMD 1800 Machine PVR 250 (Latest Drivers) Any help would be really appreciated!  | 
| 
		 
			 
			#2  
			
			
			
			
			
		 
		
	 | 
||||
		
		
  | 
||||
| 
		
	
		
		
		
		 
			
			Bump for anyone that might have any idea what my problem is!
		 
		
		
		
		
		
		
		
		
	
	 | 
| 
		 
			 
			#3  
			
			
			
			
			
		 
		
	 | 
||||
		
		
  | 
||||
| 
		
	
		
		
		
		 
			
			Since you said you are running the latest beta, you should have a log file (sagetv_0.txt) that you could submit to SageTV. 
		
		
		
		
		
		
			- Andy 
				__________________ 
		
		
		
		
		
	
	SageTV Open Source v9 is available. - Read the SageTV FAQ. Older PDF User's Guides mostly still apply: SageTV V7.0 & SageTV Studio v7.1. - Hauppauge remote help: 1) Basics/Extending it 2) Replace it 3) Use it w/o needing focus - HD Extenders: A) FAQs B) URC MX-700 remote setup Note: This is a users' forum; see the Rules. For official tech support fill out a Support Request.  | 
| 
		 
			 
			#4  
			
			
			
			
			
		 
		
	 | 
||||
		
		
  | 
||||
| 
		
	
		
		
		
		 
			
			I will submit a bug requets, but just to be more clear this is not a new version 6 bug.  I had the same problem in version 5.  I was hoping the upgrade might solve the problem.
		 
		
		
		
		
		
		
		
		
	
	 | 
![]()  | 
	
	
| Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
		
  | 
	
		
  |