Official Kodi Wiki - User contributions [en]

Media flags

2015-11-12T18:42:30Z

Menakite: erm no, don't suggest to edit the db - doesn't even make sense

'''Media flags''' are icons in Kodi that displays the meta-information from the media file of a movie, TV show or music title.

== Examples ==
<gallery widths=450px heights=250px>
File:Posterwrapmediaflags.png|Media Flags in the movie library, Confluence skin: 1080, H.264, dts, 5.1, 1.85 and Blu-Ray Disc
File:media_flags_music.png|Media Flags in music-section
</gallery>
{{-}}

== Flag types and where they come from ==
Kodi tries to read the meta information from the media file after it's been added to the [[Library]]. This meta-information can be queried by the built-in [[InfoLabels]] in order to display it in the skin.<br />
Example-code for a resolution-flag in [[Confluence]] (Kodi's default skin):
<syntaxhighlight lang="xml" enclose="div">
<control type="image">
<description>Video rez Image</description>
<width>55</width>
<height>35</height>
<aspectratio align="right">keep</aspectratio>
<texture>$INFO[ListItem.VideoResolution,flagging/video/,.png]</texture>
</control>
</syntaxhighlight>

=== Video flags ===
The category video flags provides images for the following properties:
{| class=wikitable
! Resolution
! Format
! Aspect ratio
|-
|[[File:480.png|50px]] [[File:1080.png|50px]] [[File:720.png|50px]] [[File:1080 n.png|50px]] [[File:480-1.png|50px]] '''...'''
|[[File:Divx.png|80px]] [[File:Xvid.png|80px]] [[File:H264.png|80px]] [[File:Bluray.png|80px]] [[File:Dvd.png|80px]] [[File:Avc1.png|80px]] '''...'''
|[[File:1.33.png|50px]] [[File:1.66.png|50px]] [[File:2.20.png|50px]] [[File:2.35.png|50px]] '''...'''
|}

What exact kind of video flag is provided depends on the skin you are using. The above are just a few examples types.

=== Audio flags ===
The category audio flags provides images for the following properties: e.g.
{| class=wikitable
! Channels
! Formats
|-
|[[File:1.png|50px]] [[File:2.png|50px]] [[File:6.png|50px]] [[File:8.png|50px]] [[File:10.png|50px]] '''...'''
|[[File:Aac.png|80px]] [[File:Ac3.png|80px]] [[File:Mp3.png|80px]] [[File:Flac.png|80px]] [[File:Dts.png|80px]] [[File:Dtshd_ma.png|80px]] [[File:Truehd.png|80px]] [[File:Pcm_bluray.png|80px]] [[File:Cdda.png|80px]] '''...'''
|}
What exact kind of audio flag is provided depends on the skin you are using. The above are just a few examples types.

=== Media source ===
{{see also|Add-on:Confluence#Media flags|Naming video files}}
Most skins have flags for the video source of a media file. This information is obtained from the the filename or the directory name.
Media can be flagged with following media source flags in Confluence:
{{#lst:Add-on:Confluence|flags}}

As an alternative you can set your folder structure to fit the keywords above:
* '''C:\Videos\DVDR\Movie1...''' on Windows
* '''/mnt/dev1/videos/bluray/movie1''' on Linux

What exact kind of source flag is provided depends on the skin you are using and its naming convention.

=== Custom flags ===
Most skins also have the ability to show media flags from [[InfoLabels]] that come not from the media file itself. These pieces of information are provided by the scraper that was used to scan the file to the library and can be:<br />
* Movie Studio: WarnerBros., 20th Century Fox, Universal ...
* TV Channel/Network: HBO, ABC, FOX ...
* Rating: MPAA, FSK, UK-Rating ...

=== Special notes ===
* Some file types (e.g. .iso) have to be played one time, before the media flags appear in the database<br />

== See also ==
'''Development:'''
* [[Add-on development]]
* [[Skinning]]
* [http://forum.kodi.tv/showthread.php?tid=184403&pid=1615348#pid1615348 Add custom flag] Forum post

{{Isengard updated}}

[[Category:Skin development]]

Add-on rules

2015-03-05T19:13:04Z

Menakite: /* General requirements */ +note for skins/Default - https://github.com/Razzeee/script.trakt/issues/152#issuecomment-77424059

{{mininav|[[Development]]|[[Add-on development]]}}

=== Repository Submission Guidelines - Please Read Before Submitting Your Addon ===

Because maintaining such a large repository is a large task, we have set some guidelines for inclusion. Please ensure that these guidelines are met before submitting request to be added.
In order to be considered for the official repository, the following guidelines must be met:
* All add-ons must be developed as described on the [[Add-on development]] page.
* You ''must'' include a license file (named LICENSE.txt). We recommend the [http://creativecommons.org/choose/non-web-popup?license_code=by-sa&jurisdiction=&version=3.0&lang=en CC-BY-SA 3.0] for skins and the [http://www.gnu.org/licenses/gpl-howto.html GPL v2+] for others, but most copy left licenses will suffice. Please investigate which license suits your needs and you fully understand the contents.
* All files must be free and legal to distribute.
* The add-on must not violate any known copyright laws - if in doubt, let us know and we'll look into it for you.
* All source files must be included. No pre-compiled files will be allowed.
* You acknowledge that you are the maintainer of your add-on.
* Team-Kodi reserves the right to update or remove it at any time as we deem necessary.
* If a new stable XBMC is going to be released no new submissions are accepted to the repository for the previous version. This will start from when the first [http://en.wikipedia.org/wiki/Release_candidate#Release_candidate release candidate (RC)] of the new version is released. Only fixes and updates will be accepted and processed for the previous version (e.g. if the current stable is 13.x, no updates are allowed for 11.x any more). [[Submitting Add-ons#Allowed submissions|Allowed submissions]]
* Add-ons that contain advertising will not be allowed
* All service providing modules must be used by at least one other add-on in official repository.

=== Updates ===
Keep in mind that add-ons in the official repository should be considered ''stable''. This means that they should be well-tested before you submit them for inclusion.
Because they are for stable users, they should avoid being updated too often. Too often is of course subjective. If your add-on is in rapid development, and features are constantly being added, hold off until you have hit a good stopping point and ''tested'' the current version.

This means that you should ''not'' submit a request every time you change your code. If you are submitting updates more than once per week something is wrong. Once or twice per month is probably a better goal, barring unforeseen conditions (like a content source changing its paths). With good reasons provided we will of course make exceptions as we strive to prove the best user experience.

=== General requirements ===
Here's a list of what basic sanity checks are done by repository maintainer on each submission.

'''Basic file checks:'''

* all strings used by add-ons must be localized, no hard-coded language strings should ever be used
* all paths should be treated as case-sensitive, so that they work on all OSs and file systems.
* all paths and files should be lower-case due to the previous point
** exceptions are README, COPYING, LICENSE.txt that should be upper-case and the "Default" directory in <tt>resources/skins</tt>, for add-ons that need it.
* exception are the translation Language folders with should be first letter capitalised.
* the following file-types are not allowed: .so .dll .pyo .exe .xbt .xpr Thumbs.db and so on<any binary files>
* all text files should use UNIX end-of-line
* all .xml files must pass xml validation
* all .xml files must have xml declaration as header
* all .xml/.txt must have unix style EOL's
* don't use a BOM at the start of your files
* file permissions: files should not be marked as executable
* filenames must have correct encoding (for skins: check your studio logos for corrupt filenames)

'''Things that must be included:'''

* [[Add-on structure#addon.xml|addon.xml]] must contain correct and valid info / version
* [[Add-on structure#icon.png|icon.png]] must be present (256x256)
* [[Add-on structure#fanart.jpg|fanart.jpg]] must be present (1280x720 or 1920x1080)
* [[Add-on structure#LICENSE.txt|LICENCE.txt]] must be present
* [[Add-on structure#changelog.txt|changelog.txt]] must be present
*: start with last changes at top of the file
{{See also|Add-on_structure}}

'''Things that can't be included:'''

* no .xbt files (these will be generated by our repository)
* no other add-ons included (skinners: if you need a script, submit it separately and depend on it)
* don't include unneeded files (.pdf, .doc, thumbs.db, etc...)
* no licensed fonts / background images / anything

==== Requirements for skins ====

'''Basic checks:'''

* The file size must be sane. There is no hard limit, but a 100mb skin is pushing it.
* No mods. Mods are great, and pop up frequently in the forums. But they are only confusing to non-forum-goers. This can be vague, each is evaluated on its own merit. By naming your "mod" different and make it substantial different enough, we will of course take it in consideration.
* Due to a bug in TexturePacker, all graphics files should have a resolution of at least 4x4.
* themes must be in a subfolder of the themes/ folder in the skin root (eg. skin.foo/themes/blue/<files>). The .xbt file will be created by our repo backend.
* If you want to have some images outside of Textures.xbt, then make sure you place those images outside of the media/ folder and reference them using special://skin/backdrops/* or similar. This is most useful for backgrounds - it keeps the size of the packed textures down. Any images you have in the media/ folder will be placed in Textures.xbt in the official repository.
* The amount of extra add-on dependencies must be kept to a bare minimum. Only add dependencies that have direct interactions with the skin.

'''Things that must be included:'''

* _screenshots folder must be present, containing max. 10 .jpg screenshots (1280x720) with a reasonable file size.

'''Code checks:'''

* all labels must be localized
* code should be case-sensitive
* skins should not create warning/errors in the logfile, this can be a lot of things:
:* invalid includes
:* undefined actions
:* unable to evaluate condition
:* undefined vars
:* can't focus 'id'

{{Note|This of course also applies to script add-ons that use skin files}}

==== Optional support ====

This is optional and should not block inclusion in official repo.

* mouse support
* touchscreen support
* karaoke dialogs
* peripheral dialogs
* pvr support

=== Requirements for scripts and plugins ===

* all special:// paths should be translated using xbmc.translatePath("special://foo/bar")
* direct access to the XBMC database is '''not''' allowed. You must use [[JSON RPC]] for this.
* directly using analytics (Google Analytics for example) from within add-ons is not allowed. This should be handled server side by using user-agent.
* add-ons should store all their data in their own subfolder inside the addon_data directory. Access (read/write/delete) to any other files in settings folders is not allowed. Access (read/write/delete) to other all other files/directories must be opt-in by the user, and be clear for the user to understand what is being accessed. ''Exceptions to this rule may be granted in specific cases only. Please contact Team XBMC's add-on repository maintainers via the add-on mailing list if your add-on needs access to such files.''
** xbmc.translatePath(_xbmcaddon.Addon().getAddonInfo('path')).decode('utf-8') should be used for files included with the add-on
** xbmc.translatePath(_xbmcaddon.Addon().getAddonInfo('profile')).decode('utf-8') should be used for storing add-on related files

'''Things that shouldn't be included:'''

* _screenshots folder (only in remote cases it could have some added value)

=== Requirements for scrapers ===
* scraper must return the following minimum information: movie title, year, plot, cast, poster, fanart
* use 'chain function' for calling functions in common scrapers
* remove the deprecated XML tags from the scraper header in case you use a scraper editor made for pre-Dharma versions of XBMC

[[Category:Add-on development]]
[[Category:Team Kodi specific notes]]

Texture Cache Maintenance utility

2015-02-11T21:21:33Z

Menakite: follow redirects with curl

{{mininav| [[Supplemental tools]] }}
{{forum link2|1=For the most up to date information and help, see ''[http://forum.xbmc.org/showthread.php?tid=158373 Texture Cache Maintenance utility]'' on the Kodi forums.}}
<section begin="intro" />Texture Cache Maintenance utility is a python script created by MillhouseVH, that can do a number of artwork related maintenance on the XBMC library. The script can be used to pre-generate thumbnails, clean up old thumbnail files, find corrupted files, and much more. The script can work on any OS that can run Python 2.6 or higher.<section end="intro" />

== From the author ==
It's annoying having to delete the entire Textures13.db+Thumbnails folder to try and correct scraping errors and/or corrupted images that just never go away, so I've written a very trivial Python script that can be used to interrogate the texture cache database, and can also be used to remove - with absolute precision - those database rows and cached files that relate to problematic artwork.

The script has been tested with local installations of XBMC Frodo on OpenELEC R-Pi and Ubuntu 12.10, and also Windows with Python 2.7.3 running against a remote Frodo installation of XBMC. A separate properties file can be used to specify non-default configurations (see property file details at the end of this post).

This is not an addon, and it requires that the webserver is enabled in XBMC on port 8080 (unless another port is specified in the properties file). It also assumes you are comfortable working at the command line (ssh in Linux, a large CMD window may also work OK for Windows users).

== Summary of features ==

* [c, C] Automatically re-cache missing artwork, with option to force download of existing artwork (remove first, then re-cache). Can use multiple threads (default is 2)
* [nc] Identify those items that require caching (and would be cached by '''c''' option)
* [lc, lnc] Same as '''c''' and '''nc''', but only considers those media (movies, tvshows/episodes) added since the modification timestamp of the file identified by the property ''lastrunfile''
* [p, P] Prune texture cache by removing accumulated cruft such as image previews, previously deleted movies/tv shows/music and whose artwork remains in the texture cache even after cleaning the database. Essentially, remove any cached file that is no longer associated with an entry in the media library, or an addon.
* [s, S] Search texture cache for specific files and view database content, can help explain reason for incorrect artwork. '''S''' will return only those database results for items that no longer exist in the filesystem.
* [x, X] Extract rows from texture cache database, with optional SQL filter. '''X''' will return only those database results for items that no longer exist in the filesystem.
* [d] Delete specific database rows and corresponding files from the texture cache using database row identifier (see '''s'''/'''S''')
* [r, R] Reverse query cache, identifying any "orphaned" files no longer referenced by texture cache database, with option to auto-delete files
* [j, J, jd, Jd] Query media library using JSON API, and export content as JSON (and suitable for further external processing)
* [qa] Perform QA check on media library recently added items, identifying missing properties (eg. plot, mpaa certificate, artwork etc.). Default QA period is previous 30 days. Add property ''qa.file = yes'' to verify file exists during QA. Add additional QA fields using ''qa.art.*'', ''qa.blank.*'' and ''qa.zero.*'' properties.
* [qax] Like the '''qa''' option, but performs a remove and then rescan of any media found to fail the QA tests
* [ascan, vscan] Initiate audio/video library scan, either entire library or a specific path (see '''sources'''). The exit status is the number of items added during each scan, ie. 0 or +n.
* [watched] Backup and restore movie and tvshow watched lists to a text file. Watched list will be restored keeping more recent playcount, lastplayed and resume points unless property '''watched.overwrite=yes''' is specified, in which case the watched list will be restored exactly as per the backup.
* [missing] Locate media files missing from the specified media library and source label, eg. ''missing movies "My Movies"''
* [aclean, vclean] Clean audio/video library
* [directory] Obtain directory listing for a specific path (see '''sources''')
* [sources] List of sources for a specific media class (video, music, pictures, files, programs)
* [status] Display status of client - ScreenSaver active, IsIdle (default period 600 seconds, or user specified) and active Player type (audio or video), plus title of any media currently being played.
* [monitor] Display client event notifications as they occur
* [power] Set power state of client - suspend, hibernate, shutdown or reboot
* [wake] Use Wake Over LAN to wake a suspended/hibernating remote client. Specify the MAC address of the remote client in the '''network.mac''' property (ie. '''network.mac=xx:xx:xx:xx:xx:xx'''). When the client is no longer required, suspend or hibernate it with the relevant '''power''' option
* [exec, execw] Execute the specified addon, with optional parameters. eg. ''exec script.artwork.downloader silent=true mediatype=tvshow''. Use execw to wait, but this rarely has any effect (possibly not implemented by JSON?)

== Installation instructions ==

Download the single Python file required from [https://github.com/MilhouseVH/texturecache.py github]. A default properties file is available on github, rename this to texturecache.cfg in order to use it.

To download the script at the command line:
<pre>
wget https://raw.github.com/MilhouseVH/texturecache.py/master/texturecache.py
chmod +x ./texturecache.py
</pre>

If you get a certificate error, try adding "--no-check-certificate" to the wget command line.

and for anyone on OpenELEC which has a pretty basic wget that doesn't support https downloads, use curl instead:
<pre>
curl -L https://raw.github.com/MilhouseVH/texturecache.py/master/texturecache.py -o texturecache.py
chmod +x ./texturecache.py
</pre>

'''ATV2 (iOS) users'''

Python 2.6+ is required to run this script, and although Python can be installed on iOS using "apt-get install python", the version installed (typically v2.5.1 - check with "python --version") is very old and lacks language features required by the script. It is possible to install a more recent [http://code.google.com/p/yangapp/downloads/detail?name=python_2.7.3-3_iphoneos-arm.deb&can=2&q= Python 2.7.3 package] as follows:
<pre>
ssh root@YOUR.ATV2.IP.ADDRESS
rm -f python*.deb
wget http://yangapp.googlecode.com/files/python_2.7.3-3_iphoneos-arm.deb
dpkg -i python*.deb
rm python*.deb
</pre>

== Example usage ==

Let's say the poster image for my "Dr. No" movie is corrupted, and I want to delete it so that XBMC will automatically re-cache it (hopefully correctly) next time it is displayed:

1) Execute: '''./texturecache.py s "Dr. No"''' to search for my Dr. No related artwork

2) Several rows should be returned, relating to different cached artwork - one row will be for the poster, the other fanart, and there may also be rows for other image types too (logo, clearart etc.). This is what I get:
<pre>
000226|5/596edd13.jpg|0720|1280|0011|2013-03-05 02:07:40|2013-03-04 21:27:37|nfs://192.168.0.3/mnt/share/media/Video/Movies/James Bond/Dr. No (1962)[DVDRip]-fanart.jpg
000227|6/6f3d0d94.jpg|0512|0364|0003|2013-03-05 02:07:40|2013-03-04 22:26:38|nfs://192.168.0.3/mnt/share/media/Video/Movies/James Bond/Dr. No (1962)[DVDRip].tbn
Matching row ids: 226 227
</pre>

3) Since I want to remove only the poster (.tbn) I can execute '''./texturecache.py d 227''' and both the database row and cached poster image will be deleted. If I wanted to remove both images, I would simply execute '''./texturecache.py d 226 227''' and the two rows and their corresponding cached images will be removed.

Alternatively, '''./texturecache.py C movies "Dr. No"''' would achieve the same result including re-caching the deleted items.

== Format of "dumped" records ==

When displaying rows from the database, the following fields (columns) are shown:

<pre>
rowid, cachedurl, height, width, usecount, lastusetime, lasthashcheck, url
</pre>

== Additional usage examples ==

To view your most recently accessed artwork:
<pre>
./texturecache.py x | sort -t"|" -k6
-- or --
./texturecache.py x "order by lastusetime asc"
</pre>

or your top 10 accessed artwork...
<pre>
./texturecache.py x | sort -t"|" -k5r | head -10
-- or --
./texturecache.py x "order by usecount desc" 2>/dev/null | head -10
</pre>

Use texturecache.py to identify artwork for deletion, then cutting and pasting the matched ids into the "d" option or via a script:

For example, to delete those small remote thumbnails you might have viewed when downloading artwork (and which still clutter up your cache):
<pre>
./texturecache.py s "size=thumb"
<then cut & paste the ids as an argument to ./texturecache.py d>
</pre>

and the same, but automatically:
<pre>
IDS=$(./texturecache.py s "size=thumb" 2>&1 1>/dev/null | cut -b19-)
[ -n "$IDS" ] && ./texturecache.py d $IDS
-- or --
./texturecache.py P
</pre>

Delete any artwork that has not been accessed since a particular date:
<pre>
./texturecache.py x "where lastusetime <= '2013-03-05'
</pre>

or hasn't been accessed more than once:
<pre>
./texturecache.py x "where usecount <= 1"
</pre>

Query the media library returning JSON results:

First, just the default fields for a particular class (movies), filtering for a specific item (Avatar):

<pre>
./texturecache.py j movies "Avatar"
[
{
"movieid": 22,
"title": "Avatar",
"art": {
"fanart": "image://nfs%3a%2f%2f192.168.0.3%2fmnt%2fshare%2fmedia%2fVideo%2fMovies%2fAvatar%20(2009)%5bDVDRip%5d-fanart.jpg/",
"discart": "image://http%3a%2f%2fassets.fanart.tv%2ffanart%2fmovies%2f19995%2fmoviedisc%2favatar-4eea31049147b.png/",
"poster": "image://nfs%3a%2f%2f192.168.0.3%2fmnt%2fshare%2fmedia%2fVideo%2fMovies%2fAvatar%20(2009)%5bDVDRip%5d.tbn/",
"clearart": "image://http%3a%2f%2fassets.fanart.tv%2ffanart%2fmovies%2f19995%2fmovieart%2favatar-4f803992128b8.png/",
"clearlogo": "image://http%3a%2f%2fassets.fanart.tv%2ffanart%2fmovies%2f19995%2fhdmovielogo%2favatar-503e0262ba196.png/"
},
"label": "Avatar"
}
]
</pre>

With "extrajson.movies = trailer, streamdetails, file" in the properties file, the same query but returning the extra fields too:

<pre>
./texturecache.py J movies "Avatar"
[
{
"movieid": 22,
"title": "Avatar",
"label": "Avatar",
"file": "nfs://192.168.0.3/mnt/share/media/Video/Movies/Avatar (2009)[DVDRip].m4v",
"art": {
"fanart": "image://nfs%3a%2f%2f192.168.0.3%2fmnt%2fshare%2fmedia%2fVideo%2fMovies%2fAvatar%20(2009)%5bDVDRip%5d-fanart.jpg/",
"discart": "image://http%3a%2f%2fassets.fanart.tv%2ffanart%2fmovies%2f19995%2fmoviedisc%2favatar-4eea31049147b.png/",
"poster": "image://nfs%3a%2f%2f192.168.0.3%2fmnt%2fshare%2fmedia%2fVideo%2fMovies%2fAvatar%20(2009)%5bDVDRip%5d.tbn/",
"clearart": "image://http%3a%2f%2fassets.fanart.tv%2ffanart%2fmovies%2f19995%2fmovieart%2favatar-4f803992128b8.png/",
"clearlogo": "image://http%3a%2f%2fassets.fanart.tv%2ffanart%2fmovies%2f19995%2fhdmovielogo%2favatar-503e0262ba196.png/"
},
"trailer": "",
"streamdetails": {
"video": [
{
"duration": 9305,
"width": 720,
"codec": "avc1",
"aspect": 1.7779999971389771,
"height": 576
}
],
"audio": [
{
"channels": 6,
"codec": "aac",
"language": "eng"
}
],
"subtitle": []
}
}
]
</pre>

== Optional Properties File ==

By default the script will run fine on distributions where the .xbmc/userdata folder is within the users Home folder (ie. userdata=~/.xbmc/userdata). To override this default, specify a properties file with a different value for the userdata property.

The properties file should be called '''texturecache.cfg''', and be in the same directory as the texturecache.py script. What follows is an example properties file with the default values shown:

<pre>
sep = |
userdata = ~/.xbmc/userdata
dbfile = Database/Textures13.db
thumbnails = Thumbnails
xbmc.host = localhost
webserver.port = 8080
webserver.username =
webserver.password =
rpc.port = 9090
download.threads = 2
extrajson.albums =
extrajson.artists =
extrajson.songs =
extrajson.movies =
extrajson.sets =
extrajson.tvshows.tvshow =
extrajson.tvshows.season =
extrajson.tvshows.episode =
qaperiod = 30
qa.file = no
qa.fail.urls = image://video, image://music
qa.warn.urls =
cache.castthumb = no
cache.hideallitems = no
cache.ignore.types = image://video
logfile =
logfile.verbose = no
checkupdate = yes
lastrunfile =
orphan.limit.check = yes
nonmedia.filetypes =
watched.overwrite = no
network.mac =
</pre>

The dbfile and thumbbnails properties represent folders that are both relative to the userdata property.

Specify webserver.username and webserver.password if you require webserver authentication.

extrajson.* properties allow the specification of additional JSON audio/video fields to be returned by the J query option.

Cast thumbnails will not be updated by default, so specify cache.castthumb = yes if you require cast artwork to be re-cached.

Ignore specific URLs when pre-loading the cache (c/C options), by specifying comma delimited regex patterns for the cache.ignore.types property. Default value is image://video. Set to None to process all URLs. Any matching URL will not be cached (c/C), nor will it be deleted when forcing a reload (option C).

Specify a filename for the logfile property, to log detailed processing information.
== Notes ==
See [https://github.com/MilhouseVH/texturecache.py github] for full changelog and further details in [https://github.com/MilhouseVH/texturecache.py/blob/master/README.md README].

Run the script without arguments for usage and current configuration information.

[[Category:Supplemental tools]]
[[Category:Linux]]
[[Category:Mac OS X]]
[[Category:IOS]]

XBian

2015-02-07T17:23:05Z

Menakite: fix links

<section begin="intro" />XBian is a small, fast and lightweight media center distro for the [[Raspberry Pi]], based on a minimal Raspbian image. Their slogan is “XBMC on Raspberry Pi, the bleeding edge” as their main focus is delivering the fastest XBMC solution for the Raspberry Pi. It has a fast userinterface and is often even able to playback DTS encoded audio without any problems.<section end="intro" />

More about [http://xbian.org XBian] can be found in their [http://xbian.org/community/what-is-xbian/ About us] and the [http://xbian.org/why-xbian/ Why XBian?]-page

== Main features ==
* Fits on 1GB SD cards
* Very smooth UI
* Low RAM usage and low CPU usage
* Auto-mount USB
* Toggle between 1080p,720p,540p & 480p GUI
* Support for AFP, NFS, AirPlay, CEC, Lirc, PVR
* 1080p/DTS smooth playback
* Easy configuration

== Installation ==
XBian can be installed using the Windows Installer or manually ([http://xbian.org/getting-started/ instructions here]). For existing installation it provides updates over the internet, so users can upgrade their installation.

* [http://xbian.org/getxbian/ Download page with Installers]
* [http://xbian.org/getting-started/ Getting Started]

== Using Xbian ==
* [http://xbian.org/getting-started/ Getting Started]
* [http://xbian.org/faq/ FAQ]
* [http://forum.xbian.org Forum]

== XBian Wiki ==
* [http://wiki.xbian.org/ XBian Wiki for Users]
* [https://github.com/xbianonpi/xbian/wiki XBian Wiki for Developers]

The Wikis will get better and better by time. It's just opened.

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

[[Category:Linux]]
[[Category:Raspberry Pi]]
[[Category:Embedded distro]]

Raspberry Pi

2015-02-07T17:15:55Z

Menakite: /* Installing Kodi */ fix links to xbian.org

{{mininav|[[Devices]]}}

{{divbox|orange|| {{center| {{larger| Yes, Kodi works on the '''[[Raspberry Pi 2]]!''' }} }} }}

[[File:Single-board computer Raspberry Pi.jpg|320px|right]]

{{forum link2|1=For more info and help, check out the [http://forum.xbmc.org/forumdisplay.php?fid=166 XBMC Raspberry Pi support forum]}}
<section begin="intro" />The '''Raspberry Pi''' is an ARM powered, credit card sized computer developed in the UK by the Raspberry Pi Foundation for educational and hobbyist purposes. The low power computer is mass produced at very low prices and the high number of units sold gives it massive community support. As an XBMC HTPC, the Pi supports full 1080P video playback, supports most major codecs, most if not all XBMC add-ons, and a reasonably responsive GUI.<section end="intro" />

== Installing Kodi ==
{{Main|HOW-TO:Install Kodi on Raspberry Pi}}
<section begin="install"/>The easiest way to install Kodi on an R-Pi is to use one of these pre-made OS/Kodi packages:
<div class="plainlinks">
* '''[[OpenELEC]] -''' [http://wiki.openelec.tv/index.php?title=Installing_OpenELEC_on_Raspberry_Pi Installing] • [http://wiki.openelec.tv/index.php?title=Raspberry_Pi_FAQ FAQ] • [http://openelec.tv/forum/124-raspberry-pi Help forum] • [[HOW-TO:Install XBMC on Raspberry Pi with USB drive|USB drive install]]
* '''[[Raspbmc]] -''' Installing: [http://www.raspbmc.com/wiki/user/windows-installation/ Windows], [http://www.raspbmc.com/wiki/user/os-x-linux-installation/ Mac OS X, Linux] • [http://www.raspbmc.com/wiki/user/frequently-asked-questions/ FAQ] • [http://www.raspbmc.com/wiki/user/ User guide] - [http://forum.stmlabs.com/forumdisplay.php?fid=7 Help forum]
* '''[[XBian]] -''' [http://xbian.org/getxbian/ Installing] • [http://xbian.org/faq/ FAQ] • [http://xbian.org/getting-started/ Starters guide] • [http://forum.xbian.org/ Forum]
</div>
<section end="install"/>

== Frequently Asked Questions ==
{{see|Raspberry Pi FAQ}}

== Maximizing performance ==
<section begin="performance" />
* Use a lightweight skin such as the default Confluence, Amber, Quartz, Bellow, or xTV-SAF.

* Turn off RSS feeds and any scrolling text options for your skin.

* Use an SD card with good rewrite speeds. The class of the SD card doesn't always mean it will be faster, as that speed listing is for sustained reading and writing. For {{kodi}} random read/write speeds are more important. '''''[http://swag.raspberrypi.org/products/noobs-8gb-sd-card The class 4/6 Samsung SD cards sold on the Raspberry Pi Store] (the ones with NOOBS on them) typically have much better performance than most class 10 cards.''''' For more information about SD card speeds, check out this excellent thread on the R-Pi forum: ''' http://www.raspberrypi.org/forums/viewtopic.php?p=53159 '''

* You can also try to use a combination of SD and fast USB drive for your {{kodi}} install, but recent improvements to the software make it so that even just using a good SD card is about as fast as using a fast USB drive.

* Avoid using wifi. If you do use wifi, use a wifi adapter that contains two antenna (either internally or externally). Otherwise, stick to wired ethernet, local USB drives, or ethernet-over-power devices (like Homeplug, etc).

* If you are using wifi and it seems just on the edge of being fast enough, check out '''[[HOW-TO:Modify the video cache]]'''.

* Try using '''[[NFS]]''' file shares instead of SMB file shares.

* Try mounting network shares through OS rather than Kodi. This allows more tweaking of filesystem options, like chosing UDP and larger block sizes. See [http://forum.osmc.tv/showthread.php?tid=6825 This raspbmc thread for details]

* Overclock. Most Pi's can handle a significant overclock, as long as they have a good power supply. There is no universal setting that will work for everyone (except for the default speed that you get without overclocking). Try various overclocking settings and run {{kodi}} for a while and see if it's stable. If one group of overclocking settings causes crashes, try a group of settings that are lower than that. For more information about this check out this forum thread: ''' http://forum.xbmc.org/showthread.php?tid=199272 '''

* "Extract thumbnail and video information" from '''[[Settings/Video#File lists|file lists settings]]''' is disabled by default on the Pi as it improves browsing performance.

* For smoother video playback enable "Adjust display refresh rate to match video" from '''[[Settings/Video#Playback|playback settings]]'''

* When using dvdplayer "Sync playback to display" and "adjust PLL" for sync method are recommended. See '''[[Settings/Video#Playback|playback settings]]'''

* Make sure the video is using H.264 (up to High Profile. Hi10P will not work) or MPEG-4, or, if a codec was purchased and enabled, MPEG-2 or VC-1.

* Passthrough is recommended as it lowers CPU usage for DTS and AC3. Use '''[[Settings/System#Audio output|audio passthrough]]''' if your TV/receiver supports it.

* To determine which audio passthrough formats your HDMI-connected TV supports, you can log in to your chosen distribution, via SSH, and run this command: <code>/opt/vc/bin/tvservice a</code> (on OpenELEC: <code>tvservice -a</code>).

* Feeling adventurous? Check out the latest OpenELEC test builds, which often have even more speed improvements. Just remember that these builds can often be unstable: ''' http://forum.xbmc.org/showthread.php?tid=192380 '''

* Some additional advanced tips for speeding up boot times. {{editor note|Some of this can likely be broken up into individual bullet points for this list, but I haven't examined any of this in detail yet. I'm not sure which ones only improve boot time and which ones improve actual performance once already booted. If anyone wants to take a whack at this, please do.}} http://forum.xbmc.org/showthread.php?tid=201354

* For locally connected drives containing videos and music, the format of the drive can have an impact on read and write speeds. For example, NTFS tends to be much slower on any Linux-based system than the more native EXOFS formats (ext2, ext3, etc).

* If you use [[MySQL]] then you will want to make sure your images are pre-cached using the '''[[Texture Cache Maintenance utility]] tool'''. Local libraries typically don't need this as their images are cached when videos are scanned in. Using MySQL can improve performance as the database queries are handled by another machine.

* Organizing your movies in single folders for each movie, rather than all movies in one folder, is recommended. The individual folders reduce the time it takes for {{kodi}} to look for supporting media like external subtitles, making browsing, scanning and starting playback a little faster. You might also want to consider pre-scraping the meta data using a '''[[Library manager]]''' to reduce the time it takes to scan in both movies and TV shows.
<section end="performance" />

== Remote controls ==
[[File:gpioir.png|right|250px|thumb|Wiring instructions for a TSOP4838 GPIO IR sensor.]]
;GPIO IR receiver
:Don't have a CEC TV or a smartphone remote? For less than a dollar/euro, you can add an IR receiver to your Raspberry Pi that works with most MCE and Apple remotes (and a few others). Most {{kodi}} install options for the Pi should work with the GPIO IR out of the box, or by enabling a setting from within {{kodi}}. Go to a local electronics store or search on ebay for "<code>TSOP4838</code>" and use some simple jumper wires (or solder the pins directly, if you wish). {{smaller|''(We need a link to a good, up to date GPIO IR guide. Most of the links I found are outdated and contain instructions for additional configurations that are no longer required. If you find a good link/guide, please add it to the wiki.)''}}

;[[CEC]]
:If your TV supports '''[[CEC]]''' then you should be able to use the remote control that came with your TV to control {{kodi}}. The remote control signals are sent over the HDMI cable and most often don't require any further settings or configuration.

;[[MCE remotes]]
:Various '''MCE''' USB receivers and remotes will work on the Pi.

;[[Keyboards]] and mice
:Any '''[[Keyboard]]''' such as wired, wireless, bluetooth. This includes remotes that are seen as keyboards, such as Rii remotes, the Mele F10-Pro remote, or the (very awesome) '''[[Flirc]]'''.

;[[Smartphone/tablet remotes]]
:Use your smartphone or tablet as a remote control.

;[[Web interface]]s
:Control {{kodi}} from anything that has a web browser.
{{-}}

== How good is it, really? ==
See for yourself: https://www.youtube.com/watch?v=ErWF2sYgJec<br />
{{youtube|ErWF2sYgJec}}

== Further reading ==
* [http://raspberrypi.org RaspberryPi.org]
* [http://elinux.org/RaspberryPiBoard Raspberry Pi Hub Wiki]
* [http://lea-linux.org/documentations/Raspberry_Pi Raspberry Pi French Wiki]
* [[Wikipedia:Raspberry Pi]]

==Random notes==
{{large|''Feel free to place various notes, tips, and links here. As this section of the wiki gets more organized, those notes will be properly sorted. Consider this like a dumping ground for when you're not sure where to put something.''}}
*

{{Gotham updated}}

[[Category:Linux]]
[[Category:HTPC]]
[[Category:Raspberry Pi]]
[[Category:Broadcom]]
[[Category:ARM]]