SageTV Community  

Go Back   SageTV Community > SageTV Development and Customizations > SageTV Github Development
Reload this Page Hauppauge 2250 Data Scan Failure
Forum Rules FAQs Community Downloads Today's Posts Search

Notices

SageTV Github Development Discussion related to SageTV Open Source Development. Use this forum for development topics about the Open Source versions of SageTV, hosted on Github.

Reply
Page 1 of 2 1 2
 
Thread Tools Search this Thread Display Modes
  #1  
Old 09-19-2016, 07:13 AM
KarylFStein KarylFStein is offline
Sage Fanatic
  
Join Date: Apr 2006
Location: Westland, Michigan, USA
Posts: 999
Hauppauge 2250 Data Scan Failure
I'm getting the following warning on a regular basis after my last update of the Sage JAR:

The capture device input Hauppauge WinTV-7164 Analog Capture Digital TV Tuner had a failure while trying to start scanning for data on its channels.

I can tune OTA channels directly, but recordings fall to using CableCard, (the OTA tuners have a higher merit and used to be chosen first).
__________________
Home Network: https://karylstein.com/technology.html
Reply With Quote
  #2  
Old 09-19-2016, 05:40 PM
KarylFStein KarylFStein is offline
Sage Fanatic
  
Join Date: Apr 2006
Location: Westland, Michigan, USA
Posts: 999
Well, this seems to have cleared up on its own. I was poking around at it, but don't think I did anything other than try and get more logs. My recordings tonight are back to using the OTA as primary, though, and I don't see any recent warnings posted...
__________________
Home Network: https://karylstein.com/technology.html
Reply With Quote
  #3  
Old 09-20-2016, 05:55 AM
KarylFStein KarylFStein is offline
Sage Fanatic
  
Join Date: Apr 2006
Location: Westland, Michigan, USA
Posts: 999
Scratch that. I got 120 of these errors over the night...
__________________
Home Network: https://karylstein.com/technology.html
Reply With Quote
  #4  
Old 09-20-2016, 07:31 AM
jptheripper jptheripper is offline
Sage Fanatic
  
Join Date: Dec 2007
Location: Florida
Posts: 956
This may be related to the same error I am having on my 2250. When you preview a channel, do you get an error code?
__________________
Gigabyte GA-MA770-DS3/4gb DDR2/AMD Phenom 955 3.2ghz Quad Core
Windows 7 64bit Home Premium
Hauppauge 1600/1850/2250/colossus/2650(CableCard 2 tuner)
8tb RAID5 storage/media/other &3tb RAID5 backup storage on a HighPoint RocketRaid 2680
1tb 3 disk Recording Pool
all in a beautiful Antec 1200
SageMyMovies/Comskip/PlayON/SageDCT/SRE
HD100/HD300 extenders
Reply With Quote
  #5  
Old 09-20-2016, 08:13 AM
KarylFStein KarylFStein is offline
Sage Fanatic
  
Join Date: Apr 2006
Location: Westland, Michigan, USA
Posts: 999
No, preview in setup and payback from guide work fine.
__________________
Home Network: https://karylstein.com/technology.html
Reply With Quote
  #6  
Old 10-01-2016, 09:36 AM
KarylFStein KarylFStein is offline
Sage Fanatic
  
Join Date: Apr 2006
Location: Westland, Michigan, USA
Posts: 999
I've been trying to track this down more as I'm still getting tons of these per day. It seems to happen in Seeker trying to enable data scanning. I was trying to put some more logging in there because I didn't see a stack trace in the logs, but it looks like SageAlert might hijack the main log file (?). Anyway, I believe this is the error:

Code:
Enabling data scanning for input Hauppauge WinTV-7164 Analog Capture Digital TV Tuner
setEncodingProperties0 1194098056 Great
Set encoding property audiooutputmode to 0
Set encoding property audiocrc to 0
Set encoding property gopsize to 15
Set encoding property videobitrate to 3800000
Set encoding property inversetelecine to 0
Set encoding property closedgop to 0
Set encoding property vbr to 0
Set encoding property outputstreamtype to 10
Set encoding property width to 720
Set encoding property height to 480
Set encoding property audiobitrate to 384
Set encoding property audiosampling to 48000
Set encoding property disablefilter to 1
Set encoding property medianfilter to 3
Set encoding property fps to 30
Set encoding property ipb to 0
Set encoding property deinterlace to 0
Set encoding property aspectratio to 1
setupEncoding0 called for 1194098056 'Hauppauge WinTV-7164 Analog Capture-0' (ver 1.0)
QAM:Got capture drv info for QAM mfg:'Hauppauge' Hauppauge WinTV-7164 Analog Capture-0
QAM: Hauppauge QAM interface not found (0) hr=0x80070492 at Hauppauge WinTV-7164 Analog Capture-0 
QAM:not supported Hauppauge WinTV-7164 Analog Capture-0
Encoding to /dev/null ;)
setupEncoding0 Trace27 
setupEncoding0 Trace28 
startEncoding0 called for 'Hauppauge WinTV-7164 Analog Capture-0'
Failed: startEncoding0 Run return code:8007001f  1
Built:sage.EncodingException: ERROR (-4,0x8007001f): There was an problem using the capture device. Please be sure you have the latest drivers installed for your capture device, and that they are installed correctly.
ERROR enabling data scanning of:sage.EncodingException: ERROR (-4,0x8007001f): There was an problem using the capture device. Please be sure you have the latest drivers installed for your capture device, and that they are installed correctly.
sage.EncodingException: ERROR (-4,0x8007001f): There was an problem using the capture device. Please be sure you have the latest drivers installed for your capture device, and that they are installed correctly.
	at sage.DShowCaptureDevice.startEncoding0(Native Method)
	at sage.DShowCaptureDevice.startEncodingSync(DShowCaptureDevice.java:250)
	at sage.Sage.processMsg(Sage.java:1851)
	at sage.Sage$8.run(Sage.java:1793)
I did see something about some Hauppauge cards needing a driver update after the W10 anniversary update, so did that as well with no change. Other thoughts?
__________________
Home Network: https://karylstein.com/technology.html
Reply With Quote
  #7  
Old 10-03-2016, 03:42 PM
Fuzzy's Avatar
Fuzzy Fuzzy is offline
SageTVaholic
  
Join Date: Sep 2005
Location: Jurupa Valley, CA
Posts: 9,957
Isn't the 2250's digital tuner called something different? That appears to be trying to use the 'Hauppauge WinTV-7164 Analog Capture-0' device, which I think, as the name implies, is the analog capture device on the card (for analog tuning and/or composite/s-video capture).
__________________
Buy Fuzzy a beer! (Fuzzy likes beer)

unRAID Server: i7-6700, 32GB RAM, Dual 128GB SSD cache and 13TB pool, with SageTVv9, openDCT, Logitech Media Server and Plex Media Server each in Dockers.
Sources: HRHR Prime with Charter CableCard. HDHR-US for OTA.
Primary Client: HD-300 through XBoxOne in Living Room, Samsung HLT-6189S
Other Clients: Mi Box in Master Bedroom, HD-200 in kids room
Reply With Quote
  #8  
Old 10-03-2016, 05:05 PM
tmiranda's Avatar
tmiranda tmiranda is offline
SageTVaholic
  
Join Date: Jul 2005
Location: Central Florida, USA
Posts: 5,851
Quote:
Originally Posted by Fuzzy View Post
Isn't the 2250's digital tuner called something different? That appears to be trying to use the 'Hauppauge WinTV-7164 Analog Capture-0' device, which I think, as the name implies, is the analog capture device on the card (for analog tuning and/or composite/s-video capture).
I think that's normal. I have a 2250 and it still says "analog capture device" even after selecting the digital tuner.
__________________

Sage Server: 8th gen Intel based system w/32GB RAM running Ubuntu Linux, HDHomeRun Prime with cable card for recording. Runs headless. Accessed via RD when necessary. Four HD-300 Extenders.
Reply With Quote
  #9  
Old 10-03-2016, 05:11 PM
KarylFStein KarylFStein is offline
Sage Fanatic
  
Join Date: Apr 2006
Location: Westland, Michigan, USA
Posts: 999
Quote:
Originally Posted by Fuzzy View Post
Isn't the 2250's digital tuner called something different? That appears to be trying to use the 'Hauppauge WinTV-7164 Analog Capture-0' device, which I think, as the name implies, is the analog capture device on the card (for analog tuning and/or composite/s-video capture).
That is what the device is called on the top level. When adding the source you get a choice of what input to use one of which is the Digital TV Tuner. It tunes fine, but I'm getting over 100 of these warnings per day which is a recent development. It started happening after the stuckless Phoenix/BMT/Core update, (which I installed too quickly hoping that would fix my fanart issues). I also went from JAVA 7 to 8 right after that because Gemstone broke and I was trying to see if that would fix it. The W10 Anniversary and Hauppauge driver updates happened a couple days later and did not change anything.

This is the init stuff as far as I can tell:

Code:
Mon 10/3 17:06:07.855 [main@1f4acd0] network encoder version:3.0
Mon 10/3 17:06:07.858 [main@1f4acd0] Parsed network encoder major version: 3
Mon 10/3 17:06:07.910 [main@1f4acd0] network encoder version:3.0
Mon 10/3 17:06:07.916 [main@1f4acd0] Parsed network encoder major version: 3
Mon 10/3 17:06:07.974 [main@1f4acd0] network encoder version:3.0
Mon 10/3 17:06:07.978 [main@1f4acd0] Parsed network encoder major version: 3
Mon 10/3 17:06:08.027 [main@1f4acd0] Doing broadcast discovery of new encoding servers on the network...
Mon 10/3 17:06:08.034 [main@1f4acd0] Discovery packet received:java.net.DatagramPacket@32be31
Mon 10/3 17:06:08.095 [main@1f4acd0] Added server info:0:0:0:0:0:0:0:0,V4.1.0,192.168.1.2
Mon 10/3 17:06:11.027 [main@1f4acd0] Error discovering servers:java.net.SocketTimeoutException: Receive timed out
Mon 10/3 17:06:11.031 [main@1f4acd0] Connected to encoding server at 192.168.1.2
Mon 10/3 17:06:11.037 [main@1f4acd0] Ignoring network encoder because it's already in our config: 741291179
Mon 10/3 17:06:11.040 [main@1f4acd0] Ignoring network encoder because it's already in our config: 741291183
Mon 10/3 17:06:11.043 [main@1f4acd0] Ignoring network encoder because it's already in our config: 741291184
Mon 10/3 17:06:11.046 [main@1f4acd0] Ignoring network encoder because it's already in our config: 741291181
Mon 10/3 17:06:11.049 [main@1f4acd0] Ignoring network encoder because it's already in our config: 741291182
Mon 10/3 17:06:11.052 [main@1f4acd0] Ignoring network encoder because it's already in our config: 741291180
Mon 10/3 17:06:11.055 [main@1f4acd0] devices detected=[DCT-Ceton InfiniTV PCIe (00-80-8b-81) Tuner 5 on 127.0.0.1:9000, DCT-Ceton InfiniTV PCIe (00-80-8b-81) Tuner 3 on 127.0.0.1:9000, DCT-Ceton InfiniTV PCIe (00-80-8b-81) Tuner 6 on 127.0.0.1:9000, DCT-Ceton InfiniTV PCIe (00-80-8b-81) Tuner 4 on 127.0.0.1:9000, DCT-Ceton InfiniTV PCIe (00-80-8b-81) Tuner 1 on 127.0.0.1:9000, DCT-Ceton InfiniTV PCIe (00-80-8b-81) Tuner 2 on 127.0.0.1:9000]
Mon 10/3 17:06:11.058 [main@1f4acd0] EncoderMap={DCT-Ceton InfiniTV PCIe (00-80-8b-81) Tuner 2 on 127.0.0.1:9000=DCT-Ceton InfiniTV PCIe (00-80-8b-81) Tuner 2 on 127.0.0.1:9000, DCT-Ceton InfiniTV PCIe (00-80-8b-81) Tuner 5 on 127.0.0.1:9000=DCT-Ceton InfiniTV PCIe (00-80-8b-81) Tuner 5 on 127.0.0.1:9000, DCT-Ceton InfiniTV PCIe (00-80-8b-81) Tuner 4 on 127.0.0.1:9000=DCT-Ceton InfiniTV PCIe (00-80-8b-81) Tuner 4 on 127.0.0.1:9000, DCT-Ceton InfiniTV PCIe (00-80-8b-81) Tuner 1 on 127.0.0.1:9000=DCT-Ceton InfiniTV PCIe (00-80-8b-81) Tuner 1 on 127.0.0.1:9000, DCT-Ceton InfiniTV PCIe (00-80-8b-81) Tuner 3 on 127.0.0.1:9000=DCT-Ceton InfiniTV PCIe (00-80-8b-81) Tuner 3 on 127.0.0.1:9000, DCT-Ceton InfiniTV PCIe (00-80-8b-81) Tuner 6 on 127.0.0.1:9000=DCT-Ceton InfiniTV PCIe (00-80-8b-81) Tuner 6 on 127.0.0.1:9000}
Mon 10/3 17:06:11.061 [main@1f4acd0] MMC calling detectCaptureDevices on sage.DShowCaptureManager@9ba398
Mon 10/3 17:06:11.064 [main@1f4acd0] Splash: DirectShow WDM Capture Manager is initializing...
Mon 10/3 17:06:11.069 [main@1f4acd0] Setup globalInvalidParameterHandler
Mon 10/3 17:06:11.069 [main@1f4acd0] Device detecting->:{65E8773D-8F56-11D0-A3B9-00A0C9223196}
Mon 10/3 17:06:11.074 [main@1f4acd0] Device found--'Hauppauge WinTV-7164 Analog Capture'
Mon 10/3 17:06:11.074 [main@1f4acd0] Device found--'Hauppauge WinTV-7164 Analog Capture'
Mon 10/3 17:06:11.074 [main@1f4acd0] Device detecting->:{FD0A5AF4-B41D-11d2-9C95-00C04F7971E0}
Mon 10/3 17:06:11.075 [main@1f4acd0] Device found--'Hauppauge WinTV-7164 BDA Digital Capture'
Mon 10/3 17:06:11.075 [main@1f4acd0] Device found--'Hauppauge WinTV-7164 BDA Digital Capture'
Mon 10/3 17:06:11.076 [main@1f4acd0] Device detecting->:{71985F48-1CA1-11d3-9CC8-00C04F7971E0}
Mon 10/3 17:06:11.077 [main@1f4acd0] Device found--'Hauppauge WinTV-7164 BDA ATSC/QAM Tuner'
Mon 10/3 17:06:11.077 [main@1f4acd0] Device found--'Hauppauge WinTV-7164 BDA ATSC/QAM Tuner'
Mon 10/3 17:06:11.077 [main@1f4acd0] Device found 'Hauppauge WinTV-7164 Analog Capture'
Mon 10/3 17:06:11.077 [main@1f4acd0] Device found 'Hauppauge WinTV-7164 Analog Capture'
Mon 10/3 17:06:11.077 [main@1f4acd0] systemCapDevices=[Hauppauge WinTV-7164 Analog Capture, Hauppauge WinTV-7164 Analog Capture]
Mon 10/3 17:06:11.081 [main@1f4acd0] Checking encoder key:60838500
Mon 10/3 17:06:11.084 [main@1f4acd0] Checking encoder key:1749782242
Mon 10/3 17:06:11.087 [main@1f4acd0] Checking encoder key:-783633371
Mon 10/3 17:06:11.090 [main@1f4acd0] Checking encoder key:905310371
Mon 10/3 17:06:11.093 [main@1f4acd0] Checking encoder key:-856241312
Mon 10/3 17:06:11.096 [main@1f4acd0] Checking encoder key:-112107779
Mon 10/3 17:06:11.101 [main@1f4acd0] Created DShowCapDev object for:Hauppauge WinTV-7164 Analog Capture
Mon 10/3 17:06:11.104 [main@1f4acd0] Checking encoder key:-1700713183
Mon 10/3 17:06:11.107 [main@1f4acd0] Checking encoder key:1681743986
Mon 10/3 17:06:11.111 [main@1f4acd0] Created DShowCapDev object for:Hauppauge WinTV-7164 Analog Capture #2
Mon 10/3 17:06:11.114 [main@1f4acd0] EncoderMap1={Hauppauge WinTV-7164 Analog Capture=Hauppauge WinTV-7164 Analog Capture, Hauppauge WinTV-7164 Analog Capture #2=Hauppauge WinTV-7164 Analog Capture #2}
Mon 10/3 17:06:11.186 [main@1f4acd0] Capture device Hauppauge WinTV-7164 Analog Capture (0) exists
Mon 10/3 17:06:11.187 [main@1f4acd0] Get CaptureMask from registry SOFTWARE\Frey Technologies\Common\AdditionalCaptureSetups\Hauppauge WinTV-7164 Analog Capture, 0x8800 (hybrid:'')
Mon 10/3 17:06:11.187 [main@1f4acd0] @DEBUG@ device found 'Hauppauge WinTV-7164 Analog Capture' (index:0) for 'Hauppauge WinTV-7164 Analog Capture'.
Mon 10/3 17:06:11.189 [main@1f4acd0] Device desc:'@oem14.inf,%halesite.devicedesc8851%;Hauppauge WinTV-HVR-2250 (8851)'.
Mon 10/3 17:06:11.189 [main@1f4acd0] It's Hauppauge device.
Mon 10/3 17:06:11.193 [main@1f4acd0] BAD Tuner index :1 dev:\\?\pci#ven_1131&dev_7164&subsys_88510070&rev_81#4&211c806e&0&00e6#{65e8773d-8f56-11d0-a3b9-00a0c9223196}\{bd5b5aea-2141-48a8-8758-f0cf5e0bc800} name:@device:pnp:\\?\pci#ven_1131&dev_7164&subsys_88510070&rev_81#4&211c806e&0&00e6#{65e8773d-8f56-11d0-a3b9-00a0c9223196}\{bd5b5aea-2141-48a8-8758-f0cf5e0bc800} loc:pci:8-0 (1 0) select
Mon 10/3 17:06:11.193 [main@1f4acd0] Check BDA capture device:Hauppauge WinTV-7164 Analog Capture-0 (\\?\pci#ven_1131&dev_7164&subsys_88510070&rev_81#4&211c806e&0&00e6#{65e8773d-8f56-11d0-a3b9-00a0c9223196}\{bd5b5aea-2141-48a8-8758-f0cf5e0bc800}) on location:'pci:8-0' id:'PCI\VEN_1131&DEV_7164&SUBSYS_88510070&REV_81' [state1, index:0] .
Mon 10/3 17:06:11.194 [main@1f4acd0] >>BDA capture device found:@device:pnp:\\?\pci#ven_1131&dev_7164&subsys_88510070&rev_81#4&211c806e&0&00e6#{fd0a5af4-b41d-11d2-9c95-00c04f7971e0}\{b3e3d165-54eb-4b9e-a805-1756644fa400}; loc:'pci:8-0' id:'PCI\VEN_1131&DEV_7164&SUBSYS_88510070&REV_81' guid:b3e3d165-54eb-4b9e-a805-1756644fa400 desc:@oem14.inf,%halesite.devicedesc8851%;Hauppauge WinTV-HVR-2250 (8851)
Mon 10/3 17:06:11.194 [main@1f4acd0] BDA Capture found: (0) @device:pnp:\\?\pci#ven_1131&dev_7164&subsys_88510070&rev_81#4&211c806e&0&00e6#{fd0a5af4-b41d-11d2-9c95-00c04f7971e0}\{b3e3d165-54eb-4b9e-a805-1756644fa400} on loc pci:8-0.
Mon 10/3 17:06:11.194 [main@1f4acd0] >>BDA capture device found:@device:pnp:\\?\pci#ven_1131&dev_7164&subsys_88510070&rev_81#4&211c806e&0&00e6#{fd0a5af4-b41d-11d2-9c95-00c04f7971e0}\{b3e3d165-54eb-4b9e-a805-1756644fa401}; loc:'pci:8-0' id:'PCI\VEN_1131&DEV_7164&SUBSYS_88510070&REV_81' guid:b3e3d165-54eb-4b9e-a805-1756644fa401 desc:@oem14.inf,%halesite.devicedesc8851%;Hauppauge WinTV-HVR-2250 (8851)
Mon 10/3 17:06:11.194 [main@1f4acd0] BDA Capture found: (1) @device:pnp:\\?\pci#ven_1131&dev_7164&subsys_88510070&rev_81#4&211c806e&0&00e6#{fd0a5af4-b41d-11d2-9c95-00c04f7971e0}\{b3e3d165-54eb-4b9e-a805-1756644fa401} on loc pci:8-0.
Mon 10/3 17:06:11.194 [main@1f4acd0] Mutil-tuner(2) BDA capture is found on location:'pci:8-0' id:'PCI\VEN_1131&DEV_7164&SUBSYS_88510070&REV_81' for Hauppauge WinTV-7164 Analog Capture-0. (@device:pnp:\\?\pci#ven_1131&dev_7164&subsys_88510070&rev_81#4&211c806e&0&00e6#{fd0a5af4-b41d-11d2-9c95-00c04f7971e0}\{b3e3d165-54eb-4b9e-a805-1756644fa400},0,desc:@oem14.inf,%halesite.devicedesc8851%;Hauppauge WinTV-HVR-2250 (8851)).
Mon 10/3 17:06:11.194 [main@1f4acd0] BDA CaptureDetail:0x8800; hasBDAInput:0x2; BDA type:0x0
Mon 10/3 17:06:11.195 [main@1f4acd0] fake BDA crossbar cap0 is added for Hauppauge WinTV-7164 Analog Capture..
Mon 10/3 17:06:11.195 [main@1f4acd0] DeviceCap: 0x8810
Mon 10/3 17:06:11.201 [main@1f4acd0] BAD Tuner index :1 dev:\\?\pci#ven_1131&dev_7164&subsys_88510070&rev_81#4&211c806e&0&00e6#{65e8773d-8f56-11d0-a3b9-00a0c9223196}\{bd5b5aea-2141-48a8-8758-f0cf5e0bc800} name:@device:pnp:\\?\pci#ven_1131&dev_7164&subsys_88510070&rev_81#4&211c806e&0&00e6#{65e8773d-8f56-11d0-a3b9-00a0c9223196}\{bd5b5aea-2141-48a8-8758-f0cf5e0bc800} loc:pci:8-0 (1 0) select
Mon 10/3 17:06:11.201 [main@1f4acd0] Check BDA capture device:Hauppauge WinTV-7164 Analog Capture-0 (\\?\pci#ven_1131&dev_7164&subsys_88510070&rev_81#4&211c806e&0&00e6#{65e8773d-8f56-11d0-a3b9-00a0c9223196}\{bd5b5aea-2141-48a8-8758-f0cf5e0bc800}) on location:'pci:8-0' id:'PCI\VEN_1131&DEV_7164&SUBSYS_88510070&REV_81' [state1, index:0] .
Mon 10/3 17:06:11.202 [main@1f4acd0] >>BDA capture device found:@device:pnp:\\?\pci#ven_1131&dev_7164&subsys_88510070&rev_81#4&211c806e&0&00e6#{fd0a5af4-b41d-11d2-9c95-00c04f7971e0}\{b3e3d165-54eb-4b9e-a805-1756644fa400}; loc:'pci:8-0' id:'PCI\VEN_1131&DEV_7164&SUBSYS_88510070&REV_81' guid:b3e3d165-54eb-4b9e-a805-1756644fa400 desc:@oem14.inf,%halesite.devicedesc8851%;Hauppauge WinTV-HVR-2250 (8851)
Mon 10/3 17:06:11.202 [main@1f4acd0] BDA Capture found: (0) @device:pnp:\\?\pci#ven_1131&dev_7164&subsys_88510070&rev_81#4&211c806e&0&00e6#{fd0a5af4-b41d-11d2-9c95-00c04f7971e0}\{b3e3d165-54eb-4b9e-a805-1756644fa400} on loc pci:8-0.
Mon 10/3 17:06:11.202 [main@1f4acd0] >>BDA capture device found:@device:pnp:\\?\pci#ven_1131&dev_7164&subsys_88510070&rev_81#4&211c806e&0&00e6#{fd0a5af4-b41d-11d2-9c95-00c04f7971e0}\{b3e3d165-54eb-4b9e-a805-1756644fa401}; loc:'pci:8-0' id:'PCI\VEN_1131&DEV_7164&SUBSYS_88510070&REV_81' guid:b3e3d165-54eb-4b9e-a805-1756644fa401 desc:@oem14.inf,%halesite.devicedesc8851%;Hauppauge WinTV-HVR-2250 (8851)
Mon 10/3 17:06:11.202 [main@1f4acd0] BDA Capture found: (1) @device:pnp:\\?\pci#ven_1131&dev_7164&subsys_88510070&rev_81#4&211c806e&0&00e6#{fd0a5af4-b41d-11d2-9c95-00c04f7971e0}\{b3e3d165-54eb-4b9e-a805-1756644fa401} on loc pci:8-0.
Mon 10/3 17:06:11.202 [main@1f4acd0] Mutil-tuner(2) BDA capture is found on location:'pci:8-0' id:'PCI\VEN_1131&DEV_7164&SUBSYS_88510070&REV_81' for Hauppauge WinTV-7164 Analog Capture-0. (@device:pnp:\\?\pci#ven_1131&dev_7164&subsys_88510070&rev_81#4&211c806e&0&00e6#{fd0a5af4-b41d-11d2-9c95-00c04f7971e0}\{b3e3d165-54eb-4b9e-a805-1756644fa400},0,desc:@oem14.inf,%halesite.devicedesc8851%;Hauppauge WinTV-HVR-2250 (8851)).
Mon 10/3 17:06:11.203 [main@1f4acd0] Found the pin2 ;)
Mon 10/3 17:06:11.203 [main@1f4acd0] BDA FindVideoPin:0x4731092c hasBDAInput:2 on Hauppauge WinTV-7164 Analog Capture
Mon 10/3 17:06:11.234 [main@1f4acd0] Encoder passed the check:Hauppauge WinTV-7164 Analog Capture
Mon 10/3 17:06:11.238 [main@1f4acd0] Saving properties file to C:\Program Files (x86)\SageTV\SageTV\Sage.properties
Mon 10/3 17:06:11.265 [main@1f4acd0] Done writing out the data to the properties file
Mon 10/3 17:06:11.270 [main@1f4acd0] Capture device Hauppauge WinTV-7164 Analog Capture (1) exists
Mon 10/3 17:06:11.271 [main@1f4acd0] Get CaptureMask from registry SOFTWARE\Frey Technologies\Common\AdditionalCaptureSetups\Hauppauge WinTV-7164 Analog Capture, 0x8800 (hybrid:'')
Mon 10/3 17:06:11.271 [main@1f4acd0] @DEBUG@ device found 'Hauppauge WinTV-7164 Analog Capture' (index:1) for 'Hauppauge WinTV-7164 Analog Capture'.
Mon 10/3 17:06:11.272 [main@1f4acd0] @DEBUG@ device found 'Hauppauge WinTV-7164 Analog Capture' (index:0) for 'Hauppauge WinTV-7164 Analog Capture'.
Mon 10/3 17:06:11.273 [main@1f4acd0] Device desc:'@oem14.inf,%halesite.devicedesc8851%;Hauppauge WinTV-HVR-2250 (8851)'.
Mon 10/3 17:06:11.273 [main@1f4acd0] It's Hauppauge device.
Mon 10/3 17:06:11.276 [main@1f4acd0] BAD Tuner index :1 dev:\\?\pci#ven_1131&dev_7164&subsys_88510070&rev_81#4&211c806e&0&00e6#{65e8773d-8f56-11d0-a3b9-00a0c9223196}\{bd5b5aea-2141-48a8-8758-f0cf5e0bc801} name:@device:pnp:\\?\pci#ven_1131&dev_7164&subsys_88510070&rev_81#4&211c806e&0&00e6#{65e8773d-8f56-11d0-a3b9-00a0c9223196}\{bd5b5aea-2141-48a8-8758-f0cf5e0bc800} loc:pci:8-0 (1 0) select
Mon 10/3 17:06:11.276 [main@1f4acd0] BAD Tuner index :2 dev:\\?\pci#ven_1131&dev_7164&subsys_88510070&rev_81#4&211c806e&0&00e6#{65e8773d-8f56-11d0-a3b9-00a0c9223196}\{bd5b5aea-2141-48a8-8758-f0cf5e0bc801} name:@device:pnp:\\?\pci#ven_1131&dev_7164&subsys_88510070&rev_81#4&211c806e&0&00e6#{65e8773d-8f56-11d0-a3b9-00a0c9223196}\{bd5b5aea-2141-48a8-8758-f0cf5e0bc801} loc:pci:8-0 (2 0) select
Mon 10/3 17:06:11.276 [main@1f4acd0] Check BDA capture device:Hauppauge WinTV-7164 Analog Capture-1 (\\?\pci#ven_1131&dev_7164&subsys_88510070&rev_81#4&211c806e&0&00e6#{65e8773d-8f56-11d0-a3b9-00a0c9223196}\{bd5b5aea-2141-48a8-8758-f0cf5e0bc801}) on location:'pci:8-0' id:'PCI\VEN_1131&DEV_7164&SUBSYS_88510070&REV_81' [state1, index:1] .
Mon 10/3 17:06:11.277 [main@1f4acd0] >>BDA capture device found:@device:pnp:\\?\pci#ven_1131&dev_7164&subsys_88510070&rev_81#4&211c806e&0&00e6#{fd0a5af4-b41d-11d2-9c95-00c04f7971e0}\{b3e3d165-54eb-4b9e-a805-1756644fa400}; loc:'pci:8-0' id:'PCI\VEN_1131&DEV_7164&SUBSYS_88510070&REV_81' guid:b3e3d165-54eb-4b9e-a805-1756644fa400 desc:@oem14.inf,%halesite.devicedesc8851%;Hauppauge WinTV-HVR-2250 (8851)
Mon 10/3 17:06:11.277 [main@1f4acd0] BDA Capture found: (0) @device:pnp:\\?\pci#ven_1131&dev_7164&subsys_88510070&rev_81#4&211c806e&0&00e6#{fd0a5af4-b41d-11d2-9c95-00c04f7971e0}\{b3e3d165-54eb-4b9e-a805-1756644fa400} on loc pci:8-0.
Mon 10/3 17:06:11.277 [main@1f4acd0] >>BDA capture device found:@device:pnp:\\?\pci#ven_1131&dev_7164&subsys_88510070&rev_81#4&211c806e&0&00e6#{fd0a5af4-b41d-11d2-9c95-00c04f7971e0}\{b3e3d165-54eb-4b9e-a805-1756644fa401}; loc:'pci:8-0' id:'PCI\VEN_1131&DEV_7164&SUBSYS_88510070&REV_81' guid:b3e3d165-54eb-4b9e-a805-1756644fa401 desc:@oem14.inf,%halesite.devicedesc8851%;Hauppauge WinTV-HVR-2250 (8851)
Mon 10/3 17:06:11.277 [main@1f4acd0] BDA Capture found: (1) @device:pnp:\\?\pci#ven_1131&dev_7164&subsys_88510070&rev_81#4&211c806e&0&00e6#{fd0a5af4-b41d-11d2-9c95-00c04f7971e0}\{b3e3d165-54eb-4b9e-a805-1756644fa401} on loc pci:8-0.
Mon 10/3 17:06:11.277 [main@1f4acd0] Mutil-tuner(2) BDA capture is found on location:'pci:8-0' id:'PCI\VEN_1131&DEV_7164&SUBSYS_88510070&REV_81' for Hauppauge WinTV-7164 Analog Capture-1. (@device:pnp:\\?\pci#ven_1131&dev_7164&subsys_88510070&rev_81#4&211c806e&0&00e6#{fd0a5af4-b41d-11d2-9c95-00c04f7971e0}\{b3e3d165-54eb-4b9e-a805-1756644fa401},1,desc:@oem14.inf,%halesite.devicedesc8851%;Hauppauge WinTV-HVR-2250 (8851)).
Mon 10/3 17:06:11.277 [main@1f4acd0] BDA CaptureDetail:0x8800; hasBDAInput:0x2; BDA type:0x0
Mon 10/3 17:06:11.277 [main@1f4acd0] fake BDA crossbar cap0 is added for Hauppauge WinTV-7164 Analog Capture..
Mon 10/3 17:06:11.278 [main@1f4acd0] DeviceCap: 0x8810
Mon 10/3 17:06:11.285 [main@1f4acd0] BAD Tuner index :1 dev:\\?\pci#ven_1131&dev_7164&subsys_88510070&rev_81#4&211c806e&0&00e6#{65e8773d-8f56-11d0-a3b9-00a0c9223196}\{bd5b5aea-2141-48a8-8758-f0cf5e0bc801} name:@device:pnp:\\?\pci#ven_1131&dev_7164&subsys_88510070&rev_81#4&211c806e&0&00e6#{65e8773d-8f56-11d0-a3b9-00a0c9223196}\{bd5b5aea-2141-48a8-8758-f0cf5e0bc800} loc:pci:8-0 (1 0) select
Mon 10/3 17:06:11.285 [main@1f4acd0] BAD Tuner index :2 dev:\\?\pci#ven_1131&dev_7164&subsys_88510070&rev_81#4&211c806e&0&00e6#{65e8773d-8f56-11d0-a3b9-00a0c9223196}\{bd5b5aea-2141-48a8-8758-f0cf5e0bc801} name:@device:pnp:\\?\pci#ven_1131&dev_7164&subsys_88510070&rev_81#4&211c806e&0&00e6#{65e8773d-8f56-11d0-a3b9-00a0c9223196}\{bd5b5aea-2141-48a8-8758-f0cf5e0bc801} loc:pci:8-0 (2 0) select
Mon 10/3 17:06:11.285 [main@1f4acd0] Check BDA capture device:Hauppauge WinTV-7164 Analog Capture-1 (\\?\pci#ven_1131&dev_7164&subsys_88510070&rev_81#4&211c806e&0&00e6#{65e8773d-8f56-11d0-a3b9-00a0c9223196}\{bd5b5aea-2141-48a8-8758-f0cf5e0bc801}) on location:'pci:8-0' id:'PCI\VEN_1131&DEV_7164&SUBSYS_88510070&REV_81' [state1, index:1] .
Mon 10/3 17:06:11.286 [main@1f4acd0] >>BDA capture device found:@device:pnp:\\?\pci#ven_1131&dev_7164&subsys_88510070&rev_81#4&211c806e&0&00e6#{fd0a5af4-b41d-11d2-9c95-00c04f7971e0}\{b3e3d165-54eb-4b9e-a805-1756644fa400}; loc:'pci:8-0' id:'PCI\VEN_1131&DEV_7164&SUBSYS_88510070&REV_81' guid:b3e3d165-54eb-4b9e-a805-1756644fa400 desc:@oem14.inf,%halesite.devicedesc8851%;Hauppauge WinTV-HVR-2250 (8851)
Mon 10/3 17:06:11.286 [main@1f4acd0] BDA Capture found: (0) @device:pnp:\\?\pci#ven_1131&dev_7164&subsys_88510070&rev_81#4&211c806e&0&00e6#{fd0a5af4-b41d-11d2-9c95-00c04f7971e0}\{b3e3d165-54eb-4b9e-a805-1756644fa400} on loc pci:8-0.
Mon 10/3 17:06:11.286 [main@1f4acd0] >>BDA capture device found:@device:pnp:\\?\pci#ven_1131&dev_7164&subsys_88510070&rev_81#4&211c806e&0&00e6#{fd0a5af4-b41d-11d2-9c95-00c04f7971e0}\{b3e3d165-54eb-4b9e-a805-1756644fa401}; loc:'pci:8-0' id:'PCI\VEN_1131&DEV_7164&SUBSYS_88510070&REV_81' guid:b3e3d165-54eb-4b9e-a805-1756644fa401 desc:@oem14.inf,%halesite.devicedesc8851%;Hauppauge WinTV-HVR-2250 (8851)
Mon 10/3 17:06:11.286 [main@1f4acd0] BDA Capture found: (1) @device:pnp:\\?\pci#ven_1131&dev_7164&subsys_88510070&rev_81#4&211c806e&0&00e6#{fd0a5af4-b41d-11d2-9c95-00c04f7971e0}\{b3e3d165-54eb-4b9e-a805-1756644fa401} on loc pci:8-0.
Mon 10/3 17:06:11.286 [main@1f4acd0] Mutil-tuner(2) BDA capture is found on location:'pci:8-0' id:'PCI\VEN_1131&DEV_7164&SUBSYS_88510070&REV_81' for Hauppauge WinTV-7164 Analog Capture-1. (@device:pnp:\\?\pci#ven_1131&dev_7164&subsys_88510070&rev_81#4&211c806e&0&00e6#{fd0a5af4-b41d-11d2-9c95-00c04f7971e0}\{b3e3d165-54eb-4b9e-a805-1756644fa401},1,desc:@oem14.inf,%halesite.devicedesc8851%;Hauppauge WinTV-HVR-2250 (8851)).
Mon 10/3 17:06:11.287 [main@1f4acd0] Found the pin2 ;)
Mon 10/3 17:06:11.287 [main@1f4acd0] BDA FindVideoPin:0x4731411c hasBDAInput:2 on Hauppauge WinTV-7164 Analog Capture
Mon 10/3 17:06:11.295 [main@1f4acd0] Encoder passed the check:Hauppauge WinTV-7164 Analog Capture #2
Mon 10/3 17:06:11.299 [main@1f4acd0] Saving properties file to C:\Program Files (x86)\SageTV\SageTV\Sage.properties
Mon 10/3 17:06:11.317 [main@1f4acd0] Done writing out the data to the properties file
Mon 10/3 17:06:11.320 [main@1f4acd0] Processing new system dev:Hauppauge WinTV-7164 Analog Capture
Mon 10/3 17:06:11.323 [main@1f4acd0] Device already has been processed
Mon 10/3 17:06:11.326 [main@1f4acd0] Processing new system dev:Hauppauge WinTV-7164 Analog Capture
Mon 10/3 17:06:11.329 [main@1f4acd0] Device already has been processed
Mon 10/3 17:06:11.332 [main@1f4acd0] devices detected=[Hauppauge WinTV-7164 Analog Capture, Hauppauge WinTV-7164 Analog Capture #2]
Mon 10/3 17:06:11.335 [main@1f4acd0] EncoderMap={DCT-Ceton InfiniTV PCIe (00-80-8b-81) Tuner 2 on 127.0.0.1:9000=DCT-Ceton InfiniTV PCIe (00-80-8b-81) Tuner 2 on 127.0.0.1:9000, DCT-Ceton InfiniTV PCIe (00-80-8b-81) Tuner 5 on 127.0.0.1:9000=DCT-Ceton InfiniTV PCIe (00-80-8b-81) Tuner 5 on 127.0.0.1:9000, DCT-Ceton InfiniTV PCIe (00-80-8b-81) Tuner 4 on 127.0.0.1:9000=DCT-Ceton InfiniTV PCIe (00-80-8b-81) Tuner 4 on 127.0.0.1:9000, DCT-Ceton InfiniTV PCIe (00-80-8b-81) Tuner 1 on 127.0.0.1:9000=DCT-Ceton InfiniTV PCIe (00-80-8b-81) Tuner 1 on 127.0.0.1:9000, DCT-Ceton InfiniTV PCIe (00-80-8b-81) Tuner 3 on 127.0.0.1:9000=DCT-Ceton InfiniTV PCIe (00-80-8b-81) Tuner 3 on 127.0.0.1:9000, Hauppauge WinTV-7164 Analog Capture=Hauppauge WinTV-7164 Analog Capture, DCT-Ceton InfiniTV PCIe (00-80-8b-81) Tuner 6 on 127.0.0.1:9000=DCT-Ceton InfiniTV PCIe (00-80-8b-81) Tuner 6 on 127.0.0.1:9000, Hauppauge WinTV-7164 Analog Capture #2=Hauppauge WinTV-7164 Analog Capture #2}
__________________
Home Network: https://karylstein.com/technology.html
Reply With Quote
  #10  
Old 10-03-2016, 06:24 PM
Fuzzy's Avatar
Fuzzy Fuzzy is offline
SageTVaholic
  
Join Date: Sep 2005
Location: Jurupa Valley, CA
Posts: 9,957
Out of curiosity, do you need the datascanning for any particular reason?
__________________
Buy Fuzzy a beer! (Fuzzy likes beer)

unRAID Server: i7-6700, 32GB RAM, Dual 128GB SSD cache and 13TB pool, with SageTVv9, openDCT, Logitech Media Server and Plex Media Server each in Dockers.
Sources: HRHR Prime with Charter CableCard. HDHR-US for OTA.
Primary Client: HD-300 through XBoxOne in Living Room, Samsung HLT-6189S
Other Clients: Mi Box in Master Bedroom, HD-200 in kids room
Reply With Quote
  #11  
Old 10-04-2016, 04:44 AM
KarylFStein KarylFStein is offline
Sage Fanatic
  
Join Date: Apr 2006
Location: Westland, Michigan, USA
Posts: 999
No clue. It's not something I intentionally turned on. Can I turn it off somewhere?
__________________
Home Network: https://karylstein.com/technology.html
Reply With Quote
  #12  
Old 10-04-2016, 08:20 AM
Fuzzy's Avatar
Fuzzy Fuzzy is offline
SageTVaholic
  
Join Date: Sep 2005
Location: Jurupa Valley, CA
Posts: 9,957
Quote:
Originally Posted by KarylFStein View Post
No clue. It's not something I intentionally turned on. Can I turn it off somewhere?
I don't believe there is a flag to disable the 'feature'. If it is a digital tuner, when sage stops recording from it, it will attempt to tune in a channel to look for EPG data in the stream - it failing to tune is indicative of a problem, but I'm not sure it is a major issue, if you aren't depending on that EPG data (which you probably aren't in the US, as it is typically a horrible source of EPG data).
__________________
Buy Fuzzy a beer! (Fuzzy likes beer)

unRAID Server: i7-6700, 32GB RAM, Dual 128GB SSD cache and 13TB pool, with SageTVv9, openDCT, Logitech Media Server and Plex Media Server each in Dockers.
Sources: HRHR Prime with Charter CableCard. HDHR-US for OTA.
Primary Client: HD-300 through XBoxOne in Living Room, Samsung HLT-6189S
Other Clients: Mi Box in Master Bedroom, HD-200 in kids room
Reply With Quote
  #13  
Old 10-04-2016, 11:56 AM
Narflex's Avatar
Narflex Narflex is offline
Sage
  
Join Date: Feb 2003
Location: Redondo Beach, CA
Posts: 6,349
There's a property called 'disable_data_scanning' that's per EPG source...set that to false and it'll stop trying to do it.

And from the code it appears that it can end up doing this for any ATSC or DVB-T/DVB-C capture device (although you can enable it for QAM and DVB-S by modifying the properties file).
__________________
Jeffrey Kardatzke
Google
Founder of SageTV
Reply With Quote
  #14  
Old 10-04-2016, 03:51 PM
Fuzzy's Avatar
Fuzzy Fuzzy is offline
SageTVaholic
  
Join Date: Sep 2005
Location: Jurupa Valley, CA
Posts: 9,957
Quote:
Originally Posted by Narflex View Post
There's a property called 'disable_data_scanning' that's per EPG source...set that to false and it'll stop trying to do it.

And from the code it appears that it can end up doing this for any ATSC or DVB-T/DVB-C capture device (although you can enable it for QAM and DVB-S by modifying the properties file).
Huh.. I looked all over the capture device code for a property, thinking it MUST be there.. Didn't think to look per-EPG. Any thoughts on why it might be failing to tune for him though?
__________________
Buy Fuzzy a beer! (Fuzzy likes beer)

unRAID Server: i7-6700, 32GB RAM, Dual 128GB SSD cache and 13TB pool, with SageTVv9, openDCT, Logitech Media Server and Plex Media Server each in Dockers.
Sources: HRHR Prime with Charter CableCard. HDHR-US for OTA.
Primary Client: HD-300 through XBoxOne in Living Room, Samsung HLT-6189S
Other Clients: Mi Box in Master Bedroom, HD-200 in kids room
Reply With Quote
  #15  
Old 10-05-2016, 11:46 AM
Narflex's Avatar
Narflex Narflex is offline
Sage
  
Join Date: Feb 2003
Location: Redondo Beach, CA
Posts: 6,349
I'd need to see a complete log file. The snippet above (which is odd because it doesn't have any of the normal prefixes you see in a SageTV log file on each line) points to it trying to configure QAM but the card saying it doesn't support the ksPropertySet for QAM configuration..which is weird. But it's likely a driver/OS issue (pretty much all weird stuff like this with cards that work for most people but not some are related to things like that...because the SageTV code in these areas hasn't changed in over 5 years)
__________________
Jeffrey Kardatzke
Google
Founder of SageTV
Reply With Quote
  #16  
Old 10-05-2016, 03:24 PM
KarylFStein KarylFStein is offline
Sage Fanatic
  
Join Date: Apr 2006
Location: Westland, Michigan, USA
Posts: 999
It looks like Sage Alert hijacks the logs. On the plus side I haven't seen the warning since making the property change. I can see if I can get a proper log tonight.
__________________
Home Network: https://karylstein.com/technology.html
Reply With Quote
  #17  
Old 10-05-2016, 05:27 PM
Fuzzy's Avatar
Fuzzy Fuzzy is offline
SageTVaholic
  
Join Date: Sep 2005
Location: Jurupa Valley, CA
Posts: 9,957
Quote:
Originally Posted by KarylFStein View Post
It looks like Sage Alert hijacks the logs. On the plus side I haven't seen the warning since making the property change. I can see if I can get a proper log tonight.
I really doubt anything 'hijacks' the logs. Check to make sure logging is enabled (Setup -> Detailed Setup -> Advanced -> Debug Logging = On) and the log will be written in SageTV/SageTV/sagetv_0.txt.
__________________
Buy Fuzzy a beer! (Fuzzy likes beer)

unRAID Server: i7-6700, 32GB RAM, Dual 128GB SSD cache and 13TB pool, with SageTVv9, openDCT, Logitech Media Server and Plex Media Server each in Dockers.
Sources: HRHR Prime with Charter CableCard. HDHR-US for OTA.
Primary Client: HD-300 through XBoxOne in Living Room, Samsung HLT-6189S
Other Clients: Mi Box in Master Bedroom, HD-200 in kids room
Reply With Quote
  #18  
Old 10-05-2016, 06:56 PM
KarylFStein KarylFStein is offline
Sage Fanatic
  
Join Date: Apr 2006
Location: Westland, Michigan, USA
Posts: 999
Quote:
Originally Posted by Fuzzy View Post
I really doubt anything 'hijacks' the logs. Check to make sure logging is enabled (Setup -> Detailed Setup -> Advanced -> Debug Logging = On) and the log will be written in SageTV/SageTV/sagetv_0.txt.
Well, maybe it's not SA. Here's how sagetv_0.txt looks as it transitions into what I call a "hijacked" state, (from this point on there are no time stamps in any entries):

Code:
Tue 10/4 14:28:57.767 [SageTV@1327747] Calling start on plugin: Jetty Web Server
Tue 10/4 14:28:57.774 [SageTV@1327747] ::INFO:  Starting Jetty
Tue 10/4 14:28:57.778 [SageTV@1327747] ::INFO:  Jetty Plugin log level: INFO
Tue 10/4 14:28:57.938 [SageTV@1327747] ::INFO:  Redirecting stderr/stdout to C:\Program Files (x86)\SageTV\SageTV\jetty\logs\2016_10_04.stderrout.log
INFO - Deploying SageAlert v2.x into Jetty plugin...
INFO - Deployment successful!
INFO - Registering all connected UI contexts...
INFO - Client id 'a0369f034978' registered!
INFO - Migrating license details to license server...
INFO - Checking license server...
And if you want to find the output of things you'd expect in sagetv_0.txt it's actually in one of the log files under jetty/logs except without timestamps or levels e.g.:

Code:
Done with switch encoding on Hauppauge WinTV-7164 Analog Capture
VF.submitJob(VFJob[InactiveFile r=0.0 t=0 file=null ifn=\\STEINSERVER\Recorded TV\Jeopardy-S33E18-25717462-0.mpg])
CD: SystemStatus: Number running = 1
CD: SystemStatus: Jobs running = 1
CD: SystemStatus:   MediaFileID = 25831104
CD: SystemStatus:   Title : Episode = Jeopardy! : 
CD: SystemStatus: No jobs in queue.
RootFile=\\STEINSERVER\Recorded TV fstype=null fileLength=6908168100 file=\\STEINSERVER\Recorded TV\NHLPreseasonHockey-DetroitRedWingsatPittsburghPenguins-25719665-0.ts
RootFile=\\STEINSERVER\Recorded TV fstype=null fileLength=574610 file=\\STEINSERVER\Recorded TV\Blindspot-S02E04-IfBeth-25728260-0.mpg
Checking video directories for new files
Saving properties file to C:\Program Files (x86)\SageTV\SageTV\Sage.properties
Diskspace checking is running
Verifying existence of all TV media files in database fixDurs=false avoidArchive=true
Done writing out the data to the properties file
Enforcing keep at most limits for the files...
Seeker enforcing KEEP AT MOST of 10 for Agent[Trend=LikeTitleFirstRunsTrend, Title=Jeopardy! id=14496318 watchProb=1.0 numWatchedAirs=-1 numWastedAirs=-1 numManualWaste=-1 createTime=Sun 3/24 13:44:30.267 del=auto keep=10 enabled=true] on MediaFile[id=25698379 A[25580994,25580964,"Jeopardy!",20359@0920.19:30,30,T] mask=TV host=STEINSERVER encodedBy=Hauppauge WinTV-7164 Analog Capture WDIVDT format=MPEG2-PS 0:00:00 3576 kbps [#0 Video[MPEG2-Video 29.97003 fps 1920x1080 16:9 interlaced id=e0]#1 Audio[AC3 48000 Hz 6 channels 384 kbps MAIN idx=1 id=bd-80010000 eng]#2 Audio[AC3 48000 Hz 2 channels 192 kbps idx=2 id=bd-81010000 spa]] \\STEINSERVER\Recorded TV\Jeopardy-S33E07-25580994-0.mpg, Seg0[Tue 9/20 19:30:00.162-Tue 9/20 20:00:00.002]]
Seeker.destroyFile called for: MediaFile[id=25698379 A[25580994,25580964,"Jeopardy!",20359@0920.19:30,30,T] mask=TV host=STEINSERVER encodedBy=Hauppauge WinTV-7164 Analog Capture WDIVDT format=MPEG2-PS 0:00:00 3576 kbps [#0 Video[MPEG2-Video 29.97003 fps 1920x1080 16:9 interlaced id=e0]#1 Audio[AC3 48000 Hz 6 channels 384 kbps MAIN idx=1 id=bd-80010000 eng]#2 Audio[AC3 48000 Hz 2 channels 192 kbps idx=2 id=bd-81010000 spa]] \\STEINSERVER\Recorded TV\Jeopardy-S33E07-25580994-0.mpg, Seg0[Tue 9/20 19:30:00.162-Tue 9/20 20:00:00.002]]
Saving properties file to C:\Program Files (x86)\SageTV\SageTV\Sage.properties
Added file to delete queue: \\STEINSERVER\Recorded TV\Jeopardy-S33E07-25580994-0.mpg
Deleted media segment file \\STEINSERVER\Recorded TV\Jeopardy-S33E07-25580994-0.mpg dtime=3 len=3150189920
Starting async delete for:\\STEINSERVER\Recorded TV\Jeopardy-S33E07-25580994-0.mpg.delete
DONE enforcing keep at most limits for the files.
Seeker clearing unwanted and partial files...
DONE clearing unwanted and partial files.
Done writing out the data to the properties file
__________________
Home Network: https://karylstein.com/technology.html
Reply With Quote
  #19  
Old 10-05-2016, 08:19 PM
Fuzzy's Avatar
Fuzzy Fuzzy is offline
SageTVaholic
  
Join Date: Sep 2005
Location: Jurupa Valley, CA
Posts: 9,957
Okay, that's actually Jetty doing that. You have jetty's debug logging enabled, which is not intended to be left on. In your Sage.properties file, find jetty/jetty.configfiles, and remove jetty-logging.xml from it and restart sage.
__________________
Buy Fuzzy a beer! (Fuzzy likes beer)

unRAID Server: i7-6700, 32GB RAM, Dual 128GB SSD cache and 13TB pool, with SageTVv9, openDCT, Logitech Media Server and Plex Media Server each in Dockers.
Sources: HRHR Prime with Charter CableCard. HDHR-US for OTA.
Primary Client: HD-300 through XBoxOne in Living Room, Samsung HLT-6189S
Other Clients: Mi Box in Master Bedroom, HD-200 in kids room
Reply With Quote
  #20  
Old 10-05-2016, 11:22 PM
KarylFStein KarylFStein is offline
Sage Fanatic
  
Join Date: Apr 2006
Location: Westland, Michigan, USA
Posts: 999
Quote:
Originally Posted by Fuzzy View Post
Okay, that's actually Jetty doing that. You have jetty's debug logging enabled, which is not intended to be left on. In your Sage.properties file, find jetty/jetty.configfiles, and remove jetty-logging.xml from it and restart sage.
Oops, I can't remember why I added that. Things look a lot better now...
__________________
Home Network: https://karylstein.com/technology.html
Reply With Quote
Reply
Page 1 of 2 1 2

« Previous Thread | Next Thread »

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

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 QAM Network Encoder Scan The Truth Hardware Support 3 04-17-2011 03:52 PM
questions about clear qam tv listing data for Hauppauge 2250 tvmaster2 Hardware Support 7 01-23-2011 11:00 AM
Warning - Capture Device Failure while Starting Data Scanning SDeGonge Hardware Support 1 01-09-2011 06:05 AM
Hauppauge 2250 Capture Device Failure with Sage and Comcast corwiniii Hardware Support 2 10-20-2009 09:32 AM
Hauppauge 350 Remote initialization failure with 350(15)/250 MCE (OEM-16) combo cards naln Hardware Support 10 08-11-2004 11:46 PM


All times are GMT -6. The time now is 12:11 PM.

Contact Us - SageTV, LLC - Archive - Privacy Statement - Top

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