+- Kodi Community Forum (https://forum.kodi.tv)
+-- Forum: Support (https://forum.kodi.tv/forumdisplay.php?fid=33)
+--- Forum: Tips, tricks, and step by step guides (https://forum.kodi.tv/forumdisplay.php?fid=110)
+--- Thread: [OLD] HOW-TO watch Live TV in XBMC for Linux with Tvheadend, the easy way! (/showthread.php?tid=51945)
Pages:
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
EPG ext_text - sengst - 2011-01-18
Is it true that XBMC does not import the ext_text data from Tvheadend?
I've compared the EPG output of Tvheadend (localhost:9981/epg) with the parseevent in the xbmc.log.
It does import the desc string but not the ext_text string. Most german channels seem to provide in the desc string only a kind of subtitle and description itself in the ext_text string.
Are there any plans of supporting this string? Or do I have missed some settings anywhere ;-)
- opdenkamp - 2011-01-18
There is no 'ext_text' in the HTSP protocol. the following fields are sent and these are used by the addon:
Code:
start int required Start time of event (Seconds since the epoch, in UTC)
stop int required Ending time of event (Seconds since the epoch, in UTC)
title str optional Title of event.
description str optional Description of event. This can be quite huge and may also contain newlines.
channelId int required ID of channel (introduced in HTSP version 4)
nextEventId int optional ID of next event on the same channel.
contentType int optional dvb content code (introduced in HTSP version 4)you can find the htsp protocol documentation here: http://www.lonelycoder.com/redmine/projects/tvheadend/wiki/Htsp
- sengst - 2011-01-19
dushmaniac Wrote:There is no 'ext_text' in the HTSP protocol. the following fields are sent and these are used by the addon:
Code:start int required Start time of event (Seconds since the epoch, in UTC)
stop int required Ending time of event (Seconds since the epoch, in UTC)
title str optional Title of event.
description str optional Description of event. This can be quite huge and may also contain newlines.
channelId int required ID of channel (introduced in HTSP version 4)
nextEventId int optional ID of next event on the same channel.
contentType int optional dvb content code (introduced in HTSP version 4)
you can find the htsp protocol documentation here: http://www.lonelycoder.com/redmine/projects/tvheadend/wiki/Htsp
Thanks for your answer!
Just for clarificaton:
Here's the output of localhost:9981/epg for a program just running:
Code:
{"channel": "Das Erste","channelid": 52,"title": "Menschen bei Maischberger","description": "Thema: Altwerden macht Spaß? Alles Lüge!","ext_text": "Zu Gast: * Joachim Fuchsberger, Schauspieler und Entertainer * Dr. Marianne Koch, Ärztin und Autorin * Harry Valérien, Sportmoderator * Edgar Geller, bietet Kampfsportkurse für Senioren an","id": 2714,"start": 1295387100,"end": 1295391600,"duration": 4500,"contentgrp": "Movie / Drama"}
Here's the output in the xbmc.log for the same program:
Code:
21:59:49 T:139738192049920 M:2362433536 DEBUG: AddOnLog: xbmc.pvrclient/Tvheadend HTSP Client: ParseEvent - id:2625, chan_id:28, title:'Menschen bei Maischberger', genre_type:1, genre_sub_type:0, desc:'Thema: Altwerden macht Spaß? Alles Lüge!', start:1295387100, stop:1295391600, next:2626
Am I right that the problem is on the Tvheadend side? Does it have to append the ext_text field to description field for the htsp transmission?
Thanks for your answer!
- opdenkamp - 2011-01-19
looks like that field is missing in the htsp protocol indeed, or it's not documented. haven't checked the code.
- Dojrude - 2011-01-19
dushmaniac Wrote:@Dojrude:
please pastebin your debug log: http://wiki.xbmc.org/index.php?title=Log_file
Doesn't this apply to xbmc only?
I don't currently have xbmc installed as I'm trying to get tvheadend working correctly first, before moving on to integrating into xbmc.
Are there any tvheadend specific logs that I can provide?
- opdenkamp - 2011-01-19
then you should post your problem here: http://www.lonelycoder.com/redmine/projects/tvheadend/boards
I was assuming you had tvheadend working correctly and you were having problems with the tvheadend addon.
- Dojrude - 2011-01-19
dushmaniac Wrote:then you should post your problem here: http://www.lonelycoder.com/redmine/projects/tvheadend/boards
I was assuming you had tvheadend working correctly and you were having problems with the tvheadend addon.
Apologies.
I thought that as you were providing the ppa download for tvheadend, that you'd also answer questions on it. Lonelycoder forums are completely dead, so would be wasting my time posting there (6 topics on whole forum).
I'll have to see if I can resolve it myself.
- Ruud - 2011-01-19
Dojrude Wrote:Apologies.Hi,
I thought that as you were providing the ppa download for tvheadend, that you'd also answer questions on it. Lonelycoder forums are completely dead, so would be wasting my time posting there (6 topics on whole forum).
I'll have to see if I can resolve it myself.
just to reflect on almost empty lonelycoder forum: it is in transition from mailing list to forum, that is the reason.
as you know: if nobody posts on the forum it is very likely to stay 'empty'
I suggest you give it a try on the forum.
regards,
Ruud.
- opdenkamp - 2011-01-19
I agree with Ruud.
- xoox - 2011-01-19
sengst Wrote:Is it true that XBMC does not import the ext_text data from Tvheadend?
I've compared the EPG output of Tvheadend (localhost:9981/epg) with the parseevent in the xbmc.log.
It does import the desc string but not the ext_text string. Most german channels seem to provide in the desc string only a kind of subtitle and description itself in the ext_text string.
Are there any plans of supporting this string? Or do I have missed some settings anywhere ;-)
I had the same problem. I swapped ext_text and desc in the HTSP part of the Tvheadend source code and now I have the description in XBMC :-)
But you're right, there should be a general solution to this problem.
- ant_thomas - 2011-01-19
Dojrude Wrote:Apologies.
I thought that as you were providing the ppa download for tvheadend, that you'd also answer questions on it. Lonelycoder forums are completely dead, so would be wasting my time posting there (6 topics on whole forum).
I'll have to see if I can resolve it myself.
Or try the IRC channel - irc://irc.freenode.net/hts
Plenty of people on there.
- stippie - 2011-01-20
@Ruud, Hi there, I see you're using the ct3650ci. I just received this device today. Trying to get it to work now. I have standard xbmc live 10 install. and device is recognized when doin' lsusb. but says no driver. Can you help me out on this ?
- prensel - 2011-01-20
I (finally) installed xbmc-dharma-pvr on my Archlinux Asrock ION and noticed that when using the Live TV option the order of the tv channels is not according the channelnumbers. When using the htsp stream as source (from the content menu) the order is according the channelnumbers. Is this a known bug in XBMC Dharma ?
- xoox - 2011-01-20
prensel Wrote:I (finally) installed xbmc-dharma-pvr on my Archlinux Asrock ION and noticed that when using the Live TV option the order of the tv channels is not according the channelnumbers. When using the htsp stream as source (from the content menu) the order is according the channelnumbers. Is this a known bug in XBMC Dharma ?
Yes, that's known. I would call it a missing feature instead of a bug. You can change the channel numbers manually.
- prensel - 2011-01-20
xoox Wrote:Yes, that's known. I would call it a missing feature instead of a bug. You can change the channel numbers manually.
Cant this be easily changed by having an 'order' field in the designated xml file ?
I vagely remember to have seen something like this for having the movies or tv shows putting ordered on the screen...