Live TV not showing
#31
(2015-05-12, 22:21)nickr Wrote: Can you watch recordings?

No. Not in Kodi. I can watch recorded videos from the other PC running Myth frontend.

(2015-05-12, 22:47)nickr Wrote: Also go through the docs http://janbar.github.io/pvr.mythtv/manual/index.html

The only section of that doc that's complete is the basic network setup: IP address, no IPv6, and setting PIN to 0000. And I think I've done that part correctly.
Reply
#32
I'll try and remember to take another look at your log tonight. Not very productive to do it at work LOL.
If I have helped you or increased your knowledge, click the 'thumbs up' button to give thanks :) (People with less than 20 posts won't see the "thumbs up" button.)
Reply
#33
EDIT: 1st question, what version of the PVR addon do you have. Janbar has made many changes and it is best to get his latest version. http://janbar.github.io/pvr.mythtv/download/index.html

As you are on ubuntu go for the ppa.

--

I see errors with connecting to the hostname myth-test.control, which seems odd (as in the .control part of the hostname seems odd). eg

Code:
0:18:11 T:2625633088   DEBUG: AddOnLog: MythTV PVR Client: (CPPMyth)SendRequest: GET /Content/GetRecordingArtwork?Type=%63%6F%76%65%72%61%72%74&Inetref=%74%74%76%64%62%2E%70%79%5F%37%38%38%33%37&Season=%39 HTTP/1.1
                                            Host: myth-test.control:6544
                                            Connection: keep-alive
                                            Accept-Charset: utf-8
10:18:11 T:2625633088   DEBUG: AddOnLog: MythTV PVR Client: (CPPMyth)GetResponse: HTTP/1.1 404 Not Found

What exactly do you have the backend host set to in your pvr.mythtv settings. Try setting it to the backend's IP address and see what happens.
If I have helped you or increased your knowledge, click the 'thumbs up' button to give thanks :) (People with less than 20 posts won't see the "thumbs up" button.)
Reply
#34
(2015-05-12, 17:30)living_room_rob Wrote: I'm seeing the same symptoms as others here: No "Live TV" item in the menu. Googling the problem brought me to this thread.

I've got Kodi 14.2 (mythbuntu/kodibuntu) on my "media center" PC. I have a MythTV backend running ver 0.27 on a separate mythbuntu machine. The PVR plugin is installed and enabled.

Unless it was a super-realistic dream, Live TV had been working a few weeks ago. Now, it's gone. Perhaps something was updated that introduced an incompatibility, but I'm not sure how to tell.

I can see Live TV with myth frontend running on the myth backend box. I can also see live tv from a third computer running myth frontend. It appears to be operating normally. I have the Kodi PVR configured the same as the myth frontend on the other PC.

In the System Info I can see the PVR Service, and it lists the correct URL, and shows correct available disk space, etc. on the backend. I see that there are the correct number of recordings and upcoming recordings. It also shows 0 channels, which looks suspicious.

I've uploaded the log here: http://goo.gl/uVaSln

What are my next steps?

Thanks

From your log:

Code:
10:18:10 T:2704386880   ERROR: AddOnLog: MythTV PVR Client: (CPPMyth)Document: failed to parse: 1: illegal unprintable codepoint in string

This is probably the reason you are not seeing any channels. pvr.mythtv cannot load the channel information from mythtv backend.


Are you running the latest 0.27 fixes on your mythtv backend ?

From a terminal connected to the mythtv-backend please post the output from mythbackend --version

Also what is the version of the pvr.mythtv addon ?

Mike
Reply
#35
(2015-05-13, 08:46)nickr Wrote: EDIT: 1st question, what version of the PVR addon do you have. Janbar has made many changes and it is best to get his latest version. http://janbar.github.io/pvr.mythtv/download/index.html

As you are on ubuntu go for the ppa.

My PVR addon is 1.12.6. (Looks like the one in your link is 1.12.18.) Since it said it worked with myth backend through 0.28 and mine is 0.27, I didn't think to look for a newer version anywhere.

Quote:I see errors with connecting to the hostname myth-test.control, which seems odd (as in the .control part of the hostname seems odd). eg

Code:
0:18:11 T:2625633088   DEBUG: AddOnLog: MythTV PVR Client: (CPPMyth)SendRequest: GET /Content/GetRecordingArtwork?Type=%63%6F%76%65%72%61%72%74&Inetref=%74%74%76%64%62%2E%70%79%5F%37%38%38%33%37&Season=%39 HTTP/1.1
                                            Host: myth-test.control:6544
                                            Connection: keep-alive
                                            Accept-Charset: utf-8
10:18:11 T:2625633088   DEBUG: AddOnLog: MythTV PVR Client: (CPPMyth)GetResponse: HTTP/1.1 404 Not Found

What exactly do you have the backend host set to in your pvr.mythtv settings. Try setting it to the backend's IP address and see what happens.

The address of the backend host in the PVR config is "myth-test.control". ".control" is the domain of my local network. (I'm old school, and all the devices get themed names -- in my case characters from the Get Smart TV series.) All the devices I know I'll need to access remotely get a static IP and URL from the router. I use the hostname "myth-test.control" in the settings for the myth frontend I've been using as a sanity check. Does Kodi not like hostnames? I can try using the numeric IP instead. I'll update the results of this.


(2015-05-13, 13:06)MikeB2013 Wrote: From your log:

Code:
10:18:10 T:2704386880   ERROR: AddOnLog: MythTV PVR Client: (CPPMyth)Document: failed to parse: 1: illegal unprintable codepoint in string

This is probably the reason you are not seeing any channels. pvr.mythtv cannot load the channel information from mythtv backend.


Are you running the latest 0.27 fixes on your mythtv backend ?

From a terminal connected to the mythtv-backend please post the output from mythbackend --version

Also what is the version of the pvr.mythtv addon ?

Mike

PVR addon is 1.12.6

output of mythbackend --version:

Code:
Please attach all output as a file in bug reports.
MythTV Version : v0.27.4-58-g45d2d51
MythTV Branch : fixes/0.27
Network Protocol : 77
Library API : 0.27.20141016-1
QT Version : 4.8.6
Options compiled in:
linux profile use_hidesyms using_alsa using_oss using_pulse using_pulseoutput using_backend using_bindings_perl using_bindings_python using_bindings_php using_crystalhd using_dvb using_firewire using_frontend using_hdhomerun using_ceton using_hdpvr using_ivtv using_joystick_menu using_libcrypto using_libdns_sd using_libfftw3 using_libxml2 using_lirc using_mheg using_opengl using_opengl_video using_qtwebkit using_qtscript using_qtdbus using_sdl using_taglib using_v4l2 using_x11 using_xrandr using_xv using_profiletype using_bindings_perl using_bindings_python using_bindings_php using_mythtranscode using_opengl using_vaapi using_vdpau using_ffmpeg_threads using_mheg using_libass using_libxml2

I'll start trying these things one at a time and update with results.

One more thing I've seen: every so often, I see a "MAC Discovery" message pop up in Kodi. Looks like an error, since it's red with an "X" in it, but I can't tell for sure. The message appears and disappears far too quickly to attempt to write down the MAC address it gives. I have no idea if this is related to my problem.

ED: I switched from hostname to IP address in the PVR addon configuration. That didn't change anything. So I added the PPA with the newer myth plugin. After figuring out I needed to remove the existing kodi-pvr-mythtv before installing kodi-pvr-mythtv-helix I got it installed and now the mythtv pvr addon version shows 1.12.18. Still no Live TV, and still the number of channels in the System Info PVR service shows 0. But still I see that I have 2 recordings and 4 scheduled and how much disk space I have on the backend. I can't watch the recordings, but it is talking to the backend server.

EDIT2: Since I've changed stuff, I guess I should post another log to see if anything jumps out. http://goo.gl/XkgU9U

Also, I followed the 404 clue in the log, making sure that the Kodi box (Max) could see the server. To be thorough, I pulled it up both at 192.168.2.117:6544 and myth-test.control:6544 with chromium on Max, and it works both ways. (I did not know that it was human readable, but now I do.) So still searching and head-scratching.
Reply
#36
kodi doesn't mind hostnames, I was just wondering where it go that .control domain, which seemed odd to me. False alert, sorry about that chief.
If I have helped you or increased your knowledge, click the 'thumbs up' button to give thanks :) (People with less than 20 posts won't see the "thumbs up" button.)
Reply
#37
@living_room_rob

Your latest log still shows the error when getting channel data from mythtv-backend.
The data in the log shows that ChannelName is "" (i.e. missing) for ChanNum 18-7 and 18-8
This may or may not be significant, I am out of my depth with SchedulesDirect.

Can you try deselecting visible checkbox for these two channels using Mythweb on the mythtv-backend and then running kodi, to see if the remaining channels now appear in kodi.

Another thing you could try is, using a browser pastebin the result of the following command, changing the ip address to that of your mythtv-backend server.

http://192.168.0.22:6544/Channel/GetChan...&Count=100

This will display all the channel data that pvr.mythtv will get (the kodi log file gets truncated due the quantity of data)

Mike
Reply
#38
(2015-05-14, 15:54)MikeB2013 Wrote: @living_room_rob

Your latest log still shows the error when getting channel data from mythtv-backend.
The data in the log shows that ChannelName is "" (i.e. missing) for ChanNum 18-7 and 18-8
This may or may not be significant, I am out of my depth with SchedulesDirect.

Can you try deselecting visible checkbox for these two channels using Mythweb on the mythtv-backend and then running kodi, to see if the remaining channels now appear in kodi.

They're already set not visible. Sad 18 is the local public broadcasting system affiliate, and channels 7 and 8 are listed as "control" when I check the HDHomeRun GUI. I have no idea what they are, nor am I sure why there's a 7 and 8, but no 4, 5, and 6. 1-3 are really TV streams, BTW.

Quote:Another thing you could try is, using a browser pastebin the result of the following command, changing the ip address to that of your mythtv-backend server.

http://192.168.0.22:6544/Channel/GetChan...&Count=100

This will display all the channel data that pvr.mythtv will get (the kodi log file gets truncated due the quantity of data)

Mike

OK, I pasted the output: http://goo.gl/a6qzRY
And for fun the page source: http://goo.gl/0MPaxL

Can definitely see empty channel names which is not unexpected, but also that the page isn't rendering properly in the browser due to that problem. Whether this error breaks Kodi Myth PVR plugin or not I'm not yet sure. Myth frontend seems to somehow deal with it -- maybe it just ignores errors. If this is really breaking things, then this might be a Myth backend setup bug that channel names are allowed to be blank if blank is really invalid, not just . . . blank.

Since these channels are still in the list despite being not visible, maybe I need to make up names . . . will update.
Reply
#39
Looked at output of ChannelInfoList command.

There is definitely bad data in mythtv-backend database (pvr.mythtv assumes good data).
ChannelNames for channum 38_1 and 41_1 contain some zip code data after the Channel Names, plus I suspect non-printing characters :

Code:
<ChannelInfo><ChanId>1381</ChanId><ChanNum>38_1</ChanNum><CallSign>KMCI-TV</CallSign><IconURL>kmci_kansas_city.jpg</IconURL><ChannelName>KMCI-TV
4720 Oak Street
Kansas City, MO 64112</ChannelName><MplexId>7</MplexId><TransportId>1187</TransportId><ServiceId>3</ServiceId><NetworkId>0</NetworkId><ATSCMajorChan>38</ATSCMajorChan><ATSCMinorChan>1</ATSCMinorChan><Format>ATSC</Format><Modulation>8vsb</Modulation><Frequency>635000000</Frequency><FrequencyId>41</FrequencyId><FrequencyTable>default</FrequencyTable><FineTune>0</FineTune><SIStandard>atsc</SIStandard><ChanFilters></ChanFilters><SourceId>1</SourceId><InputId>0</InputId><CommFree>0</CommFree><UseEIT>true</UseEIT><Visible>true</Visible><XMLTVID>34773</XMLTVID><DefaultAuth></DefaultAuth><Programs/></ChannelInfo><ChannelInfo><ChanId>1411</ChanId><ChanNum>41_1</ChanNum><CallSign>KSHB-TV</CallSign><IconURL>kshb41_kansas.jpg</IconURL><ChannelName>KSHB-TV
4720 Oak Street
Kansas City, MO 64112</ChannelName><MplexId>8</MplexId><TransportId>1647</TransportId><ServiceId>3</ServiceId><NetworkId>0</NetworkId><ATSCMajorChan>41</ATSCMajorChan><ATSCMinorChan>1</ATSCMinorChan><Format>ATSC</Format><Modulation>8vsb</Modulation><Frequency>641000000</Frequency><FrequencyId>42</FrequencyId><FrequencyTable>default</FrequencyTable><FineTune>0</FineTune><SIStandard>atsc</SIStandard><ChanFilters></ChanFilters><SourceId>1</SourceId><InputId>0</InputId><CommFree>0</CommFree><UseEIT>true</UseEIT><Visible>true</Visible><XMLTVID>34885</XMLTVID><DefaultAuth></DefaultAuth><Programs/></ChannelInfo>

plus http://xbmclogs.com/pbbgdikic indicates error on line 5 at column 13751: Char 0x0 out of allowed range


As a quick test you could use mythweb to delete these channels and run kodi again.



Mike
Reply
#40
(2015-05-11, 04:43)nickr Wrote: Assuming you have nothing on the hard drive you need, simply format it as one partition as xfs or ext4.

Mount it at, say, /mnt/media and make a directory inside it called recordings. Make it's ownership right with
Code:
chown -R mythtv:mythtv /mnt/media/recordings


Then set it to mount on each boot in /etc/fstab

Then in mythtv-setup set /mnt/media/recordings as your default storage group.

nickr

Been too embarrassed with my progress this week trying to learn how to execute your instructions. I am now here:

1. The storage drive ended up in media/kn/086d7ccxxxxxxxxxxxxxx. I tried remounting to /mnt/media but that was a disaster so a few minutes ago I figured not worth wasting more days and leave it where it is.

2. I assumed “recordings” go on the storage drive rather than the same directory as the drive. media/kn/086d7ccxxxxxxxxxxxxxx/recordings.

3. Appending fstab didn't work, however I had not done ownership right yet figuring fstab more important a step.

UUII=1111axxxxxxxxxxxxxx / ext4 errors=remount-ro 0 1
UUII-6865bxxxxxxxxxxxxxxx none swap sw 0 0
# I appended
UUII=086d7cxxxxxxxxxxxxxx /media/kn 0 0

Computer didn't like that addition. I humbly ask any direction you might have time to share.
Reply
#41
(2015-05-14, 18:50)MikeB2013 Wrote: Looked at output of ChannelInfoList command.

There is definitely bad data in mythtv-backend database (pvr.mythtv assumes good data).
ChannelNames for channum 38_1 and 41_1 contain some zip code data after the Channel Names, plus I suspect non-printing characters :


plus http://xbmclogs.com/pbbgdikic indicates error on line 5 at column 13751: Char 0x0 out of allowed range


As a quick test you could use mythweb to delete these channels and run kodi again.


Mike

Despite being overly (and needlessly and annoyingly) verbose, 38_1 and 41_1 appear ok on the Myth frontend. But -- and I didn't notice this before -- trying to tune channel 45 caused the livetv player in myth to crash and dump me back at the mythtv frontend home. I'd never even tried that before since it's Home Shopping Channel 2.

But back to Kodi. First thing I did was edit the channel name from "HSN2(garbagegarbagegarbage)" to just "HSN2" and then running mythfilldatabase and resetting everything a bunch of times got TV to appear in Kodi. I can even sort of watch HSN2 on Kodi but not Myth. That's a mystery that will never be solved, since HSN2 is taking a trip to invisibility land real soon now.

Also, the weirdness in 18_7 and 18_8 having blank names didn't seem to cause any noticeable problems. They're hidden and don't show up and any parsing errors they cause don't affect overall operation.
Reply
#42
(2015-05-14, 21:31)deskbound Wrote:
(2015-05-11, 04:43)nickr Wrote: Assuming you have nothing on the hard drive you need, simply format it as one partition as xfs or ext4.

Mount it at, say, /mnt/media and make a directory inside it called recordings. Make it's ownership right with
Code:
chown -R mythtv:mythtv /mnt/media/recordings


Then set it to mount on each boot in /etc/fstab

Then in mythtv-setup set /mnt/media/recordings as your default storage group.

nickr

Been too embarrassed with my progress this week trying to learn how to execute your instructions. I am now here:

1. The storage drive ended up in media/kn/086d7ccxxxxxxxxxxxxxx. I tried remounting to /mnt/media but that was a disaster so a few minutes ago I figured not worth wasting more days and leave it where it is.

2. I assumed “recordings” go on the storage drive rather than the same directory as the drive. media/kn/086d7ccxxxxxxxxxxxxxx/recordings.

3. Appending fstab didn't work, however I had not done ownership right yet figuring fstab more important a step.

UUII=1111axxxxxxxxxxxxxx / ext4 errors=remount-ro 0 1
UUII-6865bxxxxxxxxxxxxxxx none swap sw 0 0
# I appended
UUII=086d7cxxxxxxxxxxxxxx /media/kn 0 0

Computer didn't like that addition. I humbly ask any direction you might have time to share.

So this is am external drive is it?

UUII is wrong, I suspect you are not copying and pasting.

It is UUID. To discover the correct UUID use
Code:
sudo blkid

Then do some googling to discover what to put in fstab. Your line is so wrong I don't know where to start. You don't even follow the pattern of the earlier entries.
If I have helped you or increased your knowledge, click the 'thumbs up' button to give thanks :) (People with less than 20 posts won't see the "thumbs up" button.)
Reply
#43
correction on the fstab
UUID=xxxxxxxxxxxx /media/kn ext4 0 0
also tried
UUID=xxxxxxxxxxxx /media/kn ext4 0 2
Reply
#44
[/quote]

So this is am external drive is it?

UUII is wrong, I suspect you are not copying and pasting.

It is UUID. To discover the correct UUID use
Code:
sudo blkid

Then do some googling to discover what to put in fstab. Your line is so wrong I don't know where to start. You don't even follow the pattern of the earlier entries.
[/quote]

Sorry, the first 8-10hrs I'm somewhat alert, 11-18+ I get sloppy.

This is a second drive in the same box. I have been googling for 4 days and try to find a second drive in the same box examples. However, most of this time was spent trying to move it to mnt/media. I noticed that I had left the ext4 out but already mentioned that in my last post before I got your post. But that didn't help. I had found the UUID using the code and it also shows when I highlight the drive using Thunar File Manager and I just move the terminal window below it to try not to make an error copying into fstab.
Reply
#45
nickr

You are the man again, tried a few more combinations and got it this time.
Reply

Logout Mark Read Team Forum Stats Members Help
Live TV not showing0