Puzzled: Sage not using 3rd tuner

[wvpolekat]

I recently replaced one of my PVR-150's with a PVR-500 to get a 3rd tuner.

My current setup is this:

STB--->PVR-150 Composite Digital Channel Lineup
STB--->PVR-500-1 Composite Digital Channel Lineup
Straight Cable--->PVR-500 analog tuner Regular Basic Cable Lineup

In tuner and channel setup all 3 tuner work as expected, are able to tune all channels available to them.

It does not appear that SageTV is using the 3rd tuner for intelligent recording or conflict resolution. Meaning, if I schedule 3 recordings at one time within the basic cable channel range, it does not use the 3rd tuner. The conflict resolution acts like it isnt there. I feel like there is something I am missing here.

What I have done:
Restarted sage
Removed all sources, restarted sage, readded sources, restarted sage
Changed channel lineup for analog tuner to nearby city with same provider and lineup.
Everyone looks happy in device manager.

I do have debug logging enabled, but I doubt it will fit in this textbox. Below is a snippit that seems relevant:

Wed 11/14 18:24:35.358 systemCapDevices=[Hauppauge WinTV PVR PCI II Capture, Hauppauge WinTV PVR PCI II Capture, Hauppauge WinTV PVR PCI II Capture, BDA Slip De-Framer]
Wed 11/14 18:24:35.359 Checking encoder key:1642691032
Wed 11/14 18:24:35.364 Created DShowCapDev object for:Hauppauge WinTV PVR PCI II Capture
Wed 11/14 18:24:35.365 Checking encoder key:551195575
Wed 11/14 18:24:35.367 Created DShowCapDev object for:Hauppauge WinTV PVR PCI II Capture #2
Wed 11/14 18:24:35.368 EncoderMap1={Hauppauge WinTV PVR PCI II Capture=Hauppauge WinTV PVR PCI II Capture, Hauppauge WinTV PVR PCI II Capture #2=Hauppauge WinTV PVR PCI II Capture #2}
Wed 11/14 18:24:35.380 Capture device Hauppauge WinTV PVR PCI II Capture (0) exists
Wed 11/14 18:24:35.391 BAD Tuner index :1 dev:\\?\pci#ven_4444&dev_0016&subsys_80030070&rev_01#4&cf81c54&0&08f0#{65e8773d-8f56-11d0-a3b9-00a0c9223196}\{9b365890-165f-11d0-a195-0020afd156e4} name:@devicenp:\\?\pci#ven_4444&dev_0016&subsys_80030070&rev_01#4&cf81c54&0&08f0#{65e8773d-8f56-11d0-a3b9-00a0c9223196}\{9b365890-165f-11d0-a195-0020afd156e4} locci:3-1 (1 0) select
Wed 11/14 18:24:35.391 Check BDA capture device:Hauppauge WinTV PVR PCI II Capture-0 (\\?\pci#ven_4444&dev_0016&subsys_80030070&rev_01#4&cf81c54&0&08f0#{65e8773d-8f56-11d0-a3b9-00a0c9223196}\{9b365890-165f-11d0-a195-0020afd156e4}) on locationci:3-1 [state1, index:0] .
Wed 11/14 18:24:35.393 BDA capture device found:@devicenp:\\?\root#system#0000#{fd0a5af4-b41d-11d2-9c95-00c04f7971e0}\{03884cb6-e89a-4deb-b69e-8dc621686e6a}&global; loc:rootStandard system devices)
Wed 11/14 18:24:35.393 BDA capture is not found on locationci:3-1 for Hauppauge WinTV PVR PCI II Capture.
Wed 11/14 18:24:35.393 debug BDA CaptureDetail:0x0 hasBDAInput:0x0
Wed 11/14 18:24:35.402 DeviceCap: 0x810
Wed 11/14 18:24:35.427 BAD Tuner index :1 dev:\\?\pci#ven_4444&dev_0016&subsys_80030070&rev_01#4&cf81c54&0&08f0#{65e8773d-8f56-11d0-a3b9-00a0c9223196}\{9b365890-165f-11d0-a195-0020afd156e4} name:@devicenp:\\?\pci#ven_4444&dev_0016&subsys_80030070&rev_01#4&cf81c54&0&08f0#{65e8773d-8f56-11d0-a3b9-00a0c9223196}\{9b365890-165f-11d0-a195-0020afd156e4} locci:3-1 (1 0) select
Wed 11/14 18:24:35.427 Check BDA capture device:Hauppauge WinTV PVR PCI II Capture-0 (\\?\pci#ven_4444&dev_0016&subsys_80030070&rev_01#4&cf81c54&0&08f0#{65e8773d-8f56-11d0-a3b9-00a0c9223196}\{9b365890-165f-11d0-a195-0020afd156e4}) on locationci:3-1 [state1, index:0] .
Wed 11/14 18:24:35.429 BDA capture device found:@devicenp:\\?\root#system#0000#{fd0a5af4-b41d-11d2-9c95-00c04f7971e0}\{03884cb6-e89a-4deb-b69e-8dc621686e6a}&global; loc:rootStandard system devices)
Wed 11/14 18:24:35.429 BDA capture is not found on locationci:3-1 for Hauppauge WinTV PVR PCI II Capture.
Wed 11/14 18:24:35.429 Found the pin2
Wed 11/14 18:24:35.430 debug BDA FindVideoPin:0x838df4 hasBDAInput:0
Wed 11/14 18:24:35.440 Encoder passed the check:Hauppauge WinTV PVR PCI II Capture
Wed 11/14 18:24:35.441 Saving properties file to C:\Program Files\SageTV\SageTV\Sage.properties
Wed 11/14 18:24:35.508 Capture device Hauppauge WinTV PVR PCI II Capture (1) exists
Wed 11/14 18:24:35.519 BAD Tuner index :1 dev:\\?\pci#ven_4444&dev_0016&subsys_e8070070&rev_01#5&341ca7b&0&4010f0#{65e8773d-8f56-11d0-a3b9-00a0c9223196}\{9b365890-165f-11d0-a195-0020afd156e4} name:@devicenp:\\?\pci#ven_4444&dev_0016&subsys_e8070070&rev_01#5&341ca7b&0&4010f0#{65e8773d-8f56-11d0-a3b9-00a0c9223196}\{9b365890-165f-11d0-a195-0020afd156e4} locci:4-8 (1 0) select
Wed 11/14 18:24:35.520 Check BDA capture device:Hauppauge WinTV PVR PCI II Capture-1 (\\?\pci#ven_4444&dev_0016&subsys_e8070070&rev_01#5&341ca7b&0&4010f0#{65e8773d-8f56-11d0-a3b9-00a0c9223196}\{9b365890-165f-11d0-a195-0020afd156e4}) on locationci:4-8 [state1, index:0] .
Wed 11/14 18:24:35.521 BDA capture device found:@devicenp:\\?\root#system#0000#{fd0a5af4-b41d-11d2-9c95-00c04f7971e0}\{03884cb6-e89a-4deb-b69e-8dc621686e6a}&global; loc:rootStandard system devices)
Wed 11/14 18:24:35.521 BDA capture is not found on locationci:4-8 for Hauppauge WinTV PVR PCI II Capture.
Wed 11/14 18:24:35.522 debug BDA CaptureDetail:0x0 hasBDAInput:0x0
Wed 11/14 18:24:35.531 DeviceCap: 0x810
Wed 11/14 18:24:35.557 BAD Tuner index :1 dev:\\?\pci#ven_4444&dev_0016&subsys_e8070070&rev_01#5&341ca7b&0&4010f0#{65e8773d-8f56-11d0-a3b9-00a0c9223196}\{9b365890-165f-11d0-a195-0020afd156e4} name:@devicenp:\\?\pci#ven_4444&dev_0016&subsys_e8070070&rev_01#5&341ca7b&0&4010f0#{65e8773d-8f56-11d0-a3b9-00a0c9223196}\{9b365890-165f-11d0-a195-0020afd156e4} locci:4-8 (1 0) select
Wed 11/14 18:24:35.557 Check BDA capture device:Hauppauge WinTV PVR PCI II Capture-1 (\\?\pci#ven_4444&dev_0016&subsys_e8070070&rev_01#5&341ca7b&0&4010f0#{65e8773d-8f56-11d0-a3b9-00a0c9223196}\{9b365890-165f-11d0-a195-0020afd156e4}) on locationci:4-8 [state1, index:0] .
Wed 11/14 18:24:35.558 BDA capture device found:@devicenp:\\?\root#system#0000#{fd0a5af4-b41d-11d2-9c95-00c04f7971e0}\{03884cb6-e89a-4deb-b69e-8dc621686e6a}&global; loc:rootStandard system devices)
Wed 11/14 18:24:35.558 BDA capture is not found on locationci:4-8 for Hauppauge WinTV PVR PCI II Capture.
Wed 11/14 18:24:35.559 Found the pin2
Wed 11/14 18:24:35.559 debug BDA FindVideoPin:0x83ac2c hasBDAInput:0
Wed 11/14 18:24:35.568 Encoder passed the check:Hauppauge WinTV PVR PCI II Capture #2
Wed 11/14 18:24:35.568 Saving properties file to C:\Program Files\SageTV\SageTV\Sage.properties
Wed 11/14 18:24:35.622 Processing new system dev:Hauppauge WinTV PVR PCI II Capture
Wed 11/14 18:24:35.622 Device already has been processed
Wed 11/14 18:24:35.622 Processing new system dev:Hauppauge WinTV PVR PCI II Capture
Wed 11/14 18:24:35.623 Device already has been processed
Wed 11/14 18:24:35.623 Processing new system dev:Hauppauge WinTV PVR PCI II Capture
Wed 11/14 18:24:35.623 Processing new system dev:BDA Slip De-Framer
Wed 11/14 18:24:35.624 devices detected=[Hauppauge WinTV PVR PCI II Capture, Hauppauge WinTV PVR PCI II Capture #2]
Wed 11/14 18:24:35.624 EncoderMap={Hauppauge WinTV PVR PCI II Capture=Hauppauge WinTV PVR PCI II Capture, Hauppauge WinTV PVR PCI II Capture #2=Hauppauge WinTV PVR PCI II Capture #2}
Wed 11/14 18:24:35.661 Checking video directories for new files
Wed 11/14 18:24:35.724 DShowFilters=[.RAM file Parser, 9x8Resize, AC3 Parser Filter, AC3Filter, ACELP.net Sipro Lab Audio Decoder, ACM Wrapper, Allocator Fix, ASF ACM Handler, ASF DIB Handler, ASF DJPEG Handler, ASF embedded stuff Handler, ASF ICM Handler, ASF JPEG Handler, ASF URL Handler, ASX file Parser, ASX v.2 file Parser, AVI Decompressor, AVI Draw, AVI Mux, AVI Splitter, AVI/WAV File Source, Bitmap Generate, Color Space Converter, Deinterlace Filter, DV Muxer, DV Splitter, DV Video Decoder, DVD Navigator, File Source (Async.), File Source (Netshow URL), File Source (URL), File stream renderer, File writer, Frame Eater, Full Screen Renderer, G.711 Codec, Hauppauge WinTV Color Format Converter 2, Indeo® audio softwar, Indeo® video 4.4 Compression Filte, Indeo® video 4.4 Decompression Filte, Indeo® video 5.10 Compression Filte, Indeo® video 5.10 Decompression Filte, Infinite Pin Tee Filter, Internal Script Command Renderer, IVF source filter, Line 21 Decoder, Line 21 Decoder 2, Lyric Parser, Microsoft MPEG-4 Video Decompressor, Microsoft Screen Video Decompressor, MIDI Parser, MJPEG Decompressor, MPEG Audio Decoder, MPEG Layer-3 Decoder, MPEG Video Decoder, MPEG-2 Demultiplexer, MPEG-2 Sections and Tables, MPEG-2 Splitter, MPEG-2 Video Stream Analyzer, MPEG-I Stream Splitter, MPEG2Dump, Mpeg4 Decoder DMO, Mpeg43 Decoder DMO, Mpeg4s Decoder DMO, Multi-file Parser, NSC file Parser, Null Renderer, Overlay Mixer, Overlay Mixer2, QT Decompressor, QuickTime Movie Parser, Record Queue, SageTV MPEG Audio Decoder, SageTV MPEG Audio Encoder, SageTV MPEG Encoder, SageTV MPEG Layer II Audio Encoder, SageTV MPEG Multiplexer, SageTV MPEG Splitter, SageTV MPEG Video Decoder, SageTV MPEG Video Encoder, SageTV MpegDeMux, SageTV MpegMux, SageTV Music Visualization, SageTV TS Splitter 1.0, SAMI (CC) Parser, SampleGrabber, Shared File Source (Async.), ShotBoundaryDet, Smart Tee, StreamBufferSink, StreamBufferSource, Stretch Video, Uncompressed Domain Shot Detection Filter, VBI Surface Allocator, VGA 16 Color Ditherer, Video Mixing Renderer 9, Video Port Manager, Video Renderer, Video Renderer, Wave Parser, WIA Stream Snapshot Filter, Windows Media Audio Decoder, Windows Media Multiplexer, Windows Media Pad VU Data Grabber, Windows Media source filter, Windows Media Update Filter, Windows Media Video Decoder, Windows Media Video Decoder, WM ASF Reader, WM ASF Writer, WMAudio Decoder DMO, WMSpeech Decoder DMO, WMT AudioAnalyzer, WMT Black Frame Generator, WMT DirectX Transform Wrapper, WMT DV Extract, WMT Format Conversion, WMT Import Filter, WMT Interlacer, WMT Log Filter, WMT MuxDeMux Filter, WMT Sample Information Filter, WMT Screen Capture filter, WMT Switch Filter, WMT VIH2 Fix, WMT Virtual Renderer, WMT Virtual Source, WMT Volume, WMV Screen decoder DMO, WMVideo Decoder DMO, WST Decoder, XML Playlist]
Wed 11/14 18:24:35.838 CARNY Processing 3747 Agents & 9008 Airs

[wvpolekat]

New development.

Last night it showed up in the recent recordings list recording something on discovery that was 3200 days long. So, my current suspicion is that it thinks the tuner is busy.

When I looked at sources, it was showing it and one other as being used for live TV.

Not sure if this is a red herring or not.

[Djc208]

Last night it showed up in the recent recordings list recording something on discovery that was 3200 days long. So, my current suspicion is that it thinks the tuner is busy.

I like discovery as much as the next person but that's a lot of Mythbusters