Official Kodi Wiki - User contributions [en]

Add-on manager

2015-01-10T22:22:29Z

Sharrken:

{{mininav|[[Settings]]{{l2|[[Add-ons]]}} }}
<section begin="intro" />The ''Add-on manager's'' purpose is to manage the various add-ons to the {{kodi}} application. It can be browsed like any other section and the various installed/uninstalled, enabled/disabled add-ons. In the Add-on manager you can also change the settings for auto update, notifications and foreign filter by bringing up the slide in submenu (press left {{keypress|left}} to show/hide). The Add-on manager is not where you go to run add-ons, but only to install and configure them.<section end="intro" />

=== How to access the Add-on manager ===
From the ''home screen'', go to
;<big>{{highlight|System -> Add-ons|bordered=yes}}</big>
<gallery widths=500px heights=313px>
File:add-ons-accessing-1.png|'''Step 1:''' Select ''System'' on the ''home screen''.
File:add-ons-accessing-2.png|'''Step 2:''' Select ''Add-ons''.
File:add-ons-accessing-3.png|'''Step 3:''' The ''Add-on manager'', displaying four/five options (explained below).
</gallery>

'''Enabled add-ons''' are add-ons that are currently enabled. {{kodi}} comes with certain add-ons already installed and enabled (such as movie scrapers, screen-savers and visualisation)<br />
'''Disabled add-ons''' is not visible if you don't have any disabled add-ons. It shows add-ons you've manually disabled or that's been disabled by {{kodi}} because they're "marked as broken" in the repository.<br />
'''Get add-ons''' allows you to install new add-ons from the installed repositories. ''Kodi Add-on repository'' and ''Kodi PVR Add-on repository'' are the two official pre-installed add-on repositories. (see [[Unofficial repositories#How to install additional add-on repositories|How to install additional add-on repositories]] for more)<br />
'''Install from ZIP file''' allows the installation of an add-on or repository from a ZIP file, either from the hard drive or LAN.<br />
'''Search''' allows you to search add-ons in the installed repositories and your installed add-ons.

=== How to install add-ons from a repository ===
<section begin="HOW-TO install" />
For this example a skin is being installed, the same method is used for other add-ons.
;<big>{{highlight| Select ''Get Add-ons'' -> Select the repository -> Select the add-on category -> Select the add-on -> Select ''Install''|bordered=yes}}</big>
<gallery widths=500px heights=313px>
File:Installaddon1.png|'''Step 1:''' Select ''Get Add-ons''
File:Installaddon2.png|'''Step 2:''' Select the repository you want to install from.
File:Installaddon3.png|'''Step 3:''' Select the add-on category, in this case ''Skin''.
File:Installaddon4.png|'''Step 4:''' Select the add-on you want to install, in this case the skin ''Ace''.
File:Installaddon5.png|'''Step 5:''' A summary dialog will be brought up allowing you to see various properties of the add-on. Select ''Install'' to begin automatic downloading and installation.
File:Installaddon6.png|'''Step 6:''' In the case of skin installation you'll be asked if you want to change to the installed skin immediately.
</gallery>
When the add-on has finished downloading {{kodi}} will enable it and depending on the add-on ask if you want to start using it. Add-ons will then appear in their appropriate section (e.g. skins in the appearance section of settings, movie scrapers in the options of scrapers when adding a new movie source)
<section end="HOW-TO install" />
==== Empty repository list ====

[[File:Repo_refresh.png|500px|thumb|right|Force repository refresh]]If the repository list is empty or you are suspect you don't receive any add-on updates you can try fixing it with ''Force refresh''. Bring up the ''[[context menu]]'' when the ''repository is highlighted'' and select ''Force refresh''. This will re-download the list from the server and hopefully the add-ons will show. This should work for the default XBMC.org repositories or any 3rd party repository installed. Updating will take some time so be patient.<br /><br />

To try to fix an empty repository:
;<big>{{highlight| Highlight the repository -> Bring up the ''context menu'' -> Select ''Force refresh''|bordered=yes}}</big>

If the repository still remains empty after some time you can try to hard reset the database by removing addons**.db from the [[userdata]] folder.
{{-}}

=== How to install from a ZIP file ===
<section begin="HOW-TO zip" />
In this example the ''hybrid'' repository is being installed, but the method is the same for add-ons. First download the ZIP file, then:

;<big>{{highlight| Select ''Install from zip file'' -> Navigate to the ZIP file and select it|bordered=yes}}</big>
<gallery widths=500px heights=313px>
File:installing-repo-1.png|'''Step 1:''' Select ''Install from zip file''.
File:installing-repo-2.png|'''Step 2:''' Navigate to the ZIP file and select it.
File:installing-repo-3.png|'''Step 3:''' In the bottom right, {{subst:Name}} notifies when the add-on is installed and enabled.
File:installing-repo-4.png|'''Step 4:''' Select ''Get Add-ons''. The new repository is listed. In the case of add-ons they are added under ''All Add-ons'' in the appropriate category.
</gallery>
<section end="HOW-TO zip" />

== Repositories ==

Repositories are storage locations from where add-ons can be retrieved from. XBMC comes with two official add-on repositories installed by default, ''Kodi Add-on repository'' and ''Kodi PVR Add-on repository''. However others can be added.<br />
To install a new repository you must first find the ZIP file to install the repository, a list of [[3rd party add-on repositories]] is semi-maintained on the wiki - other repositories may exist. Then follow the instructions at [[Add-ons#How to install from a ZIP file|How to install from a ZIP file]].

== Updating ==
[[File:Add-on_manager-update.png|500px|right|thumb|Slide in submenu, with Add-on manager settings.]]
[[File:Installing-repo-3.png|500px|right|thumb|A notification that an add-on has been installed and enabled.]]
To manually update add-ons or change update settings, from the ''home screen'' go to the Add-on manager
;<big>{{highlight|bordered=yes|System -> Add-ons}}</big>

By default ''Auto update'' is enabled and all installed add-ons will be automatically updated when new versions are available from the repositories.

If you want to enable/disable auto-updates, while in the Add-on manager bring up the slide in submenu (press right {{keypress|right}} to show/hide) and enable/disable ''Auto update''.

If ''Auto update'' is turned ''off'' you should see a folder in the Add-on manager that says ''Available Updates'', where you can go in and one-by-one and update add-ons.

Installing an ''add-on'' from a ZIP file can lead to it not having a repository associated with it. Automatic or manual (using ''Available Updates'' folder) update will then not be available. You can of course manually update the add-on by downloading a ZIP file with the new version. If you later install the associated repository the add-on will be able to get automatically or manually updated.

Update/install ''notifications'', which can be toggled on/off in the submenu, will show up in the right bottom corner and will notify you that:
* a new version of an add-on is available, if you have ''Auto update'' '''disabled'''.
* an add-on has been updated, if you have ''Auto update'' '''enabled'''.
* an add-on has been enabled (only when installing a new add-on or when doing rollbacks).
* an installation has failed.
{{-}}

== Rollback ==
Rollback is a function to reinstall a previous version of an add-on. The reason to do this can be that you don't like the new version (e.g changed features) or that the new version introduced a bug.

Rollback is ''only'' available if you've had a previous version installed before getting the add-on manually or automatically updated. I.e. if you install a new add-on only the latest version will be installed, thus you can't rollback to any other version.

If you rollback from version B to A and version C is added to its repository the add-on will automatically get updated (if you have ''Auto update'' enabled) to version C and you'll have to rollback again to version A. To stop this from happening disable ''Auto update'' or uninstall the associated repository. The latter is not always practical or even possible, e.g. the official repositories.

To do a rollback, from the ''home screen'' go to the Add-on manager
;<big>{{highlight|bordered=yes|System -> Add-ons}}</big><br />
then
;<big>{{highlight|bordered=yes|Select ''Enabled Add-ons'' -> Select the category -> Select the add-on -> Select ''Rollback'' -> Select a previous version to reinstall }}</big>

<gallery widths=500px heights=313px>
File:Rollback1a.png|'''Step 1:''' Select ''Enabled Add-ons''.
File:Rollback1b.png|'''Step 2:''' Select the category.
File:rollback1.png|'''Step 3:''' Select the add-on.
File:rollback3.png|'''Step 4:''' Select ''Rollback''.
File:rollback4.png|'''Step 5:''' Select a previous version to reinstall.
</gallery>

== Force refresh ==
[[File:Repo_refresh.png|500px|thumb|right|Force repository refresh]]If the repository list is empty or you are suspect you don't receive any add-on updates you can try fixing it with ''Force refresh''. Bring up the ''[[context menu]]'' when the ''repository is highlighted'' and select ''Force refresh''. This will re-download the list from the server and hopefully the add-ons will show. This should work for the default XBMC.org repositories or any 3rd party repository installed. Updating will take some time so be patient.<br /><br />

To try to fix an empty or stale repository:
;<big>{{highlight| Highlight the repository -> Bring up the ''context menu'' -> Select ''Force refresh''|bordered=yes}}</big>

If the repository still remains empty after some time you can try to hard reset the database by removing addons**.db from the [[userdata]] folder.
{{-}}

== See also ==
* [[:Category:All add-ons]]
* [[3rd party add-on repositories]]
'''Development:'''
* [[Add-on development]]
* [[Python development]]
* [[Skinning]]
* [[Add-on repositories]]
* [[Official add-on repository]]
{{frodo updated}}

[[Category:Add-ons]]
[[Category:Settings]]
[[Category:Manual]]

Settings

2015-01-10T22:18:43Z

Sharrken: {{kodi}} name changes

{{mininav|[[General topics]]}}
<section begin="intro" />This section covers {{kodi}}'s various settings and where to find them.<section end="intro" />
__TOC__
== Settings levels ==
[[File:Confluence - settings level.jpg|400px|right]]
In XBMC v13 "Gotham" or later there are tiered settings levels. Each mode unlocks more settings, and is available by selecting the "Settings level" button, which will also display the currently used level.
{{-}}

== System settings ==
[[File:System settings.png|400px|right]]

Most of {{kodi}}'s global settings can be configured via the GUI (Graphical User Interface) under Settings (labeled "System" under the default skin, Confluence).

Choosing Settings from the Home Screen opens the Settings Window. In this window, you are able to configure {{kodi}}'s options:
{{-}}
{{Index two column
| image 1 = Crystal Clear app kcoloredit.png
| link 1 = Settings/Appearance
| link name 1 = Appearance
| image 2 = Video.svg
| link 2 = Settings/Videos
| link name 2 = Videos
| image 3 = Television.svg
| link 3 = Settings/Live TV
| link name 3 = Live TV
| image 4 = IYY logo.png
| link 4 = Settings/Music
| link name 4 = Music
| image 5 = Gnome-emblem-photos.svg
| link 5 = Settings/Pictures
| link name 5 = Pictures
| image 6 = Crystal Project kweather.png
| link 6 = Weather
| image 7 = Nuvola apps kthememgr.png
| link 7 = Add-on manager
| image 8 = Crystal Project Network Connection Manager.png
| link 8 = Settings/Services
| link name 8 = Services
| image 9 = Gnome-system-run.svg
| link 9 = Settings/System
| link name 9 = System
}}

== Additional settings ==
{{Index two column
| image 1 = Oxygen480-actions-media-playback-start.svg
| link 1 = Video playback
| link name 1 = Video OSD settings
| description 1 = Some video playback settings can (currently) only be accessed while playing a video back and accessing the on-screen-display. For more info see [[Video playback]]. These include subtitle and audio track selection, zoom (aspect ratio) options, and more.
| link 2 = Media sources
| description 2 = [[Media sources]] and [[scrapers]] control what files are listed in {{kodi}} and what is scanned into the library. These settings can also control what information is pulled from the internet.
| image 3 = Nuvola apps kthememgr.png
| link 3 = Add-ons#Add-on settings
| link name 3 = Add-on settings
| description 3 = {{#lst:Add-ons|settings}}
| image 4 = Gdm.png
| link 4 = Profiles
}}

== Advanced settings ==
{{main|advancedsettings.xml}}
{{#lst:advancedsettings.xml|intro}}

== Resetting {{kodi}} settings to default ==
{{see also|userdata}}
Delete your [[userdata]] folder to remove all {{kodi}} settings and library databases. Deleting some individual files/folders in the [[userdata]] folder will also selectively reset those settings.

== Other settings related pages ==
* [[Audio]]

{{gotham updated}}

[[Category:Settings|*]]
[[Category:Manual]]
[[Category:General topics]]
[[Category:Index]]

MySQL/Advanced notes

2015-01-10T22:11:53Z

Sharrken: /* Windows */ Kodi name changes, some consistency edits

{{:MySQL/Contents}}
{{mininav| [[MySQL]] }}
__TOC__
{{-}}
==advancedsettings.xml==
For a full listing of the advancedsettings.xml parameters, see [[advancedsettings.xml#<musicdatabase>/<videodatabase>]]

==MySQL speed-up tweaks==
From: [http://xbmcstuff.bossanova808.net/2011/03/summary-of-xbmc-mysql-database.html?m=1 MySQL speed-up tweaks for XBMC]. For XBMC v11 (Eden) only the first two tweaks are necessary. See Comments for more information.
=== In advancedsettings.xml: ===
Use the IP address and NOT the hostname of your MySQL server

=== In my.ini: ===
(add to mysqld section)
skip-name-resolve

==Automated Backup ==
=== Windows ===
This will allow you to make a regular backup of your MySQL database using the schedule of your choosing and saving the backups for however many days you choose. Recommend performing daily backups and saving for a minimum of 7 days. This will give you enough time to discover a problem with the DB and restore to a previous version that did not have problems.

To begin, go ahead and download the [http://www.7-zip.org/download.html command line version of 7zip]. We will use this to compress our MySQL dumps. Create a new folder in your C directory named KODISQLBACKUP. So you should have a C:\KODISQLBACKUP\ location now. In this location, create another new folder and name it zip. So you should now have C:\KODISQLBACKUP\zip. Extract the contents of the 7zip download to this location. Once complete you should have:
<br>
<pre>C:\KODISQLBACKUP\zip\7za.exe

C:\KODISQLBACKUP\zip\7-zip.chm

C:\KODISQLBACKUP\zip\license.txt

C:\KODISQLBACKUP\zip\readme.txt</pre>

We're going to create a down and dirty batch file to perform the actual backup, then we'll execute the batch script with the task scheduler built into Windows. For the purpose of these instructions, it is assumed that you are running MySQL 5.5 installed to the default location. If not, be sure to adjust your path(s) accordingly. It's also a good idea to save your backups to a network location to protect against local drive failure, so the paths here will reflect this. So here are the batch file contents:

<syntaxhighlight lang="winbatch" enclose="div">
:: All lines that start with 2 colons are comments, they do not affect the script itself. These comments are explanations of each command, as well as instructions for the things that you will need to edit. Pay close attention to all comments.

:: These lines do not NEED to be edited
set year=%DATE:~10,4%
set day=%DATE:~7,2%
set mnt=%DATE:~4,2%
set hr=%TIME:~0,2%
set min=%TIME:~3,2%

IF %day% LSS 10 SET day=0%day:~1,1%
IF %mnt% LSS 10 SET mnt=0%mnt:~1,1%
IF %hr% LSS 10 SET hr=0%hr:~1,1%
IF %min% LSS 10 SET min=0%min:~1,1%

set backuptime=%mnt%-%day%-%year%-%hr%-%min%

:: User name for DB - NOTE that root credentials are needed for this script.
set dbuser=root

:: User password - NOTE that the root credentials are needed for this script.
set dbpass=password

:: Path to location where you would like to save the errors log file. For simplicity, I keep mine in the same location as the backups.
set errorLogPath="\\REMOTE\KODI_Database\backups\dumperrors.txt"

:: We need to switch to the data directory to enumerate the folders
pushd "C:\ProgramData\MySQL\MySQL Server 5.5\data"

:: We will dump each database to it's own .sql so you can easily restore ONLY what is needed in the future. We're also going to skip the performance_schema db as it is not necessary.

FOR /D %%F IN (*) DO (

IF NOT [%%F]==[performance_schema] (
SET %%F=!%%F:@002d=-!
"C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqldump.exe" --user=%dbuser% --password=%dbpass% --databases --routines --log-error=%errorLogPath% %%F > "\\REMOTE\KODI_Database\backups\%%F.%backuptime%.sql"
) ELSE (
echo Skipping DB backup for performance_schema
)
)

::Now to zip all of the .sql files in this folder and move the resulting .zip files to our network location.

"c:\KODISQLBACKUP\zip\7za.exe" a -tzip "\\REMOTE\KODI_Database\backups\FullBackup.%backuptime%.zip" "\\REMOTE\KODI_Database\backups\*.sql"

::Now we'll delete the unzipped .sql files

del "\\REMOTE\KODI_Database\backups\*.sql"

::Now we'll delete all zip files older than 30 days. You can adjust the number of days to suit your needs, simply change the -30 to whatever number of days you prefer. Be sure you enter the path to your backup location.
Forfiles -p \\REMOTE\KODI_Database\backups\ -s -m *.* -d -30 -c "cmd /c del /q @path"

popd
</syntaxhighlight>

Save this as Kodibackup.bat at C:\KODISQLBACKUP
Make ''sure'' you include the .bat at the end.

After you have edited the above batch file to reflect your paths and saved it as a batch file, all that is left is scheduling it to run. Daily backups are best, but you can use whatever frequency you are comfortable with. To do this, open up the Windows Task Scheduler.

In the Task Scheduler click on "Create Task...", NOT "Create Basic Task...". In the new task window, in the Name box put Kodi MySQL backup (or whatever name you want).

Then click on the Triggers tab, followed by the New button. Select Daily (or whatever you want) and adjust the time you would like it to run. Click OK.

Click on the Actions tab and click New. In the Program/Script box enter C:\KODISQLBACKUP\Kodibackup.bat (or whatever you named your batch file) and in the start in box enter C:\KODISQLBACKUP

Click ok, then click ok in the task window. In the main task scheduler window, right click on the task you just created and select run. If everything works as it should, you should now have a zipped backup of your database(s) in your backup location. It will now do this for you automatically.

Enjoy!

=== Linux ===
[http://sourceforge.net/projects/automysqlbackup/ AutoMySQLBackup] is a script that is designed to keep daily, weekly and monthly backups of your databases. It is very customizable and reliable. There is useful information on installing and configuring the script here: http://www.linux.com/learn/tutorials/659107-how-to-do-painless-mysql-server-backups-with-automysqlbackup.
{{note|Detailed instructions on configuring AutoMySQLBackup should probably be added to this section as the linked page above could be deleted at any time and there is little beginner friendly information available on the web.}}

==Name tag==
{{#lst:MySQL/Setting up XBMC|name tag}}

==Multiple profiles with one MySQL database==
See: http://forum.xbmc.org/showthread.php?tid=81095&pid=840499#pid840499

{{Gotham updated}}

MySQL/Advanced notes

2015-01-10T22:05:58Z

Sharrken: /* MySQL speed-up tweaks */

{{:MySQL/Contents}}
{{mininav| [[MySQL]] }}
__TOC__
{{-}}
==advancedsettings.xml==
For a full listing of the advancedsettings.xml parameters, see [[advancedsettings.xml#<musicdatabase>/<videodatabase>]]

==MySQL speed-up tweaks==
From: [http://xbmcstuff.bossanova808.net/2011/03/summary-of-xbmc-mysql-database.html?m=1 MySQL speed-up tweaks for XBMC]. For XBMC v11 (Eden) only the first two tweaks are necessary. See Comments for more information.
=== In advancedsettings.xml: ===
Use the IP address and NOT the hostname of your MySQL server

=== In my.ini: ===
(add to mysqld section)
skip-name-resolve

==Automated Backup ==
=== Windows ===
This will allow you to make a regular backup of your MySQL database using the schedule of your choosing and saving the backups for however many days you choose. Recommend performing daily backups and saving for a minimum of 7 days. This will give you enough time to discover a problem with the DB and restore to a previous version that did not have problems.

To begin, go ahead and download the [http://www.7-zip.org/download.html command line version of 7zip]. We will use this to compress our MySQL dumps. Create a new folder in your C directory named XBMCSQLBACKUP. So you should have a C:\XBMCSQLBACKUP\ location now. In this location, create another new folder and name it zip. So you should now have C:\XBMCSQLBACKUP\zip. Extract the contents of the 7zip download to this location. Once complete you should have:
<br>
<pre>C:\XBMCSQLBACKUP\zip\7za.exe

C:\XBMCSQLBACKUP\zip\7-zip.chm

C:\XBMCSQLBACKUP\zip\license.txt

C:\XBMCSQLBACKUP\zip\readme.txt</pre>

We're going to create a down and dirty batch file to perform the actual backup, then we'll execute the batch script with the task scheduler built into Windows. For the purpose of these instructions, it is assumed that you are running MySQL 5.5 installed to the default location. If not, be sure to adjust your path(s) accordingly. It's also a good idea to save your backups to a network location to protect against local drive failure, so the paths here will reflect this. So here are the batch file contents:

<syntaxhighlight lang="winbatch" enclose="div">
:: All lines that start with 2 colons are comments, they do not affect the script itself. These comments are explanations of each command, as well as instructions for the things that you will need to edit. Pay close attention to all comments.

:: These lines do not NEED to be edited
set year=%DATE:~10,4%
set day=%DATE:~7,2%
set mnt=%DATE:~4,2%
set hr=%TIME:~0,2%
set min=%TIME:~3,2%

IF %day% LSS 10 SET day=0%day:~1,1%
IF %mnt% LSS 10 SET mnt=0%mnt:~1,1%
IF %hr% LSS 10 SET hr=0%hr:~1,1%
IF %min% LSS 10 SET min=0%min:~1,1%

set backuptime=%mnt%-%day%-%year%-%hr%-%min%

:: User name for DB - NOTE that root credentials are needed for this script.
set dbuser=root

:: User password - NOTE that the root credentials are needed for this script.
set dbpass=password

:: Path to location where you would like to save the errors log file. For simplicity, I keep mine in the same location as the backups.
set errorLogPath="\\REMOTE\XBMC_Database\backups\dumperrors.txt"

:: We need to switch to the data directory to enumerate the folders
pushd "C:\ProgramData\MySQL\MySQL Server 5.5\data"

:: We will dump each database to it's own .sql so you can easily restore ONLY what is needed in the future. We're also going to skip the performance_schema db as it is not necessary.

FOR /D %%F IN (*) DO (

IF NOT [%%F]==[performance_schema] (
SET %%F=!%%F:@002d=-!
"C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqldump.exe" --user=%dbuser% --password=%dbpass% --databases --routines --log-error=%errorLogPath% %%F > "\\REMOTE\XBMC_Database\backups\%%F.%backuptime%.sql"
) ELSE (
echo Skipping DB backup for performance_schema
)
)

::Now to zip all of the .sql files in this folder and move the resulting .zip files to our network location.

"c:\XBMCSQLBACKUP\zip\7za.exe" a -tzip "\\REMOTE\XBMC_Database\backups\FullBackup.%backuptime%.zip" "\\REMOTE\XBMC_Database\backups\*.sql"

::Now we'll delete the unzipped .sql files

del "\\REMOTE\XBMC_Database\backups\*.sql"

::Now we'll delete all zip files older than 30 days. You can adjust the number of days to suit your needs, simply change the -30 to whatever number of days you prefer. Be sure you enter the path to your backup location.
Forfiles -p \\REMOTE\XBMC_Database\backups\ -s -m *.* -d -30 -c "cmd /c del /q @path"

popd
</syntaxhighlight>

Save this as XBMCbackup.bat at C:\XBMCSQLBACKUP
Make ''sure'' you include the .bat at the end.

After you have edited the above batch file to reflect your paths and saved it as a batch file, all that is left is scheduling it to run. Daily backups are best, but you can use whatever frequency you are comfortable with. To do this, open up the Windows Task Scheduler.

In the Task Scheduler click on "Create Task...", NOT "Create Basic Task...". In the new task window, in the Name box put XBMC MySQL backup (or whatever name you want).

Then click on the Triggers tab, followed by the New button. Select Daily (or whatever you want) and adjust the time you would like it to run. Click OK.

Click on the Actions tab and click New. In the Program/Script box enter C:\XBMCSQLBACKUP\xbmcdump.bat (or whatever you named your batch file) and in the start in box enter C:\XBMCSQLBACKUP

Click ok, then click ok in the task window. In the main task scheduler window, right click on the task you just created and select run. If everything works as it should, you should now have a zipped backup of your database(s) in your backup location. It will now do this for you automatically.

Enjoy!

=== Linux ===
[http://sourceforge.net/projects/automysqlbackup/ AutoMySQLBackup] is a script that is designed to keep daily, weekly and monthly backups of your databases. It is very customizable and reliable. There is useful information on installing and configuring the script here: http://www.linux.com/learn/tutorials/659107-how-to-do-painless-mysql-server-backups-with-automysqlbackup.
{{note|Detailed instructions on configuring AutoMySQLBackup should probably be added to this section as the linked page above could be deleted at any time and there is little beginner friendly information available on the web.}}

==Name tag==
{{#lst:MySQL/Setting up XBMC|name tag}}

==Multiple profiles with one MySQL database==
See: http://forum.xbmc.org/showthread.php?tid=81095&pid=840499#pid840499

{{Gotham updated}}

MySQL/Portable devices and profiles

2015-01-10T22:05:11Z

Sharrken: /* Configure the MySQL profile */ {{kodi}} name changes

{{:MySQL/Contents}}
{{mininav| [[MySQL]] }}
If you use your device (notebook or mobile iOS device) in multiple situations, you can create multiple profiles. You can use one profile at home, using a central MySQL database and another profile for use when travelling.

First create two profiles. Configure one profile for "local use" (internal HDD only, while traveling, etc) and another for using a central database. You can even make profiles for different wifi networks that have different centralized databases (your home, a friend's home, etc).

== Create profiles ==
{{main|Profiles}}
#Configure the Master User profile:
## Open the Profile settings
## Modify the Master User profile
## Rename the profile, for example "Portable"
#Configure the Second profile:
## Create a new profile
## Enter a name for the second profile, for example "Home"
## Accept the default profile path
## Select "Separate" for "Media info" and "Media sources"
# Enable the login screen to select a profile on startup

== Configure the MySQL profile ==
Create a new file "advancedsettings.xml" in [[userdata]]/profiles/<username>/:
<pre><nowiki>
<advancedsettings>
<videodatabase>
<type>mysql</type>
<host>***.***.***.***</host>
<port>3306</port>
<user>kodi</user>
<pass>kodi</pass>
</videodatabase>

<musicdatabase>
<type>mysql</type>
<host>***.***.***.***</host>
<port>3306</port>
<user>kodi</user>
<pass>kodi</pass>
</musicdatabase>
</advancedsettings>
</nowiki></pre>

See [[MySQL/Setting up XBMC|Setting up XMBC]] for more information.

{{Gotham updated}}

MySQL/Setting up Kodi

2015-01-10T22:03:03Z

Sharrken:

{{: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 {{kodi}} devices by sharing them on the network through file sharing. {{kodi}} 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 {{kodi}} device.
*Do not use mapped drives on the OS-level, as {{kodi}} 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 {{kodi}} 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 {{kodi}}.

==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 {{kodi}}.}}

{{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 {{kodi}} 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 {{kodi}} install you want to sync with.
{{-}}

==Importing==
At this point {{kodi}} 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, {{kodi}} behaves exactly like it would as if it had a local database, except that database is on the MySQL server and multiple installs can access that single database.

# Open any of your 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 {{kodi}} and scan it in as if you were setting up your library for the first time (see [[adding videos to the library]]). However, {{kodi}} 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 {{kodi}}'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 devices and the library for all of them will stay in sync.

== Adding new {{kodi}} 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 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 device then it should work on all of them, as they are basically sharing the same "brain".

If you however used a metadata collector add-on ([[scraper]]) that does not ship by default with new installations, such as the [[Add-on:Universal Movie Scraper|Universal Movie Scraper]] you will not be able to display the [[Video_navigation#Media_information_screen|media information screen]] on the new {{kodi}} device. To fix that you need to install the same metadata collector add-on on the new device.

==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. {{kodi}} 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 {{kodi}} 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 {{kodi}} leading to the library functionality not working at all. In other words, don't use <code><name>Kodi</name></code> for both music and videos, but instead use something like <code><name>Kodi-music</name></code> and <code><name>Kodi-video</name></code>.}}

{{Gotham updated}}

MySQL/Setting up MySQL

2015-01-10T22:01:58Z

Sharrken: {{kodi}} name changes

{{: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 'kodi' IDENTIFIED BY 'kodi';</code> and press return
##Type in: <code>GRANT ALL ON *.* TO 'kodi';</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 'kodi' IDENTIFIED BY 'kodi';</code> and press return
##Type in: <code>GRANT ALL ON *.* TO 'kodi';</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 'kodi' IDENTIFIED BY 'kodi';</code> and press return
##Type in: <code>GRANT ALL ON *.* TO 'kodi';</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 "kodi" 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 'kodi' IDENTIFIED BY 'kodi';</code>
##<code>GRANT ALL ON *.* TO 'kodi';</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=
== Installing MySQL on Windows ==
If you have chocolatey installed run '''choco install mysql'''
:'''or'''
#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.

If you're using a firewall such as the one that's built into Windows, you will need to follow the steps below for the version of windows you installed XBMC/Kodi on.
=== Windows 7/8/8.1 Built-in Firewall ===
: Run the following command in powershell or execute all the steps below.
'''New-NetFirewallRule -DisplayName "Allow inbound TCP Port 3306 for MySQL" -Direction inbound –LocalPort 3306 -Protocol TCP -Action Allow'''
:#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

== Setup users in MySQL for XBMC/Kodi clients ==

#Open the "MySQL Command Line Client" from the MySQL start menu
#Enter the following commands:
##Type in: <code>CREATE USER 'kodi' IDENTIFIED BY 'kodi';</code> and press return
##Type in: <code>GRANT ALL ON *.* TO 'kodi';</code> and press return
#Close out the command line tool

{{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 'kodi' IDENTIFIED BY 'kodi';</code>
* <code>GRANT ALL ON *.* TO 'kodi';</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 'kodi'@'%' IDENTIFIED BY 'kodi';</code>
#<code>GRANT ALL ON `MyVideos%`.* TO 'kodi'@'%' IDENTIFIED BY 'kodi';</code>

{{Divbox|orange||
The limited grants on this page don't give the kodi user permissions to create required TRIGGERs during install or upgrade.
'''{{kodi}} 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}}

MySQL/Upgrading

2015-01-10T21:56:13Z

Sharrken: /* Making sure {{kodi}} can update the library */

{{mininav| [[MySQL]] }}
{{Kodi MySQL}}
{{:MySQL/Contents}}

When updating to a new version, {{kodi}} will make a copy of the current DB and upgrade the copy. That way if anything goes wrong in the upgrading you still have an original untouched copy of your DB.

{{big|{{note|Updating your library may take a few minutes, so be sure to give {{kodi}} time to do its thing. Stopping midway will mess up the updated DB. }} }}

==Backing up the database==
{{big|'''BACKUP YOUR DATABASE JUST IN CASE.'''}}

Even though {{kodi}} makes a copy of your DB and updates that, it is still highly recommended to [[Import - Export Video Library#Import .2F Export options|export]] your library from your current version before beginning the upgrade process. You don't want to find yourself starting your library from scratch, and it's better to be safe than sorry.

It's also a good idea to make periodic backups of your library even if you are not updating Kodi. Disks can fail, bugs can happen, and if you've put a lot of time in setting up your library then you should play it safe.

To backup simply [[export]] the library to a single file using {{highlight|bordered=yes|[[Settings/Videos#Library|Settings -> Videos -> Library]] -> Export library}} and select "multiple files". "Single file" also works, but "multiple files" is recommended as it is the most fail-safe method, especially for saving/resorting images. For more information see '''[[HOW-TO:Backup the library]]'''.

==Making sure {{kodi}} can update the library==
{{Note|If you originally set up MySQL using this {{kodi}} Wiki guide then you should not have to worry about this section. It never hurts to double check the settings, though.}}

{{Note|if you used 'xbmc' as a username in the past, you can keep using it even though the program has changed names to Kodi. It makes no difference as long as that is the name you set up MySQL with.}}

For {{kodi}} to update the library from a previous version, you may need to make changes to your MySQL server. The user made for the MySQL DB ("xbmc" in most guides) will need access to create new databases. If the user already has that access then you don't need to do anything. If not, you will have to use the following command on your MySQL server:

:<code>GRANT ALL ON *.* TO 'kodi';</code>

Or if using an old xbmc username:

:<code>GRANT ALL ON *.* TO 'xbmc';</code>

If you are worried about security then you can limit Kodi's access in MySQL once it has created the new video DB. However, you will need to re-grant these privileges the next time you update Kodi. If the only thing you use MySQL for is {{kodi}} then you don't really need to worry about security.

==Common problems==
===Upgrade fails===
;Method 1

# Downgrade {{kodi}} on one of your {{kodi}} devices to the previous version of {{kodi}} (you only need to do this to one device). [[Export]] the library to multiple files using {{highlight|bordered=yes|[[Settings/Videos#Library|Settings -> Videos -> Library]] -> Export library}} and select "multiple files".
#:'''''Note:''' If you backed up your {{kodi}} database, you can use that backup in place of this first step.''
# Quit Kodi
# Place {{highlight|<nowiki><importwatchedstate>true</importwatchedstate></nowiki>}} in your [[advancedsettings.xml]] file on the downgraded {{kodi}} device.
# If you used the <name> tag in your [[advancedsettings.xml]] file, remove these lines. {{kodi}} will simply use default database names instead (MyVideos and MyMusic). Sometimes using the <name> tag will cause issues when updating the MySQL libraries, but the tag is not needed as of {{kodi}} v11 and later.
# Use the MySQL configuration utility to drop/delete the existing MySQL copies of the {{kodi}} database(s).
## When using phpMyAdmin: select ''Databases'' option from the top of the screen, put a checkbox in front of all databases called '''MyMusic''' or '''MyVideos''' followed by some digits, and select ''Drop'' underneath the list. Confirm that you want to drop the databases.
## When using the command line tools: enter <code>show databases;</code> including the semicolon. Type <code>drop database <name>;</code> for every name in the resulting list starting with '''MyMusic''' or '''MyVideos''' and followed by some digits, for example: <code>drop database MyVideos78; drop database MyMusic46;</code> Note that actual names may vary per {{kodi}} version, and do not forget the trailing semicolon.
# You can now re-update the device you downgraded in step 1.
# Import the library by simply scanning it in as a new file source. {{kodi}} will pick up the exported data as it scans the files in.
# {{kodi}} will now rebuild a fresh MySQL library DB, but using all your existing information.
# You can now open/launch {{kodi}} on the other devices.

;Method 2

# Quit Kodi
# Use the MySQL configuration utility to drop/delete the existing MySQL copies of the {{kodi}} database(s).
## Consult the table on '''[[Databases/Versions]]''' and note the version number for the downgraded version. You will want to get rid of all of the versions '''after''' that version.
## When using phpMyAdmin: select ''Databases'' option from the top of the screen, put a checkbox in front of all databases (''after'' the stable version from step 2) called '''MyMusic''' or '''MyVideos''' followed by some digits, and select ''Drop'' underneath the list. Confirm that you want to drop the databases.
## When using the command line tools: enter <code>show databases;</code> including the semicolon. Type <code>drop database <name>;</code> for every name in the resulting list, ''after'' the stable version from step 2, starting with '''MyMusic''' or '''MyVideos''' and followed by some digits, for example: <code>drop database MyVideos78; drop database MyMusic46;</code> Note that actual names may vary per {{kodi}} version, and do not forget the trailing semicolon.
# Start one {{kodi}} instance that is using the version you want to use and give it lots of time to update the database.
# {{kodi}} will make a new updated DB using the last working DB from the previous {{kodi}} installation.
# You can now open/launch {{kodi}} on the other devices.

===Different {{kodi}} versions===
Using MySQL to sync the library only works if all {{kodi}} devices are using the same version of Kodi.

==Notes==
<references />

{{Helix updated}}

MySQL/Setting up MySQL

2015-01-10T21:54:06Z

Sharrken: /* Ubuntu Linux */ {{kodi}} name change

{{: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 'kodi' IDENTIFIED BY 'xodi';</code> and press return
##Type in: <code>GRANT ALL ON *.* TO 'kodi';</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=
== Installing MySQL on Windows ==
If you have chocolatey installed run '''choco install mysql'''
:'''or'''
#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.

If you're using a firewall such as the one that's built into Windows, you will need to follow the steps below for the version of windows you installed XBMC/Kodi on.
=== Windows 7/8/8.1 Built-in Firewall ===
: Run the following command in powershell or execute all the steps below.
'''New-NetFirewallRule -DisplayName "Allow inbound TCP Port 3306 for MySQL" -Direction inbound –LocalPort 3306 -Protocol TCP -Action Allow'''
:#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

== Setup users in MySQL for XBMC/Kodi clients ==

#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

{{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}}

MySQL/Sync other parts of Kodi

2015-01-10T21:50:56Z

Sharrken: {{kodi}} name changes

{{:MySQL/Contents}}
{{mininav| [[MySQL]] }}
{{divbox|orange||'''Note:''' Path substitution or any kind of sharing of setting files is not officially supported (with the exception of playlists). It probably won't hurt anything, but some things might not always work right depending on what you are substituting. The following settings on this page are believed to work okay, but if something doesn't work out, just copy the file instead of trying to share/pathsub it.}}

Many things can be synced using [[path substitution]].

'''DO NOT TRY TO SHARE DATABASES WITH THIS METHOD.'''

This works with both directories and single files. The following directories and files are generally safe to share between {{kodi}} devices:
__TOC__
{{-}}
==Steps==
#Share your existing [[userdata folder]] or a new folder with those files via NFS, SMB, or AFP (make sure have write access, not just read-only access). Most users to do this from the same computer/device as the MySQL server.
#{{highlight|bordered=yes|Copy the text from the right hand boxes and add it to your '''advancedsettings.xml''' file, between the <code><pathsubstitution></code> and <code></pathsubstitution></code> tags.}}
#Note/copy the network path of your shared data folder and use that to replace '''PROTOCOL://YOUR_NETWORK_SHARE/kodi/userdata/''', for example an SMB share holding your playlists use <code>smb://NAS/share/kodi_stuff/Playlists/</code>
#Make sure all {{kodi}} devices that are being synced have this addition to their ''advancedsettings.xml'' file.<br/><br/>

===Playlists===
{| class="infobox"
|-
|
<pre>
<substitute>
<from>special://profile/playlists/</from>
<to>PROTOCOL://YOUR_NETWORK_SHARE/kodi/userdata/playlists/</to>
</substitute>
</pre>
|}
The Playlist folder in {{kodi}} contains music, video and mixed [[playlists]]. If you have imported from pre-existing media libraries then you can use your old playlist folder to save time on recreating the various playlists. If your playlists include local file paths, you will need to edit them to use network shares instead.
{{-}}<br/><br/>

===Keymaps===
{| class="infobox"
|-
|
<pre>
<substitute>
<from>special://profile/keymaps/</from>
<to>PROTOCOL://YOUR_NETWORK_SHARE/kodi/userdata/keymaps/</to>
</substitute>
</pre>
|}
Useful if you want the controls on all your {{kodi}} devices to be the same. Might not be a good idea if you use different types of remotes on different devices, as you'll likely want to have individual configurations for them.
{{-}}<br/><br/>

===Sources===
{| class="infobox"
|-
|
<pre>
<substitute>
<from>special://profile/sources.xml</from>
<to>PROTOCOL://YOUR_NETWORK_SHARE/kodi/userdata/sources.xml</to>
</substitute>
<substitute>
<from>special://profile/mediasources.xml</from>
<to>PROTOCOL://YOUR_NETWORK_SHARE/kodi/userdata/mediasources.xml</to>
</substitute>
</pre>
|}
The sources.xml file contains a list of all the sources your media will be collected from, including both local and network-based media. This will also allow you to sync everything that is just in Files view and not in the video library.

If an {{kodi}} device has a source that is specific to it (such as on an internal hard drive that is not shared with the rest of the devices) then you might not want to share sources.xml.

mediasources.xml is similar to sources.xml, but only effects the options seen when you add a new source and select "browse". It really doesn't matter much if you share this file or not.
{{-}}<br/><br/>

===RSS Feeds===
{| class="infobox"
|-
|
<pre>
<substitute>
<from>special://profile/RssFeeds.xml</from>
<to>PROTOCOL://YOUR_NETWORK_SHARE/kodi/userdata/RssFeeds.xml</to>
</substitute>
</pre>
|}
This file tells {{kodi}} what RSS feed to show on the home screen, if enabled.
{{-}}<br/><br/>

===Favourites===
{| class="infobox"
|-
|
<pre>
<substitute>
<from>special://profile/favourites.xml</from>
<to>PROTOCOL://YOUR_NETWORK_SHARE/xodi/userdata/favourites.xml</to>
</substitute>
</pre>
|}
This will sync your [[favorites]] selections between all {{kodi}} devices. If the favorite depends on a file path that is specific to one device then this might not work for the other devices.
{{-}}<br/><br/>

===Network share passwords===
{| class="infobox"
|-
|
<pre>
<substitute>
<from>special://profile/passwords.xml</from>
<to>PROTOCOL://YOUR_NETWORK_SHARE/kodi/userdata/passwords.xml</to>
</substitute>
</pre>
|}
If your network shares use passwords (at least for SMB) then you will need to manually copy the passwords.xml file over to each {{kodi}} device. This file keeps track of those passwords.

{{Gotham updated}}

MySQL/Setting up Kodi

2015-01-10T21:39:14Z

Sharrken: {{kodi}} name changes

{{: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 {{kodi}} devices by sharing them on the network through file sharing. {{kodi}} 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 {{kodi}} device.
*Do not use mapped drives on the OS-level, as {{kodi}} 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 {{kodi}} 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 {{kodi}}.

==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 {{kodi}}.}}

{{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 {{kodi}} 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 {{kodi}} install you want to sync with.
{{-}}

==Importing==
At this point {{kodi}} 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, {{kodi}} behaves exactly like it would as if it had a local database, except that database is on the MySQL server and multiple installs can access that single database.

# Open any of your 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 {{kodi}} and scan it in as if you were setting up your library for the first time (see [[adding videos to the library]]). However, {{kodi}} 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 {{kodi}}'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 devices and the library for all of them will stay in sync.

== Adding new {{kodi}} 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 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 device then it should work on all of them, as they are basically sharing the same "brain".

If you however used a metadata collector add-on ([[scraper]]) that does not ship by default with new installations, such as the [[Add-on:Universal Movie Scraper|Universal Movie Scraper]] you will not be able to display the [[Video_navigation#Media_information_screen|media information screen]] on the new {{kodi}} device. To fix that you need to install the same metadata collector add-on on the new device.

==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. {{kodi}} 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 {{kodi}} 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 {{kodi}} leading to the library functionality not working at all. In other words, don't use <code><nameKodi</name></code> for both music and videos, but instead use something like <code><name>Kodi-music</name></code> and <code><name>Kodi-video</name></code>.}}

{{Gotham updated}}

MySQL

2015-01-10T21:31:13Z

Sharrken: {{kodi}} name changes

{{mininav|[[Syncing and sharing]]}}
{{divbox|orange||<big>'''NOTICE:''' This is considered an advanced (complicated) and experimental feature.</big>}}
{{divbox|red||{{huge|'''NOTICE:''' Every {{kodi}} "client" '''must''' run the same version of {{kodi}}.}}<br />Otherwise they will not be sharing the same library. There can even be differences between [[development builds]], so make sure you always use the same build dates. See '''[[XBMC databases/Version table|Version table]]''' for more info. }}
{{:MySQL/Contents}}
:''For simple library sharing see: '''[[HOW-TO:Share libraries using UPnP]]'''''
[[File:Network.png|200px|left]]
;<big><u>Introduction</u></big>
<section begin="intro"/>If you have more than one {{kodi}} device on your local network then you might want to synchronize them using a MySQL library. Using a MySQL library allows you to store information about your whole video library in a central database, so that multiple devices can access the same information at the same time.<section end="intro"/>

This gives you the ability to do things like:
* Share watched and unwatched status for your media on all devices
* Stop watching a movie or TV show in one room then finish watching it in another room automatically
* Only one library to maintain for all devices

{{next|[[MySQL/Setting up MySQL|Setting up MySQL]]}}
{{Gotham updated}}

[[Category:How-to]]
[[Category:File sharing]]
[[Category:Guides]]
[[Category:Advanced topics]]

Archive:Share libraries using UPnP

2015-01-10T21:29:36Z

Sharrken: {{kodi}} name changes, version clarification

{{mininav|[[UPnP]] {{l2| [[Syncing and sharing]] }} }}
:''For a more complex method of sharing using MySQL see '''[[MySQL]]'''''

<section begin="intro"/>[[UPnP]] sharing between two {{kodi}} devices is the easiest way to share a library. You can also share multiple libraries, one from each {{kodi}} device, to all the other devices on the same network. UPnP also takes care of file sharing, so you do not need to do anything extra even if your files are added locally to {{kodi}}.<section end="intro"/>

# For {{kodi}} device A (the "server") go to:
#* If using XBMC v11 "Eden": {{highlight|bordered=yes|[[Settings/Network#Services|Settings → Network → Services]]}}
#* If using XBMC v12 "Frodo", XBMC v13 "Gotham" or Kodi: {{highlight|bordered=yes|[[Settings/Services#UPnP|Settings → Services → UPnP]]}}
# Enable the UPnP server ('''Share video and music libraries through UPnP''')<br />[[File:Share_libraries_using_UPnP_-_Main_-_2_-_12.0_Frodo.png|500px]]<br /><br />
# For {{kodi}} device B (the "client") you will add device A as a [[UPnP/Media source|media source]]: {{highlight|'''Videos''' → '''Files''' → '''Add Videos...''' → '''Browse''' → ''(scroll down to)'' '''UPnP Devices'''}}<br />[[File:Share_libraries_using_UPnP_-_Browse_UPnP_devices.png|500px]]<br /><br />
# A shows up there. Open the share and then hit '''OK'''.
# Give the new video source from A a name.
# You should now be able to see everything as it is set up on A on B.

== Other guides ==

=== Video guides ===
;UPnP sharing (as seen in XBMC v12, Frodo)

{{youtube|EYX-8FrB1DM}}

[[Category:Manual]]
[[Category:How-to]]
[[Category:UPnP]]
[[Category:Video library]]
[[Category:Music library]]

OSMC

2015-01-10T21:21:24Z

Sharrken: /* RaspBMC */ {{kodi}} name change

{{mininav| [[Devices]] }}
{{to do}}
<section begin="intro" />OSMC is the future name of the RaspBMC and Crystalbuntu XBMC/OS distributions, created and maintained by Sam Nazarko.<section end="intro" />

* More info on OSMC and what it is: http://forum.stmlabs.com/showthread.php?tid=15102

= RaspBMC =

Raspbmc is an {{kodi}} and linux-based OS distribution for [[Raspberry Pi]], created and maintained by Sam Nazarko.

== Main features ==
* Custom Linux distribution with minimalised kernel.
* Auto-updating
* UI installers for Windows, Linux and Mac OS X to allow installation onto am removable device (like USB key or external Hard drive), and NFS share
* PVR / AirTunes / AirPlay integration
* Many addons will work on Raspbmc including SpotiMC for Spotify support
* Same stability and support as the [[Crystalbuntu]] Linux distribution
* AFP, NFS and SMB file sharing
* Configuration utility allowing installation of custom nightlies, audio configuration, update management,
* Server mode – allows MySQL database hosting and Thumbnail sharing for {{kodi}} multiseat systems.
* 1080p decoding
* Free!

== Installing Raspbmc ==
* [http://www.raspbmc.com/wiki/user/windows-installation/ Installing via Windows]
* [http://www.raspbmc.com/wiki/user/os-x-linux-installation/ Installing via Mac OS X or Linux]

== Updating Raspbmc ==
Raspbmc auto-updates itself, as long as version 1.0 Final (or later) is installed and the option 'Keep Raspbmc updated' is enabled in Raspbmc settings under System Configuration. This only takes place if the release build of {{kodi}} is being used. If you have updated to a nightly version then you have to switch back to the release build via the Raspbmc Settings plugin for it to auto-update.

=== How to force an update if your Pi won't update ===

Ssh into your Pi and run the following commands:

<pre>sudo -s
cd /scripts/upd_sys
rm *.sh
wget http://svn.stmlabs.com/svn/raspbmc/release/update-system/getfile.sh
wget http://svn.stmlabs.com/svn/raspbmc/release/update-system/cdn_env_prep.sh
reboot</pre>

== Back Up Configuration/settings ==
# Login to the pi and, from the /home/pi/ dir, type: <code>tar -czf backup.tar.gz .xbmc/ </code>
# Transfer that file to a secondary machine (ftp, sftp, or scp are all viable options)
Put back the backup on the system:
# Return the tar file you copied in step 2 to the Raspberry Pi
# Run the following commands: <code> sudo initctl stop xbmc; tar -xzf backup.tar.gz; rm backup.tar.gz; sudo initctl start xbmc </code>

== Further reading ==
* http://www.raspbmc.com - Project home
* http://forum.stmlabs.com/forumdisplay.php?fid=7 - Raspbmc support forums
* http://www.raspberrypi.org/archives/604- Raspbmc announcement from RaspberryPi.org
* [[forum:121499|forum.xbmc.org thread about Raspbmc]]

== See also ==
* [[Raspberry Pi]]

= Crystalbuntu =
Crystalbuntu is an easy to use XBMC and linux-based OS distribution for [[Apple TV 1]] (silver) created and maintained by Sam Nazarko. It is based on a light weight Ubuntu 12.04 LTS distribution.

* http://crystalbuntu.com

== See also ==
* [[Apple TV 1]]
* [[Apple TV 1 FAQ]]
* [[HOW-TO:Install XBMC on Apple TV 1 (Linux)]]

[[Category:Linux]]
[[Category:Apple TV 1]]
[[Category:Raspberry Pi]]
[[Category:Embedded distro]]

Archive:OpenELEC

2015-01-10T21:19:57Z

Sharrken:

{{mininav|[[General topics]]{{l2|[[Devices]]}}|[[Installing]]{{l2|[[Linux]]}}}}

<section begin=intro />'''OpenELEC''' (short for "''Open Embedded Linux Entertainment Center''") is a free and open source, small and very fast booting, embedded operating system. OpenELEC is a complete media center software suite that comes with a pre-configured version of {{kodi}} and third-party add-ons with retro video game console emulators and PVR plugins.<section end=intro />

OpenELEC is also designed to be used with flash based drives, like compact flash, USB drives, or SSDs.

OpenELEC works on most computers you can install {{kodi}} on, even the [[Raspberry Pi]] and the [[Apple TV 1]] (silver only).

== Main features ==

OpenELEC includes all features that {{kodi}} has to offer.

== Installing OpenELEC ==

A detailed guide about installing OpenELEC can be found at their wiki page: [http://wiki.openelec.tv/index.php?title=Installation Installation]

== Updating OpenELEC ==

A detailed guide about updating OpenELEC can be found at their wiki page: [http://wiki.openelec.tv/index.php?title=Updating_OpenELEC Updating]

== Back Up Configuration/settings ==

== Further reading ==

* http://www.openelec.tv
* [http://wiki.openelec.tv/index.php?title=Installation Installing OpenELEC]
* http://openelec.thestateofme.com/ - Nightly build images for Raspberry Pi
* http://openelec.tv/forum/20-development-discussion/67846-xbmc-gotham-generic-nightly-builds - Nightly build (Gotham) images for generic x86 platforms

== See also ==

* [[Cubox-i]]
* [[Raspberry Pi]]

[[Category:Linux]]
[[Category:Raspberry Pi]]
[[Category:Embedded distro]]
[[Category:Apple TV 1]]

Archive:OpenELEC

2015-01-10T21:18:52Z

Sharrken: /* Main features */

{{mininav|[[General topics]]{{l2|[[Devices]]}}|[[Installing]]{{l2|[[Linux]]}}}}

<section begin=intro />'''OpenELEC''' (short for "''Open Embedded Linux Entertainment Center''") is a free and open source, small and very fast booting, embedded operating system. OpenELEC is a complete media center software suite that comes with a pre-configured version of XBMC and third-party add-ons with retro video game console emulators and PVR plugins.<section end=intro />

OpenELEC is also designed to be used with flash based drives, like compact flash, USB drives, or SSDs.

OpenELEC works on most computers you can install XBMC on, even the [[Raspberry Pi]] and the [[Apple TV 1]] (silver only).

== Main features ==

OpenELEC includes all features that {{kodi}} has to offer.

== Installing OpenELEC ==

A detailed guide about installing OpenELEC can be found at their wiki page: [http://wiki.openelec.tv/index.php?title=Installation Installation]

== Updating OpenELEC ==

A detailed guide about updating OpenELEC can be found at their wiki page: [http://wiki.openelec.tv/index.php?title=Updating_OpenELEC Updating]

== Back Up Configuration/settings ==

== Further reading ==

* http://www.openelec.tv
* [http://wiki.openelec.tv/index.php?title=Installation Installing OpenELEC]
* http://openelec.thestateofme.com/ - Nightly build images for Raspberry Pi
* http://openelec.tv/forum/20-development-discussion/67846-xbmc-gotham-generic-nightly-builds - Nightly build (Gotham) images for generic x86 platforms

== See also ==

* [[Cubox-i]]
* [[Raspberry Pi]]

[[Category:Linux]]
[[Category:Raspberry Pi]]
[[Category:Embedded distro]]
[[Category:Apple TV 1]]