VDR Integration - Revision history

Ray N at 03:47, 25 August 2009

2009-08-25T03:47:44Z

←Older revision		Revision as of 03:47, 25 August 2009
Line 1:		Line 1:
			[[Category: Development]]
	=State Of The Integration=		=State Of The Integration=
	Currently, interaction between LinuxMCE and VDR is mainly done via the SVDR protocol. Remote control is designed to be done with IR remote controls. Scheduling and EPG is done using the VDR OSD. Recordings can be watch either thru the Videos screen, or thru the VDR OSD.		Currently, interaction between LinuxMCE and VDR is mainly done via the SVDR protocol. Remote control is designed to be done with IR remote controls. Scheduling and EPG is done using the VDR OSD. Recordings can be watch either thru the Videos screen, or thru the VDR OSD.

Niz23: /* Variant #2 */

2008-10-21T14:03:15Z

Variant #2

←Older revision		Revision as of 14:03, 21 October 2008
Line 57:		Line 57:

	PreReq:		PreReq:
	Working VDR install on your core.		#Working VDR install on your core.
	No vdr on MD.		#No vdr on MD.

	Create a new TV button that map to a new TV control mechanism/screen.		Create a new TV button that map to a new TV control mechanism/screen.
	When user want to watch a TV channel Xine is started and fetch the chosen channel/stream from streamdev-server.		When user want to watch a TV channel Xine is started and fetch the chosen channel/stream from streamdev-server.
	EPG functionality can be implemented by querying vdr control-plugin.		EPG functionality can be implemented by querying vdr control-plugin and populate an EPG datagrid.
			We need functionality to map the streams provided by streamdev-server to appropriate channel we get from control-plugin.

			Changing channel is just a matter of changing which stream to display.
			We probably get "follow me" functionality too.

			How to handle recording of a channel:

			Since we have a working vdr install in our core we can use that instance to schedule recordings.

			New functionality need to be added into UpdateMedia (or appropriate place) to handle added recordings.
			Maybe we can create have a method in the vdr integration that create an ID3 file for the recording with information fetched from epg.

Niz23: /* Different Approach */

2008-10-21T13:57:46Z

Different Approach

@@ Line 43: / Line 43: @@
 Be able to do everything that onscreen orbiter can do.
-= Different Approach =
+= Different Approach 1=
 Instead of setting up a VDR system on each MD, only have a single instance on the core. Use the http streaming of the vdr-plugin-streamdev-server to provide live streams to xine.
 # Add a file entry containing a URL to each channel
@@ Line 50: / Line 51: @@
 # Have a cron job fill the attributes for the file pointing to the channels
 # Add a record button to the media remote

Marie.o: /* Different Approach */

2008-10-21T13:13:30Z

Different Approach

←Older revision		Revision as of 13:13, 21 October 2008
Line 49:		Line 49:
	# Use xine to play the playlists		# Use xine to play the playlists
	# Have a cron job fill the attributes for the file pointing to the channels		# Have a cron job fill the attributes for the file pointing to the channels
			# Add a record button to the media remote

Marie.o: Notes about a different approach.

2008-10-21T13:12:46Z

Notes about a different approach.

←Older revision		Revision as of 13:12, 21 October 2008
Line 43:		Line 43:

	Be able to do everything that onscreen orbiter can do.		Be able to do everything that onscreen orbiter can do.
			= Different Approach =
			Instead of setting up a VDR system on each MD, only have a single instance on the core. Use the http streaming of the vdr-plugin-streamdev-server to provide live streams to xine.
			# Add a file entry containing a URL to each channel
			# Create Playlists containing all channels
			# Use xine to play the playlists
			# Have a cron job fill the attributes for the file pointing to the channels

Niz23: /* Offscreen Orbiter */

2008-10-21T10:07:04Z

Offscreen Orbiter

←Older revision		Revision as of 10:07, 21 October 2008
Line 41:		Line 41:

	Proposed:		Proposed:

	Be able to do everything that onscreen orbiter can do.		Be able to do everything that onscreen orbiter can do.

Niz23: /* What needs to be done */

2008-10-21T10:06:45Z

What needs to be done

←Older revision		Revision as of 10:06, 21 October 2008
Line 6:		Line 6:

	Proposed:		Proposed:

	A general way of how to control TV apps like VDR or MythTV.		A general way of how to control TV apps like VDR or MythTV.
	I propose that we create a general TVAppPlugin that have all things that we make available in our UI.		I propose that we create a general TVAppPlugin that have all things that we make available in our UI.

Niz23: /* What needs to be done */

2008-10-21T10:06:03Z

What needs to be done

←Older revision		Revision as of 10:06, 21 October 2008
Line 4:		Line 4:
	=What needs to be done=		=What needs to be done=
	To have full control over VDR, and to always know, what state VDR is in at any given time, we need to have vdr-plugin. A vdr-plugin has direct access to events happening within VDR, and can export these events to a LinuxMCE VDRPlugin.		To have full control over VDR, and to always know, what state VDR is in at any given time, we need to have vdr-plugin. A vdr-plugin has direct access to events happening within VDR, and can export these events to a LinuxMCE VDRPlugin.

			Proposed:
			A general way of how to control TV apps like VDR or MythTV.
			I propose that we create a general TVAppPlugin that have all things that we make available in our UI.
			No matter if it is on-screen or off-screen UIs.

			As a second level there is a interface that do VDR or MythTV specifics.

	= OSD or not OSD =		= OSD or not OSD =

Niz23: /* Remote Control */

2008-10-21T09:59:44Z

Remote Control

@@ Line 13: / Line 13: @@
 = Remote Control =
 The current VDRPlugin is designed to work with the on-screen orbiter and a regular IR remote control.
 == Offscreen Orbiter ==
 Off-screen orbiters use UI1. The current UI1 remote control for VDR lacks a couple of standard features
@@ Line 21: / Line 31: @@
 The lighting control and channel list can easily be implemented with a new screen. The EPG listing is a different beast, as not all information seems to be provided by the plugin. And there is currently no provisioning for displaying and controlling timer.

Marie.o: Filled out information about the current VDR implementation, and ideas what needs to be done.

2008-10-21T08:45:57Z

Filled out information about the current VDR implementation, and ideas what needs to be done.

←Older revision		Revision as of 08:45, 21 October 2008
Line 1:		Line 1:
	~~Just a 'stub' right now~~...		=State Of The Integration=
			Currently, interaction between LinuxMCE and VDR is mainly done via the SVDR protocol. Remote control is designed to be done with IR remote controls. Scheduling and EPG is done using the VDR OSD. Recordings can be watch either thru the Videos screen, or thru the VDR OSD.

	This ~~page will contain~~ information ~~about how vdr will~~ be ~~integrated more fully into LinuxMCE~~.		=What needs to be done=
			To have full control over VDR, and to always know, what state VDR is in at any given time, we need to have vdr-plugin. A vdr-plugin has direct access to events happening within VDR, and can export these events to a LinuxMCE VDRPlugin.

			= OSD or not OSD =
			The VDR OSD looks and acts different than the LinuxMCE OSD. Question is, are we going to be able to re-create all the needed pages from the VDR OSD in LinuxMCE screens, and do we want to?

			= Recordings =
			The recordings are currently shown with their filenames vdr.001 to vdr.255 and with a title entry. This does not look nice, and is irritating. The xxx.vdr files should be excluded from the file listing, and the title entry be the only thing visible.

			= Remote Control =
			The current VDRPlugin is designed to work with the on-screen orbiter and a regular IR remote control.
			== Offscreen Orbiter ==
			Off-screen orbiters use UI1. The current UI1 remote control for VDR lacks a couple of standard features
			# No lighting control
			# No off-screen channel list
			# No off-screen EPG listing
			# No off-screen timer settings

			The lighting control and channel list can easily be implemented with a new screen. The EPG listing is a different beast, as not all information seems to be provided by the plugin. And there is currently no provisioning for displaying and controlling timer.