LinuxMCE - User contributions [en]

Add support for new remote controls

2009-05-22T14:37:46Z

Centove: /* Adding Support for a New Remote using a USB UIRT Receiver */

{| align="right"
| __TOC__
|}
[[Category:Input]]
[[Category:Infrared]]
[[Category:Tutorials]]
===Overview===
In general, adding support for a new remote control is accomplished by pressing each button and capturing a key code sent by the remote. Once the key code captured for each key, they are organized into a map that is used to configure LinuxMCE.

===Receiver Hardware===
There are a variety of different infrared (IR) receivers that work with LinuxMCE. Infrared receivers are small pieces of hardware that have an infrared-sensitive "eye" and plug into a computer. Some examples of LinuxMCE compatible IR receivers are [[USB UIRT]], [[Tira]], and [[IRTrans]].

===Receiver Software===
For some IR receivers, the best support is via [http://lirc.org/ LIRC], while for others, purpose-built LinuxMCE drivers are available.

===Learning Is Specific to Combination of Receiver and Remote===
The key code that is captured when a button is pressed depends on both the remote control model ''and'' the receiver model. That is, the key codes that you capture from a [[Windows MCE Remote]] with USB UIRT are different from those captured from the same remote with Tira or IRTrans.

===Adding Support for a New Remote using a USB UIRT Receiver===
''The technique in this section was originally provided in [http://forum.linuxmce.org/index.php?topic=4901.msg28630#msg28630 this forum post].''

To add support for a new remote using USB UIRT as a receiver, perform the steps below. Note that most of the configuration is performed through the Web Admin Page:

:1. Verify USB UIRT is installed and configured: Once you plug in the USB UIRT it should be plug and play and add both the '''USB UIRT''' device as well as the '''Windows XP MCE Remote (USBUIRT)'''. Go to '''Wizard->devices->media directors'''. Near the bottom of the page you should see the MCE remote listed, with the '''Infrared Receivers''' pulldown set to '''USB UIRT 0038'''.[[Image:DirectorShot.jpg]]

:2. Create a new template for your remote: Go to '''Advanced->Configuration->Device Templates'''.
[[Image:DeviceTemplate.png]] Select the remote's manufacturer and <tt>USB-UIRT Remote Controls < Remote Controls < Peripherals</tt> from '''Device Category''' then click '''Add Device Template'''. This will open the '''Add device template window'''. Enter the name or model # of the remote followed by <tt>(USBUIRT)</tt> into the text box and click '''Add'''. Try to be descriptive and unambiguous if you don't have a model number. For example, a good name for the remote that comes bundled with the Hauppauge PVR-150 is <tt>PVR-150 remote (USBUIRT)</tt>. The number of characters allowed is limited, so you'll have to use your judgment to come up with a good name.
[[image:USB UIRT new remote.jpg|right|thumb|128px|screenshot details for steps 3,6 and 7]]

:3. Configure the remote correctly: Go to '''Advanced->Configuration->Device Templates''', find the remote you just added (you may have to refresh your browser to see it), and click the '''Pick Template''' button. This brings up the '''Edit Device Template''' window. Change the '''Device Category''' to '''Peripherals - Remote Controls - USB-UIRT Remote Controls'''. Select the correct manufacturer for your remote.

:4. Get the USB UIRT device ID: From the bottom of the left pane on the Admin Page, click '''Show devices tree'''. In the tree, click '''USB UIRT 0038'''. Find the device number in the title of the '''Device Info''' block. For example, '''Device Info #50''' indicates that the USB UIRT is device #50.

:5. Capture the key codes: In a terminal window, enter the command <code>tail -f /var/log/pluto/XX_USB_UIRT_0038.log</code> where XX is the device number you found in the previous step. Press a button on the remote control twice. You should see something like this:
05 05/16/08 19:29:18.757 Cannot find anything for IR 1500003E3CFC <0x40800950>
05 05/16/08 19:29:19.021 Cannot find anything for IR 1700009E0FC0 <0x40800950>
:The numbers <code>1500003E3CFC</code> and <code>1700009E0FC0</code> are the key codes for that button. If the two numbers are the same, then there is only one key code for that button. In a text editor, format the button names and key codes in the same format as [[#Sample USB UIRT key codes|this]].

:6. Add the Configuration (string): In the '''Device Data''' box select '''Configuration'''. Paste the key codes you created in the last step into the '''Default Value''' field. Click the '''Use Master Device List Defaults''' box.

:7. Add the Remote Layout (String): In the Device Data box, add the new parameter '''Remote Layout (String)'''. In the '''Default Value''' field enter W.

:8. Click '''Save''' then '''Close''' to close the '''Edit Device Template''' window.

:9. Add the remote: Go to '''Wizard->devices->Media Directors''' and scroll to the media director that you want to control with the remote. Click '''Add Remote''' then select the remote template you just created from the '''Device Template''' drop-down. Click '''Pick Template''' and then back on the Media Director page, click '''Update'''. After this you should be prompted to reload the router, if not do a quick reload.

Once the router reloads, you should have a working remote.

===Share your Key Codes===
It is helpful to share your key codes with others. See [[Share IR Codes]] for details.

===LIRC===
LinuxMCE's infrared remote control module is based on LIRC. See http://lirc.org/ for details. LIRC includes an 'IR Record' utility to build a configuration file for a new remote control. Once you do that, then in LinuxMCE Admin choose 'Advanced', 'Device Templates'. Choose the manufacturer, for the Category choose Peripherals, Remote Controls, LIRC Remote controls. Type in the model of the remote and click 'add'. Then edit the device, add a device data "Configuration" and copy the LIRC configuration file into it.

The Programming Guide in [[Control LinuxMCE using an Infrared remote]] explains how it all works, and also how to use it.

[[Adding iMON PAD]] explains how to add it to the LinnuxMCE.

===Related Topics===
[[Control LinuxMCE using an Infrared remote]]

[[Infrared Remote Buttons Understood by LinuxMCE]]

[[Share IR Codes]]

[[Adding a New MCE Compatible Transceiver]]

===Sample USB UIRT key codes===
power 170000870FC0 1500003F0FC0
stop 1300000F3FFC 170000F80FC0
record 150000383FFC 170000F80FC0
pause 150000303EFC 170000D00FC0
play 130000093FFC 150000390FC0
rewind 1300000F3EFC 150000370FC0
fastforward 1300000B3FFC 1500003B0FC0
skipback 1300000F37FC 1500003F0DC0
skipfwd 150000212DFC 170000A10BC0
back 170000802DFC 190002400BC0
up 1300000B2EFC 150000330BC0
left 1300000F2EFC 150000370BC0
ok 1300000D37FC 1500003D0DC0
right 150000382EFC 170000D80BC0
down 130000092EFC 150000310BC0
volup 150000302FFC 170000F00BC0
voldn 150000322FFC 170000F20BC0
chup 1500002036FC 170000C00DC0
chdown 1500002236FC 170000C20DC0
mute 170000A029FC 190002500AC0
menu 1500002F29FC 170000AF0AC0
1 1700008228FC 190002010AC0
2 1500002328FC 170000830AC0
3 1700008A28FC 190002050AC0
4 1500002F28FC 1700008F0AC0
5 1500002D28FC 1700008D0AC0
6 1500002B28FC 1700008B0AC0
7 170000A828FC 190002140AC0
8 1500003C29FC 170000BC0AC0
9 1500003E29FC 170000BE0AC0
0 1700008028FC 190002000AC0
red 1500003629FC 170000B60AC0
green 1300000933FC 150000390CC0
yellow 150000343CFC 170000940FC0
blue 1300000E31FC 1500002E0CC0
tv 150000252DFC 170000A50BC0
videos 150000342DFC 170000B40BC0
music 150000362DFC 170000B60BC0
pictures 1300000E2DFC 1500002E0BC0
guide 1500003E2DFC 170000BE0BC0
radio 1500002D29FC 170000AD0AC0
previouschannel 1300000F2FFC 1500003F0BC0
go 1500003E3CFC 1700009E0FC0

File:DeviceTemplate.png

2009-05-22T14:35:27Z

Centove:

Add support for new remote controls

2009-05-22T14:35:09Z

Centove: /* Adding Support for a New Remote using a USB UIRT Receiver */

{| align="right"
| __TOC__
|}
[[Category:Input]]
[[Category:Infrared]]
[[Category:Tutorials]]
===Overview===
In general, adding support for a new remote control is accomplished by pressing each button and capturing a key code sent by the remote. Once the key code captured for each key, they are organized into a map that is used to configure LinuxMCE.

===Receiver Hardware===
There are a variety of different infrared (IR) receivers that work with LinuxMCE. Infrared receivers are small pieces of hardware that have an infrared-sensitive "eye" and plug into a computer. Some examples of LinuxMCE compatible IR receivers are [[USB UIRT]], [[Tira]], and [[IRTrans]].

===Receiver Software===
For some IR receivers, the best support is via [http://lirc.org/ LIRC], while for others, purpose-built LinuxMCE drivers are available.

===Learning Is Specific to Combination of Receiver and Remote===
The key code that is captured when a button is pressed depends on both the remote control model ''and'' the receiver model. That is, the key codes that you capture from a [[Windows MCE Remote]] with USB UIRT are different from those captured from the same remote with Tira or IRTrans.

===Adding Support for a New Remote using a USB UIRT Receiver===
''The technique in this section was originally provided in [http://forum.linuxmce.org/index.php?topic=4901.msg28630#msg28630 this forum post].''

To add support for a new remote using USB UIRT as a receiver, perform the steps below. Note that most of the configuration is performed through the Admin Page:

:1. Verify USB UIRT is installed and configured: Once you plug in the USB UIRT it should be plug and play and add both the '''USB UIRT''' device as well as the '''Windows XP MCE Remote (USBUIRT)'''. Go to '''Wizard->devices->media directors'''. Near the bottom of the page you should see the MCE remote listed, with the '''Infrared Receivers''' pulldown set to '''USB UIRT 0038'''.[[Image:DirectorShot.jpg]]

:2. Create a new template for your remote: Go to '''Advanced->Configuration->Device Templates'''.
[[Image:DeviceTemplate.png]]
Select the remote's manufacturer and <tt>USB-UIRT Remote Controls < Remote Controls < Peripherals</tt> from '''Device Category''' then click '''Add Device'''. This will open the '''Add device template window'''. Enter the name or model # of the remote followed by <tt>(USBUIRT)</tt> into the text box and click '''Add'''. Try to be descriptive and unambiguous if you don't have a model number. For example, a good name for the remote that comes bundled with the Hauppauge PVR-150 is <tt>PVR-150 remote (USBUIRT)</tt>. The number of characters allowed is limited, so you'll have to use your judgment to come up with a good name.
[[image:USB UIRT new remote.jpg|right|thumb|128px|screenshot details for steps 3,6 and 7]]

:3. Configure the remote correctly: Go to '''Advanced->Configuration->Device Templates''', find the remote you just added (you may have to refresh your browser to see it), and click the '''Pick Template''' button. This brings up the '''Edit Device Template''' window. Change the '''Device Category''' to '''Peripherals - Remote Controls - USB-UIRT Remote Controls'''. Select the correct manufacturer for your remote.

:4. Get the USB UIRT device ID: From the bottom of the left pane on the Admin Page, click '''Show devices tree'''. In the tree, click '''USB UIRT 0038'''. Find the device number in the title of the '''Device Info''' block. For example, '''Device Info #50''' indicates that the USB UIRT is device #50.

:5. Capture the key codes: In a terminal window, enter the command <code>tail -f /var/log/pluto/XX_USB_UIRT_0038.log</code> where XX is the device number you found in the previous step. Press a button on the remote control twice. You should see something like this:
05 05/16/08 19:29:18.757 Cannot find anything for IR 1500003E3CFC <0x40800950>
05 05/16/08 19:29:19.021 Cannot find anything for IR 1700009E0FC0 <0x40800950>
:The numbers <code>1500003E3CFC</code> and <code>1700009E0FC0</code> are the key codes for that button. If the two numbers are the same, then there is only one key code for that button. In a text editor, format the button names and key codes in the same format as [[#Sample USB UIRT key codes|this]].

:6. Add the Configuration (string): In the '''Device Data''' box select '''Configuration'''. Paste the key codes you created in the last step into the '''Default Value''' field. Click the '''Use Master Device List Defaults''' box.

:7. Add the Remote Layout (String): In the Device Data box, add the new parameter '''Remote Layout (String)'''. In the '''Default Value''' field enter W.

:8. Click '''Save''' then '''Close''' to close the '''Edit Device Template''' window.

:9. Add the remote: Go to '''Wizard->devices->Media Directors''' and scroll to the media director that you want to control with the remote. Click '''Add Remote''' then select the remote template you just created from the '''Device Template''' drop-down. Click '''Pick Template''' and then back on the Media Director page, click '''Update'''. After this you should be prompted to reload the router, if not do a quick reload.

Once the router reloads, you should have a working remote.
[[Image:Example.jpg]]

===Share your Key Codes===
It is helpful to share your key codes with others. See [[Share IR Codes]] for details.

===LIRC===
LinuxMCE's infrared remote control module is based on LIRC. See http://lirc.org/ for details. LIRC includes an 'IR Record' utility to build a configuration file for a new remote control. Once you do that, then in LinuxMCE Admin choose 'Advanced', 'Device Templates'. Choose the manufacturer, for the Category choose Peripherals, Remote Controls, LIRC Remote controls. Type in the model of the remote and click 'add'. Then edit the device, add a device data "Configuration" and copy the LIRC configuration file into it.

The Programming Guide in [[Control LinuxMCE using an Infrared remote]] explains how it all works, and also how to use it.

[[Adding iMON PAD]] explains how to add it to the LinnuxMCE.

===Related Topics===
[[Control LinuxMCE using an Infrared remote]]

[[Infrared Remote Buttons Understood by LinuxMCE]]

[[Share IR Codes]]

[[Adding a New MCE Compatible Transceiver]]

===Sample USB UIRT key codes===
power 170000870FC0 1500003F0FC0
stop 1300000F3FFC 170000F80FC0
record 150000383FFC 170000F80FC0
pause 150000303EFC 170000D00FC0
play 130000093FFC 150000390FC0
rewind 1300000F3EFC 150000370FC0
fastforward 1300000B3FFC 1500003B0FC0
skipback 1300000F37FC 1500003F0DC0
skipfwd 150000212DFC 170000A10BC0
back 170000802DFC 190002400BC0
up 1300000B2EFC 150000330BC0
left 1300000F2EFC 150000370BC0
ok 1300000D37FC 1500003D0DC0
right 150000382EFC 170000D80BC0
down 130000092EFC 150000310BC0
volup 150000302FFC 170000F00BC0
voldn 150000322FFC 170000F20BC0
chup 1500002036FC 170000C00DC0
chdown 1500002236FC 170000C20DC0
mute 170000A029FC 190002500AC0
menu 1500002F29FC 170000AF0AC0
1 1700008228FC 190002010AC0
2 1500002328FC 170000830AC0
3 1700008A28FC 190002050AC0
4 1500002F28FC 1700008F0AC0
5 1500002D28FC 1700008D0AC0
6 1500002B28FC 1700008B0AC0
7 170000A828FC 190002140AC0
8 1500003C29FC 170000BC0AC0
9 1500003E29FC 170000BE0AC0
0 1700008028FC 190002000AC0
red 1500003629FC 170000B60AC0
green 1300000933FC 150000390CC0
yellow 150000343CFC 170000940FC0
blue 1300000E31FC 1500002E0CC0
tv 150000252DFC 170000A50BC0
videos 150000342DFC 170000B40BC0
music 150000362DFC 170000B60BC0
pictures 1300000E2DFC 1500002E0BC0
guide 1500003E2DFC 170000BE0BC0
radio 1500002D29FC 170000AD0AC0
previouschannel 1300000F2FFC 1500003F0BC0
go 1500003E3CFC 1700009E0FC0

File:DirectorShot.jpg

2009-05-22T14:30:36Z

Centove: Screenshot to clarify where to look.

Screenshot to clarify where to look.

Add support for new remote controls

2009-05-22T14:29:51Z

Centove: /* Adding Support for a New Remote using a USB UIRT Receiver */

{| align="right"
| __TOC__
|}
[[Category:Input]]
[[Category:Infrared]]
[[Category:Tutorials]]
===Overview===
In general, adding support for a new remote control is accomplished by pressing each button and capturing a key code sent by the remote. Once the key code captured for each key, they are organized into a map that is used to configure LinuxMCE.

===Receiver Hardware===
There are a variety of different infrared (IR) receivers that work with LinuxMCE. Infrared receivers are small pieces of hardware that have an infrared-sensitive "eye" and plug into a computer. Some examples of LinuxMCE compatible IR receivers are [[USB UIRT]], [[Tira]], and [[IRTrans]].

===Receiver Software===
For some IR receivers, the best support is via [http://lirc.org/ LIRC], while for others, purpose-built LinuxMCE drivers are available.

===Learning Is Specific to Combination of Receiver and Remote===
The key code that is captured when a button is pressed depends on both the remote control model ''and'' the receiver model. That is, the key codes that you capture from a [[Windows MCE Remote]] with USB UIRT are different from those captured from the same remote with Tira or IRTrans.

===Adding Support for a New Remote using a USB UIRT Receiver===
''The technique in this section was originally provided in [http://forum.linuxmce.org/index.php?topic=4901.msg28630#msg28630 this forum post].''

To add support for a new remote using USB UIRT as a receiver, perform the steps below. Note that most of the configuration is performed through the Admin Page:

:1. Verify USB UIRT is installed and configured: Once you plug in the USB UIRT it should be plug and play and add both the '''USB UIRT''' device as well as the '''Windows XP MCE Remote (USBUIRT)'''. Go to '''Wizard->devices->media directors'''. Near the bottom of the page you should see the MCE remote listed, with the '''Infrared Receivers''' pulldown set to '''USB UIRT 0038'''.[[Image:DirectorShot.jpg]]

:2. Create a new template for your remote: Go to '''Advanced->Configuration->Device Templates'''. Select the remote's manufacturer and <tt>USB-UIRT Remote Controls < Remote Controls < Peripherals</tt> from '''Device Category''' then click '''Add Device'''. This will open the '''Add device template window'''. Enter the name or model # of the remote followed by <tt>(USBUIRT)</tt> into the text box and click '''Add'''. Try to be descriptive and unambiguous if you don't have a model number. For example, a good name for the remote that comes bundled with the Hauppauge PVR-150 is <tt>PVR-150 remote (USBUIRT)</tt>. The number of characters allowed is limited, so you'll have to use your judgment to come up with a good name.
[[image:USB UIRT new remote.jpg|right|thumb|128px|screenshot details for steps 3,6 and 7]]

:3. Configure the remote correctly: Go to '''Advanced->Configuration->Device Templates''', find the remote you just added (you may have to refresh your browser to see it), and click the '''Pick Template''' button. This brings up the '''Edit Device Template''' window. Change the '''Device Category''' to '''Peripherals - Remote Controls - USB-UIRT Remote Controls'''. Select the correct manufacturer for your remote.

:4. Get the USB UIRT device ID: From the bottom of the left pane on the Admin Page, click '''Show devices tree'''. In the tree, click '''USB UIRT 0038'''. Find the device number in the title of the '''Device Info''' block. For example, '''Device Info #50''' indicates that the USB UIRT is device #50.

:5. Capture the key codes: In a terminal window, enter the command <code>tail -f /var/log/pluto/XX_USB_UIRT_0038.log</code> where XX is the device number you found in the previous step. Press a button on the remote control twice. You should see something like this:
05 05/16/08 19:29:18.757 Cannot find anything for IR 1500003E3CFC <0x40800950>
05 05/16/08 19:29:19.021 Cannot find anything for IR 1700009E0FC0 <0x40800950>
:The numbers <code>1500003E3CFC</code> and <code>1700009E0FC0</code> are the key codes for that button. If the two numbers are the same, then there is only one key code for that button. In a text editor, format the button names and key codes in the same format as [[#Sample USB UIRT key codes|this]].

:6. Add the Configuration (string): In the '''Device Data''' box select '''Configuration'''. Paste the key codes you created in the last step into the '''Default Value''' field. Click the '''Use Master Device List Defaults''' box.

:7. Add the Remote Layout (String): In the Device Data box, add the new parameter '''Remote Layout (String)'''. In the '''Default Value''' field enter W.

:8. Click '''Save''' then '''Close''' to close the '''Edit Device Template''' window.

:9. Add the remote: Go to '''Wizard->devices->Media Directors''' and scroll to the media director that you want to control with the remote. Click '''Add Remote''' then select the remote template you just created from the '''Device Template''' drop-down. Click '''Pick Template''' and then back on the Media Director page, click '''Update'''. After this you should be prompted to reload the router, if not do a quick reload.

Once the router reloads, you should have a working remote.
[[Image:Example.jpg]]

===Share your Key Codes===
It is helpful to share your key codes with others. See [[Share IR Codes]] for details.

===LIRC===
LinuxMCE's infrared remote control module is based on LIRC. See http://lirc.org/ for details. LIRC includes an 'IR Record' utility to build a configuration file for a new remote control. Once you do that, then in LinuxMCE Admin choose 'Advanced', 'Device Templates'. Choose the manufacturer, for the Category choose Peripherals, Remote Controls, LIRC Remote controls. Type in the model of the remote and click 'add'. Then edit the device, add a device data "Configuration" and copy the LIRC configuration file into it.

The Programming Guide in [[Control LinuxMCE using an Infrared remote]] explains how it all works, and also how to use it.

[[Adding iMON PAD]] explains how to add it to the LinnuxMCE.

===Related Topics===
[[Control LinuxMCE using an Infrared remote]]

[[Infrared Remote Buttons Understood by LinuxMCE]]

[[Share IR Codes]]

[[Adding a New MCE Compatible Transceiver]]

===Sample USB UIRT key codes===
power 170000870FC0 1500003F0FC0
stop 1300000F3FFC 170000F80FC0
record 150000383FFC 170000F80FC0
pause 150000303EFC 170000D00FC0
play 130000093FFC 150000390FC0
rewind 1300000F3EFC 150000370FC0
fastforward 1300000B3FFC 1500003B0FC0
skipback 1300000F37FC 1500003F0DC0
skipfwd 150000212DFC 170000A10BC0
back 170000802DFC 190002400BC0
up 1300000B2EFC 150000330BC0
left 1300000F2EFC 150000370BC0
ok 1300000D37FC 1500003D0DC0
right 150000382EFC 170000D80BC0
down 130000092EFC 150000310BC0
volup 150000302FFC 170000F00BC0
voldn 150000322FFC 170000F20BC0
chup 1500002036FC 170000C00DC0
chdown 1500002236FC 170000C20DC0
mute 170000A029FC 190002500AC0
menu 1500002F29FC 170000AF0AC0
1 1700008228FC 190002010AC0
2 1500002328FC 170000830AC0
3 1700008A28FC 190002050AC0
4 1500002F28FC 1700008F0AC0
5 1500002D28FC 1700008D0AC0
6 1500002B28FC 1700008B0AC0
7 170000A828FC 190002140AC0
8 1500003C29FC 170000BC0AC0
9 1500003E29FC 170000BE0AC0
0 1700008028FC 190002000AC0
red 1500003629FC 170000B60AC0
green 1300000933FC 150000390CC0
yellow 150000343CFC 170000940FC0
blue 1300000E31FC 1500002E0CC0
tv 150000252DFC 170000A50BC0
videos 150000342DFC 170000B40BC0
music 150000362DFC 170000B60BC0
pictures 1300000E2DFC 1500002E0BC0
guide 1500003E2DFC 170000BE0BC0
radio 1500002D29FC 170000AD0AC0
previouschannel 1300000F2FFC 1500003F0BC0
go 1500003E3CFC 1700009E0FC0

LinuxMCE-0810 alpha2

2009-05-22T01:43:45Z

Centove: /* Installation */

{| align="right"
| __TOC__
|}

==Installation==
# Install Kubuntu Intrepid, update it and enable the restricted (video) drivers if needed. (download Kubuntu 8.10 release from one of these: [http://mirrors.ccs.neu.edu/releases.ubuntu.com/kubuntu/8.10/ Northeastern University Mirror, USA], [http://swtsrv.informatik.uni-mannheim.de/pub/linux/distributions/ubuntu-release/kubuntu/8.10/ Mannheim University Mirror, Germany]) '''Currently, only the 32bit version of LinuxMCE is available. Only download the i386 version of 8.10 Kubuntu, even if your system can support 64bit versions.'''
# Run aptitude update and aptitude dist-upgrade to get the latest Kubuntu updates.
# Grab the latest installer script from [http://deb.linuxmce.org/ubuntu here], unpack them and change into the freshly created ''new-installer'' directory.
# Run the following scripts (as root, in order): pre-install-from-repo.sh, mce-install.sh, post-install.sh.
# Reboot, wait for the activity to stop (see progress on console 8).

In other words, after installing Kubuntu and upgrading it etcetera:
sudo su - #This might ask for the password you specified earlier during the install of kubuntu.
wget -c http://deb.linuxmce.org/ubuntu/new-installer-alpha-latest.tar.gz
tar xvf new-installer-alpha-latest.tar.gz
cd new-installer
./pre-install-from-repo.sh
./mce-install.sh
./post-install.sh
reboot
=== nVidia Restricted Driver ===
<strike>Install the nVidia restricted driver (177) from KDE using the Hardware Manager ''before'' installing LinuxMCE 0810 Alpha for the best results</strike>

=== MythTV ===
<strike>Remove reference to hardy in /etc/apt/sources.list

from terminal
<pre>
sudo apt-get install pluto-mythtv-player
</pre>

Install updated version of pluto-mythtv-plugin</strike>

=== Setup Diskless MD ===
<strike>Follow the steps from [[LinuxMCE-0810_alpha1#Setup_Diskless_MD|alpha1]].</strike>

=== Upgrading kernel ===
<strike>There are issues with the ''fglrx'' driver that are documented in Ubuntu's bug tracking system. If you're experiencing those issues, upgrade the kernel to ''2.6.27-13'' or better. [[Upgrading the Kernel]] has been updated with instructions on doing this.</strike> The latest official kernel is -14

== Updates ==
Check if there is no junk like references to hardy in /etc/apt/sources.list then:
sudo apt-get update
sudo apt-get dist-upgrade
Or use a package manager on the KDE desktop for more convenience.

=== 20090218 (alpha-2.1) ===
*lmce-datalog-db_2.0.0.44.0902180810
*lmce-datalogger-plugin_2.0.0.44.0902180810
*lmce-enocean-tcm120_2.0.0.44.0902180810
*lmce-src-datalogger-plugin_2.0.0.44.0902180810
*lmce-src-enocean-tcm120_2.0.0.44.0902180810
*lmce-src-lmce-datalog_2.0.0.44.0902180810
*pluto-dcerouter_2.0.0.44.0902180810
*pluto-dhcpd-plugin_2.0.0.44.0902180810
*pluto-hald-src_2.0.0.44.0902180810
*pluto-hald_2.0.0.44.0902180810
*pluto-mythtv-plugin_2.0.0.44.0902180810
*pluto-orbitergen_2.0.0.44.0902180810
*pluto-src-dcerouter_2.0.0.44.0902180810
*pluto-src-hal-device-finder_2.0.0.44.0902180810
*pluto-src-mythtv-plugin_2.0.0.44.0902180810
*pluto-src-orbitergen_2.0.0.44.0902180810
*pluto-src-updatemedia_2.0.0.44.0902180810
*pluto-updateentarea_2.0.0.44.0902180810
*pluto-updatemedia_2.0.0.44.0902180810
*pluto-zwave-lighting_2.0.0.44.0902180810
*lmce-game-player_2.0.0.44.0902180810
*lmce-game-plugin_2.0.0.44.0902180810
*lmce-src-game-player_2.0.0.44.0902180810
*lmce-src-game-plugin_2.0.0.44.0902180810

==== 20090222 (alpha-2.1.1) ====
*pluto-dcerouter_2.0.0.44.0902220810
*pluto-bluetooth-dongle_2.0.0.44.0902220810

=== 20090301 (alpha-2.2) ===
SVN revision: 21746

To avoid a known problem when upgrading pluto-storage-devices, forcefully remove it before upgrading and let apt fix it:
dpkg -r --force-all pluto-storage-devices
apt-get update
apt-get install -f
Also please note that installing the upgrade of pluto-system-database will OVERWRITE your existing pluto_main database. It is therefore advisable to make a backup first!
mysqldump --skip-extended-insert pluto_main >pluto_main_$PK_Installation-`date '+%Y%m%d:%H%M%S'`.sql
*pluto-boot-scripts_2.0.0.44.0903010810
*pluto-network-storage_2.0.0.44.0903010810
*pluto-skins-basic_2.0.0.44.0903010810
*pluto-src-network-storage_2.0.0.44.0903010810
*pluto-src-std-plugins_2.0.0.44.0903010810
*pluto-src-updatemedia_2.0.0.44.0903010810
*pluto-std-plugins_2.0.0.44.0903010810
*pluto-storage-devices_2.0.0.44.0903010810
*pluto-system-database_2.0.0.44.0903010810
*pluto-updatemedia_2.0.0.44.0903010810
*pluto-website-admin_2.0.0.44.0903010810

=== 20090308 (alpha-2.3) ===
SVN revision: 21765

Again it is wise to backup your database as there is a new pluto-system-database package, but this one will not overwrite your pluto_main database if it is already installed, it should do an sqlCVS update instead.
Also remove the pluto-storage-devices, hopefully for the last time.
See the previous upgrade [[LinuxMCE-0810_alpha2#20090301_.28alpha-2.2.29|above]] for details on how to do these things.

*pluto-asterisk_2.0.0.44.0903080810
*pluto-src-asterisk_2.0.0.44.0903080810
*pluto-src-text-to-speech_2.0.0.44.0903080810
*pluto-src-updatemedia_2.0.0.44.0903080810
*pluto-storage-devices_2.0.0.44.0903080810
*pluto-system-database_2.0.0.44.0903080810
*pluto-text-to-speech_2.0.0.44.0903080810
*pluto-updatemedia_2.0.0.44.0903080810
*pluto-website-admin_2.0.0.44.0903080810

=== 20090315 (alpha-2.4) ===
SVN revision: 21798

The web admin is being moved from pluto-admin to lmce-admin with this build. A redirect has been placed in pluto-admin to redirect to the new web admin URL to help smooth the transition. While every attempt has been made to make this a smooth transition, please be sure to file a trac ticket if you find bugs related to this move so I can get them taken care of - [[User:jondecker76|jondecker76]]

The Asterisk IVR is broken in this release. For those that need to get it working/wish to try out new changes, do the following:
sudo apt-get install libsox-fmt-all
cd /usr/pluto/bin
sudo rm generate_users_voicemenu.pl
sudo wget http://svn.linuxmce.org/trac.cgi/browser/branches/LinuxMCE-0810/src/Asterisk/generate_users_voicemenu.pl?format=raw
sudo chmod 755 generate_users_voicemenu.pl
sudo ./generate_users_voicemenu.pl
Be sure to have the default voice set up in the Text_To_Speech device's device data (its default is the ugly one we're already used to)! I also highly recommend following the instructions located at [http://wiki.linuxmce.org/index.php/Text_To_Speech http://wiki.linuxmce.org/index.php/Text_To_Speech] on how to install some better voices, and set the default voice to voice_nitech_us_slt_arctic_hts after you install the better voices (this is the best free voice available ATM). This should all work on next weeks build for those that can wait.. I'm still working on getting the better voices included by default, but need to check on licensing issues first.

*pluto-asterisk_2.0.0.44.0903150810
*pluto-boot-scripts_2.0.0.44.0903150810
*pluto-makerelease_2.0.0.44.0903150810
*pluto-newmdinteractor_2.0.0.44.0903150810
*pluto-orbitergen_2.0.0.44.0903150810
*pluto-proxy-orbiter_2.0.0.44.0903150810
*pluto-src-asterisk_2.0.0.44.0903150810
*pluto-src-makerelease_2.0.0.44.0903150810
*pluto-src-newmdinteractor_2.0.0.44.0903150810
*pluto-src-orbitergen_2.0.0.44.0903150810
*pluto-src-proxy-orbiter_2.0.0.44.0903150810
*pluto-src-std-plugins_2.0.0.44.0903150810
*pluto-src-text-to-speech_2.0.0.44.0903150810
*pluto-std-plugins_2.0.0.44.0903150810
*pluto-system-database_2.0.0.44.0903150810
*pluto-text-to-speech_2.0.0.44.0903150810
*pluto-updateentarea_2.0.0.44.0903150810
*pluto-website-admin_2.0.0.44.0903150810

=== 20090322 (alpha-2.5) ===
SVN revision: 21827

*freepbx_0+2.3.1-2
*pluto-asterisk_2.0.0.44.0903220810
*pluto-dhcpd-plugin_2.0.0.44.0903220810
*pluto-install-scripts_2.0.0.44.0903220810
*pluto-raid-tools_2.0.0.44.0903220810
*pluto-skins-basic_2.0.0.44.0903220810
*pluto-src-asterisk_2.0.0.44.0903220810
*pluto-website-admin_2.0.0.44.0903220810

=== 20090401 (alpha-2.6) ===
Note: This build will attempt to use Launch Manager to co-ordinate startup and shutdown of devices. While it is not 100% finished, it is working and stable. Please test it out and file any problems against trac ticket #48. Also, please note the following:
I'm not sure on this, but you may have to manually install LM via apt-get
After you upgrade, reboot your core
CLI output of LM can be viewed on tty8 on the core, and tty1 on MD's (alt+ctrl+F8 and alt+ctrl+F1 respectively). You will have to manually switch back to the orbiter on tty7 when finished
CLI output is not yet completely finished, so the top fields will be blank (this is normal for now)
CLI output of the log messages is working however, so please take a peek at them on tty8/tty1 shortly after you hear the 2nd set of beeps on boot up (when the "x" cursor appears on the screen).
You can further test out LM by switching to tty8/tty1 right after doing a router reload and watching the output and comparing it to what you would expect it to be.
LM dos not yet track regen process and report the % done. This should be working in next week's build, however.
If there are problems and/or you wish to restore previous functionality, the original /usr/pluto/bin/startCore.sh file can be restored from the backup /usr/pluto/bin/startCore.sh._backup, and the LM package removed
LM is not yet properly daemonized. I'm saving this step for last after the socket layer is implemented and we get a client coded.
'''Note:''' All orbiters will likely do a FULL REGEN after this update, and it may appear that your system is hanging because of this. Please give it some time to finish the regen (could take up to an hour on large installs)

* lmcevdr_1.1-10_all.deb
* pluto-website-admin_2.0.0.44.0904010019_i386.deb
* pluto-dynamic-dns_2.0.0.44.0904010019_i386.deb
* lmce-launch-manager_2.0.0.44.0904010019_i386.deb
* pluto-boot-scripts_2.0.0.44.0904010019_i386.deb
* pluto-system-database_2.0.0.44.0904010019_i386.deb
* pluto-orbitergen_2.0.0.44.0904010019_i386.deb
* pluto-updateentarea_2.0.0.44.0904010019_i386.deb
* pluto-orbiter_2.0.0.44.0904010019_i386.deb

=== 20090405 (alpha 2.7) ===
From now on, the SVN version will part of the deb name.
You may need to uninstall 'lmcevdr' (dpkg -r --force-all lmcevdr) and reinstall it (apt-get install lmcevdr) to get around the install-script bug in last weeks .deb package. It worked for me.
* lmce-game-player_2.0.0.44.090405.21873_i386.deb
* lmce-game-plugin_2.0.0.44.090405.21873_i386.deb
* lmce-launch-manager_2.0.0.44.090405.21873_i386.deb
* lmce-phoenix-solo-usb_2.0.0.44.090405.21873_i386.deb
* lmcevdr_1.1-10_all.deb (This is no main package, and therefore does not contain the regular version designation. It is based upon version 21875)
* pluto-bluetooth-dongle_2.0.0.44.090405.21873_i386.deb
* pluto-simplephone_2.0.0.44.090405.21873_i386.deb
* pluto-system-database_2.0.0.44.090405.21873_i386.deb
* pluto-website-admin_2.0.0.44.09040521873_i386.deb

=== 20090412 (alpha 2.8) ===
* pluto-text-to-speech_2.0.0.44.09041221886_i386.deb (283,284) - Finally, good voices will actually install (Nitech HTS Arctic).
* pluto-system-database_2.0.0.44.09041221886_i386.deb (211) - New default voice is voice_nitech_us_slt_arctic_hts. - game plugin and player template cleanups
* mce-diskless-tools_2.0.0.44.09041221886_i386.deb (627,628) - Update kernel image for diskless MDs upon regenning.
* pluto-website-admin_2.0.0.44.09041221886_i386.deb (220) - Infrared codes will now properly come from schema.linuxmce.org
* pluto-boot-scripts_2.0.0.44.09041221886_i386.deb (234)- also schema.linuxmce.org IR codes related.
* pluto-motion-wrapper_2.0.0.44.09041221886_i386.deb (455,456) - changed config variable from ffmpeg_filename to movie_filename
* lmce_launch_manager_2.0.0.44.09041221886_i386.deb (298,299) - LM Actions now work from CLI(such as reload, regen, reboot, etc...)
* lmce-game-player_2.0.0.44.09041221886_i386.deb (673,674) - Rebuilt for new device template
* lmce-game-plugin_2.0.0.44.09041221886_i386.deb (671,672) - Rebuilt for new device template
* pluto-updateentarea_2.0.0.44.09041221886_i386.deb (341,342) - may need to be rebuilt for device template changes

=== 20090413 (alpha 2.9 jondecker special) ===
* pluto-text-to-speech_2.0.0.44.09041321887_i386.deb (283,284) - fixes stupid post-install typo
* pluto-zwave-lighting_2.0.0.44.09041321891_i386.deb (505,506) - thermostate support

=== 20090419 (alpha 2.10 pbr) ===
* pluto-text-to-speech_2.0.0.44.09041921897_i386.deb
* pluto-website-admin_2.0.0.44.09041921897_i386.deb
* lmce-screen-capture-camera_2.0.0.44.09041921897_i386.deb
* pluto-system-database_2.0.0.44.09041921897_i386.deb
* lmce-game-plugin_2.0.0.44.09041921897_i386.deb
* lmce-game-player_2.0.0.44.09041921897_i386.deb
* pluto-asterisk_2.0.0.44.09041921897_i386.deb

=== 20090426 (alpha 2.11) ===
With this release, MythTV now takes advantage of storage groups. Do some recordings, and try recording to a few different storage groups.
Please test this out and report any problems such as duplicate attributes appearing in pluto_media, icon image not showing up, recordings failing to record, etc. Also, if you do have problems, try a reboot and see if it fixes the problem, then please let me know if the reboot fixed your problem. - jondecker76

'''POST-BUILD UPDATE:''' A couple of small bugs have been found that will be fixed in next week's build. 1) Some storage groups are missing the leading "/" in the path, causing problems images in mythweb, downloads in the mythweb, etc. 2) Unmounted storage devices were being skipped. This means that you may not have a storage group for some of your devices at some times. I am changing this so that the storage groups are created, and if for some reason it is not available when a recording is set to use the storage group, then the recording will go to the (always present) Default storage group.
For those wanting to fix #1 right now, just edit /usr/pluto/bin/StorageDevices_PlutoDirStructure.sh and add a preceeding slash before the path beginning with 'home/....' on lines 214 and 226. After this modification, MythTV works great in all of the storage groups! (You should do a reboot after making the change)

* lmcevdr_1.1-10_all.deb - more setup fixes, this time for the MD
* pluto-boot-scripts_2.0.0.44.09042621919_i386.deb (234) - small fix to get rid of a warning on DCERouter startup re missing dir., New MythTV directory structure stuff
* pluto-asterisk_2.0.0.44.09042621919_i386.deb (270,271) - Added Support for Cisco 7910 phone
* pluto-dhcpd-plugin_2.0.0.44.09042621919_i386.deb (302) - Added support for Cisco 7910 phone
* pluto-system-database_2.0.0.44.09042621919_i386.deb (211) - '''If new devices are added, the pluto-system-database needs to be updates as well'''
* pluto-storage-devices_2.0.0.44.09042621919_i386.deb (533) - Adds new tv_shows_* directories. Generates MythTV storage groups
* pluto-std-plugins_2.0.0.44.09042621919_i386.deb (134,153) - adds some useful debugging snippets that helped trace down the problem of mythtv attributes not adding to pluto_media
* pluto-mythtv-plugin_2.0.0.44.09042621919_i386.deb (134,153) - lots of changes to facilitate the new storage groups
* pluto-network-storage_2.0.0.44.09042621919_i386.deb (503,508) - small changes to work with new tv_shows_* directories

=== 20090429 (alpha 2.12) ===
* pluto-storage-devices_2.0.0.44.09042921929_i386.deb (533) - Fixes some small bugs in MythTV storage groups
* pluto-boot-scripts_2.0.0.44.09042921929_i386.deb (234) - misc. MythTV storage group enhancements
* pluto-mythtv-plugin_2.0.0.44.09042921929_i386.deb (134,153) - misc. MythTV storage group enhancement
* mce-diskless-tools_2.0.0.44.09042921929_i386.changes (627,628) - lots of fixes for MD boot- Changes effect new installs only
* pluto-system-database_2.0.0.44.09042921929_i386.deb (211) - Fixes hardy issue in sources.list
* pluto-nvidia-video-drivers_2.0.0.44.09042921929_i386.deb (490) - changed the package requirement to nvidia-glx-180 for intrepid

=== 20090501 (alpha 2.13) ===
There are a few more MythTV storage group changes in this build. Please understand that the storage group name changes may throw mythweb out of whack on some old recordings, but this should be minimal. The old "user_*/<storage_device>" naming scheme is replaced with a "<username>:<storage_device>" naming convention. This will appeal to many more users than the user_* convention. Also, there is now support for custom storage groups. You can make your own storage groups now on top of the auto-generated LMCE ones by prepending with "custom:" (for example, you may make a new storage group named "custom:MyDrive", and it will not be removed or overwritten by the scripts that generate the storage groups). One last change is in the "Default" storage group - it no longer points to the drive with most space. This was changed because eventually it would throw mythweb for a loop once the paths changed. I will look into a better way to defaultly record to the drive with most space, most likely using recording profiles.

* lmce-launch-manager (298,299) - db wrapper fix to handle empty resultsets
* pluto-bluetooth-dongle (124,143) - fix some connection issues in JavaMO
* pluto-mythtv-plugin (134,153)
* pluto-storage-devices (533)
* pluto-boot-scripts (234) - MD fixes
* mce-diskless-tools (391) - MD fixes
* pluto-install-scripts (627,628) - MD fixes
* pluto-x-scripts (520,523) - AV Wizard fix for MD
* pluto-zwave-lighting (505,506) - Init speedup

=== 20090503 (alpha2.14) ===
* pluto-zwave-lighting_2.0.0.44.09050321942_i386.deb (505,506) - boolean fixes

=== 20090505 (alpha2.15) ===
KDE on the MD should work now. The first boot of the system after the update will take a bit longer, as stuff that has not worked, is now being executed for the first time.

* mce-diskless-tools_2.0.0.44.09050521951_i386.deb (627,628) - Lots of small fixes
* pluto-system-database_2.0.0.44.09050521951_i386.deb (211) - More hardy extinction
* pluto-boot-scripts_2.0.0.44.09050521951_i386.deb (234) - Small bug with regards to MySQL authorization fixed, which results in a running KDE on the MD, again.

=== 20090505 (alpha2.16 snafu fix) ===
* pluto-boot-scripts_2.0.0.44.09050521958_i386.deb (234) - snafu causing weird things and corruption on updates

=== 20090506 (alpha2.17) ===
* pluto-asterisk_2.0.0.44.09050621962_i386.deb (270,271) - Additional australian provider in the web admin (VoIPWA) and some janitory work.
* pluto-boot-scripts_2.0.0.44.09050621962_i386.deb (234) - Additional visual feedback during the first boot, after running the AV Wizard

=== 20090507 (alpha2.18)===
* pluto-dhcpd-plugin_2.0.0.44.09050721973_i386.deb (302) - Pnp script for Cisco 7910, aastra (aastra still needs a device template)
* lmce-launch-manager_2.0.0.44.09050721973_i386.deb (298,299) - Launch manager is now started in its own screen session
* pluto-system-database_2.0.0.44.09050721973_i386.deb (211) - Removal of X Client Data as a dependency
* pluto-mythtv-plugin_2.0.0.44.09050721973_i386.deb (134,153) - small changes to keep backend in sync
* pluto-storage-devices_2.0.0.44.09050721973_i386.deb (533) - Updates the Default and LiveTV storage groups so they use the drive with most space
* pluto-boot-scripts_2.0.0.44.09050721973_i386.deb (234) - Better detection of Intel Mobile Graphics adapter

=== 20090511 (alpha2.19) ===
* lmcevdr - more VDR configuration settings
* pluto-boot-scripts_2.0.0.44.09051121983_i386.deb (234) - Another KDE Desktop on MD fix
* mce-diskless-tools_2.0.0.44.09051121984_i386.deb (627,628) - Be agnostic about the compression format of tar archives, and more forgiving on download problems

=== 20090515 (alpha2.20) ===
* lmcevdr_1.1-10_all.deb - more VDR configuration settings
* pluto-system-database_2.0.0.44.09051522002_i386.deb (211) - Additional package definitions (vdr-plugin-streamdev-server and vdr-plugin-streamdev-client)
* pluto-hald_2.0.0.44.09051522002_i386.deb (529,530) - USB detection, better MCE2 support
* pluto-vdr-plugin_2.0.0.44.09051522002_i386.deb (466,467) - Additional dependency for pluto-vdr-plugin to vdr-plugin-streamdev-server
* lmce-launch-manager_2.0.0.44.09051522002_i386.deb (298,299) - Prompt user for reload after new MD creation (Requires manual re-run of Diskless_CreateTBZ.sh)
* pluto-orbiter_2.0.0.44.09051522002_i386.deb (119,138) - Prompt user for reload after new MD creation (Requires manual re-run of Diskless_CreateTBZ.sh)
* pluto-storage-devices_2.0.0.44.09051522003_i386.deb (533) - some small MythTV storage group tweaks
* pluto-slim-server-streamer_2.0.0.44.09051522002_i386.deb (289,290) - changes to the configuraton script to start squeezecenter instead of slimserver
* pluto-website-admin_2.0.0.44.09051522002_i386.deb (220) - Screen Saver section fixed
* pluto-plutoutils_2.0.0.44.09051522002_i386.deb (197,196) - fix FileUtils::ReadURL method
* pluto-std-plugins_2.0.0.44.09051522002_i386.deb (116,135) - support for external media in conjunction with playlists

=== 20090520 (alpha2.21) ===
* pluto-website-admin_2.0.0.44.09052022008_i386.deb (220) - GSD/IR code update fixes

=== 20090524 (upcoming ...) ===
* pluto-system-database (211) - More VDR related changes in the package definitions.

== Previous alpha releases ==
* Notes about [[LinuxMCE-0810 alpha1]]
* Notes about [[LinuxMCE-0810 alpha0]]

Control a TV or cable/satellite box

2009-05-22T01:41:46Z

Centove: /* Set to Channel Fix */

[[Category: Tutorials]]
[[Category: Hardware| ]]
[[Category: Programmer's Guide]]

==How to set it up==

In the [[LinuxMCE Admin Website]], go to '''Wizard > Devices > A/V equipment'''. If you haven't already added the TV and whatever cable/satellite box you use for the tuning, click 'Add Device'. Choose the manufacturer, category, and then model of the device. Then click 'Add Device'.

If your model is not in the list, then after choosing the manufacturer and category, type the model name in the box under the models column and click 'Add' to create your own Device Template, which means a definition of a device that explains the properties of this model. Be sure popups are not blocked--a popup window will appear asking how many tuners this TV has (see next paragraph for an explanation). After you add the Device Template for this model, then select it from the model list and click 'Add Device' to add it to your installation. Since this is a new Device Template, on the A/V equipment page be sure to click the 'A/V Properties' button for this device to tell LinuxMCE about this Device Template, such as what inputs it has, whether you will control it with infrared, and so on.

'''Note:''' You will see that a TV is actually treated as multiple devices: the display device, and also a separate device for the tuner(s) inside the TV. This may seem confusing, but it's necessary. Many TV's have multiple tuners, and different tuners may have different video sources; one may be hooked up to cable, and another one to an antenna. And those tuners use different inputs on the TV. Therefore, LinuxMCE treats the tuners as "embedded devices" within the TV. When you want to watch TV, you will actually be telling LinuxMCE you want to use a tuner within the TV. For example, you will say you want to use Tuner #1 (cable), or Tuner #2 (antenna), etc. Therefore when you add a new Device Template for a TV, LinuxMCE Admin will ask how many tuners it has. Receivers are treated the same way since they can also have multiple tuners inside, like FM, AM, Weather Band, Satellite, etc.

On the A/V equipment page you also need to specify the A/V Connections, also known as "Pipes". You can do it using the "Edit" link in the "Pipes" column, or do it graphically by drawing lines between your devices by clicking the "Connection Wizard" link. If you added a cable or satellite box, the video pipe from the box will be the TV that it's connected to, and you choose the input on the TV you used, such as "Video 2". If you want the sound to come out of the TV too, the audio pipe will also go to the TV on the same input. If you want the sound to come out of your receiver, then the audio pipe goes to the receiver. If you're not using an external satellite/cable box, but rather the TV's internal tuner, you'll see that the internal tuner already has an audio/video pipe to the TV. If you don't want the sound to come out of the TV's internal speakers but rather use a stereo receiver, then change the audio pipe for the tuner to go to the receiver instead.

The "Controlled Via" pull-down should be set to whatever device is going to be responsible for controlling this piece of equipment. If this is controlled via infrared the "Controlled Via" device is the infrared device you are using to control it (added on the '''Wizard > Devices > [[Interfaces]]''' page). If this a/v equipment is controllable by RS232 or USB, the Controlled Via should be the PC computer it is connected to. If it is controlled via Ethernet, it can be any computer on which you want to run the device driver, usually it's the Core.

If you have multiple TV sources in your home, such as Cable and Satellite, you may want to click the "Media Providers" link to specify the providers. This step isn't necessary. However if you do add Media Providers, then for each piece of a/v equipment that is a source device you can specify what Media Provider it uses (this box provides "Cable TV" and this "Satellite TV"). The advantage of doing this is that then follow-me media, move media and broadcast are more accurate. If LinuxMCE is able to know that you were watching channel 35 on a device that uses Media Provider "satellite tv", then when the user wants to move or broadcast this media to other rooms, LinuxMCE knows to find devices in those rooms that also use provider "satellite tv". Otherwise LinuxMCE may end up picking a cable tv device instead. If you only have one provider for tv then there is no reason to worry about specifying a provider.

Next go to the '''Wizard > Scenarios > [[Media Scenarios]]''' page. Every media scenario will appear as a button on the Orbiters, so we need to add a media scenario in the room (aka Entertainment Area) where you want to use this TV. Under 'Add Scenario' type the description you want on the button, such as "Live TV", "Cable, etc". Choose the Entertainment Area, or room, then choose the source device. This should be the tuner in the TV, or a satellite or cable box. Also choose the type of media, "Live TV" in this case. If there is more than one remote control interface that will wok with this device you'll have a pull-down for that too. The next time you regen the UI for this Orbiter (see '''Wizard > Devices > [[Orbiters]]'''), the button will appear.

After you add new devices, you need to go to '''Wizard > [[Restart]]''' and click "Quick Reload Router" so DCERouter starts using the new devices you just added.

==How to use it==

Just touch the button you created with the Media Scenarios above. It will appear on all the Orbiters for the room (Entertainment Area) you added it to. LinuxMCE will automatically turn on all the appropriate devices and set their inputs based on the A/V connections you specified in LinuxMCE Admin.

If the A/V equipment is controlled in some way that LinuxMCE can get feedback from it, such as RS232 or Ethernet, then you can also physically turn on or adjust any relevant device and LinuxMCE will figure out automatically what you want to do. For example, if you turn on the satellite box by hand, LinuxMCE knows you want to use it and will automatically turn on the tv and receiver, set the inputs, and put the remote control on the orbiters for you. Or, if you switch the input on the receiver to "DBS", which your satellite box is connected, LinuxMCE also knows that means you want to watch Satellite TV and will set everything up for you. However this functionality is not possible with a/v equipment that is controlled via infrared since i/r is 1-way communication; LinuxMCE can only send it commands, but has no way to know when you are controlling it manually.

==Programmer's guide==

The Media Scenario will send a "MH Play Media" command to the media plugin. The media plugin will then find a media handler plugin that knows how to handle that type of media. Tightly integrated media devices, like Xine or Myth, have their own media handler plugins that are intelligent and know how to do things like synchronize multiple rooms to the same media, move media between rooms and respect stopping/starting at the same place and so on. Generic A/V devices like TV's and satellite boxes are nearly always by the media handler "Generic NonLinuxMCE Media", which is built into the media plugin itself. This media handler is very simple--it just forwards the command to the device.

When a device gets an "ON" command, DCERouter router calls the function "HandleCommandPipes". This is what knows how to turn on all the devices and set their inputs based on the a/v pipes you specified on the a/v equipment page. This is also why the tuners need to be treated as separate embedded devices within the TV, since each one will use different inputs.

The table MediaType_DesignObj has the standard remote controls for each type of Media, and the table DeviceTemplate_MediaType_DesignObj has custom remote controls more appropriate for a given device. When adding the media scenario if there is more than 1 remote control that can be used to control this type of media on this device, the user can choose from the list.

The message translation class is used within the infrared devices (like gc100), and within [[GSD]] (generic serial device) to translate commands and handle things like toggle vs discrete inputs. Devices which are controlled using GSD and a serial/ethernet interface will fire events AV_Input_Changed and Device_OnOff which Media_Plugin has interceptors for and will use the a/v pipes to figure out what device you're trying to use.

==Set to Channel Fix==
Setting the "Preset tuner to channel" in the "Input connections" screen may not cause MythTV to actually tune to that preset channel.

It may be necessary to type the following in a terminal window (this will tune to channel "3"- change as needed):
ivtv-tune -c 3 -d /dev/video0

For more details look on the [http://www.mythtv.org/wiki/Using_an_IR_Blaster_with_MythTV MythTV Wiki]