LinuxMCE - User contributions [en]

RaspberryPi

2016-01-15T20:38:20Z

Esperanto: /* Setup Steps */ ssh remark

[[Category: Hardware]]
[[Category: Media Directors]]
[[Category: Barebones]]
qMDs are still a thing of myth, although seen occasionally in the wild they are elusive and not easily tamed. ;)

=Device Specification=
*The Raspberry Pi 2 B is an ARM based computer the size of a credit card. 4x900Mhz Cores, 1GB RAM, FastEthernet, 4xUSB, 40xGPIO
*The Raspberry Pi B is an ARM based computer the size of a credit card. 1x700Mhz Core, 256MB or 512MB RAM, FastEthernet, 2xUSB, GPIO

=RPi Disked Media Director=

==Requirements==
* Your core must be LinuxMCE 1204 or higher.
* The recommended device is the RPi2. The RPi2 runs at a reasonable speed and can support all the functions of a LinuxMCE MediaDirector.
* The following Raspbian based SD cards are bootable on anything that is a Raspberry Pi Model B or higher. RPi1 performance is very, very, very slow.

==Setup Steps==
*Download the rpi uSD card image ([http://download.linuxmce.org/lmce-disked-md-rpi2-jessie.tar.xz raspbian jessie (recommended)] (Updated: 2015-12-23)
*Download the rpi uSD card image ([http://download.linuxmce.org/lmce-disked-md-rpi2-wheezy.tar.xz raspbian wheezy (deprecated)]
*Download the rpi uSD card image ([http://download.linuxmce.org/lmce-disked-md-rpi2-trusty.tar.xz ubuntu trusty(RPi2 only and you're on your own here)])
*untar the compressed file (e.g. tar -xvJf lmce-disked-md-rpi2-jessie.tar.xz)
*Install the resulting image onto an SD card, using dd on linux ( e.g. sudo dd bs=4M if=2015-12-23-raspbian-jessie.img of=/dev/sdb [make sure device name is correct!]) or win32diskimage on windows
*Ensure the RPi is connected to the internal lan of your core and boot the RPi.
*You may be prompted on existing orbiters to choose a device type MD/qMD/SqueezeOnly, do so. (qMD is not working yet)
*The device will automatically be created, you will need to reload your router.
*The MD will resize the filesystem to fit the SDCard and then reboot.
*AVWizard will not appear.
*You should see the setup wizard and be asked to configure your new MD.
*The new RPi moonpi should continue installing and eventually present you with a UI1 OnScreen Orbiter.
*Please report any bugs with *very* specific (package date/svn, etc) information in a ticket.

If you have any issues you can ssh to the rpi with: ssh moonXX -c aes128-ctr (replace the XX with the device number. you currently have to specify the cipher https://git.linuxmce.org/linuxmce/linuxmce/issues/2451 )

==HDMI-CEC Control==
Please see [[Pulse-Eight]] for HDMI-CEC setup information

==Manual Settings==
*Overscan - currently only able to change by manually editing the config.txt file on the sdcard. (See [http://elinux.org/RPiconfig http://elinux.org/RPiconfig])
*Overscan compensation - currently only able to change by manually editing the config.txt file on the sdcard. In /sdcard/config.txt from a booted moonpi. (See [http://elinux.org/RPiconfig http://elinux.org/RPiconfig])
*Orbiter will automatically regenerate following a reboot and detecting a new display resolution.
*Audio settings are adjusted in webadmin: S = Stereo, H = HDMI, H3 = HDMI with passthrough capability for AC3 & DTS

==What works==
*Orbiter UI1
*Photo Screen Saver (need to disable on RPi1)
*AppServer
*HAL
*Embedded phone
*OMX_Player will play audio and video. You must have the appropriate codecs to play MPG and VC1 media. The codecs can be purchased from the Raspberry Pi foundation.
*squeezelite can play audio
*USB-UIRT
*HDMI-CEC control
*Generic Serial Devices (only on RPi2)

==What does not work==
*Video Overlays

= RPi2 Core =
This section is meant for informational purposes only and is not intended to suggest that the RaspberryPi2 would make a good core. There is NO support for this.

*Download an Ubuntu Trusty Tahr 14.04 image for the RPi2 from [http://www.finnie.org/software/raspberrypi/2015-04-06-ubuntu-trusty.zip http://www.finnie.org/software/raspberrypi/2015-04-06-ubuntu-trusty.zip].
*Unzip it and write it to an sdcard.
*Boot and resize the filesystem to fill the sdcard:
**There are no Raspbian-specific utilities included, specifically no automatic root resizer. However, it's not hard to do manually. Once booted:
$ sudo fdisk /dev/mmcblk0
**Delete the second partition (d, 2), then re-create it using the defaults (n, p, 2, enter, enter), then write and exit (w). Reboot the system, then:
$ sudo resize2fs /dev/mmcblk0p2
*Add the following linuxmce repo's to your /etc/apt/sources.list:
deb http://deb.linuxmce.org/ubuntu/ trusty main
deb http://deb.linuxmce.org/ trusty main
*Run:
apt-get update && DEBIAN_FRONTEND="noninteractive" apt-get install -y --allow-unauthenticated lmce-core
*reboot
*Feel free to play. This is not, and will never be, supported.

=RPi1 (obsolete) =
NOTE: The RPi1 is no longer supported as a LinuxMCE Diskless style device. If you wish to continue working on RPi1 support please contact us.

The Raspberry Pi v1 B/B+ will not be supported for much longer, but can be used as a minimal diskless Media Director within LinuxMCE. The following instructions will show how to create a diskless MD. The Raspberry Pi 2 is not compatible with the PXE method of booting.

When using the sdcard below the RPi will be overclocked using the standard Raspberry Pi foundation overclock settings. These are throttled automatically as thermally required. You are free to overclock the device further by editing the config.txt file on the sdcard.

==Requirements==
* Your core must be LinuxMCE 1204 or higher.
* The Raspberry Pi must be a 512MB Model B (or B+). The Model A and the 256MB Model B do not have enough RAM to boot into Orbiter.
* The Raspberry Pi must be plugged into the internal side of your LinuxMCE core's network to act as a media director.
* The Raspberry Pi must be plugged in using the HDMI connector<del> and using HDMI sound</del>. Set an S (for Stereo) or H (for HDMI) for the Audio Settings for the MD in webadmin.
** The Raspberry Pi will detect the boot resolution of your television and adjust itself accordingly.
** If resolution has changed since the last boot the orbiter will be regenerated.
* You may wish to have a usb keyboard or mouse for orbiter interaction. USB-UIRT/MCE Remote is also possible but must be installed using the webadmin (device detection is working but the device is not added currently).

==Setup Steps==
*On the Core:
**Install the [http://www.linuxmce.org/linux-image-default-raspbian-wheezy_3.10-3-rpi-lmce1_all.deb default PXE kernel package (lmce1)] for a Raspberry Pi MD. This image will create an RPi MD (DT#2216) only.
**-- To be able to choose betwen an RPi MD and an RPi qMD (as well as other possible rpi Device Templates) at MD creation use [http://www.linuxmce.org/linux-image-default-raspbian-wheezy_3.10-3-rpi-lmce2_all.deb this (lmce2)] as the default image instead. This image will allow you to choose from multiple RPi based image including RPi MD (DT#2216), RPi qMD (DT#2281) and others.
**edit /usr/pluto/bin/Diskless_CreateTBZ.sh and enable "raspbian_armhf" as the only TARGET_TYPE, be sure to comment (use a #) any other TARGET_TYPE lines so that only this one is enabled.
**run /usr/pluto/bin/Diskless_CreateTBZ.sh to create a raspbian tarball<del>, and sdcard.zip file on your core</del>.

*Get the LinuxMCE Raspberry Pi MD SD card contents.
**Download the [http://www.linuxmce.org/sdcard.zip zip]
***Format the SD card for VFAT using the SD card formatter for Mac or Windows https://www.sdcard.org/downloads/formatter_4, or using mkfs.vfat on linux.
***Copy the entire contents of the sdcard zip to the newly formatted SD card, all files should be in the root directory of the card with no sub-directories.
*Insert the SD card into the Raspberry Pi.
*Power up the Raspberry Pi.
*On first boot the u-boot bootloader will start, it will try to grab various different pxe files until it finally finds the default PXE kernel and initrd.
*The kernel will boot, there is a 10 second delay when activating the ethernet drivers to allow for the hardware to respond properly, this delay only occurs during the default kernel/initrd boot.
*Raspberry Pi will display "Announced ourselves to the router".
**If you have the lmce1 default image installed (see above,) the core will run Diskless_Setup to prepare an RPi MD.
**If you have the lmce2 default image installed (see above,) you will be prompted on existing orbiters to select the type of RPi device you would like installed. Once you have made your selection the core will run Diskless_Setup to prepare the device.
*The Raspberry Pi will reboot automatically once Diskless_Setup completes properly.
*You should go to an existing orbiter and 'Reload the Router' after this point. You will be prompted to do so eventually on the moonPi, if you have not already done so.
*On the second boot (called the 'FIRSTRUN') the bootloader on the sdcard will be updated to the version on the diskless image.
*The Raspberry Pi will reboot again.
*On the third boot LinuxMCE will slowly come to life. Please be patient, this can take up to 45 minutes. You will be presented with the Setup Wizard after ConfirmDependencies has finished installing all ancillary packages.

RaspberryPi

2016-01-14T19:26:09Z

Esperanto: /* Setup Steps */

[[Category: Hardware]]
[[Category: Media Directors]]
[[Category: Barebones]]
qMDs are still a thing of myth, although seen occasionally in the wild they are elusive and not easily tamed. ;)

=Device Specification=
*The Raspberry Pi 2 B is an ARM based computer the size of a credit card. 4x900Mhz Cores, 1GB RAM, FastEthernet, 4xUSB, 40xGPIO
*The Raspberry Pi B is an ARM based computer the size of a credit card. 1x700Mhz Core, 256MB or 512MB RAM, FastEthernet, 2xUSB, GPIO

=RPi Disked Media Director=

==Requirements==
* Your core must be LinuxMCE 1204 or higher.
* The recommended device is the RPi2. The RPi2 runs at a reasonable speed and can support all the functions of a LinuxMCE MediaDirector.
* The following Raspbian based SD cards are bootable on anything that is a Raspberry Pi Model B or higher. RPi1 performance is very, very, very slow.

==Setup Steps==
*Download the rpi uSD card image ([http://download.linuxmce.org/lmce-disked-md-rpi2-jessie.tar.xz raspbian jessie (recommended)] (Updated: 2015-12-23)
*Download the rpi uSD card image ([http://download.linuxmce.org/lmce-disked-md-rpi2-wheezy.tar.xz raspbian wheezy (deprecated)]
*Download the rpi uSD card image ([http://download.linuxmce.org/lmce-disked-md-rpi2-trusty.tar.xz ubuntu trusty(RPi2 only and you're on your own here)])
*untar the compressed file (e.g. tar -xvJf lmce-disked-md-rpi2-jessie.tar.xz)
*Install the resulting image onto an SD card, using dd on linux ( e.g. sudo dd bs=4M if=2015-12-23-raspbian-jessie.img of=/dev/sdb [make sure device name is correct!]) or win32diskimage on windows
*Ensure the RPi is connected to the internal lan of your core and boot the RPi.
*You may be prompted on existing orbiters to choose a device type MD/qMD/SqueezeOnly, do so. (qMD is not working yet)
*The device will automatically be created, you will need to reload your router.
*The MD will resize the filesystem to fit the SDCard and then reboot.
*AVWizard will not appear.
*You should see the setup wizard and be asked to configure your new MD.
*The new RPi moonpi should continue installing and eventually present you with a UI1 OnScreen Orbiter.
*Please report any bugs with *very* specific (package date/svn, etc) information in a ticket.

==HDMI-CEC Control==
Please see [[Pulse-Eight]] for HDMI-CEC setup information

==Manual Settings==
*Overscan - currently only able to change by manually editing the config.txt file on the sdcard. (See [http://elinux.org/RPiconfig http://elinux.org/RPiconfig])
*Overscan compensation - currently only able to change by manually editing the config.txt file on the sdcard. In /sdcard/config.txt from a booted moonpi. (See [http://elinux.org/RPiconfig http://elinux.org/RPiconfig])
*Orbiter will automatically regenerate following a reboot and detecting a new display resolution.
*Audio settings are adjusted in webadmin: S = Stereo, H = HDMI, H3 = HDMI with passthrough capability for AC3 & DTS

==What works==
*Orbiter UI1
*Photo Screen Saver (need to disable on RPi1)
*AppServer
*HAL
*Embedded phone
*OMX_Player will play audio and video. You must have the appropriate codecs to play MPG and VC1 media. The codecs can be purchased from the Raspberry Pi foundation.
*squeezelite can play audio
*USB-UIRT
*HDMI-CEC control
*Generic Serial Devices (only on RPi2)

==What does not work==
*Video Overlays

= RPi2 Core =
This section is meant for informational purposes only and is not intended to suggest that the RaspberryPi2 would make a good core. There is NO support for this.

*Download an Ubuntu Trusty Tahr 14.04 image for the RPi2 from [http://www.finnie.org/software/raspberrypi/2015-04-06-ubuntu-trusty.zip http://www.finnie.org/software/raspberrypi/2015-04-06-ubuntu-trusty.zip].
*Unzip it and write it to an sdcard.
*Boot and resize the filesystem to fill the sdcard:
**There are no Raspbian-specific utilities included, specifically no automatic root resizer. However, it's not hard to do manually. Once booted:
$ sudo fdisk /dev/mmcblk0
**Delete the second partition (d, 2), then re-create it using the defaults (n, p, 2, enter, enter), then write and exit (w). Reboot the system, then:
$ sudo resize2fs /dev/mmcblk0p2
*Add the following linuxmce repo's to your /etc/apt/sources.list:
deb http://deb.linuxmce.org/ubuntu/ trusty main
deb http://deb.linuxmce.org/ trusty main
*Run:
apt-get update && DEBIAN_FRONTEND="noninteractive" apt-get install -y --allow-unauthenticated lmce-core
*reboot
*Feel free to play. This is not, and will never be, supported.

=RPi1 (obsolete) =
NOTE: The RPi1 is no longer supported as a LinuxMCE Diskless style device. If you wish to continue working on RPi1 support please contact us.

The Raspberry Pi v1 B/B+ will not be supported for much longer, but can be used as a minimal diskless Media Director within LinuxMCE. The following instructions will show how to create a diskless MD. The Raspberry Pi 2 is not compatible with the PXE method of booting.

When using the sdcard below the RPi will be overclocked using the standard Raspberry Pi foundation overclock settings. These are throttled automatically as thermally required. You are free to overclock the device further by editing the config.txt file on the sdcard.

==Requirements==
* Your core must be LinuxMCE 1204 or higher.
* The Raspberry Pi must be a 512MB Model B (or B+). The Model A and the 256MB Model B do not have enough RAM to boot into Orbiter.
* The Raspberry Pi must be plugged into the internal side of your LinuxMCE core's network to act as a media director.
* The Raspberry Pi must be plugged in using the HDMI connector<del> and using HDMI sound</del>. Set an S (for Stereo) or H (for HDMI) for the Audio Settings for the MD in webadmin.
** The Raspberry Pi will detect the boot resolution of your television and adjust itself accordingly.
** If resolution has changed since the last boot the orbiter will be regenerated.
* You may wish to have a usb keyboard or mouse for orbiter interaction. USB-UIRT/MCE Remote is also possible but must be installed using the webadmin (device detection is working but the device is not added currently).

==Setup Steps==
*On the Core:
**Install the [http://www.linuxmce.org/linux-image-default-raspbian-wheezy_3.10-3-rpi-lmce1_all.deb default PXE kernel package (lmce1)] for a Raspberry Pi MD. This image will create an RPi MD (DT#2216) only.
**-- To be able to choose betwen an RPi MD and an RPi qMD (as well as other possible rpi Device Templates) at MD creation use [http://www.linuxmce.org/linux-image-default-raspbian-wheezy_3.10-3-rpi-lmce2_all.deb this (lmce2)] as the default image instead. This image will allow you to choose from multiple RPi based image including RPi MD (DT#2216), RPi qMD (DT#2281) and others.
**edit /usr/pluto/bin/Diskless_CreateTBZ.sh and enable "raspbian_armhf" as the only TARGET_TYPE, be sure to comment (use a #) any other TARGET_TYPE lines so that only this one is enabled.
**run /usr/pluto/bin/Diskless_CreateTBZ.sh to create a raspbian tarball<del>, and sdcard.zip file on your core</del>.

*Get the LinuxMCE Raspberry Pi MD SD card contents.
**Download the [http://www.linuxmce.org/sdcard.zip zip]
***Format the SD card for VFAT using the SD card formatter for Mac or Windows https://www.sdcard.org/downloads/formatter_4, or using mkfs.vfat on linux.
***Copy the entire contents of the sdcard zip to the newly formatted SD card, all files should be in the root directory of the card with no sub-directories.
*Insert the SD card into the Raspberry Pi.
*Power up the Raspberry Pi.
*On first boot the u-boot bootloader will start, it will try to grab various different pxe files until it finally finds the default PXE kernel and initrd.
*The kernel will boot, there is a 10 second delay when activating the ethernet drivers to allow for the hardware to respond properly, this delay only occurs during the default kernel/initrd boot.
*Raspberry Pi will display "Announced ourselves to the router".
**If you have the lmce1 default image installed (see above,) the core will run Diskless_Setup to prepare an RPi MD.
**If you have the lmce2 default image installed (see above,) you will be prompted on existing orbiters to select the type of RPi device you would like installed. Once you have made your selection the core will run Diskless_Setup to prepare the device.
*The Raspberry Pi will reboot automatically once Diskless_Setup completes properly.
*You should go to an existing orbiter and 'Reload the Router' after this point. You will be prompted to do so eventually on the moonPi, if you have not already done so.
*On the second boot (called the 'FIRSTRUN') the bootloader on the sdcard will be updated to the version on the diskless image.
*The Raspberry Pi will reboot again.
*On the third boot LinuxMCE will slowly come to life. Please be patient, this can take up to 45 minutes. You will be presented with the Setup Wizard after ConfirmDependencies has finished installing all ancillary packages.

Kmx3

2014-11-13T14:49:40Z

Esperanto: kmx3 xev codes

= KMX3 =
2.4Ghz Wireless Air Fly Mouse Keyboard Remote Control For Android TV Box MX3

http://www.ebay.com/itm/2-4Ghz-Wireless-Air-Fly-Mouse-Keyboard-Remote-Control-For-Android-TV-Box-MX3-/111297791678

== dmesg ==
[321010.916163] usb 1-1.1: new full-speed USB device number 4 using ehci-pci
[321011.018927] usb 1-1.1: New USB device found, idVendor=0c45, idProduct=2702
[321011.018931] usb 1-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[321011.018933] usb 1-1.1: Product: 2.4G Wireless Device
[321011.018934] usb 1-1.1: Manufacturer: 2.4G
[321011.047235] input: 2.4G 2.4G Wireless Device as /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.1/1-1.1:1.2/input/input12
[321011.048214] hid-generic 0003:0C45:2702.0003: input,hiddev0,hidraw0: USB HID v1.10 Mouse [2.4G 2.4G Wireless Device] on usb-0000:00:1a.0-1.1/input2
[321011.048499] input: 2.4G 2.4G Wireless Device as /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.1/1-1.1:1.3/input/input13
[321011.048641] hid-generic 0003:0C45:2702.0004: input,hidraw1: USB HID v1.10 Keyboard [2.4G 2.4G Wireless Device] on usb-0000:00:1a.0-1.1/input3
[321011.053389] cannot find the slot for index 1 (range 0-1), error: -16
[321011.053392] cannot create card instance 0
[321011.053396] snd-usb-audio: probe of 1-1.1:1.0 failed with error -5
[321011.053411] usbcore: registered new interface driver snd-usb-audio

== lsusb ==
Bus 001 Device 004: ID 0c45:2702 Microdia

== xev output ==

|<<
KeyPress event, serial 31, synthetic NO, window 0x5a00001,
root 0x209, subw 0x0, time 324316296, (335,437), root:(1206,879),
state 0x0, keycode 173 (keysym 0x1008ff16, XF86AudioPrev), same_screen YES,
XLookupString gives 0 bytes:
XmbLookupString gives 0 bytes:
XFilterEvent returns: False

KeyRelease event, serial 34, synthetic NO, window 0x5a00001,
root 0x209, subw 0x0, time 324316498, (335,437), root:(1206,879),
state 0x0, keycode 173 (keysym 0x1008ff16, XF86AudioPrev), same_screen YES,
XLookupString gives 0 bytes:
XFilterEvent returns: False

>>|
KeyPress event, serial 34, synthetic NO, window 0x5a00001,
root 0x209, subw 0x0, time 324318094, (340,449), root:(1211,891),
state 0x0, keycode 171 (keysym 0x1008ff17, XF86AudioNext), same_screen YES,
XLookupString gives 0 bytes:
XmbLookupString gives 0 bytes:
XFilterEvent returns: False

KeyRelease event, serial 34, synthetic NO, window 0x5a00001,
root 0x209, subw 0x0, time 324318296, (340,449), root:(1211,891),
state 0x0, keycode 171 (keysym 0x1008ff17, XF86AudioNext), same_screen YES,
XLookupString gives 0 bytes:
XFilterEvent returns: False

PG+
KeyPress event, serial 31, synthetic NO, window 0x5a00001,
root 0x209, subw 0x0, time 324385642, (-871,397), root:(0,839),
state 0x0, keycode 112 (keysym 0xff55, Prior), same_screen YES,
XLookupString gives 0 bytes:
XmbLookupString gives 0 bytes:
XFilterEvent returns: False

KeyRelease event, serial 34, synthetic NO, window 0x5a00001,
root 0x209, subw 0x0, time 324385750, (-870,402), root:(1,844),
state 0x0, keycode 112 (keysym 0xff55, Prior), same_screen YES,
XLookupString gives 0 bytes:
XFilterEvent returns: False

PG-
KeyPress event, serial 34, synthetic NO, window 0x5a00001,
root 0x209, subw 0x0, time 324387021, (-854,369), root:(17,811),
state 0x0, keycode 117 (keysym 0xff56, Next), same_screen YES,
XLookupString gives 0 bytes:
XmbLookupString gives 0 bytes:
XFilterEvent returns: False

KeyRelease event, serial 34, synthetic NO, window 0x5a00001,
root 0x209, subw 0x0, time 324387207, (-868,360), root:(3,802),
state 0x0, keycode 117 (keysym 0xff56, Next), same_screen YES,
XLookupString gives 0 bytes:
XFilterEvent returns: False

MUTE:
FocusOut event, serial 34, synthetic NO, window 0x5a00001,
mode NotifyGrab, detail NotifyAncestor

FocusIn event, serial 34, synthetic NO, window 0x5a00001,
mode NotifyUngrab, detail NotifyAncestor

KeymapNotify event, serial 34, synthetic NO, window 0x0,
keys: 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 2
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

KeyRelease event, serial 34, synthetic NO, window 0x5a00001,
root 0x209, subw 0x0, time 324450254, (-740,-144), root:(131,298),
state 0x0, keycode 121 (keysym 0x1008ff12, XF86AudioMute), same_screen YES,
XLookupString gives 0 bytes:
XFilterEvent returns: False

SEARCH:
KeyPress event, serial 34, synthetic NO, window 0x5a00001,
root 0x209, subw 0x0, time 324507875, (-390,239), root:(481,681),
state 0x0, keycode 69 (keysym 0xffc0, F3), same_screen YES,
XLookupString gives 0 bytes:
XmbLookupString gives 0 bytes:
XFilterEvent returns: False

KeyRelease event, serial 34, synthetic NO, window 0x5a00001,
root 0x209, subw 0x0, time 324508076, (-390,233), root:(481,675),
state 0x0, keycode 69 (keysym 0xffc0, F3), same_screen YES,
XLookupString gives 0 bytes:
XFilterEvent returns: False

DEL:
KeyPress event, serial 34, synthetic NO, window 0x5a00001,
root 0x209, subw 0x0, time 324533944, (827,471), root:(1698,913),
state 0x0, keycode 22 (keysym 0xff08, BackSpace), same_screen YES,
XLookupString gives 1 bytes: (08) "
XmbLookupString gives 1 bytes: (08) "
XFilterEvent returns: False

KeyRelease event, serial 34, synthetic NO, window 0x5a00001,
root 0x209, subw 0x0, time 324534178, (827,471), root:(1698,913),
state 0x0, keycode 22 (keysym 0xff08, BackSpace), same_screen YES,
XLookupString gives 1 bytes: (08) "
XFilterEvent returns: False

!:
KeyPress event, serial 34, synthetic NO, window 0x5a00001,
root 0x209, subw 0x0, time 324563973, (827,471), root:(1698,913),
state 0x0, keycode 248 (keysym 0x0, NoSymbol), same_screen YES,
XLookupString gives 0 bytes:
XmbLookupString gives 0 bytes:
XFilterEvent returns: False

KeyRelease event, serial 34, synthetic NO, window 0x5a00001,
root 0x209, subw 0x0, time 324564100, (827,471), root:(1698,913),
state 0x0, keycode 248 (keysym 0x0, NoSymbol), same_screen YES,
XLookupString gives 0 bytes:
XFilterEvent returns: False

VIDEO:
KeyPress event, serial 34, synthetic NO, window 0x5a00001,
root 0x209, subw 0x0, time 324592004, (827,471), root:(1698,913),
state 0x0, keycode 179 (keysym 0x1008ff81, XF86Tools), same_screen YES,
XLookupString gives 0 bytes:
XmbLookupString gives 0 bytes:
XFilterEvent returns: False

KeyRelease event, serial 34, synthetic NO, window 0x5a00001,
root 0x209, subw 0x0, time 324592124, (827,471), root:(1698,913),
state 0x0, keycode 179 (keysym 0x1008ff81, XF86Tools), same_screen YES,
XLookupString gives 0 bytes:
XFilterEvent returns: False

WINDOWS:
KeyPress event, serial 34, synthetic NO, window 0x5a00001,
root 0x209, subw 0x0, time 324921384, (931,297), root:(1802,739),
state 0x0, keycode 68 (keysym 0xffbf, F2), same_screen YES,
XLookupString gives 0 bytes:
XmbLookupString gives 0 bytes:
XFilterEvent returns: False

KeyRelease event, serial 34, synthetic NO, window 0x5a00001,
root 0x209, subw 0x0, time 324921569, (923,294), root:(1794,736),
state 0x0, keycode 68 (keysym 0xffbf, F2), same_screen YES,
XLookupString gives 0 bytes:
XFilterEvent returns: False

PLAY/PAUSE:
KeyPress event, serial 34, synthetic NO, window 0x5a00001,
root 0x209, subw 0x0, time 324731366, (835,470), root:(1706,912),
state 0x0, keycode 172 (keysym 0x1008ff14, XF86AudioPlay), same_screen YES,
XLookupString gives 0 bytes:
XmbLookupString gives 0 bytes:
XFilterEvent returns: False

KeyRelease event, serial 34, synthetic NO, window 0x5a00001,
root 0x209, subw 0x0, time 324731447, (820,469), root:(1691,911),
state 0x0, keycode 172 (keysym 0x1008ff14, XF86AudioPlay), same_screen YES,
XLookupString gives 0 bytes:
XFilterEvent returns: False

UP/RIGHT/DOWN/LEFT:

KeyPress event, serial 34, synthetic NO, window 0x5a00001,
root 0x209, subw 0x5a00002, time 325176788, (42,13), root:(859,571),
state 0x0, keycode 116 (keysym 0xff54, Down), same_screen YES,
XLookupString gives 0 bytes:
XmbLookupString gives 0 bytes:
XFilterEvent returns: False

KeyRelease event, serial 34, synthetic NO, window 0x5a00001,
root 0x209, subw 0x5a00002, time 325176943, (42,13), root:(859,571),
state 0x0, keycode 116 (keysym 0xff54, Down), same_screen YES,
XLookupString gives 0 bytes:
XFilterEvent returns: False

KeyPress event, serial 34, synthetic NO, window 0x5a00001,
root 0x209, subw 0x0, time 325381821, (0,16), root:(871,458),
state 0x0, keycode 114 (keysym 0xff53, Right), same_screen YES,
XLookupString gives 0 bytes:
XmbLookupString gives 0 bytes:
XFilterEvent returns: False

KeyRelease event, serial 34, synthetic NO, window 0x5a00001,
root 0x209, subw 0x0, time 325382038, (-13,23), root:(858,465),
state 0x0, keycode 114 (keysym 0xff53, Right), same_screen YES,
XLookupString gives 0 bytes:
XFilterEvent returns: False

KeyPress event, serial 34, synthetic NO, window 0x5a00001,
root 0x209, subw 0x5a00002, time 325241274, (42,13), root:(859,571),
state 0x0, keycode 111 (keysym 0xff52, Up), same_screen YES,
XLookupString gives 0 bytes:
XmbLookupString gives 0 bytes:
XFilterEvent returns: False

KeyRelease event, serial 34, synthetic NO, window 0x5a00001,
root 0x209, subw 0x5a00002, time 325241524, (42,13), root:(859,571),
state 0x0, keycode 111 (keysym 0xff52, Up), same_screen YES,
XLookupString gives 0 bytes:
XFilterEvent returns: False

KeyPress event, serial 34, synthetic NO, window 0x5a00001,
root 0x209, subw 0x0, time 325416950, (-871,202), root:(0,644),
state 0x0, keycode 113 (keysym 0xff51, Left), same_screen YES,
XLookupString gives 0 bytes:
XmbLookupString gives 0 bytes:
XFilterEvent returns: False

KeyRelease event, serial 34, synthetic NO, window 0x5a00001,
root 0x209, subw 0x0, time 325417107, (-871,202), root:(0,644),
state 0x0, keycode 113 (keysym 0xff51, Left), same_screen YES,
XLookupString gives 0 bytes:
XFilterEvent returns: False

Bananapi mythtv

2014-09-30T08:16:45Z

Esperanto:

Using Raspbian_For_BananaPi_v3.1
http://www.lemaker.org/resources/9-81/raspbian_for_bananapi.html

After installing the image and booting one time I had to use a partition mananger to increase the root partition otherwise all the required packages will not fit.

apt-get install \
make gcc git automake autoconf pkg-config libtool dh-autoreconf \
xserver-xorg-dev \
libgl1-mesa-dev \
libgles2-mesa-dev \
libgles1-mesa-dev \
xutils-dev \
x11proto-xf86dri-dev \
mesa-utils \
mplayer2 \
glew-utils \
libglew-dev \
libvdpau-dev \
freeglut3-dev

apt-get purge libegl1-mesa

cd $HOME
git clone https://github.com/robclark/libdri2.git
git clone https://github.com/linux-sunxi/libump.git
git clone https://github.com/linux-sunxi/sunxi-mali.git
git clone https://github.com/ssvb/xf86-video-fbturbo.git

(I actualy have git clone -b 0.4.0 https://github.com/ssvb/xf86-video-fbturbo.git currently but I doubt that makes a difference )

ran:
dpkg-reconfigure locales
and selected the locale that was failing when running autogen in the next step

cd $HOME/libdri2
./autogen.sh --prefix=/usr
sudo make install

cd $HOME/libump
autoreconf -vi
./configure --prefix=/usr
make
sudo make install

cd $HOME/sunxi-mali
git submodule init
git submodule update
make config ABI=armhf VERSION=r3p0
sudo make install

cd $HOME/xf86-video-fbturbo
autoreconf -vi
./configure --prefix=/usr
make
sudo make install

mkdir -p /etc/X11/xorg.conf.d/

vi /etc/X11/xorg.conf.d/99-fbturbo.conf
-----------------
Section "Device"
Identifier "Allwinner A10/A13 FBDEV"
Driver "fbturbo"
Option "fbdev" "/dev/fb0"
Option "SwapbuffersWait" "true"
Option "AccelMethod" "G2D"
EndSection
------------------

cd $HOME
git clone https://github.com/linux-sunxi/libvdpau-sunxi.git
cd $HOME/libvdpau-sunxi
make
sudo make install

modprobe sunxi_cedar_mod

to run as non root user:
chmod 666 /dev/ump /dev/mali /dev/disp /dev/g2d /dev/fb* /dev/cedar_dev

export VDPAU_DRIVER=sunxi
wget http://babilejo.org/linuxmce/sample.mkv
mplayer -fs -vo vdpau -vc ffmpeg12vdpau,ffh264vdpau sample.mkv

==================
apt-get update
apt-get dist-upgrade
sudo apt-get install qt4-qmake libfreetype6-dev libmp3lame-dev libqt4-dev libxxf86vm-dev libxinerama-dev libasound2-dev pkg-config uuid-dev libtag1-dev libgexiv2-dev

cd $HOME
git clone git://github.com/MythTV/mythtv.git
cd $HOME/mythtv/mythtv
./configure
make -j 2
make install

set vdpau normal in playback profiles
set the audio output

#!/bin/sh
sudo modprobe sunxi_cedar_mod
export VDPAU_DRIVER=sunxi
export VDPAU_OSD=1
sudo chmod 666 /dev/ump /dev/mali /dev/disp /dev/g2d /dev/fb* /dev/cedar_dev
mythfrontend

Xine does not work yet:

sudo apt-get install xine-console xfonts-base

xine --no-splash --no-logo --no-gui -f -V vdpau sample.mkv

===============
bananapi@lemaker ~ $ xine --no-splash --no-logo --no-gui -f -V vdpau sample.mkv
This is xine (X11 gui) - a free video player v0.99.7.
(c) 2000-2010 The xine Team.
vo_vdpau: vdpau API version : 1
vo_vdpau: vdpau implementation description : sunxi VDPAU Driver
vo_vdpau: VideoSurface doesn't support chroma type 4:2:2, sorry.

Bananapi mythtv

2014-09-29T19:51:55Z

Esperanto: concept info

Boblight

2014-09-14T17:44:36Z

Esperanto: boblight & adalight notes

= Boblight with Adalight on Linuxmce =

Until Linuxmce integrates the possibility to do some postprocessing in xine it looks like you have to run a separate xine process which enables postprocessing. I put this together based on my notes so if something does not work please let me know and improve this page.

* [https://code.google.com/p/boblight/ boblight]
* [https://learn.adafruit.com/adalight-diy-ambient-tv-lighting adalight] (the hardware can be order for less then $50 on ebay.

== install Boblight ==

sudo apt-get install libx11-dev libgl1-mesa-dev libxrender-dev libxext-dev libavcodec-dev libavformat-dev libswscale-dev libavdevice-device

svn checkout http://boblight.googlecode.com/svn/trunk/ boblight-read-only
cd boblight-read-only/

./configure --without-portaudio
make
make install
echo "/usr/local/lib/libboblight.so" > /etc/ld.so.conf.d/boblightlibs.conf
sudo ldconfig

Next create a startscript for the daemon

/etc/init/boblight.conf
# boblight service

description "boblight"
author "jordi"

start on started network-services
stop on starting shutdown

respawn

env EXEC="/usr/local/bin/boblightd"
env PIDFILE="/var/run/boblightd.pid"
env CONFFILE="/etc/boblight.conf"
env LOGFILE="/var/log/boblightd.log"

exec start-stop-daemon -m --pidfile $PIDFILE --exec $EXEC --start -- -c $CONFFILE > $LOGFILE 2>&1

------------------------------

Lastly setup the configuration script for boblight at /etc/boblight.conf. Below is the basis for the configuration file to start from. You need to calculate the lights location and add those to the file. Use an online calculator for this:
* http://tvgloria.hu/

[global]
interface 127.0.0.1
port 19333

[device]
name ambilight
type momo
output /dev/ttyUSB0
channels 150
#25 leds
#prefix 41 64 61 00 18 4D
#50 leds
prefix 41 64 61 00 31 64
#100 leds
#prefix 41 64 61 00 63 36
interval 10000
rate 115200
debug off #turn this on to see what it's doing with the serial port
delayafteropen 1000000

[color]
name red
rgb FF0000
gamma 1.1
adjust 0.22
blacklevel 0.01

[color]
name green
rgb 00FF00
gamma 1.1
adjust 0.22
blacklevel 0.01

[color]
name blue
rgb 0000FF
gamma 1.2
adjust 0.2
blacklevel 0.01

Create a log rotate file:

# cat /etc/logrotate.d/boblightd
/var/log/boblightd.log {
daily
rotate 7
delaycompress
compress
missingok
postrotate
[ ! -f /var/run/boblightd.pid ] || kill -HUP `cat /var/run/boblightd.pid`
endscript
}

== DFatmo plugin ==
sudo apt-get install libxine2-dev
git clone https://github.com/durchflieger/DFAtmo
cd DFAtmo/

make xineplugin
make xineinstall
make dfatmo
make dfatmoinstall

== install xine player ==

to compile Xine_Player you need:
sudo apt-get install libxmu-dev \
libxxf86vm-dev \
libxtst-dev \
libcdparanoia-dev

then get the latest xine player from https://www.xine-project.org/homeand install it.

== run ==

sudo start boblight
export DISPLAY=:0; xine --verbose=10 --hide-gui --geometry 1x1+0+1080 --post=dfatmo:driver=serial &
export DISPLAY=:0; boblight-X11 &

User talk:Phenigma

2014-09-14T15:41:40Z

Esperanto:

This is from my notes:

===== MYTHTV 0.28 PPA daily =====

sudo add-apt-repository ppa:mythbuntu/0.28
sudo apt-get update
sudo apt-get purge libmyth-0* mythtv-backend mythtv-common mythtv-frontend mythtv-transcode-utils libmyth-python libmythtv-perl
sudo apt-get install mythtv-frontend pluto-mythtv-player

then start mythtv on frontend and fill in IP, port and password of the core backend.
Don't forget to select vdpau and set the sound device in mythtv.

commented the start-on line on the MD:
sed -e '/^start on / s/^#*/#/' -i /etc/init/mythtv-backend.conf
mv /usr/pluto/bin/Restart_MythBackend.sh /usr/pluto/bin/Restart_MythBackend.sh_

Don't forget to set the token and protocol nr in the device template:
https://code.mythtv.org/doxygen/mythversion_8h_source.html

User talk:Phenigma

2014-09-12T19:24:46Z

Esperanto:

User talk:Phenigma

2014-09-12T19:23:22Z

Esperanto: notes mythtv

Developing a DCE Device

2014-04-14T13:46:38Z

Esperanto: libattr1-dev needed for sql2cpp?

[[Category: Development]]
[[Category: Programmer's Guide]]
Document Relevance:
*LinuxMCE 810
*LinuxMCE 1004
== Introduction ==

DCE (Data, Commands and Events) is a lightweight network protocol allowing any device to access its configuration (ie data) from a central database, send + receive commands, and fire + respond to events.

A DCE device is a piece of software that implements the DCE protocol, as a means to interface with hardware or other pieces of software.

See [[Developers Guide]] for more info on DCE and other parts of LinuxMCE architecture.

For the purposes of this demonstration, we will be using the instructions below to create a c++ project that will result in a working DCE implementation of a fictional smart light bulb socket.

== Preparation ==
Developing for any part of the system requires a specific environment setup, including an up to date source code tree and some required programs to be installed. It is assumed that this guide will be followed on an existing LinuxMCE Core installation. All commands following a # sign are to be run as a privileged user, either by prepending 'sudo' or after obtaining a root shell ("sudo -s", "sudo -r", or "sudo su" are all acceptable means of doing this).
=== Required Packages ===
Install pluto-dcegen, [http://svn.linuxmce.org/svn/trunk/src/sql2cpp/ pluto-sql2cpp ], and a few other build dependencies
# apt-get install pluto-dcegen subversion build-essential libmysqld-dev libattr1-dev

*In my case on 810 replace libmysqld-dev with libmysqlclient15-dev -L3mce

=== Source Tree ===
Check out the LinuxMCE source tree
# svn co http://svn.linuxmce.org/svn/branches/LinuxMCE-1004/src .

=== Environment Preparation ===
Copy the system libs into the source tree
# cp /usr/pluto/lib/* src/lib
== Developing the Device ==

=== Device Template ===
Every DCE device, starts with a template.

A template merely specifies what the device is, what it's capable of, how it relates to the other devices in the system, what it needs to install (the package entry), any data it might need to carry around (device data), any events the device may want to EMIT, any related devices that need to exist for this device to function, and any orbiter screens this thing might need, as well as plug and play data so the system can detect it if it's hardware. 
In short, as the name implies, it is a template that the system can use as a basis to create a unique device for each piece of hardware or software attached to the system (even multiples of each).

Before any code can be written, a device template is needed. This is created in the Web Admin, under Advanced -> Configuration -> Device Templates. 
There is a button for "Add device template", but a manufacturer and a device category must be selected first. In this case, the manufacturer will be "Pluto" and the device category will be "Lighting Device < Environment". New manufacturers and device categories can be added if none are suitable for the device being controlled. 
Select the manufacturer and device category, then click the "Add device template" button. 
On the window that pops up, select the second option (to make it a c++ device) and fill in a name (this guide will use "Intelligent Light Switch") and click "Add". 
At this point the device template is complete and a functioning device could be made from it, however there are some important options that need to be set to make the device actually be useful. These are listed below organized by the section they appear in on the device template configuration screen.

==== Device Template #xxxx ====
This is the main section. Remember the number after the pound sign; this is the unique identifier for this device template and will be required for some steps later. For demonstration purposes, this guide will use the number 2181. There are some important options that must be set here. For details on items which are not covered here, see [[Edit Device Template]]. 
''Implements DCE device'' - this should always be checked for DCE devices, for obvious reasons. 
''This device is controlled via'' and ''This device is controlled via category'' - devices are usually attached to other devices or controlled via other devices; these options provide a way of specifying that relationship. This mythical intelligent light can be controlled by any Media Director (which includes the Media Director portion of a Core/Hybrid) so click the "Add a new controlled via category device" and choose "Media Director". 
''Inherits MAC from PC'' and ''Is IP Based'' - the light is network-attached, so select these options. 

==== Device Data ====
Device Data is simply a way of describing pieces of information, so that the device and the rest of the system know how to talk to each other. Events and Commands make use of Device Data to pass information around. This section tells this device what kind of information it will send or receive. 
The intelligent light will be able to provide information on how much electricity it is consuming, or we can manually configure it with this information, so open the drop-down next to "Add a new parameter" and select "Energy Consumption". There are several options available for each Device Data: 
''Comments'' - as it says, a comment describing what this piece of information is for. Device Data are fairly generic in nature, so this allows a more descriptive entry. This is required, so fill it in with something. 
''Default Value'' - the value to use by default in any device created by this template. It is not required, but fill in a 0 for now. 
''Required'' - device data can be optional. If this is checked then a default value must be provided or the user must enter a value. Leave it unchecked. 
''Allowed to Modify'' - as it implies, this controls whether the user can modify the value in the web admin. Enable this. 
''Use Master Device List Defaults'' - this means that the default value above will always be used by any created devices, and any time the device template default is changed all created devices will be automatically updated. Leave it unchecked. 
''Set by Device'' - this means that the DCE device itself sets the value. Normally a device like the intelligent light switch would set its energy usage, but since this is just a demonstration this will be left unchecked.

==== Commands ====
Commands are how the system tells this device to perform an action. As can be seen, several command groups have already been made available, chosen based on what device category this device template is. None are actually enabled, however, so some will need to be selected. The intelligent light switch is able to turn on and off, as well as dim to partially on states, so select the check boxes for "Dimming" and "On/Off Light Switch". You can click on the "Edit Commands" button to see what commands make up each group.

==== Events ====
Events are how the device lets the system know that something with this device has happened. Other parts of the system can register to listen for these events and perform an action of their own when the event is fired. The intelligent light switch also has manual controls, so it needs to let the system know when someone operates one of these controls. 
Usually events will mirror commands, so use the dropdown to add events for "Device On/Off" and "State Changed" and use the textbox to add an appropriate comment for each.

==== Plug & Play ====
This is used to help the system identify when a device becomes available and know that this is the device template to use when creating a device for it. This section is not used in this guide.

==== Device Template Related ====
This is used to let the system know about devices that are related to this one. This section is not used in this guide.

==== Screens ====
This is used to let OrbiterGen know about Orbiter screens that are not referenced directly but are still used by this device. This section is not use in this guide.

=== Running DCEGen ===
DCEGen is a program that uses the device template information to create a skeleton of c++ code that will comprise the basics of the device. It creates the necessary header files, source files and makefiles in order for the device's code to compile. Included in this are functions for the device data, commands, and events defined in the template. Under normal circumstances, you would do an initial sqlCVS checkin at this point in order to get a permanent Device Template number, but since this is a demonstration only this will not be performed. 
Run DCEGen to create the source code skeleton:
# cd src/DCEGen
# /usr/pluto/bin/DCEGen -d 2181
It is important to be in src/DCEGen of the svn tree when running this command! Also make sure to use the correct device template number for your template in place of 2181. DCEGen can also be run again later if you change the device template options; it will leave your customizations alone and only update the device template specified options. DCEGen adds very verbose comments that makes the code very easy to read and modify.

=== Running sql2cpp ===
All database tables, rows, and columns are represented as c++ constants, and must be regenerated any time device template options change. sql2cpp performs this operation. 
# cd ../sql2cpp
# /usr/pluto/bin/sql2cpp
As with DCEGen, it is important to be in src/sql2cpp of the svn tree when executing it, and it is safe to execute this again at any time.

=== Testing Compilation ===
Before compilation, you may need to install build packages required for some code. Its wise to do this in the start and spare yourself the headaches.

apt-get install $(cat home/src/LinuxMCE-1004/src/Ubuntu_Helpers_NoHardcode/conf-files/lucid-i386/build-packages)

This should install the packages needed for compilation.

At this point the device code is complete and will create a fully functioning device binary when compiled. DCEGen created a new directory in src for the device and placed all the code within that directory, so to compile it, simply cd into that directory and invoke the "make" command: 
# cd ../Intelligent_Light_Switch
# ./make
Due to a bug in DCEGen, there will be an error during compilation about post_make.sh, however it is not fatal. If the error bothers you, you can simply make the file executable: 
# chmod 755 post_make.sh
You should now have a binary of the device in the current dir: Intelligent_Light_Switch

=== Testing the Device ===
At this point you could create a device in the device tree and copy the binary to /usr/pluto/bin and the device would be started in a screen session after a router reload. However for testing purposes it is usually better to just run the device directly from where it is at. Go ahead and create a device in the device tree: 
Sign in to the web admin, go to Advanced -> Configuration -> Devices, and browse to and select the "The core/hybrid" device under "CORE" in the tree to the left. 
Click "Create Child Device", enter a description, and click the "Pick device template" button. 
Enter your device template ID in the box next to the "Go" button, click the "Go" button, then click "Pick device template". 
Write down the device number this is assigned to this device. For demonstration purposes, this guide will use "53" as the device number. 
Now, start the device, providing it with the device number to use: 
# ./Intelligent_Light_Switch -d 53
It will probably tell you that the router needs reloaded; go ahead and do this using the web admin or an Orbiter. You may need to restart the device afterwards. Note that at any time you can press ctrl-c to stop the device and exit back to the shell. To see the device in action, click on the "Send command to device" link at the top of it's web admin page. Choose one of the available commands and click "Send Message", providing any Device Data that you want. The terminal running the device will output messages saying that the command was received.

=== Implementing Code ===
Of course the device created so far doesn't actually do anything, other than provide some output when it is sent commands; hardly a useful device! Here begins the process of adding functionality and testing the results. Add/edit some code, then do the compiling and testing steps above to make sure things are going in the right direction. Repeat until the device does everything it should. 
Refer to the source code for other devices if you get stuck or if you need ideas on how to implement something. And make sure to run DCEGen and sql2cpp as necessary if you change options in the device template.

== Packaging the Device ==

=== Creating the Binary Package ===
=== Creating the Source Package ===

Developing a DCE Device

2014-04-14T13:39:38Z

Esperanto: removed pluto-sql2cpp package

[[Category: Development]]
[[Category: Programmer's Guide]]
Document Relevance:
*LinuxMCE 810
*LinuxMCE 1004
== Introduction ==

DCE (Data, Commands and Events) is a lightweight network protocol allowing any device to access its configuration (ie data) from a central database, send + receive commands, and fire + respond to events.

A DCE device is a piece of software that implements the DCE protocol, as a means to interface with hardware or other pieces of software.

See [[Developers Guide]] for more info on DCE and other parts of LinuxMCE architecture.

For the purposes of this demonstration, we will be using the instructions below to create a c++ project that will result in a working DCE implementation of a fictional smart light bulb socket.

== Preparation ==
Developing for any part of the system requires a specific environment setup, including an up to date source code tree and some required programs to be installed. It is assumed that this guide will be followed on an existing LinuxMCE Core installation. All commands following a # sign are to be run as a privileged user, either by prepending 'sudo' or after obtaining a root shell ("sudo -s", "sudo -r", or "sudo su" are all acceptable means of doing this).
=== Required Packages ===
Install pluto-dcegen, [http://svn.linuxmce.org/svn/trunk/src/sql2cpp/ pluto-sql2cpp ], and a few other build dependencies
# apt-get install pluto-dcegen subversion build-essential libmysqld-dev

*In my case on 810 replace libmysqld-dev with libmysqlclient15-dev -L3mce

=== Source Tree ===
Check out the LinuxMCE source tree
# svn co http://svn.linuxmce.org/svn/branches/LinuxMCE-1004/src .

=== Environment Preparation ===
Copy the system libs into the source tree
# cp /usr/pluto/lib/* src/lib
== Developing the Device ==

=== Device Template ===
Every DCE device, starts with a template.

A template merely specifies what the device is, what it's capable of, how it relates to the other devices in the system, what it needs to install (the package entry), any data it might need to carry around (device data), any events the device may want to EMIT, any related devices that need to exist for this device to function, and any orbiter screens this thing might need, as well as plug and play data so the system can detect it if it's hardware. 
In short, as the name implies, it is a template that the system can use as a basis to create a unique device for each piece of hardware or software attached to the system (even multiples of each).

Before any code can be written, a device template is needed. This is created in the Web Admin, under Advanced -> Configuration -> Device Templates. 
There is a button for "Add device template", but a manufacturer and a device category must be selected first. In this case, the manufacturer will be "Pluto" and the device category will be "Lighting Device < Environment". New manufacturers and device categories can be added if none are suitable for the device being controlled. 
Select the manufacturer and device category, then click the "Add device template" button. 
On the window that pops up, select the second option (to make it a c++ device) and fill in a name (this guide will use "Intelligent Light Switch") and click "Add". 
At this point the device template is complete and a functioning device could be made from it, however there are some important options that need to be set to make the device actually be useful. These are listed below organized by the section they appear in on the device template configuration screen.

==== Device Template #xxxx ====
This is the main section. Remember the number after the pound sign; this is the unique identifier for this device template and will be required for some steps later. For demonstration purposes, this guide will use the number 2181. There are some important options that must be set here. For details on items which are not covered here, see [[Edit Device Template]]. 
''Implements DCE device'' - this should always be checked for DCE devices, for obvious reasons. 
''This device is controlled via'' and ''This device is controlled via category'' - devices are usually attached to other devices or controlled via other devices; these options provide a way of specifying that relationship. This mythical intelligent light can be controlled by any Media Director (which includes the Media Director portion of a Core/Hybrid) so click the "Add a new controlled via category device" and choose "Media Director". 
''Inherits MAC from PC'' and ''Is IP Based'' - the light is network-attached, so select these options. 

==== Device Data ====
Device Data is simply a way of describing pieces of information, so that the device and the rest of the system know how to talk to each other. Events and Commands make use of Device Data to pass information around. This section tells this device what kind of information it will send or receive. 
The intelligent light will be able to provide information on how much electricity it is consuming, or we can manually configure it with this information, so open the drop-down next to "Add a new parameter" and select "Energy Consumption". There are several options available for each Device Data: 
''Comments'' - as it says, a comment describing what this piece of information is for. Device Data are fairly generic in nature, so this allows a more descriptive entry. This is required, so fill it in with something. 
''Default Value'' - the value to use by default in any device created by this template. It is not required, but fill in a 0 for now. 
''Required'' - device data can be optional. If this is checked then a default value must be provided or the user must enter a value. Leave it unchecked. 
''Allowed to Modify'' - as it implies, this controls whether the user can modify the value in the web admin. Enable this. 
''Use Master Device List Defaults'' - this means that the default value above will always be used by any created devices, and any time the device template default is changed all created devices will be automatically updated. Leave it unchecked. 
''Set by Device'' - this means that the DCE device itself sets the value. Normally a device like the intelligent light switch would set its energy usage, but since this is just a demonstration this will be left unchecked.

==== Commands ====
Commands are how the system tells this device to perform an action. As can be seen, several command groups have already been made available, chosen based on what device category this device template is. None are actually enabled, however, so some will need to be selected. The intelligent light switch is able to turn on and off, as well as dim to partially on states, so select the check boxes for "Dimming" and "On/Off Light Switch". You can click on the "Edit Commands" button to see what commands make up each group.

==== Events ====
Events are how the device lets the system know that something with this device has happened. Other parts of the system can register to listen for these events and perform an action of their own when the event is fired. The intelligent light switch also has manual controls, so it needs to let the system know when someone operates one of these controls. 
Usually events will mirror commands, so use the dropdown to add events for "Device On/Off" and "State Changed" and use the textbox to add an appropriate comment for each.

==== Plug & Play ====
This is used to help the system identify when a device becomes available and know that this is the device template to use when creating a device for it. This section is not used in this guide.

==== Device Template Related ====
This is used to let the system know about devices that are related to this one. This section is not used in this guide.

==== Screens ====
This is used to let OrbiterGen know about Orbiter screens that are not referenced directly but are still used by this device. This section is not use in this guide.

=== Running DCEGen ===
DCEGen is a program that uses the device template information to create a skeleton of c++ code that will comprise the basics of the device. It creates the necessary header files, source files and makefiles in order for the device's code to compile. Included in this are functions for the device data, commands, and events defined in the template. Under normal circumstances, you would do an initial sqlCVS checkin at this point in order to get a permanent Device Template number, but since this is a demonstration only this will not be performed. 
Run DCEGen to create the source code skeleton:
# cd src/DCEGen
# /usr/pluto/bin/DCEGen -d 2181
It is important to be in src/DCEGen of the svn tree when running this command! Also make sure to use the correct device template number for your template in place of 2181. DCEGen can also be run again later if you change the device template options; it will leave your customizations alone and only update the device template specified options. DCEGen adds very verbose comments that makes the code very easy to read and modify.

=== Running sql2cpp ===
All database tables, rows, and columns are represented as c++ constants, and must be regenerated any time device template options change. sql2cpp performs this operation. 
# cd ../sql2cpp
# /usr/pluto/bin/sql2cpp
As with DCEGen, it is important to be in src/sql2cpp of the svn tree when executing it, and it is safe to execute this again at any time.

=== Testing Compilation ===
Before compilation, you may need to install build packages required for some code. Its wise to do this in the start and spare yourself the headaches.

apt-get install $(cat home/src/LinuxMCE-1004/src/Ubuntu_Helpers_NoHardcode/conf-files/lucid-i386/build-packages)

This should install the packages needed for compilation.

At this point the device code is complete and will create a fully functioning device binary when compiled. DCEGen created a new directory in src for the device and placed all the code within that directory, so to compile it, simply cd into that directory and invoke the "make" command: 
# cd ../Intelligent_Light_Switch
# ./make
Due to a bug in DCEGen, there will be an error during compilation about post_make.sh, however it is not fatal. If the error bothers you, you can simply make the file executable: 
# chmod 755 post_make.sh
You should now have a binary of the device in the current dir: Intelligent_Light_Switch

=== Testing the Device ===
At this point you could create a device in the device tree and copy the binary to /usr/pluto/bin and the device would be started in a screen session after a router reload. However for testing purposes it is usually better to just run the device directly from where it is at. Go ahead and create a device in the device tree: 
Sign in to the web admin, go to Advanced -> Configuration -> Devices, and browse to and select the "The core/hybrid" device under "CORE" in the tree to the left. 
Click "Create Child Device", enter a description, and click the "Pick device template" button. 
Enter your device template ID in the box next to the "Go" button, click the "Go" button, then click "Pick device template". 
Write down the device number this is assigned to this device. For demonstration purposes, this guide will use "53" as the device number. 
Now, start the device, providing it with the device number to use: 
# ./Intelligent_Light_Switch -d 53
It will probably tell you that the router needs reloaded; go ahead and do this using the web admin or an Orbiter. You may need to restart the device afterwards. Note that at any time you can press ctrl-c to stop the device and exit back to the shell. To see the device in action, click on the "Send command to device" link at the top of it's web admin page. Choose one of the available commands and click "Send Message", providing any Device Data that you want. The terminal running the device will output messages saying that the command was received.

=== Implementing Code ===
Of course the device created so far doesn't actually do anything, other than provide some output when it is sent commands; hardly a useful device! Here begins the process of adding functionality and testing the results. Add/edit some code, then do the compiling and testing steps above to make sure things are going in the right direction. Repeat until the device does everything it should. 
Refer to the source code for other devices if you get stuck or if you need ideas on how to implement something. And make sure to run DCEGen and sql2cpp as necessary if you change options in the device template.

== Packaging the Device ==

=== Creating the Binary Package ===
=== Creating the Source Package ===

RF03 Air mouse

2014-03-30T16:42:00Z

Esperanto: added reset procedure

Mele F10 Fly mouse / RF03 Air Mouse & Wireless Keyboard

http://www.amazon.com/Mele-wireless-Keyboard-Control-Universal/dp/B0092KDSQW/

To reset the mouse: make sure the distance between the usb receiver and the air mouse is as small as possible. Put the air mouse horizontally. Next press the Enter key (middle of circle) and the right mouse button/back key (just right above the circle) simultanously.

Button layout on mouse side:

X X

KEY_ENTER BTN_RIGHT

KEY_UP

KEY_LEFT BTN_LEFT KEY_RIGHT

KEY_DOWN

KEY_HOME BTN_MIDDLE KEY_VOLUMEDOWN KEY_VOLUMEUP

KEY_TV X X KEY_MUTE

KEY_F1 KEY_F2 KEY_F3 KEY_F4

USB ID: 1915af11

Squeezelite

2014-03-20T14:31:47Z

Esperanto: stop section

An alternative for squeezeslave.

Downloadable executables and source at:

http://code.google.com/p/squeezelite/

Squeezelite upstart (/etc/init/squeezelite.conf). This is run after pulseaudio is started up and uses the pulseaudio sink 'kitchen'.
<nowiki>
# squeezelite service

description "squeezelite"

start on started pulseaudio
stop on starting shutdown or stopping pulseaudio

respawn

env EXEC="/root/squeezelite-i386"
env ARGS="-a 180 -o pulse"
env LOGGING="-d all=info"
env MAC="00:00:00:00:00:04"
env LOGFILE="/var/log/squeezelite.log"
env PIDFILE="/var/run/squeezelite.pid"
env NAME="kitchen"
env PULSE_SINK="kitchen"
env PULSE_PROP_OVERRIDE="application.name='squeezelite kitchen'"
env SERVER="192.168.80.1"

exec start-stop-daemon -m --pidfile $PIDFILE --exec $EXEC --start -- -s $SERVER $ARGS $LOGGING -m $MAC -f $LOGFILE -n $NAME
</nowiki>

Take care of the logfile
<nowiki>
/var/log/squeezelite.log {
daily
rotate 7
delaycompress
compress
missingok
postrotate
[ ! -f /var/run/squeezelite.pid ] || kill -HUP `cat /var/run/squeezelite.pid`
endscript
}
</nowiki>

Since pulseaudio is started via /etc/init.d/ instead of upstart I changed /etc/init.d/pulseaudio and added to end of the pulseaudio_start () section:
<nowiki>
if [ ${status} -eq 0 ]; then
initctl emit started JOB=pulseaudio
fi
log_end_msg ${status}
</nowiki>
And added an emit entry to the /etc/init.d/pulseaudio pulseaudio_stop () section:
<nowiki>
pulseaudio_stop () {
log_daemon_msg "Stopping system PulseAudio Daemon"
start-stop-daemon -p $PIDFILE --stop --retry 5 || echo -n "...which is not running"
initctl emit stopping JOB=pulseaudio
log_end_msg $?
}
</nowiki>

Squeezelite

2014-03-20T14:19:33Z

Esperanto:

Squeezelite

2014-03-20T14:18:38Z

Esperanto: Added upstart and log scripts

An alternative for squeezeslave.

Downloadable executables and source at:

http://code.google.com/p/squeezelite/

Squeezelite upstart (/etc/init/squeezelite.conf). This is run after pulseaudio is started up and uses the pulseaudio sink 'kitchen'.
<nowiki>
# squeezelite service

description "squeezelite"

start on start pulseaudio
stop on starting shutdown

respawn

env EXEC="/root/squeezelite-i386"
env ARGS="-a 180 -o pulse"
env LOGGING="-d all=info"
env MAC="00:00:00:00:00:04"
env LOGFILE="/var/log/squeezelite.log"
env PIDFILE="/var/run/squeezelite.pid"
env NAME="kitchen"
env PULSE_SINK="kitchen"
env PULSE_PROP_OVERRIDE="application.name='squeezelite kitchen'"
env SERVER="192.168.80.1"

exec start-stop-daemon -m --pidfile $PIDFILE --exec $EXEC --start -- -s $SERVER $ARGS $LOGGING -m $MAC -f $LOGFILE -n $NAME
</nowiki>

Take care of the logfile
<nowiki>
/var/log/squeezelite.log {
daily
rotate 7
delaycompress
compress
missingok
postrotate
[ ! -f /var/run/squeezelite.pid ] || kill -HUP `cat /var/run/squeezelite.pid`
endscript
}
</nowiki>

Since pulseaudio is started via /etc/init.d/ instead of upstart I changed /etc/init.d/pulseaudio and added to end of the pulseaudio_start () section:
<nowiki>
if [ ${status} -eq 0 ]; then
initctl emit started JOB=pulseaudio
fi
log_end_msg ${status}
</nowiki>

RF03 Air mouse

2013-05-31T19:17:06Z

Esperanto:

Mele F10 Fly mouse / RF03 Air Mouse & Wireless Keyboard

http://www.amazon.com/Mele-wireless-Keyboard-Control-Universal/dp/B0092KDSQW/

Button layout on mouse side:

X X

KEY_ENTER BTN_RIGHT

KEY_UP

KEY_LEFT BTN_LEFT KEY_RIGHT

KEY_DOWN

KEY_HOME BTN_MIDDLE KEY_VOLUMEDOWN KEY_VOLUMEUP

KEY_TV X X KEY_MUTE

KEY_F1 KEY_F2 KEY_F3 KEY_F4

USB ID: 1915af11

RF03 Air mouse

2013-05-31T07:59:41Z

Esperanto:

Mele F10 Fly mouse / RF03 Air Mouse & Wireless Keyboard

Button layout on mouse side:

X X

KEY_ENTER BTN_RIGHT

KEY_UP

KEY_LEFT BTN_LEFT KEY_RIGHT

KEY_DOWN

KEY_HOME BTN_MIDDLE KEY_VOLUMEDOWN KEY_VOLUMEUP

KEY_TV X X KEY_MUTE

KEY_F1 KEY_F2 KEY_F3 KEY_F4

USB ID: 1915af11

RF03 Air mouse

2013-05-31T07:56:06Z

Esperanto: Created page with "Mele F10 Fly mouse / RF03 Air Mouse & Wireless Keyboard Button layout on mouse side: X X KEY_ENTER BTN_RIGHT ..."

Squeezelite

2013-01-20T16:53:41Z

Esperanto: squeezeslave alternative

An alternative for squeezeslave.

Downloadable executables and source at:

http://code.google.com/p/squeezelite/

Custom orbiter sizes

2013-01-19T20:14:39Z

Esperanto:

See [[Custom_Display_Resolutions#Orbiter_size]] for more info.

To add a custom size via the commandline:
* sudo mysql pluto_main
* copy paste one of the insert lines below

* Asus Transformer infinity
INSERT INTO Size SET Description='1920x1128 (asus transformer infinity)', Width=1920, Height=1128, ScaleX=902, ScaleY=707, ScaleMenuBg='S', ScaleOtherGraphics='F';

* Asus Transformer prime
INSERT INTO Size SET Description='1280x752 (Asus transformer prime)', Width=1280, Height=752, ScaleX=602, ScaleY=471, ScaleMenuBg='S', ScaleOtherGraphics='F';

* generic 1920x1200
INSERT INTO Size SET Description='1920x1200', Width=1920, Height=1200, ScaleX=902, ScaleY=752, ScaleMenuBg='S', ScaleOtherGraphics='F';

Custom orbiter sizes

2013-01-19T20:11:51Z

Esperanto: sql insert lines for custom orbiter sizes for different devices

See [[Custom_Display_Resolutions#Orbiter_size]] for more info.

To add a custom size via the commandline:
* sudo mysql pluto_main
* copy paste one of the insert lines below

* Asus Transformer infinity
INSERT INTO Size SET Description='1920x1128 (asus transformer infinity)', Width=1920, Height=1128, ScaleX=902, ScaleY=707, ScaleMenuBg='S',

* Asus Transformer prime
INSERT INTO Size SET Description='1280x752 (Asus transformer prime)', Width=1280, Height=752, ScaleX=602, ScaleY=471, ScaleMenuBg='S', ScaleOtherGraphics='F';

* generic 1920x1200
INSERT INTO Size SET Description='1920x1200', Width=1920, Height=1200, ScaleX=902, ScaleY=752, ScaleMenuBg='S', ScaleOtherGraphics='F';

Squeezeslave on the core

2013-01-16T15:44:56Z

Esperanto: /* Select Device */

[[Category: Tutorials]]
[[Category:Audio]]
{| align="right"
| __TOC__
|}
==Whats does it do?==
Squeezeslave basically makes it possible to add additional 'virtual' Squeezeboxes to your Core or MD's just by adding additional sound-cards. Each Squeezeslave/Sound-card combo uses about 4-5% CPU on an ATOM/Ion based MD. We have tested an ATOM/Ion based MD running 3 x Squeezeslave/Sound-Card combo's while playing a ripped DVD from the Core without any problems at all. Using Squeezeslave/Sound-Card combo's makes it possible to have several independent audio outputs from your Core or from an MD allowing you to use the 2nd Zone of your Surround Amp for example to provide audio to an adjoining room eg a bathroom or maybe a kitchen. All of this expands the options you have when designing your system, gives you enormous additional flexibility to locate additional audio sources where you need them, and reduces the energy footprint of your system at the same time (in comparison to adding additional physical Squeezeboxes).

==Squeezeslave Setup==
Here's how to setup squeezeslave to run on your core or in fact any of your MD's. It's fairly straight forward but currently requires manual config/install of each Squeezeslave - I'm working on making this something you can just configure from Web Admin simply and quickly. One small issue is that because squeezeslave uses the OSS interface, you will need a separate sound card for each instance of squeezeslave you want to run.

==Hardware Supported==
The Startech Virtual 7.1 USB Audio Adapter (model No. ICUSBAUD107) works fine. This tiny USB Stick style adapter works perfectly under 7.10, 9.10 & 10.04. No installation...just plug it in and its ready a few secs later. Only stereo out jack and Mic input jack.

Many other brands of USB Audio adapter will probably work too. Please add your experiences with other working hardware here too.

Under LinuxMCE 0810 it may be necessary to downgrade Alsa in order for the device to appear (in 'aplay -l' or 'squeezeslave -L'). Be aware that downgrading alsa will remove audio over hdmi capabilities on the affected computer.

===Setting Up Squeezeslave on your Core or MD's===
If you want to setup Squeezeslave on your Core then either open Konsole session from the KDE Desktop or ssh in from another machine and sudo yourself. If you want to set up Squeezeslave on an MD then ssh into your Core and then use;

ssh moonNNN (**where NNN is the ID number of the MD you want to ssh into.)

You can find the ID of your MD from the Web Admin page at Wizard->Devices->Media Directors and the ID is the number with a '#' in front of it at the top of each MD section. Now follow the instructions below for each MD you want to add Squeezeslave too.

===Needed Dependencies===
System libraries needed are subversion and libasound2-dev
sudo apt-get install subversion
sudo apt-get install libasound2-dev
Since squeezeslave is only updating the display versions of their makefiles also needed for building
sudo apt-get install libncurses5-dev
sudo apt-get install liblircclient-dev

===Squeezeslave is available in the debs===
Easiest for anybody will be
sudo apt-get install squeezeslave
This will install squeezeslave in the right directory for you to use. If you want to build it yourself follow the next steps.

===Typical build===
svn checkout http://squeezeslave.googlecode.com/svn/squeezeslave/trunk/squeezeslave
cd squeezeslave
make -f makefile.linux26-alsa-display realclean
make -f makefile.linux26-alsa-display

===Or Download Source / look at the squeezeslave wiki===
Download a version of [http://sourceforge.net/project/showfiles.php?group_id=105169 Squeezeslave]. I'm running the latest version which was 0.9-173

Look at the slimdevices wiki for the latest options and install instructions http://wiki.slimdevices.com/index.php/SqueezeSlave

===Installing===
*You'll want to put it somewhere in your path. (This is already done if you did the apt-get install method)
*There will be a file in the /bin directory called squeezeslave (there might be something added to this to represent the version you build, just rename the file to squeezeslave and copy to your wanted directory
*Example: /usr/bin
====Modify /etc/rc.local====
Next add the following to /etc/rc.local

If your setting up Squeezeslave on your Core then use;
/usr/bin/squeezeslave -o4 -m00:00:00:00:00:01 -r5 -M/var/log/squeezeslave.log

If your setting up Squeezeslave on one of your MD's then use;
/usr/bin/squeezeslave -o4 192.168.80.1 -m00:00:00:00:00:01 -r5 -M/var/log/squeezeslave.log

* the IP address should be the IP address of your Core (**Only needed if your running Squeezeslave on MD's**).
* the MAC address can be whatever you want, it just needs to be the same as the device created in linux mce
* the -o option specifies which output device ie /dev/dsp1 (check with "squeezeslave -L" for available devices then use '-oN' where 'N' is the number next to your output device)
See example output using 'squeezeslave -L' below;

<pre>Output devices:
0: (ALSA) SB Live! Value [CT4832]: ADC Capture/Standard PCM Playback (hw:0,0) (11/46)
2: (ALSA) SB Live! Value [CT4832]: Multichannel Capture/PT Playback (hw:0,2) (10/42)
3: (ALSA) SB Live! Value [CT4832]: Multichannel Playback (hw:0,3) (10/42)
4: (ALSA) USB Audio Device: USB Audio (hw:1,0) (10/42)
5: (ALSA) front (11/46)
6: (ALSA) rear (11/46)
7: (ALSA) center_lfe (11/46)
8: (ALSA) surround40 (11/46)
9: (ALSA) surround41 (11/46)
10: (ALSA) surround50 (11/46)
11: (ALSA) surround51 (11/46)
12: (ALSA) iec958 (10/42)
13: (ALSA) spdif (10/42)
14: (ALSA) spdif_playback (11/46)
15: (ALSA) asym_spdif (11/46)
17: (ALSA) asym_analog (42/46)
18: (ALSA) usb_analog (42/46)
19: (ALSA) dmix (42/42)
*20: (ALSA) default (42/46)</pre>

I am using the No.18 device in the output above and therefore would use '-o18' switch when using the squeezeslave command.

* the -r option tells squeezeslave to keep retrying to connect to the server, useful if the server is not running yet.
* the -M option makes it run as a Daemon and creates log

====Fixing sample rate issues====
Squeezeslave only likes the 44.1 kHz sample rate. Anything lower will sounds like the Smurfs, anything higher will sound "slow". This is fixed by converting the source stream to something squeezeslave can cope with.

You need to edit the /etc/squeezeboxserver/convert.conf file so it has these lines in it:

mp3 flc squeezeslave *
[sox] -q -t mp3 $FILE$ -t flac -C 0 -r 44100 -
aac flc squeezeslave *
[faad] -q -w -f 1 $FILE$ | [flac] -cs --totally-silent --compression-level-0 --ignore-chunk-sizes - | [sox] -q -t flac - -t flac -C 0 -b 16 -r 44100 -

The aac to flc conversion could be shorter, but sox has a problem with '-t wav' with the output of faad and outputs an empty stream, and flac won't actually resample the stream when the --sample-rate=44100 parameter is given to it.

More conversions might be necessary as new stations are found to be problematic, but the strategy is the same: Convert to 'flac', resample to 44100 Hz.

You'll have to restart Squeezebox Server (Logitech Media Server) for the change to take effect.

===Setting Up Alsamixer===
Next make sure all the volume levels in the mixer (alsamixer) are set correctly
alsamixer
Make sure that the settings are as desired and save (Esc button)
===Setting Up LinuxMCE===

Next step, manually add the squeezeslave to linuxmce as a squeezebox using the mac address you gave it. The squeezebox player can be assigned to a room/entertainment area without an MD, in fact this would be a typical installation.

====Select Device====
* Select '''Wizard->Devices->A/V Equipment''' and press 'Add device' on the bottom of the page.
* In the Device Template dropdown select 'SqueezeBox Player' (template #58) and press 'Pick device template'.
* Assign it to a room in the left dropdown box (-select room-, make sure you select a room that does not yet have a MD in it!), put the MAC of the squeezeslave in the MAC entry field and press update.
* Regen your orbiters and reload the router.

Restart the core to make sure it's starting automatically, to run it manually just run the line made in the rc.local

/usr/bin/squeezeslave -o5 -m 00:00:00:00:00:01 -r5 -M/var/log/squeezeslave.log

* Check with ps if it is running:
ps aux | grep squeezeslave
**Example output:
root 11502 0.0 0.8 51484 8812 ? SLl Apr07 0:33 /usr/bin/squeezeslave -05 -m00:00:00:00:00:02 -r5 -M/var/log/squeezeslave

That should do it.

use /usr/bin/squeezeslave -L for available audio devices

use /usr/bin/squeezeslave -h for a list of options (see below)

<pre>/usr/bin/squeezeslave -h
squeezeslave 0.9-143
compile flags: linux portaudio:1485 debug signals daemon

Squeezeslave is licensed free of charge. There is NO WARRANTY for
the program. This program is provided "as is" without warranty of
any kind, either expressed or implied, including, but not limited
to, the implied warranties of merchantability and fitness for a
particular purpose. The entire risk as to the quality and
performance of the program is with you. Should the program prove
defective, you assume the cost of all necessary servicing, repair
or correction.

Copyright (c) 2004-2007 Richard Titmuss,
2008-2010 Duane Paddock.

squeezeslave [options] [<server address>]
The Squeezebox Server address defaults to 127.0.0.1.
Options:
-h, --help: Prints this message.
-a, Sets the amplitude of a high-frequency tone
--predelay_amplitude <val>: produced during the predelay (see --predelay).
The frequency is set at the source's sampling
rate/2 and the amplitude is in absolute value.
For 16-bit sources, the max is 32767, but values
below 10 are likely to work. The goal is to
produce an inaudible signal that will cause DACs
to wake-up and lock before actual samples are
played out. If the DAC locks using only silence,
do not use this option (it will default to 0).
-k, --keepalive <sec>: Controls how frequently squeezeslave sends a
alive signal to SqueezeCenter. 6.5.x servers
need this to avoid dropping the player's
connection. By default, the implementation
chooses the right value: 10s for a >=6.5.x server
and 0s for a <6.5.x server, which means no
keepalive.
-M, --daemonize <logfile> Run squeezeslave as a daemon.
Messages written to specified file.
Not supported with lirc and display modes.
-L, --list List available audio devices and exit.
-m, --mac <mac_address>: Sets the mac address for this instance.
Use the colon-separated notation.
The default is 00:00:00:00:00:01.
SqueezeCenter uses this value to distinguish
multiple instances, allowing per-player settings.
-o, --output <device_id>: Sets the output device id.
The default id is 0.
The output device ids can be found with -L.
-P, --port <portnumber>: Sets the SqueezeCenter port number.
The default port is 3483.
-p, --predelay <msec>: Sets a delay before any playback is started. This
is useful if the DAC used for output is slow to
wake-up/lock, causing the first few samples to be
dropped.
--retry Causes the program to retry connecting to
SqueezeCenter until it succeeds or is stopped using
SIGTERM or keyboard entry (see -s/--signal).
If the connection to SqueezeCenter is lost, the
program will poll it until it restarts. --retry
enables retry with a 5 second delay between
attempts.
-r <sec> For a different retry interval use -r and the
desired interval in seconds. (ie. -r10)
A value is required for this option.
-s, --signal: Ignored. Always uses SIGTERM to exit.
-V, --version: Prints the squeezeslave version.
-v, --volume <sw|off>: Enables/disables volume changes done by
SqueezeCenter during its operation, such as when
changing the volume through the web interface or
when applying replay gain. Defaults to sw.
sw: volume changes performed in software.
off: volume changes ignored.
-Y, --debuglog <logfile>: Redirect debug output from stderr to <logfile>.
-d, --debug <trace_name>: Turns on debug tracing for the specified level.
The option can be used multiple times to enable
multiple levels.
Available levels:
all
slimproto
slimaudio
slimaudio_buffer
slimaudio_buffer_v
slimaudio_decoder
slimaudio_decoder_r
slimaudio_decoder_v
slimaudio_http
slimaudio_http_v
slimaudio_output
slimaudio_output_v</pre>

==Troubleshooting==

If you use a USB audio card and squeezeslave gives you an error, try the following

First of all make sure you are running the latest version.

Edit your /etc/asound.conf and add the following

<pre>pcm.usb_analog {
type asym
playback.pcm "plug:dmix:1"
capture.pcm "plughw:1"
}</pre>

After this restart alsa

/etc/init.d/alsa-utils restart

check your alsamixer to make sure pcm is unmuted and on a good level

Try squeezeslave again
== Information from other places ==
The slimdevices forum has a nice [http://forums.slimdevices.com/showthread.php?86253-Poor-Man-s-Multiroom-Audio post] on how to setup multiple Squeezeslave zones with a single soundcard.

In case the above link does not work anymore, there is a [http://deb.linuxmce.org/PoorMansMultiroomAudio.pdf PDF] output of said forum entry available.

Squeezeslave on the core

2013-01-16T10:20:05Z

Esperanto: /* Select Device */

[[Category: Tutorials]]
[[Category:Audio]]
{| align="right"
| __TOC__
|}
==Whats does it do?==
Squeezeslave basically makes it possible to add additional 'virtual' Squeezeboxes to your Core or MD's just by adding additional sound-cards. Each Squeezeslave/Sound-card combo uses about 4-5% CPU on an ATOM/Ion based MD. We have tested an ATOM/Ion based MD running 3 x Squeezeslave/Sound-Card combo's while playing a ripped DVD from the Core without any problems at all. Using Squeezeslave/Sound-Card combo's makes it possible to have several independent audio outputs from your Core or from an MD allowing you to use the 2nd Zone of your Surround Amp for example to provide audio to an adjoining room eg a bathroom or maybe a kitchen. All of this expands the options you have when designing your system, gives you enormous additional flexibility to locate additional audio sources where you need them, and reduces the energy footprint of your system at the same time (in comparison to adding additional physical Squeezeboxes).

==Squeezeslave Setup==
Here's how to setup squeezeslave to run on your core or in fact any of your MD's. It's fairly straight forward but currently requires manual config/install of each Squeezeslave - I'm working on making this something you can just configure from Web Admin simply and quickly. One small issue is that because squeezeslave uses the OSS interface, you will need a separate sound card for each instance of squeezeslave you want to run.

==Hardware Supported==
The Startech Virtual 7.1 USB Audio Adapter (model No. ICUSBAUD107) works fine. This tiny USB Stick style adapter works perfectly under 7.10, 9.10 & 10.04. No installation...just plug it in and its ready a few secs later. Only stereo out jack and Mic input jack.

Many other brands of USB Audio adapter will probably work too. Please add your experiences with other working hardware here too.

Under LinuxMCE 0810 it may be necessary to downgrade Alsa in order for the device to appear (in 'aplay -l' or 'squeezeslave -L'). Be aware that downgrading alsa will remove audio over hdmi capabilities on the affected computer.

===Setting Up Squeezeslave on your Core or MD's===
If you want to setup Squeezeslave on your Core then either open Konsole session from the KDE Desktop or ssh in from another machine and sudo yourself. If you want to set up Squeezeslave on an MD then ssh into your Core and then use;

ssh moonNNN (**where NNN is the ID number of the MD you want to ssh into.)

You can find the ID of your MD from the Web Admin page at Wizard->Devices->Media Directors and the ID is the number with a '#' in front of it at the top of each MD section. Now follow the instructions below for each MD you want to add Squeezeslave too.

===Needed Dependencies===
System libraries needed are subversion and libasound2-dev
sudo apt-get install subversion
sudo apt-get install libasound2-dev
Since squeezeslave is only updating the display versions of their makefiles also needed for building
sudo apt-get install libncurses5-dev
sudo apt-get install liblircclient-dev

===Squeezeslave is available in the debs===
Easiest for anybody will be
sudo apt-get install squeezeslave
This will install squeezeslave in the right directory for you to use. If you want to build it yourself follow the next steps.

===Typical build===
svn checkout http://squeezeslave.googlecode.com/svn/squeezeslave/trunk/squeezeslave
cd squeezeslave
make -f makefile.linux26-alsa-display realclean
make -f makefile.linux26-alsa-display

===Or Download Source / look at the squeezeslave wiki===
Download a version of [http://sourceforge.net/project/showfiles.php?group_id=105169 Squeezeslave]. I'm running the latest version which was 0.9-173

Look at the slimdevices wiki for the latest options and install instructions http://wiki.slimdevices.com/index.php/SqueezeSlave

===Installing===
*You'll want to put it somewhere in your path. (This is already done if you did the apt-get install method)
*There will be a file in the /bin directory called squeezeslave (there might be something added to this to represent the version you build, just rename the file to squeezeslave and copy to your wanted directory
*Example: /usr/bin
====Modify /etc/rc.local====
Next add the following to /etc/rc.local

If your setting up Squeezeslave on your Core then use;
/usr/bin/squeezeslave -o4 -m00:00:00:00:00:01 -r5 -M/var/log/squeezeslave.log

If your setting up Squeezeslave on one of your MD's then use;
/usr/bin/squeezeslave -o4 192.168.80.1 -m00:00:00:00:00:01 -r5 -M/var/log/squeezeslave.log

* the IP address should be the IP address of your Core (**Only needed if your running Squeezeslave on MD's**).
* the MAC address can be whatever you want, it just needs to be the same as the device created in linux mce
* the -o option specifies which output device ie /dev/dsp1 (check with "squeezeslave -L" for available devices then use '-oN' where 'N' is the number next to your output device)
See example output using 'squeezeslave -L' below;

<pre>Output devices:
0: (ALSA) SB Live! Value [CT4832]: ADC Capture/Standard PCM Playback (hw:0,0) (11/46)
2: (ALSA) SB Live! Value [CT4832]: Multichannel Capture/PT Playback (hw:0,2) (10/42)
3: (ALSA) SB Live! Value [CT4832]: Multichannel Playback (hw:0,3) (10/42)
4: (ALSA) USB Audio Device: USB Audio (hw:1,0) (10/42)
5: (ALSA) front (11/46)
6: (ALSA) rear (11/46)
7: (ALSA) center_lfe (11/46)
8: (ALSA) surround40 (11/46)
9: (ALSA) surround41 (11/46)
10: (ALSA) surround50 (11/46)
11: (ALSA) surround51 (11/46)
12: (ALSA) iec958 (10/42)
13: (ALSA) spdif (10/42)
14: (ALSA) spdif_playback (11/46)
15: (ALSA) asym_spdif (11/46)
17: (ALSA) asym_analog (42/46)
18: (ALSA) usb_analog (42/46)
19: (ALSA) dmix (42/42)
*20: (ALSA) default (42/46)</pre>

I am using the No.18 device in the output above and therefore would use '-o18' switch when using the squeezeslave command.

* the -r option tells squeezeslave to keep retrying to connect to the server, useful if the server is not running yet.
* the -M option makes it run as a Daemon and creates log

====Fixing sample rate issues====
Squeezeslave only likes the 44.1 kHz sample rate. Anything lower will sounds like the Smurfs, anything higher will sound "slow". This is fixed by converting the source stream to something squeezeslave can cope with.

You need to edit the /etc/squeezeboxserver/convert.conf file so it has these lines in it:

mp3 flc squeezeslave *
[sox] -q -t mp3 $FILE$ -t flac -C 0 -r 44100 -
aac flc squeezeslave *
[faad] -q -w -f 1 $FILE$ | [flac] -cs --totally-silent --compression-level-0 --ignore-chunk-sizes - | [sox] -q -t flac - -t flac -C 0 -b 16 -r 44100 -

The aac to flc conversion could be shorter, but sox has a problem with '-t wav' with the output of faad and outputs an empty stream, and flac won't actually resample the stream when the --sample-rate=44100 parameter is given to it.

More conversions might be necessary as new stations are found to be problematic, but the strategy is the same: Convert to 'flac', resample to 44100 Hz.

You'll have to restart Squeezebox Server (Logitech Media Server) for the change to take effect.

===Setting Up Alsamixer===
Next make sure all the volume levels in the mixer (alsamixer) are set correctly
alsamixer
Make sure that the settings are as desired and save (Esc button)
===Setting Up LinuxMCE===

Next step, manually add the squeezeslave to linuxmce as a squeezebox using the mac address you gave it. The squeezebox player can be assigned to a room/entertainment area without an MD, in fact this would be a typical installation.

====Select Device====
* Select '''Wizard->Devices->A/V Equipment'''
* Select SqueezeBox Player from the dropdown options
* Assign it to a room and entertainment area.
* Regen your orbiters and reload the router.

Restart the core to make sure it's starting automatically, to run it manually just run the line made in the rc.local

/usr/bin/squeezeslave -o5 -m 00:00:00:00:00:01 -r5 -M/var/log/squeezeslave.log

* Check with ps if it is running:
ps aux | grep squeezeslave
**Example output:
root 11502 0.0 0.8 51484 8812 ? SLl Apr07 0:33 /usr/bin/squeezeslave -05 -m00:00:00:00:00:02 -r5 -M/var/log/squeezeslave

That should do it.

use /usr/bin/squeezeslave -L for available audio devices

use /usr/bin/squeezeslave -h for a list of options (see below)

<pre>/usr/bin/squeezeslave -h
squeezeslave 0.9-143
compile flags: linux portaudio:1485 debug signals daemon

Squeezeslave is licensed free of charge. There is NO WARRANTY for
the program. This program is provided "as is" without warranty of
any kind, either expressed or implied, including, but not limited
to, the implied warranties of merchantability and fitness for a
particular purpose. The entire risk as to the quality and
performance of the program is with you. Should the program prove
defective, you assume the cost of all necessary servicing, repair
or correction.

Copyright (c) 2004-2007 Richard Titmuss,
2008-2010 Duane Paddock.

squeezeslave [options] [<server address>]
The Squeezebox Server address defaults to 127.0.0.1.
Options:
-h, --help: Prints this message.
-a, Sets the amplitude of a high-frequency tone
--predelay_amplitude <val>: produced during the predelay (see --predelay).
The frequency is set at the source's sampling
rate/2 and the amplitude is in absolute value.
For 16-bit sources, the max is 32767, but values
below 10 are likely to work. The goal is to
produce an inaudible signal that will cause DACs
to wake-up and lock before actual samples are
played out. If the DAC locks using only silence,
do not use this option (it will default to 0).
-k, --keepalive <sec>: Controls how frequently squeezeslave sends a
alive signal to SqueezeCenter. 6.5.x servers
need this to avoid dropping the player's
connection. By default, the implementation
chooses the right value: 10s for a >=6.5.x server
and 0s for a <6.5.x server, which means no
keepalive.
-M, --daemonize <logfile> Run squeezeslave as a daemon.
Messages written to specified file.
Not supported with lirc and display modes.
-L, --list List available audio devices and exit.
-m, --mac <mac_address>: Sets the mac address for this instance.
Use the colon-separated notation.
The default is 00:00:00:00:00:01.
SqueezeCenter uses this value to distinguish
multiple instances, allowing per-player settings.
-o, --output <device_id>: Sets the output device id.
The default id is 0.
The output device ids can be found with -L.
-P, --port <portnumber>: Sets the SqueezeCenter port number.
The default port is 3483.
-p, --predelay <msec>: Sets a delay before any playback is started. This
is useful if the DAC used for output is slow to
wake-up/lock, causing the first few samples to be
dropped.
--retry Causes the program to retry connecting to
SqueezeCenter until it succeeds or is stopped using
SIGTERM or keyboard entry (see -s/--signal).
If the connection to SqueezeCenter is lost, the
program will poll it until it restarts. --retry
enables retry with a 5 second delay between
attempts.
-r <sec> For a different retry interval use -r and the
desired interval in seconds. (ie. -r10)
A value is required for this option.
-s, --signal: Ignored. Always uses SIGTERM to exit.
-V, --version: Prints the squeezeslave version.
-v, --volume <sw|off>: Enables/disables volume changes done by
SqueezeCenter during its operation, such as when
changing the volume through the web interface or
when applying replay gain. Defaults to sw.
sw: volume changes performed in software.
off: volume changes ignored.
-Y, --debuglog <logfile>: Redirect debug output from stderr to <logfile>.
-d, --debug <trace_name>: Turns on debug tracing for the specified level.
The option can be used multiple times to enable
multiple levels.
Available levels:
all
slimproto
slimaudio
slimaudio_buffer
slimaudio_buffer_v
slimaudio_decoder
slimaudio_decoder_r
slimaudio_decoder_v
slimaudio_http
slimaudio_http_v
slimaudio_output
slimaudio_output_v</pre>

==Troubleshooting==

If you use a USB audio card and squeezeslave gives you an error, try the following

First of all make sure you are running the latest version.

Edit your /etc/asound.conf and add the following

<pre>pcm.usb_analog {
type asym
playback.pcm "plug:dmix:1"
capture.pcm "plughw:1"
}</pre>

After this restart alsa

/etc/init.d/alsa-utils restart

check your alsamixer to make sure pcm is unmuted and on a good level

Try squeezeslave again
== Information from other places ==
The slimdevices forum has a nice [http://forums.slimdevices.com/showthread.php?86253-Poor-Man-s-Multiroom-Audio post] on how to setup multiple Squeezeslave zones with a single soundcard.

In case the above link does not work anymore, there is a [http://deb.linuxmce.org/PoorMansMultiroomAudio.pdf PDF] output of said forum entry available.

Firewall Rules

2012-07-31T14:11:50Z

Esperanto: /* Limit IP */

{{versioninfo|810Status=relevant|810UpdatedDate=21 Aug 2011|810UpdatedBy=[[User:Foxi352|Foxi352]]|1004Status=relevant|1004UpdatedDate=21 Aug 2011|1004UpdatedBy=[[User:Foxi352|Foxi352]]}}
[[Category:Admin Website]]
[[Category:Networking]]
[[Category:Tutorials]]

[[Image:Firewall.jpg|thumb|200px|Firewall Rules Admin Page]]

This page allows you to customize your firewall rules, even disabling the firewall. When first opened you will notice that there are several predefined rules already in place.

==Options==
[[Image:FirewallOptions.jpg]]

===Protocol===
Here is where you can choose the protocol involved with this rule, or define any protocol by choosing 'IP':
* [http://en.wikipedia.org/wiki/Transmission_Control_Protocol TCP]
* [http://en.wikipedia.org/wiki/User_Datagram_Protocol UDP]
* [http://en.wikipedia.org/wiki/List_of_IP_protocol_numbers IP]

===IP version===
Here you can choose if you want the rule to be active for IPv4, IPv6 or both.

===Source Ports===
Choose the Ports to be used in the rule. If you chose 'IP' in the Protocol section then you can define your IP protocol (NOT PORT !!!) number here.

===Destination Port===
Port to forward requests to.

''This option is only available if Port Forwarding is selected in the Rule Type''

===Destination IP===
IP Address of the computer being forwarded to.

''This option is only available if Port Forwarding is selected in the Rule Type''

===Rule Type===
There are two types of rules available:
* Core Input
* Port Forward

===Limit IP===
You can limit rules to specific IP addresses.

It looks like you can add the mask to specify ranges: 134.78.0.0/16

Internet Radio

2012-02-19T09:58:09Z

Esperanto: /* How to use */

{{versioninfo|710Status=Working|710UpdatedDate=13th Oct 2010|710UpdatedBy=[[User:cht_winston|cht_winston]]|810Status=Working|810UpdatedDate=23rd June 2010|810UpdatedBy=Metoer|1004Status=Working|1004UpdatedDate=14th Oct 2011|1004UpdatedBy=sambuca}}
[[Category: Tutorials]][[Category:Internet Streaming]]
= 1004 =
== Overview ==
The Radio scenario is added automatically and lists audio streams by genre.

== How to use ==
To add streams to the database, go to the Web Admin -> Files & Media -> Media Browser. In the left section, you will find a "Add new" link. Clicking on this will open the normal file view screen in the right pane, and allow you to add a new file. (This can be any file, it does not have to be a stream).

If you are adding an audio stream, be sure to set the type to "LinuxMCE streamed Audio".
Enter the URL into the file input box and press 'add' to save it. Then the saved item appears. Add at least one genre and one channel name attribute. Those attributes are expected by LinuxMCE and should always be added. The path field is not used.

When going to a orbiter, you should now see all genres containing any streamed audio items. Selecting a genre will list all channels in that genre. Selecting a channel will open the file detail screen and allows you to press play to play the stream.

== Limitations ==
The Xine player currently does not support playlists, so adding a URL to a playlist will not work. You have to find the URL to the stream itself.

= Older releases (810/710) =
Older releases does not have any direct support for the Internet Radio station list. However, you can create the scenario shortcut to quick-start your favorite station.

Here is a link to a page with a few stations that you can choose from, I tried a couple and they all seemed to work with this wiki.
http://slhungary.hu/print.php?plugin:content.40

* Go to [[LinuxMCE Admin Website]] --> Advanced --> Configuration --> Scenarios --> Media Scenarios" and press "Add My Scenario" button.

* Under "Add My Scenario" type a description, like "DI - Lounge". Check in which room you want this scenario to appear. Press "Save".

* Click on the description of the scenario that you've just added.

* In "Scenario commands" select "Media Plug-in" from the "Device:" drop-down and "MH Play Media" from the "Command:" drop-down. Press the "Add" button.

# In the "#13 Filename (string)" field type the URL of your online radio station ( e.g.: http://scfire-chi0l-1.stream.aol.com/stream/1009 ).
# In the "#29 PK_MediaType (int)" type 4.
# In the "#45 PK_EntertainArea (string)" put the number of the Entertaining Area (it usually starts from 1, see the note below). Press the "Save" button and the "Test Command" to see if it works.

* Do a [[quick reload router|Quick Reload]] & [[Orbiter Generator|Regen]] and you'll be able to see you radio on the media menu of your Orbiter. Click on the button and it should start playing.

==Where to Find Compatible Internet Radio Stations==

If you're in the U.S. like me, you'll probably have a hard time finding "direct URLs" that you can create scenarios with that are compatible with LMCE. Like many of you, I wanted to use ShoutCast stations, however, ShoutCast has changed their webpage in such a way that it will open up it's own propreitary plug-in that doesn't provide you with the actual station's direct URL. Useless, if you want to create a new station scenario in LMCE.

I recommend doing the following:

1. Download WinAmp onto a Windows Box

2. Open up WinAmp and browse to your favorite Station (I use shoutcast stations)

3. Right click on the Winamp window where it lists what you're currently listening to

4. Click "View File Info"

5. This will provide the direct URL link you'll need to include in the steps below when you're creating your stations.

* I hope this helps... I had a hard time finding useful information on where to go to actually get "legitimate" direct URLs for Internet Radio Stations.

==Notes and troubleshooting==

* The media type "4" corresponds to a workaround, MEDIATYPE_pluto_StoredAudio_CONST. When all stuff eventually works, it will be changed to the "6" (MEDIATYPE_pluto_LiveRadio_CONST)

* If radio station playback doesn't start - try playing it a couple times more. There is an issue in xine-lib which sometimes causes it to fail the first time.

* Be sure not to put the URL of the playlist in "#13 Filename" parameter - it should be the URL of the station itself. Playlist URLs usually end with ".m3u" and ".pls". Download the playlist and get the URL of station from it (there can be many entries, each representing a mirror).

* If you have issues identifying your Entertainment Area ID, you can query the DB directly:
:* At the terminal, start the mysql commandline:
mysql -u root -p pluto_main <enter>
:then issue the following query
mysql> SELECT PK_EntertainArea, Description FROM EntertainArea;
:*Select the ID of the desired area from the list:
+------------------+------------------+
| PK_EntertainArea | Description |
+------------------+------------------+
| 1 | Bedroom (Master) |
+------------------+------------------+
1 row in set (0.00 sec)
:type 'quit' to exit:
mysql> quit <enter>

HTTPS

2011-04-01T18:03:03Z

Esperanto: listen not in the ports.conf ?? so added remark

[[Category: Development]]
= HTTPS / SSL access on the outside =

I am trying to setup https on the outside so Linuxmce can be used safely. Below is my setup.

We start by creating a new password file (-c option) and adding a user (linux) with a password (test) to the password file:

htpasswd -bc /etc/apache2/httpd.passwd linuxmce test

(Use the same line without the -c to add additional users)

mkdir /root/ssl
openssl genrsa -des3 -out /root/ssl/server.key 4096

(type a passwd twice)

openssl req -new -key /root/ssl/server.key -out /root/ssl/server.csr

(type your previous passwd once and then fill in the fields)

Make sure that "Common Name (eg, YOUR name)" matches the registered fully qualified domain name of your box (or your IP address if you don't have one).

openssl x509 -req -days 3650 -in /root/ssl/server.csr -signkey /root/ssl/server.key -out /root/ssl/server.crt

openssl rsa -in /root/ssl/server.key -out /root/ssl/server.key.insecure
mv /root/ssl/server.key /root/ssl/server.key.secure
mv /root/ssl/server.key.insecure /root/ssl/server.key

You now have the following files in /root/ssl:

server.crt: The self-signed server certificate.
server.csr: Server certificate signing request.
server.key: The private server key, does not require a password when starting Apache.
server.key.secure: The private server key, it does require a password when starting Apache.

mkdir /etc/apache2/ssl
cp /root/ssl/server.key /etc/apache2/ssl
cp /root/ssl/server.crt /etc/apache2/ssl

add the following in /etc/apache2/httpd.conf

<pre>
SSLCertificateFile /etc/apache2/ssl/server.crt
SSLCertificateKeyFile /etc/apache2/ssl/server.key

<LocationMatch "/*">
# Inside the subarea any Intranet access is allowed
# but from the Internet only HTTPS + Strong-Cipher + Password
# or the alternative HTTPS + Strong-Cipher + Client-Certificate

# If HTTPS is used, make sure a strong cipher is used.
# Additionally allow client certs as alternative to basic auth.
SSLVerifyClient optional
SSLVerifyDepth 1
SSLOptions +FakeBasicAuth +StrictRequire
SSLRequire %{SSL_CIPHER_USEKEYSIZE} >= 128

# Force clients from the Internet to use HTTPS
#RewriteEngine on
#RewriteCond %{REMOTE_ADDR} !^192\.168\.80\.[0-9]+$
#RewriteCond %{HTTPS} !=on
#RewriteRule ^/(.*) https://%{SERVER_NAME}/$2 [R,L]

# Allow Network Access and/or Basic Auth
Satisfy any

# Network Access Control
Order deny,allow
Deny from all
Allow from 192.168.80.0/24 127.0.0.1

# HTTP Basic Authentication
AuthType basic
AuthName "LinuxMCE"
AuthUserFile /etc/apache2/httpd.passwd
Require valid-user

</LocationMatch>

# Since mythweb has it's own rewrites in a .htaccess file https redirection is enabled only on other urls
<LocationMatch "^/(?!mythweb).*">
# Force clients from the Internet to use HTTPS
RewriteEngine on
RewriteCond %{REMOTE_ADDR} !^192\.168\.80\.[0-9]+$
RewriteCond %{REMOTE_ADDR} !^127\.0\.0\.[0-9]+$
RewriteCond %{HTTPS} !=on
RewriteRule ^/(.*) https://%{SERVER_NAME}/$2 [R,L]
</LocationMatch>

</pre>

On the top of httpd.conf add the fully qualified domain name of your box that you added by "Common Name (eg, YOUR name)" when creating the certificate:

ServerName linuxmce.yourdomain.com

we have to change the beginning of vi /etc/apache2/sites-available/pluto to:
<pre>
# NameVirtualHost *
<VirtualHost _default_:80>
</pre>

and then copy this file:
cp /etc/apache2/sites-available/pluto /etc/apache2/sites-available/pluto443

then change the beginnig to:
<pre>
# NameVirtualHost *
<VirtualHost _default_:443>
SSLEngine On
</pre>

make a symbolic link:
ln -s /etc/apache2/sites-available/pluto443 /etc/apache2/sites-enabled/pluto443

move the original ssl configuration out of the way (to your home dir):
mv /etc/apache2/sites-available/default-ssl ~/
rm /etc/apache2/sites-enabled/default-ssl

make sure that apache is listening on port 443 and the following line is in /etc/apache2/ports.conf:
Listen 443

go to pluto web admin and to Advanced>Network>Firewall and add a new rule:
tcp ipv4 443 443 core_input

then run:

apache2ctl restart

HTTPS

2011-03-12T17:38:57Z

Esperanto: changes because ssl is enabled by default

[[Category: Development]]
= HTTPS / SSL access on the outside =

I am trying to setup https on the outside so Linuxmce can be used safely. Below is my setup.

We start by creating a new password file (-c option) and adding a user (linux) with a password (test) to the password file:

htpasswd -bc /etc/apache2/httpd.passwd linuxmce test

(Use the same line without the -c to add additional users)

mkdir /root/ssl
openssl genrsa -des3 -out /root/ssl/server.key 4096

(type a passwd twice)

openssl req -new -key /root/ssl/server.key -out /root/ssl/server.csr

(type your previous passwd once and then fill in the fields)

Make sure that "Common Name (eg, YOUR name)" matches the registered fully qualified domain name of your box (or your IP address if you don't have one).

openssl x509 -req -days 3650 -in /root/ssl/server.csr -signkey /root/ssl/server.key -out /root/ssl/server.crt

openssl rsa -in /root/ssl/server.key -out /root/ssl/server.key.insecure
mv /root/ssl/server.key /root/ssl/server.key.secure
mv /root/ssl/server.key.insecure /root/ssl/server.key

You now have the following files in /root/ssl:

server.crt: The self-signed server certificate.
server.csr: Server certificate signing request.
server.key: The private server key, does not require a password when starting Apache.
server.key.secure: The private server key, it does require a password when starting Apache.

mkdir /etc/apache2/ssl
cp /root/ssl/server.key /etc/apache2/ssl
cp /root/ssl/server.crt /etc/apache2/ssl

add the following in /etc/apache2/httpd.conf

<pre>
SSLCertificateFile /etc/apache2/ssl/server.crt
SSLCertificateKeyFile /etc/apache2/ssl/server.key

<LocationMatch "/*">
# Inside the subarea any Intranet access is allowed
# but from the Internet only HTTPS + Strong-Cipher + Password
# or the alternative HTTPS + Strong-Cipher + Client-Certificate

# If HTTPS is used, make sure a strong cipher is used.
# Additionally allow client certs as alternative to basic auth.
SSLVerifyClient optional
SSLVerifyDepth 1
SSLOptions +FakeBasicAuth +StrictRequire
SSLRequire %{SSL_CIPHER_USEKEYSIZE} >= 128

# Force clients from the Internet to use HTTPS
#RewriteEngine on
#RewriteCond %{REMOTE_ADDR} !^192\.168\.80\.[0-9]+$
#RewriteCond %{HTTPS} !=on
#RewriteRule ^/(.*) https://%{SERVER_NAME}/$2 [R,L]

# Allow Network Access and/or Basic Auth
Satisfy any

# Network Access Control
Order deny,allow
Deny from all
Allow from 192.168.80.0/24 127.0.0.1

# HTTP Basic Authentication
AuthType basic
AuthName "LinuxMCE"
AuthUserFile /etc/apache2/httpd.passwd
Require valid-user

</LocationMatch>

# Since mythweb has it's own rewrites in a .htaccess file https redirection is enabled only on other urls
<LocationMatch "^/(?!mythweb).*">
# Force clients from the Internet to use HTTPS
RewriteEngine on
RewriteCond %{REMOTE_ADDR} !^192\.168\.80\.[0-9]+$
RewriteCond %{REMOTE_ADDR} !^127\.0\.0\.[0-9]+$
RewriteCond %{HTTPS} !=on
RewriteRule ^/(.*) https://%{SERVER_NAME}/$2 [R,L]
</LocationMatch>

</pre>

On the top of httpd.conf add the fully qualified domain name of your box that you added by "Common Name (eg, YOUR name)" when creating the certificate:

ServerName linuxmce.yourdomain.com

we have to change the beginning of vi /etc/apache2/sites-available/pluto to:
<pre>
# NameVirtualHost *
<VirtualHost _default_:80>
</pre>

and then copy this file:
cp /etc/apache2/sites-available/pluto /etc/apache2/sites-available/pluto443

then change the beginnig to:
<pre>
# NameVirtualHost *
<VirtualHost _default_:443>
SSLEngine On
</pre>

make a symbolic link:
ln -s /etc/apache2/sites-available/pluto443 /etc/apache2/sites-enabled/pluto443

move the original ssl configuration out of the way (to your home dir):
mv /etc/apache2/sites-available/default-ssl ~/
rm /etc/apache2/sites-enabled/default-ssl

go to pluto web admin and to Advanced>Network>Firewall and add a new rule:
tcp 443 443 core_input

then run:

apache2ctl restart

Installing 0810

2011-03-07T17:58:11Z

Esperanto: added apt-get install mediabuntu-keyring

Installing LinuxMCE-0810 is a fairly easy process that involves:
* Installing Kubuntu 8.10
* Updating Kubuntu 8.10
* Installing LinuxMCE-0810 on top of the updated Kubuntu 8.10

Before proceeding its wise to read the FAQ.
Because of the fact that its a delicate installation small things make a huge difference.

Please see below for details on Internet Installation and DVD Installation methods.

'''Note: an active internet connection is required regardless of installation method.

==Internet Installation==
# Install Kubuntu Intrepid desktop and update it. (download Kubuntu 8.10 '''desktop''' release from http://old-releases.ubuntu.com/releases/kubuntu/8.10/kubuntu-8.10-desktop-i386.iso) '''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.''' Note: If Kubuntu asks whether you would like to install/activate 'Restricted Drivers' for your video card, ignore it and continue to step 2.
# Edit your /etc/apt/sources.list file to contain only (from post http://forum.linuxmce.org/index.php?topic=10917.15 ):
deb http://old-releases.ubuntu.com/ubuntu/ intrepid main restricted universe multiverse
deb-src http://old-releases.ubuntu.com/ubuntu/ intrepid main restricted universe multiverse
deb http://old-releases.ubuntu.com/ubuntu/ intrepid-updates main restricted universe multiverse
deb-src http://old-releases.ubuntu.com/ubuntu/ intrepid-updates main restricted universe multiverse
deb http://deb.linuxmce.org/ubuntu/ intrepid beta2
deb http://debian.slimdevices.com/ stable main
deb http://packages.medibuntu.org/ intrepid free non-free
deb http://old-releases.ubuntu.com/ubuntu/ intrepid-security main restricted universe multiverse
deb-src http://old-releases.ubuntu.com/ubuntu/ intrepid-security main restricted universe multiverse
deb http://old-releases.ubuntu.com/ubuntu/ intrepid main universe multiverse
deb http://deb.linuxmce.org/ubuntu/ replacements_debian main
deb http://deb.linuxmce.org/ubuntu/ 20dev_ubuntu main
# Run aptitude update and aptitude dist-upgrade to get the latest Kubuntu updates.
# Install medibuntu keyring: apt-get install medibuntu-keyring
# 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:
sudo su - #This might ask for the password you specified earlier during the install of kubuntu.
apt-get update
sudo apt-get dist-upgrade
apt-get install medibuntu-keyring
wget -c http://deb.linuxmce.org/ubuntu/new-installer-latest.tar.gz
tar xvf new-installer-latest.tar.gz
cd new-installer
./pre-install-from-repo.sh
./mce-install.sh
./post-install.sh
reboot

The avenard repo is no longer needed.

==DVD Installation==

However, if you want to install the DVD, grab it via the torrent [http://www.linuxmce.org/index.php/download here] or if you want use the following link to obtain the latest [http://linuxmce.iptp.org/snapshots/ snapshot] '''Highly recommended'''

'''Upon DVD boot, select LinuxMCE install(it is the bottom option)'''. This will install a regular Kubuntu 810 system, with an additional button on the desktop to install LinuxMCE upon restart. Let Kubuntu's install run through, and after restart, login.
Open a terminal and run
sudo su - #This might ask for the password you specified earlier during the install of kubuntu.
apt-get update
sudo apt-get dist-upgrade

Once you have done this, you can go to the Desktop and double click on the LinuxMCE icon. This will run the fullinstall.sh in /root/new-installer and install LinuxMCE-0810 on top of you updated Kubuntu installation.

'''Note''': Once the above process is complete - the [http://wiki.linuxmce.org/index.php/AVWizard_Step_by_Step AV Wizard] should start (after rebooting). If you get a ''black or blank screen'' you probably need to change your video card outputs. Instructions on how to do this are available: [http://wiki.linuxmce.org/index.php/AVWizard#What_to_do_if_A.2FV_Wizard_does_not_start here]

The DVD installer per default does not create the initial [[MD|MD]] image, as that creation takes a very long time, and most people probably prefer to give 810 a test, without the MDs. If you want to setup MDs, you have to manually run
/usr/pluto/bin/Diskless_CreateTBZ.sh
(You should only have to do this once)

If you have problems running Diskless_CreateTBZ.sh, check [[Error Running Diskless CreateTBZ.sh|this article]].

If you then have problems netbooting your diskless media directors because you are receiving the error message "Diskless Setup Failed", check [[Diskless setup failed error in 0810 beta|this article]].

== Keeping Up-to-date with updates ==
'''Note''' It is strongly recommend that you do not update/upgrade a stable, working system [[user:L3mce]]

Once you have installed LinuxMCE-0810, all you need to do to keep up-to-date with the latest and greatest, is run the following from a terminal on the core and each MD:
sudo apt-get update
sudo apt-get upgrade
Note: You should NOT run apt-get dist-upgrade after LinuxMCE is installed, as it can cause several problems, including having different kernel versions on your core and media directors, and the installation of new Kubuntu packages that can break some features!

[[Category:Tutorials]]

PLCBUS

2010-10-16T11:55:14Z

Esperanto:

{{versioninfo|810Status=Not Working|810UpdatedDate=1st May 2010|810UpdatedBy=BongoWongo}}
[[Category: Automation]]
[[Category: Power Line Control]]
[[Category: 0810]]
{| align="right"
| __TOC__
|}
[[Image:Plcbus-logo.jpg|right]]
= Status =
ddamron wrote a GSD for PLCBUS with ruby. Hari will try to get a c++ dce client running.

= About =
PLCBUS Technology provides you the most perfect Home Automation solutions. Control one lamp minimally to the whole house, all the PLCBUS products range is including Lamp control, Appliance control, Remote telephone control, Computer control and Security System control.
Based on the features: “High Reliability”, “Two-Way Communications”, “No rewiring necessary”, etc, PLCBUS Technology will be new Home Automation standard in the following 10-15 years.

See the following setup page for details on how to get running.
[[Setting Up PLC-BUS Template]]

==Demo video:==
* http://www.x10-hk.com/store/download/plcbus-1.mp4

= Features =
* Reliability
* 2-way communication
* Powerline, no rewiring
* ~200bps
* 230V/50hz

= Interfaces =
* http://x10-hk.com/store/product_info.php?products_id=165
* http://www.elekhomica.nl/product_info.php?cPath=135&products_id=757

= Command specification =
* http://x10-hk.com/store/manual/plcbus/plcbus-1141.pdf

= GSD/Ruby Code =
* [[ThreadedRuby]]
* http://wiki.linuxmce.org/index.php/PLCBUScmd776 Reset (used for testing)
* http://wiki.linuxmce.org/index.php/PLCBUScmd373 Private Method Listing
* http://wiki.linuxmce.org/index.php/PLCBUScmd350 Process INCOMING Data Listing
* http://wiki.linuxmce.org/index.php/PLCBUScmd351 Process IDLE Listing
* http://wiki.linuxmce.org/index.php/PLCBUScmd355 Process Initialize Listing
* http://wiki.linuxmce.org/index.php/PLCBUScmd384 Process Receive Command for Child Listing
* http://wiki.linuxmce.org/index.php/PLCBUScmd760 Send Command to Child (before init)
* http://wiki.linuxmce.org/index.php/PLCBUScmd776 Status Report (used for testing)
* http://wiki.linuxmce.org/index.php/PLCBUScmd756 Report Child Devices (nothing yet)

= Links =
* http://www.plcbus.com.cn/
* http://www.futurehomes.com.sg/PLCBUSinfo.htm

VDR

2010-06-01T19:39:57Z

Esperanto: /* Installation */

{| align="right"
| __TOC__
|}
[[Category:Software components]]
[[Category:Video]]
[[Category:Tutorials]]
= The Video Disk Recorder =
VDR is a [[personal video recorder]] system aimed at the DVB market. It supports DVB-S, DVB-C and DVB-T tuner cards. More details can be found at the [http://www.cadsoftusa.com/vdr/ VDR homepage].

It is the second PVR system integrated into LinuxMCE. The main aim is for a seamless integration into LinuxMCE. The UI should not change between VDR and the other LinuxMCE pieces. The first version of this integration wass scheduled for January 2008, and is mainly sponsored by [http://www.dianemo.co.uk Convergent Home Technologies Ltd].

== Configuration ==

Recently I managed to setup VDR under LinuxMCE successfully. This brief howto is a result of my personal experience. Don't hesitate to improve it.

===Installation===

VDR should be selected using the setup wizard. If you did not select VDR during the initial configuration after installation, simply re-run the wizard (it's on the Advanced menu) and select VDR as the PVR. VDR will be installed automatically and will start after installation.

[[Image:LMCE-software-modules.jpg|thumb|550px|left|LinuxMCE Software Modules]]
 
To make VDR configuration and manage easier its web interface - VDRAdmin can be used. It should be installed manually:

sudo apt-get install vdradmin-am

and then enabled to be able run by replacing ENABLED="0" by ENABLED="1" in the /etc/default/vdradmin-am. Also don't forget to add a new firewall rule for the port 8001 - Advanced -->> Network --> Firewall Rules.

=== Scanning for Channels ===

To enable scanning for channels the DVB utilities package should also installed manually:

sudo apt-get update

then do

sudo apt-get install dvb-utils

==== Scanning for DVB-T Channels ====

Firstly we need to stop VDR before we scan for channels;

sudo /etc/init.d/vdr stop

Above we installed the dvb-utils package and this will have installed the scan utility and tuning files for many DVB transmitters in various regions. Look for a transmitter in your region by looking in the following directory;

ls /usr/share/doc/dvb-utils/examples/scan/dvb-t

You should now see something like this on your console;

au-Adelaide fi-Ahtari fi-Taivalkoski se-Borlange se-Uddevalla
au-Brisbane fi-Ala-Vuokki fi-Tammela se-Emmaboda se-Uppsala
au-canberra fi-Ammansaari fi-Tampere se-Falun se-Vannas
au-Darwin fi-Anjalankoski fi-Tervola se-Gallivare se-Varberg
au-GoldCoast fi-Espoo fi-Turku se-Gavle se-Vasteras
au-Hobart fi-Eurajoki fi-Utsjoki se-Goteborg_Brudaremossen se-Vastervik
au-Mackay fi-Fiskars fi-Vaasa se-Goteborg_Slattadamm se-Visby
au-Melbourne fi-Haapavesi fi-Vuokatti se-Halmstad se-Vislanda
au-Melbourne-Upwey fi-Hetta fi-Vuotso se-Harnosand se-Ystad
au-Perth fi-Iisalmi fi-Yllas se-Helsingborg tw-Taipei
au-Sydney_Kings_Cross fi-Inari fr-Bordeaux se-Horby uk-Angus
au-sydney_north_shore fi-Joutseno fr-Brest se-Hudiksvall uk-Bilsdale
au-Townsville fi-Juntusranta fr-LeMans se-Jonkoping uk-BlackHill
au-unknown fi-Jyvaskyla fr-Lyon-Fourviere se-Kalix uk-BluebellHill
cz-Praha fi-Kaihuanvaara fr-Lyon-Pilat se-Karlshamn uk-Caradon
de-Berlin fi-Karigasniemi fr-Marseille se-Karlskrona uk-CaradonHill
de-Braunschweig fi-Kaunispaa fr-Nantes se-Karlstad uk-Craigkelly
de-Bremen fi-Kerimaki fr-Niort se-Kiruna uk-CrystalPalace
de-Erfurt-Weimar fi-Kiihtelysvaara fr-Orleans se-Kisa uk-Dover
de-Frankfurt fi-Kilpisjarvi fr-Paris se-Kramfors uk-DoverB
de-Hamburg fi-Koli fr-Rennes se-Linkoping_Vattentorn uk-Durris
de-Hannover fi-Kruunupyy fr-Rouen se-Malmo uk-EmleyMoor
de-Kiel fi-Kuopio fr-Toulouse se-Malmo_Kronprinsen uk-Hannington
de-Koeln-Bonn fi-Kuttanen fr-Vannes se-Molndal_Vasterberget uk-Heathfield
de-Leipzig fi-Lahti hr-Zagreb se-Mora uk-Llanddona
de-Luebeck fi-Lapua is-Reykjavik se-Motala uk-Mendip
de-Muenchen fi-Mikkeli it-Bologna se-Nassjo uk-Oxford
de-Nuernberg fi-Oulu it-Bolzano se-Norrkoping uk-PontopPike
de-Rostock fi-Pello it-Catania se-Norrtalje_Sodra_Bergen uk-Redruth
de-Ruhrgebiet fi-Pernaja it-Conero se-Orebro uk-Reigate
de-Schwerin fi-Pihtipudas it-Genova se-Ornskoldsvik uk-Rowridge
dk-Copenhagen fi-Posio it-Milano se-Ostersund uk-SandyHeath
es-Alfabia fi-Pudasjarvi it-Torino se-Osthammar uk-Storeton
es-Alpicat fi-Puolanka it-Varese se-Skelleftea uk-SudburyB
es-Collserola fi-Pyhatunturi nl-AlphenaandenRijn se-Skovde uk-SuttonColdfield
es-Lugo fi-Pyhavuori nl-Randstad se-Sodertalje_Ragnhildsborg uk-TheWrekin
es-Madrid fi-Ranua se-Alvsbyn se-Stockholm_Marieberg uk-TheWrekinB
es-Mussara fi-Rovaniemi se-Angelholm se-Stockholm_Nacka uk-Waltham
es-Rocacorba fi-Ruka se-Bollnas se-Sundsvall uk-WhitehawkHill
es-Sevilla fi-Salla se-Boras se-Trollhattan uk-WinterHill

Once you have found the DVB-T transmitter for your region then use the line below to generate the VDR compatible channels.conf for that specific transmitter using the line below substituting 'uk-CrystalPalace' with the name of your closest transmitter;

cd /home
sudo scan -o vdr -p -u /usr/share/doc/dvb-utils/examples/scan/dvb-t/uk-CrystalPalace > channels.conf

This will write the channels.conf file and also output data on all the found and tuned channels to the console. The scan process usually takes less than a minute but can take longer if you have a low quality signal in your area. Below is an example of the output for 'uk-CrystalPalace' my local transmitter here in the UK showing the channels broadcast on all 6 MUX's;

scanning /usr/share/doc/dvb-utils/examples/scan/dvb-t/uk-CrystalPalace
using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0'
initial transponder 505833333 0 3 9 1 0 0 0
>>> tune to: 505833:I999B8C34D999M16T2G32Y0:T:27500:
0x0000 0x1044: pmt_pid 0x1044 BBC -- BBC ONE (running)
0x0000 0x1084: pmt_pid 0x1084 BBC -- BBC TWO (running)
0x0000 0x10ff: pmt_pid 0x10ff BBC -- BBC THREE (running)
0x0000 0x113f: pmt_pid 0x113f BBC -- BBC NEWS 24 (running)
0x0000 0x117f: pmt_pid 0x117f BBC -- BBCi (running)
0x0000 0x123f: pmt_pid 0x123f BBC -- CBBC Channel (running)
Network Name 'Crystal Palace'
>>> tune to: 481833:I999B8C23D12M64T2G32Y0:T:27500:
Network Name 'Crystal Palace'
0x2005 0x2045: pmt_pid 0x0100 ITV -- ITV1 (running)
0x2005 0x2066: pmt_pid 0x0104 ITV -- ITV3 (running)
0x2005 0x2085: pmt_pid 0x0102 ITV -- ITV2 (running)
0x2005 0x20a1: pmt_pid 0x0116 ITV -- ITV4 (running)
0x2005 0x20c0: pmt_pid 0x0108 Channel 4 TV -- Channel 4 (running)
0x2005 0x20fa: pmt_pid 0x010e Channel 4 TV -- More 4 (running)
0x2005 0x2100: pmt_pid 0x010b Channel 4 TV -- E4 (running)
0x2005 0x2104: pmt_pid 0x010c Channel 4 TV -- Channel 4+1 (running)
0x2005 0x2145: pmt_pid 0x0110 Teletext Limited -- Teletext (running)
0x2005 0x21c3: pmt_pid 0x0112 Teletext Limited -- Teletext Cars (running)
0x2005 0x2240: pmt_pid 0x0114 Channel 4 TV -- Teletext on 4 (running)
0x2005 0x2244: pmt_pid 0x011c Global Radio -- Heart (running)
>>> tune to: 561833:I999B8C23D12M64T2G32Y0:T:27500:
0x3002 0x3242: pmt_pid 0x0101 five -- Five (running)
0x3002 0x3280: pmt_pid 0x0113 five -- Five Life (running)
0x3002 0x32c0: pmt_pid 0x0117 five -- Five US (running)
0x3002 0x3340: pmt_pid 0x0103 QVC -- QVC (running)
0x3002 0x37c0: pmt_pid 0x0105 Sit-Up Ltd -- bid tv (running)
0x3002 0x3900: pmt_pid 0x010a EMAP -- Smash Hits! (running)
0x3002 0x3940: pmt_pid 0x010b EMAP -- MOJO (running)
0x3002 0x39c0: pmt_pid 0x010c Teletext Limited -- Ttext Holidays (running)
0x3002 0x3a80: pmt_pid 0x010e five -- UKTV Style (running, scrambled)
0x3002 0x3b80: pmt_pid 0x0112 five -- TVX / RED HOT (running)
0x3002 0x3cc0: pmt_pid 0x0114 five -- UKTV Gold (running, scrambled)
0x3002 0x3d00: pmt_pid 0x0115 Sit-Up Ltd -- price-drop tv (running)
0x3002 0x3dc0: pmt_pid 0x0118 five -- Teachers TV (running)
0x3002 0x3e20: pmt_pid 0x0124 Turner Broadcasting System Europe Limited -- Nuts TV (running)
0x3002 0x3e80: pmt_pid 0x011d five -- Eurosport UK (running, scrambled)
0x3002 0x3ea0: pmt_pid 0x0104 ITV -- CITV (running)
0x3002 0x3ee0: pmt_pid 0x011c ITV -- SETANTA SPORTS (running)
0x3002 0x3f00: pmt_pid 0x011b Teletext Limited -- Teletext Games (running)
0x3002 0x3f20: pmt_pid 0x0125 The Jewellery Channel -- Jewellery Chan (running)
0x3002 0x3f60: pmt_pid 0x0120 TopUp TV Ltd -- TopUp Anytime1 (running, scrambled)
0x3002 0x3f80: pmt_pid 0x0121 TopUp TV Ltd -- TopUp Anytime2 (running, scrambled)
0x3002 0x3fa0: pmt_pid 0x0122 TopUp TV Ltd -- TopUp Anytime3 (running, scrambled)
WARNING: filter timeout pid 0x0010
>>> tune to: 529833:I999B8C34D34M16T2G32Y0:T:27500:
0x4000 0x4280: pmt_pid 0x02ca BBC -- BBC Parliament (running)
0x4000 0x41c0: pmt_pid 0x02be BBC -- BBC FOUR (running)
0x4000 0x4240: pmt_pid 0x02bf BBC -- CBeebies (running)
0x4000 0x4600: pmt_pid 0x02c0 BBC -- BBC R5 Live (running)
0x4000 0x4640: pmt_pid 0x02c1 BBC -- BBC 5L SportsX (running)
0x4000 0x4680: pmt_pid 0x02c2 BBC -- BBC 6 Music (running)
0x4000 0x46c0: pmt_pid 0x02c3 BBC -- BBC 7 (running)
0x4000 0x4700: pmt_pid 0x02c4 BBC -- 1Xtra BBC (running)
0x4000 0x4740: pmt_pid 0x02c5 BBC -- BBC Asian Net. (running)
0x4000 0x4c00: pmt_pid 0x02c6 BBC -- 301 (running)
0x4000 0x4c40: pmt_pid 0x02c7 BBC -- 302 (running)
0x4000 0x4c80: pmt_pid 0x02c8 BBC -- 303 (running)
0x4000 0x4180: pmt_pid 0x02bd BBC -- 305 (running)
0x4000 0x4e00: pmt_pid 0x02c9 BBC -- Community (running)
0x4000 0x4840: pmt_pid 0x02cb BBC -- BBC Radio 1 (running)
0x4000 0x4880: pmt_pid 0x02cc BBC -- BBC Radio 2 (running)
0x4000 0x48c0: pmt_pid 0x02cd BBC -- BBC Radio 3 (running)
0x4000 0x4900: pmt_pid 0x02ce BBC -- BBC Radio 4 (running)
Network Name 'Crystal Palace'
>>> tune to: 578166:I999B8C34D34M16T2G32Y0:T:27500:
0x5000 0x5740: pmt_pid 0x02c1 Channel 4 TV -- E4+1 (running)
0x5000 0x5640: pmt_pid 0x02bd Sky -- Sky News (running)
0x5000 0x5680: pmt_pid 0x02be Sky -- Sky Spts News (running)
0x5000 0x56c0: pmt_pid 0x02bf Sky -- SKY THREE (running)
0x5000 0x5840: pmt_pid 0x02c2 talkSPORT -- talkSPORT (running)
0x5000 0x5c80: pmt_pid 0x02cd Sky -- Sky Text (running)
0x5000 0x5a40: pmt_pid 0x02ca Virgin Radio -- Virgin Radio (running)
0x5000 0x5cc0: pmt_pid 0x02cf yoomedia -- tvtv DIGITAL (running)
0x5000 0x5700: pmt_pid 0x02c0 UKTV -- Dave (running)
0x5000 0x5780: pmt_pid 0x02cc Square1 Management Ltd -- smileTV (running)
0x5000 0x59c0: pmt_pid 0x02c8 London Christian Radio Ltd -- Premier Radio (running)
0x5000 0x5a00: pmt_pid 0x02c9 Score Digital -- Clyde 1 (running)
Network Name 'Crystal Palace'
>>> tune to: 537833:I999B8C34D34M16T2G32Y0:T:27500:
0x6000 0x6440: pmt_pid 0x03e9 EMAP -- The HITS (running)
0x6000 0x6480: pmt_pid 0x03ea MTV Europe -- TMF (running)
0x6000 0x64c0: pmt_pid 0x03eb UKTV -- UKTV History (running)
0x6000 0x6500: pmt_pid 0x03ec Flextech -- Virgin1 (running)
0x6000 0x6540: pmt_pid 0x03ed CCI -- Ideal World (running)
0x6000 0x6640: pmt_pid 0x03fd EMAP -- Kiss (running)
0x6000 0x66c0: pmt_pid 0x03ff EMAP -- Kerrang! (running)
0x6000 0x6700: pmt_pid 0x0400 GMG -- SMOOTH RADIO (running)
0x6000 0x67c0: pmt_pid 0x0403 EMAP -- The Hits Radio (running)
0x6000 0x6800: pmt_pid 0x0404 EMAP -- Magic (running)
0x6000 0x6840: pmt_pid 0x0405 EMAP -- Q (running)
0x6000 0x6980: pmt_pid 0x0407 4TV Ltd -- 4TVinteractive (running)
0x6000 0x69c0: pmt_pid 0x03ee ITV -- ITV2 +1 (running)
0x6000 0x6a00: pmt_pid 0x03f0 Channel 4 TV -- Film4 (running)
0x6000 0x6780: pmt_pid 0x0402 BBC -- BBC World Sv. (running)
0x6000 0x6680: pmt_pid 0x03fe EMAP -- heat (running)
0x6000 0x6a40: pmt_pid 0x03f1 Channel 4 -- Gems TV (running)
0x6000 0x6a80: pmt_pid 0x03f2 Camelot Group plc -- Lottery Xtra (running)
Network Name 'Crystal Palace'
dumping lists (90 services)
Done.

Below is an example of the first few lines of the 'channels.conf' that was produced by the example above. Notice that the channels are grouped by MUX and not by their UK LCN (Logical Channel Number) which are the numbers with the '@' in front on alternate lines.

:@1
BBC - BBC ONE:505833:I999B8C34D34M16T2G32Y0:T:27500:600:601,602:0:0:4164:0:0:0
:@2
BBC - BBC TWO:505833:I999B8C34D34M16T2G32Y0:T:27500:610:611,612:0:0:4228:0:0:0
:@80
BBC - BBC NEWS 24:505833:I999B8C34D34M16T2G32Y0:T:27500:640:641:0:0:4415:0:0:0
:@70
BBC - CBBC Channel:505833:I999B8C34D34M16T2G32Y0:T:27500:620:621,622:0:0:4671:0:0:0
:@3
ITV - ITV1:481833:I999B8C23D12M64T2G32Y0:T:27500:520:521,522:0:0:8261:0:0:0
:@6
ITV - ITV2:481833:I999B8C23D12M64T2G32Y0:T:27500:530:531,532:0:0:8325:0:0:0
:@10
ITV - ITV3:481833:I999B8C23D12M64T2G32Y0:T:27500:540:541,542:0:0:8294:0:0:0
:@102
Teletext Limited - Teletext Cars:481833:I999B8C23D12M64T2G32Y0:T:27500:0:789:0:0:8643:0:0:0
:@4
Channel 4 TV - Channel 4:481833:I999B8C23D12M64T2G32Y0:T:27500:560+8190:561,562:0:0:8384:0:0:0
:@13
Channel 4 TV - Channel 4+1:481833:I999B8C23D12M64T2G32Y0:T:27500:580+8190:581,582:0:0:8452:0:0:0
:@29
Channel 4 TV - E4:481833:I999B8C23D12M64T2G32Y0:T:27500:570+8190:571,572:0:0:8448:0:0:0
:@14
Channel 4 TV - More 4:481833:I999B8C23D12M64T2G32Y0:T:27500:590+8190:591,592:0:0:8442:0:0:0
:@28
ITV - ITV4:481833:I999B8C23D12M64T2G32Y0:T:27500:600:601:0:0:8353:0:0:0
(null) - [2243]:481833:I999B8C23D12M64T2G32Y0:T:27500:0:621:0:0:8771:0:0:0
:@728
Global Radio - Heart:481833:I999B8C23D12M64T2G32Y0:T:27500:0:631:0:0:8772:0:0:0

VDR will load the channels into the EPG in the order that they are listed in the 'channels.conf'. So for example in the UK you might want to 'sort' the lines in the 'channels.conf' based on their LCN before loading them into VDR... although the 'channels.conf' will work fine without this. Here is a command which will create a new 'channels-sorted.conf' file from the original, sorted by LCN:

perl -0777ne 'print for sort{($a=~/^:@(\d+)/)[0]<=>($b=~/^:@(\d+)/)[0]}split/(?=^:@)/m' channels.conf > channels-sorted.conf
mv channels-sorted.conf channels.conf

Now that you have a good 'channels.conf' for your local DVB-T transmitter you need to load it into VDR. So just upload the new 'channels.conf' file using LinuxMCE's Web Admin site - go to Advanced –> Configuration –> VDR and use the 'Browse' button next to 'Upload custom file' to find where you created your 'channels.conf' file and click 'Upload'. Now restart vdr from the console;
sudo /etc/init.d/vdr restart
Now use the following command to check that vdr is running;
/etc/init.d/vdr status
You should see the line below;
Getting status of Linux Video Disk Recorder -= LMCE VERSION 0710-10 =- : vdr - is running.
Now the acid test...go to your LinuxMCE Orbiter and select 'TV' from the 'Media' menu to see a live picture and your all done.
==== Scanning for DVB-S Channels ====
Configuration
To configure VDR we should get the list of all available channels for desire satellite. You can find it somewhere or create using DVB utility scan. To do that we need the list of transponders stored as INI file. Get it from the [http://joshyfun.peque.org/transponders/index.html JoshyFun's site]. Store it somewhere on your LinuxMCE core. In my case I use the INI file for [http://joshyfun.peque.org/transponders/0130.ini Hotbird].

Before scanning stop VDR:
sudo /etc/init.d/vdr stop
and start scanning procedure:
scan -o vdr -p -x 0 0130.ini > channels.conf
It might take about 10-20 minutes depends on the number of available channels on your satellite. When scanning is finished just upload the created channels.conf file via Admin site - Advanced --> Configuration --> VDR. And then pickup your satellite from the list (see picture above).
[[Image:LMCE-VDR-config.jpg|thumb|550px|left|LinuxMCE VDR Configuration Screen]]
 
Quick reload router (most probably is not needed) and press button TV on the on-screen Orbiter. You should be able to watch live TV. To navigate on that screen use F6, F7 and F8 buttons on your keyboard, Gyration mouse or Fiire remote. Additionally you can switch channels, see EPG and schedule recording from VDRAdmin web interface.
===Enable Dolby Digital Audio in xinelibout===

sudo -s
ssh moonXX (where XX is the number of your MD)
Then start alsamixer on the commandline and press the right arrow on the keyboard until you get till "IEC958". If this is muted (says MM) then press the "m" button on the keyboard and the ESC key to save.

Then stop vdr :
/etc/init.d/vdr stop

and edit /etc/vdr/setup.conf and change the following lines to look like this :
xineliboutput.Audio.Port = iec958
xineliboutput.Audio.Speakers = Pass Through
CurrentDolby = 1
UseDolbyDigital = 1

And if you also want to record Dolby Digital then also change :
RecordDolbyDigital = 1

After saving the changes, restart vdr :
/etc/init.d/vdr start

Now you can replay recordings with Dolby Digital Audio

/Viking

===Troubleshooting===
If VDR works not as you expect you can do following:

<ol>
<li>Check VDR log - /var/log/pluto/<ID_VDR_IN_YOUR_SYSTEM>_VDR.log</li>
<li>Check if everything ok with your DVB card:
<ul>
<li>lspci - you should see your card in the list of PCI devices</li>
<li>dmesg|grep -i dvb - if driver if your DVB card is loaded correctly you will see it here. Note that in some cases you should place a firmware for your card into /lib/firmware!</li>
</ul>
</li>
</ol>
=== MCE Remote Functions ===
The MCE Remote button functions listed below are for lmcevdr-v10.
==== What do the buttons do? ====
[[Image:MCE-Remote-2.jpg|frame|50px|left|MCE IR Remote]]
==== TV Off ====
Not implemented currently
==== PC Off ====
When the menu bar is displayed or the screen saver is displaying images this button will power off the Core or any Media Directors that have IR remote control features. In VDR this button stops the Live TV picture (any scheduled recordings will be unaffected).
==== Record ====
Pressing this button when watching Live TV will start an 'Instant Recording'.
==== Stop ====
Pressing this button will stop the playback of a recording and return you to the Live TV picture on the channel you were watching previously.
==== Pause ====
When you have a Live TV picture on the screen pressing this button will 'Pause Live TV' and start recording - pressing this button again will un-pause the picture and start playing the recording while continuing to record the live transmission. If you are watching a recording and you press this button the playback of the recording will stop and the picture will 'freeze' on the screen. Pressing this button again will continue the playback of the recording again.
==== Rew ====
Rewinds a recording. There are 3 Rew speeds - pressing this button once gives you speed 1, press it again for speed 2 and a third time for speed 3. This button does nothing when watching Live TV.
==== Play ====
Pressing this button in 'Pause' mode plays the paused recording and pressing it again will 'Pause' the playback again.
==== Fwd ====
Fast Forwards a recording. There are 3 Fwd speeds - pressing this button once gives you speed 1, press it again for speed 2 and a third time for speed 3. This button does nothing when watching Live TV.
==== Replay ====
Press to jump back 1 min in a recording. Press repeatedly to jump back quickly through a recording.
==== Skip ====
Press to Skip forward 1 min in a recording. Press repeatedly to jump forward quickly through a recording.
==== Back ====
Takes you back to the last VDR on-screen menu if watching Live TV or a Recording and back to previous on-screen menu if an a VDR on-screen menu is already displayed.
==== More Info ====
Press once to display 'Info screen' for a Live Channel or a Recording. Press again to cancel 'Info screen'.
==== Up Arrow ====
While watching Live TV does a Channel Up. In on-screen menu moves to the menu option above.
==== Left Arrow ====
When watching a recording is equivalent to pressing 'Rewind'. In on-screen Schedule menu moves backwards in time.
==== OK ====
Pressing this button when Live TV displays the mini on-screen guide for 5 secs at the bottom of the screen. When playing a recording pressing this button displays the playback progress panel at the bottom of the screen. Press again to hide the playback progress panel.
==== Right Arrow ====
When watching a recording is equivalent to pressing 'Fwd'. In on-screen Schedule menu pressing this button moves forwards in time.
==== Down Arrow ====
While watching Live TV pressing this button does a Channel Down. In VDR on-screen menu moves pressing this button moves you to the menu option below. When watching a recording is equivalent to pressing 'Pause'.
==== Vol - (+) (-) ====
Increase or Decrease volume.
==== Green Start Button ====
Displays LinuxMCE Menu Bar.
==== Channel - (+) (-) ====
Increases or Decreases the Channel number and then changes to that Live TV channel
==== Mute ====
Pressing this button repeatedly toggles between Muted sound, on-screen subtitles and un-muted sound.
==== Recorded TV ====
Displays the VDR TV Recordings screen. Use Back repeatedly to back out of on-screen menus and get back to Live TV.
==== Guide ====
Displays the on-screen EPG Guide for the currently tuned channel. Use Colour buttons to Record, View Progs, Now & Next, Schedule & Next.
==== Live TV ====
Turns on Live TV or if already watching Live TV displays the on-screen EPG.
==== DVD Menu ====
When watching Live TV displays Channel List.
==== 1,2,3,4,5,6,7,8,9,*,0,# ====
Use to choose channel number directly in Live TV or to jump to on-screen menu items directly when an on-screen menu is displayed.
==== Clear ====
Currently unused
==== Enter ====
Equivalent to pressing 'OK'
==== Text ====
Currently unused
==== Red ====
In Live TV displays Recordings menu. In VDR menus does the 'Red' labeled function.
==== Green ====
In Live TV displays Channels on-screen menu. In on-screen menus does the 'Green' labeled function.
==== Yellow ====
In Live TV displays Info on-screen menu. In on-screen menus does the 'Yellow' labeled function.
==== Blue ====
In Live TV displays Timers on-screen menu. In on-screen menus does the 'Yellow' labeled function.
== Adding your own plugins to vdr ==
===Installing vdr-dev===
If you want to build and add plugins to vdr you need to install the vdr-dev package. Open a console session at your core or ssh in from another machine and do;
apt-get install vdr-dev
Now follow the instructions for building the plugin you are interested in.
== Manual Installation ==
For details on manually installing VDR please look in [[VDR Manual Install]].
== See also ==
* [http://www.linuxtv.org/vdrwiki/index.php/Main_Page VDR Wiki (English)]
* [http://www.free-x.de/wiki/index.php VDR Wiki (Russian)]
* [http://allrussian.info/board.php?boardid=61 VDR Forum (Russian)]
* [http://www.vdr-portal.de VDR Portal (German)]

VDR

2010-06-01T19:39:28Z

Esperanto: /* Installation */ removed other install method on request of possy

{| align="right"
| __TOC__
|}
[[Category:Software components]]
[[Category:Video]]
[[Category:Tutorials]]
= The Video Disk Recorder =
VDR is a [[personal video recorder]] system aimed at the DVB market. It supports DVB-S, DVB-C and DVB-T tuner cards. More details can be found at the [http://www.cadsoftusa.com/vdr/ VDR homepage].

It is the second PVR system integrated into LinuxMCE. The main aim is for a seamless integration into LinuxMCE. The UI should not change between VDR and the other LinuxMCE pieces. The first version of this integration wass scheduled for January 2008, and is mainly sponsored by [http://www.dianemo.co.uk Convergent Home Technologies Ltd].

== Configuration ==

Recently I managed to setup VDR under LinuxMCE successfully. This brief howto is a result of my personal experience. Don't hesitate to improve it.

===Installation===

VDR should be selected using the setup wizard. If you did not select VDR during the initial configuration after installation Simply re-run the wizard (it's on the Advanced menu) and select VDR as the PVR. VDR will be installed automatically and will start after installation.

[[Image:LMCE-software-modules.jpg|thumb|550px|left|LinuxMCE Software Modules]]
 
To make VDR configuration and manage easier its web interface - VDRAdmin can be used. It should be installed manually:

sudo apt-get install vdradmin-am

and then enabled to be able run by replacing ENABLED="0" by ENABLED="1" in the /etc/default/vdradmin-am. Also don't forget to add a new firewall rule for the port 8001 - Advanced -->> Network --> Firewall Rules.

=== Scanning for Channels ===

To enable scanning for channels the DVB utilities package should also installed manually:

sudo apt-get update

then do

sudo apt-get install dvb-utils

==== Scanning for DVB-T Channels ====

Firstly we need to stop VDR before we scan for channels;

sudo /etc/init.d/vdr stop

Above we installed the dvb-utils package and this will have installed the scan utility and tuning files for many DVB transmitters in various regions. Look for a transmitter in your region by looking in the following directory;

ls /usr/share/doc/dvb-utils/examples/scan/dvb-t

You should now see something like this on your console;

au-Adelaide fi-Ahtari fi-Taivalkoski se-Borlange se-Uddevalla
au-Brisbane fi-Ala-Vuokki fi-Tammela se-Emmaboda se-Uppsala
au-canberra fi-Ammansaari fi-Tampere se-Falun se-Vannas
au-Darwin fi-Anjalankoski fi-Tervola se-Gallivare se-Varberg
au-GoldCoast fi-Espoo fi-Turku se-Gavle se-Vasteras
au-Hobart fi-Eurajoki fi-Utsjoki se-Goteborg_Brudaremossen se-Vastervik
au-Mackay fi-Fiskars fi-Vaasa se-Goteborg_Slattadamm se-Visby
au-Melbourne fi-Haapavesi fi-Vuokatti se-Halmstad se-Vislanda
au-Melbourne-Upwey fi-Hetta fi-Vuotso se-Harnosand se-Ystad
au-Perth fi-Iisalmi fi-Yllas se-Helsingborg tw-Taipei
au-Sydney_Kings_Cross fi-Inari fr-Bordeaux se-Horby uk-Angus
au-sydney_north_shore fi-Joutseno fr-Brest se-Hudiksvall uk-Bilsdale
au-Townsville fi-Juntusranta fr-LeMans se-Jonkoping uk-BlackHill
au-unknown fi-Jyvaskyla fr-Lyon-Fourviere se-Kalix uk-BluebellHill
cz-Praha fi-Kaihuanvaara fr-Lyon-Pilat se-Karlshamn uk-Caradon
de-Berlin fi-Karigasniemi fr-Marseille se-Karlskrona uk-CaradonHill
de-Braunschweig fi-Kaunispaa fr-Nantes se-Karlstad uk-Craigkelly
de-Bremen fi-Kerimaki fr-Niort se-Kiruna uk-CrystalPalace
de-Erfurt-Weimar fi-Kiihtelysvaara fr-Orleans se-Kisa uk-Dover
de-Frankfurt fi-Kilpisjarvi fr-Paris se-Kramfors uk-DoverB
de-Hamburg fi-Koli fr-Rennes se-Linkoping_Vattentorn uk-Durris
de-Hannover fi-Kruunupyy fr-Rouen se-Malmo uk-EmleyMoor
de-Kiel fi-Kuopio fr-Toulouse se-Malmo_Kronprinsen uk-Hannington
de-Koeln-Bonn fi-Kuttanen fr-Vannes se-Molndal_Vasterberget uk-Heathfield
de-Leipzig fi-Lahti hr-Zagreb se-Mora uk-Llanddona
de-Luebeck fi-Lapua is-Reykjavik se-Motala uk-Mendip
de-Muenchen fi-Mikkeli it-Bologna se-Nassjo uk-Oxford
de-Nuernberg fi-Oulu it-Bolzano se-Norrkoping uk-PontopPike
de-Rostock fi-Pello it-Catania se-Norrtalje_Sodra_Bergen uk-Redruth
de-Ruhrgebiet fi-Pernaja it-Conero se-Orebro uk-Reigate
de-Schwerin fi-Pihtipudas it-Genova se-Ornskoldsvik uk-Rowridge
dk-Copenhagen fi-Posio it-Milano se-Ostersund uk-SandyHeath
es-Alfabia fi-Pudasjarvi it-Torino se-Osthammar uk-Storeton
es-Alpicat fi-Puolanka it-Varese se-Skelleftea uk-SudburyB
es-Collserola fi-Pyhatunturi nl-AlphenaandenRijn se-Skovde uk-SuttonColdfield
es-Lugo fi-Pyhavuori nl-Randstad se-Sodertalje_Ragnhildsborg uk-TheWrekin
es-Madrid fi-Ranua se-Alvsbyn se-Stockholm_Marieberg uk-TheWrekinB
es-Mussara fi-Rovaniemi se-Angelholm se-Stockholm_Nacka uk-Waltham
es-Rocacorba fi-Ruka se-Bollnas se-Sundsvall uk-WhitehawkHill
es-Sevilla fi-Salla se-Boras se-Trollhattan uk-WinterHill

Once you have found the DVB-T transmitter for your region then use the line below to generate the VDR compatible channels.conf for that specific transmitter using the line below substituting 'uk-CrystalPalace' with the name of your closest transmitter;

cd /home
sudo scan -o vdr -p -u /usr/share/doc/dvb-utils/examples/scan/dvb-t/uk-CrystalPalace > channels.conf

This will write the channels.conf file and also output data on all the found and tuned channels to the console. The scan process usually takes less than a minute but can take longer if you have a low quality signal in your area. Below is an example of the output for 'uk-CrystalPalace' my local transmitter here in the UK showing the channels broadcast on all 6 MUX's;

scanning /usr/share/doc/dvb-utils/examples/scan/dvb-t/uk-CrystalPalace
using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0'
initial transponder 505833333 0 3 9 1 0 0 0
>>> tune to: 505833:I999B8C34D999M16T2G32Y0:T:27500:
0x0000 0x1044: pmt_pid 0x1044 BBC -- BBC ONE (running)
0x0000 0x1084: pmt_pid 0x1084 BBC -- BBC TWO (running)
0x0000 0x10ff: pmt_pid 0x10ff BBC -- BBC THREE (running)
0x0000 0x113f: pmt_pid 0x113f BBC -- BBC NEWS 24 (running)
0x0000 0x117f: pmt_pid 0x117f BBC -- BBCi (running)
0x0000 0x123f: pmt_pid 0x123f BBC -- CBBC Channel (running)
Network Name 'Crystal Palace'
>>> tune to: 481833:I999B8C23D12M64T2G32Y0:T:27500:
Network Name 'Crystal Palace'
0x2005 0x2045: pmt_pid 0x0100 ITV -- ITV1 (running)
0x2005 0x2066: pmt_pid 0x0104 ITV -- ITV3 (running)
0x2005 0x2085: pmt_pid 0x0102 ITV -- ITV2 (running)
0x2005 0x20a1: pmt_pid 0x0116 ITV -- ITV4 (running)
0x2005 0x20c0: pmt_pid 0x0108 Channel 4 TV -- Channel 4 (running)
0x2005 0x20fa: pmt_pid 0x010e Channel 4 TV -- More 4 (running)
0x2005 0x2100: pmt_pid 0x010b Channel 4 TV -- E4 (running)
0x2005 0x2104: pmt_pid 0x010c Channel 4 TV -- Channel 4+1 (running)
0x2005 0x2145: pmt_pid 0x0110 Teletext Limited -- Teletext (running)
0x2005 0x21c3: pmt_pid 0x0112 Teletext Limited -- Teletext Cars (running)
0x2005 0x2240: pmt_pid 0x0114 Channel 4 TV -- Teletext on 4 (running)
0x2005 0x2244: pmt_pid 0x011c Global Radio -- Heart (running)
>>> tune to: 561833:I999B8C23D12M64T2G32Y0:T:27500:
0x3002 0x3242: pmt_pid 0x0101 five -- Five (running)
0x3002 0x3280: pmt_pid 0x0113 five -- Five Life (running)
0x3002 0x32c0: pmt_pid 0x0117 five -- Five US (running)
0x3002 0x3340: pmt_pid 0x0103 QVC -- QVC (running)
0x3002 0x37c0: pmt_pid 0x0105 Sit-Up Ltd -- bid tv (running)
0x3002 0x3900: pmt_pid 0x010a EMAP -- Smash Hits! (running)
0x3002 0x3940: pmt_pid 0x010b EMAP -- MOJO (running)
0x3002 0x39c0: pmt_pid 0x010c Teletext Limited -- Ttext Holidays (running)
0x3002 0x3a80: pmt_pid 0x010e five -- UKTV Style (running, scrambled)
0x3002 0x3b80: pmt_pid 0x0112 five -- TVX / RED HOT (running)
0x3002 0x3cc0: pmt_pid 0x0114 five -- UKTV Gold (running, scrambled)
0x3002 0x3d00: pmt_pid 0x0115 Sit-Up Ltd -- price-drop tv (running)
0x3002 0x3dc0: pmt_pid 0x0118 five -- Teachers TV (running)
0x3002 0x3e20: pmt_pid 0x0124 Turner Broadcasting System Europe Limited -- Nuts TV (running)
0x3002 0x3e80: pmt_pid 0x011d five -- Eurosport UK (running, scrambled)
0x3002 0x3ea0: pmt_pid 0x0104 ITV -- CITV (running)
0x3002 0x3ee0: pmt_pid 0x011c ITV -- SETANTA SPORTS (running)
0x3002 0x3f00: pmt_pid 0x011b Teletext Limited -- Teletext Games (running)
0x3002 0x3f20: pmt_pid 0x0125 The Jewellery Channel -- Jewellery Chan (running)
0x3002 0x3f60: pmt_pid 0x0120 TopUp TV Ltd -- TopUp Anytime1 (running, scrambled)
0x3002 0x3f80: pmt_pid 0x0121 TopUp TV Ltd -- TopUp Anytime2 (running, scrambled)
0x3002 0x3fa0: pmt_pid 0x0122 TopUp TV Ltd -- TopUp Anytime3 (running, scrambled)
WARNING: filter timeout pid 0x0010
>>> tune to: 529833:I999B8C34D34M16T2G32Y0:T:27500:
0x4000 0x4280: pmt_pid 0x02ca BBC -- BBC Parliament (running)
0x4000 0x41c0: pmt_pid 0x02be BBC -- BBC FOUR (running)
0x4000 0x4240: pmt_pid 0x02bf BBC -- CBeebies (running)
0x4000 0x4600: pmt_pid 0x02c0 BBC -- BBC R5 Live (running)
0x4000 0x4640: pmt_pid 0x02c1 BBC -- BBC 5L SportsX (running)
0x4000 0x4680: pmt_pid 0x02c2 BBC -- BBC 6 Music (running)
0x4000 0x46c0: pmt_pid 0x02c3 BBC -- BBC 7 (running)
0x4000 0x4700: pmt_pid 0x02c4 BBC -- 1Xtra BBC (running)
0x4000 0x4740: pmt_pid 0x02c5 BBC -- BBC Asian Net. (running)
0x4000 0x4c00: pmt_pid 0x02c6 BBC -- 301 (running)
0x4000 0x4c40: pmt_pid 0x02c7 BBC -- 302 (running)
0x4000 0x4c80: pmt_pid 0x02c8 BBC -- 303 (running)
0x4000 0x4180: pmt_pid 0x02bd BBC -- 305 (running)
0x4000 0x4e00: pmt_pid 0x02c9 BBC -- Community (running)
0x4000 0x4840: pmt_pid 0x02cb BBC -- BBC Radio 1 (running)
0x4000 0x4880: pmt_pid 0x02cc BBC -- BBC Radio 2 (running)
0x4000 0x48c0: pmt_pid 0x02cd BBC -- BBC Radio 3 (running)
0x4000 0x4900: pmt_pid 0x02ce BBC -- BBC Radio 4 (running)
Network Name 'Crystal Palace'
>>> tune to: 578166:I999B8C34D34M16T2G32Y0:T:27500:
0x5000 0x5740: pmt_pid 0x02c1 Channel 4 TV -- E4+1 (running)
0x5000 0x5640: pmt_pid 0x02bd Sky -- Sky News (running)
0x5000 0x5680: pmt_pid 0x02be Sky -- Sky Spts News (running)
0x5000 0x56c0: pmt_pid 0x02bf Sky -- SKY THREE (running)
0x5000 0x5840: pmt_pid 0x02c2 talkSPORT -- talkSPORT (running)
0x5000 0x5c80: pmt_pid 0x02cd Sky -- Sky Text (running)
0x5000 0x5a40: pmt_pid 0x02ca Virgin Radio -- Virgin Radio (running)
0x5000 0x5cc0: pmt_pid 0x02cf yoomedia -- tvtv DIGITAL (running)
0x5000 0x5700: pmt_pid 0x02c0 UKTV -- Dave (running)
0x5000 0x5780: pmt_pid 0x02cc Square1 Management Ltd -- smileTV (running)
0x5000 0x59c0: pmt_pid 0x02c8 London Christian Radio Ltd -- Premier Radio (running)
0x5000 0x5a00: pmt_pid 0x02c9 Score Digital -- Clyde 1 (running)
Network Name 'Crystal Palace'
>>> tune to: 537833:I999B8C34D34M16T2G32Y0:T:27500:
0x6000 0x6440: pmt_pid 0x03e9 EMAP -- The HITS (running)
0x6000 0x6480: pmt_pid 0x03ea MTV Europe -- TMF (running)
0x6000 0x64c0: pmt_pid 0x03eb UKTV -- UKTV History (running)
0x6000 0x6500: pmt_pid 0x03ec Flextech -- Virgin1 (running)
0x6000 0x6540: pmt_pid 0x03ed CCI -- Ideal World (running)
0x6000 0x6640: pmt_pid 0x03fd EMAP -- Kiss (running)
0x6000 0x66c0: pmt_pid 0x03ff EMAP -- Kerrang! (running)
0x6000 0x6700: pmt_pid 0x0400 GMG -- SMOOTH RADIO (running)
0x6000 0x67c0: pmt_pid 0x0403 EMAP -- The Hits Radio (running)
0x6000 0x6800: pmt_pid 0x0404 EMAP -- Magic (running)
0x6000 0x6840: pmt_pid 0x0405 EMAP -- Q (running)
0x6000 0x6980: pmt_pid 0x0407 4TV Ltd -- 4TVinteractive (running)
0x6000 0x69c0: pmt_pid 0x03ee ITV -- ITV2 +1 (running)
0x6000 0x6a00: pmt_pid 0x03f0 Channel 4 TV -- Film4 (running)
0x6000 0x6780: pmt_pid 0x0402 BBC -- BBC World Sv. (running)
0x6000 0x6680: pmt_pid 0x03fe EMAP -- heat (running)
0x6000 0x6a40: pmt_pid 0x03f1 Channel 4 -- Gems TV (running)
0x6000 0x6a80: pmt_pid 0x03f2 Camelot Group plc -- Lottery Xtra (running)
Network Name 'Crystal Palace'
dumping lists (90 services)
Done.

Below is an example of the first few lines of the 'channels.conf' that was produced by the example above. Notice that the channels are grouped by MUX and not by their UK LCN (Logical Channel Number) which are the numbers with the '@' in front on alternate lines.

:@1
BBC - BBC ONE:505833:I999B8C34D34M16T2G32Y0:T:27500:600:601,602:0:0:4164:0:0:0
:@2
BBC - BBC TWO:505833:I999B8C34D34M16T2G32Y0:T:27500:610:611,612:0:0:4228:0:0:0
:@80
BBC - BBC NEWS 24:505833:I999B8C34D34M16T2G32Y0:T:27500:640:641:0:0:4415:0:0:0
:@70
BBC - CBBC Channel:505833:I999B8C34D34M16T2G32Y0:T:27500:620:621,622:0:0:4671:0:0:0
:@3
ITV - ITV1:481833:I999B8C23D12M64T2G32Y0:T:27500:520:521,522:0:0:8261:0:0:0
:@6
ITV - ITV2:481833:I999B8C23D12M64T2G32Y0:T:27500:530:531,532:0:0:8325:0:0:0
:@10
ITV - ITV3:481833:I999B8C23D12M64T2G32Y0:T:27500:540:541,542:0:0:8294:0:0:0
:@102
Teletext Limited - Teletext Cars:481833:I999B8C23D12M64T2G32Y0:T:27500:0:789:0:0:8643:0:0:0
:@4
Channel 4 TV - Channel 4:481833:I999B8C23D12M64T2G32Y0:T:27500:560+8190:561,562:0:0:8384:0:0:0
:@13
Channel 4 TV - Channel 4+1:481833:I999B8C23D12M64T2G32Y0:T:27500:580+8190:581,582:0:0:8452:0:0:0
:@29
Channel 4 TV - E4:481833:I999B8C23D12M64T2G32Y0:T:27500:570+8190:571,572:0:0:8448:0:0:0
:@14
Channel 4 TV - More 4:481833:I999B8C23D12M64T2G32Y0:T:27500:590+8190:591,592:0:0:8442:0:0:0
:@28
ITV - ITV4:481833:I999B8C23D12M64T2G32Y0:T:27500:600:601:0:0:8353:0:0:0
(null) - [2243]:481833:I999B8C23D12M64T2G32Y0:T:27500:0:621:0:0:8771:0:0:0
:@728
Global Radio - Heart:481833:I999B8C23D12M64T2G32Y0:T:27500:0:631:0:0:8772:0:0:0

VDR will load the channels into the EPG in the order that they are listed in the 'channels.conf'. So for example in the UK you might want to 'sort' the lines in the 'channels.conf' based on their LCN before loading them into VDR... although the 'channels.conf' will work fine without this. Here is a command which will create a new 'channels-sorted.conf' file from the original, sorted by LCN:

perl -0777ne 'print for sort{($a=~/^:@(\d+)/)[0]<=>($b=~/^:@(\d+)/)[0]}split/(?=^:@)/m' channels.conf > channels-sorted.conf
mv channels-sorted.conf channels.conf

Now that you have a good 'channels.conf' for your local DVB-T transmitter you need to load it into VDR. So just upload the new 'channels.conf' file using LinuxMCE's Web Admin site - go to Advanced –> Configuration –> VDR and use the 'Browse' button next to 'Upload custom file' to find where you created your 'channels.conf' file and click 'Upload'. Now restart vdr from the console;
sudo /etc/init.d/vdr restart
Now use the following command to check that vdr is running;
/etc/init.d/vdr status
You should see the line below;
Getting status of Linux Video Disk Recorder -= LMCE VERSION 0710-10 =- : vdr - is running.
Now the acid test...go to your LinuxMCE Orbiter and select 'TV' from the 'Media' menu to see a live picture and your all done.
==== Scanning for DVB-S Channels ====
Configuration
To configure VDR we should get the list of all available channels for desire satellite. You can find it somewhere or create using DVB utility scan. To do that we need the list of transponders stored as INI file. Get it from the [http://joshyfun.peque.org/transponders/index.html JoshyFun's site]. Store it somewhere on your LinuxMCE core. In my case I use the INI file for [http://joshyfun.peque.org/transponders/0130.ini Hotbird].

Before scanning stop VDR:
sudo /etc/init.d/vdr stop
and start scanning procedure:
scan -o vdr -p -x 0 0130.ini > channels.conf
It might take about 10-20 minutes depends on the number of available channels on your satellite. When scanning is finished just upload the created channels.conf file via Admin site - Advanced --> Configuration --> VDR. And then pickup your satellite from the list (see picture above).
[[Image:LMCE-VDR-config.jpg|thumb|550px|left|LinuxMCE VDR Configuration Screen]]
 
Quick reload router (most probably is not needed) and press button TV on the on-screen Orbiter. You should be able to watch live TV. To navigate on that screen use F6, F7 and F8 buttons on your keyboard, Gyration mouse or Fiire remote. Additionally you can switch channels, see EPG and schedule recording from VDRAdmin web interface.
===Enable Dolby Digital Audio in xinelibout===

sudo -s
ssh moonXX (where XX is the number of your MD)
Then start alsamixer on the commandline and press the right arrow on the keyboard until you get till "IEC958". If this is muted (says MM) then press the "m" button on the keyboard and the ESC key to save.

Then stop vdr :
/etc/init.d/vdr stop

and edit /etc/vdr/setup.conf and change the following lines to look like this :
xineliboutput.Audio.Port = iec958
xineliboutput.Audio.Speakers = Pass Through
CurrentDolby = 1
UseDolbyDigital = 1

And if you also want to record Dolby Digital then also change :
RecordDolbyDigital = 1

After saving the changes, restart vdr :
/etc/init.d/vdr start

Now you can replay recordings with Dolby Digital Audio

/Viking

===Troubleshooting===
If VDR works not as you expect you can do following:

<ol>
<li>Check VDR log - /var/log/pluto/<ID_VDR_IN_YOUR_SYSTEM>_VDR.log</li>
<li>Check if everything ok with your DVB card:
<ul>
<li>lspci - you should see your card in the list of PCI devices</li>
<li>dmesg|grep -i dvb - if driver if your DVB card is loaded correctly you will see it here. Note that in some cases you should place a firmware for your card into /lib/firmware!</li>
</ul>
</li>
</ol>
=== MCE Remote Functions ===
The MCE Remote button functions listed below are for lmcevdr-v10.
==== What do the buttons do? ====
[[Image:MCE-Remote-2.jpg|frame|50px|left|MCE IR Remote]]
==== TV Off ====
Not implemented currently
==== PC Off ====
When the menu bar is displayed or the screen saver is displaying images this button will power off the Core or any Media Directors that have IR remote control features. In VDR this button stops the Live TV picture (any scheduled recordings will be unaffected).
==== Record ====
Pressing this button when watching Live TV will start an 'Instant Recording'.
==== Stop ====
Pressing this button will stop the playback of a recording and return you to the Live TV picture on the channel you were watching previously.
==== Pause ====
When you have a Live TV picture on the screen pressing this button will 'Pause Live TV' and start recording - pressing this button again will un-pause the picture and start playing the recording while continuing to record the live transmission. If you are watching a recording and you press this button the playback of the recording will stop and the picture will 'freeze' on the screen. Pressing this button again will continue the playback of the recording again.
==== Rew ====
Rewinds a recording. There are 3 Rew speeds - pressing this button once gives you speed 1, press it again for speed 2 and a third time for speed 3. This button does nothing when watching Live TV.
==== Play ====
Pressing this button in 'Pause' mode plays the paused recording and pressing it again will 'Pause' the playback again.
==== Fwd ====
Fast Forwards a recording. There are 3 Fwd speeds - pressing this button once gives you speed 1, press it again for speed 2 and a third time for speed 3. This button does nothing when watching Live TV.
==== Replay ====
Press to jump back 1 min in a recording. Press repeatedly to jump back quickly through a recording.
==== Skip ====
Press to Skip forward 1 min in a recording. Press repeatedly to jump forward quickly through a recording.
==== Back ====
Takes you back to the last VDR on-screen menu if watching Live TV or a Recording and back to previous on-screen menu if an a VDR on-screen menu is already displayed.
==== More Info ====
Press once to display 'Info screen' for a Live Channel or a Recording. Press again to cancel 'Info screen'.
==== Up Arrow ====
While watching Live TV does a Channel Up. In on-screen menu moves to the menu option above.
==== Left Arrow ====
When watching a recording is equivalent to pressing 'Rewind'. In on-screen Schedule menu moves backwards in time.
==== OK ====
Pressing this button when Live TV displays the mini on-screen guide for 5 secs at the bottom of the screen. When playing a recording pressing this button displays the playback progress panel at the bottom of the screen. Press again to hide the playback progress panel.
==== Right Arrow ====
When watching a recording is equivalent to pressing 'Fwd'. In on-screen Schedule menu pressing this button moves forwards in time.
==== Down Arrow ====
While watching Live TV pressing this button does a Channel Down. In VDR on-screen menu moves pressing this button moves you to the menu option below. When watching a recording is equivalent to pressing 'Pause'.
==== Vol - (+) (-) ====
Increase or Decrease volume.
==== Green Start Button ====
Displays LinuxMCE Menu Bar.
==== Channel - (+) (-) ====
Increases or Decreases the Channel number and then changes to that Live TV channel
==== Mute ====
Pressing this button repeatedly toggles between Muted sound, on-screen subtitles and un-muted sound.
==== Recorded TV ====
Displays the VDR TV Recordings screen. Use Back repeatedly to back out of on-screen menus and get back to Live TV.
==== Guide ====
Displays the on-screen EPG Guide for the currently tuned channel. Use Colour buttons to Record, View Progs, Now & Next, Schedule & Next.
==== Live TV ====
Turns on Live TV or if already watching Live TV displays the on-screen EPG.
==== DVD Menu ====
When watching Live TV displays Channel List.
==== 1,2,3,4,5,6,7,8,9,*,0,# ====
Use to choose channel number directly in Live TV or to jump to on-screen menu items directly when an on-screen menu is displayed.
==== Clear ====
Currently unused
==== Enter ====
Equivalent to pressing 'OK'
==== Text ====
Currently unused
==== Red ====
In Live TV displays Recordings menu. In VDR menus does the 'Red' labeled function.
==== Green ====
In Live TV displays Channels on-screen menu. In on-screen menus does the 'Green' labeled function.
==== Yellow ====
In Live TV displays Info on-screen menu. In on-screen menus does the 'Yellow' labeled function.
==== Blue ====
In Live TV displays Timers on-screen menu. In on-screen menus does the 'Yellow' labeled function.
== Adding your own plugins to vdr ==
===Installing vdr-dev===
If you want to build and add plugins to vdr you need to install the vdr-dev package. Open a console session at your core or ssh in from another machine and do;
apt-get install vdr-dev
Now follow the instructions for building the plugin you are interested in.
== Manual Installation ==
For details on manually installing VDR please look in [[VDR Manual Install]].
== See also ==
* [http://www.linuxtv.org/vdrwiki/index.php/Main_Page VDR Wiki (English)]
* [http://www.free-x.de/wiki/index.php VDR Wiki (Russian)]
* [http://allrussian.info/board.php?boardid=61 VDR Forum (Russian)]
* [http://www.vdr-portal.de VDR Portal (German)]

Creating a Device Template for a Remote that uses the kernel input subsystem

2010-05-05T17:57:02Z

Esperanto: /* Controlled By Category */

[[Category: Tutorials]]
== Criteria for using The Generic HID Interface ==

The Remote in question must:

* Expose itself as an input device, and have a file entry in /dev/input as eventX where X is the order in which the kernel discovered the device.
* Must emit EV_KEY packets, as specified by the Linux Input subsystem.

Following these criteria, creating a device template is simple.

== Adding Support for a new Remote ==

=== Before you start ===

Press Keys on the remote, make note of which keys work, and which ones do not. '''You will only need to specify keys for the keys that do not work in your template.'''

=== Step 1: Plug in device ===

With orbiter started, plug in the device, and quick reload the router.

=== Step 2: Find the Device # of the On-Screen Orbiter you are using. ===

In the web admin, go to Advanced > Configuration > Devices.

Select your media director from the top of the device tree. For the Core Hybrid, select Core/Hybrid under CORE.

Select the On Screen Orbiter child. Get its device #. You will need this.

=== Step 3: Tail the Orbiter Log looking for Generic HID events ===

Open a shell on the media director on which you have the remote connected.

Due to the sheer volume of data generated by the Orbiter log, we will need to filter it, looking specifically for GenericHIDInterface messages. This is simple with a grep command.

tail -f /var/log/pluto/XX_LaunchOrbiter.sh.log | grep "GenericHIDInterface"

You will start seeing GenericHIDInterface messages.

=== Step 4: Press the keys that do not work ===

Press the keys that do not work. If the Generic HID Interface is able to decode them, you will see messages similar to the following:

10 06/27/09 22:00:33.856 GenericHIDInterface::DecodeEventInFD() Begin <0xb3232b90>
10 06/27/09 22:00:33.856 GenericHIDInterface::DecodeEventInFD code 20114 value 1. <0xb3232b90>
10 06/27/09 22:00:33.856 GenericHIDInterface::DecodeEventInFD() End <0xb3232b90>
10 06/27/09 22:00:34.048 GenericHIDInterface::DecodeEventInFD() Begin <0xb3232b90>
10 06/27/09 22:00:34.048 GenericHIDInterface::DecodeEventInFD code 20114 value 0. <0xb3232b90>
10 06/27/09 22:00:34.048 GenericHIDInterface::DecodeEventInFD() End <0xb3232b90>

If you recieve the code, Make note of the code. Match this with the button you're intending to press, in your notes.

Repeat this for all the buttons that do not work.

=== Step 5: Open a notepad and write Configuration Device Data ===

Open a notepad and take the codes you have written down, and pair them with buttons in the [[Remote Mapping Table]].

The Lines should be like this:

VolUp,20114,R[,Y]

and should be one per line. Where the:

* first value, is the symbol in the [[Remote Mapping Table]]
* second value, is the key code you determined by looking at the logs.
* third value is a key state, where:
** U = Button Up
** D = Button Down
** H = Button Held Down
** R = Button Repeats when Held Down.
* fourth value (optional) means that this key code should be honored even on screens which yield to the OS, examples of this screen include:
** DVD Menu
** Web Browser
** On-Screen navigation (think MythTV menus, etc.)

=== Step 6: Write the Mapping Device Data ===

Press enter a few times, and enter the mapping device data.

This device data is used to map one key code, to another.

According to the 1812: Gyration Go Mouse template:

new line delimited list of events to replace with other events in the format: Event Type,ID=EventType,id

To give an example:

The Gyration 3101 emits a key code, 97, when the Windows button is pressed. This needs to be changed so the system interprets it as the key code for F7.

so we add a mapping for it:

2,97=2,73
3,97=3,73

The code, 73, for F7, is coincidentally the xkeysym for F7. X Key symbols can be found using the '''xev''' utility, and reading the "code:" value when a key is pressed.

You can also add mappings for mouse buttons. These have a event type of 4 and 5. So mapping mouse button 6 to F7 would be like this:

4,6=2,73
5,6=3,73

==== Wait, what are the 2, 3, 4 and 5 values? ====

These are the Event Types.

According to Orbiter.h:
<pre>
typedef enum _EventType {
QUIT,
NOT_PROCESSED,
BUTTON_DOWN, // keyboard
BUTTON_UP,
REGION_DOWN, // mouse
REGION_UP,
MOUSE_MOVE,
MOUSE_RELATIVE_MOVE,
HID,
NONE
} EventType;
</pre>
Since this is an enumerated type, starting from 0, 2 = BUTTON_DOWN, 3 = BUTTON_UP, 4 = REGION_DOWN, 5 = REGION_UP.

=== Step 7: Make a New template, with all the compiled information ===

Please read the general information on [[Device Templates]] before continuing.

Go to the web admin, Advanced > Configuration > Device Templates.

Select the appropriate Manufacturer. If it does not exist, make one.

Select Remote Controls from the device category, or Gestural Remotes if it is a gyro-mouse. Basically, use an appropriate category.

Select [Add Device]

Select that this is a device that does not require any programming. Name it appropriately.

====Controlled By Category====
This device needs to be controlled via category '''Orbiters -> Standard Orbiter'''. So add that as a controlled via Device Category. Orbiter uses this relation to not only make the remote a child of the on-screen orbiter, but Orbiter expects to find remote controls in this category so it knows to appropriate them.

====Configuration Device data====
add the following, with the Use Master List Defaults checked for all:

* Configuration. Paste the Configuration device data from your notepad, here.
* Mapping. Paste the Mapping Device data from your notepad, here.
* Only One Per PC, set this to 1
* Auto Assign This to Parents Room, set this to 1
* PNP Create Without Prompting, set this to 1
* Immediate Reload isn't Necessary, set this to 1.

''Please be sure to put appropriate comments into the comments field. This is required.''

====Plug and Play====

This is how LinuxMCE will detect the device. Since this is most likely, a USB device, you will need to put 0 in both the beginning and end MAC, as they will not be used.

You will then need to fill out the Vendor/Model ID appropriately. You can grab this information using '''lsusb'''

For example: The Gyration Go Mouse and MCR Remote use a USB ID of 0c16:0002, where 0c16 is the vendor number, and 0002 is the model number. Enter this without the colon: '''0c160002'''. Write a suitable comment, and click the add button.

You can then press the Save button, and the device template will be saved. You can then check this in anonymously, by using the sqlCVS functions in the web admin to check in your '''dce''' and '''ir''' repositories. Use the default credentials for an anonymous check in, and let us know in a trac ticket that you've checked in a template.

Pvr-150 picture quality guide

2009-02-15T09:56:13Z

Esperanto: corrected path

== PVR-150 PICTURE QUALITY GUIDE ==

The PVR-150 is one of the most common devices used to capture live analog TV broadcast.
After weeks of searching the internet and trying various settings I have finally got to a point where picture quality is almost identical to the picture you get watching your set top box connected directly to you TV.

The first thing you need to take into account is that the picture quality is vary much dependent on the type of connection you are using on the card. I received the best results using the S-VIDEO connection, how ever it is a good idea to experiment with the various connections because in different countries there are different broadcast formats and you might find that using a different connection works better for you.

====Next, launch MythTV, got to the '''Utilities/Setup --> Setup --> TV Settings --> Playback'''.====

*On the first screen you'll see several options:
*Deselect the '''Deinterlace''' option.
*for '''Preferred Decoder''' choose '''libmpeg2'''
*Select '''Enable OpenGL'''.

After that keep clicking "next until you get to the last screen and click "finish". Failing to do so will leave your settings unsaved.

These settings should stop the OSD from tearing, how ever, at the time of writing this these settings do not survive a router reload.

The next step is vary important as it is dealing with the picture quality and is the reason for writing this tutorial.

====Still in the setup menu go to '''Recording Profiles --> Mpeg2 Encoders --> Default'''.====

The reason to use the default profile rather then the high quality one is that they are basically all the same until you change them.
I always use the default one because I always want to get the best picture quality I can.

On the second screen - '''picture size''' choose at least '''720X480'''.

depending on your country, using a larger resolution might give you better quality so try it.

*On the next screen:
*For '''Stream Type''' use '''DVD-Special 2'''.
*Set the regular bitrate to '''8000'''
*Set the max bitrate to '''12000''', which the highest bitrate the card can handle.

Once again, go thru all screens until you get to the last one and click finish.

You should now have a pretty good picture quality which is pretty close to direct TV picture quality (at least on my system).

HTTPS

2009-02-10T19:12:56Z

Esperanto: enabled local host so lmce can connect to itselves ;-)

= HTTPS / SSL access on the outside =

I am trying to setup https on the outside so Linuxmce can be used safely. Below is my setup.

We start by creating a new password file (-c option) and adding a user (linux) with a password (test) to the password file:

htpasswd -bc /etc/apache2/httpd.passwd linuxmce test

(Use the same line without the -c to add additional users)

mkdir /root/ssl
openssl genrsa -des3 -out /root/ssl/server.key 4096

(type a passwd twice)

openssl req -new -key /root/ssl/server.key -out /root/ssl/server.csr

(type your previous passwd once and then fill in the fields)

Make sure that "Common Name (eg, YOUR name)" matches the registered fully qualified domain name of your box (or your IP address if you don't have one).

openssl x509 -req -days 3650 -in /root/ssl/server.csr -signkey /root/ssl/server.key -out /root/ssl/server.crt

openssl rsa -in /root/ssl/server.key -out /root/ssl/server.key.insecure
mv /root/ssl/server.key /root/ssl/server.key.secure
mv /root/ssl/server.key.insecure /root/ssl/server.key

You now have the following files in /root/ssl:

server.crt: The self-signed server certificate.
server.csr: Server certificate signing request.
server.key: The private server key, does not require a password when starting Apache.
server.key.secure: The private server key, it does require a password when starting Apache.

mkdir /etc/apache2/ssl
cp /root/ssl/server.key /etc/apache2/ssl
cp /root/ssl/server.crt /etc/apache2/ssl

add to /etc/apache2/ports.conf:

<pre>
<IfModule mod_ssl.c>
Listen 443
</IfModule>

</pre>

ln -s /etc/apache2/mods-available/ssl.load /etc/apache2/mods-enabled/ssl.load
ln -s /etc/apache2/mods-available/ssl.conf /etc/apache2/mods-enabled/ssl.conf

add the following in /etc/apache2/httpd.conf

<pre>
SSLCertificateFile /etc/apache2/ssl/server.crt
SSLCertificateKeyFile /etc/apache2/ssl/server.key

<LocationMatch "/*">
# Inside the subarea any Intranet access is allowed
# but from the Internet only HTTPS + Strong-Cipher + Password
# or the alternative HTTPS + Strong-Cipher + Client-Certificate

# If HTTPS is used, make sure a strong cipher is used.
# Additionally allow client certs as alternative to basic auth.
SSLVerifyClient optional
SSLVerifyDepth 1
SSLOptions +FakeBasicAuth +StrictRequire
SSLRequire %{SSL_CIPHER_USEKEYSIZE} >= 128

# Force clients from the Internet to use HTTPS
#RewriteEngine on
#RewriteCond %{REMOTE_ADDR} !^192\.168\.80\.[0-9]+$
#RewriteCond %{HTTPS} !=on
#RewriteRule ^/(.*) https://%{SERVER_NAME}/$2 [R,L]

# Allow Network Access and/or Basic Auth
Satisfy any

# Network Access Control
Order deny,allow
Deny from all
Allow from 192.168.80.0/24 127.0.0.1

# HTTP Basic Authentication
AuthType basic
AuthName "LinuxMCE"
AuthUserFile /etc/apache2/httpd.passwd
Require valid-user

</LocationMatch>

# Since mythweb has it's own rewrites in a .htaccess file https redirection is enabled only on other urls
<LocationMatch "^/(?!mythweb).*">
# Force clients from the Internet to use HTTPS
RewriteEngine on
RewriteCond %{REMOTE_ADDR} !^192\.168\.80\.[0-9]+$
RewriteCond %{REMOTE_ADDR} !^127\.0\.0\.[0-9]+$
RewriteCond %{HTTPS} !=on
RewriteRule ^/(.*) https://%{SERVER_NAME}/$2 [R,L]
</LocationMatch>

</pre>

On the top of httpd.conf add the fully qualified domain name of your box that you added by "Common Name (eg, YOUR name)" when creating the certificate:

ServerName linuxmce.yourdomain.com

we have to change the beginning of vi /etc/apache2/sites-available/pluto to:
<pre>
# NameVirtualHost *
<VirtualHost *:80>
</pre>

and then copy this file:
cp /etc/apache2/sites-available/pluto /etc/apache2/sites-available/pluto443

then change the beginnig to:
<pre>
# NameVirtualHost *
<VirtualHost *:443>
SSLEngine On
</pre>

make a symbolic link:
ln -s /etc/apache2/sites-available/pluto443 /etc/apache2/sites-enabled/pluto443

go to pluto web admin and to Advanced>Network>Firewall and add a new rule:
tcp 443 443 core_input

then run:

apache2ctl restart

Torrentflux

2008-12-16T17:43:10Z

Esperanto:

= Torrentflux =

I wanted to make the use of torrents a little easier. So installed torrentflux (apt-get install torrentflux).

To het an extra folder button to move the files to the media directory and an unrar (you need to install it also) button via the webinterface I changed the following:

Add to lines to the bottom of the sudoers file:
sudo vi /etc/sudoers
<pre>
www-data ALL=(root) NOPASSWD: /bin/chown root\:public /var/cache/torrentflux/[a-zA-Z0-9]*/*
www-data ALL=(root) NOPASSWD: /bin/mv /var/cache/torrentflux/[a-zA-Z0-9]*/* /home/public/data/*
</pre>

add the following code to the file /usr/share/torrentflux/www/dir.php. I have put it just above:
<pre>
// Are we to unrar something?
$rar = getRequestVar('rar');
if ($rar != "")
{

$current = "";

$rar = stripslashes(stripslashes($rar));

$command = "cd ". escapeshellarg(dirname($cfg["path"] . $rar)) ."; /usr/bin/unrar x " . escapeshellarg($cfg["path"] . $rar);
passthru($command);
session_write_close();
}

// Are we to move something?
$move = getRequestVar('move');
if ($move != "")
{

$current = "";

$move = stripslashes(stripslashes($move));

$command = "chmod -R 775 " . $cfg["path"] . $move;
$result = exec($command);

$command = "sudo chown root:public " . $cfg["path"] . $move;
$result .= exec($command);

$command = "sudo mv '" . $cfg["path"] . $move . "' " . "'/home/public/data/videos/www/'";
$result .= exec($command);

header("Location: dir.php?dir=".urlencode($dir));
}

// Are we to rename something?
$rename = getRequestVar('rename');
$toname = getRequestVar('toname');
if ($rename != "" && $toname != "")
{
echo "<pre>" . $rename . " to: " . $toname . "</pre>";
$current = "";

$rename = stripslashes(stripslashes($rename));
$toname = stripslashes(stripslashes($toname));

$command = "mv '" . $cfg["path"] . $rename . "' '" . $cfg["path"] . "/" . $toname . "'";
$result .= exec($command);

echo "<pre>" . "mv '" . $cfg["path"] . $rename . "' '" . $cfg["path"] . "/" . $toname . "'" . "</pre>";
}

</pre>

Then just below this:
<pre>
echo "</td>";
echo "<td align=\"right\">".$fileSize." KB</td>";
echo "<td>".date("m-d-Y g:i a", $timeStamp)."</td>";
echo "<td align=\"right\">"
</pre>
add this code:
<pre>
if( 1 == 1 )
{
echo "<a href=\"dir.php?dir=".urlencode($dir)."&move=".urlencode($dir.$entry)."\" >";
echo "<img src=\"images/folder.png\" width=\"16\" height=\"16\" title=\"move to linuxMCE\" border=\"0\"></a>";
}

echo "<a href=\"javascript:popRename('" . urlencode(addslashes($dir.$entry)) ."');\">rn</a>";

if( ( substr( strtolower($entry), -4 ) == ".rar" ) )
{
echo "<a href=\"dir.php?rar=".urlencode($dir.$entry)."\" >";
echo "<img src=\"".$image."\" width=\"16\" height=\"16\" title=\"unrar\" border=\"0\"></a>";
}

</pre>

after:
<pre>
$dirName = stripslashes($dirName);

if (isset($dir))
{
</pre>

put the code:
<pre>
$javascript = <<<JSPOPRENAME
<script type='text/javascript' language='javascript'>
function popRename(name){

newwindow2=window.open('','name','height=100,width=550');
var tmp = newwindow2.document;
tmp.write('<html><head><title>rename ' + name + '</title>');
tmp.write('<script type=\'text/javascript\' language=\'javascript\'>function getname(obj) {');
tmp.write('window.location=\'dir.php?rename=' + escape(name) + '&toname=\' + escape(obj.childNodes[0].value);');
tmp.write('self.close();');
tmp.write('}</scr' + 'ipt>');
tmp.write('</head><body>type new name below and press enter');
tmp.write('<form action="javascript:getname(document.getElementById(\'myform\'));" name="myform" id="myform">');
tmp.write('<input style="width: 450px" type="text" value="' + name + '"></form>');
tmp.write('refresh the original page to see the results.');
tmp.write('</body></html>');
tmp.close();
} </script>

JSPOPRENAME;

echo $javascript;

</pre>

HTTPS

2008-12-10T10:56:41Z

Esperanto:

= HTTPS / SSL access on the outside =

I am trying to setup https on the outside so Linuxmce can be used safely. Below is my setup.

We start by creating a new password file (-c option) and adding a user (linux) with a password (test) to the password file:

htpasswd -bc /etc/apache2/httpd.passwd linuxmce test

(Use the same line without the -c to add additional users)

mkdir /root/ssl
openssl genrsa -des3 -out /root/ssl/server.key 4096

(type a passwd twice)

openssl req -new -key /root/ssl/server.key -out /root/ssl/server.csr

(type your previous passwd once and then fill in the fields)

Make sure that "Common Name (eg, YOUR name)" matches the registered fully qualified domain name of your box (or your IP address if you don't have one).

openssl x509 -req -days 3650 -in /root/ssl/server.csr -signkey /root/ssl/server.key -out /root/ssl/server.crt

openssl rsa -in /root/ssl/server.key -out /root/ssl/server.key.insecure
mv /root/ssl/server.key /root/ssl/server.key.secure
mv /root/ssl/server.key.insecure /root/ssl/server.key

You now have the following files in /root/ssl:

server.crt: The self-signed server certificate.
server.csr: Server certificate signing request.
server.key: The private server key, does not require a password when starting Apache.
server.key.secure: The private server key, it does require a password when starting Apache.

mkdir /etc/apache2/ssl
cp /root/ssl/server.key /etc/apache2/ssl
cp /root/ssl/server.crt /etc/apache2/ssl

add to /etc/apache2/ports.conf:

<pre>
<IfModule mod_ssl.c>
Listen 443
</IfModule>

</pre>

ln -s /etc/apache2/mods-available/ssl.load /etc/apache2/mods-enabled/ssl.load
ln -s /etc/apache2/mods-available/ssl.conf /etc/apache2/mods-enabled/ssl.conf

add the following in /etc/apache2/httpd.conf

<pre>
SSLCertificateFile /etc/apache2/ssl/server.crt
SSLCertificateKeyFile /etc/apache2/ssl/server.key

<LocationMatch "/*">
# Inside the subarea any Intranet access is allowed
# but from the Internet only HTTPS + Strong-Cipher + Password
# or the alternative HTTPS + Strong-Cipher + Client-Certificate

# If HTTPS is used, make sure a strong cipher is used.
# Additionally allow client certs as alternative to basic auth.
SSLVerifyClient optional
SSLVerifyDepth 1
SSLOptions +FakeBasicAuth +StrictRequire
SSLRequire %{SSL_CIPHER_USEKEYSIZE} >= 128

# Force clients from the Internet to use HTTPS
#RewriteEngine on
#RewriteCond %{REMOTE_ADDR} !^192\.168\.80\.[0-9]+$
#RewriteCond %{HTTPS} !=on
#RewriteRule ^/(.*) https://%{SERVER_NAME}/$2 [R,L]

# Allow Network Access and/or Basic Auth
Satisfy any

# Network Access Control
Order deny,allow
Deny from all
Allow from 192.168.80.0/24

# HTTP Basic Authentication
AuthType basic
AuthName "LinuxMCE"
AuthUserFile /etc/apache2/httpd.passwd
Require valid-user

</LocationMatch>

# Since mythweb has it's own rewrites in a .htaccess file https redirection is enabled only on other urls
<LocationMatch "^/(?!mythweb).*">
# Force clients from the Internet to use HTTPS
RewriteEngine on
RewriteCond %{REMOTE_ADDR} !^192\.168\.80\.[0-9]+$
RewriteCond %{HTTPS} !=on
RewriteRule ^/(.*) https://%{SERVER_NAME}/$2 [R,L]
</LocationMatch>

</pre>

On the top of httpd.conf add the fully qualified domain name of your box that you added by "Common Name (eg, YOUR name)" when creating the certificate:

ServerName linuxmce.yourdomain.com

we have to change the beginning of vi /etc/apache2/sites-available/pluto to:
<pre>
# NameVirtualHost *
<VirtualHost *:80>
</pre>

and then copy this file:
cp /etc/apache2/sites-available/pluto /etc/apache2/sites-available/pluto443

then change the beginnig to:
<pre>
# NameVirtualHost *
<VirtualHost *:443>
SSLEngine On
</pre>

make a symbolic link:
ln -s /etc/apache2/sites-available/pluto443 /etc/apache2/sites-enabled/pluto443

go to pluto web admin and to Advanced>Network>Firewall and add a new rule:
tcp 443 443 core_input

then run:

apache2ctl restart

HTTPS

2008-12-03T13:34:10Z

Esperanto: New page: = HTTPS / SSL access on the outside = I am trying to setup https on the outside so Linuxmce can be used safely. Below is my setup. We start by creating a new password file (-c option) an...

= HTTPS / SSL access on the outside =

I am trying to setup https on the outside so Linuxmce can be used safely. Below is my setup.

We start by creating a new password file (-c option) and adding a user (linux) with a password (test) to the password file:

htpasswd -c /etc/apache2/httpd.passwd linuxmce test

(Use the same line without the -c to add additional users)

mkdir /root/ssl
openssl genrsa -des3 -out /root/ssl/server.key 4096

(type a passwd twice)

openssl req -new -key /root/ssl/server.key -out /root/ssl/server.csr

(type your previous passwd once and then fill in the fields)

Make sure that "Common Name (eg, YOUR name)" matches the registered fully qualified domain name of your box (or your IP address if you don't have one).

openssl x509 -req -days 3650 -in /root/ssl/server.csr -signkey /root/ssl/server.key -out /root/ssl/server.crt

openssl rsa -in /root/ssl/server.key -out /root/ssl/server.key.insecure
mv /root/ssl/server.key /root/ssl/server.key.secure
mv /root/ssl/server.key.insecure /root/ssl/server.key

You now have the following files in /root/ssl:

server.crt: The self-signed server certificate.
server.csr: Server certificate signing request.
server.key: The private server key, does not require a password when starting Apache.
server.key.secure: The private server key, it does require a password when starting Apache.

mkdir /etc/apache2/ssl
cp /root/ssl/server.key /etc/apache2/ssl
cp /root/ssl/server.crt /etc/apache2/ssl

add to /etc/apache2/ports.conf:

<pre>
<IfModule mod_ssl.c>
Listen 443
</IfModule>

</pre>

ln -s /etc/apache2/mods-available/ssl.load /etc/apache2/mods-enabled/ssl.load
ln -s /etc/apache2/mods-available/ssl.conf /etc/apache2/mods-enabled/ssl.conf

add the following in /etc/apache2/httpd.conf

<pre>
SSLCertificateFile /etc/apache2/ssl/server.crt
SSLCertificateKeyFile /etc/apache2/ssl/server.key

<LocationMatch "/*">
# Inside the subarea any Intranet access is allowed
# but from the Internet only HTTPS + Strong-Cipher + Password
# or the alternative HTTPS + Strong-Cipher + Client-Certificate

# If HTTPS is used, make sure a strong cipher is used.
# Additionally allow client certs as alternative to basic auth.
SSLVerifyClient optional
SSLVerifyDepth 1
SSLOptions +FakeBasicAuth +StrictRequire
SSLRequire %{SSL_CIPHER_USEKEYSIZE} >= 128

# Force clients from the Internet to use HTTPS
#RewriteEngine on
#RewriteCond %{REMOTE_ADDR} !^192\.168\.80\.[0-9]+$
#RewriteCond %{HTTPS} !=on
#RewriteRule ^/(.*) https://%{SERVER_NAME}/$2 [R,L]

# Allow Network Access and/or Basic Auth
Satisfy any

# Network Access Control
Order deny,allow
Deny from all
Allow from 192.168.80.0/24

# HTTP Basic Authentication
AuthType basic
AuthName "LinuxMCE"
AuthUserFile /etc/apache2/httpd.passwd
Require valid-user

</LocationMatch>

# Since mythweb has it's own rewrites in a .htaccess file https redirection is enabled only on other urls
<LocationMatch "^/(?!mythweb).*">
# Force clients from the Internet to use HTTPS
RewriteEngine on
RewriteCond %{REMOTE_ADDR} !^192\.168\.80\.[0-9]+$
RewriteCond %{HTTPS} !=on
RewriteRule ^/(.*) https://%{SERVER_NAME}/$2 [R,L]
</LocationMatch>

</pre>

On the top of httpd.conf add the fully qualified domain name of your box that you added by "Common Name (eg, YOUR name)" when creating the certificate:

ServerName linuxmce.yourdomain.com

we have to change the beginning of vi /etc/apache2/sites-available/pluto to:
<pre>
# NameVirtualHost *
<VirtualHost *:80>
</pre>

and then copy this file:
cp /etc/apache2/sites-available/pluto /etc/apache2/sites-available/pluto443

then change the beginnig to:
<pre>
# NameVirtualHost *
<VirtualHost *:443>
SSLEngine On
</pre>

make a symbolic link:
ln -s /etc/apache2/sites-available/pluto443 /etc/apache2/sites-enabled/pluto443

go to pluto web admin and to Advanced>Network>Firewall and add a new rule:
tcp 443 443 core_input

then run:

apache2ctl restart

Torrentflux

2008-09-13T13:37:17Z

Esperanto:

= Torrentflux =

I wanted to make the use of torrents a little easier. So installed torrentflux (apt-get install torrentflux).

To het an extra folder button to move the files to the media directory and an unrar (you need to install it also) button via the webinterface I changed the following:

Add to lines to the bottom of the sudoers file:
sudo vi /etc/sudoers
<pre>
www-data ALL=(root) NOPASSWD: /bin/chown root\:public /var/cache/torrentflux/[a-zA-Z0-9]*/*
www-data ALL=(root) NOPASSWD: /bin/mv /var/cache/torrentflux/[a-zA-Z0-9]*/* /home/public/data/*
</pre>

add the following code to the file /usr/share/torrentflux/www/dir.php. I have put it just above:
<pre>
// Are we to delete something?
if ($del != "")
</pre>

the code:
<pre>
// Are we to unrar something?
$rar = getRequestVar('rar');
if ($rar != "")
{

$current = "";

$rar = stripslashes(stripslashes($rar));

$command = "cd ". escapeshellarg(dirname($cfg["path"] . $rar)) ."; /usr/bin/unrar x " . escapeshellarg($cfg["path"] . $rar);
passthru($command);
session_write_close();
}

// Are we to move something?
$move = getRequestVar('move');
if ($move != "")
{

$current = "";

$move = stripslashes(stripslashes($move));

$command = "chmod -R 775 " . $cfg["path"] . $move;
$result = exec($command);

$command = "sudo chown root:public " . $cfg["path"] . $move;
$result .= exec($command);

$command = "sudo mv " . $cfg["path"] . $move . " " . "/home/public/data/videos/";
$result .= exec($command);

header("Location: dir.php?dir=".urlencode($dir));
}

// Are we to rename something?
$rename = getRequestVar('rename');
$toname = getRequestVar('toname');
if ($rename != "" && $toname != "")
{
echo "<pre>" . $rename . " to: " . $toname . "</pre>";
$current = "";

$rename = stripslashes(stripslashes($rename));
$toname = stripslashes(stripslashes($toname));

$command = "mv " . $cfg["path"] . $rename . " " . $cfg["path"] . toname;
$result .= exec($command);

echo "<pre>" . "mv " . $cfg["path"] . $rename . " " . $cfg["path"] . dirname($rename) . "/" . $toname . "</pre>";
header("Location: dir.php?dir=".urlencode($dir));
}

</pre>

Then just below this:
<pre>
echo "</td>";
echo "<td align=\"right\">".$fileSize." KB</td>";
echo "<td>".date("m-d-Y g:i a", $timeStamp)."</td>";
echo "<td align=\"right\">"
</pre>
add this code:
<pre>
if( 1 == 1 )
{
echo "<a href=\"dir.php?dir=".urlencode($dir)."&move=".urlencode($dir.$entry)."\" >";
echo "<img src=\"images/folder.png\" width=\"16\" height=\"16\" title=\"move to linuxMCE\" border=\"0\"></a>";
}

echo "<a href=\"javascript:popRename('" . urlencode(addslashes($dir.$entry)) ."');\">rn</a>";

if( ( substr( strtolower($entry), -4 ) == ".rar" ) )
{
echo "<a href=\"dir.php?rar=".urlencode($dir.$entry)."\" >";
echo "<img src=\"".$image."\" width=\"16\" height=\"16\" title=\"unrar\" border=\"0\"></a>";
}

</pre>

after:
<pre>
$dirName = stripslashes($dirName);

if (isset($dir))
{
</pre>

put the code:
<pre>
$javascript = <<<JSPOPRENAME
<script type='text/javascript' language='javascript'>
function popRename(name){

newwindow2=window.open('','name','height=100,width=550');
var tmp = newwindow2.document;
tmp.write('<html><head><title>rename ' + name + '</title>');
tmp.write('<script type=\'text/javascript\' language=\'javascript\'>function getname(obj) {');
tmp.write('window.location=\'dir.php?rename=' + escape(name) + '&toname=\' + escape(obj.childNodes[0].value);');
tmp.write('self.close();');
tmp.write('}</scr' + 'ipt>');
tmp.write('</head><body>type new name below and press enter');
tmp.write('<form action="javascript:getname(document.getElementById(\'myform\'));" name="myform" id="myform">');
tmp.write('<input style="width: 450px" type="text" value="' + name + '"></form>');
tmp.write('refresh the original page to see the results.');
tmp.write('</body></html>');
tmp.close();
} </script>

JSPOPRENAME;

</pre>

Torrentflux

2008-09-13T12:29:34Z

Esperanto:

= Torrentflux =

I wanted to make the use of torrents a little easier. So installed torrentflux (apt-get install torrentflux).

To het an extra folder button to move the files to the media directory and an unrar (you need to install it also) button via the webinterface I changed the following:

Add to lines to the bottom of the sudoers file:
sudo vi /etc/sudoers
<pre>
www-data ALL=(root) NOPASSWD: /bin/chown root\:public /var/cache/torrentflux/[a-zA-Z0-9]*/*
www-data ALL=(root) NOPASSWD: /bin/mv /var/cache/torrentflux/[a-zA-Z0-9]*/* /home/public/data/*
</pre>

add the following code to the file /usr/share/torrentflux/www/dir.php. I have put it just above:
<pre>
// Are we to delete something?
if ($del != "")
</pre>

the code:
<pre>
// Are we to unrar something?
$rar = getRequestVar('rar');
if ($rar != "")
{

$current = "";

$rar = stripslashes(stripslashes($rar));

$command = "cd ". escapeshellarg(dirname($cfg["path"] . $rar)) ."; /usr/bin/unrar x " . escapeshellarg($cfg["path"] . $rar);
passthru($command);
session_write_close();
}

// Are we to move something?
$move = getRequestVar('move');
if ($move != "")
{

$current = "";

$move = stripslashes(stripslashes($move));

$command = "chmod -R 775 " . $cfg["path"] . $move;
$result = exec($command);

$command = "sudo chown root:public " . $cfg["path"] . $move;
$result .= exec($command);

$command = "sudo mv " . $cfg["path"] . $move . " " . "/home/public/data/videos/";
$result .= exec($command);

header("Location: dir.php?dir=".urlencode($dir));
}

// Are we to rename something?
$rename = getRequestVar('rename');
$toname = getRequestVar('toname');
if ($rename != "" && $toname != "")
{
echo "<pre>" . $rename . " to: " . $toname . "</pre>";
$current = "";

$rename = stripslashes(stripslashes($rename));
$toname = stripslashes(stripslashes($toname));

$command = "mv " . $cfg["path"] . $rename . " " . $cfg["path"] . toname;
$result .= exec($command);

echo "<pre>" . "mv " . $cfg["path"] . $rename . " " . $cfg["path"] . dirname($rename) . "/" . $toname . "</pre>";
header("Location: dir.php?dir=".urlencode($dir));
}

</pre>

Then just below this:
<pre>
echo "</td>";
echo "<td align=\"right\">".$fileSize." KB</td>";
echo "<td>".date("m-d-Y g:i a", $timeStamp)."</td>";
echo "<td align=\"right\">"
</pre>
add this code:
<pre>
if( 1 == 1 )
{
echo "<a href=\"dir.php?dir=".urlencode($dir)."&move=".urlencode($dir.$entry)."\" >";
echo "<img src=\"images/folder.png\" width=\"16\" height=\"16\" title=\"move to linuxMCE\" border=\"0\"></a>";
}

echo "<form style=\"display:none\" action=\"javascript:get(document.getElementById('" . $entry ."'), '" . urlencode(addslashes($dir.$entry)) ."');\" name=\"" . $entry ."\" id=\"" . $entry ."\">";
echo '<input type="text" value="'. $entry . '"></form>';
echo "<a href=\"javascript:show(document.getElementById('" . $entry ."'));\">rn</a>";

if( ( substr( strtolower($entry), -4 ) == ".rar" ) )
{
echo "<a href=\"dir.php?rar=".urlencode($dir.$entry)."\" >";
echo "<img src=\"".$image."\" width=\"16\" height=\"16\" title=\"unrar\" border=\"0\"></a>";
}

</pre>

after:
<pre>
$dirName = stripslashes($dirName);

if (isset($dir))
{
</pre>

put the code:
<pre>
echo " <script type='text/javascript' language='javascript'>";
echo "function show(obj) {";
echo " obj.style.display = 'inline';";
echo "} ";

echo "function get(obj,name) {";

echo " window.location='dir.php?dir=".urlencode($dir)."&rename=' + name + '&toname=' + obj.childNodes[0].value ;";
echo "} </script>";
</pre>

Torrentflux

2008-09-13T10:56:49Z

Esperanto:

Torrentflux

2008-09-13T10:52:54Z

Esperanto: New page: = Torrentflux = I wanted to make the use of torrents a little easier. So installed torrentflux (apt-get install torrentflux). To het an extra folder button to move the files to the medi...

Gyration GYR3101US

2008-04-29T20:12:09Z

Esperanto:

[[Category: Hardware]]
[[Category: Input]]
[[Category: Infrared]]
[[Category: Tutorials]]

== Summary ==
[[Image:Gyration.JPG|right]]
The Gyration GYR3101US remote is identical in style to the [http://fiire.com/fiire-chief.php Fiire Chief]

And uses the gyro feature just like a mouse. The major difference is how the remote is detected and used by LMCE.

However the keys are not all mapped as nicely as the custom firmware of the Chief. However this can be simply updated by using the
[http://cf.ccmr.cornell.edu/cgi-bin/w3mman2html.cgi?xmodmap(1) Xmodmap] program, and its corresponding config file, to gain similar functionality from this remote.

The one I am using I purchased at [http://www.circuitcity.com/ssm/Gyration-Universal-Remote-Control-for-PC-GYR3101US/sem/rpsm/oid/178884/rpem/ccd/productDetail.do Circuit CIty] for $99US. This is only $50 less + shipping than the Fiire, but for those of us lucky enough to have a Circuit City nearby, it makes an inexpensive solution.

edit 4/13/2008
note, this can be found at new egg for $99+S/H http://www.newegg.com/Product/Product.aspx?Item=N82E16880105001 New Egg]

When the device is plugged in, it is identified and configured as a GO Wireless USB device. And the gyration mouse bit works immediatley. If this is all you want, your done. No more configuration is needed. In my case I wanted the "Ambience" (Volume/Lighting) control key mapped, as well as the Channel/Chapter function, and lets not forget the ability to pull up the menu while watching/listening to media. Also by default the Stop button will stop media playback, and the skip forward and back buttons work. Again, if this is all you want, your done :).

By default kubuntu/LMCE sees the volume up/down keys, the 10 key numbers, the MCE button, and the media control play/stop/ffwd/rwd/pause/skip fwd/skip back.

Gyration codes: [[Gyration-GYR3101US-codes]]

== The HowTo ==

To enable the volume control, I used the ''xev'' application from the KDE desktop terminal window, and identified the required keys.

xev

Once this is run, it will pop-up a test window. Place your mouse in there, and then press the buttons on the Gyration remote, and see the results in the terminal. Pay special attention to the

keycode

entries, they are what you will place in your new .Xmodmap file.

Now on my particular setup, and I have a feeling its the default, the keys show up as:

Volume Up keycode 176
Volume Down keycode 174
MCE button keycode 97

Now the keys in LMCE that provide for the volume/channel/menu function are:

F6 = Channel/Chapter FFWD/RWD/PAUSE menu
F7 = Menu button
F8 = Volume/Lighting button "ambience"

== Update to get more MythTV functionality!!! ==

MythTV Keys

P = Pause # Pause key on remote
R = Record # Record key on remote
Z = 30 second skip # Right skip key under directional pad
Q = 10 second back # Left skip key under directional pad
I = Info # Info button
F9 = Mute # Mute button
Y = Switch Cards # Pictures button
PgUP = Fast Forward # FFWD Button
PgDOWN = Rewind # RWND Button

Using this info, I created the following .Xmodmap file as root user in /etc

cd /etc
sudo vi /etc/.Xmodmap

/etc/.Xmodmap
keycode 176 = F8
keycode 174 = F6
keycode 97 = F7
keycode 110 = P
keycode 177 = R
keycode 153 = Z
keycode 144 = Q
keycode 134 = I
keycode 160 = F9
keycode 237 = Y
keycode 180 = PgUP
keycode 152 = PgDOWN

Now after creating the file, we need to make sure it is loaded when LMCE starts up. To do this add the following as root to
''/usr/pluto/bin/lmce_launch_manager.sh''

sudo vi /usr/pluto/bin/lmce_launch_manager.sh
Put this right before the line '''KDE_DEBUG=1'''
So that it looks like.....
xmodmap /etc/.Xmodmap
KDE_DEBUG=1

Save the file. Now you have two choices to get it going,

Choice 1 is to fire off the command
sudo xmodmap /etc/.Xmodmap
This must be done from the KDE desktop term window, as it needs to be run in the X environment. (you can also export the display like: export DISPLAY=:0;xmodmap /etc/.Xmodmap )

Choice 2 is to restart the core.

By placing the file in the lmce_launch_manager.sh script, anytime the core is rebooted, your settings are automagically set up. :)

There are a couple of oddities to deal with that I have seen. Now when I watch a movie, and want to change the volume or lighting, on a movie or pre-recorded program, it does what it supposed to, but when watching mythtv live, pressing the volume up on the Gyration remote invokes the Sleep Timer in mythtv. This can be easily resolved by remapping the sleep timer key using the mythweb application located at http://core.ip.address/mythweb/ for internal open systems or http://core.dhcp.server.adress/mythweb/

This can be avoided by unmapping the following keys in Mythweb/Settings/Controls

F6
F7
F8

Simply unmap these keys. Make sure you scroll down the whole list, as they appear more than once :)

So after you have completed these steps the following keys will do these functions:

MCE button pulls up LMCE menu system
Volume Up button brings up the "Ambience" controls during media playback
Volume Down button brings up the Channel/Chapter Fast Forward/Rewind and Pause functions
The Gyration center button does movement
If you double click the center button, the mouse stays active,
but remember to click once more to turn off, or you'll kill the batteries.
The Gyration Left button acts like the left mouse button for "Choose" functions
The Gyration Right button is the "exit" or "clear item" button.
The left and right buttons are just like mouse buttons.
The Number keys work with MythTV
The Pause button will pause MythTV
The Record button will start an on-the-fly-recording
The skip forward button, does the standard 30 second skip
The skip back button does the 10 second back skip
The fast-forward and rewind buttons function as they should
The Pictures button, will switch tuner cards if you have more than one, Nice for us DVB users who don't use VDR.
The Mute button functions
The Info button functions

Thats it, your ready to be Inter "Active" with your LMCE system. Enjoy.

Please feel free to update this article with any other information, or if I forgot something. :-)

Receivers rs-232

2008-04-09T10:22:29Z

Esperanto:

= Receivers rs-232 support =
Here is a list of receivers that do or do not have rs-232 (serial port) support

== Denon ==
{| class="wikitable" border="1" cellpadding="5" cellspacing="0"
|-
! model
! rs-232 port
! rs-232 controllable
! lmce support
|-
| AVR-2307
|
|
|
|-
| AVR-2308
|
|
|
|-
| AVR-2807
|
|
|
|-
| AVR-2808
|
|
|
|-
| AVR-3807
|
|
|
|-
| AVR-4306
|
|
|
|}

== Harman Kardon ==
{| class="wikitable" border="1" cellpadding="5" cellspacing="0"
|-
! model
! rs-232 port
! rs-232 controllable
! lmce support
|-
| AVR 247
| yes
| no
|
|-
| AVR 347
|
|
|
|}

== Marantz ==
{| class="wikitable" border="1" cellpadding="5" cellspacing="0"
|-
! model
! rs-232 port
! rs-232 controllable
! lmce support
|-
| SR5001
|
|
|
|-
| SR5002
|
|
|
|-
| [http://www.marantz.com/new/index.cfm?fuseaction=Products.Product&cont=eu&bus=hf&prod_id=3662&series=comp&type=avr SR6001 ]
|
|
|
|-
| SR7001
| yes
| yes
|
|-
| [http://www.marantz.com/new/index.cfm?fuseaction=Products.Product&cont=eu&bus=hf&prod_id=3702&series=comp&type=avr SR7002]
|
|
|
|-
| ZR6001
|
|
|
|}

== Meridian ==
{| class="wikitable" border="1" cellpadding="5" cellspacing="0"
|-
! model
! rs-232 port
! rs-232 controllable
! lmce support
|-
| [http://www.meridian-audio.com/p_g68.htm G68-ADV]
| yes
| yes
|
|}

== NAD ==
{| class="wikitable" border="1" cellpadding="5" cellspacing="0"
|-
! model
! rs-232 port
! rs-232 controllable
! lmce support
|-
| T-765
|
|
|
|-
| T-773
|
|
|
|}

== Onkyo ==
{| class="wikitable" border="1" cellpadding="5" cellspacing="0"
|-
! model
! rs-232 port
! rs-232 controllable
! lmce support
|-
| TX-SR705
|
|
|
|-
| TX-SR875
|
|
|
|}

== Pioneer ==
{| class="wikitable" border="1" cellpadding="5" cellspacing="0"
|-
! model
! rs-232 port
! rs-232 controllable
! lmce support
|-
| VSX-LX60
|
|
|
|-
| VSX-LX70
|
|
|
|}

== Sony ==
{| class="wikitable" border="1" cellpadding="5" cellspacing="0"
|-
! model
! rs-232 port
! rs-232 controllable
! lmce support
|-
| STR-DA3000ES
|
|
|
|-
| STR-DA3200ES
|
|
|
|}

== Yamaha ==
{| class="wikitable" border="1" cellpadding="5" cellspacing="0"
|-
! model
! rs-232 port
! rs-232 controllable
! lmce support
|-
| RX-V1700
|
|
|
|-
| RX-V1800
|
|
|
|-
| RX-V2700
|
|
|
|}

Receivers rs-232

2008-04-09T10:10:56Z

Esperanto:

= Receivers rs-232 support =
Here is a list of receivers that do or do not have rs-232 (serial port) support

== Denon ==
{| class="wikitable" border="1" cellpadding="5" cellspacing="0"
|-
! model
! rs-232 port
! rs-232 controllable
! lmce support
|-
| AVR-2307
|
|
|
|-
| AVR-2308
|
|
|
|-
| AVR-2807
|
|
|
|-
| AVR-2808
|
|
|
|-
| AVR-3807
|
|
|
|-
| AVR-4306
|
|
|
|}

== Harman Kardon ==
{| class="wikitable" border="1" cellpadding="5" cellspacing="0"
|-
! model
! rs-232 port
! rs-232 controllable
! lmce support
|-
| AVR 247
| yes
| no
|
|-
| AVR 347
|
|
|
|}

== Marantz ==
{| class="wikitable" border="1" cellpadding="5" cellspacing="0"
|-
! model
! rs-232 port
! rs-232 controllable
! lmce support
|-
| SR5001
|
|
|
|-
| SR5002
|
|
|
|-
| SR6001
|
|
|
|-
| SR7001
| yes
| yes
|
|-
| ZR6001
|
|
|
|}

== Meridian ==
{| class="wikitable" border="1" cellpadding="5" cellspacing="0"
|-
! model
! rs-232 port
! rs-232 controllable
! lmce support
|-
| [http://www.meridian-audio.com/p_g68.htm G68-ADV]
| yes
| yes
|
|}

== NAD ==
{| class="wikitable" border="1" cellpadding="5" cellspacing="0"
|-
! model
! rs-232 port
! rs-232 controllable
! lmce support
|-
| T-765
|
|
|
|-
| T-773
|
|
|
|}

== Onkyo ==
{| class="wikitable" border="1" cellpadding="5" cellspacing="0"
|-
! model
! rs-232 port
! rs-232 controllable
! lmce support
|-
| TX-SR705
|
|
|
|-
| TX-SR875
|
|
|
|}

== Pioneer ==
{| class="wikitable" border="1" cellpadding="5" cellspacing="0"
|-
! model
! rs-232 port
! rs-232 controllable
! lmce support
|-
| VSX-LX60
|
|
|
|-
| VSX-LX70
|
|
|
|}

== Sony ==
{| class="wikitable" border="1" cellpadding="5" cellspacing="0"
|-
! model
! rs-232 port
! rs-232 controllable
! lmce support
|-
| STR-DA3000ES
|
|
|
|-
| STR-DA3200ES
|
|
|
|}

== Yamaha ==
{| class="wikitable" border="1" cellpadding="5" cellspacing="0"
|-
! model
! rs-232 port
! rs-232 controllable
! lmce support
|-
| RX-V1700
|
|
|
|-
| RX-V1800
|
|
|
|-
| RX-V2700
|
|
|
|}

Receivers rs-232

2008-04-09T10:06:34Z

Esperanto:

= Receivers rs-232 support =
Here is a list of receivers that do or do not have rs-232 (serial port) support

== Denon ==
{| class="wikitable" border="1" cellpadding="5" cellspacing="0"
|-
! model
! rs-232 port
! rs-232 controllable
! lmce support
|-
| AVR-2307
|
|
|
|-
| AVR-2308
|
|
|
|-
| AVR-2807
|
|
|
|-
| AVR-2808
|
|
|
|-
| AVR-3807
|
|
|
|-
| AVR-4306
|
|
|
|}

== Harman Kardon ==
{| class="wikitable" border="1" cellpadding="5" cellspacing="0"
|-
! model
! rs-232 port
! rs-232 controllable
! lmce support
|-
| AVR 247
| yes
| no
|
|-
| AVR 347
|
|
|
|}

== Marantz ==
{| class="wikitable" border="1" cellpadding="5" cellspacing="0"
|-
! model
! rs-232 port
! rs-232 controllable
! lmce support
|-
| SR5001
|
|
|
|-
| SR5002
|
|
|
|-
| SR6001
|
|
|
|-
| SR7001
|
|
|
|-
| ZR6001
|
|
|
|}

== Meridian ==
{| class="wikitable" border="1" cellpadding="5" cellspacing="0"
|-
! model
! rs-232 port
! rs-232 controllable
! lmce support
|-
| G68-ADV
| yes
| yes
|
|}

== NAD ==
{| class="wikitable" border="1" cellpadding="5" cellspacing="0"
|-
! model
! rs-232 port
! rs-232 controllable
! lmce support
|-
| T-765
|
|
|
|-
| T-773
|
|
|
|}

== Onkyo ==
{| class="wikitable" border="1" cellpadding="5" cellspacing="0"
|-
! model
! rs-232 port
! rs-232 controllable
! lmce support
|-
| TX-SR705
|
|
|
|-
| TX-SR875
|
|
|
|}

== Pioneer ==
{| class="wikitable" border="1" cellpadding="5" cellspacing="0"
|-
! model
! rs-232 port
! rs-232 controllable
! lmce support
|-
| VSX-LX60
|
|
|
|-
| VSX-LX70
|
|
|
|}

== Sony ==
{| class="wikitable" border="1" cellpadding="5" cellspacing="0"
|-
! model
! rs-232 port
! rs-232 controllable
! lmce support
|-
| STR-DA3000ES
|
|
|
|-
| STR-DA3200ES
|
|
|
|}

== Yamaha ==
{| class="wikitable" border="1" cellpadding="5" cellspacing="0"
|-
! model
! rs-232 port
! rs-232 controllable
! lmce support
|-
| RX-V1700
|
|
|
|-
| RX-V1800
|
|
|
|-
| RX-V2700
|
|
|
|}

Receivers rs-232

2008-04-09T09:56:52Z

Esperanto:

= Receivers rs-232 support =
Here is a list of receivers that do or do not have rs-232 (serial port) support

== Denon ==
{| class="wikitable" border="1" cellpadding="5" cellspacing="0"
|-
! model
! rs-232 port
! rs-232 controllable
! lmce support
|-
| AVR-2307
|
|
|
|-
| AVR-2308
|
|
|
|-
| AVR-2807
|
|
|
|-
| AVR-2808
|
|
|
|-
| AVR-3807
|
|
|
|-
| AVR-4306
|
|
|
|}

== Harman Kardon ==
{| class="wikitable" border="1" cellpadding="5" cellspacing="0"
|-
! model
! rs-232 port
! rs-232 controllable
! lmce support
|-
| AVR 247
| yes
| no
|
|-
| AVR 347
|
|
|
|}

== Marantz ==
{| class="wikitable" border="1" cellpadding="5" cellspacing="0"
|-
! model
! rs-232 port
! rs-232 controllable
! lmce support
|-
|
|
|
|
|}

== Onkyo ==
{| class="wikitable" border="1" cellpadding="5" cellspacing="0"
|-
! model
! rs-232 port
! rs-232 controllable
! lmce support
|-
| TX-SR705
|
|
|
|-
| TX-SR875
|
|
|
|}

== Pioneer ==
{| class="wikitable" border="1" cellpadding="5" cellspacing="0"
|-
! model
! rs-232 port
! rs-232 controllable
! lmce support
|-
|
|
|
|
|-
|
|
|
|
|}

== Onkyo ==
{| class="wikitable" border="1" cellpadding="5" cellspacing="0"
|-
! model
! rs-232 port
! rs-232 controllable
! lmce support
|-
|
|
|
|
|-
|
|
|
|
|}

== Sony ==
{| class="wikitable" border="1" cellpadding="5" cellspacing="0"
|-
! model
! rs-232 port
! rs-232 controllable
! lmce support
|-
|
|
|
|
|-
|
|
|
|
|}

== Yamaha ==
{| class="wikitable" border="1" cellpadding="5" cellspacing="0"
|-
! model
! rs-232 port
! rs-232 controllable
! lmce support
|-
|
|
|
|
|-
|
|
|
|
|}

Receivers rs-232

2008-04-09T09:46:47Z

Esperanto: New page: = Receivers rs-232 support = Here is a list of receivers that do or do not have rs-232 (serial port) support {| class="wikitable" border="1" cellpadding="5" cellspacing="0" |- ! brand ! m...

= Receivers rs-232 support =
Here is a list of receivers that do or do not have rs-232 (serial port) support

{| class="wikitable" border="1" cellpadding="5" cellspacing="0"
|-
! brand
! model
! rs-232 port
! rs-232 controllable
! lmce support
|-
| rowspan="1" valign="top"|Denon
|
|
|
|
|-
| rowspan="2" valign="top"|Harman Kardon
| AVR 247
| yes
| no
|
|-
| AVR 347
|
|
|
|-
| rowspan="1" valign="top"|Marantz
|
|
|
|
|-
| rowspan="1" valign="top"|Onkyo
|
|
|
|
|-
| rowspan="1" valign="top"|Pioneer
|
|
|
|
|-
| rowspan="1" valign="top"|Sony
|
|
|
|
|-
| rowspan="1" valign="top"|Yamaha
|
|
|
|
|}

Serial Port debugging

2008-03-05T21:38:30Z

Esperanto:

== Debugging serial Port (Com port/RS-232) ==

You can use minicom (apt-get install minicom)

# minicom

then press ctcl-a z to open the help interface

select 'o'

goto 'Serial port setup'

Set the Serial device to the port you want to test
In my case I also had to set:
- Bps/Par/Bits: 9600 8N1
- Hardware Flow Control : No

Exit this screen and then select:
* 'Save setup as dfl'
(this makes this configuration default next time you start minicom)

Exit this screen

then reinitialize the modem (m)

you should enable local echo so you can see what you type.
* ctrl-a e

When you type the command the device should respond.

Testing turn of delay command line for my TV:
* echo "ka 01 01"> /dev/ttyS1;sleep 7.4;echo "kb 01 01" > /dev/ttyS1

Serial Port debugging

2008-03-05T20:27:09Z

Esperanto: New page: == Debugging serial Port (Com port/RS-232) == You can use minicom (apt-get install minicom) # minicom then press ctcl-a z to open the help interface select 'o' goto 'Serial port set...

Gyration-GYR3101US-codes

2008-03-05T19:17:42Z

Esperanto:

== ToDo ==

The best solution would be if we could make it work without evrouter. Then we should need some way to have the higher keyevents in X. Any suggestions??

Using [http://www.bedroomlan.org/~alexios/coding_evrouter.html evrouter] we would still need the following:
* LinuxMCE should recognize the remote properly (now it saids it's a GO Cordless GC1005M but 'Registered: No')
* This means we should reuse the fiire chief template (if it's possible to reroute it that way) or create a new one
* Evrouter should route all high events to have the proper actions (so to key events or shell commands) (see the [[Gyration-GYR3101US-codes#Working_document_for_usage_with_evrouter | template]])
* Evrouter should be supplied with Lmce
* it should have a proper way to automaticly start evrouter with the right configuration

== Code table ==
{| class="wikitable" border="1" cellpadding="5" cellspacing="0"
|-
! name
! xev keycode
! evkeycode
|-
| Stop
| 164
| key/166
|-
| Record
| 177
| key/167
|-
| Pause
| 110
| key/119
|-
| Play
| 179
| key/207
|-
| Rewind
| 152
| key/168
|-
| Fast Forward
| 180
| key/208
|-
| Skip back
| 144
| key/165
|-
| Skip ahead
| 153
| key/163
|}

{| class="wikitable" border="1" cellpadding="5" cellspacing="0"
|-
! name
! xev keycode
! evkeycode
|-
| Live TV
| -
| key/377
|-
| UP
| 98
| key/103
|-
| Program guide
| -
| key/362
|-
| LEFT
| 100
| key/105
|-
| OK/Enter/Select
| 36
| key/28
|-
| Right
| 102
| key/106
|-
| Go back
| 234
| key/158
|-
| Down
| 104
| key/108
|-
| Information
| 134
| key/130
|}

{| class="wikitable" border="1" cellpadding="5" cellspacing="0"
|-
! name
! xev keycode
! evkeycode
|-
| Left mouse button
|
| key/272
|-
| Mouse enable
|
| -
|-
| Right mouse button
|
| key/273
|}

{| class="wikitable" border="1" cellpadding="5" cellspacing="0"
|-
! name
! xev keycode
! evkeycode
|-
| Volume UP
| 176
| key/115
|-
| MCE Home
| 97
| key/102
|-
| Channel UP
| -
| key/402
|-
| Volume Down
| 174
| key/114
|-
| Mute
| 160
| key/113
|-
| Channel Down
| -
| key/403
|}

{| class="wikitable" border="1" cellpadding="5" cellspacing="0"
|-
! name
! xev keycode
! evkeycode
|-
| My Pictures
| 237
| key/226
|-
| TV home
| -
| -
|-
| Music
| -
| key/391
|-
| My videos
| -
| key/393
|}

{| class="wikitable" border="1" cellpadding="5" cellspacing="0"
|-
! name
! xev keycode
! evkeycode
|-
| 1
| 10
| key/2
|-
| 2
| 11
| key/3
|-
| 3
| 12
| key/4
|-
| 4
| 13
| key/5
|-
| 5
| 14
| key/6
|-
| 6
| 15
| key/7
|-
| 7
| 16
| key/8
|-
| 8
| 17
| key/9
|-
| 9
| 18
| key/10
|-
| *
| 50 & 17
| key/42 & key/9
|-
| 0
| 19
| key/11
|-
| #
| 50&12
| key/42 & key/4
|}

{| class="wikitable" border="1" cellpadding="5" cellspacing="0"
|-
! name
! xev keycode
! evkeycode
|-
| clear
| 9
| key/1
|-
| enter
| 36
| key/28
|}

{| class="wikitable" border="1" cellpadding="5" cellspacing="0"
|-
! name
! xev keycode
! evkeycode
|-
| Setup Menu
| -
| -
|-
| Last
| -
| -
|-
| Connect
| -
| -
|-
| Input
| -
| -
|-
| DVD Menu
| -
| key/410
|}

== Picture ==
[[Image:Gyration-GYR3101US-codes.png]]

== Device Template info (based on template #1848) ==
<pre>
The Device Template.
Values taken from the gyration template for the fiire-chief.

These values are probably the same as on the fiire-chief:
1,10,U,Y
2,11,U,Y
3,12,U,Y
4,13,U,Y
5,14,U,Y
6,15,U,Y
7,16,U,Y
8,17,U,Y
9,18,U,Y
0,19,U,Y
shortcut1,10,H,Y
shortcut2,11,H,Y
shortcut3,12,H,Y
shortcut4,13,H,Y
shortcut5,14,H,Y
shortcut6,15,H,Y
shortcut7,16,H,Y
shortcut8,17,H,Y
shortcut9,18,H,Y
shortcut0,19,H,Y

fastforward,180,D
Rewind,152,D
Play,179,D
Stop,164,D

Down,104,R,Y
Up,98,R,Y
Left,100,R,Y
Right,102,R,Y
ok,36,D,Y
enter,36,D,Y
Record,177,D
SkipNext,153,R
SkipPrior,144,R

These have standard 'xev' output keys (and differ from the fiire):
Clear,9,D
voldn,176,R
VolUp,174,R

How to set these and which they are is still the question:
Power,100130,U
Halt,100130,H

red,100070,U
green,100073,U
yellow,100071,U
blue,100074,U
shortcutr,100070,H
shortcutg,100073,H
shortcuty,100071,H
shortcutb,100074,H
Music,100071,U
Videos,100074,U
tv,100073,U
Pictures,100070,U

enter,108,D,Y

chup,100156,R
chdown,100157,R

Pause,162,D
Pause,110,D

Mute,100226,D

menu,100194,U
avwizard,100194,H

Guide,100141,D

Back,100193,D

info,100201,U
help,100201,H

input,100202,U
</pre>

== Working document for usage with evrouter ==
<pre>
# Stop
# "Gyration Gyration RF Technology Receiver" "/dev/input/event*" none key/166 "fill this in!"

# Record
"Gyration Gyration RF Technology Receiver" "/dev/input/event*" none key/167 "XKey/R"

# Pause
"Gyration Gyration RF Technology Receiver" "/dev/input/event*" none key/119 "XKey/P"

# Play
"Gyration Gyration RF Technology Receiver" "/dev/input/event*" none key/207 "XKey/P"

# Rewind
"Gyration Gyration RF Technology Receiver" "/dev/input/event*" none key/168 "XKey/Left"

# Fast Forward
"Gyration Gyration RF Technology Receiver" "/dev/input/event*" none key/208 "XKey/Right"

# Skip Back
"Gyration Gyration RF Technology Receiver" "/dev/input/event*" none key/165 "XKey/Home"

# Skip Forward
"Gyration Gyration RF Technology Receiver" "/dev/input/event*" none key/163 "XKey/End"

# Guide
"Gyration Gyration RF Technology Receiver" "/dev/input/event*" none key/362 "XKey/M"

# Up
# "Gyration Gyration RF Technology Receiver" "/dev/input/event*" none key/103 "fill this in!"

# Left
# "Gyration Gyration RF Technology Receiver" "/dev/input/event*" none key/105 "fill this in!"

# Right
# "Gyration Gyration RF Technology Receiver" "/dev/input/event*" none key/106 "fill this in!"

# Down
# "Gyration Gyration RF Technology Receiver" "/dev/input/event*" none key/108 "fill this in!"

# Back
# "Gyration Gyration RF Technology Receiver" "/dev/input/event*" none key/158 "fill this in!"

# Info
"Gyration Gyration RF Technology Receiver" "/dev/input/event*" none key/130 "XKey/I"

# OK/Enter
# "Gyration Gyration RF Technology Receiver" "/dev/input/event*" none key/28 "fill this in!"

# Volume Up
"Gyration Gyration RF Technology Receiver" "/dev/input/event*" none key/115 "XKey/F11"

# Volume Down
"Gyration Gyration RF Technology Receiver" "/dev/input/event*" none key/114 "XKey/F10"

# Channel Up
"Gyration Gyration RF Technology Receiver" "/dev/input/event*" none key/402 "XKey/Up"

# Channel Down
"Gyration Gyration RF Technology Receiver" "/dev/input/event*" none key/403 "XKey/Down"

# Mute
"Gyration Gyration RF Technology Receiver" "/dev/input/event*" none key/113 "XKey/F9"

# 1
# "Gyration Gyration RF Technology Receiver" "/dev/input/event*" none key/2 "fill this in!"
#
# 2
# "Gyration Gyration RF Technology Receiver" "/dev/input/event*" none key/3 "fill this in!"
#
# 3
# "Gyration Gyration RF Technology Receiver" "/dev/input/event*" none key/4 "fill this in!"
#
# 4
# "Gyration Gyration RF Technology Receiver" "/dev/input/event*" none key/5 "fill this in!"
#
# 5
# "Gyration Gyration RF Technology Receiver" "/dev/input/event*" none key/6 "fill this in!"
#
# 6
# "Gyration Gyration RF Technology Receiver" "/dev/input/event*" none key/7 "fill this in!"
#
# 7
# "Gyration Gyration RF Technology Receiver" "/dev/input/event*" none key/8 "fill this in!"
#
# 8
# "Gyration Gyration RF Technology Receiver" "/dev/input/event*" none key/9 "fill this in!"
#
# 9
# "Gyration Gyration RF Technology Receiver" "/dev/input/event*" none key/10 "fill this in!"
#
# 0
# "Gyration Gyration RF Technology Receiver" "/dev/input/event*" none key/11 "fill this in!"
#
# *
# "Gyration Gyration RF Technology Receiver" "/dev/input/event*" none key/42 "fill this in!"
# "Gyration Gyration RF Technology Receiver" "/dev/input/event*" none key/9 "fill this in!"
#
# #
# "Gyration Gyration RF Technology Receiver" "/dev/input/event*" none key/42 "fill this in!"
# "Gyration Gyration RF Technology Receiver" "/dev/input/event*" none key/4 "fill this in!"

# Clear
# "Gyration Gyration RF Technology Receiver" "/dev/input/event*" none key/1 "fill this in!"

# Other /dev/input/eventY events:
# Left Click
# "Gyration Gyration RF Technology Receiver" "/dev/input/event*" none key/272 "fill this in!"
#
# Right Click
# "Gyration Gyration RF Technology Receiver" "/dev/input/event*" none key/273 "fill this in!"

# Live TV
"Gyration Gyration RF Technology Receiver" "/dev/input/event*" none key/377 "XKey/C"

# Windows
"Gyration Gyration RF Technology Receiver" "/dev/input/event*" none key/102 "XKey/Alt_L+Control_L+BackSpace"

# Pictures
# "Gyration Gyration RF Technology Receiver" "/dev/input/event*" none key/226 "fill this in!"
#
# Music
# "Gyration Gyration RF Technology Receiver" "/dev/input/event*" none key/391 "fill this in!"
#
# Video
# "Gyration Gyration RF Technology Receiver" "/dev/input/event*" none key/393 "fill this in!"

# DVD Menu
"Gyration Gyration RF Technology Receiver" "/dev/input/event*" none key/410 "XKey/O"
</pre>

== evtest output ==
evtest ( apt-get install lineakd ) gives the following output:

<pre>
Input driver version is 1.0.0
Input device ID: bus 0x3 vendor 0xc16 product 0x2 version 0x110
Input device name: "Gyration Gyration RF Technology Receiver"
Supported events:
Event type 0 (Sync)
Event type 1 (Key)
Event code 1 (Esc)
Event code 2 (1)
Event code 3 (2)
Event code 4 (3)
Event code 5 (4)
Event code 6 (5)
Event code 7 (6)
Event code 8 (7)
Event code 9 (8)
Event code 10 (9)
Event code 11 (0)
Event code 12 (Minus)
Event code 13 (Equal)
Event code 14 (Backspace)
Event code 15 (Tab)
Event code 16 (Q)
Event code 17 (W)
Event code 18 (E)
Event code 19 (R)
Event code 20 (T)
Event code 21 (Y)
Event code 22 (U)
Event code 23 (I)
Event code 24 (O)
Event code 25 (P)
Event code 26 (LeftBrace)
Event code 27 (RightBrace)
Event code 28 (Enter)
Event code 29 (LeftControl)
Event code 30 (A)
Event code 31 (S)
Event code 32 (D)
Event code 33 (F)
Event code 34 (G)
Event code 35 (H)
Event code 36 (J)
Event code 37 (K)
Event code 38 (L)
Event code 39 (Semicolon)
Event code 40 (Apostrophe)
Event code 41 (Grave)
Event code 42 (LeftShift)
Event code 43 (BackSlash)
Event code 44 (Z)
Event code 45 (X)
Event code 46 (C)
Event code 47 (V)
Event code 48 (B)
Event code 49 (N)
Event code 50 (M)
Event code 51 (Comma)
Event code 52 (Dot)
Event code 53 (Slash)
Event code 54 (RightShift)
Event code 55 (KPAsterisk)
Event code 56 (LeftAlt)
Event code 57 (Space)
Event code 58 (CapsLock)
Event code 59 (F1)
Event code 60 (F2)
Event code 61 (F3)
Event code 62 (F4)
Event code 63 (F5)
Event code 64 (F6)
Event code 65 (F7)
Event code 66 (F8)
Event code 67 (F9)
Event code 68 (F10)
Event code 69 (NumLock)
Event code 70 (ScrollLock)
Event code 71 (KP7)
Event code 72 (KP8)
Event code 73 (KP9)
Event code 74 (KPMinus)
Event code 75 (KP4)
Event code 76 (KP5)
Event code 77 (KP6)
Event code 78 (KPPlus)
Event code 79 (KP1)
Event code 80 (KP2)
Event code 81 (KP3)
Event code 82 (KP0)
Event code 83 (KPDot)
Event code 86 (102nd)
Event code 87 (F11)
Event code 88 (F12)
Event code 96 (KPEnter)
Event code 97 (RightCtrl)
Event code 98 (KPSlash)
Event code 99 (SysRq)
Event code 100 (RightAlt)
Event code 102 (Home)
Event code 103 (Up)
Event code 104 (PageUp)
Event code 105 (Left)
Event code 106 (Right)
Event code 107 (End)
Event code 108 (Down)
Event code 109 (PageDown)
Event code 110 (Insert)
Event code 111 (Delete)
Event code 113 (Mute)
Event code 114 (VolumeDown)
Event code 115 (VolumeUp)
Event code 116 (Power)
Event code 119 (Pause)
Event code 125 (LeftMeta)
Event code 126 (RightMeta)
Event code 127 (Compose)
Event code 128 (Stop)
Event code 130 (Props)
Event code 131 (Undo)
Event code 133 (Copy)
Event code 134 (Open)
Event code 135 (Paste)
Event code 136 (Find)
Event code 137 (Cut)
Event code 138 (Help)
Event code 139 (Menu)
Event code 140 (Calc)
Event code 142 (Sleep)
Event code 143 (WakeUp)
Event code 144 (File)
Event code 150 (WWW)
Event code 152 (Coffee)
Event code 155 (Mail)
Event code 156 (Bookmarks)
Event code 158 (Back)
Event code 159 (Forward)
Event code 161 (EjectCD)
Event code 163 (NextSong)
Event code 164 (PlayPause)
Event code 165 (PreviousSong)
Event code 166 (StopCD)
Event code 167 (Record)
Event code 168 (Rewind)
Event code 169 (Phone)
Event code 171 (Config)
Event code 172 (HomePage)
Event code 173 (Refresh)
Event code 174 (Exit)
Event code 177 (ScrollUp)
Event code 178 (ScrollDown)
Event code 181 (?)
Event code 206 (Close)
Event code 207 (Play)
Event code 208 (Fast Forward)
Event code 209 (Bass Boost)
Event code 210 (Print)
Event code 212 (Camera)
Event code 213 (Sound)
Event code 219 (Finance)
Event code 234 (?)
Event code 235 (?)
Event code 256 (Btn0)
Event code 358 (Info)
Event code 362 (Program)
Event code 366 (PVR)
Event code 376 (PC)
Event code 377 (TV)
Event code 378 (TV2)
Event code 379 (VCR)
Event code 380 (VCR2)
Event code 381 (Sat)
Event code 383 (CD)
Event code 384 (Tape)
Event code 385 (Radio)
Event code 386 (Tuner)
Event code 389 (DVD)
Event code 396 (Memo)
Event code 397 (Calendar)
Event code 402 (ChannelUp)
Event code 403 (ChannelDown)
Event code 405 (Last)
Event code 416 (?)
Event code 417 (?)
Event code 418 (?)
Event code 419 (?)
Event code 420 (?)
Event code 421 (?)
Event code 422 (?)
Event code 423 (?)
Event code 424 (?)
Event code 425 (?)
Event code 426 (?)
Event code 427 (?)
Event code 428 (?)
Event code 429 (?)
Event code 430 (?)
Event type 2 (Relative)
Event code 6 (HWheel)
Event type 3 (Absolute)
Event code 32 (Volume)
Value 0
Min 0
Max 572
Event type 20 (Repeat)
Testing ... (interrupt to exit)

</pre>