Official Kodi Wiki - User contributions [en]

Archive:Set up PS3 BD Remote

2014-10-18T18:45:59Z

Slvr32: Undo revision 79660 by Slvr32 (talk) - diregard? possible cache/indexing issue for old title?

This HOW-TO explains how to set up the remote control for the Sony PlayStation 3 to use with XBMC for Linux. You'll need a Bluetooth dongle and of course the remote control. All these information can be found [http://forum.xbmc.org/showthread.php?t=50717 here] at the forum.

== Installation ==

=== BlueZ ===
Note: Newer versions of bluez have been released which appear to have this patch already. I didn't need to patch 4.63 to get BD working on ubuntu 10.04

''Note:'' Kitlaan now has patches up to Bluez-4.69, and the patch is required for 4.64 - 4.69

The latest versions of the patch are available at: http://kitlaan.twinaxis.com/projects/bluez-ps3remote/

<pre>sudo apt-get purge bluez
sudo apt-get install libdbus-1-dev libglib2.0-dev python-dbus python-gobject
cd ~
wget http://kitlaan.twinaxis.com/projects/bluez-ps3remote/bluez_ps3remote_4.91.diff
wget http://www.kernel.org/pub/linux/bluetooth/bluez-4.91.tar.gz
tar xvfz bluez-4.91.tar.gz
cd bluez-4.91
patch -p1 < ../bluez_ps3remote_4.91.diff
./configure && make
sudo checkinstall --fstrans=no --install=yes --pkgname=bluez --pkgversion "4.91-patched"
</pre>
When starting bluetoothd, check /var/log/syslog to make sure the config files are read. If bluetoothd searches for them at /usr/etc, you'll have to create symlinks:
<pre>
sudo ln -s /etc/bluetooth/input.conf /usr/etc/bluetooth/input.conf
sudo ln -s /etc/bluetooth/audio.conf /usr/etc/bluetooth/audio.conf
sudo ln -s /etc/bluetooth/serial.conf /usr/etc/bluetooth/serial.conf
</pre>

Or, using [https://launchpad.net/~kitlaan/+archive/ppa kitlaan's PPA]:
<pre>
sudo apt-get purge bluez
sudo add-apt-repository ppa:kitlaan/ppa
sudo apt-get update
sudo apt-get install bluez
</pre>

=== Kernel module ===
Check if the uinput module is running:
<pre>lsmod | grep uinput</pre>
If that's not the case:
<pre>
sudo modprobe uinput
echo uinput >> /etc/modules
</pre>

=== Pairing ===
Please note that the pairing script requires that the dbus-python and pygobject python modules are installed. They are normally installed on a default 9.04 Jaunty.
(If you need them added, apt-get install python-dbus and python-gobject.)
<pre>cd ~
wget http://kitlaan.twinaxis.com/projects/bluez-ps3remote/ps3pair.tar.gz
tar xvfz ps3pair.tar.gz
cd ~/ps3pair
sudo python ps3_pair.py
</pre>
Now press START+Enter on your PS3 remote for at least 7 seconds, then it should detect the remote. Then run
<pre>/usr/share/doc/bluez/examples/list-devices</pre>
to verify that the remote is paired (and connected). If list-devices is not installed into /usr/share, check the bluez source tree, it should be in there. Also, running
<pre>cat /proc/bus/input/devices | grep emot</pre>
should show the remote. If it does not show up, you may not have the uinput module loaded.

Then customize the file "/etc/bluetooth/input.conf" for button mappings and timeout values (Example [http://pastebin.com/m5e951b8b here]). At this point, the remote should connect (and auto-disconnect after a timeout, if configured). The d-pad is probably the best way to test it within xbmc. If you have a terminal active, pressing the number buttons should type the number.

''Note:'' - The pairing scripts are not required by some distro's - just install Blueman and set up your BD remote as an input service and trust the device - this way you dont explicitly need to pair the device - it simply becomes a keyboard extension. The input.conf below will take care of key mapping.

=== Example input.conf ===

A more advanced bluetooth input.conf is probably lurking in the depths of [http://forum.xbmc.org/showthread.php?t=50717 this thread], however here's an example to get you started. The first thing you'll need to change in this is your BD Remote's hardware address (i.e. change 00:1E:3D:B6:12:7E to your remote's address)

<pre>
# input.conf - kitlaan custom
# Configuration file for the input service

# This section contains options which are not specific to any
# particular interface
[General]

# Set idle timeout (in minutes) before the connection will
# be disconnect (defaults to 0 for no timeout)
#IdleTimeout=30

# This section contains options that are specific to a device
[00:1E:3D:B6:12:7E]
#
# Set a custom idle timeout (in minutes) for this device
IdleTimeout=1

# This section is the PS3 Remote keymap. It is loaded when bluez starts.
# Use 'uinput.h' from bluez sources or '/usr/include/linux/input.h' for
# a list of possible KEY_* values.
#
[PS3 Remote Map]
# When the 'OverlayBuiltin' option is TRUE (the default), the keymap uses
# the built-in keymap as a starting point. When FALSE, an empty keymap is
# the starting point.
#OverlayBuiltin = TRUE
0x16 = KEY_E # EJECT
0x64 = KEY_A # AUDIO
0x65 = KEY_Z # ANGLE
0x63 = KEY_T # SUBTITLE
0x0f = KEY_DELETE # CLEAR
0x28 = KEY_GRAVE # TIMER
0x00 = KEY_1 # NUM-1
0x01 = KEY_2 # NUM-2
0x02 = KEY_3 # NUM-3
0x03 = KEY_4 # NUM-4
0x04 = KEY_5 # NUM-5
0x05 = KEY_6 # NUM-6
0x06 = KEY_7 # NUM-7
0x07 = KEY_8 # NUM-8
0x08 = KEY_9 # NUM-9
0x09 = KEY_0 # NUM-0
0x81 = KEY_F7 # RED
0x82 = KEY_F8 # GREEN
0x80 = KEY_F9 # BLUE
0x83 = KEY_F10 # YELLOW
0x70 = KEY_I # DISPLAY
0x1a = KEY_S # TOP MENU
0x40 = KEY_M # POP UP/MENU
0x0e = KEY_ESC # RETURN
0x5c = KEY_C # TRIANGLE/OPTIONS
0x5d = KEY_BACKSPACE # CIRCLE/BACK
0x5f = KEY_TAB # SQUARE/VIEW
0x5e = KEY_SPACE # CROSS
0x54 = KEY_UP # UP
0x56 = KEY_DOWN # DOWN
0x57 = KEY_LEFT # LEFT
0x55 = KEY_RIGHT # RIGHT
0x0b = KEY_ENTER # ENTER
0x5a = KEY_F1 # L1
0x58 = KEY_F2 # L2
0x51 = KEY_F3 # L3
0x5b = KEY_F4 # R1
0x59 = KEY_F5 # R2
0x52 = KEY_F6 # R3
0x43 = KEY_HOMEPAGE # PS button
0x50 = KEY_INSERT # SELECT
0x53 = KEY_HOME # START
0x33 = KEY_R # SCAN BACK
0x32 = KEY_PLAY # PLAY
0x34 = KEY_F # SCAN FORWARD
0x30 = KEY_PAGEUP # PREVIOUS
0x38 = KEY_STOP # STOP
0x31 = KEY_PAGEDOWN # NEXT
0x60 = KEY_COMMA # SLOW/STEP BACK
0x39 = KEY_PAUSE # PAUSE
0x61 = KEY_DOT # SLOW/STEP FORWARD
0xff = KEY_MAX
</pre>

== Troubleshooting ==

=== Pairing ===
After pairing, running <pre>cat /proc/bus/input/devices | grep emot</pre> doesn't list your device, and you've got ''uinput'' loaded <pre>lsmod | grep uinput</pre>
* Install blueman <pre>sudo apt-get install blueman</pre>
* Open System->Preferences->Bluetooth Manager.
* If your device is listed (it should be), right click it and select ''Input service''.
* Go to a terminal and try pushing some buttons on the remote, it should work.

[[Category:Remotes]]
[[Category:Linux]]
[[Category:How-to]]

Archive:Set up PS3 BD Remote

2014-10-18T18:43:51Z

Slvr32: Page title changed, but URL still has Setup vs Set up error

Windows audio

2014-10-18T18:26:12Z

Slvr32: Setup vs set up, spelling/grammar errors

{{mininav|[[Audio]]}}
<section begin="intro" />This page describes how to set up audio for the Windows OS. It covers how to set up XBMC when using either Directsound or WASAPI, and when to use one vs the other.<section end="intro" />

Since WASAPI performs no mixing or resampling this is the preferred mode for best quality audio.

From Frodo onwards XBMC uses WASAPI only in the Exclusive Mode of operation in order that XBMC gets the exclusive rights to the audio buffers whilst playing audio streams to the exclusion of all other sounds or players, this is a change from previous version of XBMC where Shared Mode was also allowed. When using WASAPI care must be taken to ensure Windows is configured to allow XBMC to run in exclusive mode, refer to the below '''Configure Windows Sound Settings''' section.

In addition XBMC from Frodo onwards uses WASAPI the more modern Event driven mode, previously XBMC used the Push mode, so both the audio hardware & audio driver need to support the Event mode for audio to work with WASAPI selected.

{{Note|Due to the above changes in how XBMC implements WASAPI from Frodo onwards, then previously working configurations may not work when upgrading to XBMC Frodo or later}}
<br />

=Hardware Vendor Specifics=
== AMD GPU ==

If using WASAPI do not use the Realtek HD Audio drivers as they do not work with the event driven mode XBMC uses for WASAPI. To use WASAPI you must use the AMD High Definition Audio drivers.

The Realtek HD Audio drivers will however work with the Directsound mode.
== Intel GPU ==

To support HD Audio on Windows the Intel Management Engine Interface driver must be installed, it's this driver that provides the HDCP DRM necessary for the HD Audio formats to works. If this driver is not installed then the HD formats will be missing from the Supported Formats tab.

In order to verify you have the Intel Management Engine Interface driver installed, follow the relevant step at [http://www.intel.com/support/graphics/sb/CS-031600.htm?wapkw=management+engine+driver Blu-Ray* Disc Playback with Intel® HD Graphics FAQ]

= Check drivers =
<gallery widths=500px heights=400px>
File:Computer management.JPG|'''Step 1:''' Select '''Device Manager''' then go to '''Sound, video and game controllers'''. Select the device you'll be using for audio and right click then select '''Properties'''

File:Driver.JPG|'''Step 2:''' Go to '''Driver''' tab and ensure '''Driver Provider''' shows the manufacturer of your device. If '''Microsoft''' is shown here then you have a driver provided by your Windows installation or Windows Update. In the case of '''HDMI''' being used to provide audio, <u>you must ensure the driver is provided by your device manufacturer</u> as the Microsoft provided ones will usually have reduced functionality such as HD Audio formats not supported.
</gallery>

= Configure Windows Sound Settings =

The Windows sound settings will only apply if you select an audio device using the Directsound API within XBMC, if you select an audio device using the WASAPI API then these settings will be ignored however it's a good to configure these correctly no matter what type of API you're using.

<gallery widths=500px heights=400px>
File:Sound - playback.jpg|'''Step 3:''' Set the audio device to be used for {{subst:Name}} audio as the default device,
File:Speaker setup.jpg|'''Step 4:''' Next launch the '''Configure''' wizard to set the speaker layout you have. If operating {{subst:Name}} in WASAPI mode this isn't strictly needed to be correct but it's good practice to ensure it's correctly set.
File:Output Properties - Supported Formats.jpg|'''Step 5:''' <big>'''<u>For HDMI connections only</u>'''</big> Next select '''Properties''' and go to the '''Supported Formats''' tab. In this tab you'll see the formats that the audio driver is reporting to Windows that you selected hardware is capable of, if audio codecs are missing from '''Encoded Formats''' list then {{subst:Name}} won't be able to play these formats back. If formats are missing that you know your hardware is capable of then this points to there being either a driver problem or if using HDMI then it maybe a EDID handshaking problem. <br><br>'''IMPORTANT -''' For HD audio to work then '''Max Number of Channels''' must be reported as '''8''' if anything other than 8 is reported then HD audio will not work even if DTS-HD and TrueHD are listed in the Encoded Formats box.
File:Output Properties - Advanced.jpg|'''Step 6:''' Finally go to the '''Advanced Tab''' and ensure the '''Exclusive Mode''' check boxes '''Allow applications to take exclusive control of this device''' and '''Give exclusive mode applications priority''' are ticked. This is a requirement if WASAPI mode is to be used in XBMC. Once this is done you should be good to go in setting up audio on {{subst:Name}} so refer back to [[AudioEngine]]
</gallery>

= Windows Audio API's - Background =
Since Windows Vista SP1 there has two primary audio interfaces, DirectSound and WASAPI (Windows Audio Session Application Programming Interface) with WASAPI being a replacement for Windows XP's Kernel Streaming mode.

== Directsound ==
DirectSound acts as a program-friendly middle layer between the program and the audio driver, which in turn speaks to the audio hardware. With DirectSound, Windows controls the sample rate, channel layout and other details of the audio stream via an Audio Mixer. Every program using sound passes it's data to DirectSound and the Audio Mixer which then resamples as required so it can mix audio streams from any program together with system sounds.

The advantages are that programs don't need resampling code or other complexities, and any program can play sounds at the same time as others, or the same time as system sounds, because they are all mixed to one format.

The disadvantages are that other programs can play at the same time, and that a program's output gets mixed to whatever the system's settings are. This means the program cannot control the sampling rate, channel count, format, etc. Even more important for this thread is that you cannot pass through encoded formats, as DirectSound will not decode them and it would otherwise bit-mangle them, and there is a loss of sonic quality involved in the mixing and resampling.

== WASAPI ==
Partly to allow for cleaner, uncompromised or encoded audio, and for low-latency requirements like mixing and recording, Microsoft re-vamped their Kernel Streaming mode after XP and came up with WASAPI for Vista.

WASAPI itself has two modes, Shared and Exclusive.

Shared mode is in many ways similar to DirectSound as it allows other sounds to be mixed into the currently playing stream, however this mode is not supported on XBMC so won't be covered any further here.

WASAPI Exclusive mode bypasses the Audio Mixer and thus the mixing/resampling layers of DirectSound so audio is passed-through as-is, this is why WASAPI should be used for encoded formats like DTS in order that they can reach the receiver unchanged for decoding there.

WASAPI Exclusive mode allows the application to interrogate the capabilities of the audio driver, since audio is presented directly by the application to the audio driver the format that the audio is sent in by the application must be in a format that is compatible with the capabilities of the audio driver, as there is no DirectSound between to convert it. This interrogation is a two way process that often involves some back-and-forth depending on the format specified and the device's capabilities, once a set of compatible formats is agreed upon by application and audio driver, the application then decides how it will present the audio stream to the audio driver.

In addition to Shared and Exclusive modes, there are two modes for how data is passed from the application to the audio driver.

The normal manner is in push mode - a buffer is created which the audio device draws from, and the application pushes as much data in as it can to keep that buffer full. To do this it must constantly monitor the levels in the buffer, with short "sleeps" in between to allow other threads to run.

WASAPI, and most modern sound devices, also support a "pull" or "event-driven" mode. In this mode two buffers are used. The application gives the audio driver a call-back address or function, fills one buffer and starts playback, then goes off to do other processing. It can forget about the data stream for a while. Whenever one of the two buffers is empty, the audio driver "calls you back", and gives you the address of the empty buffer. You fill this and go your way again. Between the two buffers there is a ping-pong action: one is in use and draining, the other is full and ready. As soon as the first is emptied the buffers are switched, and you are called upon to fill the empty one. So audio data is being "pulled" from the application by the audio driver, as opposed to "pushed" by the application.

[[Category:How-to]]
[[Category:Audio]]
[[Category:Windows]]
[[Category:Settings]]

Settings/System

2014-10-18T18:21:05Z

Slvr32: Setup vs set up, grammar/spelling errors

{{mininav|[[Settings]]}}
<section begin="intro" />System settings are found here. Set up and calibrate displays/video output, configure audio output, set up remote controls, set power saving options, enable debugging, set up master lock.<section end="intro" />
__TOC__
{{-}}
== Video output ==
{{see also|Settings/Videos|Video playback#OSD video settings}}
[[File:Settings.system.video output.png|800px|center]]
{| class="prettytable"
! width="20%" | Setting
! Description
! Setting level
|-
| Display Mode
| Display XBMC in a window, or fullscreen on the selected screen.
|
|-
|
:-Display/Resolution 
| Changes the resolution that the User Interface is displayed in.
|
|-
|
:-Use a fullscreen window rather than true fullscreen
| ...when active (Windows only). Does not use the DirectX fullscreen mode. The main benefit is for multi-screen configurations, where XBMC can be used at the same time as other applications without automatically minimizing. Uses a bit more resources and playback may be slightly less smooth.
|
|-
|
:-Blank other displays
| In a multi-screen configuration, the screens where XBMC is not displayed are blacked out.
|
|-
| Stereoscopic mode (current)
| {{main|3D}}
|
|-
|
:-Preferred mode
|
|
|-
| Vertical blank sync
| Compensation for [[w:vertical tearing|vertical tearing]].
|
|-
| Video calibration...
| See [[#Video calibration...]]
|
|-
| Test patterns...
|
|
|-
| Use limited color range (16-235)
| Use limited color range instead of full color range (0-255). Limited range should be used if your display is a regular HDMI TV, while full color range should be used if your display is a PC monitor.
|
|}

==== Video calibration... ====
{{Note|Always adjust your TV display settings before XBMC's settings (such as overscan, etc). In most cases, you can get a "just scan/just fit/PC mode/something" mode turned on that will not require any adjustments in XBMC, and will allow for the best screen quality.}}
This screen allows you to calibrate the User Interface by adjusting the overscan. Use this tool if the image being displayed is too large or small for your display.<br />
Simply adjust the screen so that the arrows are in the top left and bottom right corners and that the entire frame is visible on screen.

It offers the ability to adjust:
* The overscan of the video - How close to the edges of the screen that the image is displayed.
* The position where subtitles are displayed.
* The pixel ratio allows you calibrate the aspect ratio at which videos are played back.
<gallery widths=250px heights=141px>
File:uicalibration1.png|Upper left corner
File:uicalibration2.png|Lower right corner
File:uicalibration3.png|Subtitles position
File:uicalibration4.png|Aspect ratio
</gallery>
{{-}}

== Audio output ==
{{Main|Audio}}
{{see also|Settings/Music|Video playback#OSD audio and subtitle settings}}
<section begin="Audio output settings" />
[[File:Settings - Audio Output.png|800px|center]]
{{-}}
{| class="prettytable" style="color: black;"
|-
!style="width:15%" colspan="2"| Setting
!style="width:70%" | Description
!style="width:8%" | Setting level
!style="width:7%" | Device type
|-
|colspan="2"|'''Audio output device'''
|Select the device to be used for audio output.
|Standard
|All
|-
|colspan="2"|'''Number of channels'''
|Select the number of channels supported by the audio connection.

;For digital connections
:This is the number of PCM channels that the audio connection supports and '''not''' the number of speakers connected. For example, using Dolby Digital over SPDIF will provide 5.1 audio to your system, even though SPDIF only supports 2.0 PCM channels. This setting does not apply to passthrough audio connections, if enabled.

;For analog connections
:This is the number of speakers outputs used, which is likely the number of speakers your system is using. Note that some "2.1" systems only use two audio channels and do not have a dedicated subwoofer output.

{{note|This setting might not be exposed depending on what is set for '''Audio output device'''.}}
|Basic
|HDMI/Analog-Speakers
|-
|rowspan="3"|'''Output configuration'''
|'''Fixed'''
|rowspan="3"|Select how the properties of the audio output are set:<br>
'''[Fixed] -''' output properties are set to the specified sampling rate & speaker configuration at all times<br>
'''[Optimized] -''' output properties are set at the start of playback and will not change if the properties of the source changes<br>
'''[Best Match] -''' output properties are set to always be as close a match to the source properties as possible
|rowspan="3"|Advanced
|rowspan="3"|All
|-
|'''Optimized'''
|-
|'''Best Match'''
|-
|-
|colspan="2"|'''Limit sampling rate (kHz)'''
|Maximum sampling rate for spdif or sampling rate for fixed output configuration
|Advanced
|SPDIF
|-
|colspan="2"|'''Stereo upmix'''
|Select to enable upmixing of 2 channel audio to the number of audio channels specified by the channel configuration
|Advanced
|All
|-
|colspan="2"|'''Normalize levels on downmix'''
|Select how audio is downmixed, for example from 5.1 to 2.0:<br>
'''[Enabled]''' maintains the dynamic range of the original audio source when downmixed however volume will be lower<br>
'''[Disabled]''' maintains volume level of the original audio source however the dynamic range is compressed. Note - Dynamic range is the difference between the quietest and loudest sounds in a audio source
|Advanced
|All
|-
|rowspan="3"|'''Resample quality'''
|'''Low'''
|rowspan="3"|Select the quality of resampling for cases where the audio output needs to be at a different sampling rate from that used by the source<br>
'''[Low]''' is fast and will have minimal impact on system resources such as the use of the CPU<br>
'''[Medium] & [High]''' will use progressively more system resources
|rowspan="3"|Advanced
|rowspan="3"|All
|-
|'''Medium'''
|-
|'''High'''
|-
|colspan="2"|'''Keep audio device alive'''
|Select the behaviour when no sound is required for either playback or GUI sounds:<br>
'''[Always] -''' continuous inaudible signal is output, this keeps the receiving audio device alive for any new sounds, however this might also block sound from other applications<br>
'''[1- 10 Minutes] -''' same as Always except that after the selected period of time audio enters a suspended state<br>
'''[Off] -''' audio output enters a suspended state. Note - sounds can be missed if audio enters suspended state
|Standard
|All
|-
|colspan="2"|'''Play GUI sounds'''
|Configure how interface sounds are handled, such as menu navigation and important notifications
|Basic
|All
|-
|colspan="2"|'''Enable passthrough'''
|Select to enable the passthrough audio options for playback of encoded audio such as Dolby Digital
|Advanced
|HDMI/SPDIF
|-
|colspan="2"|'''Passthrough output device'''
|Select the device to be used for playback of encoded formats, these are any of the formats below in the 'capable receiver' options
|Advanced
|HDMI/SPDIF
|-
|colspan="2"|'''Dolby Digital (AC3) capable receiver'''
|Select this option if your receiver is capable of decoding AC3 streams
|Advanced
|HDMI/SPDIF
|-
|colspan="2"|'''- Enable Dolby Digital transcoding'''
|Select this if the audio out connection only supports multichannel audio as Dolby Digital 5.1, such as an SPDIF connection. If your system supports LPCM multichannel sound via HDMI then leave this disabled. This option is only available where the number of channels is 2.0, for SPDIF this is set automatically so this option is always available, if using HDMI then you may need to change the Number of Channels setting to 2.0.
|Advanced
|HDMI/SPDIF
|-
|colspan="2"|'''Dolby Digital Plus (E-AC3) capable receiver'''
|Select this option if your receiver is capable of decoding E-AC3 streams
|Advanced
|HDMI
|-
|colspan="2"|'''DTS capable receiver'''
|Select this option if your receiver is capable of decoding DTS streams
|Advanced
|HDMI/SPDIF
|-
|colspan="2"|'''TrueHD capable receiver'''
|Select this option if your receiver is capable of decoding TrueHD streams
|Advanced
|HDMI
|-
|colspan="2"|'''DTS-HD capable receiver'''
|Select this option if your receiver is capable of decoding DTS-HD streams
|Advanced
|HDMI
|}

{{redv|'''IMPORTANT NOTE:'''|
The "'''capable receiver'''" options relate only to the '''passthrough''' of audio to another device such as an AVR, where that device must support decoding of the format. Before leaving any "'''capable receiver'''" option enabled check to make sure that both the playback device running XBMC (e.g. HTPC) and the connected device (e.g. AVR) both support that format.

If you have a "'''capable receiver'''" option enabled that your device does not support then this will result in poor playback of video typically with a very low frames-per-second and no audio, so for example if the '''TrueHD capable receiver''' option were enabled then make sure that the playback device can passthrough TrueHD and that the connected device can decode TrueHD, if either of the devices do not support TrueHD then the '''TrueHD capable receiver''' option '''MUST''' be left disabled.

For any format where the "capable receiver" option is not selected, XBMC will still playback any content containing those audio types, however instead of the audio being passed through, XBMC will decode audio and then send the audio in a compatible format.

If connected directly to a TV be aware that TV are not compatible with DTS, TrueHD or DTS-HD, typically the only encoded format a TV will be compatible with is AC3.}}
<section end="Audio output settings" />

== Input devices ==
{{note|The content of this screen largely depends on the input devices that XBMC detects and the OS being used.}}
[[File:Settings.system.input devices.png|800px|center]]
{| class="prettytable"
! width="20%" | Setting
! Description
! Setting level
|-
| Peripherals
| See '''[[#Peripherals]]'''.
|
|-
| Apple remote ''(OS X only)''
|
|
|-
| Allow start of XBMC using the remote ''(OS X only)''
|
|
|-
| Sequence delay time
|
|
|-
| Remote control sends keyboard presses
| When activated, your keyboard arrows will move the selection on the virtual keyboard. When deactivated, they will move the cursor from your text.
|
|-
| Enable mouse and touch screen support
| {{see also|Touch screen}}
If deactivated, XBMC will ignore all mouse movements and clicks.
|
|-
| Enable joystick and gamepad support
|
|
|-
| Enable system keys in fullscreen ''(Linux only)''
|
|
|}

=== Peripherals ===

== Internet access ==
[[File:Settings.network.internet access.png|center|800px]]
{| class="prettytable"
! width="20%" | Setting
! Description
! Setting level
|-
| Use an HTTP proxy server to access the internet
| If your internet connection uses a proxy, configure it here.
|
|-
|
:-Proxy type
|
|
|-
|
:-Server
| Proxy server address.
|
|-
|
:-Port
| Defines the port of the proxy server
|
|-
|
:-Username
| Defines the username used for the proxy server
|
|-
|
:-Password
| Defines the password used for the proxy server
|
|-
| Internet connection bandwidth limitation
| If you have limited bandwidth available, select a suitable value here and XBMC will try to keep to these limits. {{?}}
|
|}

== Power saving ==
{{see also|Settings/Appearance#Screensaver}}
{{note|Some options might not be available on all hardware or OSes. For example, XBMC cannot control shutdown or sleep on [[Android]].}}
[[File:Settings.system.power saving.png|800px|center]]
{| class="prettytable"
! width="20%" | Setting
! Description
! Setting level
|-
| Put display to sleep when idle
| Turns off display when idle. Useful for TVs that turn off when there is no display signal detected, but you don't want to suspend/shutdown the whole computer. Selectable from 5 minutes to 120 minutes.
|
|-
| Shutdown function timer
| Sleeps the computer when idle. Selectable from 5 minutes to 120 minutes.
|
|-
| Shutdown function
| Defines what "Shutdown" will do by default. Can be set to actually shutdown, suspend, minimize, or quit.
|
|-
| Try to wake remote servers on access
| {{Main|Wake on lan}}
|
|}

{{note|XBMC also has a "Custom shutdown timer" selectable from the power icon on the home screen, or from the shutdown menu (press {{keypress|S}} on a keyboard or {{button|Power}} on a remote).}}

== Debugging ==
{{main|Log file}}
[[File:Settings.system.debugging.png|800px|center]]
{| class="prettytable"
! width="20%" | Setting
! Description
! Setting level
|-
| Enable debug logging
| Toggles [[debug log]] on / off. Useful for troubleshooting.
|
|-
|
:-Verbose logging
| {{main|Log file/Advanced}}
See '''[[#Verbose logging]]'''
|
|-
| Screenshot folder
| Folder used to save screenshots taken within XBMC. (see [[Keyboard controls]] for the screenshot key for your OS)
|
|}

=== Verbose logging ===
{{main|Log file/Advanced}}
[[File:Verbose logging options.png|right|400px]]

{{-}}

== Master lock ==
{{see also|Profiles}}
{{note|''The Master lock options are ONLY available while using the default user [[profile]].''}}
[[File:Settings.system.master lock.png|800px|center]]
{| class="prettytable"
! width="20%" | Setting
! Description
! Setting level
|-
| Master lock code and settings
| Opens the [[#Master lock settings|Master lock settings window]], where you can configure your Master Lock options. See '''[[#Master lock settings]]'''.
|
|-
|
:-Ask for master lock code on startup
| If enabled, the master lock code is required to unlock XBMC on startup
|
|}

=== Master lock settings ===
[[File:Lock settings.png|center|600px]]
{| class="prettytable"
! width="20%" | Setting
! Description
|-
| Master Lock
| Allows you to set the master lock password. Can be one of three types:
* '''Numeric password''' - Enter a Numeric Password using the On Screen Keyboard
* '''Gamepad button combo''' - Enter a series of buttons using the Gamepad
* '''Full-text password''' - Enter a plain-text password using the On Screen Keyboard
|-
| Lock music window
|
|-
| Lock video window
|
|-
| Lock pictures window
|
|-
| Lock programs and scripts windows
|
|-
| Lock file manager
|
|-
| Lock settings
|
|-
| Lock Add-on manager
|
|}

=== Locking media sources ===
{{main|Media sources#Locking}}
{{#lst:Media sources|Locking}}

===Locked out?===
XBMC will give you three tries when you need to enter a lock/password to access something that is locked. If you max out these three tries then just quit XBMC and re-open it to get three more tries. The Master Lock code is stored in the "'''profiles.xml'''" file in the [[userdata]] folder. Should you get locked out, you can delete or edit the "'''profiles.xml'''" file.

=== additional settings ===
{{editor note|This was in [[advancedsettings.xml]], but it appears to be documenting something in guisettings.xml that don't actually have a GUI setting.}}
Code needs to be MD5'd, and you can use [http://pajhome.org.uk/crypt/md5/ this site] to hash it.

<syntaxhighlight lang="xml" enclose="div">
<masterlock>
<startuplock>false</startuplock> 
<automastermode>false</automastermode> 
<loginlock>true</loginlock> 

<maxretries>3<maxretries> 
</masterlock>
</syntaxhighlight>

{{Gotham updated}}

[[Category:XBMC Manual]]
[[Category:Settings]]

MythTV PVR

2014-10-18T18:19:12Z

Slvr32: Setup vs set up grammar/spelling errors

{{:PVR/Contents}}
{{mininav|[[PVR]]|[[Recording software]]}}
MythTV is a Free Open Source software digital video recorder (DVR) project that is designed to run on Linux, although other operating system packages are available. With MythTV you can watch live TV, schedule recordings, view episode guide information, and many other features you'd expect from a DVR type device. MythTV can also be set up with multiple backends (master/slave) and multiple frontends to spread out the workload of recording, scheduling, and post processing jobs. More information on MythTV can be found on their [http://www.mythtv.org/ official] website.

The released addon supports MythTV Backend version 0.24 - 0.27.

__TOC__
{{-}}

== Installing MythTV ==
MythTV can be set up on a variety of Linux distributions and also on Mac OS X. The [http://www.mythtv.org/wiki/Packages MythTV Wiki] page has several pages of detailed instruction sets for various distros and tuner types.

== MythTV quick start guide ==
{{incomplete}}
If your tuner hardware is not detected or is having issues, check http://linuxtv.org for driver support.

== Connecting XBMC to MythTV ==
{{PVR repo notice}}
# Go to {{highlight|Settings -> Add-ons -> Enabled add-ons -> PVR Clients}} and select the MythTV add-on
# Select "Configure"

== Settings ==
=== General ===
<section begin="Settings" />
[[File:Xbmc-settings-mythtv-general.png|500px|right]]
{|
|
; MythTV Backend Hostname or IP
: The hostname or IP address of the server where MythTV / MythBackend is installed. If backend and frontend run on the same machine then 'localhost' can be used.
; MythTV Backend Port
: The default is 6543 but this will need updating if you have changed it in the MythTV settings.
; MythTV Database Username
: The default is 'mythtv' but this will need updating if you have changed it for the MythTV database.
; MythTV Database Password
: The default is 'mythtv' but this will need updating if you have changed it for the MythTV database.
; MythTV Database Databasename
: The default is 'mythconverg' but this will need updating if you have changed it in the MythTV settings.
; MythTV Backend Ethernet address (WOL) [GOTHAM]
: Add the MAC address of your backend to allow the addon to wake up the backend using WOL.
; Include more debug information in the log file
: If turned on, additional debugging information is written to the log file. This should be turned on if you want to debug or report problems. It should be off for normal usage.
; Enable Live TV
: This enables Live TV. Switch it off if you do want to use MythTV only for watching recordings.
; Allow Live TV to move scheduled shows
: This allows MythBackend to move scheduled recordings to another tuner if the scheduled tuner is blocked by an active Live TV playback. If turned off, you might miss recordings!
; Conflict handling
: This allows to configure the Live TV vs. scheduled recoding conflict handling. The setting determines how the addon should handle upcoming recordings for a tuner, that is being used for Live TV at the moment.
: '''- Prefer Live TV when recording has later slot:''' (default) Continue watching Live TV in case there is a known later slot for the recording. Reschedule to record this repeat instead. If there's no later slot, stop Live TV and start the recording now.
: '''- Prefer recording and stop Live TV:''' Stop Live TV and start the scheduled recording.
: '''- Prefer Live TV and cancel conflicting recording:''' Ignore the conflicting, upcoming recording and continue to watch Live TV instead.
|}
{{-}}
In addition the addon supports advanced settings, that can be edited in the addon's settings file: <code>[[userdata]]/addon_data/pvr.mythtv.cmyth/settings.xml</code>
{|
|
; MythTV Database Hostname or IP
: The default is your MythTV Backend Hostname but this will need updating if your database server runs on a different host.
:<code><setting id="db_host" value="192.168.0.1" /></code>
; MythTV Database Port
: The default is 3306 but this will need updating if you have changed it.
:<code><setting id="db_port" value="3306" /></code>
|}
<section end="Settings" />

=== Recording template ===
Configuration of the default rules for new recordings. Recording rule templates have been introduced in MythTV 0.26.
For older MythTV versions, please use and configure the addon-'''Internal''' template provider.
<section begin="Settings" />
[[File:Xbmc-settings-mythtv-template.png|500px|right]]
{|
|
; Template provider
: '''- MythTV:''' Use MythTV's default recording rule template
: '''- Internal:''' Use XBMC's respectively the addon's settings
; Automatically Look Up Metadata
: Advises the MythTV backend to download metadata for this recording.
; Commercial Flag new recordings
: Advises the MythTV backend to run the commercial flag job for this recording.
; Allow recordings to expire?
: Allows the MythTV backend to automatically delete the recording when necessary.
; Transcode new recordings and Transcoder
: Advises the MythTV backend to automatically transcode the recording into a different format.
; Run user Job #1-4
: Advises the MythTV backend to automatically run the user defined jobs for this recording.
;Note
: '''Start''' and '''End Offset''' is configured in [[PVR/XBMC#Recording|XBMC Live TV settings]]
|}

=== Advanced ===
{|
|
; Enable demuxing of MPEG-TS
: Enables the addon internal demuxing of the stream. Advantages are faster channel switching and better timeshift functionality.
: '''Note:''' This might not work with all video formats. Disable this settings in case you experience playback problems.
|}

<section end="Settings" />

{{Next|[[PVR/XBMC|Configuring XBMC]]}}

== Troubleshooting ==
# If you're experiencing troubles with the addon, [http://forum.xbmc.org/forumdisplay.php?fid=170 MythTV section of XBMC Forum] is the correct place to ask for help.
# Always include a '''full [http://wiki.xbmc.org/index.php?title=Debug_log debug log]''' with the addon setting '''Include more debug information in the log file''' enabled. (also please make yourself familiar with [http://wiki.xbmc.org/index.php?title=Troubleshooting XBMC troubleshooting])
# Issues that are only related to this addon (not to XBMC itself or XBMC's general PVR code) should be reported here: https://github.com/fetzerch/xbmc-pvr-addons/issues (if unsure, ask in the forum first!)

== Development ==
* See [[PVR/Backend/MythTV/BuildFromSource|Build addon from source]] to learn how to build addon from the official or from the development repository
* This addon uses the Transifex Localization platform. You're welcome to contribute translations: https://www.transifex.com/projects/p/XBMC-Main-Frodo/resource/pvr-mythtv-cmyth/

== Additional guides and links ==
* MythTV website - http://mythtv.org
** [http://www.mythtv.org/wiki/ Documentation]
* MythTV backend for XBMC support forum - http://forum.xbmc.org/forumdisplay.php?fid=170
* Addon's issue tracker: https://github.com/fetzerch/xbmc-pvr-addons/issues
* MythTV genre colours in XBMC EPG: [[PVR/Backend/MythTV/DVB-EIT-categories]]

HOW-TO:Install Kodi for Linux

2014-10-13T17:43:37Z

Slvr32: Spelling/grammar error, setup vs set up

{{mininav| [[Installing]] {{l2| [[Linux]] }} }}
{{see also|Linux FAQ}}

These are instructions for people who already have a Linux-based OS setup. If you have not installed a Linux-based OS yet, you might wish to try out [[XBMCbuntu]] which will install both the OS and XBMC with an easy installer.

=Official Team Kodi/XBMC repositories=

==Ubuntu==
;Simple Install Instructions

{{note|1=[http://help.ubuntu.com/community/UsingTheTerminal Click here to find out how to use the terminal.]}}

Use the command line terminal and enter the following commands. Follow the prompts as you would any other software installation.

<syntaxhighlight lang="bash">
sudo apt-get install python-software-properties pkg-config
sudo apt-get install software-properties-common
sudo add-apt-repository ppa:team-xbmc/ppa
sudo apt-get update
sudo apt-get install xbmc
</syntaxhighlight>

{{#lst:Team XBMC PPA|repos}}

=== Upgrading ===
<section begin="Ubuntu upgrade" />
To update XBMC/Kodi when a new version is released, just do a general system/package or use the following commands in the terminal (or via [[SSH]]):

<syntaxhighlight lang="bash">
sudo apt-get update
sudo apt-get install xbmc
</syntaxhighlight>
<section end="Ubuntu upgrade" />

===XBMCbuntu===
{{main|XBMCbuntu}}
{{#lst:XBMCbuntu|intro}}

===Installing a development build===
{{see also|Development builds}}
To install a beta/unstable version of XBMC you must first add the unstable repository, then install XBMC:

Use <code>ppa:team-xbmc/xbmc-nightly</code> for nightly builds and <code>ppa:team-xbmc/unstable</code> for [[beta]] builds.

<syntaxhighlight lang="bash">
sudo add-apt-repository ppa:team-xbmc/xbmc-nightly
sudo apt-get update
sudo apt-get install xbmc
</syntaxhighlight>

Follow the prompts to add the repository, then to add the updates, and finally install the new version of XBMC.

=== Going back to a stable version from a development version ===
To return to a stable release:

Find the current PPA you are using:
<syntaxhighlight lang="bash">
sudo apt-cache policy
</syntaxhighlight>

Remove the unstable or nightly PPA where it says '''PPAHERE''':
<syntaxhighlight lang="bash">
sudo add-apt-repository -r ppa:PPAHERE
</syntaxhighlight>

Then restore the stable version with the following commands:
<syntaxhighlight lang="bash">
sudo add-apt-repository ppa:team-xbmc/ppa
sudo apt-get update
sudo apt-get remove xbmc
sudo apt-get install xbmc
</syntaxhighlight>

=== Uninstalling ===
If you need to remove and purge an application and finally removing/purging also the application configurations files, do so by using the following commands:

<syntaxhighlight lang="bash" enclose="div">
sudo apt-get update
sudo apt-get remove xbmc*
sudo apt-get purge xbmc*
</syntaxhighlight>

Then remove the settings folder to remove all settings and library data. This will not delete any videos or music, but just the settings and library data itself:
<syntaxhighlight lang="bash" enclose="div">
rm ~/.xbmc/
</syntaxhighlight>

= Other repositories =


Unofficial Linux binaries that are un/semi supported by Team XBMC. These use internal ffmpeg libraries rather than system ffmpeg or libav, which is recommended for XBMC.

== Debian ==
http://people.debian.org/~rbalint/ppa/xbmc-ffmpeg/

== OpenELEC ==
{{main|OpenELEC}}
{{#lst:OpenELEC|intro}}

= Installation from source =

If distribution packages are not available, or you need a newer version, or specific features enabled, then you will most likely need to compile from source. While compiling from source does not differ very much between distributions (except for installation of build dependencies), a few different guides are available in this wiki.

*[[HOW-TO compile XBMC for Linux from source code]]
*[[HOW-TO compile XBMC for Linux on Debian/Ubuntu]] - This is a tutorial on how to compile and install XBMC on Debian and Ubuntu.

= See also =
*[[Linux]]
*[[HOW-TO:Autostart XBMC for Linux]]

{{gotham updated}}

[[Category:Linux]]
[[Category:How-to]]
[[Category:Installation|Linux]]
[[Category:XBMC Manual]]

MySQL/Setting up Kodi

2014-10-13T17:42:09Z

Slvr32: Spelling/grammar errors, setup vs set up.

{{:MySQL/Contents}}
{{mininav| [[MySQL]] }}
Each device that will be sharing a library will need an [[Advancedsettings.xml|advancedsetting.xml]] file.

__TOC__
{{-}}
==Make files accessible over the network==
If you haven't already done so, you will need to make your media files accessible to all your XBMC devices by sharing them on the network through file sharing. XBMC itself or the MySQL server will not share the actual files for this setup. Most operating systems have built-in methods for sharing files to the network, or a [[NAS]] device can be used.

{{note|
*If you use passwords on your network shares then you will need to copy (or [[MySQL/Sync other parts of XBMC|sync]]) your passwords.xml file from the userdata folder to each XBMC device.
*Do not use mapped drives on the OS-level, as XBMC will see those as local drives.
*If you use smb:// paths, you may want to use static IP addresses rather than NetBIOS names, as not all your devices may be able to resolve the latter.
*'''Even if the media is on the same computer as one of the XBMC instances, you MUST use a network share path. You cannot use a local file path with MySQL.'''}}

See [[:Category:File Sharing]] for some of the file sharing methods that work with XBMC.

==Exporting==
{{see also|HOW-TO:Backup the video library|Import-export library}}

{{note|You only need to do the exporting steps if you are migrating an existing local library to a MySQL database. The MySQL setup creates an entirely new library on the MySQL server, so this step allows you to preserve your old library and restore it once MySQL is used in XBMC.}}

{{redv|'''Warning:''' |This will create individual ".nfo" and image files along side your video files. This is considered the safest way to backup and/or migrate a library (MySQL or otherwise), but some users might not want the file clutter. For an alternative method see '''[[why multiple files|here]]'''.}}

#Open XBMC on the computer that has the library you want to share
##Export the Video Library by doing the following:
###Go to '''System/Settings -> Video -> Library''' and select '''Export library'''
###Select '''Multiple files'''
##Export the Music Library by doing the following:
###Go to '''System/Settings -> Music -> Library''' and select '''Export library'''
###Select '''Multiple files'''

==MySQL and advancedsettings.xml==
{| class=infobox
| advancedsettings.xml:
|-
|
<syntaxhighlight lang="XML">
<advancedsettings>
<videodatabase>
<type>mysql</type>
<host>***.***.***.***</host>
<port>3306</port>
<user>xbmc</user>
<pass>xbmc</pass>
</videodatabase>
<musicdatabase>
<type>mysql</type>
<host>***.***.***.***</host>
<port>3306</port>
<user>xbmc</user>
<pass>xbmc</pass>
</musicdatabase>
<videolibrary>
<importwatchedstate>true</importwatchedstate>
<importresumepoint>true</importresumepoint>
</videolibrary>
</advancedsettings>
</syntaxhighlight>
<small>''See also this note about using the <name> tag: [[#Name tag]]<br/><importwatchedstate> is only needed when you're importing a previous library from exported files.</small>
|}
#Create (or add to, if you already have one) an [[Advancedsettings.xml#.3Cmusicdatabase.3E.2F.3Cvideodatabase.3E|advancedsettings.xml]] file:
##Open up a plain text editor
##Copy and paste the text from the right-hand box into a new text document
##Replace the two instances of <code>***.***.***.***</code> with local network IP address of your MySQL server. If you installed MySQL on a Windows machine, do not use its NetBIOS name, as not all devices may be able to resolve them.
##Save the file as '''advancedsettings.xml'''
#Copy this ''advancedsettings.xml'' file you just created to the '''[[userdata folder]]''' of every XBMC install you want to sync with.
{{-}}

==Importing==
At this point XBMC is using the MySQL server for the database, which means it has a new blank library. Now we can either import an old library (see below) or simply start a new library (see [[adding videos to the library]]. From this point on, XBMC behaves exactly like it would as if it had a local database, except that database is on the MySQL server and multiple XBMC installs can access that single database.

# Open any of your XBMC installs and re-import your library data, ''or'' simply set up a new library if you are starting fresh.
# Add (or just "set content" on) the networked video source to XBMC and scan it in as if you were setting up your library for the first time (see [[adding videos to the library]]). However, XBMC will read the exported nfo files and images and use those instead of rebuilding the library from scratch. The end result will be an identical library, and your watched status for videos will be preserved.
#:{{Note|You must add a network source using XBMC's standard formatting. For example, use "smb://192.168.1.20/Videos/" and not "\\BOBPC\Videos\". Try to use static IP addresses over NetBIOS names if using SMB.}}
# Import the Music Library by doing the following: Same idea as videos, but using the steps for [[adding music to the library]]. You'll end up with an identical library.
You can now add files and update the library from any of your XBMC devices and the library for all of them will stay in sync.

== Adding new XBMC devices to the MySQL setup ==
Since the database has now been set up on the MySQL server, all you need to do for any additional XBMC devices is add the advancedsettings.xml file. You don't need to do any of the other steps, such as rescanning or reimporting. If it works on one XBMC device then it should work on all of them, as they are basically sharing the same "brain".

==Name tag==
<section begin="name tag" />
An additional <code><name></code> tag can be used for both the <code><videodatabase></code> and <code><musicdatabase></code> entries in advancedsettings.xml file, if you want to change the name of the database. The <code><name></code> tag is not required. XBMC will use "MyVideos" and "MyMusic" as database names if the <code><name></code> tag is not specified.

You may want to do this if you want to have multiple separate libraries (with different content) on the same MySQL server. For example, if you want to create multiple profiles, each with their own shared library, so that each XBMC device can "log-into" that library. (a kids library, a guest library, etc)

{{note|Don't try to merge the video and music databases! You need to use different values in the <code><name></code> tag or you'll end up confusing XBMC leading to the library functionality not working at all. In other words, don't use <code><name>XBMC</name></code> for both music and videos, but instead use something like <code><name>XBMC-music</name></code> and <code><name>XBMC-video</name></code>.}}

{{Gotham updated}}

Archive:MythTV

2014-10-13T17:40:31Z

Slvr32: Spelling/grammar errors, setup vs set up

{{outdated|raw=This is old. It might still work, but you can just use [[PVR]] or [[Add-on:MythBox]], which are much easier options.}}

== What is MythTV? ==

[http://www.mythtv.org/detail/mythtv MythTV] is a [http://en.wikipedia.org/wiki/Digital_video_recorder digital video recorder] for watching and recording television. MythTV also contains plugins for viewing other home media, similar to what XBMC Media Center provides. MythTV is like a free open source alternative to Tivo and Windows Media Center.

Some of MythTV's features include:
* Watch and record analog and/or digital TV, including HDTV.
* Pause, skip, and rewind live TV shows.
* Completely automatic commercial detection/skipping, with manual correction via an intuitive cutlist editor.
* Intelligently schedules recordings to avoid conflicts.
* Parental controls to keep your kids out of the good shows.
* Schedule and administer many functions remotely via a web browser.
* Flexible client/server architecture allows multiple frontend client machines to access content served by one or more backend servers (although the most common installation consists of a single computer running both the client and server together).

This wiki page doesn't contain any information about how to install, set up or configure MythTV. If you need further information about how best to do this, [http://www.mythbuntu.org/ Mythbuntu] is a good place to start. Mythbuntu is a community supported add-on for Ubuntu focused upon setting up a standalone MythTV based PVR system.

== Integrated support via MythTV PVR add-on ==
Integrated MythTV support in XBMC is based on the [[PVR]] support that has now been merged in mainline XBMC (as of October 2012). More information can be found on [[PVR]] wiki page. There is a currently a [[PVR/MythTV|MythTV client add-on]] along with support of other PVR backends through [[:Category:PVR add-ons|client add-ons for those backends]].

== Old-style myth:// protocol access ==
{{outdated|This section details the old-style [[Media Sources|media source]] that can communicates with a '''MythTV''' backend. While it should still work, the focus going forward will be accessing the MythTV backend via the '''[[PVR/MythTV|PVR client add-on]]'''. Thus some of the information in this article or section is likely not to be updated, and may become increasing unreliable over time}}

That said, the current support allows you to:
* '''Navigate All Recordings, Movies and TV Shows separately''' - standard XBMC navigation grouped in a sensible way.
* '''Playback recordings with automatic commercial skip''' - automatic commercial skip during playback that works as you expect with no fuss. Advanced options to help merge poorly flagged commercial breaks as well.
* '''Add recorded Movies to the XBMC library''' - integrate your recorded Movies in MythTV with all your other movies so you can see them all in one place. Standard XBMC functionality with [[scrapers]] supported.
* '''Watch and pause Live TV with direct channel navigation''' - change up or down channel with a single button press, or choose a channel number using the remote keypad.
* '''Look at electronic program guide (EPG)''' - to see what is coming up on each channel
* '''Delete recorded programs after watching''' - one place to watch and delete recorded programs

This limited source support is limited to playback of MythTV recordings. You need to schedule recordings via the new [[PVR/MythTV|MythTV add-on]] or using mythfrontend or mythweb.

Versions of MythTV up to and including 0.24 are supported in the 11.0 release of XBMC Media Center (Eden). Version 0.25 of MythTV is currently only supported in trunk (see the "libcmyth" section of [[MythTV PVR Addon|the MythTV PVR Addon article]] for details).

The functionality described on this page is for the 9.11 Camelot release of XBMC.

=== Setup ===

XBMC communicates with mythbackend using the [http://www.mythtv.org/wiki/Myth_Protocol Myth Protocol] and MySQL database queries to the mythconverg database. This requires that the MythTV configuration is checked to ensure XBMC will be able to communicate with MythTV, which depends on whether XBMC is running on the same machine.

If you don't intend on using the '''Guide''' then the MySQL related configuration can be omitted. Access to the ''mythconverg'' MySQL database is only used to view the Guide.

==== Setup in MythTV ====

If XBMC Media Center and the MythTV backend will NOT be running on the same machine:

* Check that the IP Address configured in MythTV can be accessed by the XBMC machine. ''The default IP Address for an installation of MythTV is 127.0.0.1 and must be changed so playback will work''
# Run '''mythtv-setup'''
# Select '''General'''
# Check that the '''IP Address''' in '''Local Backend''' section is NOT set to ''localhost'' or ''127.0.0.1''. The IP Address must be resolvable from the XBMC Media Center machine, e.g. 192.168.1.3.
* Check that the MySQL database being used by MythTV has been configured to allow external connections.
** Generally this means ensuring that the ''bind-address'' is ''not'' set to ''localhost'' or ''127.0.0.1'' in ''/etc/mysql/mysql.cnf'' or one of the ''*.cnf'' files in ''/etc/mysql/conf.d/''.

To ensure XBMC has proper access to the MythTV mysql database, run the following commands on the mysql server. Replace '''PASSWORD''' or '''xbmc''' with whatever you prefer, but keep the single quotes for syntax.

<code>$ mysql -u root -p </code> (enter mysql root password when prompted)

<code>mysql> grant SELECT,INSERT,UPDATE,DELETE,CREATE,DROP on mythconverg.* to 'xbmc' identified by 'PASSWORD';</code>

If you just want to restrict by IP subnet (in this example, the 192.168.1.x network):
<code>
$ mysql -u root -p
mysql> grant all on mythconverg.* to mythtv@"192.168.1.%" identified by "mythtv";
mysql> flush privileges;
</code>

It is very important that the '''IP Address''' is set correctly using '''mythtv-setup'''. The Myth Protocol used by XBMC Media Center uses the IP Address configured in the Myth TV backend to determine where to stream the recordings from. So, even if the IP address in the myth:// URL points correctly to the MythTV backend, there can still be playback problems if the correct IP Address isn't also set correctly using mythtv-setup.

==== Setup in XBMC ====

To communicate with a MythTV backend, add a new ''Source'' from the ''Videos'' section. The source should have a URL that looks like:
'''myth://username:password@i.p.address'''
This URL needs to be specified manually as many skins don't support the ability to configure a MythTV source.

''username'' and ''password'' are the credentials for a user that has access to the MySQL ''mythconverg'' database on the MythTV backend. The username and password supplied in the URL are used to obtain EPG information from the MythTV database when using the '''Guide'''. If the username and password are not supplied a default of ''mythtv'' is used for both. The username and password are not used when watching recordings.

''i.p.address'' is the IP address of the MythTV master server. A hostname can also be used, but it must be resolvable to an IP address on the XBMC Media Center machine.

When you select the newly added MythTV [[Media Sources|media source]] five folders will be listed:
* '''All Recordings''' - to watch anything that has been recorded all in one folder.
* '''Guide''' - to view the EPG for a channel
* '''Live Channels''' - to display what is currently being aired
* '''Movies''' - to list the movies that have been recorded
* '''TV Shows''' - to list each series of TV shows that have been recorded

[[File:MythTV.FolderListing.jpg|800px]]

=== Watching Recorded Programs ===

==== All Recordings ====

After choosing '''All Recordings''' a list of all recorded programs is presented. Standard XBMC functionality can be used to sort by date to see the most recent recordings, or sort by name to get all the shows from a given series grouped together.

[[File:MythTV.AllRecordings.jpg|800px]]

==== Movies ====

After choosing '''Movies''' a list of all the recorded movies is shown.

[[File:MythTV.Movies.jpg|800px]]

If not all of the movies are shown, e.g. some still display in the '''TV Shows''' section, the Electronic Program Guide (EPG) being used by MythTV might not be very accurate. The EPG describes which programs are Movies and which are TV Shows. Use the [[Advancedsettings.xml#.3Cmyth.3E|<myth><movielength> advanced setting]] to help with this problem. 85 minutes seems to work well.

==== TV Shows ====

After choosing '''TV Shows''' a list of all the recorded TV shows grouped by title is shown. This makes it easy to see what TV series or one-off programs have been recorded.

TODO: Update image.
[[File:MythTV.TVShows.jpg|800px]]

After choosing a title, the list of recorded programs with that title is shown.

TODO: Update image.
[[File:MythTV.TVShows.BestOfTopGear.jpg|800px]]

=== Watching Live TV ===

After choosing '''Live Channels''' a listing of the channels used by MythTV is displayed.
[[File:MythTV.LiveTV.jpg|800px]]

When a channel is chosen, the currently playing TV show on that channel is shown.

It is possible to pause Live TV, but it is not possible to skip.
To move up or down a channel when playing Live TV press the PageUp or PageDown button. Note that channel changes can take some time depending on the tuner hardware and configuration being used by MythTV.

=== Viewing the Electronic Program Guide (EPG) ===

After choosing '''Guide''' a listing of channels used by MythTV is shown.

[[File:MythTV.Guide.jpg|800px]]

When a channel is chosen, the listing of upcoming programs on that channel is displayed.

[[File:MythTV.Guide.TV3.jpg|800px]]

There is a future project to be able to schedule programs to record from the EPG similar to the functionality available in the MythTV frontend.

=== Adding Recorded Movies to the Video Library ===

Recorded movies can be added to the XBMC [[Video Library]] by setting the '''Content Type''' on the Movies directory and then choosing the appropriate Movie scraper.

Once the recorded Movies have been scanned to the Library, you can see and play them via the XBMC Movie Library.

'''NOTE:''' be sure to only set the content type for the '''Movies''' folder. XBMC doesn't understand how to add anything other than movies. If you choose a folder containing recorded TV Shows to be added to the library you may end up with all sorts of strange files in your XBMC library.

=== Automatic Commercial Skipping ===

Commercial breaks that have been flagged in MythTV are automatically skipped as of the 9.11 release (note that the option to turn EDL support on/off has now been removed). Prior to 9.11, automatic commercial skipping can be enabled by turning on [[EDL (commercial skipping) and SceneMarker support|Edit Decision List (EDL) support]] in XBMC Media Center through ''Settings -> Video -> Player -> Enable edit decision lists''.

Each commercial break is only skipped once so it's possible to go back into any incorrectly flagged commercial break. Scene markers are also put in at the beginning and end of the flagged commercial breaks to further support navigation.

For more information about the configuration that is possible for commercial skipping, see the [[EDL (commercial skipping) and SceneMarker support|Edit Decision Lists]] wiki page.

=== Deleting Recorded Programs ===

The ability to delete recorded programs can be enabled through ''Settings -> Appearance -> View Options -> Allow file renaming and deletion''.

=== Known Problems ===

* Need to delete a recording twice for it to be removed if using a MythTV 0.20 backend. Deleting works as expected using a MythTV 0.21 backend.
* Channel changes can take some time when using LiveTV.

=== Trouble Shooting ===

==== Recordings Don't Play ====

For the myth:// protocol to play recordings, XBMC must be able to access the '''IP Address''' configured in the MythTV backend using '''mythtv-setup'''. This is necessary because of the way the Myth Protocol works. The Myth API gets the IP Address configured in the MythTV backend and uses that to stream recordings.

If a hostname was used in the IP Address configuration for the MythTV Local Backend, either the DNS server on the network needs to be able to resolve the hostname to an IP address, or a static hostname to IP address entry is needed on the XBMC machine. A static IP address mapping can be set in the ''/etc/hosts'' file in Linux or Mac OSX, or in the ''AdvancedSettings.xml'' file for the original XBox.

Even if you haven't used a hostname, it may be worth adding an ''/etc/hosts'' file entry, as it appears that the backend returns a hostname anyway sometimes (see [http://forum.xbmc.org/showthread.php?t=45050&page=3]).

Double check that the Local Backend IP Address configured in the MythTV backend is not set to ''localhost'' or ''127.0.0.1'' if the MythTV backend is running on a different machine to XBMC Media Center.

==== Guide Doesn't Display Anything ====

Check that the username and password supplied in the myth:// URL are a username and password that have access to the mythconverg MySQL database. The guide information is obtained directly from the database.

If a username and password have not been supplied in the myth:// URL then the default of 'mythtv' will be used for both.

See Setup in XBMC for more information.

==== Live TV Doesn't Play ====

The '''libcmyth''' library used for to connect to MythTV from XBMC only enumerates the first 16 tuner devices when looking for available tuners. [http://trac.xbmc.org/ticket/4771 Trac - CMyth only enumerates 17 tuners]

Depending on what was done when the MythTV backend was set up, it's possible that some Tuner ID's are > 17 in the mythconverg database (especially if tuners were added and deleted several times, or if multiplexing is being used for digital terrestrial tuners).

If this is the case, you may be able to see the '''Guide''' and all the stations displayed in XBMC, but XBMC may not be able to select a tuner for live TV playback.

This can be resolved by removing all the tuners through '''mythtv-setup''' (so they start at 0 when re-added), and then re-adding them, or reducing the number of multiplexed virtual tuners that are created for each physical digital terrestrial tuner.

If a only a green screen displayed but the audio is working fine. Use mythtv's frontend to change the encoder to mpeg4. The settings can be found in "Utilites/Setup- Setup - TV Settings - Recording Profiles - Software Encoders. Select Live TV, and change it's encoder from rtjpeg to mpeg4.

==== Audio Plays Out of Sync ====

If CPU utilization is close to 100% on any of the CPU cores then there could be audio sync problems.

Depending on the video card and driver being used, there could be significant CPU utilized when playing H264 video content. The [[Advancedsettings.xml#.3Cskiploopfilter.3E|<skiploopfilter> advanced setting]] can be used to reduce the CPU utilization by reducing the quality of the output H264 video. Try setting it to 48.

== History of MythTV support in XBMC ==

MythTV support in XBMC has been available since ~2004. It started life as a Python script for the original XBox that had functionality added by willing developers over the following years. Eventually the script moved to the current home at Sourceforge, and is now called [http://sourceforge.net/projects/xbmcmythtv/ xbmcmythtv]. In late 2008 another script based solution arrived called [http://code.google.com/p/mythbox/ MythBox].

In 2007 support for communicating with the MythTV backend was added directly to XBMC via a Source using the myth:// protocol. This project uses the cmyth library, which was built to use the network based [http://www.mythtv.org/wiki/index.php/Myth_Protocol Myth Protocol] supported by MythTV.

In 2009, the [[GSoC - Unified PVR Frontend|Google Summer of Code - Unified PVR Frontend]] project was launched to provide added functionality to the existing myth:// protocol support (here is a historical [http://forum.xbmc.org/showthread.php?t=2297 MythTV frontend client built into XBMC] forum thread).

In early 2011 the initial work from the GSoC for the unified PVR API was folded into a branch of xbmc, which was eventually pushed back to mainline XBMC in October 2012 and is scheduled to be released in Frodo/12.x: see [[PVR]]. This support will include a [[PVR/MythTV|MythTV client]].

=== myth:// Source ===

The myth:// source was released in early 2007. This project uses the network based [http://www.mythtv.org/wiki/index.php/Myth_Protocol Myth Protocol] to communicate with the MythTV backend. It also accesses the MySQL database directly to get '''Guide''' information.

Although the myth:// source doesn't support all the functionality that the xbmcmythtv script supported, it is possible to play recordings, which is all many XBMC frontend systems need to support.

The native MythTV frontend client needs to be used to schedule recordings.

=== MythTV Python Scripts for XBMC ===

MythTV Python Scripts for XBMC that provide a python coded GUI for MythTV interface.

=== MythBox Script (Linux/Mac/Windows) ===

[http://code.google.com/p/mythbox/ MythBox] was released in late 2008 and is a XBMC script for MythTV that supports the most common frontend use cases:
* Watching recordings with commercial skipping
* Watching Live TV
* Creating and editing recording schedules
* Showing upcoming recordings
* TV Guide
* Tuner and job status
* Fanart and episode meta data from tvdb.com, tvrage.com, themoviedb.org, imdb.com, and Google image search.
* MythTV Backends: 0.21, 0.22, 0.23, 0.23.1

=== Myth2XBMC Script (Xbox) ===

[http://code.google.com/p/myth2xbmc/ Myth2XBMC] heavily based on the original [http://sourceforge.net/projects/xbmcmythtv/ xbmcmythtv] script and is only tested on the Xbox.

=== xbmcmythtv Script (Xbox) ===

Support for MythTV in XBMC started with this [http://sourceforge.net/projects/xbmcmythtv/ xbmcmythtv] python script for XBMC on the Xbox. This project communicated with the MythTV mythconverg MySQL database to get information, and played recordings via a Samba share on the MythTV backend.

The last official release of the Python script was in May 2007 and supported version 0.20 of MythTV and protocol 34. Various unofficial releases were made available by some of the developers of xbmcmythtv, but appears to no longer be supported on an ongoing basis.

=== MythicalLibrarian and MythSExx ===

[[MythicalLibrarian]] and [[MythSExx]] are bash scripts which can be run on the MythTV server to create symlinks to the recorded files. The symlinks use the supported XBMC naming conventions so the standard filesystem scrapers can be used to scan recorded MythTV content into the XBMC Movie and TV Show libraries. They also generate the required EDL files to support commercial skip during playback.

[[MythicalLibrarian]] handles both TV episodes and Movies whereas [[MythSExx]] only handles TV episodes.

== External links ==

* [http://www.mythtv.org mythtv.org] - MythTV official website
** http://en.wikipedia.org/wiki/MythTV
* [http://mythbuntu.org mythbuntu.org] - Mythbuntu official website, a Linux distro with MythTV preconfigured
** http://en.wikipedia.org/wiki/Mythbuntu
* [http://adamhaeder.com/wordpress/2010/01/19/how-to-configure-xbmc-as-a-mythtv-frontend/ Walkthrough on how to configure XBMC for MythTV support], including skin modification for episode information, and EventGhost remote control support.

[[Category:File sharing]]
[[Category:Live TV]]

Archive:Set up PS3 BD Remote

2014-10-13T17:39:03Z

Slvr32: Spelling/grammar errors, setup vs set up

MySQL/Setting up MySQL

2014-10-13T17:37:29Z

Slvr32: Spelling/grammar error, setup vs set up

{{:MySQL/Contents}}
{{mininav| [[MySQL]] }}
You'll need to choose which of your computers, XBMC devices, or [[NAS]] will be the MySQL server. The server needs to be on 24/7 or have wake-on-lan (preferably the former), and needs to have a local static IP. You will probably want the XBMC device that is hosting most or all of your videos and music to also be the MySQL server, but this is not required.
{{-}}

{{note|XBMC v13 seems to have fixed the issue with MySQL 5.6, making it safe to use with XBMC.}}

{{redv|'''Please Note:'''| Don't create the MySQL databases on your server'''. Simply set up the MySQL server itself, as XBMC will create the specific databases by itself.}}

MySQL can be installed on just about every major OS:

=Ubuntu Linux=
'''Ubuntu Linux:'''
#<code>$sudo apt-get install mysql-server</code> ''(see also: https://help.ubuntu.com/10.04/serverguide/C/mysql.html )''
#Create a password when asked
#To configure MySQL to listen for connections from network hosts, edit ''/etc/mysql/my.cnf'' and change the bind-address directive to the server's IP address:
##from: <code>bind-address = 127.0.0.1</code>
##to: <code>bind-address = 192.168.0.5</code>
#*Note: Replace 192.168.0.5 with the appropriate address.
#*Note: To allow local and remote access try comment out bind-address using a hash(#) or use <code>bind-address = 0.0.0.0</code>
#Restart your MySQL server. <code>$sudo restart mysql</code>
#Get into the MySQL command line utility: <code>$mysql -u root -p</code>
#Enter the following commands:
##Type in: <code>CREATE USER 'xbmc' IDENTIFIED BY 'xbmc';</code> and press return
##Type in: <code>GRANT ALL ON *.* TO 'xbmc';</code> and press return
#Close out the command line tool with <code>\q</code>

=Arch Linux=
'''Arch Linux:'''
*Please note: Arch, along with many other distributions, has migrated to the faster and more open MariaDB. It is a drop in replacement to MySQL and, thus, XBMC will require no modifications to work with it.
#Install MariaDB: <code>$ sudo pacman -S mariadb</code>
#Start the service: <code>$ sudo systemctl start mysqld</code>
#To have it automatically launch at startup: <code>$ sudo systemctl enable mysqld</code>
#Create a password: <code>$ /usr/bin/mysql_secure_installation</code> ''This will also clean up the demo database.''
#Get into the MariaDB command line utility: <code>$ mysql -u root -p</code>
#Enter the following commands:
##Type in: <code>CREATE USER 'xbmc' IDENTIFIED BY 'xbmc';</code> and press return
##Type in: <code>GRANT ALL ON *.* TO 'xbmc';</code> and press return
#Close out the command line tool with <code>\q</code>

=RedHat based Linux=
'''RedHat based Linux (RHEL, CentOS, Fedora):'''
#<code>$sudo yum install mysql-server</code>
#Create a password when asked
#To configure MySQL to listen for connections only from network hosts, edit ''/etc/mysql/my.cnf'' and add the bind-address directive to the server's IP address:<br /><code>bind-address = 192.168.0.5</code>
#*Note: Replace 192.168.0.5 with the appropriate address.
#*Note: Alternatively you can leave this file as is to allow local and remote access.
#Restart your MySQL server. <code>$sudo /sbin/service mysqld restart</code>
#*Recommended - Set your MySQL root password with <code>/usr/bin/mysqladmin -u root password 'new-password'</code>
#Get into the MySQL command line utility: <code>$mysql -u root -p</code>
#*Enter your MySQL root password as set above, or just press enter if you didn't set one to log in with a blank password
#Enter the following commands:
##Type in: <code>CREATE USER 'xbmc' IDENTIFIED BY 'xbmc';</code> and press return
##Type in: <code>GRANT ALL ON *.* TO 'xbmc';</code> and press return
#Close out the command line tool with <code>\q</code>

=Mac OS X=
'''Mac OS X:'''
#Download a copy of MySQL server from http://dev.mysql.com/downloads/mysql/
#In Mac OS X, go to System Preferences -> MySQL, and click on “Start MySQL Server”. You’ll also want to tick to enable the “Automatically … on Startup” option.
#Now to set up the "xbmc" user in MySQL and give it access. Launch Terminal.app on your Mac and issue the following commands, one line at a time:
##<code>sudo /usr/local/mysql/bin/mysql</code>
##<code>CREATE USER 'xbmc' IDENTIFIED BY 'xbmc';</code>
##<code>GRANT ALL ON *.* TO 'xbmc';</code>
##<code>exit</code>
#Remain in Terminal.app. Now you'll be giving other computers on your network access to MySQL. Enter the next set of commands, one line at a time:
##<code>cd /usr/local/mysql/support-files/</code>
##<code>sudo cp my-huge.cnf /etc/my.cnf</code>
##:''The command line will ask for your Mac OS X user password. Enter it and press return. No text will show when you type your password in, this is normal.
##<code>cd /etc</code>
##<code>sudo nano my.cnf</code>
##:''This opens a file in a command line text editor''
##Scroll down to the [mysqld] section and add or edit the following line so that it appears as:
##:<code>bind-address = ***.***.***.***</code>
##Save and exit from the command line text editor
#Reboot the Mac, or restart the MySQL service from the System Preferences pane you installed earlier

*Alternative guide for Mac OS X: http://forum.xbmc.org/showthread.php?tid=151631

=Windows=
'''Windows:'''
#Download a copy of MySQL server from http://dev.mysql.com/downloads/mysql/
#Select ''Standard configuration''
#Create a password when asked
#Select that you want the database to have network access when prompted during installation.
#Open the "MySQL Command Line Client" from the MySQL start menu
#Enter the following commands:
##Type in: <code>CREATE USER 'xbmc' IDENTIFIED BY 'xbmc';</code> and press return
##Type in: <code>GRANT ALL ON *.* TO 'xbmc';</code> and press return
#Close out the command line tool
#If you're using a firewall such as the one that's built into Windows, you will need to do this next step.
:*'''Windows 7 Built-in Firewall'''
:#Go to control panel and open Windows Firewall
:#Click on Advanced Settings
:#Click on Inbound Rules, then New Rule
:#For the Rule Type, choose '''''Port''''' and hit Next
:#For Protocol and Ports, select TCP protocol and type in '''''3306''''' for the '''''Specific local ports''''' and hit Next
:#For Action, leave it at default which is '''''Allow the connection''''' and hit Next
:#For Profile, you can leave it as default (everything checked by default) and hit Next
:#For Name, set it to '''''MySQL''''' or any name that you will know what it is and click Finished
:*'''Windows XP Built-in Firewall'''
:#Open Control Panel and Set to 'Classic View'
:#Double Click on Windows Firewall
:#Click on tab that says Exceptions
:#Click on Add Port
:#Name it '''''MySQL''''' or any other name
:#Set the port number to '''3306'''
:#Choose '''''TCP''''' and click OK

{{Note|If XBMC is unable to connect to the MySQL server, returning an error code [1130]:}}<br/>
If this occurs to you, try amending Step 2 above to read <code>GRANT ALL ON *.* TO 'xbmc'@'xxx.xxx.xxx.%';</code> where xxx.xxx.xxx is the first three quadrants of your home network's IP address (192.168.1 for example) and % as the last quadrant to allow addresses on the same subnet to connect.

=Other NAS=
MySQL can also be installed on some [[w:network-attached storage|network-attached storage (NAS)]] device devices. Here are some guides for various NAS devices that can have a MySQL server installed:

*Devices running Arch Linux ARM (such as the PogoPlug, Dockstar, etc) can use the [[HOW-TO:Share libraries using MySQL/Setting up MySQL/ALARM|Arch Linux instructions]] on this page.
*[http://quixventure.com/2011/12/configure-a-synology-nas-as-mysql-server-for-xbmc/ Synology NAS as MySQL server for XBMC] and http://youtu.be/3PmmDtK65ks
*http://www.robvanhamersveld.nl/2013/02/05/share-your-xbmc-12-0-library-on-a-synology-ds-or-other-nas/ Synology DS with MySQL guide based on Frodo
*http://forum.xbmc.org/showthread.php?tid=172548 - unRAID

=FreeNAS and freeBSD=

== About FreeNAS ==

http://www.freenas.org/

FreeNAS is a FreeBSD based NAS system that can be run on almost any hardware - it uses ZFS for disk and file management. It is used at home and in enterprise businesses. 99% of tasks can be done via the web interface.

Example below is based on FreeNAS 9.1.1 on 12/12/13, and assumes you have already configured your nas with drives, datasets etc

== How to ==

=== Make a jail ===

create a Jail via the FreeNAS webui - if unsure see here http://doc.freenas.org/index.php/Adding_Jails

make a note of the jail IP address shown - you will need this to put in the advancedsettings.xml file on the XBMC machine later

=== Prepare the jail ===

*ssh into FreeNAS
**If you have a windows PC use putty (http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html)
**(easiest) click the "shell" button in the left of the FreeNAS webui

type the following commands

*<code>jls</code>

Take note of the JID of the jail you created, use it in the command below and replace n with the number of the jail you just created

*<code>jexec n csh</code>

=== Install mysql ===
You are now inside your jail

*<code>pkg install mysql55-server</code>

*<code>pkg install nano</code>
**(nano is a text editor you will need shortly)

We now need to enable mysql in rc.conf

*<code>nano /etc/rc.conf</code>

insert the line below into the rc.conf file

*<code>mysql_enable="YES"</code>

save the file and exit (see bottom of nano edit page for keystrokes info)

*<code>service mysql-server start</code>

Optional step below - this is an automated script that will secure you mysql instance - it will prompt you for answers to questions. Its up to you if you do this.

*<code>mysql_secure_installation</code>

=== Configure mysql ready for xbmc to use ===

type in

*<code>mysql -u root -p</code>

You are now in mysql administration

* <code>CREATE USER 'xbmc' IDENTIFIED BY 'xbmc';</code>
* <code>GRANT ALL ON *.* TO 'xbmc';</code>
* <code>quit;</code>

=Restricting MySQL access rights=
'''Optional:''' '''If you only use the MySQL server for XBMC and that server has non-critical data on it, then this probably not necessary.'''
For a more secure MySQL installation use these 2 commands to grant permission only to databases XBMC uses. This is useful if you plan on using your MySQL server for more than just XBMC, or if you're worried about your internal network being exposed and wanting to lock things down more, etc.
#<code>GRANT ALL ON `MyMusic%`.* TO 'xbmc'@'%' IDENTIFIED BY 'xbmc';</code>
#<code>GRANT ALL ON `MyVideos%`.* TO 'xbmc'@'%' IDENTIFIED BY 'xbmc';</code>

{{Divbox|orange||
The limited grants on this page don't give the xbmc user permissions to create required TRIGGERs during install or upgrade.
'''XBMC requires these TRIGGERs to function properly.'''
Use the broader grant *.* statement that is explained on the previous tabs while creating or upgrading the tables. Only restrict rights afterwards, if you need to.

Alternatively, figure out how to specifically give the account the right to create the require TRIGGERS - this varies between MySQL versions. }}
<headertabs />

{{Next|[[MySQL/Setting up XBMC|Setting up XBMC]]}}

{{Gotham updated}}

Archive:Dharma Guide/Set up the sources

2014-10-13T17:36:05Z

Slvr32: Spelling/grammar error, setup vs set up

{{:Dharma Guide/Contents}}
This is where XBMC looks for your media-files. The Sources will determine the content of your library, they are necessary in order for XBMC to index your Video -Files into the proper libraries. Be aware that you always should name your video- and music-sources according to XBMC’s set. This will make sure that you have the best possible experience with the XBMC. Let’s get started.

== Organization of your media files ==
Before we are adding your files to your XBMC-Sources you should make sure that the files are named properly. Ideally you have your movie-files all in one folder. It does not matter if there are subfolders
and/or single files in this directory. The best way however is to use subfolders for each movie you have. The folder should then be named like the following Layout: “Movie Name (Release-Year)”. The part "Release Year" is technically not necessary but it will make sure that XBMC scrapes the right movie and you have the right movie in your library. See the following table for "best practices" for your media-files (entries inside [] are to be replaced by the respective values):
{| cellspacing="0" border="1"
!Sourcetype
!Folder-Structure
!mediafile-name
|-
|Movies
|''Movies'' ⇒ ''Movie-Name (Release-Year)''
|''moviename (Release-Year).FileExtension''
|-
|TVShows
|''TVShows'' ⇒ ''TVShow-Name (Release-Year)'' ⇒ (optional) ''Season [SeasonNumber]''
|''tvshowname.S[SeasonNumber]E[EpisodeNumber].FileExtension
|}

If you currently have not sorted your movie-directory, you can do this with the help of some additional tools which are available. Some of these tools also apply to TV Shows and can you help sort them out too. Note however that Sickbeard (which will be handled later in this Guide) will sort your TV-Shows in the best possible way and also names your files according to the mentioned best practices.

=== Multiplatform ===
* [http://sourceforge.net/projects/universalmc/ UniversalMC]
* [http://forum.xbmc.org/showthread.php?t=49370 Media Reader]
* [http://wiki.xbmc.org/?title=MythicalLibrarian MythicalLibrarian] (for MythTV-Recordings)

=== Windows ===
* [http://forum.xbmc.org/showthread.php?t=59800 XBNE]
* [http://mediacompanion.codeplex.com/ MediaCompanion]
* [http://www.plyoung.com/projects/xmm2/ XMM2]
* [http://sourceforge.net/projects/emm-r/ Ember Media Manager]

=== Mac OS X ===
* [http://forum.xbmc.org/showthread.php?p=886768 ViMediaManager]

These tools also will generate usable NFO-Files for the XBMC. NFO-Files are little text-files in which all information about the movie is stored in a XML-Layout. If XBMC finds a NFO-File inside a subfolder, it will use the information from this NFO rather than downloading the information from the internet. For some more information on NFO-Files head down, you’ll find a section dedicated to them. A neat function of the XBMC provides the possibility to play two video-files as if they are merged to one file. This is helpful for movies which contain multiple CDs. If you have the movie "The Matrix" for example split into two files, you should name those files like "The Matrix.CD1.FileExtension" and "The Matrix.CD2.FileExtension" (this will be done by the media managers mentioned above as well). When scraping this movie to the library, XBMC will know that this is supposed to be one movie and will index the both files only as one movie in your library. If you then play this movie via the library in your XBMC both files will be played – the CD2 after CD1 ends obviously. You won’t even notice the cut between those (unless the files have an overlay of course) two.
Back to the XBMC. To start adding a source for movies hit the "Videos" button in the home - You will see a list of your CD-Drives and removable media-devices which are connected right now. You will also find a Button "Add Source" – hit it in order to bring up the Source-Menu.

You will find a screenshot below, how that should look like:

[[File:Dharma Guide 02.png|575px]]

Hit the "Browse"-Button and locate your movie-location. Click "OK" and move to the Content-Screen.

It will look like this:

[[File:Dharma Guide 03.png|445px]]

If you want to add your movies right now (you want to ;-)) hit the selection "Run automated scan". If you use subfolders in your main movie-folder you should set "Use folder names for lookups" and "Scan recursively" too. Hit "Ok" – XBMC will now search for your stored movies with the Movie- Scraper and adds the contents to your library. This will take a while.

== TV shows ==
{{editor note|This section is originally directed at users of the program sickbeard}}
Before adding TV-Shows to XBMC you should complete the Sickbeard-Tutorial first. Click here to read it now. Come back when Sickbeard is fully configured. Open up Sickbeard in your Browser and click on the button "Manage". A list of all your TV-Shows should be presented to you – click on the empty field beneath "Rename". This should mark all the "Rename"-Fields of the shows. Now click on "submit" below. Use it in order to change your entire TV-Show-Collection to the right naming convention for XBMC. Also – It will help you to actually sort your Collection and to make it more accessible. With TV-Shows you also have the option to use locally stored NFO-Files for XBMC. In this case XBMC will also use the provided information in the NFO-Files to check for your TV Shows. This will make sure that you do not have problems with the scanning. Check the option in the sickbeard- config if you want the Files to be created. Be aware that you should apply the naming-convention "TV-Show-Name (Starting-Year)" to the subfolders holding your TV-Shows. This will make sure that you do not get the wrong information.

Now head back to the XBMC and hit the "Add Source"-Button. Select your TV-Show-Directory and click OK. In the "Content"-Screen you should then select "TV Shows". Mark the option "Run automated scan" if you want to. XBMC will now scrape all your Shows to your library.

{{editor note|Sickbeard section of The Dharma Guide not currently included on the XBMC Wiki}}

== Advanced library configuration ==

'''Using advanced "nfo"-files'''

As mentioned in the steps above NFO-files can be used by the XBMC to correctly read the information about your files instead of relying on online-data. But you can do more with those NFO- Files then simply replacing the online-stored information. An example is grouping movies into a set. For example:

* Die Hard
* Die Hard 2
* Die Hard With a Vengeance
* Live Free or Die Hard

These films are all part of the "Die Hard"-Quadology, however because "Live Free or Die Hard" begins with an "L" rather than a "D" it is ordered elsewhere and not nearby all the other "Die Hard"-Movies. You can add information to your NFO-File of the movie to correct this issue:

<xml>
<movie>
<title>Live Free or Die Hard</title> <--- (Title of the movie) --->
<set>Die Hard Collection</set> <--- (Set name to which it belongs) --->
<sorttitle>Die Hard 4</sorttitle> <--- (Title within the set) --->
</movie>
http://www.themoviedb.org/movie/1571
</xml>

Repeat these steps for the other Die Hard films, re-scrape and they should display as one movie set in your library. There is also a handy addon which will write those XML-Files for you. You can find the addon in the usual repo (see the AddOn-Section of this guide for information on AddOns and how to install them).

NFO-Files can influence many aspects of XBMC’s library. For more information visit the XBMC-Wiki: [[Import - Export Library#Video nfo Files containing XML data]]

'''Automatic cleaning of the library'''

If you delete a lot of movies/TV Shows after you have watched them, you will notice that the XBMC will not clean these files if you launch the Library-Update. You can erase those movies only if you pick the "Clean Library"-Function in the settings-menu. Another solution however would be to put a file "advancedsettings.xml" into your XBMC-Userdata-Folder. For Windows just hit "Windows-Key" + "R" and type in "%AppData%/XBMC/userdata". Create a new text-file with the following content inside this directory:

<advancedsettings>
<videolibrary>
<cleanonupdate>true</cleanonupdate>
</videolibrary>
</advancedsettings>

Rename the file to "advancedsettings.xml" and restart your XBMC. Your XBMC will now clean your video-library every time it updates it.

You can do a lot more with the "advancedsettings.xml" – for more information check the XBMC-Wiki: [[advancedsettings.xml]]

{{rename media|Archive:Dharma Guide/Set up the sources|Spelling/grammar error, i.e. 'setup' is a noun, 'set up' is a verb, and 'set up' is correct here}}

Archive:Set up HDMI audio on GeForce GT210, GT220, or GT240

2014-10-13T17:34:52Z

Slvr32: Spelling/grammar error, setup vs set up

{{outdated}}

== XBMC Live [Eden] 11.0 ==
'''May 4, 2012'''

Update : Lesser configuration in Eden:

In XBMC
System => System => Audio output
[Both Audio Out and passthrough] on custom : hdmi:CARD=NVidia

Use :

add-apt-repository ppa:team-iquik/alsa
add-apt-repository ppa:ubuntu-audio-dev/ppa
apt-get update
apt-get upgrade

When you dont have sound, start alsamixer, choose your card, en unmute it (M).

If this still dont works, use the manual below.

== XBMC Live [Dharma] 10.1 ==

'''April 11, 2011'''

EVGA GT210 - added file "sudo nano /etc/asound.conf" for menu sound

pcm.!default {
type plug
slave {
pcm "hw:0,3"
rate 48000
}
}

In XBMC
System => System => Audio output
[Both Audio Out and passthrough] on custom "plughw:0,3" [Card 0, Device 3 from "aplay -l in telnet"]

Update: Didn't need to put custom "plughw:0,3" "HDA Nvidia hdmi" works also.
Tested with G210 / Asus EN210

== Before You Begin/Notes ==
This guide assumes that you have a GeForce G210, GT220, or GT240 card, are using a reasonably up-to-date system, and that you have at least the nVidia 190 series proprietary drivers installed.

== Getting ALSA ==

Team iQuick also has a PPA with the latest ALSA drivers and Ubuntu Audio Dev PPA has the necessary kernel modules for Lucid (What XBMC-Live is based on).

add-apt-repository ppa:team-iquik/alsa
add-apt-repository ppa:ubuntu-audio-dev/ppa
apt-get update
apt-get upgrade
apt-get install linux-alsa-driver-modules-$(uname -r) --force-yes

Or if you haven't yet installed ALSA:

apt-get install alsa-base alsa-utils linux-alsa-driver-modules-$(uname -r)

-----
Compiling from source:

ALSA 1.0.23 contains the new drivers. You can download, compile, and install it without further additions, and proceed to configuration. The drivers are also included with the 2.6.34 Linux kernel; users of this kernel should be able to skip straight to configuration as long as the <tt>snd_hda_codec_nvhdmi</tt> module (and its dependencies) are available.

In general, you can choose to [http://www.alsa-project.org/main/index.php/Download install ALSA from source] or use the [http://ubuntuforums.org/showthread.php?p=6589810 ALSA Upgrade Script]. Alternatively, you can find updated packages for your distribution. Note that only the ''drivers'' from 1.0.23 or later are required; updating the ALSA userspace tools is optional.

Ubuntu users make sure to remove the <tt>linux-backports-modules-alsa-`uname -r`</tt> package or your newly compiled ALSA drivers will be ignored.

== Setting Module Options ==
You may need to set options in <tt>/etc/modprobe.d/sound.conf</tt> depending on your card. The general format is:

options snd-hda-intel ''OPTIONS''

Please list your card and working module options below, along with the working device(s). Note that these options may change with future revisions and refinements to the drivers.

{| class="wikitable" style="width:100%;"
! nVidia GPU !! Manufacturer/Model !! Options !! Best/working device (X=Card #)
|-
| G210 || Point of View GF G210 || <tt>enable_msi=0 probe_mask=0xffff,0xfff2</tt> || plughw:X,7 (only stereo confirmed)
|-
| G210 || MSI N210 MD512H || <tt>enable_msi=0</tt> || plughw:X,7 (only stereo confirmed)
|-
| G210 || Asus EN210 || no options needed with a current alsa snapshot || plughw:X,7 (PCM, multichannel PCM, bitsteam (DD/DD-EX/DTS/DTS-ES)
|-
| G210 || Club 3D CGNX-212LI || <tt>enable_msi=0 probe_mask=0xfff2</tt> || plughw:X,7 (only stereo confirmed)
|-
| G210 || Galaxy G210 PCI-E 512M || <tt>enable_msi=0 probe_mask=0xfff2</tt> || hw:X,3 (6 channels)
|-
| G210 || EVGA 512-P3-1213-LR || <tt>probe_mask=2</tt> || plughw:X,3 (confirmed 2ch PCM, 6ch AC3 bitstream)
|-
| GT220 || Asus BRAVO 220 SILENT/DI/1GD2(LP) || no options needed with a current alsa snapshot || plughw:X,7 (PCM, multichannel PCM, bitsteam (DD/DD-EX/DTS/DTS-ES)
|-
| GT220 || Zontac ZT-20201-10L GT220 || <tt>enable_msi=0 probe_mask=0xfff2</tt> || plughw:X,3 (6 channels)
|-
| GT220 || ASUS ENGT220/DI/1GD2(LP) || <tt>enable_msi=0 probe_mask=0xfff2</tt> || hw:X,3 (only stereo confirmed)
|-
| GT220 || ASUS ENGT220/G/DI/1GD3(LP)/A || <tt>enable_msi=0 probe_mask=0xfff2</tt> || hw:X,3 (PCM, multichannel PCM, bitstream (DD/DD-EX/DTS/DTS-ES)
|-
| GT220 || HP Pavilion Elite HPE-141F || <tt>enable_msi=0 probe_mask=0xffff,0xfff2</tt> || hw:X,3 (only stereo confirmed)
|-
| GT210/GT220/GT240 || Any GT210/GT220/GT240 || <tt>enable_msi=0 probe_mask=0xffff,0xfff2</tt> || plughw:X,3 (PCM, multichannel PCM, bitsteam (DD/DD-EX/DTS/DTS-ES))
|-
| GT240 || MSI N240GT-MD1G || <tt>enable_msi=0 probe_mask=0xffff,0xfff2</tt> || hw:X,3 (only stereo confirmed)
|-
| GT240 || ASUS ENGT240/DI/512MD5/A || <tt>enable_msi=0</tt> || plughw:X,7 (only stereo confirmed)
|
|-
| GT240 || Zotac ZEGT240/DI/1024 || <tt>enable_msi=0 probe_mask=0xfff2</tt> || plughw:X,3
|-
| ION-2 || Asus AT5IONT-I || <tt>enable_msi=0 probe_mask=0xffff,0xfff2</tt> || plughw:X,3
|-
| ION-2 || Jetway Mini-Top || <tt>enable_msi=0</tt> || plughw:X,7
|-
| ION-2 || Asus S1-AT5NM10E || no options needed with a current alsa snapshot || hw:X,7 (6 channels)
|}

* I'm asserting that any GT210/GT220/GT240 should use plughw or plug to allow AC3 passthru. I'm not an alsa expert but the following link suggests plug should be used. However I found this info after getting it working with plughw and I'm loath to break a working system to test it (volunteers?). [http://www.alsa-project.org/main/index.php/DeviceNames Alsa Recommened DeviceNames]

Once you've set your module options, proceed to "PulseAudio Configuration" (if applicable) or "Finishing Configuration".

=== If that doesn't work... ===
if probe_mask doesn't work for you (it didn't for me, one boot my GT220 came up first instead of second, but next reboot it came up second without me touching the probe_mask parameter, you can try this (which works reliably for me):

options snd-hda-intel enable_msi=0 index=-2

or

options snd-hda-intel enable_msi=0 index=1

The first one tells snd-hda-intel "don't grab index 0", while the second one says "grab index 1" (so even if you disable your on-board card, your GT220 is still going to be hw:1,7)

I have to make a '''BIG NOTE''' that I don't have another Nvidia sound card on the motherboard, and that's why the above works for me. It won't work if you have an integrated nvidia sound AND a GT220.

For the case with Nvidia motherboard audio + GT210/GT220/GT240 HDMI don't be discouraged by the note above. I added the "enable_msi=0 probe_mask=0xffff,0xfff2" to /etc/modprobe.d/alsa-base.conf (Ubuntu 9.04) but I'm not 100% sure that's even necessary with 1.0.23. After that my HDMI audio showed up as plughw:2,3.

If multiple nVidia devices still show up with the recommended probe_mask, you may need to adjust it. More information about selecting the correct parameters for this option can be found in [http://www.kernel.org/pub/linux/kernel/people/tiwai/docs/HD-Audio.html#_codec_probing_problem Takashi Iwai's documentation for the High-Definition Audio drivers].

== XBMC Configuration ==
It may happen that even the PulseAudio configuration doesn't work. For example with the Point of View GeForce G210. In this case, simply set up the module options as described above, and then go into the XBMC Settings -> System -> Audio, select a custom device for audio and insert plughw:X,7. The audio should now work!

== PulseAudio Configuration ==
If using PulseAudio, add the following line to /etc/pulse/default.pa:

load-module module-alsa-sink device=hw:1,3

Where 1,3 is card#,device# for the nVidia HDMI output given by <tt>aplay -l</tt>.

== Finishing Installation ==
Now, reboot your system. Using <tt>`alsamixer'</tt>, select your nVidia card (select it from the F6 menu, or use the <tt>-c</tt> option) and unmute the S/PDIF output (press "m"; the box should change from "MM" to "OO".) Enjoy!

If you have no sound, you should ensure that your user is a member of the "audio" group:

$ groups
adm dialout cdrom '''audio''' video plugdev mythtv lpadmin

Consult your distributions' documentation to determine how to add users to groups.

If you still have no sound, you can try editing/creating /etc/asound.conf:

pcm.!default hdmi:NVidia
pcm:iec958 hdmi:NVidia

Ensure that <tt>$HOME/.asoundrc</tt> is empty, does not exist, or does not override these settings. Reboot.

{{rename media|HOW-TO:Set up HDMI audio on GeForce GT210, GT220, or GT240|Spelling/grammar error, i.e. 'setup' is a noun, 'set up' is a verb, and 'set up' is correct here}}

Archive:HOW-TO:Set up audio over HDMI on nVidia GeForce/nForce controller

2014-10-13T17:33:28Z

Slvr32: Spelling/grammar error, setup vs set up

{{outdated|These instructions are likely not compatible with '''Frodo''' [[AudioEngine]] builds|<big>NOTICE</big>}}

''All the information described below, taken from XBMC and Ubuntu forum''

{{note|This method was tested on ASUS P5N7A-VM motherboard [GeForce 9300 / nForce 730i] but it's believed to be working for any nVidia chipset that supports audio over HDMI. Also confirmed to work on ASUS M3N78-EM motherboard [nVidia GeForce 8300]. This method has also been confirmed working for ASUS AT3IONT-I Deluxe edition. For ASUS M78SM-S2H [nVidia GeForce 8200], updating to NVidia driver 310.19 and unmuting S/PDIF 1 was sufficient using XBMCbuntu "Eden" (Lubuntu 11.10 Oneiric Ocelot)}}
* This method works pretty well with the default installation of ALSA v1.0.22 (as of Ubuntu 10.04, lucid). There is no need to upgrade ALSA with the alsa-upgrade script.
* This guide configures ALSA, you should remove pulseaudio first.
<source lang="bash">
sudo apt-get remove pulseaudio
</source>

First, check which ALSA playback devices you have, you can use this command:
<source lang="bash">
aplay -l
</source>

You should see something like this:
<pre>xbmc@htpc:~$ aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: NVidia [HDA NVidia], device 0: ALC1200 Analog [ALC1200 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: NVidia [HDA NVidia], device 1: ALC1200 Digital [ALC1200 Digital]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: NVidia [HDA NVidia], device 3: NVIDIA HDMI [NVIDIA HDMI]
Subdevices: 0/1
Subdevice #0: subdevice #0
</pre>
The device is specified as hw:(card),(device). The sample above shows device 3 is labeled "NVIDIA HDMI"; we are gonna use that and it would be called hw:0,3.

Before continuing, run
<source lang="bash">
alsamixer
</source>
then make sure "S/PDIF 1" is not set to '''MM''' (Mute). If it is, press M to unmute that channel.
''This was enough to make the sound work on my card. --[[User:Sim175|Sim175]] 01:37, 5 August 2011 (UTC)''

Create the file "/etc/asound.conf", which configures the ALSA library for the user.
<source lang="bash">
sudo nano /etc/asound.conf
</source>
<source lang="xml">
pcm.!hdmi-remap {
type asym
playback.pcm {
type plug
slave.pcm "remap-surround71"
}
}

pcm.!remap-surround71 {
type route
slave.pcm "hw:0,3"
ttable {
0.0= 1
1.1= 1
2.4= 1
3.5= 1
4.2= 1
5.3= 1
6.6= 1
7.7= 1
}
}
</source>
{{note|This file only has an effect on the ALSA library if it is included by the user’s .asoundrc file, located in the user’s home directory.}}

The ttable section entries match sound channels (eg front left, centre, sub woofer) to speakers. You may find that you need to change the entries above if you find that your speakers are not playing the right channels afterwards. In particular you may need to change 2.4 to 2.2 and 4.2 to 4.4, as well as 3.5 to 3.3 and 5.3 to 3.5

Next, add the following lines to the end of the "/etc/modprobe.d/alsa-base.conf" file:
<source lang="bash">
# Audio over HDMI
options snd-hda-intel model=6stack-dig
</source>
The commands below should do the job:
<source lang="bash">
sudo su -
echo "# Audio over HDMI" >> /etc/modprobe.d/alsa-base.conf
echo "options snd-hda-intel model=6stack-dig" >> /etc/modprobe.d/alsa-base.conf
exit
</source>

Now change to "/usr/share/alsa/cards" and replace the default HDA-Intel.conf with the one at [http://pastebin.com/f2e38265 pastebin]. Don't forget to make a backup copy of the original one before proceeding, in case you need it in future. The command set below should do the job (you will have do this as "root"):
<source lang="bash">
sudo su -
cd /usr/share/alsa/cards
mv HDA-Intel.conf HDA-Intel.conf-ORIG
curl "http://pastebin.com/download.php?i=f2e38265" | tr -d \\r > HDA-Intel.conf
exit
</source>

As mentioned earlier, things will only work if there is a ".asoundrc" file in users' home directory; in this case the user is xbmc. So fire up a terminal and create one with the following (assuming the HDMI device is specified as hw:0,3, change it to suit your configuration):
<source lang="bash">
sudo nano ~xbmc/.asoundrc
</source>
<source lang="xml">
pcm.dmixer {
type dmix
ipc_key 1024
ipc_key_add_uid false
ipc_perm 0660
slave {
pcm "hw:0,3"
rate 48000
channels 2
format S32_LE
period_time 0
period_size 1024
buffer_time 0
buffer_size 4096
}
}

pcm.!default {
type plug
slave.pcm "dmixer"
}
</source>
Make sure that master volume and default PCM devices are not muted.
<source lang="bash">
sudo /usr/bin/amixer -q -c 0 sset 'Master',0 unmute && /usr/bin/amixer -q -c 0 sset 'Master',0 100
sudo /usr/bin/amixer -q -c 0 sset 'IEC958 Default PCM',0 unmute
sudo /usr/bin/amixer -q -c 0 sset 'IEC958',0 unmute && /usr/bin/amixer -q -c 0 sset 'IEC958',1 unmute
sudo alsactl store 0
</source>

This is the time to reboot the system to make changes take the effect. When you log back in, you can test the speakers with "speaker-test" command like this:
<source lang="bash">
speaker-test -D hdmi -c6 -r19200 -FS32_LE
</source>
The output should be something like the following. Although if you get a "Playback open error: -16,Device or resource busy" message, go back into XBMC and double check your sound, it may already be working through HDMI ;-)
xbmc@htpc:~$ speaker-test -D hdmi -c6 -r19200 -FS32_LE
speaker-test 1.0.23
Playback device is hdmi
Stream parameters are 19200Hz, S32_LE, 6 channels
Using 16 octaves of pink noise
Rate set to 19200Hz (requested 19200Hz)
Buffer size range from 6 to 544
Period size range from 3 to 273
Using max buffer size 544
Periods = 4
was set period_size = 108
was set buffer_size = 544
0 - Front Left
4 - Centre
1 - Front Right
3 - Rear Right
2 - Rear Left
5 - LFE

It appeared to be important that "Audio Settings" in the XBMC needs to be modified as well. Go to "Settings > System > Audio" and make the entries like the picture below.

[[File:Xbmc_audio_settings.jpg]]
{{|note|The values for the "Custom audio device" are case-sensitive, should be exactly as it's written. Always use the default skin for basic system setup. Now try playing a video or audio file, preferably one with multiple channels, and see If you find you have sound. If you dont, try changing the settings, for example changing Audio output to HDMI. You can also try changing the custom passthrough device and audio output device entries to hw:0,3 or whatever matches your system as explained above under the explanation of aplay -l output}}

You may notice that the mp3 playback is faster than that usual. If that happens put these in the advancedsettings.xml and should fix the problem.
<source lang="xml">
<audio>
<resample>48000</resample>
</audio>
</source>

If everything goes well, by now you are listening to the audio over HDMI. If you have sound, but find sounds are not coming out of the correct speakers, check the ttable entry mappings in ./.asoundrc Enjoy!!

{{rename media|HOW-TO:Set up audio over HDMI on nVidia GeForce/nForce controller|Spelling/grammar error, i.e. 'setup' is a noun, 'set up' is a verb, and 'set up' is correct here}}

Archive:Set up PS3 BD Remote

2014-10-13T17:32:03Z

Slvr32: Spelling/grammar error, setup vs set up

This HOW-TO explains how to setup the remote control for the Sony PlayStation 3 to use with XBMC for Linux. You'll need a Bluetooth dongle and of course the remote control. All these information can be found [http://forum.xbmc.org/showthread.php?t=50717 here] at the forum.

== Installation ==

=== BlueZ ===
Note: Newer versions of bluez have been released which appear to have this patch already. I didn't need to patch 4.63 to get BD working on ubuntu 10.04

''Note:'' Kitlaan now has patches up to Bluez-4.69, and the patch is required for 4.64 - 4.69

The latest versions of the patch are available at: http://kitlaan.twinaxis.com/projects/bluez-ps3remote/

<pre>sudo apt-get purge bluez
sudo apt-get install libdbus-1-dev libglib2.0-dev python-dbus python-gobject
cd ~
wget http://kitlaan.twinaxis.com/projects/bluez-ps3remote/bluez_ps3remote_4.91.diff
wget http://www.kernel.org/pub/linux/bluetooth/bluez-4.91.tar.gz
tar xvfz bluez-4.91.tar.gz
cd bluez-4.91
patch -p1 < ../bluez_ps3remote_4.91.diff
./configure && make
sudo checkinstall --fstrans=no --install=yes --pkgname=bluez --pkgversion "4.91-patched"
</pre>
When starting bluetoothd, check /var/log/syslog to make sure the config files are read. If bluetoothd searches for them at /usr/etc, you'll have to create symlinks:
<pre>
sudo ln -s /etc/bluetooth/input.conf /usr/etc/bluetooth/input.conf
sudo ln -s /etc/bluetooth/audio.conf /usr/etc/bluetooth/audio.conf
sudo ln -s /etc/bluetooth/serial.conf /usr/etc/bluetooth/serial.conf
</pre>

Or, using [https://launchpad.net/~kitlaan/+archive/ppa kitlaan's PPA]:
<pre>
sudo apt-get purge bluez
sudo add-apt-repository ppa:kitlaan/ppa
sudo apt-get update
sudo apt-get install bluez
</pre>

=== Kernel module ===
Check if the uinput module is running:
<pre>lsmod | grep uinput</pre>
If that's not the case:
<pre>
sudo modprobe uinput
echo uinput >> /etc/modules
</pre>

=== Pairing ===
Please note that the pairing script requires that the dbus-python and pygobject python modules are installed. They are normally installed on a default 9.04 Jaunty.
(If you need them added, apt-get install python-dbus and python-gobject.)
<pre>cd ~
wget http://kitlaan.twinaxis.com/projects/bluez-ps3remote/ps3pair.tar.gz
tar xvfz ps3pair.tar.gz
cd ~/ps3pair
sudo python ps3_pair.py
</pre>
Now press START+Enter on your PS3 remote for at least 7 seconds, then it should detect the remote. Then run
<pre>/usr/share/doc/bluez/examples/list-devices</pre>
to verify that the remote is paired (and connected). If list-devices is not installed into /usr/share, check the bluez source tree, it should be in there. Also, running
<pre>cat /proc/bus/input/devices | grep emot</pre>
should show the remote. If it does not show up, you may not have the uinput module loaded.

Then customize the file "/etc/bluetooth/input.conf" for button mappings and timeout values (Example [http://pastebin.com/m5e951b8b here]). At this point, the remote should connect (and auto-disconnect after a timeout, if configured). The d-pad is probably the best way to test it within xbmc. If you have a terminal active, pressing the number buttons should type the number.

''Note:'' - The pairing scripts are not required by some distro's - just install Blueman and setup your BD remote as an input service and trust the device - this way you dont explicitly need to pair the device - it simply becomes a keyboard extension. The input.conf below will take care of key mapping.

=== Example input.conf ===

A more advanced bluetooth input.conf is probably lurking in the depths of [http://forum.xbmc.org/showthread.php?t=50717 this thread], however here's an example to get you started. The first thing you'll need to change in this is your BD Remote's hardware address (i.e. change 00:1E:3D:B6:12:7E to your remote's address)

<pre>
# input.conf - kitlaan custom
# Configuration file for the input service

# This section contains options which are not specific to any
# particular interface
[General]

# Set idle timeout (in minutes) before the connection will
# be disconnect (defaults to 0 for no timeout)
#IdleTimeout=30

# This section contains options that are specific to a device
[00:1E:3D:B6:12:7E]
#
# Set a custom idle timeout (in minutes) for this device
IdleTimeout=1

# This section is the PS3 Remote keymap. It is loaded when bluez starts.
# Use 'uinput.h' from bluez sources or '/usr/include/linux/input.h' for
# a list of possible KEY_* values.
#
[PS3 Remote Map]
# When the 'OverlayBuiltin' option is TRUE (the default), the keymap uses
# the built-in keymap as a starting point. When FALSE, an empty keymap is
# the starting point.
#OverlayBuiltin = TRUE
0x16 = KEY_E # EJECT
0x64 = KEY_A # AUDIO
0x65 = KEY_Z # ANGLE
0x63 = KEY_T # SUBTITLE
0x0f = KEY_DELETE # CLEAR
0x28 = KEY_GRAVE # TIMER
0x00 = KEY_1 # NUM-1
0x01 = KEY_2 # NUM-2
0x02 = KEY_3 # NUM-3
0x03 = KEY_4 # NUM-4
0x04 = KEY_5 # NUM-5
0x05 = KEY_6 # NUM-6
0x06 = KEY_7 # NUM-7
0x07 = KEY_8 # NUM-8
0x08 = KEY_9 # NUM-9
0x09 = KEY_0 # NUM-0
0x81 = KEY_F7 # RED
0x82 = KEY_F8 # GREEN
0x80 = KEY_F9 # BLUE
0x83 = KEY_F10 # YELLOW
0x70 = KEY_I # DISPLAY
0x1a = KEY_S # TOP MENU
0x40 = KEY_M # POP UP/MENU
0x0e = KEY_ESC # RETURN
0x5c = KEY_C # TRIANGLE/OPTIONS
0x5d = KEY_BACKSPACE # CIRCLE/BACK
0x5f = KEY_TAB # SQUARE/VIEW
0x5e = KEY_SPACE # CROSS
0x54 = KEY_UP # UP
0x56 = KEY_DOWN # DOWN
0x57 = KEY_LEFT # LEFT
0x55 = KEY_RIGHT # RIGHT
0x0b = KEY_ENTER # ENTER
0x5a = KEY_F1 # L1
0x58 = KEY_F2 # L2
0x51 = KEY_F3 # L3
0x5b = KEY_F4 # R1
0x59 = KEY_F5 # R2
0x52 = KEY_F6 # R3
0x43 = KEY_HOMEPAGE # PS button
0x50 = KEY_INSERT # SELECT
0x53 = KEY_HOME # START
0x33 = KEY_R # SCAN BACK
0x32 = KEY_PLAY # PLAY
0x34 = KEY_F # SCAN FORWARD
0x30 = KEY_PAGEUP # PREVIOUS
0x38 = KEY_STOP # STOP
0x31 = KEY_PAGEDOWN # NEXT
0x60 = KEY_COMMA # SLOW/STEP BACK
0x39 = KEY_PAUSE # PAUSE
0x61 = KEY_DOT # SLOW/STEP FORWARD
0xff = KEY_MAX
</pre>

== Troubleshooting ==

=== Pairing ===
After pairing, running <pre>cat /proc/bus/input/devices | grep emot</pre> doesn't list your device, and you've got ''uinput'' loaded <pre>lsmod | grep uinput</pre>
* Install blueman <pre>sudo apt-get install blueman</pre>
* Open System->Preferences->Bluetooth Manager.
* If your device is listed (it should be), right click it and select ''Input service''.
* Go to a terminal and try pushing some buttons on the remote, it should work.

[[Category:Remotes]]
[[Category:Linux]]
[[Category:How-to]]

{{rename media|HOW-TO:Set up PS3 BD Remote|Spelling/grammar error, i.e. 'setup' is a noun, 'set up' is a verb, and 'set up' is correct here}}

Archive:Set up Streamzap PC Remote for Linux

2014-10-13T17:30:56Z

Slvr32: Spelling/grammar error, setup vs set up

This page is all about getting the '''[[Streamzap PC Remote]]''' to work completely with XBMC. Currently it includes only information on how to configure Streamzap on Linux.

== Remote button configuration ==

In this tutorial all buttons have mapped to their matching functionality in XBMC. However, since the remote has no display, info, or title button those have been mapped to the color buttons on the bottom of the remote. Feel free to change them as necessary.

Here are the mappings:
* Display Command: YELLOW button
* Title Command: RED button
* Info Command: GREEN Button
* Blue Command: BLUE Button

== Linux setups ==

There are two ways you can set up Streamzap to work with XBMC on Linux.
* LIRC
* inputlirc

''' Important Note''':<br />
If you run LIRC and Inputlirc they will conflict when it comes to ownership /dev/lircd. That is service that runs last gets control of it (and on Ubuntu that services always seems to be inputlirc). You can check it out for yourself by restarting either service and the doing ls -la /dev/lircd. Please make sure only one is running at one time.

== Setups tested ==

LIRCD:
* Gentoo and XBMC 9.11 (Camelot) and official app-misc/lirc-0.8.7 from portage
* Ubuntu 10.04 (Lucid Lynx) and XBMC 9.11 (Camelot)
* Ubuntu 10.10 (Maverick Meerkat) and XBMC 10.0 (Dharma RC1) [buggy, but has workaround, see below]

Inputlirc:
* Ubuntu 10.10 (Maverick Meerkat)and XBMC 10.0 (Dharma RC1) [buggy, no workaround yet, see below]

== Drivers ==
Streamzap PC Remote is well supported in linux. However, I have seen drivers named differently. Here are the variations I've run into:
* lirc_streamzap
* streamzap (new ir_core implementation?)
* rc_streamzap (new ir_core implementation?)

The configuration of LIRCD I've used in the past combine streamzap with lirc_dev.

== Bugs and workarounds ==

In Ubuntu 10.10 (Maverick Meerkat), pressing any button on the remote will send the event twice to the system. It seems to have been caused by including both the new and the old drivers in the kernel and each of the drivers sending the events to /dev/input/*.

Bug has been filed and confirmed, but the fix is still pending: [https://bugs.launchpad.net/ubuntu/+source/lirc/+bug/663651 https://bugs.launchpad.net/ubuntu/+source/lirc/+bug/663651]<br />
There is also a forum thread on this: http://ubuntuforums.org/showthread.php?s=68f4cf4da940af13a8e70457b034938d&t=1595018

'''Workarounds''':
* LIRD: Using a LIRCD with a socket configuration bypasses the problem of duplicate events. '''However''', if Streamzap still gets configured as keyboard input device it send keystrokes to the system. This can be fixed by disabling the Streamzap as keyboard as described below.
* Inputlirc: Disabling XInput device does not work when using Inputlirc since it uses the same event input system and gets the event twice anyways.

== Xinput: Preventing Streamzap from becoming a keyboard ==

This applies to people using Xorg 1.8 or higher (i.e. Ubuntu 10.10 (Maverick Meerkat) users)

Xorg 1.8 (and on) automatically scans attached devices using udev and add them as an input device (using Xinput). This creates a problem because Streamzap is then detected and added as keyboard device, and number of remotes keys are mapped to keyboard keys. For example in fresh install of Ubuntu 10.10 (Maverick Meerkat) the arrow buttons can be using to navigate around, volume and mute buttons control sound and power key pops up the shutdown dialog (other keys might work but I have not tested them).

While this feature is cool it does interfere with using the remote properly with XBMC since it is not integrated with Xorg standard keys (maybe one day?). As such I suggest disabling the remote from being detected/used as a keyboard. There are several solutions.

'''Important Note''': if you set AutoAddDevices to false in your xorg configuration, you can skip this section

=== Option 1: Disable Streamzap Xinput device usign xorg configuration ===

The correct way to disable Xinput device on Xorg 1.8 and higher is to use one or more of Match* statement and "Option Ignore" in an "Input Class" Section.

The following configuration block needs to to be added to xorg configuration.
<pre>
Section "InputClass"
Identifier "Ignore Streamzap IR"
MatchProduct "Streamzap"
MatchIsKeyboard "true"
Option "Ignore" "true"
EndSection
</pre>

There are two ways to do it:
* '''Recommended:''' add a 90-streamzap.conf file to a xorg.conf.d directory
* add the configuration directly to /etx/X11/xorg.conf

'''xorg.conf.d locations'''

xorg.conf.d location may vary on your system.
* Ubuntu 10.10 (Maverick Meerkat): /usr/share/X11/xorg.conf.d
* Ubuntu 10.04 (Lucid Lynx): /usr/lib/X11/xorg.conf.d
* ArchLinux: /etc/X11/xorg.conf.d/

So on Ubuntu 10.10 (Maverick Meerkat) run the following command and paste the configuration into the file.

sudo nano -w /usr/share/X11/xorg.conf.d/90-streamzap.conf

=== Option 2: Disable Streamzap Xinput device on user session start ===

Alternatively the Streamzap Xinput device can be disabled by a script run at login.

The following script disables the Streamzap as an Xinput device. Save it locally as '''streamzap-xinput-disabler''' in '''<SCRIPT_LOCATION>'''.<br />
The script is configured to look for Streamzap device attached to /dev/lirc0, you might need to change it if you have multiple IR Receivers.

<pre>
#! /bin/bash

REMOTE_DEVICE=/dev/lirc0

namePath="/sys/`udevadm info -q path -n $REMOTE_DEVICE`/../input*/name"
xinputLine=`xinput list | grep "$(cat $namePath)"`
id=`expr substr "$xinputLine" $(expr $(expr index "$xinputLine" "=") + 1) 100 | awk '{print $1}'`
propID=`xinput list-props $id | grep Enabled | awk '{print $3}'`
propID=${propID#"("}
propID=${propID%"):"}

xinput set-prop $id $propID 0
</pre>
<small>Borrowed and slightly modified from: [https://bugs.launchpad.net/ubuntu/+source/lirc/+bug/663651/comments/14 https://bugs.launchpad.net/ubuntu/+source/lirc/+bug/663651/comments/14]</small>

Add a start up entry for this script in your window manager to run this at start up. GNOME, KDE, XFCE and most WMs have a GUI for that. Alternatively one way to do it is by adding streamzap.desktop in ~/.config/autostart/ with following content. Make sure to replace '''<SCRIPT_LOCATION>''' with path you stored the script in.

<pre>
[Desktop Entry]
Encoding=UTF-8
Version=0.9.4
Type=Application
Name=Streamzap PC Remote Xinput Disabler
Comment=
Exec=<SCRIPT_LOCATION>/streamzap-xinput-disabler
StartupNotify=false
Terminal=false
Hidden=false
</pre>

=== Option 3: Use inputlirc to cripple Streamzap Xinput device ===

This a total hack. Not at all recommended. Use it at your own risk.

The premise of this, is that if inputlirc is configured with -g it grabs the input from the devices, specified under EVENTS= setting for inputlirc, so that no other application interferes with it. This way when X initializes the remote will be added as Xinput keyboard but won't receive any events, hence disabling it. This also means that at the end of the boot LIRC daemon needs restarted so it can take back /dev/lircd from inputlirc, making it the primary LIRC device.

Step 1, First follow the Inputlirc setup exactly as described in [[#Inputlirc]]

Step 2, Add a line to restart the LIRC daemon at the end of the boot sequence so it can take back control by editing /etc/rc.local
nano -w /etc/rc.local
Add following (above exit 0).
<pre>
service lirc restart
</pre>

== LIRC ==

[http://lirc.org/ LIRC] is a package that allows you to decode and send infra-red signals of many (but not all) commonly used remote controls. The most important part of LIRC is the lircd daemon that will decode IR signals received by the device drivers and provide the information to the system.

LIRC is versatile and can be configured to received from either a simple device node like /dev/lirc0 or from any device in /dev/input/ layer and to write either to a socket or to generate Linux input events. This tutorial currently only covers the default setup of reading from /dev/lirc0 device node and writing to socket /dev/lircd socket.

=== Installation and Configuration ===

Starting with LIRC 0.7.1 Streamzap PC Remote configuration has been included in the base package.

==== Ubuntu ====

During the install when prompted to select the IR Receiver please select "Streamzap PC Remote".

sudo apt-get install lirc

If LIRC is already installed on your system you need run the following to configure it.<br />
Again, when prompted to select the IR Receiver, select "Streamzap PC Remote".

sudo dpkg-reconfigure lirc

This will automatically setup the following files like so:

/etc/lirc/hardware.conf
<pre>
REMOTE="Streamzap PC Remote"
REMOTE_MODULES="lirc_dev streamzap"
REMOTE_DRIVER=""
REMOTE_DEVICE="/dev/lirc0"
REMOTE_SOCKET=""
REMOTE_LIRCD_CONF="streamzap/lircd.conf.streamzap"
REMOTE_LIRCD_ARGS=""

...

START_LIRCD="true"
</pre>

/etc/lirc/lircd.conf
<pre>
...

#Configuration for the Streamzap PC Remote remote:
include "/usr/share/lirc/remotes/streamzap/lircd.conf.streamzap"
</pre>

'''Fixing Ubuntu 10.10 (Maverick Meerkat) Duplicate Keypresses Issue'''

In Ubuntu 10.10 (Maverick Meerkat), pressing any button on the remote will send the event twice to the system. For more information read this: [[#Bugs and Workarounds]].

The solution is to prevent Streamzap from becoming a keyboard as describe here [[#Xinput: Preventing Streamzap from becoming a keyboard]]

==== Gentoo ====

Add streamzap to LIRC_DEVICES in /etc/make.conf

<pre>
...

LIRC_DEVICES="${LIRC_DEVICES} streamzap"
</pre>

Install app-misc/lirc, add it to boot, and run it.
<pre>
emerge -av app-misc/lirc
rc-update add lircd default
/etc/init.d/lircd start
</pre>

It works out of the box. However if you need to edit the either LIRC or remote configuration, use the following files:<br />

'''LIRCD config''': /etc/conf.d/lircd <br />
'''Streamzap Remote config''': /etc/lirc/lircd.conf <br />

=== Configuring XBMC ===
The last thing you need to do is let XBMC know to what buttons to respond.
This is done by editing a LIRC Map for XBMC.

nano -w ~/.xbmc/userdata/Lircmap.xml

and pasting the following:
<pre>
<lircmap>
<remote device="Streamzap_PC_Remote">
<play>PLAY</play>
<pause>PAUSE</pause>
<stop>STOP</stop>
<forward>&gt;&gt;</forward>
<reverse>&lt;&lt;</reverse>
<left>LEFT</left>
<right>RIGHT</right>
<up>UP</up>
<down>DOWN</down>
<pageplus>CH_UP</pageplus>
<pageminus>CH_DOWN</pageminus>
<select>OK</select>
<back>EXIT</back>
<menu>MENU</menu>
<title>RED</title>
<info>GREEN</info>
<skipplus>&gt;&gt;|</skipplus>
<skipminus>|&lt;&lt;</skipminus>
<display>YELLOW</display>
<record>RECORD</record>
<volumeplus>VOL_UP</volumeplus>
<volumeminus>VOL_DOWN</volumeminus>
<mute>MUTE</mute>
<record>RECORD</record>
<power>POWER</power>
<blue>BLUE</blue>
<one>1</one>
<two>2</two>
<three>3</three>
<four>4</four>
<five>5</five>
<six>6</six>
<seven>7</seven>
<eight>8</eight>
<nine>9</nine>
<zero>0</zero>
</remote>
</lircmap>
</pre>

In lirc 0.9 the names of the keys changed, so you should used the following configuration for the LIRC MAP:
<pre>
<lircmap>
<remote device="Streamzap_PC_Remote">
<play>KEY_PLAY</play>
<pause>KEY_PAUSE</pause>
<stop>KEY_STOP</stop>
<forward>KEY_FORWARD</forward>
<reverse>KEY_REWIND</reverse>
<left>KEY_LEFT</left>
<right>KEY_RIGHT</right>
<up>KEY_UP</up>
<down>KEY_DOWN</down>
<pageplus>KEY_CHANNELUP</pageplus>
<pageminus>KEY_CHANNELDOWN</pageminus>
<select>KEY_OK</select>
<back>KEY_EXIT</back>
<menu>KEY_MENU</menu>
<title>KEY_RED</title>
<info>KEY_GREEN</info>
<skipplus>KEY_NEXT</skipplus>
<skipminus>KEY_PREVIOUS</skipminus>
<display>KEY_YELLOW</display>
<record>KEY_RECORD</record>
<volumeplus>KEY_VOLUMEUP</volumeplus>
<volumeminus>KEY_VOLUMEDOWN</volumeminus>
<mute>KEY_MUTE</mute>
<record>KEY_RECORD</record>
<power>KEY_POWER</power>
<blue>KEY_BLUE</blue>
<one>KEY_1</one>
<two>KEY_2</two>
<three>KEY_3</three>
<four>KEY_4</four>
<five>KEY_5</five>
<six>KEY_6</six>
<seven>KEY_7</seven>
<eight>KEY_8</eight>
<nine>KEY_9</nine>
<zero>KEY_0</zero>
</remote>
</lircmap>
</pre>

== Inputlirc ==

Inputlirc is a daemon which maps remote events as given to it by the driver to linux /dev/input/event*" system.

'''Attention Ubuntu 10.10 (Maverick Meerkat) users'''. There is currently a bug with using inputlirc with no workaround.See [[#Bugs and Workarounds]] for more details.

=== UDEV Setup ===
First you have to create an own udev rule to ensure, that your device nodes are always the same.

We get the physical address from ''/proc/bus/input/devices'':

cat /proc/bus/input/devices

the output is something like this:
<pre>
...
I: Bus=0000 Vendor=0000 Product=0000 Version=0000
N: Name="Streamzap PC Remote Infrared Receiver (0e9c:0000)"
P: Phys=usb-0000:00:06.0-1/input0
S: Sysfs=/devices/virtual/rc/rc0/input4
U: Uniq=
H: Handlers=kbd event4
B: EV=100003
B: KEY=3ff 0 0 0 fc000 1 0 0 0 0 18000 4180 c0000801 9e1680 0 0 0

...
</pre>

What we need are the values behind ''Phys=''. In my case it is '''usb-0000:00:06.0-1/input0'''

''Note: Do not worry about any second device appearing for the streamzap with a Phys= like'' '''/input0'''.

Now we write a new rules file for udev:

sudo nano /etc/udev/rules.d/10-irremote.rules

and put the following content in:
<pre>
SUBSYSTEM=="input",ATTRS{phys}=="usb-0000:00:06.0-1/input0",SYMLINK="input/irremote0"
</pre>

Now restart udev and trigger a new discovery:

sudo restart udev
sudo udevadm trigger

Under /dev/input should now be a symlink call irremote0:

ls /dev/input

=== Inputlirc Installation and Configuraiton ===

First you have to install inputlirc and lirc. '''Please note that here we only need the lirc package because it contains "irw" and other utils. Please do not configure it for the Streamzap PC Remote.'''

sudo apt-get update
sudo apt-get install inputlirc lirc

Then you need to configure it properly:

sudo nano /etc/default/inputlirc

and put the following content in:
<pre>
EVENTS="/dev/input/irremote0"
OPTIONS="-c -g -m 0"
</pre>

The entries under EVENTS are the devices we created via udev.
The OPTION entries mean the following:
{|
|-
!-g
|Grabs the input from the devices, specified under EVENTS, so that no other application interferes with it.
|-
!-m 0
|By default, all keycodes below 88 are filtered out. This setting ensures, that all keycodes are captured
|-
!-c
|Because some of the keys on the remote are mapped to keys with modifiers, this option maps this codes to single events.
|}

Now restart inputlirc
sudo /etc/init.d/inputlirc restart

You can now test the remote via 'irw':
irw /dev/lircd

This is some sample output from irw when pressing buttons:
<pre>
6a 0 KEY_RIGHT irremote0
6c 0 KEY_DOWN irremote0
160 0 KEY_OK irremote0
8b 0 KEY_MENU irremote0
ae 0 KEY_EXIT irremote0
191 0 KEY_BLUE irremote0
18e 0 KEY_RED irremote0
</pre>

''Note: You may see '''/dev/input/irremote0''' instead of '''irremote0'''. If so, that is name '''inputlirc''' knows it as and is what you will need to put XBMC's '''Lircmap.xml''' instead of just '''irremote0'''.

=== Configuring XBMC ===
The last thing you need to do is let XBMC know to what buttons to respond. This is done by editing a LIRC Map for XBMC.

nano -w ~/.xbmc/userdata/Lircmap.xml

and pasting in the following:
<pre>
<lircmap>
<remote device="irremote0">
<play>KEY_PLAY</play>
<pause>KEY_PAUSE</pause>
<stop>KEY_STOP</stop>
<forward>KEY_FASTFORWARD</forward>
<reverse>KEY_REWIND</reverse>
<left>KEY_LEFT</left>
<right>KEY_RIGHT</right>
<up>KEY_UP</up>
<down>KEY_DOWN</down>
<pageplus>KEY_CHANNELUP</pageplus>
<pageminus>KEY_CHANNELDOWN</pageminus>
<select>KEY_OK</select>
<back>KEY_EXIT</back>
<menu>KEY_MENU</menu>
<title>KEY_RED</title>
<info>KEY_GREEN</info>
<skipplus>KEY_FORWARD</skipplus>
<skipminus>KEY_BACK</skipminus>
<display>KEY_YELLOW</display>
<record>KEY_RECORD</record>
<volumeplus>KEY_VOLUMEUP</volumeplus>
<volumeminus>KEY_VOLUMEDOWN</volumeminus>
<mute>KEY_MUTE</mute>
<record>KEY_RECORD</record>
<power>KEY_POWER</power>
<blue>KEY_BLUE</blue>
<one>KEY_NUMERIC_1</one>
<two>KEY_NUMERIC_2</two>
<three>KEY_NUMERIC_3</three>
<four>KEY_NUMERIC_4</four>
<five>KEY_NUMERIC_5</five>
<six>KEY_NUMERIC_6</six>
<seven>KEY_NUMERIC_7</seven>
<eight>KEY_NUMERIC_8</eight>
<nine>KEY_NUMERIC_9</nine>
<zero>KEY_NUMERIC_0</zero>
</remote>
</lircmap>
</pre>

[[Category:Remotes]]
[[Category:How-to]]

{{rename media|HOW-TO:Set up Streamzap PC Remote for Linux|Spelling/grammar error, i.e. 'setup' is a noun, 'set up' is a verb, and 'set up' is correct here}}

HOW-TO:Set up LIRC

2014-10-13T17:29:40Z

Slvr32: Spelling/grammar error, setup vs set up

{{cleanup}}

This guide explains how to set up xbmc to understand a universal remote's commands (so not the standard MCE remotes that work out of the box). You obviously need some hardware device for this that reads infrared commands. I'm using a cheap (+- 10 euro) device called the IRMan. You can find a list of supported devices [http://www.lirc.org/html/table.html here].

== Download and install Lirc ==
First you have to download and install Lirc. If you're using Ubuntu or Debian you can just type '''apt-get install lirc'''. If you don't have a lirc package in you distribution or (in my case) a buggy version, it's pretty easy to compile lirc from source:

user@computer:~$ wget http://prdownloads.sourceforge.net/lirc/lirc-0.8.4a.tar.bz2
user@computer:~$ tar -jxf lirc-0.8.4a.tar.bz2
user@computer:~$ cd lirc-0.8.4a
user@computer:~/lirc-0.8.4a$ aclocal && autoheader && autoconf
user@computer:~/lirc-0.8.4a$ ./configure --with-x --with-driver=irman (or whatever remote you are using, check ./configure --help for supported ones - for homebrew serial IR use --driver=serial)
user@computer:~/lirc-0.8.4a$ make && sudo make install

Next comes the interesting part.

== Configure Lirc to understand your remote's commands ==
You have downloaded and installed Lirc and are now ready to set it up. First, check if your IR receiver is already preconfigured. Ubuntu stores the configuration files in '''/usr/share/lirc/remotes'' but you can also find them in the source tree in the remotes directory. If you can find you remote, copy the config file to /etc/lirc/lircd.conf and open the file with a text editor. Delete the lines between ''begin codes'' and ''end codes''.

=== Learning Commands ===
Now we're going to learn commands. Fire up '''irrecord''' with the following command:
user@computer:~$ sudo -s ## you have to be root for this part
[sudo] password for user:
root@computer:~# cd /etc/lirc
root@computer:/etc/lirc# irrecord --driver=irman --device=/dev/ttyS0 MyRemote ## use the driver that you chose in the previous part. /dev/ttyS0 = first com port

You'll get a wall of text and are asked to press enter. Next you'll see a prompt.
Hold down an arbitrary button.
Just hold down any button on your remote until the next prompt.
Found gap length: 215947
Now enter the names for the buttons.
Now you have to learn all buttons. Enter a name, press enter, hold down the button you are learning and repeat. When you're done, press enter. Press one button on your remote as fast as possible but DO NOT hold it down.

=== Testing the new lirc configuration ===
Next we're going to test the config file we just created. Start lirc with the following command:
root@computer:/etc/lirc# lircd --driver=irman --device=/dev/ttyS0 /etc/lirc/MyRemote
You can test your config by starting irw:
root@computer:/etc/lirc# irw
Press the buttons on your remote you just learned and see if they match. Press ctrl+c to quit irw. If there's a problem, stop lirc with
root@computer:/etc/lirc# killall lircd
delete the file we just created
root@computer:/etc/lirc# rm -f MyRemote
and repeat the whole learning process back from the top. If it still doesn't work, have a look at [http://www.lirc.org/html/help.html#new_remote this site] or ask on the forums.

=== Make the changes to lirc ===
If ''irw'' gave the right output, stop lirc with
root@computer:/etc/lirc# killall lircd
and move the file we created to lircd.conf
root@computer:/etc/lirc# mv MyRemote lircd.conf
Finally start up lirc with
root@computer:/etc/lirc# /etc/init.d/lircd start
You can now leave your root shell.

== Configure XBMC to understand Lirc's commands ==
So now that you configured lirc and ''irw'' gives the expected output, it's time to let lirc talk to XBMC. Start your text editor and open the file named '''Lircmap.xml''', which is usually located in '''$home$/.xbmc/userdata/''' and the generic is on '''/usr/share/xbmc/system/'''.
There are some remotes in there by default. Copy the part between
<remote device="mceusb"> ... </remote>
and paste it in the file. Change the new ''mceusb'' to ''MyRemote'' (or whatever name you picked for your remote in the lirc configuration) and change the values of the tags to the names of the buttons. If you forgot them, they are in /etc/lirc/lircd.conf.

The '''Lircmap.xml''' configuration is explained in more detail in [http://forum.xbmc.org/showthread.php?t=45972 this forum post]

== It works :) ==

remember order to use lirc on xbmc (generic for ubuntu)
first install modules
then compiling lirc
then setting remote

== Changes in Linux IR ==

With kernel 2.6.35 some changes began to be made in the way Linux handles infrared remotes. What used to be a job just for LIRC is now partly done by the Linux kernel. Some distributions 'backport' changes to the kernel, so even though your kernel is older than 2.6.35 it might affect you.

The drivers for several remotes have been moved into the kernel and this means that many of them should 'Just Work' out of the box. Unfortunately LIRC, the LIRC configuration tools, the distribution setup scripts for LIRC and most of the documentation available has not yet (as of February 2011) been updated to reflect these changes.
If you are experiencing problems, your remotedriver may have been moved to the kernel. In this case, try to setup LIRC with 'devinput' as the driver (and something like /dev/input/event3 as the device).
Further reading:
[http://wilsonet.com/?page_id=95 Linux 2.6.35+ Remote Control Overview]
[http://wilsonet.com/?cat=11 What’s new in IR?]
[http://lirc.org/html/devinput.html Linux input layer driver]

[[Category:How-to|Lirc]]
[[Category:Linux]]
[[Category:XBMCbuntu]]
[[Category:Remotes]]

{{rename media|HOW-TO:Set up Lirc|Spelling/grammar error, i.e. 'setup' is a noun, 'set up' is a verb, and 'set up' is correct here}}

HOW-TO:Set up an MCE remote control in Linux

2014-10-13T17:28:44Z

Slvr32: Spelling/grammar error, setup vs set up

This guide will help to configure an MCE Remote on a linux HTPC, even if all the commands are specific to Ubuntu, the main steps are the same on any modern linux distribution.

MCE remotes are IR remotes that split into two main categories:
*MCE remotes that send keystrokes
*Windows remotes also known as RC6 or eHome remotes

Most remotes work out of the box through the kernel input event subsystem. However they are often unusable in this state due to laggy/buggy behavior.
On Linux it is often easier to use the [http://www.wikipedia.org Lirc] package.

== Install the remote ==
=== Simple Installation method with Lircd ===

The easiest way is to use the lircd daemon shipped with lirc package.

In terminal, use the following command:
<pre>apt-get install -y lirc</pre>

After the installation a configuration dialog will appear on Ubuntu.
Choose the correct values corresponding to your receiver (and eventually transmitter)

you can now test if the correct value are send by the remote buttons by using the <code>irw</code> command tool and then launch XBMC and check if the main button are responding correctly.

You can always reconfigure the lirc package with the dpkg-reconfigure command:
<pre>dpkg-reconfigure lirc</pre>

If the remote don't work it is always a good idea to reconfigure lirc package by choosing one of those 2 generic value for the receiver option :
*Windows Media Center Transceivers/Remotes (all)
*Linux input layer (/dev/input/eventX)

a more complete guide is available here : [[HOW-TO:Setup_Lirc|HOW-TO: Setup Lirc]]

=== Alternative Installation method using InputLirc ===

In some cases the simple method will work in a buggy way (keys pressed twice, key burst, laggy key, ... ).
If this is the case or you want deeper control over the configuration then use inputlirc.
Inputlirc is a small LIRC-compatible daemon that reads from /dev/input/eventX devices and sends the received keycodes to connecting LIRC clients.

*It is important to disable lircd daemon from lirc package, On ubuntu launch the lirc reconfiguration process with :
<pre>dpkg-reconfigure lirc</pre>
Then choose twice none for receiver and transmitter.

Make sure that lircd is not running. The START_LIRCD parameter should be now set to false in /etc/lirc/hardware.conf configuration file.

*Install now inputlirc :
sudo apt-get install inputlirc

*Before proceeding we need to know the eventX number corresponding to our remote :
<pre>cat /proc/bus/input/devices</pre>

For instance on my xtreamer ultra V1, the nuvoton receiver remote correspond to event4
<pre>cI: Bus=0019 Vendor=1050 Product=00c3 Version=0033
N: Name="Nuvoton w836x7hg Infrared Remote Transceiver"
P: Phys=nuvoton/cir0
S: Sysfs=/devices/pnp0/00:09/rc/rc0/input4
U: Uniq=
H: Handlers=kbd event4
...</pre>

*As the eventX number may sometimes varry upon reboot, one need to know a unique id value corresponding to our remote to further create a udev rule :
<pre>udevadm info -a -p $(udevadm info -q path -n /dev/input/event4)</pre>
For the nuvoton, the ATTRS(id) will be used from the following output
<pre>looking at device '/devices/pnp0/00:09/rc/rc0/input4/event4':
KERNEL=="event4"
SUBSYSTEM=="input"
DRIVER==""

looking at parent device '/devices/pnp0/00:09/rc/rc0/input4':
KERNELS=="input4"
SUBSYSTEMS=="input"
DRIVERS==""
ATTRS{name}=="Nuvoton w836x7hg Infrared Remote Transceiver"
ATTRS{phys}=="nuvoton/cir0"
ATTRS{uniq}==""
ATTRS{properties}=="0"

looking at parent device '/devices/pnp0/00:09/rc/rc0':
KERNELS=="rc0"
SUBSYSTEMS=="rc"
DRIVERS==""
ATTRS{protocols}=="rc-5 nec [rc-6] jvc sony mce_kbd lirc"

looking at parent device '/devices/pnp0/00:09':
KERNELS=="00:09"
SUBSYSTEMS=="pnp"
DRIVERS=="nuvoton-cir"
ATTRS{options}=="
ATTRS{id}=="NTN0530"

looking at parent device '/devices/pnp0':
KERNELS=="pnp0"
SUBSYSTEMS=="
DRIVERS=="</pre>

*One can now create a permanent symbolic link to our eventX device by creating a custom udev rule :
<pre>echo 'KERNEL=="event*",ATTRS{id}=="NTN0530",SYMLINK="input/myremote"' > /etc/udev/rules.d/10-persistent-ir.rules</pre>

Reload the udev configuration and trigger these changes :
<pre>
/etc/init.d/udev reload
udevadm trigger</pre>
Aternatively, reboot in order to apply the udev changes.

There should now be a symbolic link in /dev/input/myremote

*Configure inputlirc by editing /etc/default/inputlirc like this :
<pre>EVENTS="/dev/input/myremote"
OPTIONS="-g -m 0 -c"</pre>

*Restart inputlirc
<pre>/etc/init.d/inputlirc stop
/etc/init.d/inputlirc start</pre>

*Copy the LircMap configuration file into the personal directory
<pre>cp /usr/share/xbmc/system/Lircmap.xml ~/.xbmc/userdata/Lircmap.xml</pre>

*Edit the linux-input-layer remote section to add the remote link name, one should have something like this :
<pre><remote device="linux-input-layer">
<altname>cx23885_remote</altname>
<altname>devinput</altname>
<altname>/dev/input/myremote</altname>
<left>KEY_LEFT</left>
...</pre>

*Launch xbmc and test the working remote

Based on : [http://www.mobidyc.net/2012/09/xtreamer-ultra-ubuntu-12-04/]

== Configure the remote buttons ==
=== Edit the driver table ===

If you are using inputlirc or lircd with the <code>Linux input layer (/dev/input/eventX)</code> value for the receiver parameter, you can tweak the driver keycode/scancode table with the ir-keytable command line tool.
In the following example one will make some changes on the driver table used by the nuvoton remote shipped with the Xtreamer Ultra V1. This example can be adapted to any remote.

By default, after using the inputlirc method on ubuntu 13.04, the subtitle, tilte and enter button are mapped like this for this remote on this HTPC :
<pre>subtitle => KEY_TITLE
title => no key code sent
enter => no key code sent</pre>

One will change the driver table to map those 3 buttons like this :
<pre>subtitle => KEY_SUBTITLE
title => KEY_TITLE
enter => KEY_SELECT</pre>

*First install the ir-keytable package
<pre>apt-get install ir-keytable</pre>

*Stop or kill any lirc daemon (inputlircd or lircd)
<pre>pkill lirc</pre>

*Launch ir-keytable in test mode for the remote and read the scancode sent by pressing the buttons :
<pre>ir-keytable -t --device=/dev/input/myremote</pre>

The output looks like this :
<pre>
Testing events. Please, press CTRL-C to abort.
1378830829.479887: event MSC: scancode = 800f044d
1378830829.479887: event sync
1378830829.728814: event key up: KEY_TITLE (0x0171)
1378830829.728814: event sync
1378830833.290068: event MSC: scancode = 800f0451
...
1379288588.428518: event MSC: scancode = 800f0437
1379288588.428518: event sync
...</pre>

By analyzing the ouput, one can determine the the button/scancode association :
<pre>subtitle => 800f044d
title => 800f0451
enter =>800f0437</pre>

*Dump the driver table into /etc/lirc/myirtable.cfg
<pre>ir-keytable -r --device=/dev/input/myremote > /etc/lirc/myirtable.cfg</pre>

*Analyse the table file and grep the line corresponding to KEY_TITLE, KEY_SUBTITLE and KEY_SELECT
<pre>scancode 0x800f044d = KEY_TITLE (0x171)
scancode 0x800f045a = KEY_SUBTITLE (0x172)</pre>

As you can see, KEY_SELECT is not associated to any scancode, KEY_TITLE is associated to the subtitle button scancode and KEY_SUBTITLE is associate to a non existent scancode.

*Before procedding, it is necessary to know the key hex value associated to KEY_SELECT

Those are located in the kernel source code in include/uapi/linux/input.h file.
One can browse the source code here : [https://github.com/torvalds/linux/blob/master/include/uapi/linux/input.h]

<pre>#define KEY_SELECT 0x161</pre>

*Edit the table file dumped before to have this button key association :
<pre>subtitle => 800f044d => KEY_SUBTITLE (0x172)
title => 800f0451 => KEY_TITLE (0x171)
enter =>800f0437 => KEY_SELECT (0x161)</pre>

after modifying the KEY_TITLE,KEY_SUBTITLE lines and adding the KEY_SELECT line the edited part should look like this :
<pre>scancode 0x800f044d = KEY_SUBTITLE (0x172)
scancode 0x800f0451 = KEY_TITLE (0x171)
scancode 0x800f0437 = KEY_SELECT (0x161)</pre>

*Make sure with your favorite tool that there isn't two lines with the same scancode fot those buttons in the file and save it.

*Clear the driver table and update it with the table file :
<pre>ir-keytable -c --device=/dev/input/myremote
ir-keytable --device=/dev/input/myremote --write=/etc/lirc/myirtable.cfg
Wrote 63 keycode(s) to driver</pre>

*To make the changes persistent upon reboot add those 2 last command above to /etc/rc.local

*One can now test if everything works correctly with ir-keytable test mode, then restart inputlirc or lircd and launch xbmc

=== Edit LircMap.xml and Keyboard.xml===

First thing to do is to check the LircMap.xml located in ~/.xbmc/userdata/Lircmap.xml.

One can acquire the button key values with the help of irw and then edit this file to better suits our needs.
This can even be mandatory sometimes.

For instance some remotes will send KEY_NUMERIC_1 instead of KEY_1 for the numeric pad. It is then necessary to edit the file at the correponding remote section from
<pre><one>KEY_1</one></pre>
to
<pre><one>KEY_NUMERIC_1</one></pre>

A complete guide is available here : [[Userdata/lircmap.xml]]

For further tweaking it is necessary to edit the Keyboard.xml file.
A complete guide is available here : [[Keymap]]

[[Category:Remotes]]
[[Category:XBMC Manual]]

{{rename media|HOW-TO:Set up an MCE remote control in Linux|Spelling/grammar error, i.e. 'setup' is a noun, 'set up' is a verb, and 'set up' is correct here}}

Archive:Set up CableCard with HDHomeRun UPnP

2014-10-13T17:27:24Z

Slvr32: Spelling/grammar issue with title, setup vs set up

{{editor note|Here's a very rough guide I wrote up for a user on the forums. Feel free to touch it up if I don't get to it soon and make it more generic and for more cable services, etc.}}

Here's an easy method of using XBMC, HDHomeRun Prime, and CableCard, to easily set up live TV for all of your XBMC boxes in HD. CableCard is a cable TV technology for the United States.

I got an HDHomeRun Prime. What's great about the Prime is that if you don't need to record, as you indicated, then you can easily set it up in XBMC by adding it as a UPnP source and no additional software or hardware.

Get an HDHomeRun Prime and then call up Comcast and find where a local customer service center is so that you can go and pick up a Cable Card. They'll charge you a small fee for picking it up or activating it or something, but the card itself should be free of monthly charges. In fact, I think they will give you a credit on your bill since you are providing your own tuner hardware (the Prime). Make sure to mention this, as sometimes people get mistakenly charged for the Cable Card, but the first one you get (that is not in Comcast branded hardware, so existing cable boxes don't count against this) should be free.

Go home and insert the card into the Prime. Sometime now, even before you get the Cable Card, be sure to go to http://silicondust.com and grab the latest firmware update, in case the firmware on the Prime doesn't already have the UPnP update. The Prime should also instruct you on how to load up the Prime's interface in a web browser, which will tell you some numbers off of the Cable Card that you will need to activate it. Comcast should also tell you which phone number to call to activate the card, which for some reason has to be done while it is in the Prime, so it can't be done when you pick up the card (which is silly, I know). Once activated, it should be able to scan for channels from the web interface, and you should see a bunch of them show up in a list.

In XBMC you can now simply add the Prime as a UPnP media source ( http://wiki.xbmc.org/index.php?title=UPnP/Media_source ). It's pretty basic and doesn't have a TV guide or anything, but it is possible to add those later if you wish. Here's a great YouTube video that also explains this process. In the video they use Raspberry Pis, but the process is the same for any XBMC install (except that in most cases you do not have to buy an MPEG2 codec license, so you can ignore that part): https://www.youtube.com/watch?v=kKpqmkpkyOA

XBMC can access channels that are "flagged" as "copy freely", which includes most Comcast/Xfinity channels. The only channels you can't access in XBMC are premium channels like HBO, Showtime, etc. There were one or two sports channels that also didn't work for me, but most sports channels did seem to work, like ESPN, Fox Sports, etc. You can still use those channels with the Prime, but they require a UPnP client that can work with "copy once" channels, like a PS3, or HDHomeRun's Android app.

[[Category:How-to]]
[[Category:Live TV]]

{{rename media|HOW-TO:Set up CableCard with HDHomeRun UPnP|Spelling/grammar error, i.e. 'setup' is a noun, 'set up' is a verb, and 'set up' is correct here}}

HOW-TO:Set up subtitle services

2014-10-13T17:24:25Z

Slvr32: Spelling/grammar issues with title, setup vs set up

{{mininav| [[Video library]] | [[Video playback|Playback]] | [[Subtitles]] }}
<section begin="intro" />Starting in XBMC v13 "Gotham" subtitles are now built into XBMC, and instead of downloading the subtitle download add-on, you install specific subtitle services.<section end="intro" />

{{Note|
* You have to use a pretty up-to-date skin or the new options won’t be implemented yet. To be safe work with confluence until you do this one-time setup.

* If you have bound a remote key to bring up the subtitle search window, you will need to update the [[keymap]] to use this instead: <code>ActivateWindow(subtitlesearch)</code>}}

== Steps ==
{{how-to
|Step1= [[File:GothamNewSubs1.png|right|500px]] From XBMC's home screen, go to {{highlight|bordered=yes|Settings -> Video -> Subtitles}}. There you will see the new subtitles settings.
| Step2= [[File:GothamNewSubs0a.png|right|500px]] [[File:GothamNewSubs0b.png|right|500px]]Select the languages you want to get when searching for subtitles. For the time being there is no way of selecting order (or main language for that matter) so the search results will be shown in whatever order your service of choice (we’ll come to that) decides it fits.
| Step3= [[File:GothamNewSubs1.png|right|500px]] Select either default Service for TV Episodes and Movies to select the default service or download extra services.
| Step4= [[File:GothamNewSubs2.png|right|500px]] Here you can select the default service to use. If the list is still empty you can hit the "Get more"button to download additional services.
| Step5= [[File:GothamNewSubs3.png|right|500px]] Here you see the available list of subtitle services to download. Simply click on it to install the currently selected. If no subtitle services show up in this list you need to do the following one time: [[Add-on_manager#Empty_repository_list]]. After that you can go back to step 1 and repeat the process.
| Step6= [[File:GothamNewSubs4.png|right|500px]] After you have installed several services you can select the default one to use.
| Step7= [[File:NewSubs4.jpg|right]] Each subtitles module might have additional settings (for example you have options to enter your login info in podnapisi). To change this you have to go to each service options through {{highlight|bordered=yes|Settings -> Add-ons -> Enabled Add-ons -> Subtitles -> select the service add-on -> Configure}}
}}

== Notes ==
*Credit goes to jurrabi for the original guide.

{{gotham updated}}

[[Category:Subtitles]]
[[Category:XBMC Manual]]
[[Category:How-to]]
[[Category:Add-ons]]
[[Category:Video library]]

{{rename media|HOW-TO:Set up subtitle services|Spelling/grammar error, i.e. 'Setup' is a noun, 'Set up' is a verb, and 'Set up' is correct here}}