Login at Kodi Home

**dnairb** · (This post was last modified: 2016-03-07, 00:42 by dnairb.)

The current behaviour is as below: (running Ubuntu 14.04.4, Kodi 16.0, TVHeadend 4.0.8, kodi-pvr-hts 2.2.14-1)

ActivateWindow(TVGuide) -> opens MyPVRGuide.xml with TV guide
ActivateWindow(RadioGuide) -> opens MyPVRGuide.xml with Radio guide

ActivateWindow(TVTimers) -> opens MyPVRTimers.xml with TV timers
ActivateWindow(RadioTimers) -> opens MyPVRTimers.xml with Radio timers

ActivateWindow(TVSearch) -> opens MyPVRSearch.xml to search TV programs
ActivateWindow(RadioSearch) -> opens MyPVRSearch.xml to search Radio programs

However, both ActivateWindow(TVRecordings) and ActivateWindow(RadioRecordings) open MyPVRRecordings.xml with all recordings listed.

I propose that TV recordings and Radio recordings be separated in MyPVRRecordings.xml.
I guess that this could be achieved if TVHeadend tagged each recording with either "TV" or "Radio" (channels are currently tagged in this way), and this tag was read by the kodi-pvr-hts addon.

rpcameron · 2016-03-07, 01:17

Are you using Confluence, or a different skin? Because it sounds like a skin issue; the author may not have properly updated it for changes in Jarvis.

**dnairb** · 2016-03-07, 01:26

(2016-03-07, 01:17)rpcameron Wrote: Are you using Confluence, or a different skin? Because it sounds like a skin issue; the author may not have properly updated it for changes in Jarvis.

I am using the Confluence skin. However, if there have been changes, surely <onclick>ActivateWindow(RadioRecordings)</onclick> would open up a window showing Radio recordings only, whatever the skin?

rpcameron · 2016-03-07, 04:47

Since they're both using the same XML file for their interface, it is up to the skin to filter out and provide the proper control IDs. Yet since this is Confluence, that is likely not the issue.

**ksooo** · 2016-03-07, 09:05

(2016-03-07, 00:11)dnairb Wrote: The current behaviour is as below: (running Ubuntu 14.04.4, Kodi 16.0, TVHeadend 4.0.8, kodi-pvr-hts 2.2.14-1)

ActivateWindow(TVGuide) -> opens MyPVRGuide.xml with TV guide
ActivateWindow(RadioGuide) -> opens MyPVRGuide.xml with Radio guide

ActivateWindow(TVTimers) -> opens MyPVRTimers.xml with TV timers
ActivateWindow(RadioTimers) -> opens MyPVRTimers.xml with Radio timers

ActivateWindow(TVSearch) -> opens MyPVRSearch.xml to search TV programs
ActivateWindow(RadioSearch) -> opens MyPVRSearch.xml to search Radio programs

However, both ActivateWindow(TVRecordings) and ActivateWindow(RadioRecordings) open MyPVRRecordings.xml with all recordings listed.

I propose that TV recordings and Radio recordings be separated in MyPVRRecordings.xml.
I guess that this could be achieved if TVHeadend tagged each recording with either "TV" or "Radio" (channels are currently tagged in this way), and this tag was read by the kodi-pvr-hts addon.

You are right. This is not a skinning issue.

Kodi currently internally is not able to distinguish between tv and radio recordings, although the skinning interface implies that this works. Currently an add-on has no chance (api missing) to flag a recording as tv or radio.

And for tvheadend, tvh does not supply this information. So, even if Kodi pvr add-on would have the field in question, the tvheadend add-on could not fill it. For this, tvheadend itself needs to be extended first.

**dnairb** · (This post was last modified: 2016-03-07, 11:33 by dnairb.)

(2016-03-07, 09:05)ksooo Wrote: You are right. This is not a skinning issue.

Kodi currently internally is not able to distinguish between tv and radio recordings, although the skinning interface implies that this works. Currently an add-on has no chance (api missing) to flag a recording as tv or radio.

And for tvheadend, tvh does not supply this information. So, even if Kodi pvr add-on would have the field in question, the tvheadend add-on could not fill it. For this, tvheadend itself needs to be extended first.

As I proposed:

(2016-03-07, 00:11)dnairb Wrote: .
.
.
I guess that this could be achieved if TVHeadend tagged each recording with either "TV" or "Radio" (channels are currently tagged in this way), and this tag was read by the kodi-pvr-hts addon.

**ksooo** · (This post was last modified: 2016-03-07, 11:45 by ksooo.)

Yeah, just wanted to second what you wrote as I know all involved code (kodi/pvr.hts/tvheadend ) pretty well. :-)

So, tvh needs to be extended to support this tag (htsp version change!), all pvr add-ons needs to be extended (pvr add-on API change!) and Kodi needs to be extended, too.

Problem: how to act if an add-on cannot support the tag, for instance pvr.hts talking to an "old" tvheadend? Flag all as radio or tv or is the flag actually a tri state, including "don't know" value? How to deal with this "don't know" in the UI?

**dnairb** · (This post was last modified: 2016-03-09, 19:29 by dnairb.)

I don't now think that TVHeadend would need to tag recordings as "TV" or "Radio", as it already tags the recording with the channel name (it does the same for timers.)
Somehow, the fact that a timer is tagged "Channel 4", for example, relates to the timer being for a TV channel (Channel 4 is tagged "TV" in the channels tab on the TVH configuration browser interface.)
Recordings are also tagged with the channel name, so could this not be associated with the "Radio" or "TV" tag in the channels tab?

So I think (though I may be wrong) that the necessary info is there, it just(!) needs to be accessed to enable this separation.

**ksooo** · 2016-03-09, 19:34

A recording may live way longer than the channel configured in tvheadend. The channel may disappear at any time for different reasons. Anyway, in that case the channel name / id stored along with the recording cannot be used to lookup whether that channel is tv or radio. Tvheadend simply does not know any longer about that channel. Thus, the info whether a recording is tv or radio must be stored directly along with the recording.

**dnairb** · 2016-03-09, 19:57

(2016-03-09, 19:34)ksooo Wrote: A recording may live way longer than the channel configured in tvheadend. The channel may disappear at any time for different reasons. Anyway, in that case the channel name / id stored along with the recording cannot be used to lookup whether that channel is tv or radio. Tvheadend simply does not know any longer about that channel. Thus, the info whether a recording is tv or radio must be stored directly along with the recording.

Valid point. In that case, I suppose TVH or the pvr addon could tag the recording at the time the recording is made? Or leave it to the user to add a category to the timer?

**ksooo** · 2016-03-09, 19:59

tvh should do that, the add-on has not an own data storage.

**dnairb** · 2016-03-14, 01:46

Hmmm..... I have just tried the latest nightly build of the forthcoming Kodi Krypton. This feature is implemented!

**ksooo** · 2016-03-14, 09:06

Sure, instead of spamming the forum I just implemented it. ;-)

**dnairb** · 2016-03-14, 18:47

Coolio :-)

Jönke · 2016-03-14, 22:13

Please tell me If you can play your recordings again , didnt work last time i tested ( Rpi build )