Talk:PVR - Revision history

Karellen at 03:17, 18 July 2020

2020-07-18T03:17:52Z

← Older revision		Revision as of 03:17, 18 July 2020
Line 11:		Line 11:
	! scope="col" width="15%" \| Notes		! scope="col" width="15%" \| Notes
	\|-		\|-
	~~\|[[PVR/Tvheadened~~\|HTS Tvheadend]]		\| HTS Tvheadend
	\|Linux		\|Linux
	\|		\|
Line 19:		Line 19:
	\|[https://www.lonelycoder.com/redmine/projects/tvheadend/wiki lonelycoder wiki]		\|[https://www.lonelycoder.com/redmine/projects/tvheadend/wiki lonelycoder wiki]
	\|-		\|-
	\| ~~[[PVR/~~VDR~~\|VDR]]~~		\| VDR
	\|Linux		\|Linux
	\|		\|
Line 27:		Line 27:
	\|[http://linuxtv.org/vdrwiki/index.php/VDR_installation linuxtv.org]		\|[http://linuxtv.org/vdrwiki/index.php/VDR_installation linuxtv.org]
	\|-		\|-
	\|[[PVR/MythTV\|MythTV]]		\|PVR/MythTV\|MythTV
	\|Linux		\|Linux
	\|		\|
Line 36:		Line 36:
	\|MythTV add-on not yet merged into XBMC PVR Addons Repo, but is available in [https://github.com/fetzerch/xbmc-pvr-addons fetzerch's branch ]		\|MythTV add-on not yet merged into XBMC PVR Addons Repo, but is available in [https://github.com/fetzerch/xbmc-pvr-addons fetzerch's branch ]
	\|-		\|-
	~~\|[[Add-on:MediaPortal_PVR_Client~~\|MediaPortal]]		\| MediaPortal
	\|Windows		\|Windows
	\|Windows, Linux, iOS		\|Windows, Linux, iOS
Line 45:		Line 45:
	\|[http://www.scintilla.utwente.nl/~marcelg/xbmc/tvserverxbmc.html Backend XBMC Plugin] (Required)		\|[http://www.scintilla.utwente.nl/~marcelg/xbmc/tvserverxbmc.html Backend XBMC Plugin] (Required)
	\|-		\|-
	~~\|[[Argus_TV~~\|For The Record]]		\| For The Record
	\|Windows		\|Windows
	\|Windows,		\|Windows,
Line 56:		Line 56:
	\|[http://www.4therecord.eu/wiki/index.php?title=English_Installation_Guide 4therecord.eu wiki]		\|[http://www.4therecord.eu/wiki/index.php?title=English_Installation_Guide 4therecord.eu wiki]
	\|-		\|-
	~~\|[[DVBLink~~\|DVBLink TV Server]]		\| DVBLink TV Server
	\|Windows		\|Windows
	\|Windows		\|Windows
Line 65:		Line 65:
	\|		\|
	\|-		\|-
	~~\|[[PVR/VUPlus~~\|VU+ / Enigma2]]		\| VU+ / Enigma2
	\|Linux (Enigma2)		\|Linux (Enigma2)
	\|Windows, Linux, OSX, iOS		\|Windows, Linux, OSX, iOS
Line 74:		Line 74:
	\|		\|
	\|-		\|-
	\|~~[[PVR/~~NextPVR~~\|NextPVR]]~~		\| NextPVR
	\|Windows		\|Windows
	\|Windows, Linux		\|Windows, Linux
Line 86:		Line 86:
	;PVR history		;PVR history

	XBMC has long had support for viewing recordings from backend recording services such as MythTV and TVHeadend through the use of specialized ~~[[List_of_media_source_types#Videos_Specific_Sources\|~~video sources]] that communicate with the backend software. This did not allow XBMC to be used a true PVR frontend since user still had to view EPG data and schedule recordings via the backend interface. These file sources were also part of the XBMC core codebase, so updates to the backend API often broke the integration until XBMC pushed out an update.		XBMC has long had support for viewing recordings from backend recording services such as MythTV and TVHeadend through the use of specialized video sources that communicate with the backend software. This did not allow XBMC to be used a true PVR frontend since user still had to view EPG data and schedule recordings via the backend interface. These file sources were also part of the XBMC core codebase, so updates to the backend API often broke the integration until XBMC pushed out an update.

	Serious efforts to create a PVR frontend for XBMC started with a project during ~~[[GSoC_-_Unified_PVR_Frontend\|~~Google Summer of Code 2008]]. Project student [[User:Alcoheca\|Alcoheca]] began the fork of what would eventually become the XBMC PVR branch. As this project became more mature it opened the door for skinners to start taking advantage of skinning interfaces for PVR and add them to various XBMC skins.		Serious efforts to create a PVR frontend for XBMC started with a project during Google Summer of Code 2008. Project student [[User:Alcoheca\|Alcoheca]] began the fork of what would eventually become the XBMC PVR branch. As this project became more mature it opened the door for skinners to start taking advantage of skinning interfaces for PVR and add them to various XBMC skins.

	With the release of XBMC 10.0 (Dharma) came the addition of the ~~[[Add-ons\|~~addon]] framework to XBMC. Although binary addons were not available, the PVR branch of XBMC started to use these as a structure for having various backends plug-in to a common API structure.		With the release of XBMC 10.0 (Dharma) came the addition of the addon framework to XBMC. Although binary addons were not available, the PVR branch of XBMC started to use these as a structure for having various backends plug-in to a common API structure.

	During the development cycle for XBMC 12.0 (Frodo) the merge of the PVR and mainline XBMC branches was approved during the Devcon. This made the PVR API available to all mainstream XBMC users, although the addons are still to be maintained in a separate repository and not distributed with XBMC releases.		During the development cycle for XBMC 12.0 (Frodo) the merge of the PVR and mainline XBMC branches was approved during the Devcon. This made the PVR API available to all mainstream XBMC users, although the addons are still to be maintained in a separate repository and not distributed with XBMC releases.
Line 96:		Line 96:
	== Add-on namespace? ==		== Add-on namespace? ==

	Shouldn't the individual articles about PVR add-ons be moved into the Add-on namespace? Currently there are a number of pages already in that namespace, e.g. [[Argus_TV]] that should either be merged under PVR, or they should be merged to Add-on: There is also already a category~~: [[~~:Category:PVR add-ons]] --[[User:Fiveisalive\|Fiveisalive]] 17:19, 10 October 2012 (EDT)		Shouldn't the individual articles about PVR add-ons be moved into the Add-on namespace? Currently there are a number of pages already in that namespace, e.g. Argus_TV that should either be merged under PVR, or they should be merged to Add-on: There is also already a category: Category:PVR add-ons --[[User:Fiveisalive\|Fiveisalive]] 17:19, 10 October 2012 (EDT)

	:Well, the add-on namespace is mainly for individual add-on entries more than it is for add-on related pages, while the sub-pages of the PVR guide are about both the add-ons and the backends. I wasn't sure how much over-lap there would be, so if it makes more sense to just have everything on the PVR add-on page and then link directly to that (and not have a sub page here) then we can certainly do that instead. -- [[User:Ned Scott\|Ned Scott]] 22:38, 10 October 2012 (EDT)		:Well, the add-on namespace is mainly for individual add-on entries more than it is for add-on related pages, while the sub-pages of the PVR guide are about both the add-ons and the backends. I wasn't sure how much over-lap there would be, so if it makes more sense to just have everything on the PVR add-on page and then link directly to that (and not have a sub page here) then we can certainly do that instead. -- [[User:Ned Scott\|Ned Scott]] 22:38, 10 October 2012 (EDT)

	::OK, well I went systematically through all various Add-on:<client name> and PVR/<client_name> pages and tried to normalize as per the setup for [[PVR/VDR]] and [[Add-on:VDR VNSI Client]], i.e. moved all the Settings info to the Add-on page and transincluded it in the corresponding PVR/<client name> page. This seems OK since we don't duplicate wikitext that will get out of date. The only thing that I don't quite like about this setup is that there's no obvious way for the user (as opposed to a wiki editor) to get to the corresponding Add-on page. My understanding that a good bulk of each Add-on: page will be autogenerated from repo information, but that the settings part would be manually updated? --[[User:Fiveisalive\|Fiveisalive]] 14:52, 17 October 2012 (EDT)		::OK, well I went systematically through all various Add-on:<client name> and PVR/<client_name> pages and tried to normalize as per the setup for PVR/VDR and Add-on:VDR VNSI Client, i.e. moved all the Settings info to the Add-on page and transincluded it in the corresponding PVR/<client name> page. This seems OK since we don't duplicate wikitext that will get out of date. The only thing that I don't quite like about this setup is that there's no obvious way for the user (as opposed to a wiki editor) to get to the corresponding Add-on page. My understanding that a good bulk of each Add-on: page will be autogenerated from repo information, but that the settings part would be manually updated? --[[User:Fiveisalive\|Fiveisalive]] 14:52, 17 October 2012 (EDT)

	:::Settings will always have to be manually updated, unless we can figure out some way for add-on authors to include it in the (often unused) readme.txt file in the add-on, and automate that with a script.		:::Settings will always have to be manually updated, unless we can figure out some way for add-on authors to include it in the (often unused) readme.txt file in the add-on, and automate that with a script.

Karellen at 22:00, 15 July 2020

2020-07-15T22:00:09Z

← Older revision		Revision as of 22:00, 15 July 2020
Line 92:		Line 92:
	With the release of XBMC 10.0 (Dharma) came the addition of the [[Add-ons\|addon]] framework to XBMC. Although binary addons were not available, the PVR branch of XBMC started to use these as a structure for having various backends plug-in to a common API structure.		With the release of XBMC 10.0 (Dharma) came the addition of the [[Add-ons\|addon]] framework to XBMC. Although binary addons were not available, the PVR branch of XBMC started to use these as a structure for having various backends plug-in to a common API structure.

	During the development cycle for XBMC 12.0 (Frodo) the merge of the PVR and mainline XBMC branches was approved during the ~~[[XBMC_DevCon\|XBMC~~ Devcon]]. This made the PVR API available to all mainstream XBMC users, although the addons are still to be maintained in a separate repository and not distributed with XBMC releases.		During the development cycle for XBMC 12.0 (Frodo) the merge of the PVR and mainline XBMC branches was approved during the Devcon. This made the PVR API available to all mainstream XBMC users, although the addons are still to be maintained in a separate repository and not distributed with XBMC releases.

	== Add-on namespace? ==		== Add-on namespace? ==

Karellen: Fix dead links

2018-03-07T06:03:05Z

Fix dead links

← Older revision		Revision as of 06:03, 7 March 2018
Line 45:		Line 45:
	\|[http://www.scintilla.utwente.nl/~marcelg/xbmc/tvserverxbmc.html Backend XBMC Plugin] (Required)		\|[http://www.scintilla.utwente.nl/~marcelg/xbmc/tvserverxbmc.html Backend XBMC Plugin] (Required)
	\|-		\|-
	\|[[~~PVR/For The Record~~\|For The Record]]		\|[[Argus_TV\|For The Record]]
	\|Windows		\|Windows
	\|Windows,		\|Windows,
Line 96:		Line 96:
	== Add-on namespace? ==		== Add-on namespace? ==

	Shouldn't the individual articles about PVR add-ons be moved into the Add-on namespace? Currently there are a number of pages already in that namespace, e.g. [[~~Add-on:ForTheRecord_PVR_client~~]] that should either be merged under PVR, or they should be merged to Add-on: There is also already a category: [[:Category:PVR add-ons]] --[[User:Fiveisalive\|Fiveisalive]] 17:19, 10 October 2012 (EDT)		Shouldn't the individual articles about PVR add-ons be moved into the Add-on namespace? Currently there are a number of pages already in that namespace, e.g. [[Argus_TV]] that should either be merged under PVR, or they should be merged to Add-on: There is also already a category: [[:Category:PVR add-ons]] --[[User:Fiveisalive\|Fiveisalive]] 17:19, 10 October 2012 (EDT)

	:Well, the add-on namespace is mainly for individual add-on entries more than it is for add-on related pages, while the sub-pages of the PVR guide are about both the add-ons and the backends. I wasn't sure how much over-lap there would be, so if it makes more sense to just have everything on the PVR add-on page and then link directly to that (and not have a sub page here) then we can certainly do that instead. -- [[User:Ned Scott\|Ned Scott]] 22:38, 10 October 2012 (EDT)		:Well, the add-on namespace is mainly for individual add-on entries more than it is for add-on related pages, while the sub-pages of the PVR guide are about both the add-ons and the backends. I wasn't sure how much over-lap there would be, so if it makes more sense to just have everything on the PVR add-on page and then link directly to that (and not have a sub page here) then we can certainly do that instead. -- [[User:Ned Scott\|Ned Scott]] 22:38, 10 October 2012 (EDT)

Opdenkamp: /* From main page */

2013-09-07T10:16:26Z

From main page

← Older revision		Revision as of 10:16, 7 September 2013
Line 15:		Line 15:
	\|		\|
	\|[http://www.lonelycoder.com/hts/tvheadend_overview.html lonelycoder.com]		\|[http://www.lonelycoder.com/hts/tvheadend_overview.html lonelycoder.com]
	\|~~dushmaniac~~		\|[[User:opdenkamp\|opdenkamp]]
	\|[http://forum.xbmc.org/showthread.php?t=91716 XBMC Forum]		\|[http://forum.xbmc.org/showthread.php?t=91716 XBMC Forum]
	\|[https://www.lonelycoder.com/redmine/projects/tvheadend/wiki lonelycoder wiki]		\|[https://www.lonelycoder.com/redmine/projects/tvheadend/wiki lonelycoder wiki]

Ned Scott: /* Add-on namespace? */

2012-10-21T01:02:23Z

Add-on namespace?

← Older revision		Revision as of 01:02, 21 October 2012
Line 101:		Line 101:

	::OK, well I went systematically through all various Add-on:<client name> and PVR/<client_name> pages and tried to normalize as per the setup for [[PVR/VDR]] and [[Add-on:VDR VNSI Client]], i.e. moved all the Settings info to the Add-on page and transincluded it in the corresponding PVR/<client name> page. This seems OK since we don't duplicate wikitext that will get out of date. The only thing that I don't quite like about this setup is that there's no obvious way for the user (as opposed to a wiki editor) to get to the corresponding Add-on page. My understanding that a good bulk of each Add-on: page will be autogenerated from repo information, but that the settings part would be manually updated? --[[User:Fiveisalive\|Fiveisalive]] 14:52, 17 October 2012 (EDT)		::OK, well I went systematically through all various Add-on:<client name> and PVR/<client_name> pages and tried to normalize as per the setup for [[PVR/VDR]] and [[Add-on:VDR VNSI Client]], i.e. moved all the Settings info to the Add-on page and transincluded it in the corresponding PVR/<client name> page. This seems OK since we don't duplicate wikitext that will get out of date. The only thing that I don't quite like about this setup is that there's no obvious way for the user (as opposed to a wiki editor) to get to the corresponding Add-on page. My understanding that a good bulk of each Add-on: page will be autogenerated from repo information, but that the settings part would be manually updated? --[[User:Fiveisalive\|Fiveisalive]] 14:52, 17 October 2012 (EDT)

			:::Settings will always have to be manually updated, unless we can figure out some way for add-on authors to include it in the (often unused) readme.txt file in the add-on, and automate that with a script.

			:::I'm also not wild about having two pages for the backend add-ons. It might be best to just move the settings to the PVR subpages, or just redirect one page to the other, but for the time being I wouldn't worry too much about that. We'll likely change/tweak the over-all structure as we get a better feel for what information we have, and what information is still needed. Right now the big thing is just getting that raw content, then we can move things around and such. Of course, any ideas on what our final structure should be are most welcome.

			:::Awesome work, by the way! -- [[User:Ned Scott\|Ned Scott]] 21:02, 20 October 2012 (EDT)

Ned Scott at 09:16, 18 October 2012

2012-10-18T09:16:53Z

← Older revision		Revision as of 09:16, 18 October 2012
Line 1:		Line 1:
	From main page:		==From main page==

	{\| class="wikitable" style="text-align: left;"		{\| class="wikitable" style="text-align: left;"

Ned Scott at 09:16, 18 October 2012

2012-10-18T09:16:35Z

@@ Line 1: / Line 1: @@
 From main page:
-==PVR History==
+{| class="wikitable" style="text-align: left;"
 XBMC has long had support for viewing recordings from backend recording services such as MythTV and TVHeadend through the use of specialized [[List_of_media_source_types#Videos_Specific_Sources|video sources]] that communicate with the backend software. This did not allow XBMC to be used a true PVR frontend since user still had to view EPG data and schedule recordings via the backend interface. These file sources were also part of the XBMC core codebase, so updates to the backend API often broke the integration until XBMC pushed out an update.

>Fiveisalive: /* Add-on namespace? */

2012-10-17T18:52:15Z

Add-on namespace?

← Older revision		Revision as of 18:52, 17 October 2012
Line 16:		Line 16:

	:Well, the add-on namespace is mainly for individual add-on entries more than it is for add-on related pages, while the sub-pages of the PVR guide are about both the add-ons and the backends. I wasn't sure how much over-lap there would be, so if it makes more sense to just have everything on the PVR add-on page and then link directly to that (and not have a sub page here) then we can certainly do that instead. -- [[User:Ned Scott\|Ned Scott]] 22:38, 10 October 2012 (EDT)		:Well, the add-on namespace is mainly for individual add-on entries more than it is for add-on related pages, while the sub-pages of the PVR guide are about both the add-ons and the backends. I wasn't sure how much over-lap there would be, so if it makes more sense to just have everything on the PVR add-on page and then link directly to that (and not have a sub page here) then we can certainly do that instead. -- [[User:Ned Scott\|Ned Scott]] 22:38, 10 October 2012 (EDT)

			::OK, well I went systematically through all various Add-on:<client name> and PVR/<client_name> pages and tried to normalize as per the setup for [[PVR/VDR]] and [[Add-on:VDR VNSI Client]], i.e. moved all the Settings info to the Add-on page and transincluded it in the corresponding PVR/<client name> page. This seems OK since we don't duplicate wikitext that will get out of date. The only thing that I don't quite like about this setup is that there's no obvious way for the user (as opposed to a wiki editor) to get to the corresponding Add-on page. My understanding that a good bulk of each Add-on: page will be autogenerated from repo information, but that the settings part would be manually updated? --[[User:Fiveisalive\|Fiveisalive]] 14:52, 17 October 2012 (EDT)

Ned Scott: /* Add-on namespace? */

2012-10-11T02:38:46Z

Add-on namespace?

← Older revision		Revision as of 02:38, 11 October 2012
Line 14:		Line 14:

	Shouldn't the individual articles about PVR add-ons be moved into the Add-on namespace? Currently there are a number of pages already in that namespace, e.g. [[Add-on:ForTheRecord_PVR_client]] that should either be merged under PVR, or they should be merged to Add-on: There is also already a category: [[:Category:PVR add-ons]] --[[User:Fiveisalive\|Fiveisalive]] 17:19, 10 October 2012 (EDT)		Shouldn't the individual articles about PVR add-ons be moved into the Add-on namespace? Currently there are a number of pages already in that namespace, e.g. [[Add-on:ForTheRecord_PVR_client]] that should either be merged under PVR, or they should be merged to Add-on: There is also already a category: [[:Category:PVR add-ons]] --[[User:Fiveisalive\|Fiveisalive]] 17:19, 10 October 2012 (EDT)

			:Well, the add-on namespace is mainly for individual add-on entries more than it is for add-on related pages, while the sub-pages of the PVR guide are about both the add-ons and the backends. I wasn't sure how much over-lap there would be, so if it makes more sense to just have everything on the PVR add-on page and then link directly to that (and not have a sub page here) then we can certainly do that instead. -- [[User:Ned Scott\|Ned Scott]] 22:38, 10 October 2012 (EDT)

>Fiveisalive: /* Add-on namespace? */ new section

2012-10-10T21:19:42Z

Add-on namespace?: new section

← Older revision		Revision as of 21:19, 10 October 2012
Line 10:		Line 10:

	During the development cycle for XBMC 12.0 (Frodo) the merge of the PVR and mainline XBMC branches was approved during the [[XBMC_DevCon\|XBMC Devcon]]. This made the PVR API available to all mainstream XBMC users, although the addons are still to be maintained in a separate repository and not distributed with XBMC releases.		During the development cycle for XBMC 12.0 (Frodo) the merge of the PVR and mainline XBMC branches was approved during the [[XBMC_DevCon\|XBMC Devcon]]. This made the PVR API available to all mainstream XBMC users, although the addons are still to be maintained in a separate repository and not distributed with XBMC releases.

			== Add-on namespace? ==

			Shouldn't the individual articles about PVR add-ons be moved into the Add-on namespace? Currently there are a number of pages already in that namespace, e.g. [[Add-on:ForTheRecord_PVR_client]] that should either be merged under PVR, or they should be merged to Add-on: There is also already a category: [[:Category:PVR add-ons]] --[[User:Fiveisalive\|Fiveisalive]] 17:19, 10 October 2012 (EDT)