Tuner Disabled?

[JeremyFr79 228]

So I recently upgraded mobo/cpu/ram in my HTPC that handles my live TV.  I did a full fresh install of windows and all apps (wiped the drive and all)  I have 2 Ceton tuners totaling 8 tuners available to WMC/ServerWMC.  What I'm noticing though is that periodically when I pull up the tuner status in ServerWMC show's me that one of the tuners is "disabled"  A restart of the PC seems to resolve it though.  I never saw this before the wipe/reload of the system.  Also it seems to be the same tuner of the 8 each time it reports this status.  I've tried "resetting" the tuner through ServerWMC and it still show's disabled.

 

Any Ideas?

 

I can post logs if needed.

[krustyreturns 191]

I have had this happen to me once too, after a restart of the pc it went away and its never happened again (hdhr primes) - so I never figured out what happened.  Next time it happens to you, restart swmc while it is in this state, then query the tuner status either in swmc or emby.  After that post the swmc log.

 

Also you might try start wmc in this state and see if it notices/fixes the disabled tuner.

[JeremyFr79 228]

So I've restarted both with no changes. It only seems to clear up when I restart the whole machine.  Funny thing is if I go into the the Ceton Diagnostics software the tuner is working, I can change channels etc, however it always shows it in a "playing" state even though nothing is currently playing/streaming etc.

[krustyreturns 191]

Send on the log (as described in my last post) when you have time.

[JeremyFr79 228]

Ok here's one of the log's form when it went into "disabled" status, disregard the sharing errors that appear in the log, I've already corrected that.

[krustyreturns 191]

When serverwmc is requesting driver info for that problem tuner, its not getting anything back - which is kind of what I was afraid of.  Why this is happening, or how to fix it on the fly, I don't know.  I do notice however that your wmc configuration seems to have a lot of old tuner configuration data that is no longer valid.  See toward the top of your log, these lines:

 

2015/07/01 11:50:07.538 EnumerateRecorders> Tuner Devices and TuningSpaces found:

2015/07/01 11:50:07.542 EnumerateRecorders> ContentRecorder: 0

2015/07/01 11:50:07.554 EnumerateRecorders>   >>> devices for this recorder not found/configured <<<

2015/07/01 11:50:07.554 EnumerateRecorders> ContentRecorder: 1

2015/07/01 11:50:07.554 EnumerateRecorders>   >>> devices for this recorder not found/configured <<<

2015/07/01 11:50:07.554 EnumerateRecorders> ContentRecorder: 2

2015/07/01 11:50:07.554 EnumerateRecorders>   >>> devices for this recorder not found/configured <<<

2015/07/01 11:50:07.554 EnumerateRecorders> ContentRecorder: 3

2015/07/01 11:50:07.554 EnumerateRecorders>   >>> devices for this recorder not found/configured <<<

2015/07/01 11:50:07.554 EnumerateRecorders> ContentRecorder: 4

2015/07/01 11:50:07.554 EnumerateRecorders>   >>> devices for this recorder not found/configured <<<

2015/07/01 11:50:07.554 EnumerateRecorders> ContentRecorder: 5

2015/07/01 11:50:07.554 EnumerateRecorders>   >>> devices for this recorder not found/configured <<<

2015/07/01 11:50:07.554 EnumerateRecorders> ContentRecorder: 6

2015/07/01 11:50:07.554 EnumerateRecorders>   >>> devices for this recorder not found/configured <<<

2015/07/01 11:50:07.554 EnumerateRecorders> ContentRecorder: 7

2015/07/01 11:50:07.554 EnumerateRecorders>   >>> devices for this recorder not found/configured <<<

 

after that, it starts finding your installed tuners.  This means that the wmc configuration is in a weird state, reporting 8 tuners with no configuration info.  You might consider rerunning the wmc tv signal setup to clean this stuff out.  I don't know if it will solve this weird problem you are having, but it would be what I would try.

[JeremyFr79 228]

 

When serverwmc is requesting driver info for that problem tuner, its not getting anything back - which is kind of what I was afraid of.  Why this is happening, or how to fix it on the fly, I don't know.  I do notice however that your wmc configuration seems to have a lot of old tuner configuration data that is no longer valid.  See toward the top of your log, these lines:

 

2015/07/01 11:50:07.538 EnumerateRecorders> Tuner Devices and TuningSpaces found:

2015/07/01 11:50:07.542 EnumerateRecorders> ContentRecorder: 0

2015/07/01 11:50:07.554 EnumerateRecorders>   >>> devices for this recorder not found/configured <<<

2015/07/01 11:50:07.554 EnumerateRecorders> ContentRecorder: 1

2015/07/01 11:50:07.554 EnumerateRecorders>   >>> devices for this recorder not found/configured <<<

2015/07/01 11:50:07.554 EnumerateRecorders> ContentRecorder: 2

2015/07/01 11:50:07.554 EnumerateRecorders>   >>> devices for this recorder not found/configured <<<

2015/07/01 11:50:07.554 EnumerateRecorders> ContentRecorder: 3

2015/07/01 11:50:07.554 EnumerateRecorders>   >>> devices for this recorder not found/configured <<<

2015/07/01 11:50:07.554 EnumerateRecorders> ContentRecorder: 4

2015/07/01 11:50:07.554 EnumerateRecorders>   >>> devices for this recorder not found/configured <<<

2015/07/01 11:50:07.554 EnumerateRecorders> ContentRecorder: 5

2015/07/01 11:50:07.554 EnumerateRecorders>   >>> devices for this recorder not found/configured <<<

2015/07/01 11:50:07.554 EnumerateRecorders> ContentRecorder: 6

2015/07/01 11:50:07.554 EnumerateRecorders>   >>> devices for this recorder not found/configured <<<

2015/07/01 11:50:07.554 EnumerateRecorders> ContentRecorder: 7

2015/07/01 11:50:07.554 EnumerateRecorders>   >>> devices for this recorder not found/configured <<<

 

after that, it starts finding your installed tuners.  This means that the wmc configuration is in a weird state, reporting 8 tuners with no configuration info.  You might consider rerunning the wmc tv signal setup to clean this stuff out.  I don't know if it will solve this weird problem you are having, but it would be what I would try.

 

I think I'm going to end up wiping the machine and starting over from scratch again, I've been having some other issues as well with it.  Thanks for the help as always!