[Mobidic]

I'm new to Kodi. My background is software development.

I can find lot of old threads having people wondering where is the PVR / LiveTV icon when they have already enabled a backend plug-in and the TV plug-in. Everything are enabled and still doesn't shows-up.

It seems that the logic is well know to be flaw and not working.

Are we suppose to just 'try' stuff or some useful log files exist?

Any how we can get the design bug to be fixed?

How can I get the LiveTV icon to always show even if no plug-in exist?

I don't need any of the other Icons like Musics, Videos, Pictures, Programs, these icons shows up but I have nothing to shows under them and no need to.

In other words, the only thing I have data for is LiveTV and it doesn't shows up...

I tested with latest 15.x and latest 16 beta, both have the same problem. I tried default skin and skin known to support PVR without any success.

Maybe we should have a custom build that is tested with PVR?

https://app.box.com/s/hnyjewafevczdt9a6amgmafck4t2q5ch

[krustyreturns]

If the backend and pvr plugin are enabled, and live-tv is enabled, you should see the tv icon in Kodi's main manu. If not, try looking at the kodi log to see what is gong on, its here:
%appdata%\kodi\kodi.log

[Mobidic]

I tried with Emby (formerly MediaBrowser) Plugin instead of Kodi to access the same ServerWMC and that was working.

I could see error in the kodi.log file, same error many others mentioned in the past, like ERROR: AddOnLog: PVR WMC Client: Using ServerWMC MAC address from custom addondata

[scarecrow420]

We don't determine how Kodi behaves, we just provide the tv data when it requests it from the plugin

The message you said isn't an error message, just an info message. Please enable debug log in Kodi and post a Kodi startup log (with pvr.wmc enabled) to pastebin

[Mobidic]

This is the debug Kodi log file: http://pastebin.com/M1LKpBXL

The ServerWmc file: https://paste.ee/p/VoM7J

[krustyreturns]

Looks like the problem is serverwmc is throwing an error when your client asks for the channel list. if no channels are returned from the backend i think kodi doesn't display live tv. Not sure what the error is due to. Is live tv working in wmc?

[Mobidic]

Live tv works perfectly in wmc.

We do have this stack in ServerWmc, it looks like a code bug to me. I think my setup is common, I use Homerun. If the stack below is not good enough, do I have a way to generate more useful log files?

2016/01/18 21:10:50.724 GetChannels> error processing channel 7.1 : WHDHHD - 2CC1E2 = { (7.1 : WHDHHD - 69C7) + [ 7.1 : WHDHHD - 2CC040, 7.1 : WHDH-HD - 31EE1E] }, error: System.Collections.Generic.KeyNotFoundException: The given key was not present in the dictionary.
at System.Collections.Generic.Dictionary`2.get_Item(TKey key)
at ServerWMC.Worker.HDHRtuner.GetDlnaAddress(List`1 srcNames, Channel ch, String transcodeProfile)
at ServerWMC.Worker.RecService.GetChannels(FrontEndClient client, Boolean radioOnly)

[krustyreturns]

Turn off using dlna addressing with kodi. Kodi doesn't time shift in this mode anyway so it is not recommended. If it still doesn't work post the swmc log again. We'll figure out what is wrong with dlna later.

So set UseDlnaChannels_Kodi to false in the settings file. save, then restart swmc, then kodi.

[scarecrow420]

so looking at the ServerWMC log it seems there is some funny stuff going on with tuners. WMC reports a twin HDHomeRun (101AD13E-0 and 101AD13E-1) and another one (1019A464-0 and 1019A464-1) but also a "content recorder 3" with "no devices found/configured" and also 2 FM Radio tuners.

Code:

2016/01/18 00:07:54.773 EchoStartupInfo EnumerateRecorders> Tuner Devices and TuningSpaces found:
2016/01/18 00:07:54.773 EchoStartupInfo EnumerateRecorders> ContentRecorder: 0
2016/01/18 00:07:54.773 EchoStartupInfo EnumerateRecorders>  Device #0
2016/01/18 00:07:54.773 EchoStartupInfo EnumerateRecorders>    Name: Silicondust HDHomeRun Tuner 1019A464-0,  Space: ATSC
2016/01/18 00:07:54.773 EchoStartupInfo EnumerateRecorders>    Guid: 167e2467-ad61-4f12-a939-6c2d0c27be76
2016/01/18 00:07:54.773 EchoStartupInfo EnumerateRecorders> ContentRecorder: 1
2016/01/18 00:07:54.773 EchoStartupInfo EnumerateRecorders>  Device #0
2016/01/18 00:07:54.773 EchoStartupInfo EnumerateRecorders>    Name: Silicondust HDHomeRun Tuner 101AD13E-0,  Space: ATSC
2016/01/18 00:07:54.773 EchoStartupInfo EnumerateRecorders>    Guid: e4363751-7891-4879-8b60-dfe00940f35c
2016/01/18 00:07:54.773 EchoStartupInfo EnumerateRecorders> ContentRecorder: 2
2016/01/18 00:07:54.773 EchoStartupInfo EnumerateRecorders>  Device #0
2016/01/18 00:07:54.773 EchoStartupInfo EnumerateRecorders>    Name: Silicondust HDHomeRun Tuner 101AD13E-1,  Space: ATSC
2016/01/18 00:07:54.773 EchoStartupInfo EnumerateRecorders>    Guid: 084b7c03-fcdb-4679-b547-d3e5f3bd2af1
2016/01/18 00:07:54.773 EchoStartupInfo EnumerateRecorders> ContentRecorder: 3
2016/01/18 00:07:54.773 EchoStartupInfo EnumerateRecorders>   >>> devices for this recorder not found/configured <<<
2016/01/18 00:07:54.773 EchoStartupInfo EnumerateRecorders> ContentRecorder: 4
2016/01/18 00:07:54.773 EchoStartupInfo EnumerateRecorders>  Device #0
2016/01/18 00:07:54.773 EchoStartupInfo EnumerateRecorders>    Name: Silicondust HDHomeRun Tuner 1019A464-1,  Space: ATSC
2016/01/18 00:07:54.773 EchoStartupInfo EnumerateRecorders>    Guid: 0a41bbd7-c99e-4c86-80f9-f06cb3638dcc
2016/01/18 00:07:54.773 EchoStartupInfo EnumerateRecorders> ContentRecorder: 5
2016/01/18 00:07:54.773 EchoStartupInfo EnumerateRecorders>  Device #0
2016/01/18 00:07:54.773 EchoStartupInfo EnumerateRecorders>    Name: Hava Remote Video TvTuner,  Space: FM Radio
2016/01/18 00:07:54.773 EchoStartupInfo EnumerateRecorders>    Guid: 01b10e7d-3495-4865-af3d-4a75f9a2ebea
2016/01/18 00:07:54.773 EchoStartupInfo EnumerateRecorders> ContentRecorder: 6
2016/01/18 00:07:54.774 EchoStartupInfo EnumerateRecorders>  Device #0
2016/01/18 00:07:54.774 EchoStartupInfo EnumerateRecorders>    Name: Hava Video TvTuner,  Space: FM Radio
2016/01/18 00:07:54.774 EchoStartupInfo EnumerateRecorders>    Guid: 6c78777a-8958-4072-a9fa-66ea0c3f3f53

Then in the HDHR section we can see

Code:

2016/01/18 00:07:54.774 EchoStartupInfo HDHRtuner::Init> DeviceId: 101AD13E, IP: 192.168.1.125, Dlna: False, Transcode: False, Lineup.xml: True
2016/01/18 00:07:54.774 EchoStartupInfo HDHRtuner::Init> DeviceId: 1041D0C4, IP: 192.168.1.146, Dlna: True, Transcode: False, Lineup.xml: True

2016/01/18 00:07:54.774 EchoStartupInfo HDHRtuner::GetLineUp> found channel lineup file: 'C:\ProgramData\Silicondust\HDHomeRun\Digital Antenna.xml'
2016/01/18 00:07:54.774 EchoStartupInfo HDHRtuner::GetLineUp> exception in loading lineup.xml at address: http://192.168.1.125/lineup.xml

1 supports DLNA and the other doesnt, though that doesnt generally cause an issue since ServerWMC will find a DLNA capable tuner when you've enabled the DLNA mode. Also we have errors loading the lineup.xml from one of them (though I dont think this is the cause of any actual problem, im just observing things in the log file )

Also, frequently throughout the log, we see

Code:

2016/01/18 09:58:04.689 HDHRtuner::GetParameter> returned error: unable to connect to device
2016/01/18 09:58:05.138 HDHRtuner::GetParameter> returned error: unable to connect to device

The actual ServerWMC error is an exception when trying to return a DLNA address for each channel. a quick look at the code makes me think it's due to the Content Recorder 3 having no devices under it (we try to directly index a Dictionary using the device ID, without checking if an entry exists for that device yet, since this isnt a normal situation that is encountered).

As krusty says we obviously need to fix that bug and handle this weird situation gracefully (skip past this invalid recorder and keep looking at the others)... but if you turn off DLNA mode that would prevent it from happening for the time being. If im correct in looking at the code, it looks like you also might be able to work around the problem by specifying "DefaultDLNADevice" in your config file to the IP address of the HDHR tuner (eg 192.168.1.146). This will stop ServerWMC from searching through all the tuner devices (and blowing up when it hits the content recorder 3 with missing device) to find a DLNA capable one to use, and just use the one the user has set in their config file instead.


It looks like you could do with re-doing the tuner setup in WMC to get rid of this invalid tuner as it isn't "normal" to have that. Meanwhile it's been a good catch, and we can make ServerWMC more robust to this odd scenario if it ever crops up on someone else's setup...

[Mobidic]

Thanks both for helping.

Setting UseDlnaChannels_Kodi to false directly in the settings file of ServerWMC made the TV icon shows up. I can see the guide, load live tv, and play old recording. I remember having set this value true using the UI but now it was not allowing me to change it back to false, so I really had to modify the config file.

I do have some 'dead' tuners from http://www.monsoonmultimedia.com/product...specs.html
Even if I uninstalled the software the tuners stays. I seems I would have to delete the WMC database to fix that. I found a tool that read and somehow modify the db, but it doesn't remove tuners -> http://1geek1tool.com/guidetool/

In the long terms anyway, I need the Volcano tuners to be enabled in WMC, even if ServerWMC cannot really do much with them. I use Volcano tuners to 'reuse' the paid cablebox of my family members that are in other country.

I do have more than one live/working tuner box, so putting a fix ip address would not work, because that makes it two ip addresses.

As a feature request, maybe ServerWMC could have a flag in the tuners tab to ignore some of the tuner, or at least ignore them when they are kind of already marked 'disabled'. I mean WMC knows to ignore them, but ServerWMC may still do something with them.

I didn't investigate the DLNA functionalities, but what I'm hoping to see is that I have a cheap Vizio 4k tv that pretty much just have DLNA. If ServerWMC could shows the recorded tv shows, and also handle back button (timeshifting) of live tv, that would be super great!

I do now have some tv and recording to shows, but after like one minute, the mouse freeze, and then die after a while. I will open a different thread for that issue.

Now that I have seen for the first time what the "Tv" features in Kodi does. It seems that the "Tv" feature should still shows up when I have no tuners, because I do have hundreds of recording I still want to play.

[krustyreturns]

@Mobidic

DLNA for kodi used to be a choice in the gui, but it was removed in the last update (consider it depreciated ) although as you can see it is still selectable in the settings). The way dlna channels work in kodi you have to pick one of your dlna devices (or let serverwmc pick for you) because kodi only asks for the url when it starts and it only accepts one dlna device url. The lack of time shifting in dlna mode is also a kodi limitation, we can't do anything about that in serverwmc. The main advantage of dlna mode with swmc is the live-tv streams start faster - but that's about it.

But in non-dlna mode - that you are running now - none of these limitations exist, i.e. time shifting works already.

If your vizio tv does dlna it should discover your dlna devices on its own - no need for serverwmc. Swmc only can work as a backend server to kodi/emby/plex/gameex clients (and in a manual mode for client-less players like vlc).

Swmc does skip the tuners that don't work already, it is just this dlna mode bug you discovered that is messing it up (I agree with scarecrow - thanks for finding that). Also its very important to know that swmc is choosing tuners for live streams in the opposite priority order than wmc does - so be aware of this when you make comparisons (this behavior can be changed in settings but its not recommended).

Whether Live-TV shows up -or not- if channels are not found is kodi behavior, not something we can control in our addon or swmc.

A tuner blacklist is an interesting idea, I will think about that.