Official Kodi Wiki - User contributions [en]

Samples

2019-05-10T13:04:17Z

Gamester17: /* Library samples */

{{mininav| [[Troubleshooting]] {{l2|[[Development builds]] }} }}

{{forum link2|1=Questions? Comments? See the ''[http://forum.kodi.tv/showthread.php?tid=248794 discussion thread]''}}

''(Thanks to hdmkv for putting together these links)''

Kodi users are a demanding bunch when it comes to media players with Kodi & having as-close-to-perfect video playback capabilities as possible. All videos should play smoothly and w/o distracting artifacts such as stutters, frame skips, improper framerates, macroblocking, and audio drop-outs.

Below is a collection of a/v clips for testing, pushing media player capabilities. Not all types, but the most widely used or critical types for home theater enthusiasts. [[w:Fair use|Fair use]] is claimed on all non-[[w:copyleft|copyleft]] clips, as their the purpose is only for testing, technical evaluation, and documentation.

==3D Test Clips==

#[https://drive.google.com/file/d/0BwxFVkl63-lEd2c0ekxfbFd3Tmc/view?usp=sharing MVC 3D ISO Sample #1] (1080p/23.976)
#[https://drive.google.com/file/d/0BwxFVkl63-lEM2xjQndxV3ZzaVE/view?usp=sharing MVC 3D ISO Sample #2 with 3D Subtitles] (1080p/23.976)
#[https://drive.google.com/file/d/0BwxFVkl63-lEMkJTV21JNnhfNlE/view?usp=sharing MVC 3D ISO Sample #3 for Pop-out & Depth Evaluation] (1080p/23.976)
#[https://drive.google.com/file/d/0BwxFVkl63-lEWmRyc0YwUExxX0U/view?usp=sharing MVC 3D ISO Sample #4 for Proper Lip-synch & Clean Graphics Render Verification] (1080p/23.976)
#[https://drive.google.com/file/d/0BwxFVkl63-lETWMzM1dRZF9XMDA/view?usp=sharing MVC 3D MKV] (1080p/23.976)
#[https://drive.google.com/file/d/0BwxFVkl63-lEX3RpYTNEMFZxcjA/view?usp=sharing HSBS (side-by-side)] (MKV @ 1080p/23.976)
#[https://drive.google.com/file/d/0BwxFVkl63-lET0czejJBVXJLSkE/view?usp=sharing HTAB/HOU (top-and-bottom)] (MKV @ 1080p/23.976)

==HD Audio Test Clips==
{{note|To download, hover over link:
* If demo-world, click to go to site, then right-click thumbnail of video there & choose 'Save link as...' to download
* For rest, just click}}

#[https://mega.nz/#!cM9VmBSL!mME5qULH2H5M24vLmjqfZZkaoUjY6RsrGPiw3ultMW0 Dolby Digital Plus 7.1] (M2TS @ 1080p/29.970) ''(thanks wesk05)''
#[http://www.demo-world.eu/download-2d-trailers/?file=dolby_digital_plus_channel_check_lossless-DWEU.mkv&pic=dolby_digital_plus_channel_check_lossless.jpg Dolby Digital Plus 7.1 Channel Check] (MKV @ 1080p/29.970)
#Dolby TrueHD 5.1 (use clip #10 in 'Codecs' section below)
#[http://www.demo-world.eu/download-2d-trailers/?file=dolby_truehd_channel_check_lossless-DWEU.mkv&pic=dolby_truehd_channel_check_lossless.jpg Dolby TrueHD 7.1 Channel Check] (MKV @ 1080p/29.970)
#[http://www.demo-world.eu/download-2d-trailers/?file=dolby_amaze_lossless-DWEU.m2ts&pic=dolby_amaze.jpg Dolby ATMOS 'Amaze' Demo] (M2TS @ 1080p/24.000)
#[https://drive.google.com/open?id=0BwxFVkl63-lENElIcC1xTnF2Yk0 Dolby ATMOS 'Helicopter' Demo] (M2TS @ 1080p/29.970 with DD+ 7.1 secondary track)
#[https://www.demolandia.net/downloads.php?id=236762 Dolby ATMOS 'Audiosphere' Demo] (M2TS @ 1080p/24.000)
#[https://www.demolandia.net/downloads.php?id=52783232 Dolby ATMOS 'Silent' Demo] (M2TS @ 1080p/24.000)
#[https://drive.google.com/file/d/0BwxFVkl63-lEcU1ScWZuMjhpOXM/view?usp=sharing DTS-HD HRA 5.1] (MKV @ 1080p/23.976 VC-1)
#[http://www.demo-world.eu/download-2d-trailers/?file=dts_orchestra_short_lossless-DWEU.mkv&pic=dts_orchestra.jpg DTS-HD HRA 7.1] (MKV @ 1080p/29.970)
#[https://drive.google.com/file/d/0B4nYAKUiVpepY1NuQW5ER3l3SXc/edit?usp=sharing DTS-HD MA 5.1 Channel Check] (M2TS @ 1080p/23.976)
#[https://drive.google.com/file/d/0B67BGVX7nHIlNlJBenpkQkhFXzA/view DTS-HD MA 5.1 24-bit 192kHz audio-only sample] (MKV) ''(thanks HomerJau)''
#[http://www.demo-world.eu/download-2d-trailers/?file=dts_hd_master_audio_sound_check_7_1_lossless-DWEU.mkv&pic=dts_hd_master_audio_sound_check_7_1_lossless.jpg DTS-HD MA 7.1 Speaker Phase] (MKV @ 1080p/23.976)
#[https://drive.google.com/open?id=0Bx63o79bMC7lMEMxUmxzV2NtYTA DTS-HD MA 7.1 'Dredd' Audio Channel Check] (M2TS @ 1080p/23.976) ''(thanks looun)''
#[http://www.demo-world.eu/download-2d-trailers/?file=dts_x_all_around_us_lossless-DWEU.mkv&pic=dts_x_all_around_us.jpg DTS:X 'All Around Us' Demo] (MKV @ 1080p/23.976) ''(thanks wesk05)''
#[https://drive.google.com/open?id=0BwxFVkl63-lEQWNKRnBPUlB3QXc DTS:X 'Gravity' Demo] (MKV @ 1080p/23.976) ''(thanks wesk05; modified to only retain the X track)''
#[https://www.demolandia.net/downloads.php?id=87980801 DTS:X 'Sound Unbound Callout 11.1' Demo] (M2TS @ 1080p/24.000)
#[https://www.demolandia.net/downloads.php?id=69530805 DTS:X 'Listen X Long' Demo] (M2TS @ 1080p/24.000)
#[https://mega.nz/#!0NVhDIbY!D4Fte7Kb7728H9CRY3IVTHJ45ZwkCQiugdFS7pZCN_s DTS:X 'Movement' Demo] (M2TS @ 1080p/23.976) ''(thanks wesk05)''
#[https://mega.nz/#!Rcl1ECiL!pzPT5LvMyYIoKbsm3HdMDi2vO6aPpE8gAjLsSTH1DZg LPCM 5.1] (MKV @ 1080p/23.976) ''(thanks wesk05)''
#[https://drive.google.com/file/d/0BwxFVkl63-lEV2JjazFWQ05OSG8/view?usp=sharing LPCM 7.1] (MKV @ 1080p/23.976)
#[https://www2.iis.fraunhofer.de/AAC/multichannel.html AAC 5.1]
#FLAC 5.1 (use clip #6 in '3D Test Clips' section above)
#[https://drive.google.com/file/d/0B67BGVX7nHIlNlJBenpkQkhFXzA/view FLAC 5.1 24-bit 192kHz audio-only sample] ''(thanks HomerJau)''
#[http://www.2l.no/hires/index.html FLAC many formats]
#[https://www.cybele.de/geraete-software-download FLAC many formats] (bottom of page)

==Codecs, Framerates and Subtitles==

#[https://drive.google.com/file/d/0BwxFVkl63-lERkJRU003ZTd2VEk/view?usp=sharing H.264 1080p/23.976] (MKV)
#[https://drive.google.com/file/d/0BwxFVkl63-lEdzlZZ2lCLTVLa2c/view?usp=sharing H.264 1080p/24.000] (MKV)
#[https://drive.google.com/file/d/0BwxFVkl63-lEbFBzak1sbmU1N0E/view?usp=sharing H.264 1080i/25.000] (MKV)
#[https://drive.google.com/file/d/0BwxFVkl63-lEWDUzUVUtZEw4cDA/view?usp=sharing H.264 1080p/25.000] (MKV)
#[https://mega.nz/#!XI1yiKLA!rF4vweNo_xA7vpSzpLU-JctqfUGZN4vVU1m6WIJ5lT4 H.264 1080i/29.970 4:2:0@High 26Mbps] (C-Band satellite capture in MKV w/DTS-HD MA 2.0 audio, converted from E-AC3) ''(thanks alanisrox69)''
#[http://opencubetech.com/page47/ H.264 1080i/50.000] (download and change .mxf extension to .ts)
#[https://drive.google.com/file/d/0BwxFVkl63-lEbVptTVZ2NENURHM/view?usp=sharing H.264 1080p/50.000] (MKV)
#[https://drive.google.com/file/d/0BwxFVkl63-lEUGZnR1JHUUU0WEk/view?usp=sharing H.264 1080p/59.940] (MKV)
#[https://drive.google.com/file/d/0BwxFVkl63-lETTVtaVV0LUVRZ1k/view?usp=sharing H.264 1080p/60.000] (MKV)
#[https://drive.google.com/file/d/0BwxFVkl63-lETFVpOWRVVGNfeEU/view?usp=sharing VC-1 1080p/23.976] (MKV w/TrueHD 5.1 audio)
#[https://drive.google.com/file/d/0BwxFVkl63-lERnhlY1pHeW5wbjQ/view?usp=sharing VC-1 1080i/29.970] (MKV w/DTS-HD MA 5.1 audio)
#[https://drive.google.com/file/d/0BwxFVkl63-lETXlOa3hEMmVyZGM/view?usp=sharing MPEG2 1080i/29.970] (U.S. ATSC OTA capture, muxed into MKV w/DD5.1 audio)
#[https://mega.nz/#!GJMAADTK!deabwHlqtw2I_ihoY6_0xnxT_1W_d3jpAjnANKRBAzE MPEG2 4:2:0@High 1080i/29.970 36Mbps] (C-Band satellite capture in TS w/DTS-HD MA 5.1 audio, converted from E-AC3) ''(thanks alanisrox69 for #13-15)''
#[https://mega.nz/#!jREAxYgb!MtjBIh1oSJJBZgLT7AcdG88hGCFG-ak7pC2AyjrsaIQ MPEG2 4:2:0@High 720p/59.940 20Mbps] (C-Band satellite capture in TS)
#[https://mega.nz/#!c9dhAaKA!MG5Yi-MJNATE2_KqcnNJZCRKtTWvdjJP1NwG8Ggdw3E MPEG2 4:2:2@High 1080i/29.970 35Mbps] (C-Band satellite capture in TS w/DTS-HD MA 5.1 audio, converted from E-AC3) (most media players can't play this; Sigma SoC-based media players and Intel i3+ NUC's/HTPC's can)
#[https://www.dropbox.com/sh/6iy4gxgsfn14opq/AAAK_L1M_NwZwBPb5IkEPh7Ga?dl=0 Hi10 Anime Samples] ''(thanks Morien)''
#H.265 1080p (medium bitrate) Test #1 [https://drive.google.com/file/d/0B3-obtCH8dE8d04yQnY5ZkFJdVE/view?usp=sharing in ISO], and [https://drive.google.com/file/d/0B3-obtCH8dE8V0NXdi1Jd3NrNkk/view?usp=sharing in MKV] ''(thanks Mike for #16-17)''
#H.265 1080p (medium bitrate) Test #2 [https://drive.google.com/file/d/0B3-obtCH8dE8UnZiV2kyRGZEWW8/view?usp=sharing in ISO], and [https://drive.google.com/file/d/0B3-obtCH8dE8bFdvWVFUMlNjX0E/view?usp=sharing in MKV]
#[https://drive.google.com/file/d/0BwxFVkl63-lEbWhqS284RkpNMXc/view?usp=sharing 2D Forced Subtitles Sample #1 (SRT)]
#[https://drive.google.com/file/d/0BwxFVkl63-lEVEluSFZ4NlhpLUk/view?usp=sharing 2D Forced Subtitles Sample #2 (PGS)]
#3D Subtitles (use clip #2 in '3D Test Clips' section above)

==4K (UltraHD)==
{{note|To download, hover over link:
* If demo-world, click to go to site, then right-click thumbnail of video there & choose 'Save link as...' to download
* For any YouTube video, [https://www.4kdownload.com/products/product-videodownloader use this free tool] to download in original quality}}

#[https://drive.google.com/open?id=0BwxFVkl63-lEY3l3ODJReDg3RzQ H.264 29.970fps, 51Mbps] (in MOV, hdmkv's iPhone 6S raw 4K footage)
#[https://www.youtube.com/watch?v=Ppz41EmaJyU H.264 30.000fps] (in MP4, 4K Test Patterns) (YouTube) ''(thanks hansolo)''
#[http://demo-uhd3d.com/fiche.php?cat=uhd&id=111 H.264 50.000fps] (in MP4, Astra DVB satellite capture sample)
#[http://www.demo-world.eu/download-2d-trailers-uhd/?file=samsung_seven_wonders_of_the_world_china_uhd-DWEU.mkv&pic=samsung_seven_wonders_of_the_world_china.jpg H.264 59.940fps] (in MKV)
#[http://demo-uhd3d.com/fiche.php?cat=uhd&id=101 HEVC 8-bit 29.970fps] (in MP4)
#[http://demo-uhd3d.com/fiche.php?cat=uhd&id=45 HEVC 10-bit 23.976fps] (in TS)
#[http://demo-uhd3d.com/fiche.php?cat=uhd&id=96 HEVC 10-bit 59.940fps] (in TS)
#[https://drive.google.com/open?id=0BwxFVkl63-lEdVBuZkltckdZZ0k HEVC 10-bit 59.940fps] (Korean ATSC 3.0 satellite TV capture sample)
#[http://hdrsamples.com/ HDR 10-bit HEVC 24.000fps] (in MP4, 'Exodus' and 'Life of Pi' samples)
#[https://drive.google.com/open?id=0BwxFVkl63-lEdU9Ma0VYc3YxSVE HDR 10-bit HEVC 25.000fps] (in TS, Astra DVB satellite capture sample; no audio) ''(courtesy WeTek)''
#[http://demo-uhd3d.com/fiche.php?cat=uhd&id=144 HDR 10-bit HEVC 59.940fps] (in MP4, Camp by Sony)
#[https://drive.google.com/open?id=0BwxFVkl63-lEc3k0aldZaGtaVm8 DolbyVision 10-bit HEVC 23.976fps] (in TS, LG Comparison Demo) ''(thanks soyhakan)''
#[https://drive.google.com/open?id=0BwxFVkl63-lEWmNWcGl4eVRWS2M DolbyVision 10-bit HEVC 23.976fps] (in TS, LG Trailer) ''(thanks soyhakan)''
#[https://www.youtube.com/watch?v=s6zR2T9vn2c VP9] (open-source alternative to HEVC) (YouTube)
#[https://mega.nz/#!hJdFEIBI!uSOjZtkkjIVYSfqD9aSfONf1yq__uQvlsf47pCtFvdQ VP9 Profile 2 HDR #1] The World in HDR (in MKV, downloaded from YouTube) ''(thanks wesk05)''
#[https://mega.nz/#!pQEGgRwY!pD9whIlM-U9tJIA-LojxSt582BAZGfdSA5wAQLT06I4 VP9 Profile 2 HDR #2] The Redwoods (in MKV, downloaded from YouTube) ''(thanks wesk05)''
#[https://www.youtube.com/watch?v=nRt4Duf7GoI 5K (5120x2700) 60.000fps] (in MP4) (YouTube)
#[https://www.demolandia.net/downloads.php?id=60876578 HEVC 10-bit 23.976fps] (in MKV)
#[https://www.youtube.com/watch?v=ChOhcHD8fBA 8K (7680x4320) 29.970fps] (in MP4) (YouTube)
#[https://www.demolandia.net/downloads.php?id=73498539 HEVC 10-bit 23.976fps] (in MKV)
#[https://www.demolandia.net/downloads.php?id=99364567 HEVC 10-bit 23.976fps] (in MKV)

==Bitrate Test Clips==
Media players should be able play 70Mbps or better smoothly, w/o stutters for full 1080p, and 108-128Mbps for full 4K

*[http://jell.yfish.us/ Jellyfish, up to 400Mbps] (in H.264 and H.265 HEVC MKV) ''(thanks ScottAllyn01 for your useful site)''
*[http://dl.ganjanetwork.ru/Files/Video%20Test%20Files/Bitrate/Birds/ Birds, up to 90Mbps] (in H.264 MKV or M2TS)

==Resources for Additional Test Clips or Samples==

*[http://bbb3d.renderfarming.net/download.html Big Buck Bunny] (test suite with 2D, 3D and 4K clips)
*[http://www.cnx-software.com/2010/03/17/where-to-get-video-audio-and-image-samples/ CNXSoft's samples/links]
*[http://www.w6rz.net/ W6RZ MPEG2 clips]
*[http://thedigitaltheater.com/index.php/dolby-trailers/ The Digital Theater] (several Dolby ATMOS clips)
*[http://www.demo-world.eu/2d-demo-trailers-hd/ Demo World trailers] (several directly linked to above)
*[https://www.koi-sama.net/files/hi10/ AVC High 10 Profile Anime Samples] ''(thanks Morien)''
*[http://4ksamples.com/ 4Ksamples.com] (movie, sport, nature clips in 4K)
*[https://www.youtube.com/watch?v=k_okcNVZqqI&list=PLD33E5618740295DF Jacob + Katie Schwarz: We See the World in 4K] (beautiful 4K nature videos) (YouTube)
*[https://www.youtube.com/user/aroundtheworld4k Around the World 4K] (Cities worldwide in striking 4K) (YouTube)
*[https://www.youtube.com/channel/UCW35MLO96M_UVG7YzMt1I2A/videos Cities in 4K] (Similar to above) (YouTube)
*[https://www.youtube.com/channel/UC_3n6GTFuC4tTAojueLBTHg/playlists Manufacturer and other demos in 4K] (YouTube)
*[http://www.imaging-resource.com/news/2014/11/19/samsung-nx1-4k-video-samples-and-new-full-res-frame-grabs-available-for-do Imaging Resource 4K Samples] ''(thanks Karnis)''
*[https://www.youtube.com/channel/UCve7_yAZHFNipzeAGBI5t9g/videos The HDR Channel] (YouTube)
*[http://demo-uhd3d.com/ Demo UHD 3D] (various H.265 & H.265 4K clips) ''(thanks wrxtasy)''
*[https://x265.com/hevc-video-files/ x265 HEVC Samples]
*[http://www.evosiastudios.com/category/portfolio/films/ Evosia Studios] (several beautiful 1080p to 4K films)
*[http://www.libde265.org/downloads-videos/ libde265] (1080p to maxed-out 4K samples) ''(thanks Martijn)''
*[http://timestormfilms.net/ Timestorm Films] (4K to 8K videos)
*[http://samples.mplayerhq.hu/ MplayerHQ's library] (many clips)
::{{note|<code>http://samples.mplayerhq.hu</code> can even be added to Kodi as a video source, for easy loading, if you have a fast enough connection.}}
*[https://www.pc-magazin.de/ratgeber/hdr-tv-testfilm-testbild-kostenlos-download-3195250.html PC-Magazin.de/Ratgeber/hdr-tv-testfilm-testbild] (4K HDR / SDR test patterns with german description)

== Library samples ==

=== Ned's fake movie library ===
:A zipped collection of 1,000 empty movie files, with NFO files, poster, and fanart for each entry. Various movies from different years, including sequels/sets, remakes, movies named the same but unrelated, various genres, and so on. Useful for testing things like library scanning speed, library navigation, filtering, etc.

:* https://www.dropbox.com/s/llciqryeqqk4t70/Test%20video%20library.zip?dl=0

=== Music library ===
: Just the one album for now but hope to increase this over time. It's a complete album in MP3 format, tagged with Musicbrainz Picard ID3v2.3 (ID3v1 ID3v2.3) with extra genre, comment and composer tags for testing. Coverart is also included as a folder.jpg file. The album is licensed "Attribution-ShareAlike 3.0 Unported Creative Commons license" by the artist. You can download or pay for the album here if you like it. http://hungrylucy.com/album/pulse-of-the-earth

:* https://www.dropbox.com/s/rk8ue5fs49v5pnm/Creative_Commons_Music.zip?dl=0

=== Fake Sports TV Show library ===
: Here is a fake sports TV show library for use with the Kodi sports scraper. It includes a number of sports folders broken down into seasons and then events. This should work nicely with the current Sports TV scraper on the Kodi forums.

:* https://www.thesportsdb.com/Sports_fake_video_files.zip

=== Homebrew Games and Game ROMs ===
: These are locations to find a number of freely licensed "homebrew" games for classic consoles and stand-alone games that can be downloaded for testing with Kodi's upcoming [[Games|RetroRlayer]] feature. They include some homebrew games for NES, SNES, and GameBoy emulators, as well as a few homebrew game titles, such as; Cannonball, xrick, ChaiLove games and Lutro games.

:* https://github.com/OpenEmu/OpenEmu-Update/tree/master/Homebrew
:* https://buildbot.libretro.com/assets/cores/

== See also ==
* [[Video levels and color space]]

[[Category:Troubleshooting]]

Kodi v18 (Leia) changelog

2018-11-06T14:18:00Z

Gamester17: /* Live TV and PVR (Personal Video Recorder) */

{{mininav|[[Releases]] {{l2| [[Leia]] }} }}

{{notice|Kodi's journey via non-alpha/beta v18 (Leia) releases is currently underway. As such, these new features/functions and API changes is a placeholder containing changes to the current Kodi mainline (the git master tree repository on GitHub). This is listing changes committed to the master branch after Krypton branching. The many features/functions and API additions, alterations or removal are only subject to change during the Alpha stages. The Beta stage is all about stability and bug fixing. }}
{{incomplete}}
{{future|18}}

{{see also|Kodi v18 (Leia) FAQ|Leia API changes|Releases}}

This is the Kodi Wiki version of a condensed changelog for the future Kodi v18.x version (codename: "Leia") releases with a summary of the most important core features and functions as well as other notable changes to key areas of the application software or its user interface. Please note that this condensed changelog version is not meant bug-fixes, nor minor refactoring or cosmetic changes.

== Changelog ==

=== Gaming (Games interface and Game Clients)===
Note! Also see "Input System (Input Manager and Input APIs" section for Input System related to game controllers
* Added a "[[Games]]" window to GUI (games are managed using a basic file browser as a game library does not exist yet)
* Added a RetroPlayer player core supporting [[Game_Add-ons|game clients addons]] as well as emulator cores via [[libretro]] API<ref name="RetroPlayer">RetroPlayer http://forum.kodi.tv/showthread.php?tid=164725</ref><ref>http://github.com/xbmc/xbmc/pull/11022</ref>
* Added extentions to Kodi's Addons AP to support Game Client Addons, supporting Kodi's VFS (Virtual File System), etc.<ref name="RetroPlayer"/>
* Added support for Game Client Addons as new type of addons with just-in-time emulator installation<ref name="RetroPlayer"/>
* Added a Games window and Game OSD (On-Screen-Display) entries to the GUI<ref name="RetroPlayer"/><ref>https://github.com/xbmc/xbmc/pull/12367</ref>
* Added a gaming and game configuration interface for Game settings to the GUI<ref name="RetroPlayer"/>
* Added support for Game Info Tags (game info tag) and exposed properties to Python list items<ref name="RetroPlayer"/>
* Added a savestate (savestate) manager to Kodi for games<ref>http://github.com/xbmc/xbmc/pull/11034</ref>
* Added initial support for basic gameplay persistence (auto-save & auto-load)<ref>https://github.com/xbmc/xbmc/pull/12434</ref>
* Added support for in-game (save RAM) saves<ref>http://github.com/xbmc/xbmc/pull/11380</ref>
* Added support for Keyboard players via Joystick Emulation<ref name="RetroPlayer"/>
* Added Game API acbstraction for game controller multitaps (a.k.a. hubs) including topology GUI display<ref>https://github.com/xbmc/xbmc/pull/13499</ref>
* Added Game API acbstraction to support gamepad/joystick remapping for games (per game-addon)
* Added Game API acbstraction to support keyboard remapping for games (per game-addon)<ref>https://github.com/xbmc/xbmc/pull/13374</ref>
* Added Game API acbstraction to support mouse remapping for games (per game-addon)<ref>https://github.com/xbmc/xbmc/pull/13482</ref>
* Added support for libretro API and game cores (emulators and games) that support it as binary addons
* Added [[Game_Add-ons|game clients addons]] for many popular third-party game console emulators and native open source games *
** ''* [[Game_Add-ons|Game clients addons]] for Kodi is changing quickly so checkout the [[Game_Add-ons|game clients addons]] article for a current list''
* ?

=== Live TV and PVR (Personal Video Recorder) ===
* Added support for RDS (Radio Data System) for radio channels if the PVR backend client support RDS
* Added new settings for 'Startup action' and add 'Play TV/Radio <ref>https://github.com/xbmc/xbmc/pull/12548</ref>
* Added support for global direct channel number input & global unique channel numbers<ref>https://github.com/xbmc/xbmc/pull/13135</ref><ref>https://github.com/xbmc/xbmc/pull/11434</ref>
** Added support for no delay on switch to previous channel with key 0 when using direct channel number input<ref>https://github.com/xbmc/xbmc/pull/13232</ref>
* Added context menu support for Estuary (skin) PVR home screen widgets <ref>https://github.com/xbmc/xbmc/pull/10870</ref>
* Added percent played progress bar to PVR info panel (for recordings) in Estuary (skin)<ref>https://github.com/xbmc/xbmc/pull/13338</ref>
* Added Info support to recently played channel widget to Estuary (skin) home screen <ref>https://github.com/xbmc/xbmc/pull/12254</ref>
* Added episode name to Live TV, recordings OSD sub label, and cleanup seekbar for Live TV in Estuary (skin) <ref>https://github.com/xbmc/xbmc/pull/12306</ref>
* Added Season/Episode info in Guide window and dialog in Estuary (skin)<ref>https://github.com/xbmc/xbmc/pull/13300</ref>
* Added support for next and previous buttons in OSD Timeshift window<ref>https://github.com/xbmc/xbmc/pull/14387</ref>
* Added feature to prefill recordings folder with timer title in the timer settings dialog<ref>https://github.com/xbmc/xbmc/pull/11679</ref>
* Added support for radio channel groups to the channelgroup manager<ref>https://github.com/xbmc/xbmc/pull/11877</ref>
* Added support for a 'Smart selection' of EPG events feature to the guide window<ref>https://github.com/xbmc/xbmc/pull/11782</ref>
* Added 'Go to date' context menu item to the guide window<ref>https://github.com/xbmc/xbmc/pull/13282</ref>
* Added support for channel groups selector to the guide window<ref>https://github.com/xbmc/xbmc/pull/13364</ref>
* Added possibility to switch between horizontal and vertical epg grid view to the guide window <ref>https://github.com/xbmc/xbmc/pull/11958</ref>
* Added support to sort content by channel number/channel name/last played, support sort order to the Guide window<ref>https://github.com/xbmc/xbmc/pull/14231</ref>
* Added support next/previous chapter in PVR recordings<ref>https://github.com/xbmc/xbmc/pull/13164</ref>
* Improved PVR seekbar and info dialog in Estuary (skin) <ref>https://github.com/xbmc/xbmc/pull/13158</ref>
* Improved PVR info panel, info dialog, and recordings window in Estuary (skin)<ref>https://github.com/xbmc/xbmc/pull/12416</ref><ref>https://github.com/xbmc/xbmc/pull/13255</ref>
* Improved support for enabling multiple PVR client addons<ref>https://github.com/xbmc/xbmc/pull/12959</ref>
* Improved support for for subchannel numbers support (ATSC)<ref>https://github.com/xbmc/xbmc/pull/13069</ref>
* Improved OSD Timeshift GUI<ref>https://github.com/xbmc/xbmc/pull/14316</ref><ref>https://github.com/xbmc/xbmc/pull/14386</ref>
* Improved the guide window for better consistency and readability <ref>https://github.com/xbmc/xbmc/pull/13402</ref>
* Changed GUI actions to eliminate duplicate and dead code (major GUI refactoring for PVR and LiveTV)
* Changed implementation of EPG search filter (EPG search dialog) completely<ref>https://github.com/xbmc/xbmc/pull/11570</ref><ref>https://github.com/xbmc/xbmc/pull/12001</ref>
* Changed Guide Window removing obsolete views "channel", "now" and "next"<ref>https://github.com/xbmc/xbmc/pull/10838</ref>
* Changed "play minimized" settings handling <ref>https://github.com/xbmc/xbmc/pull/11203</ref>
* Changed 'epg.lingertime' to an official setting, remove the respective advanced setting<ref>https://github.com/xbmc/xbmc/pull/12740</ref>
* Changed shared channel selection into an optional setting<ref>https://github.com/xbmc/xbmc/pull/13237</ref>
* Removed obsolete and unused setting 'pvrplayback.scantime' <ref>https://github.com/xbmc/xbmc/pull/12800</ref>
* Removed channel guide button from EPG event info dialog, add 'channel guide' to context menu<ref>https://github.com/xbmc/xbmc/pull/12526</ref>
* Removed setting 'hide connection lost warning' <ref>https://github.com/xbmc/xbmc/pull/11500</ref>
* Removed non-working recording settings defaults <ref>https://github.com/xbmc/xbmc/pull/11746</ref>
* Recordings window: Content view filter <ref>https://github.com/xbmc/xbmc/pull/11704</ref>
* PVR-Addon API changes <ref>https://github.com/xbmc/xbmc/pull/12028</ref><ref>https://github.com/xbmc/xbmc/pull/12303</ref><ref>https://github.com/xbmc/xbmc/pull/12552</ref><ref>https://github.com/xbmc/xbmc/pull/12609</ref><ref>https://github.com/xbmc/xbmc/pull/12660</ref><ref>https://github.com/xbmc/xbmc/pull/12689</ref><ref>https://github.com/xbmc/xbmc/pull/12755</ref><ref>https://github.com/xbmc/xbmc/pull/13228</ref><ref>https://github.com/xbmc/xbmc/pull/13720</ref><ref>https://github.com/xbmc/xbmc/pull/14002</ref><ref>https://github.com/xbmc/xbmc/pull/14086</ref>
* Added, updated, and improved PVR backend clients addons for popular third-party external [[PVR backend]] platforms:
** New: [[Add-on:Zattoo PVR Client|Zattoo PVR Client]] PVR Addon backend client maintained and available from Kodi's community
** New: [[Add-on:Teleboy PVR Client|Teleboy PVR Client]] PVR Addon backend client maintained and available from Kodi's community
** New: [[Add-on:Sledovanitv.cz PVR Client|Sledovanitv.cz PVR Client]] PVR Addon backend client maintained and available from Kodi's community
** [[Add-on:PVR Demo Client|PVR Demo Client]] dummy addon with fake (method stub) [[PVR backend]] for [[PVR]] skinning and regression testing
** [[Add-on:IPTV Simple Client|IPTV Simple Client]] PVR Addon backend client maintained and available from Kodi's community
** [[Add-on:FilmOn PVR Client|FilmOn]] PVR Addon backend client maintained and available from Kodi's community
** [[Add-on:Stalker Client|Stalker Middleware]] PVR Addon backend client maintained and available from Kodi's community
** [[Add-on:HDHomeRun PVR|HDHomeRun]] PVR Addon backend client maintained and available from Kodi's community
** [[Add-on:Digital Devices Octopus NET Client|Digital Devices Octopus NET Client]] PVR Addon backend client maintained and made available by [http://digitaldevices.de/home/ Digital Devices]
** [[Add-on:VU+ / Enigma2 Client|Enigma2 (Dreambox / Vu+ / DBox2)]] PVR Addon backend client maintained and available from Kodi's community
** [[Add-on:VBox TV Gateway PVR Client|VBox TV Gateway]] PVR Addon backend client maintained and available from Kodi's community
** [[Add-on:Njoy N7 PVR Client|Njoy Digital (N7)]] PVR Addon backend client maintained and available from Kodi's community
** [[Add-on:PCTV Systems Client|PCTV Systems (Broadway)]] PVR Addon backend client maintained and available from Kodi's community
** [[Add-on:Tvheadend HTSP Client|Tvheadend HTSP Client]] PVR Addon backend client maintained and available from Kodi's community
** [[Add-on:VDR VNSI Client|VDR VNSI Client]] PVR Addon backend client maintained and available from Kodi's community
** [[Add-on:MythTV PVR Client|MythTV PVR Client]] Addon backend client maintained and available from the Kodi's community
** [[Add-on:NextPVR PVR Client|NextPVR (former GB-PVR)]] PVR Addon backend client maintained and available from Kodi's community
** [[Add-on:Argus TV Client|Argus TV (former ForTheRecord)]] PVR Addon backend client maintained and available from Kodi's community
** [[Add-on:DVBLink PVR Client|DVBLink PVR Client]] Addon backend client maintained and available from Kodi's community
** [[Add-on:DVBViewer Client|DVBViewer Client]] PVR Addon backend client maintained and available from Kodi's community
** [[Add-on:MediaPortal PVR Client|MediaPortal PVR Client]] Addon backend client maintained and available from Kodi's community
** [[Add-on:PVR.WMC|WMC (Windows Media Center)]] PVR Addon backend client maintained and available from Kodi's community
* ?

=== Add-ons Framework, API, and Manager ===
For full changelogs of all Addons APIs, see [[Leia API changes]], [https://forum.kodi.tv/showthread.php?tid=324598 JSON-RPC], and [http://forum.kodi.tv/forumdisplay.php?fid=26 Add-ons] Development Forums
* Implemented a Python 3 interpreter inside Kodi (plus enforcing Python 2 & 3 compatibility in Leia addon repository)<ref>https://kodi.tv/article/attention-addon-developers-migration-python-3</ref>
* Implemented online binary addon repository from which Kodi can now automatically installs/updates binary addon<ref>https://kodi.tv/article/kodi-v18-binary-add-ons-repository</ref><ref>https://github.com/xbmc/repo-binary-addons</ref>
* Major refactoring of Kodi's core handling and GUI management of binary addons<ref>http://github.com/xbmc/xbmc/pulls?q=label%3A%22Binary+Addons%22+is%3Aclosed</ref>
* Added framework to support VFS (Virtual File System) as binary addons<ref>http://github.com/xbmc/xbmc/pull/8966</ref>
* Added framework support for binary addons for video decoder codecs<ref name="Addon video codec implementation">https://github.com/xbmc/xbmc/pull/12340</ref>
* Added framework support for binary addons for image (picture) decoder codecs
* Added extentions to Kodi's Addons API to support binary addons for video decoder codecs<ref name="Addon video codec implementation"/>
* Added extentions to Kodi's Addons API to support binary addons for image decoder codecs
* Added support for Python addons to use PyCryptoDome crypto module for decryption<ref>https://github.com/xbmc/xbmc/pull/11477</ref>
* Added option to pass HTTP cookies with AVOption to Kodi's Video Player<ref>https://github.com/xbmc/xbmc/pull/12257</ref>
* Added support to allow addons to edit all used controls on their processed window<ref>https://github.com/xbmc/xbmc/pull/12259</ref>
* Added support to allow Python addons to set the videoinfotag path<ref>http://github.com/xbmc/xbmc/pull/11012</ref>
* Added support to allow Python addons to get/set the dbid of a (music) listitem<ref>http://github.com/xbmc/xbmc/pull/10858</ref>
* Added support for mediatype to musicinfotag tag retrieving via Python API<ref>http://github.com/xbmc/xbmc/pull/11110</ref>
* Added support "int/float slider" to Kodi's Python API<ref>http://github.com/xbmc/xbmc/pull/11230</ref>
* Added support "setContent for mediawindows" to Kodi's Python API<ref>http://github.com/xbmc/xbmc/pull/11258</ref>
* Added help for load of shared library and allow the use of their own addon temp folder<ref>https://github.com/xbmc/xbmc/pull/12379</ref>
* Added support to inspect add-on dependencies prior to installation<ref>https://github.com/xbmc/xbmc/pull/12242</ref>
* Added ability to remove add-on settings upon uninstall<ref>https://github.com/xbmc/xbmc/pull/11499</ref>
* Changed to new addon gui interface for list items to use on addon window<ref>https://github.com/xbmc/xbmc/pull/12214</ref>
* Changed service addons to use event handlers instead of synchronous addon hooks<ref>https://github.com/xbmc/xbmc/pull/12370</ref>

=== Input System (Input Manager and Input APIs) ===
* Improved the input manager and input API system for keyboards, mouses, and game controllers<ref name="Controller input system">PR #8807 Controller input system http://github.com/xbmc/xbmc/pull/8807</ref>
* Updated "Peripheral Addons" for game controllers, gamepads, joysticks, and input peripherals profiles (in Kodi-game repo<ref>http://github.com/kodi-game/ kodi-game repo on GitHub</ref>):
** [http://github.com/xbmc/peripheral.joystick Joystick Controller Addon]
** [http://github.com/kodi-game/peripheral.xarcade X-Arcade (XGaming Tankstick) support for Kodi Addon]
** [http://github.com/kodi-game/peripheral.steamcontroller Steam Controller (gamepad) Addon]
** [http://github.com/kodi-game/kodi-game-controllers/tree/master/addons/game.controller.default Default Game Controller Addon (reference game controller addon based on Xbox 360 gamepad)]
*** [https://github.com/kodi-game/controller-topology-project/tree/master/addons PlayStation Game Controller Addon]
*** [https://github.com/kodi-game/controller-topology-project/tree/master/addons Nintendo NES Game Controller Addon]
*** [https://github.com/kodi-game/controller-topology-project/tree/master/addons Nintendo SNES Game Controller Addon]
*** [https://github.com/kodi-game/controller-topology-project/tree/master/addons Nintendo N64 Game Controller Addon]
*** [https://github.com/kodi-game/controller-topology-project/tree/master/addons Nintendo GBA Game Controller Addon]
*** [https://github.com/kodi-game/controller-topology-project/tree/master/addons Sega Genesis Game Controller Addon]
*** [https://github.com/kodi-game/controller-topology-project/tree/master/addons Sega Dreamcast Game Controller Addon]
* ?

=== GUI Engine (Skinning Engine) ===
For full changelog on changes to the skinning engine, see [[Leia API changes]] and the [http://forum.kodi.tv/showthread.php?tid=298565 Skin Development Forum]
* Added windows to support Games and Game OSD in the new default skins (Estuary and Estouchy)
* Added player process info dialog to Kodi's default skin (Estuary)<ref>https://github.com/xbmc/xbmc/pull/11718</ref>
* Added support for addons to use banner and ClearLogo<ref>https://github.com/xbmc/xbmc/pull/12244</ref>
* Added support for skins/gui to allow implicit container referencing for non-media windows<ref>http://github.com/xbmc/xbmc/pull/10883</ref>
* Added support for addons to add "Enable/Disable" to context menu<ref>http://github.com/xbmc/xbmc/pull/11124</ref>
* Added support for remember last used keyboard layout in GUI<ref>http://github.com/xbmc/xbmc/pull/11242</ref>
* Added support for ISO 639-2/T language code retrieval (required by libbluray)<ref>https://github.com/xbmc/xbmc/pull/12258</ref>
* Added window that display Kodi privacy policy in GUI settings under system info<ref>https://github.com/xbmc/xbmc/pull/10785</ref>
* Added support to map a key to browse for subtitle in video fullscreen window<ref>https://github.com/xbmc/xbmc/pull/11649</ref>
* Improved Kodi's GUI engine with optimizations for message handling and SmartRedraw<ref>https://github.com/xbmc/xbmc/pull/12213</ref>
* Improved Kodi's GUI engine support for scaling container layouts<ref>http://github.com/xbmc/xbmc/pull/11229</ref>
* Improved Kodi's GUI engine by allowing %-values for origin, camera and animation attribs<ref>http://github.com/xbmc/xbmc/pull/11233</ref>
* Changed so that context menu reloading loads async to aviod GUI lockup on wait<ref>https://github.com/xbmc/xbmc/pull/11841</ref>
* Updated guilib ABI (for libgui) to version 5.13.0<ref>http://github.com/xbmc/xbmc/pull/11306</ref>
* Updated keyboard layout for some languages and added support Croatian, Slovenian, and Thai (Kedmanee)
* Updated image resource addons (as example weather icons, weather fanart, studio logos, and genre icons)
* ?

=== Platform Independent Playback ===
* Added support for "InputStream" (input stream) addons to pass CryptoSession flags field<ref>https://github.com/xbmc/xbmc/pull/12428</ref>
* Added support for BD-J / Blu-ray Disc Java menu support (requires system Java runtime enviroment)<ref>https://github.com/xbmc/xbmc/pull/12339</ref><ref>https://github.com/xbmc/xbmc/pull/12310</ref>
* Added support for Blu-ray Disc detection and use provided meta data for Blu-ray Disc names<ref>https://github.com/xbmc/xbmc/pull/12488</ref>
* Added support for video buffers to be used by decoders and renderers<ref name="VideoPlayer updates for Leia">https://github.com/xbmc/xbmc/pull/12212</ref>
** Added support for platforms to register custom buffers, like example dma<ref name="VideoPlayer updates for Leia"/>
* Added a VC1-Packet bitstream parser implementation for improved VC-1 playback<ref>http://github.com/xbmc/xbmc/pull/11417</ref>
* Added and updated many (binary) audio decoder and encoder addons for Kodi
* Added a few (binary) video decoder addons for Kodi<ref name="Addon video codec implementation"/>
* Added a "RAW" (libraw based) image decoder addon to Kodi<ref>https://github.com/xbmc/xbmc/pull/11671</ref>
* Improved MMAL playback of H.264 MVC (Blu-ray 3D) stereoscopic video with framepacking decoding on Raspberry Pi
* Improved Stereoscopic 3D playback of 3D videos (as well as better 2D playback of 3D videos)
* Improved and enhanced Blu-ray support (including updated libbluray dependecies from the VideoLAN project<ref>https://github.com/xbmc/xbmc/pull/12305</ref><ref>http://git.videolan.org/?p=libbluray.git;a=blob;f=ChangeLog</ref>
* Improved support for "InputStream" (input stream) addons as system addons
* Updated "InputStream" (input stream) client addons for common network streaming protocols and popular services:
** [http://github.com/xbmc/xbmc/tree/master/addons/kodi.inputstream InputStream Addon (default reference InputStream Addon by Team Kodi]
** [http://github.com/mapfau/inputstream.test Test InputStream Addon (Test InputStream Addon for Kodi's new inputstream interface]
** [http://github.com/peak3d/inputstream.adaptive Adaptive InputStream Addon (InputStream Client addon for several manifest types)]
** [http://github.com/xbmc/repo-binary-addons/tree/master/inputstream.rtmp RTMP InputStream Addon (InputStream Client for RTMP streams using librtmp)]
** [http://github.com/peak3d/inputstream.mpd MPD (MPEG-DASH) InputStream Addon]
** [http://github.com/peak3d/inputstream.smoothstream SmoothStream InputStream Addon for MS-SSTR (SmoothStreamingMedia) Smooth Streaming Protocol]
** [http://github.com/mapfau/inputstream.nxmsl NXMSL InputStream Addon for Netflix style manifests over MSL]
* Updated FFmpeg multimedia codec and demux libraries to stable branch release version [http://www.ffmpeg.org/download.html#release_4.0.2 FFmpeg 4.0 (4.0.2)]<ref>http://git.videolan.org/?p=ffmpeg.git;a=blob_plain;f=Changelog;hb=release/4.0.2 FFmpeg 4.0.2 release changelog</ref><ref>https://github.com/xbmc/xbmc/pull/14212</ref>
* Removed certain audio codecs from core and made them into audio decoder and audio encoder binary add-ons
* Removed certain video codecs from core and made them into video decoder binary add-ons<ref name="Addon video codec implementation"/>
* Removed certain image codecs from core and made them into image decoder binary add-ons
* ?

=== General Library ===
* Added support to use the Favourites function in context menus<ref>https://github.com/xbmc/xbmc/pull/11967</ref>
* Added support for context menus to favourites home screen widget<ref>https://github.com/xbmc/xbmc/pull/11929</ref>
* Added support to "Sort By Date Added" in Music Video title node<ref>https://github.com/xbmc/xbmc/pull/12495</ref>

=== Music Library ===
* Added an option to rescan the music file tags for existing items in the library <ref>https://github.com/xbmc/xbmc/pull/11557</ref>
* Added processing of WRITER tag for ID3 v2, Vorbis and APE formats <ref>https://github.com/xbmc/xbmc/pull/11735</ref>
* Added processing of ARTISTSORT (TSOP), ALBUMARTISTSORT (TS02) and COMPOSERSORT (TSOC) tags to provide a sort name for artists. <ref>https://github.com/xbmc/xbmc/pull/11738</ref>
* Added a new dialog for selection of both artist and album scraper addons, and their settings.<ref>https://github.com/xbmc/xbmc/pull/12987</ref><ref>https://github.com/xbmc/xbmc/pull/12943</ref>
* Added additional artist data that Musicbrainz provides: type (person, group, orchestra, choir etc.), gender, and disambiguation comments that help to differentiate artists with the same name <ref>https://github.com/xbmc/xbmc/pull/12963</ref>
* Added an Artist Information Folder - a single location for artist artwork and nfo. This solves numerous issues related to artwork, artist data import and general folder and file structure <ref>https://github.com/xbmc/xbmc/pull/12891</ref>
* Added support for Extended Artwork, making the local art that is picked up automatically on scan configurable. <ref>https://github.com/xbmc/xbmc/pull/13352</ref><ref>https://github.com/xbmc/xbmc/pull/13848</ref><ref>https://github.com/xbmc/xbmc/pull/13491</ref><ref>https://github.com/xbmc/xbmc/pull/13101</ref><ref>https://github.com/xbmc/xbmc/pull/13871</ref>
* Added an option to prefer scraped album covers to embedded images <ref>https://github.com/xbmc/xbmc/pull/13812</ref>
* Added a filter to sort music items by media source <ref>https://github.com/xbmc/xbmc/pull/14012</ref><ref>https://github.com/xbmc/xbmc/pull/14082</ref>
* Improved use of BAND and ENSEMBLE (Vorbis and APE) tags. <ref>https://github.com/xbmc/xbmc/pull/11735</ref>
* Improved handling of duplicate MusicBrainzTrackID within the same album<ref>https://github.com/xbmc/xbmc/pull/12079</ref>
* Improved handling of Cue Sheets<ref>https://github.com/xbmc/xbmc/pull/12082</ref>
* Improved online scraping of additional artist and album information making better use of Musicbrainz IDs<ref>https://github.com/xbmc/xbmc/pull/12120</ref><ref>https://github.com/xbmc/xbmc/pull/12597</ref>
* Improved on clean installs, change default song sort order to Track Number <ref>https://github.com/xbmc/xbmc/pull/12834</ref>
* Improved FileItem::IsSamePath for albums and artists to prevent false matches<ref>https://github.com/xbmc/xbmc/pull/13585</ref>
* Improved album genre inconsistencies<ref>https://github.com/xbmc/xbmc/pull/13042</ref>
* Improved performance by avoiding unnecessary db access by GUI when app processing GUI_MSG_UPDATE_ITEM messages<ref>https://github.com/xbmc/xbmc/pull/13640</ref>
* Improved support for fetching local art for multi-folder albums (disc sets) <ref>https://github.com/xbmc/xbmc/pull/13769</ref>
* Changed Artist/Album Information Dialog <ref>https://github.com/xbmc/xbmc/pull/13672</ref>
* Changed Song Information Dialog <ref>https://github.com/xbmc/xbmc/pull/13533</ref>

=== Web Scrapers ===
* Added support for Python (script) based web scrapers for Kodi<ref>http://github.com/xbmc/xbmc/pull/9984</ref>
* Refactored and updated many XML based scrapers in Kodi for music, movies, tv shows, and music videos
* Updated music, movies, tv shows, and music video scrapers for Kodi
* ?

=== AudioEngine ===
* Added a new Sndio sink for [[AudioEngine#ActiveAE|ActiveAE]] for BSD, other BSD Unix based systems, and Linux<ref>https://github.com/xbmc/xbmc/pull/11962</ref>
* Improved the default cross-platform event driven active state machine pattern [[AudioEngine#ActiveAE|ActiveAE]] (Kodi's [[AudioEngine]])
* Improved ALSA sink for [[AudioEngine#ActiveAE|ActiveAE]] for Linux Desktop and generic Linux based Embedded Systems
* Improved PulseAudio sink for [[AudioEngine#ActiveAE|ActiveAE]] for Linux Desktop
* Improved OSS (Open Sound System) sink for [[AudioEngine#ActiveAE|ActiveAE]] for BSD, like FreeBSD and similar BSD Unix based systems
* Improved AUDIOTRACK sink for [[AudioEngine#ActiveAE|ActiveAE]] for [[Amlogic]]
* Improved Pi Audio sink for [[AudioEngine#ActiveAE|ActiveAE]] for [[Raspberry Pi]]
* Improved DirectSound sink for [[AudioEngine#ActiveAE|ActiveAE]] for Windows
* Improved WASAPI sink for [[AudioEngine#ActiveAE|ActiveAE]] for Windows
* Improved CoreAudio sink for [[AudioEngine#ActiveAE|ActiveAE]] for (Mac) OS X and iOS
* Improved Darwin sink for [[AudioEngine#ActiveAE|ActiveAE]] for (Mac) OS X and iOS
* Renamed AE_SINK to KODI_AE_SINK
* ?

=== Other ===
* Added a new unified setting for "Startup action" and added "Play TV/Radio"<ref>https://github.com/xbmc/xbmc/pull/12548</ref>
* Added support to build Kodi with support for Bluetooth<ref>http://github.com/xbmc/xbmc/pull/11137</ref>
* Added possibility for CMake build system to add additional libraries on install<ref>https://github.com/xbmc/xbmc/pull/12423</ref>
* Added and updated many audio visualization and screensaver addons for Kodi<ref>https://github.com/xbmc/repo-binary-addons</ref>
* Improved Kodi's JSON-RPC API
* Improved code stability, performance. and security, as well as general code clean-up in many core areas
* Improved compiling/building and code documentation (following doxygen coding guidelines)
* Changed to use spdlog for Kodi logging as well as improved and further optimized logging (including debug logs)<ref>https://github.com/xbmc/xbmc/pull/11833</ref>
* Changed XML format of setting values for Kodi's settings configuration<ref>https://github.com/xbmc/xbmc/pull/12277</ref>
* Updated and improved mappings for new and existing remote controls
* Updated default web interface (webinterface is called "Chorus2" and is currently at version 2.4.4)<ref>https://github.com/xbmc/xbmc/pull/11872</ref>
* Updated critical dependency libraries such as openssl, gnutls, and CMake (used to compile Kodi and its binary addons)
* Removed last dependencies of SDL (Simple DirectMedia Layer) which was hardware abstraction for input devices<ref>https://github.com/xbmc/xbmc/pull/12272</ref><ref>https://github.com/xbmc/xbmc/pull/11881</ref>
* Removed all glew (libglew library) dependencies in Kodi's code<ref>http://github.com/xbmc/xbmc/pull/11128</ref>
* ?

=== Android Specific ===
* Moved to Android API 26 and SDK 26 with NDK 18 as minimum (meaning at least Android 5.0 is still required)
* Added support for speech-to-text in Kodi OSD keyboard on Android TV (triggered by voice button on remote)
* Added support for Android to move the Kodi app to SD card<ref>https://github.com/xbmc/xbmc/pull/12168</ref>
* Added support for Android TV Leanback search and recommendations meta data from Kodi<ref>|https://github.com/xbmc/xbmc/pull/11901</ref>
** Default setting for Android TV Leanback suggestion to random unwatched movies and music albums<ref>https://github.com/xbmc/xbmc/pull/11963</ref>
* Changed Rendertype from GUILayer to VideoLayer for Android MediaCodecSurface<ref>https://github.com/xbmc/xbmc/pull/12097</ref>
* Changed to use NDK native C interface for Android MediaCodec (for performance gains)<ref>https://github.com/xbmc/xbmc/pull/11931</ref>
* Changed to support ZeroConf via native Android API (and deprecates mDNSresponder)<ref>http://github.com/xbmc/xbmc/pull/11393</ref>
* Changed to support network information via native Android API (and deprecates POSIX)<ref>https://github.com/xbmc/xbmc/pull/12243</ref>
* Changed handling of Kodi's Java interfaces via JNI for better consistency<ref>https://github.com/xbmc/xbmc/pull/12292</ref>
* ?

=== BSD Specific ===
* Improved Kodi support for [http://en.wikipedia.org/wiki/Berkeley_Software_Distribution BSD (operating system)] on FreeBSD, PC-BSD, and other similar BSD platforms
* Improved VAAPI (Video Acceleration API) support (requires VAAPI compatible hardware and drivers)
* Improved VDPAU (NVIDIA) Hardware Video Acceleration (requires VDPAU compatible hardware and drivers)
* ?

=== Linux Specific ===
* Added support for a generic DRM/KMS implementation using GBM to create surfaces and V4L2 for video acceleration<ref>https://github.com/xbmc/xbmc/pull/11955</ref>
* Added support for Mir windowing system (Mir 1.0) for Kodi<ref>http://github.com/xbmc/xbmc/pull/10898</ref> and added support for VAAPI on Mir using DRM<ref>http://github.com/xbmc/xbmc/pull/11040</ref>
* Added support for the middle mouse button on embedded platforms<ref>https://github.com/xbmc/xbmc/pull/11956</ref>
* Added support more yuv420p bitwidths for direct rendering on Linux<ref>https://github.com/xbmc/xbmc/pull/12479</ref>
* Added support for using VAAPI hardware video decoding with OpenGL ES<ref>https://github.com/xbmc/xbmc/pull/12113</ref>
* Added support for build Kodi with imx support using CMake<ref>http://github.com/xbmc/xbmc/pull/11288</ref>
* Moved the CMake build system to the top of the code tree (moved to root)<ref>http://github.com/xbmc/xbmc/pull/10446</ref>
* Improved support for UltraHD decoding / 4K resolution output when hardware supports it
* Improved ARM processor architecture (using [[Raspberry Pi]] as reference device)
* Improved OpenGL ES and EGL support (using [[Raspberry Pi]] as reference device)
* Improved VAAPI (Video Acceleration API) support (requires VAAPI compatible hardware and drivers)
* Improved VDPAU (NVIDIA) Hardware Video Acceleration (requires VDPAU compatible hardware and drivers)
* Improved XvBA (AMD/ATI) Hardware Video Acceleration (requires XvBA compatible hardware and drivers)
* Improved dedicated AMLCodec hardware accelerated video decoding support for Linux on Amlogic devices
* Removed the unused and unmaintained OpenMAX video decoder from Kodi's VideoPlayer<ref>https://github.com/xbmc/xbmc/pull/12197</ref>
* Removed support for autotools based build system for Kodi and binary addons (in favour of CMake)<ref>http://github.com/xbmc/xbmc/pull/10429</ref>
* ?

=== iOS Specific ===
* Added support for iOS 10.0 by adding support for compiling Kodi with Xcode 8 IDE and iOS SDK 10.0<ref>https://github.com/xbmc/xbmc/pull/10539</ref>
* Improved Apple VDADecoder Video Acceleration support for iOS (on iPad, iPhone, and iPod iDevices)
* Improved support for TVOS (Apple's iOS fork for Apple TV 4) in Kodi mainline
* Improved support for iOS on ARM64 (64-bit iOS)
* ?

=== OS X Specific ===
* Added support for compiling Kodi with Xcode 8 IDE for OSX 10.11 (El Capitan) and macOS 10.12 (Sierra)
* Improved Apple VDADecoder Video Acceleration support for (Mac) OS X
* ?

=== Windows Specific ===
* Added support to build Kodi for Windows 64 / Windows for Intel 64-bit (x86-64)<ref>https://github.com/xbmc/xbmc/pull/12065</ref>
* Added support for 3D LUT (3D Lookup Table) and dithering to Windows video renderer<ref name="WinRenderer re-work">https://github.com/xbmc/xbmc/pull/12475</ref>
* Improved support to compiling Kodi for Microsoft's UWP (Universal Windows Platform) APIs
* Changed the inner working of render buffers and rendering methods<ref name="WinRenderer re-work"/>
* Changed to using unicode win32 api methods<ref>https://github.com/xbmc/xbmc/pull/11780</ref>
* Changed windowing systems for screen saver handling on Windows OS platforms
* Changed to make Kodi for Windows platform independent of posix/main.cpp<ref>https://github.com/xbmc/xbmc/pull/12215</ref>
* Removed support for Windows Vista as the operating-system is no longer supported by Microsoft<ref>https://github.com/xbmc/xbmc/pull/11953</ref>
* ?

== References ==
<references/>

== See also ==
* [[Leia API changes]]
{{Changelogs}}

[[Category:Manual]]
[[Category:Leia|*]]
[[Category:Changelogs|18]]

Script sources

2018-10-26T18:25:02Z

Gamester17:

{{mininav|[[Development]]|[[Add-on development]]|[[Python development]]}}
==What Kodi requires for your add-on==
For XBMC to know what to do with your addon, we require your script, and an addon.xml file. See [[Add-ons for XBMC (Developement)|add-ons for XBMC]] for more information on addon.xml, including how you add descriptions to your addon for users. A script extends XBMC via the xbmc.python.script extension point. The layout of the XML describing this extension point is as follows:

<syntaxhighlight lang="xml" enclose="div">
<extension point="xbmc.python.script"
library="default.py" />
</syntaxhighlight>

list of extension points and their explanation:

"xbmc.python.script" This is the standard Script extension point

below listed extensions will not appear in the Scripts/Programs window and can only be run via skin shortcuts

"xbmc.python.weather" Used for weather scripts
"xbmc.python.subtitles" Used for subtitle scripts
"xbmc.python.lyrics" Used for lyrics scripts
"xbmc.python.library" Used for skin dependent scripts (e.g. recently added script)

Example of "xbmc.python.script":
<syntaxhighlight lang="xml" enclose="div">
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<addon id="script.rss.editor"
name="RSS Editor"
version="1.5.6"
provider-name="rwparris2">
<requires>
<import addon="xbmc.python" version="1.0"/>
</requires>
<extension point="xbmc.python.script"
library="default.py" />
<extension point="xbmc.addon.metadata">
<platform>all</platform>
<minversion>28764</minversion>
<summary lang="en">A Script for editing XBMC's built in RSS Ticker</summary>
<description lang="en">A Script for editing XBMC's built in RSS Ticker</description>
</extension>
</addon>
</syntaxhighlight>

== Interacting with XBMC ==
Given that your script can return information to the user, you may wish to allow some (or all) of the information you provide to be translatable. You do this by providing a strings.xml file (in resources/language/<name_of_language>/strings.xml) which associates integer id's with each label. XBMC then handles loading these string files and ensuring that the users' locale information is taken into account. To display strings you use the '''getString''' function in the [[xbmcaddon module]].

== See also ==
* [[Add-ons]]
* [[:Category:All add-ons]]
* [[Unofficial add-on repositories]]
'''Development:'''
* [[Add-on development]]
* [[Addon Settings]]
* [[Python development]]
* [[Add-on repositories]]
* [[Official add-on repository]]

[[Category:Python Tutorial]]
[[Category:Python]]
[[Category:Settings]]
[[Category:How-to]]
[[Category:Add-ons]]
[[Category:Add-on development]]
[[Category:Development]]

Add-on repositories

2018-10-26T18:24:43Z

Gamester17:

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

{{see also|HOW-TO: Create a Repository to host your Add-on}}

Beginning with Dharma, Kodi includes an interface to browse remote repositories where add-ons can be retrieved. The model is similar to the way many current Linux distributions work, whereby there is a "main" repository that is the default, and additional ones may be added by the user. The [[Official Add-on Repository]] is included with Kodi by default and is maintained by the Kodi team.

After you have created your repository, consider adding it to the [[Unofficial add-on repositories]] list.

== Ingredients for a Repository ==
Repositories were created with the idea that they should be simple and easy enough to setup for anyone interested. The basic requirements are as follows:

* An HTTP server. Any should work.
* Some add-ons.
* A master xml file. This file contains metadata about all available add-ons.
* A checksum of the above file.
* A repository add-on for distribution. This allows you to share your repository with others.

== Directory Structure ==
addon.id
addon.id-x.y.z.zip
...
addon2.id
addon2.id-x.y.z.zip
...

In addition, each add-on directory should contain icon.png, fanart.jpg, changelog-x.y.z.txt and all files from the [[Addon.xml#.3Cassets.3E]] element.

* addon.id should be the same as the addon's id, which is expected to be unique.
* x.y.z is the addon's version, the same should be listed in its version attribute.

== Addons.xml ==
Kodi expects to fetch a master xml file that contains the information for each add-on inside the repo. This file is named addons.xml - it can be placed external to the main repository of add-on files if you wish. This file merely encapsulates the other addon.xml files in an <addons> tag. See below for the basic structure:
<syntaxhighlight lang="xml" enclose="div">
<?xml version="1.0" encoding="UTF-8"?>
<addons>
<addon
id="sample.addon1"
...
</addon>

<addon
id="sample.addon2"
...
</addon>
</addons>
</syntaxhighlight>

== Repository Add-on ==
Repositories are distributed just like any other add-on. In order for you to browse one in Kodi, you'll need to [[Add-ons for Kodi (Developement)|create an add-on]] and install it. The repository addon extends the xbmc.addon.repository extension point, so in addition to the general XML structure, you'll need an 'extension' block as follows:
<syntaxhighlight lang="xml" enclose="div">
<extension point="xbmc.addon.repository">
<info>https://example.com/addons/addons.xml</info>
<checksum>https://example.com/addons/addons.xml.md5</checksum>
<datadir>https://example.com/addons/</datadir>
</extension>
</syntaxhighlight>

=== info ===
URL to the main xml file.

When fetching the file, Kodi will request a gzip encoded response. If the server for some reason does not support gzip encoding, it ''may'' be pre-gzipped, in which case it must have a .gz ending ending.

Note: Kodi v15 and older do not support pre-gzipped files and must specify the attribute compressed="true" to request gzip content encoding.

=== checksum ===
A text file that identifies the content of <code><info></code>.

Before fetching the full info file, Kodi will fetch the "checksum" and compare it to the previously fetched one. If changed, the info file will be fetched.

Note: for historical reason it is called "checksum", but it is not verified and not required to be a checksum as long as it is changed whenever addons.xml has changed.

=== datadir ===
URL to the root directory that contains the addons (i.e. the directory holding the addon.id subdirectories). The location of the zip files should be /datadir/addon.id/addon.id-x.y.z.zip.
If the <code>zip</code> attribute (Note: this feature has been dropped in v17 Krypton) is set to false, then Kodi assumes that each addon.id directory simply contains the addon itself, i.e. /datadir/addon.id/files for addon. Online repositories should always have zip set to true, both for efficiency of download and for the protection that .zip offers by way of verifying the download (i.e. can we unzip it).

== Security ==

We '''highly''' recommend you to enable SSL on your HTTP server and only use https URIs for your repository. Otherwise, you expose yourself and users of your repository to a great risk as they can easily be served malicious add-ons. Kodi writes a warning to the log file if you do not use https URIs starting with Leia.

== Repository Tools ==

Once the individual add-ons have been created, the repository itself can be put together by a script.
The script will package up your add-ons from your source folders or it can fetch the sources directly from a Git repository.
* [https://raw.githubusercontent.com/chadparry/kodi-repository.chad.parry.org/master/tools/create_repository.py Download the <tt>create_repository.py</tt> script from GitHub with this link] or with this command:
wget https://raw.githubusercontent.com/chadparry/kodi-repository.chad.parry.org/master/tools/create_repository.py && chmod +x create_repository.py
* Run the script, and pass it the location of your add-ons. The location can be a local folder, a local ZIP file, or a Git repository URL.
For example, if you have one zipped add-on and one add-on folder, then the following command will create the add-on repository in the current directory:
./create_repository.py ~/my.spectacular.project.zip ~/development.project/
* The <tt>--datadir</tt> option can specify a different directory for the repository. The <tt>--compressed</tt> flag uses gzip to pre-compress the addons.xml file. Also, a Git URL can have an optional <tt>#''branch''</tt> or <tt>#''tag''</tt> and optional <tt>:''path''</tt> at the end to designate the add-on's location within the repository.
For example, if you are publishing two add-ons that are both stored within separate Git repositories, then the following command would create a compressed repository:
<nowiki>./create_repository.py --datadir=~/html/software/kodi --compressed \
https://github.com/chadparry/kodi-repository.chad.parry.org.git#release-1.0.0:repository.chad.parry.org \
https://github.com/chadparry/kodi-plugin.program.remote.control.browser.git:plugin.program.remote.control.browser</nowiki>
* Every time you update an add-on, run the script again.

== See also ==
'''Development:'''
* [[Add-on development]]
* [[Skinning]]

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

Script lyrics

2018-10-26T18:24:24Z

Gamester17:

{{mininav|[[Development]]|[[Add-on development]]|[[Python development]]}}
==What Kodi requires for your add-on==
For XBMC to know what to do with your add-on, we require your script, and an addon.xml file. See [[Add-ons for XBMC (Developement)|here]] for more information on addon.xml, including how you add descriptions to your addon for users. A plugin source extends XBMC via the xbmc.python.lyrics extension point. The layout of the XML describing this extension point is as follows:

<syntaxhighlight lang="xml" enclose="div">
<extension point="xbmc.python.lyrics"
library="default.py" />
</syntaxhighlight>

list of extension points and their explanation:

"xbmc.python.script" This is the standard Script extension point

below listed extensions will not appear in the Scripts/Programs window and can only be run via skin shortcuts

"xbmc.python.weather" Used for weather scripts
"xbmc.python.subtitles" Used for subtitle scripts
"xbmc.python.lyrics" Used for lyrics scripts
"xbmc.python.library" Used for skin dependent scripts (e.g. recently added script)

Example of "xbmc.python.lyrics":
<syntaxhighlight lang="xml" enclose="div">
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<addon id="script.cu.lyrics"
name="CU Lyrics"
version="0.8.6"
provider-name="Amet">
<requires>
<import addon="xbmc.python" version="1.0"/>
</requires>
<extension point="xbmc.python.lyrics"
library="default.py" />
<extension point="xbmc.addon.metadata">
<summary lang="en">CU Lyrics</summary>
<description lang="en">Search, download and display lyrics from LyricWIKI.org. Downloaded lyrics will be saved in userdata/addon_data.Lyrics button on OSD needs to be activated and path set to CU Lyrics under Settings-> Skin-> Scripts </description>
<platform>all</platform>
</extension>
</addon>
</syntaxhighlight>

== Interacting with XBMC ==
Given that your script can return information to the user, you may wish to allow some (or all) of the information you provide to be translatable. You do this by providing a strings.xml file (in resources/language/<name_of_language>/strings.xml) which associates integer id's with each label. XBMC then handles loading these string files and ensuring that the users' locale information is taken into account. To display strings you use the '''getString''' function in the [[xbmcaddon module]].

== See also ==
* [[Add-ons]]
* [[:Category:All add-ons]]
* [[Unofficial add-on repositories]]
'''Development:'''
* [[Add-on development]]
* [[Addon Settings]]
* [[Python development]]
* [[Add-on repositories]]
* [[Official add-on repository]]

[[Category:Python Tutorial]]
[[Category:Python]]
[[Category:How-to]]
[[Category:Add-on development]]

Official add-on repository

2018-10-26T18:24:06Z

Gamester17:

{{mininav|[[Development]]|[[Add-on development]]}}
<br />
Kodi includes an interface to browse remote [http://en.wikipedia.org/wiki/Software_repository repositories] from where add-ons can be retrieved. The model is similar to the way many current [http://en.wikipedia.org/wiki/Linux Linux] [http://en.wikipedia.org/wiki/Linux_distribution distributions] work, whereby there is a main repository that is the default, and additional ones may be added by the user. Kodi has two official repositories that are included by default (''kodi.tv Add-ons'' and ''kodi.tv PVR Add-ons'') and are maintained by the [[Team Kodi|Kodi team]] (''Team Kodi''). This page outlines how to submit your add-on to the official repositories and keep it up to date.<br />

== List of add-ons ==
See:

* http://addons.kodi.tv
* [[:Category:All add-ons]]

== The repositories ==

=== kodi.tv / Kodi Add-ons ===

Browsing add-ons can be done from within Kodi through the built-in [[add-ons]] browser. From here you can install any add-on that is listed in the kodi.tv official repository.
For the time being each version of Kodi will have its own repo which contain only add-ons that are compatible with that specific version of Kodi. Manually installing add-ons is possible but remember to check if these are compatible for your Kodi version.

Kodi uses [http://en.wikipedia.org/wiki/Git_(software) Git] to manage the official repository. See below for the list of git repositories that comprise it.

Read only pull:
git clone https://github.com/xbmc/repo-plugins
git clone https://github.com/xbmc/repo-scrapers
git clone https://github.com/xbmc/repo-scripts
git clone https://github.com/xbmc/repo-skins
git clone https://github.com/xbmc/repo-webinterfaces

All current add-ons can be downloaded as ZIP files from the [http://mirrors.kodi.tv/addons/ repository server].
Feel free to see which ones there are and perhaps you they might give you some ideas for creating your own. These are also great examples for getting started and see how things are done in more extensive add-ons.

=== kodi.tv / Kodi PVR Add-ons ===

For more info on PVR see here: [[PVR]]

=== Repo Branches ===
For each version of Kodi there will be a specific branch of the Kodi add-on repository. As development progresses for the next version of Kodi, a repository for that next version will also be made. These repositories are automatically selected depending on which version of Kodi (stable or development) that the user is using. When the development Kodi repository is open we ask that add-on developers still maintain versions of their add-ons for the stable Kodi repository until that next development version of Kodi is released and becomes the new stable. When both repositories are open add-on developers will need to follow submission and update procedures individually to be in both. It is highly recommended to take advantage of the development Kodi repository so that your add-on is prepared for the next version of Kodi.

== Submitting add-ons ==
{{main|Submitting Add-ons}}

== See also ==
* [[Add-ons]]
* [[:Category:All add-ons]]
* [[Unofficial add-on repositories]]
'''Development:'''
* [[Add-on development]]
* [[Python development]]
* [[Skinning]]
* [[Add-on repositories]]

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

Archive:All platforms FAQ

2018-10-26T18:23:47Z

Gamester17:

{{Kodi FAQ}}
{{mininav| [[FAQs]] {{l2| [[Devices]] }} }}
'''F'''requently '''A'''sked '''Q'''uestions for Kodi that apply to all versions/platforms/OSes.

__TOC__
{{-}}
== General ==
{| width="100%"
{| width="100%"
{{FAQ|1= Kodi
| BGcolor= WhiteSmoke
| Question= About Kodi
| Answer=
{{Main|Kodi FAQ|Kodi}}
{{#lst:Kodi|intro2}}
}}

{{FAQ|1= Install
| BGcolor=
| Question= Installing Kodi
| Answer=
* See '''[[Installation]]''' and select the OS for your device for installation instructions.
* The current stable build of Kodi is {{current version}}.
}}

{{FAQ|1= uninstall |2= fresh_install
| BGcolor= WhiteSmoke
| Question= Uninstalling/fresh installing
| Answer=
* To completely uninstall Kodi, or to preform a fresh reinstall, you will need to delete the [[userdata folder]] and the containing Kodi ("xbmc" on older installs) home folder that holds the userdata folder, in addition to deleting/uninstalling the Kodi application.
}}

{{FAQ|1=Kodi_version|2= Kodi_version
| BGcolor=
| Question= What version am I running?
| Answer=
* In the default skin go to: Kodi main menu > System > Lower submenu > System info
* For a nightly build, note the build date.
}}

{{FAQ|1=Quick_Start_Guide|2=Quickstart
| BGcolor= WhiteSmoke
| Question= First Time User
| Answer=
{{See|First_time_user}}
}}

{{FAQ|1=Library|2=MySQL_sync|3=Roaming_profiles
| BGcolor=
| Question= Sync the Kodi library between multiple installs
| Answer=
{{See|Syncing and sharing}}
}}

{{FAQ|1= Remotes|2= Keyboard |3= Keyboard_controls
| BGcolor= WhiteSmoke
| Question= Controlling Kodi
| Answer=
{{See|Remote controls}}
{{See|Keyboard controls}}
}}

{{FAQ|1= Full_screen |2=Windowed
| BGcolor=
| Question= Switching between windowed and full screen
| Answer=
* To toggle between windowed mode and full screen mode, press the {{keypress|\}} button on a keyboard. (This, or any keyboard button, can be assigned to a remote control button if you wish. See [[Remote controls]] for more info.)
* If you have backed out of a playing video and see it behind the GUI, you can toggle back by pressing {{keypress|Tab}}.
}}
<section begin="Consoles and smartTV" />
{{FAQ|1=DLNA|2=SmartTVs|3=UPnP
| BGcolor= WhiteSmoke
| Question= Can I stream Kodi from my PC to my TV using DLNA/UPnP?
| Answer=
* Kodi has some support for this, and more is planned for the future. Normally Kodi is meant to be ran on a computer/supported-device that is directly connected to the TV by a video cable.
* Some files can be '''[[UPnP/Share|shared]]''' from Kodi using the built-in [[UPnP]] server and files scanned into the [[Video library]]. Kodi will not currently transcode any files, so only file formats that your TV/device can natively playback will work. This will only work with video (so you won't see Kodi's GUI) and currently does not work with add-on content.
}}

{{FAQ|1= xbox |2= PS3 |3= xbox360 |4=Wii
| BGcolor=
| Question= Can I install Kodi on a PS3/4, Xbox360/One, or Wii/U?
| Answer=
* Not to be confused with [[XBMC4Xbox]], which is the continued effort to run Kodi on original Xbox hardware.
* Nope. The required reverse engineering (to get access to the video acceleration hardware, among other things) has typically not happened on any of these game consoles. Further more, no one on Team Kodi has expressed an interest in attempting to port Kodi to those platforms, which would be a huge undertaking.
}}

{{FAQ|1= original_xbox
| BGcolor= WhiteSmoke
| Question= Does Kodi still run on the original Xbox?
| Answer=
* Team Kodi no longer officially supports the original Xbox, but the group over at [[XBMC4Xbox]] does.
}}
<section end="Consoles and smartTV" />
|}

== Videos ==
{| width="100%"
{{FAQ|1= Video_library
| BGcolor=
| Question= How do I add videos with summaries and that show up under "TV Shows" and "Movies" on the main menu?
| Answer=
{{Main|HOW-TO:Create_Video_Library}}
* {{#lst:HOW-TO:Create_Video_Library|intro}}
}}
{{FAQ|1=Update_library
| BGcolor= WhiteSmoke
| Question= How do I update the library?
| Answer=
{{main|Updating_or_removing_videos}}
{{#lsth:Updating_or_removing_videos|intro}}
}}
{{FAQ|1=missing_videos
| BGcolor=WhiteSmoke
| Question=Why don't all movies/shows show up in my library?
| Answer=
{{See|Incorrect and missing videos}}
}}
{{FAQ|1= kids |2= adults|3= separate_library
| BGcolor=
| Question= How to separate the library (cartoons, documentaries, anime, etc) from normal listings
| Answer=
{{Main|Custom home items}}
{{#lst:Custom home items|intro}}
}}
{{FAQ|1=3D videos
| BGcolor=
| Question=Can Kodi playback 3D (stereoscopic) videos?
| Answer=
{{Main|3D}}
* Kodi can playback some 3D (stereoscopic) video formats but not all. See the Kodi wiki article on "[[3D]]". To summerize; Kodi can playback 3D video formats such as SBS, TAB, anaglyph or interlaced, but it can not playback MVC (Multiview Video Coding) encoded 3D video format used by 3D Blu-ray Disc and some DVB 3D streams.
}}
{{FAQ|1=Blu-ray Disc
| BGcolor= WhiteSmoke
| Question=Can kodi playback Blu-ray Discs or images?
| Answer=
* Kodi can playback unencrypted Blu-ray Disc and Blu-ray ISO images as long as they are not a [[3D]] version. There is limited support for some Blu-ray menus.
}}

{{FAQ|1= Multi_part|2= File_stacking
| BGcolor=
| Question= Can Kodi handle multi-part movie files?
| Answer=
{{Main|File stacking}}
* Kodi can combined multi-part video files so that they play and appear as once video.
* File stacking is currently only available for movies and not for TV shows or music videos.
}}

{{FAQ|1= Movie_sets
| BGcolor= WhiteSmoke
| Question= Movie series and sets
| Answer=
{{main|Movie sets}}
* {{#lst:Movie sets|intro}}
}}

{{FAQ|1= play_next
| BGcolor=
| Question= How do I automatically play the next video?
| Answer=
* As of Kodi v12 you can turn on automatic playing of the next video by going to {{highlight|bordered=yes|[[Settings/Player/Videos#Play_next_video_automatically|Settings -> Player -> Videos -> Play next video automatically]]}}
* While selecting the video you wish to start at, bring up the contextual menu (press {{keypress|C}}) and select "Play from here".
* You can also play all items in a folder, show, or season, by selecting the folder and pressing play on your remote. If you do not have a dedicated "play" button then you can also select "Play" from the contextual menu (press {{keypress|C}} or {{button|menu}}).
}}

|}

== Music ==
{| width="100%"
{{FAQ|1= Music_library
| BGcolor=
| Question= How do I add music to the library?
| Answer=
{{main|HOW-TO:Create_Music_Library}}
{{#lst:HOW-TO:Create_Music_Library|intro}}
}}

{{FAQ|1=MP3_tags
| BGcolor= WhiteSmoke
| Question= Why doesn't all of my music/info show up in my library?
| Answer=
* Most of the information for music is pulled from the embedded music tags inside the file. Make sure your music files are tagged correctly.
* Some tags might show up in other programs, but might still be damaged or invalid for the tag standard, causing issues in Kodi.
* You can use a program such as MusicBrainz Picard to easily tag files or fix broken tags. See also [[:Category:Music tools]] for other programs.
}}

|}

== Pictures ==
{| width="100%"
{{FAQ|1= Picture_viewing
| BGcolor=
| Question= How do I add view digital pictures and still images?
| Answer=
{{main|Pictures}}
{{#lst:Pictures|Intro}}
}}

{{FAQ|1=Picture_library
| BGcolor= WhiteSmoke
| Question= Why isn't there a picture library?
| Answer=
* No one have developed a picture library for Kodi yet, but there is a pictures section where you can add media sources and view pictures in file mode.
* Not having a picture library (and a picture database) unfortuanly means that you can not sort, browse, or search pictures by their tags.
}}

|}

== PVR (Live TV and DVR) ==
{| width="100%"
{{FAQ|1= PVR_frontend
| BGcolor=
| Question= Can I watch Live TV and control PVR/DVR function?
| Answer=
{{main|PVR}}
{{#lst:PVR|Intro}}
}}

{{FAQ|1=PVR_backends
| BGcolor= WhiteSmoke
| Question= How does Live TV and PVR work in Kodi?
| Answer=
Logically, the PVR / Live TV design in Kodi uses a [[wikipedia:distributed application|distributed application structure]] that is designed after the [[wikipedia:client–server model|client–server model]] concept which consists of two parts:
# The PVR '''backend''' (as the server side part), which communicates with a TV tuner adapter(s) to receive the Live TV signals and create a video or audio stream, and
# The PVR '''client''' (as an addon for Kodi) - an Kodi addon which controls the presentation of that content via the Kodi GUI that acts as unified frontend and common interface for all connected PVR backends.

The "'''PVR backend'''" as such is a separate application/process that directly interfaces with your TV tuner adapter(s) and the performs the task of tuning, streaming, and recording over-the-air and cable television signals and radio programming. PVR backends can either run on the same host running Kodi, or on a stand-alone host/device completely by itself with Kodi only running when needed, as long as they have a network connection between them. Some PVR backends may be able to serve several clients simultaneously, which may be Kodi clients or others applications/devices, and in those cases such PVR backends that serves multiple clients are commonly refereed to as PVR servers.

When paired with one or more matched PVR backends, a configured '''PVR client addon''' enables Kodi to handle the GUI interface, or frontend, allowing the user to watch Live TV (with pause/time-shift, if supported by the PVR backend used), display a graphical EPG (Electronic Program Guide) of all available television programming, schedule recordings or listen to radio, giving the same sort of functionality as TiVo-style video recorder devices.
}}

|}

== Add-ons ==
{{main|Add-ons}}
{| width="100%"
{{FAQ|1= Add-ons
| BGcolor=
| Question= What are add-ons?
| Answer=
* '''[[Add-ons]]''' are a way of extending Kodi's functionality easily. Common add-ons include: Skins, Scrapers, Video Add-ons, Subtitle services and many more are available.
}}

{{FAQ|1= Install_add-ons
| BGcolor= WhiteSmoke
| Question= How do I install add-ons?
| Answer=
* For a picture step by step see '''[[Add-on manager]]'''.
}}

{{FAQ|1= Repository
| BGcolor=
| Question= Where can I find unofficial add-ons/skins?
| Answer=
* Add-ons not included in the official Kodi repository can be obtained by using unofficial repositories or installing the add-on using '''Install from Zip file''' option. The two main sources for finding unofficial repos and add-ons are '''[[Unofficial add-on repositories]]''' and the '''[http://forum.kodi.tv/forumdisplay.php?f=27 Kodi Add-on support forums]'''.
}}

{{FAQ|1=Repository empty listing
| BGcolor= WhiteSmoke
| Question=What should I do when Addon repositories dont list any contents?
| Answer=
See [[Add-on manager#Empty repository list|'''Empty repositories list''']]
}}

{{FAQ|1= Add-on_help
| BGcolor=
| Question= Where do I get help with add-ons or skins?
| Answer=
* You can get help with add-ons at the '''[http://forum.kodi.tv/forumdisplay.php?f=27 Kodi Add-on support forums]''', with some add-ons even having dedicated threads with FAQs, and more. For skins see the '''[http://forum.kodi.tv/forumdisplay.php?f=67 Kodi Skin support forums]''', which has sub-forums for several skins as well as general help threads. '''''Be sure to use the search function to see if your question has been answered before'''''.
}}
|}

== Special features ==
{| width="100%"
{{FAQ|1=Netflix|2=LoveFilm|3=Silverlight
| BGcolor=
| Question= Netflix, LoveFilm, and other Silverlight-based video services
| Answer=
* Both [[w:Netflix|Netflix]] and [[w:LoveFilm|LoveFilm]] use [[w:silverlight|silverlight]], making it all but impossible to play inside of Kodi directly, even with an add-on. Sometimes there are add-ons for Kodi that will launch a web browser to load the service, but you will require an OS that has silverlight support (Mac OS X or Windows).
* {{editor note|Know of a guide for [[Advanced Launcher]], or a working add-on for launching Netflix or LoveFilm? Feel free to add that info/links here}}
}}

{{FAQ|1=Hulu|2=Amazon|3=Flash
| BGcolor= WhiteSmoke
| Question= Hulu, Amazon, and other Flash-based video services
| Answer=
* While Kodi does not have [[w:Adobe Flash|Flash]] video support directly, very often videos can be extracted from the Flash video stream/file container. Some sites also have non-flash video streams that can be accessed from within Kodi. Sometimes these streams/files can be accessed by using a [[STRM]] file, while others are more complicated and need an add-on to access the content. For example, there is an add-on for [[Hulu]] and Amazon Prime video services (see Bluecop's add-on repo for both). Be sure to check out [[:Category:Video add-ons]] and the Kodi forums to see what is currently available.
}}

{{FAQ|1=AirPlay
| BGcolor= WhiteSmoke
| Question= AirPlay
| Answer=
{{main|AirPlay}}
* To enable Kodi's [[AirPlay]] server go to: {{highlight|[[Settings/Services/Airplay|Settings -> Services -> Airplay]]}}
}}

|}

== Troubleshooting ==
{{main|Troubleshooting}}

{| width="100%"
{{FAQ|1= Bug_report
| BGcolor=
| Question= Reporting bugs
| Answer=
* For how to report bugs in Kodi see: '''[[HOW-TO:Submit a proper bug report]]'''.
}}

{{FAQ|1=os_specific_bugs
| BGcolor= WhiteSmoke
| Question= Platform/OS specific troubleshooting
| Answer=
* [[Android FAQ#Troubleshooting]]
* [[iOS FAQ#Troubleshooting]]
* [[Linux FAQ#Troubleshooting]]
* [[Mac FAQ #Troubleshooting]]
* [[Windows FAQ#Troubleshooting]]

* [[Raspberry Pi FAQ#Troubleshooting]]
}}

{{FAQ|1=Forum|2=IRC
| BGcolor=
| Question= Getting more help
| Answer=
* Check out the '''[http://forum.kodi.tv/forumdisplay.php?f=33 Help and Support forums]''' or the '''[irc://irc.freenode.org/kodi #kodi]''' [[w:IRC|IRC]] chat channel on irc.freenode.org
* Also check out the platform specific FAQs:
** [[Android FAQ]]
** [[iOS FAQ]]
** [[Linux FAQ]]
** [[Mac FAQ]]
** [[Windows FAQ]]
** [[KodiBuntu FAQ]]
** [[Raspberry Pi FAQ]]
}}

{{FAQ|1=Cache_full|2=Cache|3=buffering
| BGcolor= WhiteSmoke
| Question=Cache full messages and constant buffering
| Answer=
* This message refers to the playback cache that Kodi uses when a video is loading/streaming from the network (local or internet). It indicates that the video is loading too slowly for Kodi to play it back smoothly, and Kodi can't fully buffer it without having to buffer again as the video plays. The common cause for this is simply a slow connection to the file, often on the server's connection.
* The cache is loaded in RAM and is cleared out every time a video is stopped.
* Cache settings can be adjusted using [[advancedsettings.xml]]. See: '''[[HOW-TO:Modify the video cache]]'''.
* {{note|In most cases, this simply means that the server on the other side of the connection is too slow, and there's nothing you can do about it. No matter how fast your internet is, the server on the other side might simply be slow.}}
}}

{{FAQ|1=Missing_videos2
| BGcolor=
| Question= Not all videos are scanned into the library
| Answer=
{{See|Incorrect and missing videos}}
}}

{{FAQ|1= hide_watched
| BGcolor= WhiteSmoke
| Question= Previously watched videos are no longer listed/ Videos seem to go missing
| Answer=
* Bring up the side menu (arrow over left or right on a keyboard or remote) and toggle the "Hide Watched" option.
* See this video for quick guide on how to fix it.
{{youtube|4vMRBRdu5uU}}
}}

{{FAQ|1=mute
| BGcolor=
| Question= No sound and red speaker icon in the corner
| Answer=
[[File:mute.png|right]]This means that Kodi is muted. Turn the volume up.
}}

{{FAQ|1= Known issues
| BGcolor= WhiteSmoke
| Question= Is there a list of some known issues?
| Answer=
{{See|Common issues}}
}}

|}

{{Helix updated}}

[[Category:Manual]]
[[Category:FAQ|**]]

Naming video files

2018-10-26T18:23:10Z

Gamester17:

{{VideoLibraryCreate}}
{{mininav|[[Video library]]}}

= Introduction =
<section begin="intro" />{{kodi}} has the ability to display information and artwork for your video collection. As this information and artwork comes from third-party sites, video files must be placed in a certain folder structure and named correctly so accurate matches can be made with those third-party sites. This page, and following pages, will instruct on the correct methods to use for the most reliable scraping process.<section end="intro" />

The process of matching and downloading data and artwork to your {{kodi}} library is named '''scraping'''. The sites where we obtain the information from is referred to as the '''information provider site''' (also '''scraper site'''). The wonderful add-on that enables this to occur is called the '''scraper'''.

<section begin="know" />Things you should know about scraping:
*{{Kodi}} obtains artwork and metadata from third-party sites that {{kodi}} has no control over. As these sites are outside the control of Kodi, it is important that your video files and folders are named correctly to ensure an accurate match with the listings at the scraper sites.
*If a movie or TV show does not exist at the scraper site, then {{kodi}} cannot scrape it. Always check the entry at the scraper site.
*{{Kodi}} can also read information from local files known as '''''[[NFO_files|NFO Files]]'''''.
*As the information provider sites are maintained by a small volunteer community, which provides this service at no cost, it is strongly encouraged that {{Kodi}} users contribute back to those sites when discovering errors and omissions in the databases.
*Scraping problems experienced by users are attributable as follows: 95%- Incorrect naming, folder and source structure; 4%- Missing data at the scraper site; 1%- Changes at the scraper site which breaks the scraper add-on.<section end="know" />
*For a full list of metadata downloaded by the scraper see '''''[[NFO_files|NFO Files]]'''''
*For a full list of artwork that can be used by {{Kodi}} see '''''[[Artwork|Artwork]]'''''

The default scraper used by {{kodi}} for '''Movies''' is the TheMovieDB (TMDB). Other scrapers are available and can be found by searching the {{kodi}} site '''''[https://kodi.tv/addons/browse?keyword=&category=1185&author=&sort=title+ASC here]'''''
:'''''See: [https://www.themoviedb.org/ TheMovieDB]
:'''''See: [[Add-on:The_Movie_Database|TheMovieDB Add-on]]
:'''''See: [[Add-on:Universal_Movie_Scraper|Universal Movie Scraper Add-on]]

The default scraper used by {{kodi}} for '''TV Shows''' is the TheTVDB (TVDB). Other scrapers are available and can be found by searching the {{kodi}} site '''''[https://kodi.tv/addons/browse?keyword=&category=1187&author=&sort=title+ASC here]'''''
:'''''See: [https://www.thetvdb.com/ TheTVDB]
:'''''See: [[Add-on:The_TVDB|TheTVDB Add-on]]

'''{{big|This is the most important step to ensuring correct scraping.}}'''

= Source Folder =
The Source folder is the location that the user specifies for {{kodi}} to search for a class of media. In this case of videos, it is the folder that holds the movie files and TV Shows. These must be separate Sources.

The Source must be the parent folder that holds the respective movies and TV Shows.

Notes on naming and setting a '''Source''':
*There is no limit on the number of Sources that can be used
*The Source names, which essentially is your folder name, can be anything that makes sense to you. The names should be unique, which makes it easier to navigate to the correct source in {{Kodi}}
*A single class of media can be placed in one source if you desire, though larger libraries (200 or more videos) do benefit from multiple sources
*There is no requirement on how to separate videos between Sources. Many users separate based on Genre, alphabetical listing, Video Resolution (DVD, Bluray, 4k) or any method you prefer
*If you have your video collection on multiple drives, then a Source must exist on each hard drive for each Class of media and added to {{Kodi}}
*'''Never''' mix media classes. ie, ensure TV Shows, Movies, Music Videos or Music are not in the same source.
*'''Never''' set the entire hard drive as your Source as this will create multiple ghost entries.

= Movie Naming & Folder Structure =
{{#lst:Naming_video_files/Movies|intro}}
:'''''See: [[Naming_video_files/Movies|Naming Movies]]'''''

= TV Show Naming & Folder Structure =
{{#lst:Naming_video_files/TV_shows|intro}}
:'''''See: [[Naming_video_files/TV_shows|Naming TV Shows]]'''''

= Supplemental tools =
To help with mass file renaming and organizing, see the following pages for programs that can help automate these tasks, or do them in bulk.
:'''''See: [[Rename_tools|File Renaming Tools]]'''''
:'''''See: [[Library_managers|Library Managers]]'''''

{{top}}

<div style="{{linear-gradient|left|#a1f5e4, #f5f5a1}}">{{next|[[Naming_video_files/Movies|'''Naming Movies''']]}} </div>

{{updated|17}}
[[Category:FAQ]]
[[Category:Index]]
[[Category:How-to]]
[[Category:Guides]]
[[Category:Manual]]
[[Category:Karellen]]
[[Category:Video library]]
[[Category:General topics]]
[[Category:First time user]]
[[Category:Quick Start Guide]]

Translations

2018-10-26T18:22:32Z

Gamester17:

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

{{see also|Add-on development}}

== History ==
In the development cycle from Eden (V11) to Frodo (V12) the translation system has been revised.

The former strings.xml file has been superseeded by the appropriate strings.po files. Due to that the way how translations are handled has been changed, too.

== Transifex ==
The whole translation system has been moved to [http://www.transifex.net Transifex].
So if you want to help translating Kodi into your native language, first thing you need to do is to sign up at Transifex.

Next Step would be to check the current project for XBMC. Currently it is this one:

[https://www.transifex.com/projects/p/xbmc-addons/ Add-on Translation Project]
[https://www.transifex.com/projects/p/kodi-main/ Main Translation Project]
[https://www.transifex.com/projects/p/xbmc-skins/ Skin Translation Project]

On that page you should see the available languages that can be translated:

[[File:Lang overview.png|900px]]

Check your native language and request to join the translation team. In this example I choose Greek:

[[File:Join.png|900px]]

The appropriate coordinator of your language will approve or deny your request.

By approval you can start translating immediately.

Currently this project is for core Kodi only! So no third party addons or stuff like that!

This will follow later on. So stay tuned in the [http://forum.kodi.tv/forumdisplay.php?fid=90 appropriate forums section for translations]

== Translating Kodi ==
''Note: Please do not download files, modify them and upload again! Always use the "Translate Now" Button!''

Ok, let's get to work!

Search that part of the project that needs updating. You can see the percentage of the translations to the right:

[[File:Select ressource.png|900px]]

You might note that there is something missing in "visualisation milkdrop". So we click on it to translate it.

The red marked area is button mentioned before. Always use this one!

[[File:Translate now.png|900px]]

Check the missing strings on the right side. After you completed them hit the "Save and Exit" button down on the left.

[[File:Translating string.png|900px]]

== Useful hints ==
This part shows some additional information for developers and translators to make things more easy. So it's worth taking a look.

=== Details & Comments ===
The developers can set special marks in the strings.po file to give a useful comment on that string. e.g. what it exactly does or where it can be found in the GUI.
Additionaly there is a field for the occurence which shows in which file this strings is mentioned. You get these info by hovering over the buttons of the source strings.

[[File:Details.png|900px]]

In the source file it looks like this:
<syntaxhighlight lang="xml" enclose="div">
#. play GUI sounds
#: xbmc/settings/GUISettings.cpp
msgctxt "#34122"
msgid "Always"
msgstr ""
</syntaxhighlight>

With #. we can add a helper comment or context to help translators understand the meaning or usage of string.

with #: we can specify where the string is used. Sometimes this could also be a useful info.

=== Group Discussion ===
Another useful feature is the discussion board for the team. That way you can can speak about issues or just state some suggestions. You can get in conteact with other team members or the coordinator.

[[File:Discussion.png|900px]]

''NOTE: This board is not for off-topic discussions! Everything besides translations should be disucussed on the forums!''

== Addons/Skins ==
The process is the same for third-party addons/skins, except they are hosted at a different Transifex link.
For current links please visit [http://forum.kodi.tv/showthread.php?tid=141158 this] thread.

== Contact ==
If you have problems with Transifex your first person to contact should be the coordinator of your language!

If you have more general questions you might head over to the forums and post your question in the translation are there.
Alanwww1 and others can help you there.

== Sync time schedule ==
We plan to make regular sync procedures from XBMC-master to Transifex weekly and from Transifex to XBMC-master monthly at the last week of the month.
For addons we do more frequent updates, with 2-3 syncs a week.

== Syntax verification ==
For keeping the strings correctly formatted, we do a constant syntax verification at each sync occasions. The results are in sync syntax-check logs. Please check these links regularly if you find any problems for your language. The following logs are available:
* The kodi-main [https://github.com/xbmc/translations/blob/master/kodi-translations/kodi-main/txupdate-syntax.log syntax-check log]
* The xbmc-addons: [https://github.com/xbmc/translations/blob/master/translations/addons/txupdate-syntax.log syntax-check log]
* The xbmc-skins: [https://github.com/xbmc/translations/blob/master/translations/xbmc-skins/txupdate-syntax.log syntax-check log]

For more info on syntax checking, please check out [http://forum.kodi.tv/showthread.php?tid=152720 this] thread!

[[Category:Development|T]]
[[Category:Languages]]
[[Category:Team Kodi specific notes]]

Archive:Xam - XBMC Addon Manager

2018-10-26T18:22:12Z

Gamester17:

{{mininav| [[Supplemental tools]] }}
[http://pypi.python.org/pypi/xam/ xam] is a CLI utility for searching and exploring the official Kodi repositories.

== Features ==
* List addons available in remote repositories.
* List addons which require another addon as a dependency.
* Download the current version of an addon locally.
* Display the addon.xml for a remote addon.
* Search all addon.xml files in a repository for a given string.
* Supports the official Kodi respositories as well as third-party repos.

== Installation ==

$ pip install xam
$ xam --help

== Development ==

Issues, comments, development @ https://github.com/jbeluch/xam

[[Category:Supplemental tools]]

Add-on structure

2018-10-26T18:21:48Z

Gamester17:

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

This page summarizes the add-ons system introduced in the Dharma release (v10) of XBMC. This system allows third-party developed enhancements to Kodi to be distributed to Kodi users directly from inside the Kodi interface.

The add-ons system is based on the plugin library [http://www.c-pluff.org c-pluff].

== Introduction ==

Each add-on is kept in its own folder, and is described via an XML file named <code>addon.xml</code>. In addition, some other files can also come with the add-on, such as <code>icon.png</code>, <code>changelog.txt</code>, and <code>fanart.jpg</code>. These are all optional, though we encourage you to at least have <code>icon.png</code>. All of these reside in the "root" of the folder that contains the add-on. Additional data may be contained within a <code>resources/</code> subfolder, such as language translations and descriptions of settings.

When installed, the whole add-on folder will be placed inside <code>.xbmc/addons/</code>.

== Directory Name ==

Your directory name should follow this convention: <code><addon-type>[.<media-type>].<your-plugin-name></code>

Each name part is case sensitive and must be in lower case. The dot character separates each name part; you can use further dots to separate things in your plugin name if you wish. Alternatively, you may use a hyphen (-). No other non-alphanumeric characters should be used.

<code>addon-type</code> is one of the following:

{| class="prettytable" border="1"
!Add-on Type
!Description
!Media Type Required?
|-
|<code>repository</code>
|A repository definition file that allows users to add new repositories to the Kodi addon manager.
|No
|-
|<code>plugin</code>
|A plugin script or module that adds to the functionality of Kodi. Plugins appear under the relevant media section of the main home menu.
|'''Yes'''
|-
|<code>script</code>
|A runnable program file that will appear in the Program section of the main home menu.
|'''Yes'''
|-
|<code>skin</code>
|An Kodi skin definition and its supporting script files.
|No
|-
|<code>resource</code>
|An addon that will provide additional files (language files, images, [[sounds.xml|uisounds]]).
|No
|}

The following table describes the available <code>media-type</code>s for the available add-on types. Your add-on may provide more than one <code>media-type</code> if
you wish, whereby it will appear in more than one section. In most cases, however, a single media type will suffice, and it may be preferable to have multiple add-ons each providing a single media type rather than one add-on that tries to do it all.

{| class="prettytable" border="1"
!Add-on Type
!Media Type
! Description
|-
|<code>plugin</code>
|<code>audio</code>
|A music add-on that will appear in the Music main menu.
|-
|<code>plugin</code>
|<code>video</code>
|A video add-on that will appear in the Video main menu.
|-
|<code>plugin</code>
|<code>picture</code>
|A picture add-on that will appear in the Pictures main menu.
|-
|<code>plugin</code>
|<code>program</code>
|A program add-on that will appear in the Add-ons main menu.
|-
|<code>plugin</code>
|<code>weather</code>
|A weather add-on that will appear in the Weather main menu. You can omit the Add-on Type in the directory name and addon-id
|-
|<code>script</code>
|<code>module</code>
|A script plugin that will not appear under a category or within the Add-ons manager, but provides support for other add-ons.
|-
|<code>script</code>
|<code>service</code>
|A script that will be run at either login or startup
|}

The add-on name is up to you, but be sure that it isn't already in use by another add-on. For instance, if you are creating an add-on that integrates the Gpodder software with Kodi for audio podcasts you might name your directory <code>plugin.audio.gpodder-xbmc3</code>. If you are creating a screen scraper to present TV shows from MyGreatTv.com. It might be <code>plugin.video.my-great-tv-com</code>. A script to ping all your friends on twitter to tell them you are home might be called
<code>script.service.ping-twits-i-am-home</code>.

== Directory structure ==

Your directory contains all the resources needed to operate your add-on. The directory must be considered read-only and should not be used for storing transient or inter-session data. Other mechanisms are available to do that (more later). The directory should be structured as follows:

=== Kodi v17 Krypton and up===
addon.py
addon.xml
LICENSE.txt
resources/
settings.xml
language/
lib/
data/
media/
fanart.jpg
icon.png

=== Kodi v16 Jarvis and earlier===
addon.py
addon.xml
fanart.jpg
icon.png
LICENSE.txt
changelog.txt
resources/
settings.xml
language/
lib/
data/
media/

Other files may be required to run your add-on, if your add-on becomes more complex. It is considered good practice to place various add-on resources and support code modules in the <code>lib/</code> folder. If those libs are commonly used by multiple add-ons, consider adding them as a separate add-on, e.g. <code>script.module.foo</code>.

The most important thing to remember from this is that everything that doesn't need to be in the root of your directory is considered a resource and should be placed inside <code>resources/</code> or one of its subdirectories. Also remember, all the above is a ''recommended'' outline for your add-on; if you need fewer or more
directories to organise your work, just change it. For instance, skins are add-ons that will require more directories than this.

=== addon.py ===

This will contain the main Python code for your add-on. You can name it whatever you want, since you'll define this Python file in <code>[[addon.xml]]</code> as your main script file.

=== addon.xml ===
{{See also|addon.xml}}

<code>addon.xml</code> gives Kodi important metadata about your add-on, such as:
* what the add-on provides
* what the add-on relies on to work
* what script to run when it is fired up (if it is meant to be started)

=== changelog.txt ===

{{note|Deprecated in Kodi v17 Krypton. Replaced by [[Addon.xml#.3Cnews.3E]]}}

A text file that contains a description of the changes you make to the add-on for each release. This is displayed in the Kodi addon installation/update system. The recommended format is to have it sorted by version in descending order, with a simple description as to the major changes (new functionality, big fixes, etc) in each version. (In the author's opinion, too many add-ons skip this piece of information, making it difficult for users to determine whether a particular problem that
they may have been having has been fixed or not.)

Here is a sample
<code>changelog.txt:

v0.1.3 (2015-12-25)
- Update with 15.0 Isengard

v0.1.2 (2014-1-15)
- Add notification for Ubuntu users checking through apt command

v0.1.1 (2014-1-1)
- Initial version
</code>

It is recommend to add a date so users know when last update was done. Best is to use YYYY-MM-DD as this is the least confusing way of dat notation.

=== icon.png ===

This is an icon used to represent your add-on in various parts of Kodi. In order to keep a coherent look and give the skinner a good idea how the icons of the add-ons look, we have defined the following rules:

* The icon size must be 256x256 pixels or 512x512 pixels.
* File format is PNG.
* Background must be 100% solid. That doesn't mean one color, it also can be a gradient or a low contrast texture. Just make sure there is no transparency.
* Keep the logo as simple a possible, no exaggerated 3D effects or high contrast textures.
* Use a padding of at least 25px for your logo (not the background!). Excepted are large text logos (see icon for themoviedb.org).
* Keep text to a minimum. However, a text logo along with the graphical logo is recommended in order to easily recognize the addon.
* Don't mix logos with Kodi's logo; it's obvious that we're talking about Kodi here.
* Don't add borders or any overlays, that's the skinner's job. However, if borders are an element of your logo, make sure there is enough padding.
* It is suggested that a logo on a plain background (non-transparent) is best in many situations (e.g. for addons that retrieve media from an online service, use that service's logo ''as long as you are free to do so'').

=== fanart.jpg ===

This helps to keep Kodi graphically rich when browsing and using add-ons. Some simple guidelines:

* It should be 16:9 aspect ratio
* It is intended for the background, so should be simple and without text where reasonable.
* We recommend a 1280x720 JPEG image. It should certainly be no larger than 1920x1080.
* We recommend keeping it as small as is reasonable with respect to file-size. Remember that hundreds of thousands of users are going to be downloading this.

=== LICENSE.txt ===
{{See also|Submitting_Add-ons#Repository_Submission_Guidelines_-_Please_Read_Before_Submitting_Your_Addon|label 1=Repository guidelines}}

This file should contain the text of whatever software license you've chosen to release your add-on under (e.g. GPLv2).

=== resources/ ===

The <code>resources/</code> subdirectory is the preferred place to put any files that the add-on uses that don't need to be stored in the root directory. For instance, translations, software libraries, and image resources would go in <code>resources/</code> or one of its subdirectories.

==== resources/settings.xml ====
{{See also|Add-on settings}}

This is an XML file that defines the user-configurable settings used by the add-on. The file defines the names and types of the settings, and how they should appear in the settings dialog for the add-on.

==== resources/language/ ====

'''Translation tools:'''
* [[Language support]]
* [[Translation System]]
* Convert .xml to .po: [https://github.com/alanwww1/xbmc-xml2po xbmc-xml2po]
* Check for .po files: [https://github.com/alanwww1/xbmc-checkpo xbmc-checkpo]
* Utility for keeping Kodi upstream language files and the language files hosted on transifex.com in sync: [https://github.com/alanwww1/xbmc-txupdate xbmc-txupdate]

'''String ID range:'''
* strings 31000 thru 31999 reserved for skins

'''strings.po'''

{{note|strings.xml will possibly be deprecated after the release of Frodo/Gotham. Frodo and Gotham will still be backwards compatible with .xml}}

==== resources/lib/ ====

Put any module definitions or third party software libraries into this directory.

==== resources/data/ ====

Store any other static data structures your application requires here. Examples might be
XLT/XSD files or static XML files that contain lookup tables etc.

==== resources/media/ ====

Store any static media (picture, audio, video etc.) files in this directory.

== Getting started ==

Following pages will explain in more depth to get started. Providing examples, background information and useful links.

* [[Python development]]
* [[Skinning]]

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

[[Category:Add-on development]]

ServerWMC

2018-10-26T18:21:21Z

Gamester17:

{{:PVR/Contents}}
{{mininav|[[PVR]]|[[Recording software]]}}
[[File:SWMC_Logo.jpg|right|border]]
ServerWMC is a server interface for Windows which communicates with Windows Media Center (WMC) allowing it to be used as a Personal Video Recorder (PVR) backend providing Live TV, PVR functions and Electronic Program Guide (EPG) data. These services are provided to XBMC though the [[Add-on:PVR.WMC|pvr.wmc]] add-on.<br />
<br />
ServerWMC was developed and is maintained by [http://forum.kodi.tv/member.php?action=profile&uid=135134 krustyreturns].

'''A fantastic guide detailing the setup of XBMC, WMC, ServerWMC, pvr.wmc and everything else you need to know from beginning to end can be found here: http://forum.kodi.tv/showthread.php?tid=193310'''

== Configuring Windows Media Center ==
Windows Media Center must first be fully configured (tuners configured, EPG configured, channels setup, etc) on the PC to be used as the TV Server prior to using ServerWMC. This setup will vary slightly based on the tuner you are using. There is a generic WMC setup guide here that may be of assistance to those new to WMC: http://www.howtogeek.com/howto/9166/learning-windows-7-setup-live-tv-in-windows-media-center/

The following is setup information specific to some popular devices:
* [http://www.silicondust.com/products/hdhomerun/atsc/ '''HDHomeRun'''] - http://www.silicondust.com/support/hdhomerun/instructions/wmc7/
* [http://www.silicondust.com/products/hdhomerun/prime/ '''HDHomeRun Prime'''] - http://www.silicondust.com/support/hdhomerun/instructions/prime/
* [http://cetoncorp.com/products/infinitv/ '''Ceton InfiniTV Products (All)'''] - http://cetoncorp.com/product-support/
<br />
{{note|Though Windows Media Center must be configured, it is not necessary for WMC to be running to provide the connection to ServerWMC.<br />If you have previously disabled WMC services, please re-enable them at this time. Though WMC does not need to be running, if the services are disabled and WMC is unable to automatically update EPG data, XBMC will either display a blank EPG or CRASH when selecting 'Live TV'.<br />'''Please ensure you can view live TV from within WMC before continuing!'''}}<br />

== Downloading & Installing ServerWMC ==
The latest version of ServerWMC can be found here: [http://bit.ly/serverwmc http://bit.ly/serverwmc]

ServerWMC includes an installer package so simply download, unzip and run '''Installer_ServerWMC.msi''' as administrator. It is not necessary to uninstall the previous version before installing an updated version.
<br />
{{note|ServerWMC must be installed on the same PC that was configured for Windows Media Center above.}}
<br />
<br />

== ServerWMC Configuration (Quick) ==
Launch ServerWMC from the Start Menu. An entry was created during installation at Start/ServerWMC/ServerWMC. <br />
{{note|On first run, you should be prompted to allow '''ServerWMC.exe''' through your firewall. Make sure to select '''allow'''.}}

Ensure that Windows Media Center (WMC) is configured with particular attention to the following:
* Directory for recorded TV is specified
* TV tuners are installed and detected
* TV channels are scanned
* You are able to watch live TV within WMC

Ensure that the Windows Media Center "Recorded TV" folder is Shared from the server PC (as clients will need to access it via smb://). If the share is protected or if accessing with non-windows based clients, the username and password for the share should be entered on the 'folders' tab within ServerWMC.

Run ServerWMC application and check/configure the settings. Additional info on each setting can be found below.

{{note|ServerWMC supports most of the WMC configuration including enable/disable channels, set custom channel orders/numbers and custom channel icons. These settings should be configured within WMC and not XBMC.}}

== ServerWMC Configuration (Detailed) ==
{| cellpadding="8" cellspacing="0"
|- valign="top" |
| || [[File:ServerWMC_Status.png|right|border]]
=== Status ===
* '''WMC database''' - Displays the status of the connection between ServerWMC and the Windows Media Center database
** <span style="color:#4169E1">'Opened'</span> - Indicates the server has successfully connected
* '''Channels found''' - Displays the number of channels being reported as available from WMC
* '''Tuners found''' - Displays the number of tuners available and ready to use
* '''Clients online''' - Displays the names of clients connected to ServerWMC
* '''Totals of items transferred to clients:'''
** '''Channels''' - Displays the number of channels being made available to clients
** '''EPG Entries''' - Displays the number of Electronic Program Guide entries being provided to clients
** '''Timers''' - Displays the number of future recording tasks in queue
** '''Recordings''' - Displays the number of recorded programs available in the /Recorded TV/ folder (specified on the 'Folders' tab)
* '''Active Recordings''' - Displays status of programs currently being recorded
* '''Active Streams''' - Displays the status of streams being used by clients

|- valign="top" bgcolor="whitesmoke" |
| || [[File:ServerWMC_General.png|right|border]]

=== General ===
* '''Start when Windows starts''' - Starts ServerWMC when the user logs on to Windows. Unless you have a need to start the server manually at login, this option should be enabled.
* '''Startup minimized''' - Minimizes ServerWMC to the Task Bar upon startup.
* '''Minimize to system tray''' - Sends ServerWMC to the System Tray when minimized instead of the Task Bar.
** '''Close box minimizes to system tray''' - Causes ServerWMC to minimize to the system tray when the red 'X' is clicked instead of closing the program.
* '''Suspend system sleep mode when clients are online''' - Prevents PC running ServerWMC from entering sleep mode (if enabled) if any clients are connected.
** '''Suspend sleep even if only client online is MediaBrowser-Server''' - Prevents PC running ServerWMC from entering sleep mode (if enabled) if MB3Server is running on the host PC regardless of other client status.
* '''Port number for client connection''' - Specifies the port on which the pvr.wmc plug-in will communicate with ServerWMC. The default port is 9080. Unless you have another program communicating on this port, there is no reason to change from default. Again, if you were not prompted when launching ServerWMC or you chose to decline, '''make sure this port is open in your firewall software''' before continuing.

|- valign="top" |
| || [[File:ServerWMC_Folders.png|right|border]]

=== Folders ===
* '''Path to local 'RecordedTV' folder (from WMC)''' - Displays the path of the folder where recordings will be stored. This path is specified in WMC under Tasks/Settings/TV/Recorder/Recorder Storage and is not editable from ServerWMC. If you have other clients on the network, this folder should be shared and specified below.
* '''Enter the network share path to this folder, this is required for remote clients:''' The smb address of the folder specified above. It is advised to test this address from another machine to make sure it is accessible remotely before continuing.
* ''' Watched 'Recorded TV' folders (from WMC):''' If additional folders are specified as 'watch folders' within WMC, their paths will be displayed here.
* '''Use Credentials for non-windows clients''' - If the folder specified above requires a user name and password for access, please enter the credentials here.
** '''User Name''' - SMB user name for the shared folder
** '''Password''' - SMB password for the shared folder
<br />
{{note|With non-Windows based clients, user:pass credentials are ''typically'' needed even when the Windows share is shared with "Everyone".}}

|- valign="top" bgcolor="whitesmoke" |
| || [[File:ServerWMC_Update.png|right|border]]

=== Updates ===
* '''Version Installed''' - Displays information about the currently installed version of ServerWMC.
** '''Version Status''' - Indicates if version installed is up to date or if a newer version is available.
* '''Last Checked''' - Displays date ServerWMC last checked for an available update.
** '''Check Now''' - Manually initiate check for newer version.
** '''Apply Update''' - If a newer version is available, initiates installation of ServerWMC update.
* '''Next Check''' - Displays date and time of next scheduled check for update.
* '''Version Info''' - Click to view change log for currently installed version.
* '''Automatically check for updates''' - When enabled, ServerWMC will automatically check for new updates. Disable if you wish to check for updates manually.
* '''Automatically apply new updates (requires elevated privileges or UAC disabled)''' - When enabled, ServerWMC will automatically install the newest version when found. For this feature to work, ServerWMC must either be "Run as Administrator" or "User Account Control" must be disabled.

|- valign="top" |
| || [[File:ServerWMC_Display_Options.png|right|border]]

=== Display Options ===
* '''Change name of timer to indicate series (repeating) recording'''
** '''Append''' - Places "this text" after the recording's title.
** '''Prepend''' - Places "this text" before the recording's title.
*** '''this text''' - Text to place before or after the recording's title
* '''Indicate 'Repeat' episodes in plot descriptions by appending''' - Places the specified text at the end of the plot description in the XBMC EPG episode info screen if the episode was marked as a repeat in the WMC EPG data.
* '''Indicate 'Repeat' episodes in recording/EPG titles by appending''' - Places the specified text following the recording title and in the XBMC EPG if the episode was marked as a repeat in the WMC EPG data.
* '''Hide content protected recordings.''' - Hides content marked as protected by the service provider from XBMC. (Protected content is only viewable from within WMC).
* '''For sporting events, always append episode title to main title.''' - Appends the title of the episode to main title. For example, "Monday Night Football" becomes "Monday Night Football - New England vs. Miami"
* '''Ignore Recording images from wmc url''' - Prevents WMC from sending recording image thumbnail url to XBMC (if found).
* '''Ignore Epg images from wmc url''' - Prevents WMC from sending EPG thumbnail image url to XBMC (if found).

|- valign="top" bgcolor="whitesmoke" |
| || [[File:ServerWMC_Tuners.png|right|border]]

=== Tuners ===
* '''Tuner''' - Displays information about the tuners available to ServerWMC through WMC.
* '''Space''' - Indicates the signal band of the respective tuner.
* '''Channels''' - Displays number of channels available on the respective tuner.
* '''Status''' - Displays availability of the respective tuner.
* '''Clients''' - Displays client connected to the respective tuner (if any).
* '''Reset''' - Check this box to manually reset the respective tuner.
* '''Refresh''' - Click to refresh the info displayed on the "Tuners" tab.

|- valign="top" |
| || [[File:ServerWMC_Live_TV.png|right|border]]

=== Live TV ===
* '''Set the maximum run time of a Live TV stream'''
* '''Enable prime viewing time'''
** '''Start'''
** '''End'''
* '''Only remux this language to output (if available)''' - Instructs ServerWMC to only include the specified audio language in the stream sent to XBMC. For information on locating the codes available in your stream, please see [[PVR/Backend/ServerWMC#Locating audio stream codes|Locating audio stream codes]]. We have reason to believe (though not confirmed) these codes follow the [http://en.wikipedia.org/wiki/List_of_ISO_639-2_codes ISO 639-2 standards.] Confirmed valid codes for this field are as follows:
** eng = English
** ger = German
** spa = Spanish
** dut = Dutch

* '''Tuners found:''' Displays information about the tuners accessible for streaming to clients
** '''Space''' - Type of signal being provided for streaming
** '''Count''' - Number of tuners available for streaming
** '''Channels''' - Number of channels available for streaming
** '''Hardware Name''' - The name of the tuner providing the stream

|- valign="top" bgcolor="whitesmoke" |
| || [[File:ServerWMC_Recordings.png|right|border]]

=== Recordings ===
* '''Group recordings in folders''' - Groups recordings into folders within the XBMC 'Recordings' list. This does not effect the physical location of the files. As well as the individual options below, this will also cause series recordings to be grouped into folders with the series name as the folder title and places individual episodes contained within. With this option disabled, a flat list of all recordings will be displayed on the 'Recordings' list.
** '''Group active recordings in folder''' - Groups active recordings into a folder with the name specified
** '''Group movie recordings in folder''' - Groups completed recordings of programs marked as a movie in the EPG data in the folder specified
** '''Group sports recordings in folder''' - Groups completed recordings of programs marked as a sporting event in the EPG data in the folder specified
* '''Append episode title to series title for recordings using''' - Places the episode title following the series title using the delimiter entered in the box.
* '''Remux active recordings''' - This remuxes the active recording to a TS file before being streamed to XBMC. Files can be played right away but may encounter issues when attempting to timeshift. Disabling this option will stream the WTV file directly to the XBMC player. This will allow for smoother timeshifting but will cause the recording to stop prematurely as XBMC does not monitor the size of WTV files. Premature stopping of playback can easily be resumed by pressing play again which effectively communicates the new file size (and in turn new end point) to the XBMC player. This setting will be used more in the Gotham release affecting the ability of clients to resume playback. The default setting is enabled.

|- valign="top" |
| || [[File:ServerWMC_Channels.png|right|border]]

=== Channels ===
* '''Reload channels from WMC''' - Used to reload channel info from WMC if it has been updated without requiring ServerWMC to be restarted.
* '''Order channels by:''' Designates the manner in which the channels will be arranged in the EPG within XBMC
** '''Number''' - Arranges the channel lineup by number
** '''Name''' - Arranges the channel lineup by name (or call sign).
* '''Channel display format:''' - Specifies now the channel name and number will be displayed within XBMC. For example, if settings were set as displayed in the screenshot, 'The WB' would displayed as 'KWGN/656'.
* '''Hide DRM channels''' - Hides channels marked with DRM by the service provider from the EPG.
** '''Indicate DRM channels by appending:''' - If a channel is marked by the provider as being protected with DRM, the text entered in the box will be appended in the EPG.
* '''Hide encrypted channels''' - Hides channels marked as encrypted by the service provider from the EPG.
** '''Indicate encrypted channels by appending:''' - If a channel is marked by the provider as being encrypted, the text entered in the box will be appended in the EPG.
* '''Import WMC channel icons when found''' - Imports channel icons from WMC if available. Please see [[PVR/Backend/ServerWMC#Adding icons to WMC|Adding Icons to WMC]] for additional information.
* '''For channel name use:''' - Specifies how the name of the channel will be displayed within XBMC.
** '''Call Sign''' - Displays the channel name as it's call sign reported by WMC. Example: 'KWGN'
** '''Full Service Name''' - Displays the channel name as the service name reported by WMC. Example: 'The WB'

|- valign="top" bgcolor="whitesmoke" |
| || [[File:ServerWMC_Record.png|right|border]]

=== Record ===
* '''Pre-Start and Post-Stop Padding Defaults''' - This tab allows the user to specify default padding for recordings. Padding is the amount of time to record before and after the scheduled start and finish time of a program as specified by the EPG.
** '''Use WMC's padding''' - Uses padding settings specified in WMC. Settings can be found in the WMC interface under Tasks / Settings / TV / Recorder / Recording Defaults. The settings are specified as "Start when possible" and "Stop when possible".
** '''Use XBMC's padding''' - Use padding specified in XBMC.
** '''Use this padding (min)''' - Allows the user to specify the desired amount of padding directly from the ServerWMC interface.
*** '''Pre''' - Amount of time (in minutes) to start recording before the EPG scheduled start time.
*** '''Post''' - Amount of time (in minutes) to record after the EPG scheduled end time.
** '''Use custom padding for sports (min)''' - Allows the user to specify settings different from those above for programs marked as sporting events in the EPG.
*** '''Pre''' - Amount of time (in minutes) to start recording before the EPG scheduled start time.
*** '''Post''' - Amount of time (in minutes) to record after the EPG scheduled end time.
* '''Force this padding on all recordings''' - Forces specified options ''even if they will interfere with other scheduled recordings''.
** '''Force Pre-Start padding''' - Forces the pre-start padding rules specified above.
** '''Force Post-Stop padding''' - Forces the post-stop padding rules specified above.
* '''After instant recording starts, each Record button press increases end time by: (min)''' - When an instant recording is in progress, each press of the record button will extend the recording time beyond the EPG scheduled end time + padding by xx minutes. Please see [[Add-on:PVR.WMC#Recording_with_pvr.wmc|Recording with pvr.wmc]] for additional information.

|- valign="top" |
| || [[File:ServerWMC_Debug.png|right|border]]

=== Debug ===
* '''Server Version:''' - Displays the version of ServerWMC installed followed by the names of clients connected and the version(s) of pvr.wmc respectively.
* '''Keep a log file''' - Checking this box will cause ServerWMC to output important troubleshooting information to a log file. It is '''highly''' recommended this box be checked.
** '''Current log''' - Opens the log file for the current ServerWMC session in Notepad.
** '''Last run's log''' - Opens the log file for the previous ServerWMC session in Notepad.
** '''Service log''' - Opens log file for ServerWMC if it is being run as a service.
* '''Delete temporary stream files''' - When switching to a channel, it automatically starts recording. This information is stored in a temporary file to allow for time shifting. When checked, these files will be deleted when changing channels.
* '''Remux the playback of all WTV files''' - By default, only live streams are remuxed to TS before being sent to the client. This option enables remuxing of pre-recorded files as well. Raspberry Pi users have reported issues with playing large pre-recorded WTV files. If you are experiencing issues with viewing recorded TV, please try enabling this option.
* '''For advanced users'''
** '''Edit Settings File...''' - Opens the settings file for manual editing
** '''Reload Settings File''' - Reloads the settings file after being manually edited causing the changes to take effect without restarting ServerWMC.
<br />
<br />

{{note|'''If you are having issues and need to request assistance in the XBMC forums, it is mandatory to provide a copy of the log files!!!''' They contain important information that is instrumental in diagnosing issues and recommending solutions. Please copy the contents of the file to [http://pastebin.com/ pastebin] and include the link in your post. Posting of log files directly to forum threads is strictly prohibited per the rules of the XBMC Forums.}}

|}

<br />

== Connecting ServerWMC to XBMC ==
Please install and configure the pvr.wmc add-on to access live TV from within XBMC using ServerWMC.

Please see the pvr.wmc Wiki page for additional information here: '''[[Add-on:PVR.WMC]]'''

{{Next|[[Add-on:PVR.WMC|Connecting ServerWMC to XBMC]]}}

== Troubleshooting / FAQ ==
* '''Can I record to a network share, NAS drive, etc.?''' - Unfortunately no. This is not supported by WMC. Recordings must be saved to a drive connected directly to the PC running WMC. This is done because if there is a glitch in the network connection while recording, it will corrupt the entire recording rendering it unwatchable.

{{note|Advanced users can attempt to "trick" WMC into thinking a local drive is being used, using methods such as linking the recorded TV folder to a network location with a NTFS directory junction (aka symlink) or presenting a drive from their NAS using ISCSI. In both cases WMC believes it is recording to a local drive, however the drive/files actually are located on a network device.}}

== Known Issues ==
* '''Upgrading from Windows 8 to 8.1''' - When upgrading from 8 -> 8.1, it is necessary to re-install ServerWMC.

== Additional Guides and Links ==
* ServerWMC/pvr.wmc Support Forum - http://forum.kodi.tv/forumdisplay.php?fid=205
* pvr.wmc Raspbmc Suport Thread - http://forum.stmlabs.com/showthread.php?tid=10553

== Advanced Topics ==
{| cellpadding="8" cellspacing="0"
|- valign="top" |
| ||
=== Locating audio stream codes ===
Start a live TV stream in XBMC. Open the ServerWMC log file and locate the audio descriptors. In the following example excerpt of the log file, there are two available audio streams. The codes are highlighted. These are the codes that can be used to specify the desired audio stream sent to XBMC under [[PVR/Backend/ServerWMC#Live TV|Live TV / Remux Language]]. We have reason to believe (though not confirmed) these codes follow the [http://en.wikipedia.org/wiki/List_of_ISO_639-2_codes ISO 639-2 standards.]

'''If you identify and confirm a code that is not already contained in the list above, please add it or drop a comment in the [http://forum.kodi.tv/showthread.php?tid=176174 wiki thread]. Thanks!'''
<br /><br />
<code>
:2013/10/23 18:37:35.515 Remux::FindDescriptors> wtv scanned (0.15 sec), Streams found:<br />
:2013/10/23 18:37:35.517 > Other: ID:1 MPEG2 Sections and Tables<br />
:2013/10/23 18:37:35.518 > Other: ID:2 MPEG2 PES<br />
:2013/10/23 18:37:35.519 > Audio: ID:3 ({{highlight|'''eng'''}}) AC3 2.0 48000 Hz 192 kb/s<br />
:2013/10/23 18:37:35.520 > Video: ID:4 AVC High-4.0 1920x1080i fps: 25<br />
:2013/10/23 18:37:35.522 > Audio: ID:5 ({{highlight|'''nar'''}}) MPEG Audio V1L2 Stereo 48000 Hz 256 kb/s<br />
:2013/10/23 18:37:35.524 > Other: ID:6 MS TV Caption<br />
</code>

=== Adding icons to WMC ===
{| cellpadding="8" cellspacing="0"
|- valign="top" |
| ||
==== Automatically ====
Channel icons are extracted from WMC and provided to all PVR.WMC clients. Unfortunately, WMC does not populate channel icons on it own. You must add them using third-party software. [http://www.mychannellogos.com/ MyChannelLogos] is a quick and easy way to add these logos to WMC and in turn to PVR.WMC clients. There is a small donation required for the program. It's worth it, the program works flawlessly. (As of this writing, the minimum donation is $5).
<br />
<br />
==== Manually ====
* Set your Channel display format to {1}-{0} instead of {1}/{0} on the 'Channels' tab of the ServerWMC GUI.

* Rename your logos to call sign-number.extension. Example KDKADT2-2.1.jpg.

* Restart ServerWMC.

* Set your default folder for PVR thumbnails to where your logos are stored under {{highlight|bordered=yes|System → Live TV → Menu/OSD → 'Default folder for PVR thumbnails'}} within XBMC.

* If you add new logos, you will need to restart XMBC or scan for missing channels under {{highlight|bordered=yes|System → Live TV → Menu/OSD → 'Scan for missing icons'}} within XBMC.
<br />
<br />
|}

=== Running ServerWMC as a service ===
{{note|This is an experimental feature and recommended only for advanced users at this time.}}

* '''Limitations'''
** Service must be manually installed
** Service must be restarted if any settings are changed
** Standalone app must be configured to not clash with the service
** Standalone app is not aware of what the service is doing (you don't see current streams, channels transferred/loaded, etc)

* '''Installation'''
** Stop ServerWMC app from the system tray if it is running.
** Install ServerWMC_Service by running InstallService.bat (in the installed program directory) as administrator.
** Edit the ServerWMC config file (%ProgramData%\VDSoftware\ServerWMC\config.xml) and change RunAsService=false to RunAsService=true
** Start/Stop the ServerWMC service from the Windows Services admin interface.
** Use the ServerWMC app (now aware that you are running the service) to maintain settings.
** Restart the service whenever you make a change to settings via the UI or editing the config.xml manually
** The port specified in the service must be manually opened in he firewall

* '''Further Information'''
** '''Service Info''' - The service is called "ServerWMC XBMC PVR Backend" (the shortname for the service is ServerWMC_Service). Currently, the service is not automatically installed by the program installer, instead there is a batch file in the install directory to do this. This only needs to be done once and wont need to be done again for future releases. The service is installed as manual startup by default. If users want the service to start automatically when windows starts, then they should choose Automatic or possibly Automatic (Delayed Start) if there are problems with it accessing the WMC services if it starts too early.
** '''Settings''' - The service shares the settings with the standalone app, which are stored in config.xml in the ProgramData directory. NOTE that any changes to these settings are not picked up by the service automatically. You must RESTART the service after making any settings changes to this file directly or via the ServerWMC UI.
** '''Standalone ServerWMC App''' - You must set the standalone ServerWMC app to know that you are running the service, otherwise they will both try and bind to the listen port and accept client requests (causing one or both to fail). This is done by setting the RunAsService parameter in the config.xml file to true while the app is not running. The app no longer needs to be running, it is only used for editing settings. The app does not show information about current streams, current connected clients etc. It has no knowledge of what the service is doing, it is purely used to maintain the settings file.
** '''Log''' - The service has it's own log file, called ServerWMC_Service.log in the same directory as the normal log (%ProgramData%\VDSoftware\ServerWMC). '''If you are posting for help/support and are running in service mode, you will need to provide this log instead of the ServerWMC.log'''
<br />
<br />

=== Sharing the TV and EPG databases using MySQL ===
{{note|Though it is ''possible'' to share these databases using MySQL, preliminary testing has shown '''absolutely no benefit''' and is known to actually ''cause'' issues. This method is '''completely unsupported by the devs. Consider yourself warned'''.}}

Assuming you are already using MySQL with XBMC, add the following to advancedsettings.xml:<br />
{{code |lang=xml |
<epgdatabase>
<type>mysql</type>
<host>10.0.1.100</host>
<port>3306</port>
<user>xbmc</user>
<pass>xbmc</pass>
</epgdatabase>

<tvdatabase>
<type>mysql</type>
<host>10.0.1.100</host>
<port>3306</port>
<user>xbmc</user>
<pass>xbmc</pass>
</tvdatabase>
}}

Please replace the 'host' IP addresses, 'user' names and 'pass'words accordingly.

If you have not setup MySQL and wish to, please see the guide here: [[HOW-TO:Share libraries using MySQL]]

|}

[[Category:PVR|*]]
[[Category:Live TV]]

Add-on introduction

2018-10-26T18:21:01Z

Gamester17:

{{mininav|[[Development]]|[[Add-on development]]}}<br />

= Introduction =

== Purpose ==

• to provide a guide for would be Kodi Python plugin addon script developers
• to provide the skeleton frameworks to enable script developers to get up and running quickly
• to provide links to authoritative sources of information for script developers

== Caveats ==

• This document does not try to teach you how to program in Python
• This document does not cover developing for the core Kodi system

== Conventions ==
Any commands that you need to type at a terminal are shown thus;
sudo apt-get install xbmc
Any program examples, i.e. code that you will type in is shown thus;
import urllib,urllib2,re,xbmcplugin,xbmcgui
# TV DASH - by You 2008.
def CATEGORIES():
addDir('','',1,'')
addDir( '','',1,'')

== Prerequisites ==

The first two of these are really nice to haves. If you are not a programmer, there is nothing to stop
you giving it a go, it'll just take a bit longer is all.
• Some knowledge of application development, particularly in a GUI environment
• Knowledge of Python scripting
• Installed version of Kodi 10 (Dharma) minimum – you do not need the development
source version

== First Steps ==

The development user
This document assumes for the purposes of illustration, that the user that you installed Kodi with
is 'xbmc' and that that user has all rights to the /home/xbmc directory. Please bear this in mind if
you installed under a different user name on your box.
In addition you may want to set up another user on the Kodi server that you will use to login as
the developer. This user should have sudo rights on a Linux based system. This is your
development user.
Your development environment
You need to consider how you want to work whilst programming. Three options are given in order
of preference.

== Local working on your PC ==

Using a separate development environment is by far the easiest and preferred method of
development. You will need to install Kodi on your local machine and run it there. In some
senses this is not a bad idea as you can install a plain vanilla Kodi and concentrate on
developing and testing your addon in isolation, moving it to your 'production' machine for final
integration testing and thence on into the wild. In this case you can install XBMC1 as your
normal logged on user and you shouldn't need to worry about file permissions etc. You can run
XBMC in a window to see the results of your work. (Go to System Settings - System Settings –
Video Output and set Display Mode to Windowed.) Having a dual screen set-up can be very
beneficial in this scenario.

== Local working on the Kodi server ==

This scenario is similar to working on a local machine except that you will need to install a
window manager (Linux machines), run Kodi in a window and connect a keyboard and mouse
to the machine (there are some nice wireless keyboards with touchpads about, Toshiba among
others do one.) Otherwise the set-up is the same as for a local PC installation.

== Remote working to an Kodi server ==
In this scenario you are going to use your Kodi server to run your code on, but use another
machine to do the coding from. You need to be able to access the server from the local machine.
Running Kodi under windows?
- share the xbmc user directory and set permissions for your development user to read and write
to the directory and its subdirectories
Running Kodi under Linux?
- Perhaps the easiest way to do this is to set the file permissions on /home/xbmc to allow the
group to read and write, enrol your development user name in the xbmc group. Set the sticky
bits for the xbmc user and group so that all new files are owned by the xbmc user /group
irrespective of who creates them;
sudo chmod -R u+s /home/xbmc/.xbmc
1 Fedora users can use a Dharma repository. See http://forums.fedoraforum.org/showthread.php?t=229121
sudo chmod -R g+rws /home/xbmc/.xbmc
sudo useradd -G xbmc your_dev_user_name
Then logon via ssh (or sftp) from your working machine. Alternatively, install Samba and set up
the shares so that you can access your Kodi installation as any user. Ref to Samba docs
In either OS, set up permanent mappings from your working machine to the Kodi server so
that your editors etc, can see the files

== IDE's ==

An integrated development environment is a good place to start when coding in any language.
Check out the following link for a list of free and non free offerings. Look out for ones that support
not only Python scripting, but also XML editing and in particular, local and remote debugging; as
someone once said – Professional programmers use a debugger!
http://wiki.python.org/moin/IntegratedDevelopmentEnvironments
See what other people are using at
http://stackoverflow.com/questions/81584

== Editors ==

If you don't/can't use an IDE, then check
http://wiki.python.org/moin/PythonEditors
for a list of editors that support Python in some way. And don't forget you can use any simple editor
such as Nano or Gedit in Linux, ? In Windows, ? In Mac to edit python source code
Access to documentation
It's a really good idea to have a web browser set up so that you have all the documentation you need
at your finger tips. So go ahead and download another browser that is different to your normal one
(e.g. I use Firefox for everyday stuff and Chrome as my Developers reference library,) or at least set
up a group of tabs in your regular browser that you can fire up when you are developing. See the
reference section at the end of this document for sites you will want to have at hand.

Notepad++ is a recommended editor.

Files should be saved as UTF-8 without BOM

== Access to documentation ==

It's a really good idea to have a web browser set up so that you have all the documentation you need
at your finger tips. So go ahead and download another browser that is different to your normal one
(e.g. I use Firefox for everyday stuff and Chrome as my Developers reference library,) or at least set
up a group of tabs in your regular browser that you can fire up when you are developing. See the
reference section at the end of this document for sites you will want to have at hand.

== See also ==
* [[Add-ons]]
* [[:Category:All add-ons]]
* [[Unofficial add-on repositories]]
'''Development:'''
* [[Add-on development]]
* [[Addon Settings]]
* [[Python development]]
* [[Skinning]]
* [[Add-on repositories]]
* [[Official add-on repository]]

[[Category:How-to]]
[[Category:Add-on development]]
[[Category:Skin development]]

About Add-ons

2018-10-26T18:20:30Z

Gamester17:

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

{{cleanup}}

== About Addons ==

Kodi Add-ons are extensions that can be run from inside the Kodi GUI. They are usually written by third party developers and published to our official repository. Add-ons can also be published in other repositories or as stand alone zip files anywhere on the internet. Examples of Add-ons include video website streams, scrapers, skins and scripts.

Kodi Add-ons are typically written in python.

Add-ons should work with the latest Krypton Release. Each time a new version of Kodi is released we add new features which may lead to a break compatibility. It is up to the author to update their add-on to remain compatible.

== Addon system using python ==
Kodi includes a built-in [http://en.wikipedia.org/wiki/Python_%28programming_language%29 Python interpreter] that allows users to develop add-ons (scripts and plugins) that interface easily and cleanly with the Kodi dashboard. These add-ons can extend the functionality of Kodi without requiring extensive programming experience or ability. While you may not feel comfortable browsing the Kodi source code and submitting patches (or even bug reports), you can learn how to write a script or plugin with just a few hours' practice, using the information available in these pages.

This page is intended as an introduction to Kodi Python for new developers, and a quick reference for more experienced programmers. If you're not interested in programming, you might want to visit [[Add-ons|this page]] for information about installing and using Python add-ons as an end user. If you're already familiar with Kodi Python, you can probably skip on down to the [[Python Development#Environment details|environment details]] or the [[Python Development#Resource links|resource links]] below for quick reference material.

== PyDocs ==

The very latest Kodi python API documentation "''PyDocs''" with classes and functions is automatically generated from XBMC's source code and can be found here (not all functions are available in previous versions):

* http://mirrors.kodi.tv/docs/python-docs/ (Main index page)
* http://mirrors.kodi.tv/docs/python-docs/12.2-frodo/ (for 12.2 Frodo)
* http://mirrors.kodi.tv/docs/python-docs/13.0-gotham/ (for 13.0 Gotham)
* http://mirrors.kodi.tv/docs/python-docs/14.x-helix/ (for 14.0 Helix)
* http://mirrors.kodi.tv/docs/python-docs/15.x-isengard/ (for 15.x Isengard)
* http://mirrors.kodi.tv/docs/python-docs/16.x-jarvis/ (for 16.x Jarvis)
* https://codedocs.xyz/xbmc/xbmc/group__python.html (for Kodi 17.x Krypton and onwards)

== Python plugins versus scripts ==
Please do not confuse "Plugins" and "Scripts". It is '''very''' important to understand the difference between them before you start coding your addon.
Unlike Scripts (which can basically perform any action), Plugins do not really provide new functionality to Kodi, instead what they do is provide
a directory listing (for instance, like your movie library) to Kodi. This listing can contain folders as well as files. When a user clicks on a folder,
kodi will run the plugin again to retrieve another listing. If a file is clicked, kodi will either play the file directly or call the addon to retrieve a playable url.

Another difference is that scripts can create their own gui (skin) while plugins can't. Plugin listings are presented in the current skin.

Do not try to mix and match script and plugin functionality as that will only give you weird error messages.

== Script development ==
If you're new to Python programming (or just new to Kodi Python), the easiest way to get started is with a script. The traditional Hello World program, written as an Kodi Python script, would look like this:

<pre><nowiki>print("Hello World!")</nowiki></pre>

That's the same code you would enter at the Python command line, because Kodi runs a full-featured, standard Python interpreter (for more information concerning the current version number and included modules see the [[#Environment details|environment details]] below). If you're already familiar with Python programming, the only new challenge is learning the [[#PyDocs|custom modules]] that allow you to gather information from Kodi and manipulate the Graphical User Interface (GUI).

There are some excellent tutorials available to introduce you to Kodi scripting (and Python in general). See the [[HOW-TO write Python Scripts|HOW-TO]] included in the Kodi Online Manual, or visit Alexpoet's Kodi Scripting site for a popular beginner's tutorial (PDF).

== Plugin development ==
While scripts offer you flexibility and full control over the Kodi GUI, plugins allow you to quickly and consistently present information to the user through the standard Kodi menu structure.

When a user launches a plugin, the plugin generates a list of menu items and hands them to Kodi to draw on the screen (regardless of screen resolution, skin, or any other user setting). While plugin developers lose some amount of control over the presentation, they no longer have to make up their own UIs, or worry about creating a usable look and feel across multiple displays.

Plugins are most commonly used to scrape websites for links to streaming videos, displaying the video list in Kodi just like it would movie files on the local hard drive.

== Resource links ==
While the three custom libraries give you control over the Kodi GUI, you'll eventually want to be able to interact with other parts of the system. Much of Kodi's functionality is exposed to Python, one way or another. These are some of the systems you can use to make your Python add-ons more useful.

=== Must read ===

A must read for developers is [http://www.python.org/dev/peps/pep-0008/ style guide] for writing python.
This contains the do's and dont's when starting to write code.

=== List of built-in functions ===
You can call any of the Kodi Built-in Commands using the function xbmc.executebuiltin().

[[List of Built In Functions]]

=== Kodi databases (media metadata libraries) ===
Kodi uses [[Music Library|Music]] and [[Video Library|Video]] Libraries, stored in a SQL (SQLite) database, to store massive amounts of additional meta data concerning local media files (assuming the user has enabled the libraries and chosen the right Content and scraper for each of his sources). Although there's no direct access from Python to the Kodi Database, you can gain access to the databases from Python through the [[JSON RPC]]. Read more about that [[The Kodi Database#Accessing the Databases with Kodi Python|here]].

{{tip|See [[Databases]] for database layout}}

=== InfoLabels ===
Kodi uses InfoLabels to display media file information (such as Artist and Album for a song, or Title and Cast list for a movie or TV show). This information shows up in the browsing menu (when using Library Mode), as well as in the Now Playing details when the media player is active.

You can get the currently-playing InfoLabel using the getInfoLabel function in xbmc. You can also set the InfoLabel information for any menu items you create in a plugin, making a much more versatile user experience.

{{see|InfoLabels}}

=== Other python pages ===
There are several other pages in the Kodi Online Manual dedicated to Python development. You can find a comprehensive list by clicking "Python" in the Categories list at the bottom of any Python page.
Definitely check out following pages with tons of great sample code.

* [[HOW-TO write Python Scripts]]

* [[HOW-TO:Write_Python_Scripts_for_XBMC]]

* [[HOW-TO write plugins for XBMC]]

* [[HOW-TO:Upgrade Python interpreter on Linux]]

* [[HOW-TO:Debug Python Scripts with Eclipse|HOW-TO:Debug_Python_Scripts_with_Eclipse]]

* [[HOW-TO:HelloWorld_addon]]

* [[HOW-TO:DebugAndDevelopPythonScriptsWithVisualStudio|HOW-TO:Debug and Develop Python Scripts with Visual Studio]]

* [[HOW-TO:Debug Python Scripts with Web-PDB]]

* [[Script Lyrics]]

* [[Script Sources]]

* [[Add-on unicode paths]]

Need to clean this up:

* [http://forum.kodi.tv/showthread.php?tid=99082| GUIDE HOW TO ADD A LOGIN FUNCTION TO YOUR ADDON]

* [http://passion-xbmc.org/index.php?page=python Passion list of pydocs]

* [http://translate.google.com/translate?hl=en&sl=auto&tl=en&u=http%3A%2F%2Fpassion-xbmc.org%2Fdocumentation-python%2Fcode-snippet-%28exemples%29%2F|Code Snippet]

* [http://forum.kodi.tv/showthread.php?tid=100167 python interface for google's JSON api]

* [http://forum.kodi.tv/showthread.php?tid=129401 addons_xml_generator.py for repository owners]

* [http://forum.kodi.tv/showthread.php?tid=36900 Tips for coding python scripts / plugins compatible with Linux, Mac, Windows AND Xbox]

* [http://forum.kodi.tv/showthread.php?tid=24839 WindowXML GUI Toolkit (replaces GUIBuilder for Kodi python scripts for GUI coding)]

* [http://forum.kodi.tv/showthread.php?tid=29577 HOW-TO write GUI settings for Kodi python plugins and scripts (addons)]

'''General Python Info:'''

* http://www.python.org/doc/

* http://www.diveintopython.net/toc/index.html

* http://pound-python.org/

* http://stackoverflow.com/questions/tagged/python

* http://python.net/~goodger/projects/pycon/2007/idiomatic/handout.html#id10

'''A few useful libs for scraping websites:'''

* http://pypi.python.org/pypi/simplejson/ (included in py2.6 + )

* http://effbot.org/zone/pythondoc-elementtree-ElementTree.htm (included in py2.6 + )

* http://www.crummy.com/software/BeautifulSoup/

* http://www.feedparser.org/

* http://wwwsearch.sourceforge.net/mechanize/

* http://wwwsearch.sourceforge.net/ClientForm/

== Environment details ==
{{see also|HOW-TO:Upgrade Python interpreter on Linux}}

Kodi comes with Python 2.7

== Migration to Python 3 ==

[[Migration to Python 3]]

== Out of Date ==
:With the release of Eden 11.0, some functions are out of date. Please view http://kodi.wiki/view/Eden_API_changes for the latest on incorporating Python scripts.
:With the release of Frodo 12.0, some functions are out of date. Please view http://kodi.wiki/view/Frodo_API_changes for the latest on incorporating Python scripts.
:With the release of Gotham 13.0, some functions are out of date. Please view http://kodi.wiki/view/Gotham_API_changes for the latest on incorporating Python scripts.
:With the release of Helix 14.0, some functions are out of date. Please view http://kodi.wiki/view/Helix_API_changes for the latest on incorporating Python scripts.
:With the release of Isengard 15.0, some functions are out of date. Please view http://kodi.wiki/view/Isengard_API_changes for the latest on incorporating Python scripts.
:With the release of Jarvis 16.0, some functions are out of date. Please view http://kodi.wiki/view/Jarvis_API_changes for the latest on incorporating Python scripts.

== See also ==
* [[Add-ons]]
* [[:Category:All add-ons]]
* [[Unofficial add-on repositories]]
'''Development:'''
* [[Add-on development]]
* [[Skinning]]
* [[Add-on repositories]]
* [[Official add-on repository]]

[[Category:Add-on development]]
[[Category:Development]]
[[Category:Python]]

Archive:Third-Party Tutorials

2018-10-26T18:17:42Z

Gamester17: Changing "3rd-party" to "Third-Party Tutorials" because we are not in 3rd-grade

{{mininav|[[Development]]|[[Add-on development]]}}
<br />
Below you will find some links to Third-Party Tutorials

== Third-Party Tutorials ==
* http://xbmc-plugin-dev.blogspot.co.uk/2013/06/our-first-plugin.html
* http://www.element14.com/community/community/raspberry-pi/blog/2013/06/26/creating-an-xmbc-plugin-hello-world
* http://t0mm0.github.io/xbmc-urlresolver/tutorials/resolverplugin/index.html
* https://github.com/romanvm/plugin.video.example

== Magazine Add-on Developer Guides ==
* Linux User & Developer - Issue 131, 2013 http://www.greatdigitalmags.com/view/linuxuser&developer/2589/linux-user-and-developer-issue-131

[[File:LinuxMag.jpg]]

[[Category:Add-on development]]

Archive:Third-Party Tutorials

2018-10-26T18:14:53Z

Gamester17: Gamester17 moved page 3rd Party Tutorials to Third-Party Tutorials: Changing "3rd-party" to "Third-Party Tutorials" because we are not in 3rd-grade

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

<br />
Below you will find some 3rd party links to Kodi Add-on tutorials

== 3rd Party Add-on Tutorial Links ==

http://xbmc-plugin-dev.blogspot.co.uk/2013/06/our-first-plugin.html

http://www.element14.com/community/community/raspberry-pi/blog/2013/06/26/creating-an-xmbc-plugin-hello-world

http://t0mm0.github.io/xbmc-urlresolver/tutorials/resolverplugin/index.html

https://github.com/romanvm/plugin.video.example

== Magazine Add-on Developer Guides ==

Linux User & Developer - Issue 131, 2013

http://www.greatdigitalmags.com/view/linuxuser&developer/2589/linux-user-and-developer-issue-131

[[File:LinuxMag.jpg]]

[[Category:Add-on development]]

Add-on manager

2018-10-26T18:12:42Z

Gamester17:

{{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 search for installed add-ons 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 browser ==
<gallery widths=400px heights=225px>
File:add-ons-accessing-1.png|'''Step 1:''' From the Home screen, navigate to the '''Add-ons''' menu item. Then select '''Enter add-on browser'''.
File:Add-ons-accessing-3.png|'''Step 2:''' The '''Add-on browser''', displaying five/six options (explained below).
</gallery>
{{note|You may also enter into the '''Add-on manager''' (see below) by just selecting '''Add-ons''' as show in '''Step 1'''}}

== How to access the Add-on manager ==
<gallery widths=400px heights=225px>
File:Add-ons-accessing-1.png|Select '''Add-ons''' from then menu on the Home screen.
File:Add-on_manager_main.png|From there you can select which add-on category you want to view.
File:Addon_manager_browser_access.png|You will also no longer be able to access the '''Add-on browser''', as shown above from the Home menu, once you have installed your first add-on. Instead you will have to enter the '''Add-on manager''' and select the '''BOX''' icon in the upper left corner.
</gallery>

== Add-on manager options ==

;My add-ons
:All installed add-ons, disabled or not, can be found in "My add-ons". This includes both a per-category listing as well as a single unified list of all installed add-ons.

;Available updates
:When an update to an add-on is available it will show up here. By default, add-ons are set to update automatically, so this should normally be empty unless you have changed your preferences to prevent automatic update installs.

;Recently updated
:Shows as list of recently updated add-ons.

;Install from repository
:Allows you to install new add-ons from the installed repositories. ''Kodi.tv add-on repository'' is the official add-on repository that is already included in Kodi, but other add-on repository sources can also be installed. (see [[Unofficial repositories#How to install additional add-on repositories|How to install additional add-on repositories]] for more info)

;Install from ZIP file
:Allows the installation of an add-on or repository from a ZIP file, either from the hard drive or LAN.

;Search
:Allows you to search add-ons in the installed repositories and your installed add-ons.

=== Lefthand sidebar menu ===
[[File:add-on manager sidebar menu.png|500px|right]]
----
{{center|'''View options'''}}
;View
: The view mode that items are displayed as. Similar to other areas of the interface, such as the video and audio libraries. Common view modes include lists, icons, and variations on those.

;Order
: This allows you to order add-ons/repositories by '''Ascending''' or '''Descending'''.

;Sort by
:This will allow you to sort add-ons by '''Name''' or '''Last used'''.

;Search
:Allows you to search add-ons in the installed repositories and your installed add-ons.

;Check for updates
:This will search for updates for all add-ons.

;Settings
:This will take you '''Add-ons''' settings page in '''Settings/System''' (see below).

;Get more
:This will allow you to download and install other add-ons from a particular category.

{{note|Not all options will appear depending on what part of the Add-ons section you are in.}}
----
{{center|'''Settings/System/Add-ons settings'''}}
<section begin="update options" />
;Updates
: Choose how updates are handled. Options are as follows:
:* '''Install updates automatically''' At least once a day, add-ons that are listed in a repo will automatically be updated if an update is available. If the '''"Notifications"''' option is also enabled, then the user will receive an on-screen notification about the available update and install.
:* '''Notify, but don't install updates''' The same as above, but the update itself will not automatically install. The user will get a notification of available updates, and an "Available updates" folder will appear in the add-on manager list, allowing the user to manually apply updates either for all add-ons or per-add-on.
:* '''Never check for updates''' Kodi will not check for updates nor will it install any known pending updates. The user will also not get any notifications, because Kodi won't know about any pending updates.
<section end="update options" />
;Show notifications
: If '''"Install updates automatically"''' or '''"Notify, but don't install updates"''' are selected for '''Updates''', then selecting this will also show a notification in the Kodi GUI if add-on updates are found.

;Manage dependencies
:This will all you to individually update dependencies which are need by other add-ons.

;Running
:This will allow you to what add-ons are running.

;Unknown sources
:This will allow you to install or block add-ons from unknown sources. You will need to enable this for installing any add-on/repository not in the Kodi Add-on repository.

;Reset above settings to default
:This will reset all the Add-on settings to their defaults.
{{-}}

== 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.
;{{highlight| Select ''Install from repository'' -> Select the repository {{small|(if no other repositories are installed it will automatically open the Kodi Add-on repository)}} -> Select the add-on category -> Select the add-on -> Select ''Install''|bordered=yes}}
<big>To access the Add-on browser see: '''[[Add-on_manager#How_to_access_the_Add-on_browser|How to access the Add-on browser]]'''</big>
<gallery widths=500px heights=313px>
File:Installaddon1.png|'''Step 1:''' Select '''Install from repository'''. If no other repositories are installed then this will open directly into the '''Kodi Add-on Repository'''. If other repositories then a different window will open allowing you the choice of which repository you want to use.
File:Installaddon3a.png|'''Step 2''' Select the add-on category, in this case '''Look and feel''' (applies to Kodi Jarvis and up only).
File:Installaddon3b.png|'''Step 3:''' Select the add-on sub-category, in this case '''Skin'''.
File:Installaddon4.png|'''Step 4:''' Select the add-on you want to install, in this case the skin '''Aeon Nox'''.
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:Installaddon5.1.png|'''Step 6:''' Once you select install, Kodi will begin downloading your add-on and you will see the download progress beside the add-on's name.
File:Installaddon6.png|'''Step 7:''' Once the add-on and it's dependencies are installed you will be able to use that add-on. 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)

{{#widget:YouTube|id=y2z1moatN4E}}

<section end="HOW-TO install" />

== How to install from a ZIP file ==
<section begin="HOW-TO zip" />
'''Install from zip file''' allows you to install add-ons or repositories which may not be available in the '''Kodi add-on repository'''. To install a add-on or repository from a zip file you will need to enable '''Unknown Source''' from '''Settings/System/Add-ons'''. This can be done at the time of installation.

{{note|By enabling '''Unknown Sources''', Add-ons will be given access to your personal data stored on your device. By allowing, you agree that you are solely responsible for any loss of data, unwanted behavior, or damage to your device.}}

<big>To access the Add-on browser see: '''[[Add-on_manager#How_to_access_the_Add-on_browser|How to access the Add-on browser]] or [[Add-on_manager#How_to_access_the_Add-on_manager|How to access the Add-on manager]]'''</big>

<gallery widths=500px heights=313px>
File:Addon_install_from_zip.png|'''Step 1:''' Select '''Install from zip file'''

File:Addon_install_from_zip_1.png|'''Step 2:''' If you have not enabled '''Unknown Sources''', you will notified that it is disabled. If you wish to enable select '''Settings''', if you do not wish to enable select '''OK'''. If you have already enabled '''Unknown sources''' skip to '''Step 6''''.

File:Addon_unknown_sources.png|'''Step 3:''' When you select '''Settings''' you will be taken to the Add-ons settings window. Enable '''Unknow sources''' if you wish to install your add-on or repository from a zip file.

File:Addon_unknown_sources_1.png|'''Step 4:''' After you enable '''Unknown sources''' you will be presented with a '''Warning'''. Make sure you read and understand this warning, then select '''Yes''' if you wish to proceed.

File:Addon_install_from_zip.png|'''Step 5:''' If you have selected '''Yes''' and enabled '''Unknown sources''' you can then navigate back to the '''Add-on browser''' and once again select '''Install from zip file'''

File:Addon_install_from_zip_3.png|'''Step 6:''' You will now be presented with a browser window where you can navigate to where your zip file is stored. Your zip file can be stored anywhere your device has access to and can be either on local storage or a network share.

File:Addon_install_from_zip_2.png|'''Step 7:''' Once you have navigated to the zip file you want installed, select it then select '''OK'''. After your add-on and any dependencies have finished installing you will be able to use it. {{note|If you have issues with the add-on installing or after installing it does not work as intended, you will need to contact the '''Add-on Author'''.}}
</gallery>
<section end="HOW-TO zip" />

== Repositories ==

Repositories are storage locations from where add-ons can be retrieved from. They allow the user to browse for more add-ons of all types, as well as allowing Kodi to check them for updates to add-ons, so they don't have to be manually installed. Kodi comes with one official add-on repositories installed by default, ''Kodi.tv add-on repository''. However others can be added.

To install a new repository you must first find the ZIP file to install the repository, a list of [[unofficial add-on repositories]] (third-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 ==
There are several ways to update add-ons, depending on your settings in '''Settings→System settings→Add-ons'''.

'''<big>Automatic updates</big>'''

The first method, and easiest, is if you have '''Install updates automatically''' (default) enabled. With this method, any add-on installed that's in an installed repository will automatically update when there is a new one available.

'''<big>Check available updates</big>'''

The second method is if you have '''Notify, but don't install updates''' selected. Assuming that you have '''Show notifications''' also enabled in the settings, you will be notified when a update is available and you can use the following method to update. {{note|If you don't have '''Show notifications''' enabled you can still use this method, but you will not know when a update has become available}}.

<gallery widths=500px heights=313px>
File:Estuary_home_avialable_updates.png|'''Step 1:''' From the Home screen, naviagate to '''Add-ons''', then select '''Available updates'''.

File:Addon_update.png|'''Step 2:''' Select the add-on you want to update.

File:Addon_update_download.png|'''Step 3:''' The add-on will then download and install. When finished you will be notified that the add-on has been updated.
</gallery>

'''<big>Update all</big>'''

The third method is to update all add-ons. To do this, access the <big>[http://kodi.wiki/view/Add-on_manager#How_to_access_the_Add-on_manager Add-on Mangager]</big>.

<gallery widths=500px heights=313px>
File:Addons_update_all.png|Then at the top of the menu bar, select the update all icon (shown above). The number of available updates will appear next to the icon.
</gallery>

'''<big>Manually updating</big>'''

The forth method is to update manually.

<gallery widths=500px heights=313px>
File:Addon_update_manual.png|From the Home screen, select '''Add-ons''', then in the '''Add-ons manager''' select the correct category for your add-on or go to '''My add-ons''' (this can also be done from the Home screen) and select '''All'''. Navigate to your add-on and select it. Then select '''Update'''.

File:Addon_update_select_version.png|Select the version you want to update to and it will install.
</gallery>

'''<big>Update from ZIP file</big>'''

If you installed a add-on from a zip file and/or it isn't in a repository, then you will need to update from a zip file. To do this see <big>[[Add-on_manager#How_to_install_from_a_ZIP_file|How to install from a ZIP file]]</big>. Updating from a zip is the same method, just choose the new file to install.

== See also ==
* [[:Category:All add-ons]]
* [[Unofficial add-on repositories]] - Third-party add-on repositories
'''Development:'''
* [[Add-on development]]
* [[Python development]]
* [[Skinning]]
* [[Add-on repositories]]
* [[Official add-on repository]]

{{Updated|17}}

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

Quick start guide

2018-10-26T18:05:10Z

Gamester17:

{{mininav|[[First time user]]}}

= Introduction =
Hello and welcome to {{Kodi}}!!

{{Kodi}} is an award winning, open source, media centre that can play a wide variety of Music and Video formats in addition to viewing Live TV and using add-ons to further enhance your {{kodi}}.

{{Kodi}} is designed with the '''''[[w:Home cinema|Home Theater]]''''' in mind using a '''''[[10-foot user interface|10 ft interface]]''''' rather than on a small monitor while you sit at your desk. Because everything is designed with the home theater experience in mind, the best way to interact with {{Kodi}} is with a remote control, rather than a computer mouse. If it helps, think of {{Kodi}} as the ultimate DVD-player/set-top-box. Be aware that mouse functionality is limited.

<section begin="intro" />This guide is designed to point you to the correct information that will assist in correctly setting up your {{kodi}}. We strongly recommend you follow the guides to ensure the correct setup.<section end="intro" />

'''''{{red|We strongly urge you to not follow the numerous YouTube video guides as nearly all those guides have been written with the single minded purpose of Piracy and Copyright Infringement. THERE IS NO SUPPORT FOR THAT HERE AT {{kodi}}.}}

If you have not already downloaded and installed {{kodi}}, return to the previous page and follow the installation instructions for your chosen operating system.

= Wiki =
The wiki (where you are now) holds a wealth of information. For both the new and intermediate user, the second row '''Kodi Menu''' on the wiki '''''[[Main page]]''''' is all that you will require. That particular row holds the information for the menu items as seen in {{kodi}}. If you are not sure what a particular function does in {{kodi}}, then choose the appropriate item in that row.

All the links on this page are accessible from the '''''[[Main_Page|Main Page]]''''' of the wiki.

= Basic Controls =
Read this page to familiarise yourself with the menu system and other screens in {{kodi}}.
{{see|Basic_controls}}

= Library Mode =
;Why do I need a library?
One of the features that makes {{kodi}} so great is the ability to display all types of artwork and metadata (plots, directors, actors etc) in a visually stunning format.

The Libraries are accessed from the Main Menu using...
*Movies, TV Shows or Music Videos for the Video Library
*Music for the Music Library.

To use the numerous features that are only possible with a correctly setup library, then your video and/or music collections need to be added to the library to correctly function.

{{Kodi}} consists of two libraries - Music and Video. The following guides have been created to guide you through the setup process of both.

{{Index two column
| image 1 = Video.png
| link name 1 = Guide to Create, Modify and Re-build your Video Library
| link 1 = HOW-TO:Create_Video_Library
| link 2 = :HOW-TO:Create_Music_Library
| link name 2 = Guide to Create, Modify and Re-build your Music Library
| image 2 = Nuvola apps kscd.png
}}

= File Mode =
If you do not want to create the libraries and take advantage of these features, then you can '''''[[Add-on:Estuary/Settings#Main_Menu_Items_Settings|hide Menu items]]''''' and access your media through the inbuilt file browser located from the main menu by selecting '''Videos''' then '''Files'''.

Be aware that using this mode, {{kodi}} becomes a simple media player with limited functionality. There will be no extended artwork and no movie information amongst many other missing features which all require a library to function. In effect, {{kodi}} is a simple file browser similar to Windows Explorer, and will simply allow you to browse your folders and files as set up on your hard drives.

= Adding Pictures =
{{main|Pictures}}
The Pictures option allows you to add your home photo collection to {{kodi}} which you can then easily display on your large, high definition TV screen.

Pictures does not yet use any library functions and is simply a file browser. If you set up either the video or music library, you will be familiar with setting up a source for pictures.

= Adding Games =
{{main|Games}}
Note! Games support are not available before Kodi v18 Leia! The Games option allows you to add stand-alone games and games running in emulators which can be launch from Kodi.

Games does not yet use any library functions and is simply a file browser. New in Kodi v18 Leia is also many an input manager with many game controller settings for configuring gamepads, joysticks, keyboards, and mouses, for use inside those games/emulators that are running natively inside Kodi's runtime.

= Using a remote control =
{{main|Remote controls}}
{{#lst:Remote controls|intro}}

= {{Kodi}} add-ons =
{{Main|Add-ons|Add-on manager}}
{{#lst:Add-ons|intro}}

= Changing Skins =
{{Main|HOW-TO:Change_skins}}

Most other media players come with a single type of menu interface. Picture your dvd player or your set top box with it's basic menu system. {{Kodi}} has the ability to change its user interface (skin) to something that suits your taste. There are over 40 skins to choose from, each with their own attractions and features. Feel free to explore...

To get new skins, go to: {{highlight|Settings → Interface settings → Skin → Skin - Estuary|bordered=yes}}

You will be provided a list of currently installed skins and an option to "Get More..." where you can download additional skins.

Preview images of a few skins...

<gallery caption="The same home screen using different skins" widths=200px heights=113px>
File:Estuary_home_movies.png| Estuary - default skin, Kodi 17 & above
File:Confluence_ss.png|Confluence - default skin, Kodi 16 & below
File:Aeon Nox - glass home.jpg|Aeon Nox
File:ReFocus home.png|ReFocus
File:Titan.jpg|Titan
File:Welo.jpg|Welo
File:Transparency.jpg|Transparency
File:Skin.rapier.16.png|Rapier
File:Mimic004.jpg|Mimic
</gallery>

{{top}}

<div style="{{linear-gradient|left|#ffdddd, #ddffdd 50%, #ddddff}}">{{next|[[Video_library|Video Library Main Menu]]}} </div>
<br />
<div style="{{linear-gradient|left|#f5d3ff, #12b2e7}}">{{next|[[Music_library|Music Library Main Menu]]}} </div>

{{updated|17}}
[[Category:FAQ]]
[[Category:Index]]
[[Category:Guides]]
[[Category:Manual]]
[[Category:Karellen]]
[[Category:Video library]]
[[Category:Music library]]
[[Category:Advanced topics]]
[[Category:First time user]]
[[Category:Quick Start Guide]]

Basic controls

2018-10-26T17:56:26Z

Gamester17: /* Main Menu */

{{mininav|[[First time user]]}}

= Introduction =
'''Welcome new user!!''' <section begin="intro" />You have finally installed Kodi on your equipment, launched it, and then probably sat there for a few minutes scratching your head thinking what is this?? This page will describe the commonly used screens and basic navigation around Kodi. Its aim is to allow you to become familiar with Kodi and prepare you for the upcoming setup pages.<section end="intro" />

This page will not describe how to load your media. That task is covered in the following pages. As with most pages of the wiki, this page assumes you are using the default skin '''[[Estuary]]'''. If you are using another skin, then you have run before learning to walk, so you should change back until you have at least set up Kodi.

Kodi has been designed around the ''[https://en.wikipedia.org/wiki/10-foot_user_interface 10 foot interface]'' principle. This means that Kodi is best used with a remote control while sitting on your couch looking at your TV. It was not designed for use on a computer sitting at a desk with keyboard and mouse. '''If you choose to use it this way, then be aware that the navigatione experience won't be as smooth as a remote control.'''

{{red|Although this guide applies to all parts of Kodi, some portions have been based on the Video/Movies/TV Shows section of Kodi. To see the specific Basic Controls for Music, see '''''[http://kodi.wiki/view/Music_navigation Music Navigation & Playback]}}

The following image is a screenshot of the Home Screen when Kodi launches. In this case there is media in the library, but you may not have media in your library yet.

[[File:HomeScreenGuide.jpg|left|900px]]
{{-}}

= Power Options =
[[File:Estuary-power-menu.jpg|right|300px]]
Pressing {{keypress|S}} on the keyboard, or by selecting the Power icon in the top left corner of the home screen calls up the Power Options menu. Depending on your hardware, your Power Options may have more or less options to that shown in the image.

The options on this menu are from top to bottom:

;Exit
:Exits Kodi to your operating system.
;Power off system
:Powers down your computer
;Custom Shutdown Timer
:Kodi will shutdown your computer after you enter the countdown time. Enter the time interval in minutes.
;Suspend
:Suspends your computer.
;Hibernate
:Hibernates your computer.
;Reboot
:Restarts your computer.
;Log off <ProfileName> user
:If using Profiles, the option to log out the current user and login as a new user is this option. <ProfileName> will display the name of the currently logged in Profile/User.

= Settings =
The Settings Icon in the top left of the screen provides access to the Kodi Settings pages. Most general use settings are contained in these pages. During your travels with Kodi, you will come across mention of the advancedsettings.xml file. This holds advanced Settings for Kodi and can be modified by the user.

For more information on the Settings pages, {{See|Settings}}

For more information on the advancedsettings.xml file, {{see|AdvancedSettings.xml}}

= Search & Filter =
[[File:GlobalSearch.jpg|right|300px]]
The Global Search function allows you to search your library, add-ons or some on-line sources for information.

Some of the pictured options will require installation of an add-on. Simply confirm the installation of the add-on when prompted.

{{see|Add-on:Global_Search}}
{{see|Add-on:YouTube}}
{{see|Add-on:ExtendedInfo_Script}}
{{see|Advanced_library_filtering}}

There are also Search functions inside each of the Main Menu options which are accessible from the [[Basic_controls#Sideblade_Menu|Sideblade Menu]]. These are called '''Filters'''. The function "filters" the currently displayed list to match your query. When using the Filter function, be aware of the following:
*The Filter will only filter that class of media, so performing the Filter in Movies will only return Movie results.
*The Filter only works when you have a listing of media displayed. If you do not have a listing of the media to Filter, then the filter will return a ''Not Found'' result.
{{-}}

= Main Menu =
All classes of media are separated into their own menu options. The default classes are listed below. Other skins allow you to add additional menu items for, say, Home Movies, Cartoons, Disney etc.

It is possible to remove unwanted menu options and to re-add them at a later date. Very useful for those options that remain unused in your setup such as Live TV, Radio etc. See: '''''[[Add-on:Estuary/Settings#Main_Menu_Items_Settings|Hiding Menu items]]'''''

As each Main Menu option is selected, the Home Page will dynamically update with information relevant for the selected menu option. The full list of available menu options are as follows:

* '''[[Games]]''' (not available before Kodi v18 Leia) - This is a shortcut to a file manager view, which when viewed, can show your games.
* '''[[Video_library|Movies]]''' - This is a short cut to the "All movies, by title" node in the video library.
* '''[[Video_library|TV shows]]''' - This is a short cut to the "All TV shows, by title" node in the video library.
* '''[[Music_library]]''' - This is a shortcut to a file manager view, which when viewed, can show your music files either by genre, Artist, Album, Song, or by year.
* '''[[Music_library|Music Videos]]''' - This is a shortcut to a file manager view, which when viewed can show your music video files either by Genre, Title, Artist, Albums, Directors, Studio or Tags
* '''[[Live_TV|Live TV]]''' - With a PVR add-on, this can give you Free To Air Television channels with an EPG (Electronic Program Guide) with Pause/Rewind/Fast Forward and Record facilities
* '''[[Live_TV|Radio]]''' - With a PVR add-on, this can give you Free To Air Radio Channels with an EPG (Electronic Program Guide)
* '''[[Add-ons]]''' - This shortcut takes you to a secondary menu that lists your installed add-ons by type, such as 'Video-addons', Music add-ons, Program add-ons. In this menu you can install add-ons from the official Kodi repository. '''''See: [[Add-ons]]'''''
* '''[[Pictures]]''' - Shows a basic file-based image viewer, as well as picture-related add-ons.
* '''[[Video_library]]''' - Shows the top level of all video areas, including file views, movie library, TV show library, music video library, playlists, and video related add-ons. Users can also use this to navigate to more '''[[video nodes|nodes]]''' in the library, showing movies or TV shows by year, genre, actor, or even custom created nodes for specific people, moods, etc.
* '''[[Favourites]]''' - Show all your meda that has been tagged as a 'Favourite'
* '''[[Weather]]''' - Once set up, this will show the weather forecast in your local area

= Home Screen =
The term '''Home Screen''' can be used to mean the entire screen as depicted in the image in Section 1 above. If it is prefixed by a menu item, say ''Movies Home Screen'' or ''TV Show Home Screen'', then it refers to the section to the right of the Main Menu. The following information refers to the latter.

The Home Screen contains a dynamic list of media relevant for the selected main menu item. If you select Movies, then the ''Movie Home Screen'' will display a number of items as follows:

;Categories- also known as Nodes
:A quick link to the available Movie Nodes. It allows you to navigate your Movie library via Genres, Title, Year, Country Actors, Directors, Studios, Sets, Tags and Recently added
{{see also|Video_nodes|Music_nodes}}

;Poster views
:Displays movie titles that fit into the following criteria:
*In-progress
*Recently added
*Unwatched movies
*Random selection
*Movie Sets

;Genres
:Quck icon selection of available Genre's in the library.

;Studios
:Quick icon selection of available Studios in the library.

The other classes in the main menu have a similar selection but designed and named to be most relevant for their class of media.

= '''Sideblade Menu''' =
[[File:EstuarySideBarMenu_small.gif|right]]
[[File:Estuary-player-sidebar-video.jpg|210px|right]]

'''{{resize|1.4em|{{red|The Sideblade Menu is a critical menu that holds numerous options. It is available in most locations. ''REMEMBER ITS EXISTENCE''}}}}'''

The Sideblade Menu is accessible from '''most''' screens in Kodi.

{{red|The menu options shown below are for the Movies section. The options will vary for the other media classes}}

<section begin="SidebladeMenu" />You can invoke the sideblade using one of the following methods:
* pressing the {{keypress|left}} key on your remote control
* pressing the {{keypress|left}} key on a keyboard
* bringing the mouse cursor to the left border of the screen.<section end="SidebladeMenu" />

The options in the Sideblade Menu vary. The following is the menu in the Movies listing.

'''Available Options'''

;ViewType
:Change current library view.

;Sort by
:Select how the list of Movies/TV Shows/Episodes are sorted- eg Title, PlayCount etc

;Order
:Once the ''Sort by'' is selected, do you want the order Ascending or Descending

;Filter
:Allows you to filter your list on certain criteria- eg Director, Actor, Ratings, Tags etc '''''See: [[Basic_controls#Search|Search]]'''''

;All Videos / Watched / Unwatched
:Global toggle that allows you to select what is shown in the list - All Videos, Watched or Unwatched videos only

;Update library
:Scans the library for newly added Movies, TV Shows, Episodes and Music Videos

;Go to playlists
:Will open the currently playing Party Mode playlist

;Bottom Icons- From Left to right
*Pause
*Stop
*Skip to next video
*Open Play Mode screen. Displays Fanart and video information. aka Now Playing screen.

To see the Sidebar Menu for '''Music''' see '''''[[Music_navigation#Sideblade_Menu|Music Sideblade Menu]]'''''
{{-}}

= '''Context Menu''' =
'''{{resize|1.4em|{{red|The Context Menu is a critical menu that holds numerous options. It is available in most locations. ''REMEMBER ITS EXISTENCE''}}}}'''

The '''Context Menu''' allows quick access to a limited set of functions relevant for the currently selected item.

<section begin="ContextMenu" />After highlighting an item (eg a movie) the Context Menu can be invoked by:
* long press the {{keypress|OK}} key
* Press letter {{keypress|C}} on a keyboard
* right-clicking with the mouse<section end="ContextMenu" />

References to Context Menus are scattered throughout the wiki on relevant pages and can be found easily enough in Kodi. As there are many, many types of context menus, it would be uneconomical to list them all here.

The following are a few examples of the context menu.
<gallery widths="300" heights="200">
File:MovieSets02.jpg|The context menu in the ''Movie library''.
File:EstuaryContextmenu2.png|The context menu in the [[Add-on:YouTube|YouTube]] add-on.
File:EstuaryContextmenu3.png|The context menu in the ''Video file browser''.
File:EstuaryContextmenu4.png|The context menu in the ''Favourites menu''.
</gallery>

= '''Information Page''' =
[[File:Artwork-Actors01.jpg|right|500px]]
<section begin="InformationPage" />For each title in the Movies, TV Shows and Music Videos library, an Information Page is available as displayed in the image.

This screen will display the metadata for the title. A number of options are available along the bottom of the page. What is displayed will depend on the skin in use and which class of media is displayed (Movie, TV Show, Music Video)<section end="InformationPage" />

This is a Library only feature and will not work on titles not in the library. Attempting to perform this in the File Browser using Videos>Files will commence the scrape process for that individual title. '''''See: [[Updating_or_removing_videos|Update Video Library]]'''''

To access the Information Page, navigate to, and highlight the required Movie, TV Show or Music Video title. Once highlighted use one of the following methods to view the Information Page:
*Press {{keypress|i}} on a remote control, or Press {{keypress|i}} on a keyboard
*Using the '''''[[Basic_controls#Context_Menu|Context Menu]]''''', select '''Information'''

Available option buttons (not all are displayed in the image)
;Actors image
:Clicking on the image of an actor will bring up a listing of other titles, in your library, the actor appears in
:Installing the '''''[[Add-on:ExtendedInfo_Script|ExtendedInfo add-on]]''''' will provide extended actor information from online sources
;Play
:Commence playback of the title
;Your Rating
:Use this option to apply your personal rating to your media. The display of the User Rating depends upon the library view in use. It is displayed at the top of the Poster as a blue star containing the rating in Poster View. Each type of view displays it differently.
;Trailer
:Commence playback of the '''''[[TheMovieDB.org#TMDB_-_For_Moves|Trailer]]'''''. If no trailer is available, either the button will not be displayed or you will be offered to install the YouTube add-on to view online trailers.
;Show Fanart
:Full screen display of the fanart attached to the title
;Same director
:Displays a listing of other titles in the library from the same director
;Choose art
:Settings page that allows the manual selection of '''''[[Artwork]]'''''
;Refresh
:Allows you to rescan or rescrape the title. Useful if you have modified information in the NFO File, or you would like to re-scrape updated information from the site of the Information provider. '''''See: [[Updating_or_removing_videos|Update Video Library]]'''''
:Highlighting this button will also display the path to the playable file that {{kodi}} has recorded in the library database. Useful to track down duplicate entries.

= Now Playing Controls =
The Now Playing Controls are covered in more detail in the following two sections...

;Music Player Controls
:'''''See: [[Music_navigation|Music Navigation & Playback]]'''''

;Video Player Controls
:'''''See: [[Video_playback|Video Playback]]

= On Screen Keyboard =
[[File:OnScreenKeyboard.jpg|right|500px]]
When required, Kodi will display an on-screen keyboard to facilitate data entry. No special selection is required by the user as the keyboard will appear where required.

The on-screen keyboard can be used in the following ways:
*Remote control
*Mouse presses
*Using a physical keyboard.
{{-}}

= Remote Controls =
Kodi is best used with a Remote Control. Many types of Remote Controls can be used as listed on the following page.
{{see|Remote_controls}}

= Keyboard Controls =
If you are using a physical keyboard, the following page lists available keystrokes to control Kodi.
{{see|Keyboard_controls}}

= See also =
=== Favourites ===
{{main|Favourites}}
{{#lst:Favourites|intro}}

=== File Manager ===
{{main|File manager}}
{{#lst:File manager|intro}}

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

{{top}}

<div style="{{linear-gradient|left|#ffdddd, #ddffdd 50%, #ddddff}}">{{next|[[Video_library|Video Library Main Menu]]}} </div>
<br />
<div style="{{linear-gradient|left|#f5d3ff, #12b2e7}}">{{next|[[Music_library|Music Library Main Menu]]}} </div>

{{updated|17}}
[[Category:FAQ]]
[[Category:Index]]
[[Category:Guides]]
[[Category:Manual]]
[[Category:Karellen]]
[[Category:Video library]]
[[Category:Music library]]
[[Category:First time user]]
[[Category:Advanced topics]]
[[Category:First time user]]
[[Category:Quick Start Guide]]
[[Category:Music library|Music library]]

Devices

2018-10-26T17:45:01Z

Gamester17: /* HTPC and Media Appliance devices */

{{mininav}}
<section begin="intro" />This area of the wiki is all about various hardware topics as well as OS-specific topics. Everything from HTPCs to remotes to audio receivers. It is also another way to categorize and discover topics relating to specific hardware or OSes. Feel free to add or create pages/info as needed.<section end="intro" />

__TOC__
== General ==
{{big|
* '''[[Hardware requirements]]'''}}<br />
* [http://forum.kodi.tv/forumdisplay.php?fid=112 ''Hardware for Kodi'' forum]

== OS ==
{| width="100%"
| width="20%" align="center" | {{main page icon|image=Android OS.png|link=Android}}
| width="20%" align="center" | {{main page icon|image=iOS OS.png|link=iOS}}
| width="20%" align="center" | {{main page icon|image=Linux OS.png|link=Linux}}
| width="20%" align="center" | {{main page icon|image=Mac OS.png|link=Mac OS X}}
| width="20%" align="center" | {{main page icon|image=Windows OS.png|link= Windows}}
|}

== Components ==
* [[CEC]]
* [[Displays]]
* [[Audio]]
* [[Remote controls]]
* [[Ambient lighting]]
* [[LCDs|LCD info displays]]
* [[Networking]]
* [[PVR|PVR (Live TV)]]
* [[Philips Hue]] - smart bulbs for automatic playback dimming and ambient lighting

== HTPC and Media Appliance devices ==
{{Device notice}}

{{note|1=Have a device that isn't listed and want to tell people all about it? Request a wiki account and simply create a new page for it. If you need any help or want someone to make the page for you, feel free to leave a message on the '''[http://forum.kodi.tv/forumdisplay.php?fid=35 community forums here]'''.}}

{{Index two column
| image 1 = Amazon Fire TV.jpg
| link 1 = Amazon Fire TV
| image 2 = Asus Chromebox.jpg
| link 2 = Chromebox
| image 3 = Cubox-i.jpg
| link 3 = Cubox-i
| image 4 = Compulab-Utilite2.jpg
| link 4 = CompuLab Utilite
| image 5 = nexusplayer.jpg
| link 5 = Google Nexus Player
| image 6 = Intel NUC 4th Gen.jpg
| link 6 = Intel NUC
| image 7 = Nvidia SHIELD Console.jpg
| link 7 = Nvidia SHIELD Android TV
| image 8 = ODROID-C2.png
| link 8 = ODROID
| image 9 = Raspberry Pi Logo.png
| link 9 = Raspberry Pi
| image 10 = Razor Forge TV.jpg
| link 10 = Razor Forge TV
| image 11 = product1.png
| link 11 = WeTek Play
| image 12 = Xiaomi_Mi_Box_2016.png
| link 12 = Xiaomi Mi Box
| image 13 = Computer n screen.png
| link 13 = x86 hardware

}}

== See also ==
* [[Supported hardware]]
* [[Amlogic]]
* [[Freescale]]
* [[Nvidia Tegra]]
* [[x86 hardware]]

[[Category:Index]]
[[Category:Hardware|*]]

Archive:X86 hardware

2018-10-26T17:44:55Z

Gamester17:

{{mininav|[[Devices]]|page=x86 hardware}}
{{forum link2|1=Read this page and still need help? Check out the [http://forum.kodi.tv/forumdisplay.php?fid=112 ''Hardware for Kodi'' discussion forum].}}
<section begin="intro" />Computers and appliance devices with an [[w:x86|x86]] processor (a "desktop class" computer with a "normal" Intel or AMD x86/x86-64 based CPU) are the usually the most power-full and most stable option for an dedicated {{Kodi}} powered [[w:Home theater PC|HTPC (Home Theater PC)]] / media center computer.

Using standard x86 computer hardware provides a great amount of flexibility and can be made from spare parts, old laptop/desktop computers, or new dedicated hardware, and as such are also by definition upgradable.<section end="intro" />

==x86 HTPC (Home Theater PC)==
[[w:Home theater PC|HTPC (Home Theater PC)]] (or ''Home Theatre Personal Computer'') in the traditional meaning is a dedicated "media center" computer is a convergence device that combines some or all the hardware capabilities of a standard personal computer with an operating system and media player software application that supports video and audio playback, and sometimes can also offer video recording functionality. With the term "media center" referring to specialized media player application software such as [[{{Kodi}}]] which is designed to offer a nice [[10-foot user interface]] for a lean-back experience.

HTPC and other convergence devices integrate components of a home theater into a unit co-located with a home entertainment system. An HTPC system typically has a remote control and the software interface normally has a 10-foot user interface design so that it can be comfortably viewed at typical large screen television viewing distances. An HTPC can be purchased pre-configured with the required hardware and software needed to add video programming or music to the PC. Enthusiasts can also piece together a system out of discrete components as part of a software-based HTPC.

==x86 HTPC hardware==
Traditional HTPC in the classic sense means using standard or optimized desktop computer hardware to build a dedicated media center computer, but usually fitted into a purpose built computer chassi case that is design for being a HTPC / media center, however today most people looking to build a new HTPC usually go the route of just buying a Mini-PC instead.

=== Mini-PCs ===
Some people think that using desktop-class (x86) computer hardware parts to make-up a HTPC means having a huge ugly, noisy computer case next to your television set, but today this could not be further from the truth. The rise of the mini-PC (miniature personal computer) over the past few years have not only given a small option, but these small options are often powerful and budget friendly as well.

===Desktop PC hardware===
Using desktop PC hardware to build a dedicated HTPC usually means building your rig from scratch, and as of 2015 as well as the past 10-years the desktop PC hardware scene for HTPC purposes is still dominated by Nvidia GPU based hardware if you wish you use a Linux OS, or AMD GPU based hardware if you wish to use a Windows OS, but Intel CPUs with integrated GPU is quickly gaining a broader audience for both Linux OS and Windows OS builds.

You will basically need to build a custom rig with a GPU (graphics controller) that can at least hardware decode all H.264 files that you want to play. If you are looing for a multi-purpose machine for gaming as well then the CPU and GPU will also need to to meet the requirements for playing your types of games at the resolution you want, but then the question about which computer hardware to buy really become a complete different discussion.

For most dedicated HTPC purposes the difference between desktop PC hardware and a Mini-PC is however slight. The real benefit with using desktop PC hardware for media purposes is that it is upgradable, but if you just have a good 1080p television you really like then the recommendation will normally be to just buy a Mini-PC.

Here is a good starting point for the quest of building a HTPC from desktop PC hardware:
* http://whirlpool.net.au/wiki/rmp_sg_whirlpoolpcs_htpc

=== Recycle methods ===
Advice for reusing old or spare computer parts for an HTPC.
*

=== Mini-PC Examples ===
<gallery>
File:QuantumByte.jpg|[[Quantum Byte]]
File:Asus Chromebox.jpg|[[ASUS Chromebox]]
File:Intel NUC 4th Gen.jpg|[[Intel NUC]]
File:Gigabyte Brix.jpg|[[Gigabyte Brix]]
File:FitPC.jpg|FitPC
File:ASRock.jpg|ASRock VISION
File:EeePC.jpg|ASUS Eee Box
File:Lenovo.jpg|Lenovo Idea Centre
File:Foxconn.jpg|Foxconn mini PC
File:Shuttle.jpg|Shuttle SlimPC
File:Revo.jpg|Acer Revo
File:Zotac Zbox.jpg|Zotac Zbox
File:Zotac Zbox Nano.jpg|Zotac Zbox Nano
</gallery>

== OSes ==
{{list2|Linux}}
{{list2|Windows}}
{{list2|Android}}
=== JeOS implementations for Kodi ===
{{main|JeOS implementations for Kodi}}
{{#lst:JeOS implementations for Kodi|JeOS for Kodi}}

== 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.''}}
*

== Specific device pages ==
Here are a few device-specific guides/help areas that the community has provided.

{{Device notice}}


<dpl>
category = X86
category = HTPC
format = ,{{list2|%PAGE%}}
</dpl>
{{DISPLAYTITLE:x86 hardware}}

== See also ==
* [[Supported hardware]]
* [[JeOS implementations for Kodi]]
* [[Linux]]

==External Links==
* http://whirlpool.net.au/wiki/rmp_sg_whirlpoolpcs_htpc

{{Helix updated}}

[[Category:Index]]
[[Category:X86|*]]
[[Category:Hardware]]
[[Category:Linux]]
[[Category:Android]]

New features

2018-10-26T17:32:56Z

Gamester17:

{{mininav}}

__TOC__

<gallery mode="packed" widths="500px" heights="283px">
File:Kodi-Wallpaper-12B-1080p samfisher.jpg
File:Kodi-Wallpaper-14A-1080p samfisher.jpg
</gallery>

= New Features for Each Release =
For condensed lists of new ''features and functions'' that were implemented for a particular version, click the appropriate version in the list below.
* [[Kodi v18 (Leia) changelog]]
* [[Kodi v17 (Krypton) changelog]]
* [[Kodi v16 (Jarvis) changelog]]
* [[Kodi v15 (Isengard) changelog]]
* [[Kodi v14 (Helix) changelog]]
* [[XBMC v13 (Gotham) changelog]]
* [[XBMC v12 (Frodo) changelog]]
* [[XBMC v11 (Eden) changelog]]

= Frequently Asked Questions (FAQs)=
* [[Kodi v18 (Leia) FAQ]]
* [[Kodi v17 (Krypton) FAQ]]
* [[Kodi v16 (Jarvis) FAQ]]
* [[Kodi v15 (Isengard) FAQ]]
* [[Kodi v14 (Helix) FAQ]]
* [[XBMC v13 (Gotham) FAQ]]
* [[XBMC v12 (Frodo) FAQ]]
* [[XBMC v11 (Eden) FAQ]]

= Codename History =
* [[Codename history]]

= Release Dates =
* [[Releases]]

<gallery mode="packed" widths="500px" heights="283px">
File:Wallpaper by nombo 2.jpg
File:Kodi-Wallpaper-6A-Isengard-1080p samfisher.jpg
</gallery>

{{updated|18}}

[[Category:FAQ]]
[[Category:Index]]
[[Category:General topics]]

Kodi

2018-10-26T13:32:21Z

Gamester17:

{{Infobox software
| logo = [[File:Thumbnail-light-transparent.png|200px]]
| screenshot = [[File:XBMC home.jpg|300px]]
| caption = Kodi's home screen
| developer = [[XBMC Foundation]]
| Stable release = {{current version}}
| Preview release =
| programming language = C++ core, with Python scripts as add-ons from third-parties parties
| operating system = Android, Linux, BSD, Mac OS X/macOS, Windows, iOS/tvOS
| platform = [[w:ARM architecture|ARM]], [[w:x86 architecture|x86]]
| status = Active
| released = 2003
| language = 70+ languages to date
| license = GPLv2 or later
}}{{mininav|[[General topics]]{{l2|[[XBMC Foundation]]}}}}
{{see also|Kodi FAQ}}
<section begin=intro /><section begin=intro2 />'''[[Kodi]]'''® media center, formerly known as XBMC Media Center, is an award-winning free and open source cross-platform software media player and entertainment hub for digital media for HTPCs (Home theater PCs). It uses a [[10-foot user interface]] designed to be a media player for the living-room, using a remote control as the primary input device. Its graphical user interface (GUI) allows the user to easily browse and view videos, photos, podcasts, and music from a harddrive, optical disc, local network, and the internet using only a few buttons. The Kodi project is managed by the non-profit '''[[XBMC Foundation]]''', and developed by volunteers located around the world. Since its creation in 2003 more than 500 software developers have contributed to Kodi, and around 60 developers on regular basis. Also 200-plus translators have worked to expand its reach, making it available in more than 72 languages. <section end=intro />

Kodi® ''(then called "Xbox Media Center")'' was originally created as a media center application for the first-generation Xbox game console ([[XBMC4Xbox|no longer supported]]) but is now officially available as a native application for [[Android]], [[BSD]], [[Linux]], [[Mac OS X|Mac OS X/macOS]], [[iOS|iOS/tvOS]], and [[Windows]] operating systems, running on most common processor architectures. <section end=intro2 />

== Video demos ==
Check out this excellent introduction video by [http://lifehacker.com/5900626/create-a-kickass-seamless-play+everything-media-center-the-complete-guide Lifehacker.com]:<br />
{{YouTube|T970YM3w1LY}}

;Additional video demos
* [http://www.youtube.com/watch?v=2O4fCGrwrqw Kodi beginners guide - an introduction and tour] by Kodi.tv forum user fredphoesh

== Overview of features ==
{{main|Features and supported codecs}}
{{#lst:Features and supported codecs|intro}}

{{#lst:Add-ons|intro}}

For additional information about specific add-ons, see '''[[:Category:All add-ons]]'''.

=== Language support ===
{{see also|Translation System}}
Kodi includes full support for many different languages by default. Kodi's structure is such that if the language is not available, or not up-to-date, it can be made by signing up at [https://www.transifex.net/projects/p/XBMC-Main-Frodo/ Kodi Main Translation Project (Frodo)], Currently the existing supported languages are Afrikaans, Basque, Brazilian Portuguese, Bulgarian, Catalan, Simplified Chinese, Traditional Chinese, Croatian, Czech, Danish, Dutch, English, American English, Esperanto, Finnish, French, German, Greek, Hebrew, Hungarian, Icelandic, Indonesian, Italian, Japanese, Korean, Maltese, Norwegian, Polish, Portuguese, Romanian, Russian, Serbian, Slovak, Slovenian, Spanish, Mexican Spanish, Swedish, Thai, Turkish and Ukrainian.

== Hardware requirements ==
{{Main|Supported hardware}}
{{#lst:Supported hardware|intro}}

== Official versions of Kodi ==
{{See also|Releases}}
Full featured versions of Kodi are available on a number of operating system platforms. Team Kodi strives to keep a consistent feature set and include the full Kodi experience for all versions, even those on low-powered devices.

;[[Kodibuntu]]
:KodiBuntu (formerly XBMCbuntu) is a free Ubuntu-based Linux distribution with Kodi for Linux already installed and pre-configured, providing a complete packaged media center software suite for all IA-32/x86-based personal computers. KodiBuntu is based on [[w:Lubuntu|Lubuntu]] instead of Ubuntu Desktop.

;[[Android]]
:''Kodi for Android'' is a full port of the complete Kodi application to Google's Android operating-system, was first announced and its source code released publicly on 13 June 2012. This is a full port of Kodi's C++ and C source code with all its dependencies to Android with a build-system that was designed to handle multiple processor architectures, like ARM, MIPS, and x86 with the Android NDK (Native Development Kit for Android) without using a single line of Java, and the Kodi.APK is running natively under Android as a Native Activity application.

;[[iOS]]
:''Kodi for iOS'', which is a full port of Kodi to Apple's [[iOS]] operating-system, was first announced and released publicly on 20 January 2011. It supports both 720p and 1080p hardware accelerated video decoding of H.264 videos, and is compatible several Apple's [[iDevice]]s that uses Apple A4 or higher SoC processors with a jailbroken iOS operating-system.

;[[Linux]]
:''Kodi for Linux'' is primarily developed for Ubuntu Linux. Third-party packages for most other Linux distributions are however available, and it is also possible to compile Kodi from scratch for any Linux distribution as long as the pre-required dependency libraries are installed first.

;[[Mac]]
:''Kodi for Mac'' runs natively on [[Mac OS X]] with Intel processors with hardware video decoding for H.264.

;[[Windows]]
:''Kodi for Windows'' runs natively on Windows Vista and higher. It is a 32-bit application but runs on 64-bit Windows and hardware as well, however it is not yet optimized for that architecture so there is no performance gain when running on 64-bit Windows. 1080p playback can be achieved on Windows based computers either via software decoding on the CPU if it's powerful enough, or by hardware accelerated video decoding.

== Third-party forks and derivative work of Kodi ==
{{main|Third-party forks and derivatives}}
{{#lst:Third-party forks and derivatives|intro}}

== History ==
{{See|History of Kodi}}

== XBMC Foundation ==
{{see also|XBMC Foundation}}
{{#lst:XBMC Foundation|intro}}

== Awards ==
[[File:Cca.gif|right]]
In the [[w:SourceForge|SourceForge]] 2006 Community Choice Awards, XBMC won an award for Best Project for Gamers as well as an award Best Project for Multimedia.[http://sourceforge.net/blog/cca06/]

In the [[w:SourceForge|SourceForge]] 2007 Community Choice Awards, XBMC was nominated finalist in six categories.[http://sourceforge.net/blog/cca07/]

In the [[w:SourceForge|SourceForge]] 2008 Community Choice Awards, XBMC won an award for Best Project for Gamers.[http://sourceforge.net/blog/cca08/]

In the [[w:Lifehacker|Lifehacker Australia]] 2014 Community Choice Awards, XBMC won an award for Best Media Player. [http://www.lifehacker.com.au/2014/12/lifehacker-awards-2014-best-media-player/]

== Programming and developing ==
{{main|Development}}
Kodi is a non-profit and free software community driven open-source software project that is developed only by volunteers in their spare time without any monetary gain. The team of developers leading the development of Kodi, "''[[Team Kodi]]''", encourage anyone and everyone to submit their own source code patches for new features and functions, improve existing ones, or fix bugs to the Kodi project.

Kodi's source code for all its supported platforms is made publicly available by Team Kodi under the open source GNU General Public License Version 2 license. The group currently maintains a Git [https://github.com/xbmc/xbmc repository] for this source code.

== Further reading ==
* [[Wikipedia:Kodi (software)]]
* http://kodi.tv

{{Isengard updated}}

[[Category:Manual]]
[[Category:Kodi|*]]
[[Category:Team Kodi]]
[[Category:General topics]]

Kodi v18 (Leia) FAQ

2018-10-26T13:07:09Z

Gamester17: Undo revision 146290 by Gamester17 (talk)

{{notice|This FAQ applies to the current '''[[development builds]]''' which will be pre-alpha of Kodi v18 (Leia) built from the master repository.}}
{{future|18}}

{{Kodi FAQ}}

<section begin="intro" />Frequently Asked Questions for upgrading to Kodi v18 (codename Leia) from a previous version. Includes how to enable some of the new features and functions, where some controls got moved to, etc.<section end="intro" />

{{mininav| [[FAQs]] {{l2| [[Releases]] }} }}
{{see also|Kodi v18 (Leia) changelog|Leia API changes|Releases}}

__TOC__
{{-}}
== General FAQ ==
:{{big|''See also: '''[[All platforms FAQ]]''' for an FAQ that applies to all versions of Kodi.''}}

=== What is Kodi? What is Leia? ===
:{{Main|Kodi name change FAQ|History of Kodi}}
:Kodi is the new name for XBMC media center. "Leia" something will be the [[codename]] for version 18 of Kodi, just as "Krypton" was the codename for Kodi v17 and "Jarvis" was the codename for Kodi v16". You will often see "v18" and "Leia" used interchangeably in the community.

=== Changelog ===
:{{Main|Kodi v18 (Leia) changelog}}
:See: '''[[Kodi v18 (Leia) changelog]]'''. Add-on developers should also see '''[[Leia API changes]]''', and skinners should also read the respective sticky posts in the Skin Development Forum for full changelog on changes to the skinning engine.

=== What are some of the noticeable new features? ===
:{{Main|New features|Kodi v18 (Leia) changelog}}
: In addition to many "under the hood" improvements, some of the more ''visible'' additions to Kodi v18 (Leia) include:

:* Added a "[[Games]]" window and RetroPlayer player core supporting [[Game_Add-ons|game clients addons]] as well as emulator cores via [[libretro]] API
:* Major GUI (Graphical User Interface) refactoring of [[PVR]] and [[Live TV]] in Kodi
:** Other than previous PVR addons having been updated there are also new PVR addons for [[Add-on:Teleboy PVR Client|Teleboy PVR Client]], [[Add-on:Zattoo PVR Client|Zattoo PVR Client]], and [[Add-on:Sledovanitv.cz PVR Client|Sledovanitv.cz PVR Client]]
:* Major refactoring of Kodi's core handling and GUI management of binary addons (Add-ons Framework, API, and Manager)
:** Implemented a Python 3 interpreter (plus enforcing Python 2 & 3 compatibility in Leia addon repository)<ref>https://kodi.tv/article/attention-addon-developers-migration-python-3</ref>
:** Implemented online binary addon repository from which Kodi can now automatically installs/updates binary addon<ref>https://kodi.tv/article/kodi-v18-binary-add-ons-repository</ref><ref>https://github.com/xbmc/repo-binary-addons</ref>
:** Improved and updated "InputStream" (input stream) client addons for common network streaming protocols and popular services
:** Added support for Python (script) based web scrapers for Kodi<ref>http://github.com/xbmc/xbmc/pull/9984</ref>
:* Added support to render directly on DRM/KMS without the need for any display manager (implementation uses GBM to create the required surfaces)<ref>https://github.com/xbmc/xbmc/pull/11955</ref>
:* Added support for Mir windowing system (Mir 1.0) for Kodi[148] and added support for VAAPI on Mir using DRM
:* Improved support to compiling Kodi for Microsoft's UWP (Universal Windows Platform) APIs
:* Added support for speech-to-text in Kodi OSD keyboard on Android TV (triggered by voice button on remote)
:* Added support for BD-J / Blu-ray Disc Java menu support (requires system Java runtime environment)
:* ?

=== Major addition summary 1 ===

=== Major addition summary 2 ===

== New system requirements ==
:{{main|Supported hardware}}

=== Android ===
: Kodi v17 and later requires that Android devices run at least Android 5.0 or later.

: If you want to auto-update Kodi using Google Play then keep in mind that Google Play won't update Kodi unless Android 5 or higher is installed.

=== Specific system requirement example goes here ===

== Upgrading ==
{{warning|image_size=30px| If you are upgrading from XBMC v13 to Kodi v18 then please read '''[[Migration from XBMC to Kodi]]''' first.}}

{{warning|image_size=30px| Always '''[[backup]]''' your settings before upgrading, just incase! }}

=== How do I upgrade from v17 to v18? ===
:{{main|Installing}}

* '''ANDROID USERS:''' '''{{color|red|Don't}}''' uninstall an earlier version of Kodi/XBMC before installing the new version. Uninstalling first would remove all of your settings. Just install the new version and it will replace the older version and retain your settings.

* In most cases you can just '''[[Installing|install Kodi v18]]''' over Kodi v17. All your settings and library are saved and will continue to work in the new version. See '''[[Installing]]''' for specific install instructions.

* Most basic (video, audio, etc) [[add-ons]] that worked in Kodi v17 should still work in v18.

* If you have any issues (settings not being copied over, blank screens, etc) when updating from versions ''older'' than v14: remove the new version, install the older version of Kodi/XBMC from http://mirrors.kodi.tv/releases/ , and then upgrade to the next version. In other words, if you have v14, first install v15 and run Kodi, Quit Kodi and then install v16 and run Kodi. Quit Kodi again and install v17, then run Kodi. Quit Kodi again and install v18, then run Kodi.

=== MySQL ===
:{{main|MySQL/Upgrading}}
:As long as your MySQL server is set up to allow XBMC/Kodi to make new databases for the upgrade itself (see '''[[MySQL/Upgrading]]''') then you don't need to do anything for upgrading a MySQL set up for Kodi. Even if you use "XBMC" in your advancedsettings.xml file, you can leave this the same and everything will still work.

== Where did it this or that go? ==

=== advancedsettings.xml changes ===
:{{main|advancedsettings.xml}}
:* ?

=== Settings ===
:{{main|Settings}}
:* ?

=== CodecInfo playback information ===
:* ?

=== Add-on manager ===
:{{main|Add-on manager}}

:* ?

=== Live TV and PVR ===
:* ?

=== Setting that moved ===

=== Feature that moved ===

== Troubleshooting ==
{{main|Troubleshooting}}

=== What are some of the known issues in v18? ===
{{see also|Common issues}}

=== Where can I get more help? ===
:The '''[[FAQ|general and platform specific FAQs]]''', the Kodi support forums: '''http://forum.kodi.tv''', and/or the '''[irc://irc.freenode.org/kodi #kodi]''' [[w:IRC|IRC]] chat channel on irc.freenode.org.

=== EXAMPLE PLATFORM: Example issue 1 ===

== Notes ==
<references />

== See also ==
{{Upgrade FAQs}}

[[Category:FAQ]]
[[Category:Manual]]
[[Category:Leia|*]]
[[Category:Upgrade FAQ|18]]

Kodi v18 (Leia) FAQ

2018-10-26T13:05:17Z

Gamester17: /* What are some of the noticeable new features? */

{{notice|This FAQ applies to the current '''[[development builds]]''' which will be pre-alpha of Kodi v18 (Leia) built from the master repository.}}
{{future|18}}

{{Kodi FAQ}}

<section begin="intro" />Frequently Asked Questions for upgrading to Kodi v18 (codename Leia) from a previous version. Includes how to enable some of the new features and functions, where some controls got moved to, etc.<section end="intro" />

{{mininav| [[FAQs]] {{l2| [[Releases]] }} }}
{{see also|Kodi v18 (Leia) changelog|Leia API changes|Releases}}

__TOC__
{{-}}
== General FAQ ==
:{{big|''See also: '''[[All platforms FAQ]]''' for an FAQ that applies to all versions of Kodi.''}}

=== What is Kodi? What is Leia? ===
:{{Main|Kodi name change FAQ|History of Kodi}}
:Kodi is the new name for XBMC media center. "Leia" something will be the [[codename]] for version 18 of Kodi, just as "Krypton" was the codename for Kodi v17 and "Jarvis" was the codename for Kodi v16". You will often see "v18" and "Leia" used interchangeably in the community.

=== Changelog ===
:{{Main|Kodi v18 (Leia) changelog}}
:See: '''[[Kodi v18 (Leia) changelog]]'''. Add-on developers should also see '''[[Leia API changes]]''', and skinners should also read the respective sticky posts in the Skin Development Forum for full changelog on changes to the skinning engine.

=== What are some of the noticeable new features? ===
:{{Main|New features|Kodi v18 (Leia) changelog}}
: In addition to many "under the hood" improvements, some of the more ''visible'' additions to Kodi v18 (Leia) include:

:* Added a "[[Games]]" window and RetroPlayer player core supporting [[Game_Add-ons|game clients addons]] as well as emulator cores via [[libretro]] API
:* Major GUI (Graphical User Interface) refactoring of [[PVR]] and [[Live TV]] in Kodi
:** Other than previous PVR addons having been updated there are also new PVR addons for [[Add-on:Teleboy PVR Client|Teleboy PVR Client]], [[Add-on:Zattoo PVR Client|Zattoo PVR Client]], and [[Add-on:Sledovanitv.cz PVR Client|Sledovanitv.cz PVR Client]]
:* Major refactoring of Kodi's core handling and GUI management of binary addons (Add-ons Framework, API, and Manager)
:** Implemented a Python 3 interpreter (plus enforcing Python 2 & 3 compatibility in Leia addon repository)<ref>https://kodi.tv/article/attention-addon-developers-migration-python-3</ref>
:** Implemented online binary addon repository from which Kodi can now automatically installs/updates binary addon<ref>https://kodi.tv/article/kodi-v18-binary-add-ons-repository</ref><ref>https://github.com/xbmc/repo-binary-addons</ref>
:* Added support for a generic DRM/KMS implementation using GBM to create surfaces and V4L2 for video acceleration<ref>https://kodi.wiki/view/Kodi_v18_(Leia)_changelog#cite_note-153</ref>
:** Improved and updated "InputStream" (input stream) client addons for common network streaming protocols and popular services
:** Added support for Python (script) based web scrapers for Kodi<ref>http://github.com/xbmc/xbmc/pull/9984</ref>
:* Added support to render directly on DRM/KMS without the need for any display manager (implementation uses GBM to create the required surfaces)<ref>https://github.com/xbmc/xbmc/pull/11955</ref>
:* Added support for Mir windowing system (Mir 1.0) for Kodi[148] and added support for VAAPI on Mir using DRM
:* Improved support to compiling Kodi for Microsoft's UWP (Universal Windows Platform) APIs
:* Added support for speech-to-text in Kodi OSD keyboard on Android TV (triggered by voice button on remote)
:* Added support for BD-J / Blu-ray Disc Java menu support (requires system Java runtime environment)
:* ?

=== Major addition summary 1 ===

=== Major addition summary 2 ===

== New system requirements ==
:{{main|Supported hardware}}

=== Android ===
: Kodi v17 and later requires that Android devices run at least Android 5.0 or later.

: If you want to auto-update Kodi using Google Play then keep in mind that Google Play won't update Kodi unless Android 5 or higher is installed.

=== Specific system requirement example goes here ===

== Upgrading ==
{{warning|image_size=30px| If you are upgrading from XBMC v13 to Kodi v18 then please read '''[[Migration from XBMC to Kodi]]''' first.}}

{{warning|image_size=30px| Always '''[[backup]]''' your settings before upgrading, just incase! }}

=== How do I upgrade from v17 to v18? ===
:{{main|Installing}}

* '''ANDROID USERS:''' '''{{color|red|Don't}}''' uninstall an earlier version of Kodi/XBMC before installing the new version. Uninstalling first would remove all of your settings. Just install the new version and it will replace the older version and retain your settings.

* In most cases you can just '''[[Installing|install Kodi v18]]''' over Kodi v17. All your settings and library are saved and will continue to work in the new version. See '''[[Installing]]''' for specific install instructions.

* Most basic (video, audio, etc) [[add-ons]] that worked in Kodi v17 should still work in v18.

* If you have any issues (settings not being copied over, blank screens, etc) when updating from versions ''older'' than v14: remove the new version, install the older version of Kodi/XBMC from http://mirrors.kodi.tv/releases/ , and then upgrade to the next version. In other words, if you have v14, first install v15 and run Kodi, Quit Kodi and then install v16 and run Kodi. Quit Kodi again and install v17, then run Kodi. Quit Kodi again and install v18, then run Kodi.

=== MySQL ===
:{{main|MySQL/Upgrading}}
:As long as your MySQL server is set up to allow XBMC/Kodi to make new databases for the upgrade itself (see '''[[MySQL/Upgrading]]''') then you don't need to do anything for upgrading a MySQL set up for Kodi. Even if you use "XBMC" in your advancedsettings.xml file, you can leave this the same and everything will still work.

== Where did it this or that go? ==

=== advancedsettings.xml changes ===
:{{main|advancedsettings.xml}}
:* ?

=== Settings ===
:{{main|Settings}}
:* ?

=== CodecInfo playback information ===
:* ?

=== Add-on manager ===
:{{main|Add-on manager}}

:* ?

=== Live TV and PVR ===
:* ?

=== Setting that moved ===

=== Feature that moved ===

== Troubleshooting ==
{{main|Troubleshooting}}

=== What are some of the known issues in v18? ===
{{see also|Common issues}}

=== Where can I get more help? ===
:The '''[[FAQ|general and platform specific FAQs]]''', the Kodi support forums: '''http://forum.kodi.tv''', and/or the '''[irc://irc.freenode.org/kodi #kodi]''' [[w:IRC|IRC]] chat channel on irc.freenode.org.

=== EXAMPLE PLATFORM: Example issue 1 ===

== Notes ==
<references />

== See also ==
{{Upgrade FAQs}}

[[Category:FAQ]]
[[Category:Manual]]
[[Category:Leia|*]]
[[Category:Upgrade FAQ|18]]

Kodi v18 (Leia) changelog

2018-10-26T13:04:08Z

Gamester17: /* Linux Specific */

{{mininav|[[Releases]] {{l2| [[Leia]] }} }}

{{notice|Kodi's journey via non-alpha/beta v18 (Leia) releases is currently underway. As such, these new features/functions and API changes is a placeholder containing changes to the current Kodi mainline (the git master tree repository on GitHub). This is listing changes committed to the master branch after Krypton branching. The many features/functions and API additions, alterations or removal are only subject to change during the Alpha stages. The Beta stage is all about stability and bug fixing. }}
{{incomplete}}
{{future|18}}

{{see also|Kodi v18 (Leia) FAQ|Leia API changes|Releases}}

This is the Kodi Wiki version of a condensed changelog for the future Kodi v18.x version (codename: "Leia") releases with a summary of the most important core features and functions as well as other notable changes to key areas of the application software or its user interface. Please note that this condensed changelog version is not meant bug-fixes, nor minor refactoring or cosmetic changes.

== Changelog ==

=== Gaming (Games interface and Game Clients)===
Note! Also see "Input System (Input Manager and Input APIs" section for Input System related to game controllers
* Added a "[[Games]]" window to GUI (games are managed using a basic file browser as a game library does not exist yet)
* Added a RetroPlayer player core supporting [[Game_Add-ons|game clients addons]] as well as emulator cores via [[libretro]] API<ref name="RetroPlayer">RetroPlayer http://forum.kodi.tv/showthread.php?tid=164725</ref><ref>http://github.com/xbmc/xbmc/pull/11022</ref>
* Added extentions to Kodi's Addons AP to support Game Client Addons, supporting Kodi's VFS (Virtual File System), etc.<ref name="RetroPlayer"/>
* Added support for Game Client Addons as new type of addons with just-in-time emulator installation<ref name="RetroPlayer"/>
* Added a Games window and Game OSD (On-Screen-Display) entries to the GUI<ref name="RetroPlayer"/><ref>https://github.com/xbmc/xbmc/pull/12367</ref>
* Added a gaming and game configuration interface for Game settings to the GUI<ref name="RetroPlayer"/>
* Added support for Game Info Tags (game info tag) and exposed properties to Python list items<ref name="RetroPlayer"/>
* Added a savestate (savestate) manager to Kodi for games<ref>http://github.com/xbmc/xbmc/pull/11034</ref>
* Added initial support for basic gameplay persistence (auto-save & auto-load)<ref>https://github.com/xbmc/xbmc/pull/12434</ref>
* Added support for in-game (save RAM) saves<ref>http://github.com/xbmc/xbmc/pull/11380</ref>
* Added support for Keyboard players via Joystick Emulation<ref name="RetroPlayer"/>
* Added Game API acbstraction for game controller multitaps (a.k.a. hubs) including topology GUI display<ref>https://github.com/xbmc/xbmc/pull/13499</ref>
* Added Game API acbstraction to support gamepad/joystick remapping for games (per game-addon)
* Added Game API acbstraction to support keyboard remapping for games (per game-addon)<ref>https://github.com/xbmc/xbmc/pull/13374</ref>
* Added Game API acbstraction to support mouse remapping for games (per game-addon)<ref>https://github.com/xbmc/xbmc/pull/13482</ref>
* Added support for libretro API and game cores (emulators and games) that support it as binary addons
* Added [[Game_Add-ons|game clients addons]] for many popular third-party game console emulators and native open source games *
** ''* [[Game_Add-ons|Game clients addons]] for Kodi is changing quickly so checkout the [[Game_Add-ons|game clients addons]] article for a current list''
* ?

=== Live TV and PVR (Personal Video Recorder) ===
* Added new settings for 'Startup action' and add 'Play TV/Radio <ref>https://github.com/xbmc/xbmc/pull/12548</ref>
* Added support for global direct channel number input & global unique channel numbers<ref>https://github.com/xbmc/xbmc/pull/13135</ref><ref>https://github.com/xbmc/xbmc/pull/11434</ref>
** Added support for no delay on switch to previous channel with key 0 when using direct channel number input<ref>https://github.com/xbmc/xbmc/pull/13232</ref>
* Added context menu support for Estuary (skin) PVR home screen widgets <ref>https://github.com/xbmc/xbmc/pull/10870</ref>
* Added percent played progress bar to PVR info panel (for recordings) in Estuary (skin)<ref>https://github.com/xbmc/xbmc/pull/13338</ref>
* Added Info support to recently played channel widget to Estuary (skin) home screen <ref>https://github.com/xbmc/xbmc/pull/12254</ref>
* Added episode name to Live TV, recordings OSD sub label, and cleanup seekbar for Live TV in Estuary (skin) <ref>https://github.com/xbmc/xbmc/pull/12306</ref>
* Added Season/Episode info in Guide window and dialog in Estuary (skin)<ref>https://github.com/xbmc/xbmc/pull/13300</ref>
* Added support for next and previous buttons in OSD Timeshift window<ref>https://github.com/xbmc/xbmc/pull/14387</ref>
* Added feature to prefill recordings folder with timer title in the timer settings dialog<ref>https://github.com/xbmc/xbmc/pull/11679</ref>
* Added support for radio channel groups to the channelgroup manager<ref>https://github.com/xbmc/xbmc/pull/11877</ref>
* Added support for a 'Smart selection' of EPG events feature to the guide window<ref>https://github.com/xbmc/xbmc/pull/11782</ref>
* Added 'Go to date' context menu item to the guide window<ref>https://github.com/xbmc/xbmc/pull/13282</ref>
* Added support for channel groups selector to the guide window<ref>https://github.com/xbmc/xbmc/pull/13364</ref>
* Added possibility to switch between horizontal and vertical epg grid view to the guide window <ref>https://github.com/xbmc/xbmc/pull/11958</ref>
* Added support to sort content by channel number/channel name/last played, support sort order to the Guide window<ref>https://github.com/xbmc/xbmc/pull/14231</ref>
* Added support next/previous chapter in PVR recordings<ref>https://github.com/xbmc/xbmc/pull/13164</ref>
* Improved PVR seekbar and info dialog in Estuary (skin) <ref>https://github.com/xbmc/xbmc/pull/13158</ref>
* Improved PVR info panel, info dialog, and recordings window in Estuary (skin)<ref>https://github.com/xbmc/xbmc/pull/12416</ref><ref>https://github.com/xbmc/xbmc/pull/13255</ref>
* Improved support for enabling multiple PVR client addons<ref>https://github.com/xbmc/xbmc/pull/12959</ref>
* Improved support for for subchannel numbers support (ATSC)<ref>https://github.com/xbmc/xbmc/pull/13069</ref>
* Improved OSD Timeshift GUI<ref>https://github.com/xbmc/xbmc/pull/14316</ref><ref>https://github.com/xbmc/xbmc/pull/14386</ref>
* Improved the guide window for better consistency and readability <ref>https://github.com/xbmc/xbmc/pull/13402</ref>
* Changed GUI actions to eliminate duplicate and dead code (major GUI refactoring for PVR and LiveTV)
* Changed implementation of EPG search filter (EPG search dialog) completely<ref>https://github.com/xbmc/xbmc/pull/11570</ref><ref>https://github.com/xbmc/xbmc/pull/12001</ref>
* Changed Guide Window removing obsolete views "channel", "now" and "next"<ref>https://github.com/xbmc/xbmc/pull/10838</ref>
* Changed "play minimized" settings handling <ref>https://github.com/xbmc/xbmc/pull/11203</ref>
* Changed 'epg.lingertime' to an official setting, remove the respective advanced setting<ref>https://github.com/xbmc/xbmc/pull/12740</ref>
* Changed shared channel selection into an optional setting<ref>https://github.com/xbmc/xbmc/pull/13237</ref>
* Removed obsolete and unused setting 'pvrplayback.scantime' <ref>https://github.com/xbmc/xbmc/pull/12800</ref>
* Removed channel guide button from EPG event info dialog, add 'channel guide' to context menu<ref>https://github.com/xbmc/xbmc/pull/12526</ref>
* Removed setting 'hide connection lost warning' <ref>https://github.com/xbmc/xbmc/pull/11500</ref>
* Removed non-working recording settings defaults <ref>https://github.com/xbmc/xbmc/pull/11746</ref>
* Recordings window: Content view filter <ref>https://github.com/xbmc/xbmc/pull/11704</ref>
* PVR-Addon API changes <ref>https://github.com/xbmc/xbmc/pull/12028</ref><ref>https://github.com/xbmc/xbmc/pull/12303</ref><ref>https://github.com/xbmc/xbmc/pull/12552</ref><ref>https://github.com/xbmc/xbmc/pull/12609</ref><ref>https://github.com/xbmc/xbmc/pull/12660</ref><ref>https://github.com/xbmc/xbmc/pull/12689</ref><ref>https://github.com/xbmc/xbmc/pull/12755</ref><ref>https://github.com/xbmc/xbmc/pull/13228</ref><ref>https://github.com/xbmc/xbmc/pull/13720</ref><ref>https://github.com/xbmc/xbmc/pull/14002</ref><ref>https://github.com/xbmc/xbmc/pull/14086</ref>
* Added, updated, and improved PVR backend clients addons for popular third-party external [[PVR backend]] platforms:
** New: [[Add-on:Zattoo PVR Client|Zattoo PVR Client]] PVR Addon backend client maintained and available from Kodi's community
** New: [[Add-on:Teleboy PVR Client|Teleboy PVR Client]] PVR Addon backend client maintained and available from Kodi's community
** New: [[Add-on:Sledovanitv.cz PVR Client|Sledovanitv.cz PVR Client]] PVR Addon backend client maintained and available from Kodi's community
** [[Add-on:PVR Demo Client|PVR Demo Client]] dummy addon with fake (method stub) [[PVR backend]] for [[PVR]] skinning and regression testing
** [[Add-on:IPTV Simple Client|IPTV Simple Client]] PVR Addon backend client maintained and available from Kodi's community
** [[Add-on:FilmOn PVR Client|FilmOn]] PVR Addon backend client maintained and available from Kodi's community
** [[Add-on:Stalker Client|Stalker Middleware]] PVR Addon backend client maintained and available from Kodi's community
** [[Add-on:HDHomeRun PVR|HDHomeRun]] PVR Addon backend client maintained and available from Kodi's community
** [[Add-on:Digital Devices Octopus NET Client|Digital Devices Octopus NET Client]] PVR Addon backend client maintained and made available by [http://digitaldevices.de/home/ Digital Devices]
** [[Add-on:VU+ / Enigma2 Client|Enigma2 (Dreambox / Vu+ / DBox2)]] PVR Addon backend client maintained and available from Kodi's community
** [[Add-on:VBox TV Gateway PVR Client|VBox TV Gateway]] PVR Addon backend client maintained and available from Kodi's community
** [[Add-on:Njoy N7 PVR Client|Njoy Digital (N7)]] PVR Addon backend client maintained and available from Kodi's community
** [[Add-on:PCTV Systems Client|PCTV Systems (Broadway)]] PVR Addon backend client maintained and available from Kodi's community
** [[Add-on:Tvheadend HTSP Client|Tvheadend HTSP Client]] PVR Addon backend client maintained and available from Kodi's community
** [[Add-on:VDR VNSI Client|VDR VNSI Client]] PVR Addon backend client maintained and available from Kodi's community
** [[Add-on:MythTV PVR Client|MythTV PVR Client]] Addon backend client maintained and available from the Kodi's community
** [[Add-on:NextPVR PVR Client|NextPVR (former GB-PVR)]] PVR Addon backend client maintained and available from Kodi's community
** [[Add-on:Argus TV Client|Argus TV (former ForTheRecord)]] PVR Addon backend client maintained and available from Kodi's community
** [[Add-on:DVBLink PVR Client|DVBLink PVR Client]] Addon backend client maintained and available from Kodi's community
** [[Add-on:DVBViewer Client|DVBViewer Client]] PVR Addon backend client maintained and available from Kodi's community
** [[Add-on:MediaPortal PVR Client|MediaPortal PVR Client]] Addon backend client maintained and available from Kodi's community
** [[Add-on:PVR.WMC|WMC (Windows Media Center)]] PVR Addon backend client maintained and available from Kodi's community
* ?

=== Add-ons Framework, API, and Manager ===
For full changelogs of all Addons APIs, see [[Leia API changes]], [https://forum.kodi.tv/showthread.php?tid=324598 JSON-RPC], and [http://forum.kodi.tv/forumdisplay.php?fid=26 Add-ons] Development Forums
* Implemented a Python 3 interpreter inside Kodi (plus enforcing Python 2 & 3 compatibility in Leia addon repository)<ref>https://kodi.tv/article/attention-addon-developers-migration-python-3</ref>
* Implemented online binary addon repository from which Kodi can now automatically installs/updates binary addon<ref>https://kodi.tv/article/kodi-v18-binary-add-ons-repository</ref><ref>https://github.com/xbmc/repo-binary-addons</ref>
* Major refactoring of Kodi's core handling and GUI management of binary addons<ref>http://github.com/xbmc/xbmc/pulls?q=label%3A%22Binary+Addons%22+is%3Aclosed</ref>
* Added framework to support VFS (Virtual File System) as binary addons<ref>http://github.com/xbmc/xbmc/pull/8966</ref>
* Added framework support for binary addons for video decoder codecs<ref name="Addon video codec implementation">https://github.com/xbmc/xbmc/pull/12340</ref>
* Added framework support for binary addons for image (picture) decoder codecs
* Added extentions to Kodi's Addons API to support binary addons for video decoder codecs<ref name="Addon video codec implementation"/>
* Added extentions to Kodi's Addons API to support binary addons for image decoder codecs
* Added support for Python addons to use PyCryptoDome crypto module for decryption<ref>https://github.com/xbmc/xbmc/pull/11477</ref>
* Added option to pass HTTP cookies with AVOption to Kodi's Video Player<ref>https://github.com/xbmc/xbmc/pull/12257</ref>
* Added support to allow addons to edit all used controls on their processed window<ref>https://github.com/xbmc/xbmc/pull/12259</ref>
* Added support to allow Python addons to set the videoinfotag path<ref>http://github.com/xbmc/xbmc/pull/11012</ref>
* Added support to allow Python addons to get/set the dbid of a (music) listitem<ref>http://github.com/xbmc/xbmc/pull/10858</ref>
* Added support for mediatype to musicinfotag tag retrieving via Python API<ref>http://github.com/xbmc/xbmc/pull/11110</ref>
* Added support "int/float slider" to Kodi's Python API<ref>http://github.com/xbmc/xbmc/pull/11230</ref>
* Added support "setContent for mediawindows" to Kodi's Python API<ref>http://github.com/xbmc/xbmc/pull/11258</ref>
* Added help for load of shared library and allow the use of their own addon temp folder<ref>https://github.com/xbmc/xbmc/pull/12379</ref>
* Added support to inspect add-on dependencies prior to installation<ref>https://github.com/xbmc/xbmc/pull/12242</ref>
* Added ability to remove add-on settings upon uninstall<ref>https://github.com/xbmc/xbmc/pull/11499</ref>
* Changed to new addon gui interface for list items to use on addon window<ref>https://github.com/xbmc/xbmc/pull/12214</ref>
* Changed service addons to use event handlers instead of synchronous addon hooks<ref>https://github.com/xbmc/xbmc/pull/12370</ref>

=== Input System (Input Manager and Input APIs) ===
* Improved the input manager and input API system for keyboards, mouses, and game controllers<ref name="Controller input system">PR #8807 Controller input system http://github.com/xbmc/xbmc/pull/8807</ref>
* Updated "Peripheral Addons" for game controllers, gamepads, joysticks, and input peripherals profiles (in Kodi-game repo<ref>http://github.com/kodi-game/ kodi-game repo on GitHub</ref>):
** [http://github.com/xbmc/peripheral.joystick Joystick Controller Addon]
** [http://github.com/kodi-game/peripheral.xarcade X-Arcade (XGaming Tankstick) support for Kodi Addon]
** [http://github.com/kodi-game/peripheral.steamcontroller Steam Controller (gamepad) Addon]
** [http://github.com/kodi-game/kodi-game-controllers/tree/master/addons/game.controller.default Default Game Controller Addon (reference game controller addon based on Xbox 360 gamepad)]
*** [https://github.com/kodi-game/controller-topology-project/tree/master/addons PlayStation Game Controller Addon]
*** [https://github.com/kodi-game/controller-topology-project/tree/master/addons Nintendo NES Game Controller Addon]
*** [https://github.com/kodi-game/controller-topology-project/tree/master/addons Nintendo SNES Game Controller Addon]
*** [https://github.com/kodi-game/controller-topology-project/tree/master/addons Nintendo N64 Game Controller Addon]
*** [https://github.com/kodi-game/controller-topology-project/tree/master/addons Nintendo GBA Game Controller Addon]
*** [https://github.com/kodi-game/controller-topology-project/tree/master/addons Sega Genesis Game Controller Addon]
*** [https://github.com/kodi-game/controller-topology-project/tree/master/addons Sega Dreamcast Game Controller Addon]
* ?

=== GUI Engine (Skinning Engine) ===
For full changelog on changes to the skinning engine, see [[Leia API changes]] and the [http://forum.kodi.tv/showthread.php?tid=298565 Skin Development Forum]
* Added windows to support Games and Game OSD in the new default skins (Estuary and Estouchy)
* Added player process info dialog to Kodi's default skin (Estuary)<ref>https://github.com/xbmc/xbmc/pull/11718</ref>
* Added support for addons to use banner and ClearLogo<ref>https://github.com/xbmc/xbmc/pull/12244</ref>
* Added support for skins/gui to allow implicit container referencing for non-media windows<ref>http://github.com/xbmc/xbmc/pull/10883</ref>
* Added support for addons to add "Enable/Disable" to context menu<ref>http://github.com/xbmc/xbmc/pull/11124</ref>
* Added support for remember last used keyboard layout in GUI<ref>http://github.com/xbmc/xbmc/pull/11242</ref>
* Added support for ISO 639-2/T language code retrieval (required by libbluray)<ref>https://github.com/xbmc/xbmc/pull/12258</ref>
* Added window that display Kodi privacy policy in GUI settings under system info<ref>https://github.com/xbmc/xbmc/pull/10785</ref>
* Added support to map a key to browse for subtitle in video fullscreen window<ref>https://github.com/xbmc/xbmc/pull/11649</ref>
* Improved Kodi's GUI engine with optimizations for message handling and SmartRedraw<ref>https://github.com/xbmc/xbmc/pull/12213</ref>
* Improved Kodi's GUI engine support for scaling container layouts<ref>http://github.com/xbmc/xbmc/pull/11229</ref>
* Improved Kodi's GUI engine by allowing %-values for origin, camera and animation attribs<ref>http://github.com/xbmc/xbmc/pull/11233</ref>
* Changed so that context menu reloading loads async to aviod GUI lockup on wait<ref>https://github.com/xbmc/xbmc/pull/11841</ref>
* Updated guilib ABI (for libgui) to version 5.13.0<ref>http://github.com/xbmc/xbmc/pull/11306</ref>
* Updated keyboard layout for some languages and added support Croatian, Slovenian, and Thai (Kedmanee)
* Updated image resource addons (as example weather icons, weather fanart, studio logos, and genre icons)
* ?

=== Platform Independent Playback ===
* Added support for "InputStream" (input stream) addons to pass CryptoSession flags field<ref>https://github.com/xbmc/xbmc/pull/12428</ref>
* Added support for BD-J / Blu-ray Disc Java menu support (requires system Java runtime enviroment)<ref>https://github.com/xbmc/xbmc/pull/12339</ref><ref>https://github.com/xbmc/xbmc/pull/12310</ref>
* Added support for Blu-ray Disc detection and use provided meta data for Blu-ray Disc names<ref>https://github.com/xbmc/xbmc/pull/12488</ref>
* Added support for video buffers to be used by decoders and renderers<ref name="VideoPlayer updates for Leia">https://github.com/xbmc/xbmc/pull/12212</ref>
** Added support for platforms to register custom buffers, like example dma<ref name="VideoPlayer updates for Leia"/>
* Added a VC1-Packet bitstream parser implementation for improved VC-1 playback<ref>http://github.com/xbmc/xbmc/pull/11417</ref>
* Added and updated many (binary) audio decoder and encoder addons for Kodi
* Added a few (binary) video decoder addons for Kodi<ref name="Addon video codec implementation"/>
* Added a "RAW" (libraw based) image decoder addon to Kodi<ref>https://github.com/xbmc/xbmc/pull/11671</ref>
* Improved MMAL playback of H.264 MVC (Blu-ray 3D) stereoscopic video with framepacking decoding on Raspberry Pi
* Improved Stereoscopic 3D playback of 3D videos (as well as better 2D playback of 3D videos)
* Improved and enhanced Blu-ray support (including updated libbluray dependecies from the VideoLAN project<ref>https://github.com/xbmc/xbmc/pull/12305</ref><ref>http://git.videolan.org/?p=libbluray.git;a=blob;f=ChangeLog</ref>
* Improved support for "InputStream" (input stream) addons as system addons
* Updated "InputStream" (input stream) client addons for common network streaming protocols and popular services:
** [http://github.com/xbmc/xbmc/tree/master/addons/kodi.inputstream InputStream Addon (default reference InputStream Addon by Team Kodi]
** [http://github.com/mapfau/inputstream.test Test InputStream Addon (Test InputStream Addon for Kodi's new inputstream interface]
** [http://github.com/peak3d/inputstream.adaptive Adaptive InputStream Addon (InputStream Client addon for several manifest types)]
** [http://github.com/xbmc/repo-binary-addons/tree/master/inputstream.rtmp RTMP InputStream Addon (InputStream Client for RTMP streams using librtmp)]
** [http://github.com/peak3d/inputstream.mpd MPD (MPEG-DASH) InputStream Addon]
** [http://github.com/peak3d/inputstream.smoothstream SmoothStream InputStream Addon for MS-SSTR (SmoothStreamingMedia) Smooth Streaming Protocol]
** [http://github.com/mapfau/inputstream.nxmsl NXMSL InputStream Addon for Netflix style manifests over MSL]
* Updated FFmpeg multimedia codec and demux libraries to stable branch release version [http://www.ffmpeg.org/download.html#release_4.0.2 FFmpeg 4.0 (4.0.2)]<ref>http://git.videolan.org/?p=ffmpeg.git;a=blob_plain;f=Changelog;hb=release/4.0.2 FFmpeg 4.0.2 release changelog</ref><ref>https://github.com/xbmc/xbmc/pull/14212</ref>
* Removed certain audio codecs from core and made them into audio decoder and audio encoder binary add-ons
* Removed certain video codecs from core and made them into video decoder binary add-ons<ref name="Addon video codec implementation"/>
* Removed certain image codecs from core and made them into image decoder binary add-ons
* ?

=== General Library ===
* Added support to use the Favourites function in context menus<ref>https://github.com/xbmc/xbmc/pull/11967</ref>
* Added support for context menus to favourites home screen widget<ref>https://github.com/xbmc/xbmc/pull/11929</ref>
* Added support to "Sort By Date Added" in Music Video title node<ref>https://github.com/xbmc/xbmc/pull/12495</ref>

=== Music Library ===
* Added an option to rescan the music file tags for existing items in the library <ref>https://github.com/xbmc/xbmc/pull/11557</ref>
* Added processing of WRITER tag for ID3 v2, Vorbis and APE formats <ref>https://github.com/xbmc/xbmc/pull/11735</ref>
* Added processing of ARTISTSORT (TSOP), ALBUMARTISTSORT (TS02) and COMPOSERSORT (TSOC) tags to provide a sort name for artists. <ref>https://github.com/xbmc/xbmc/pull/11738</ref>
* Added a new dialog for selection of both artist and album scraper addons, and their settings.<ref>https://github.com/xbmc/xbmc/pull/12987</ref><ref>https://github.com/xbmc/xbmc/pull/12943</ref>
* Added additional artist data that Musicbrainz provides: type (person, group, orchestra, choir etc.), gender, and disambiguation comments that help to differentiate artists with the same name <ref>https://github.com/xbmc/xbmc/pull/12963</ref>
* Added an Artist Information Folder - a single location for artist artwork and nfo. This solves numerous issues related to artwork, artist data import and general folder and file structure <ref>https://github.com/xbmc/xbmc/pull/12891</ref>
* Added support for Extended Artwork, making the local art that is picked up automatically on scan configurable. <ref>https://github.com/xbmc/xbmc/pull/13352</ref><ref>https://github.com/xbmc/xbmc/pull/13848</ref><ref>https://github.com/xbmc/xbmc/pull/13491</ref><ref>https://github.com/xbmc/xbmc/pull/13101</ref><ref>https://github.com/xbmc/xbmc/pull/13871</ref>
* Added an option to prefer scraped album covers to embedded images <ref>https://github.com/xbmc/xbmc/pull/13812</ref>
* Added a filter to sort music items by media source <ref>https://github.com/xbmc/xbmc/pull/14012</ref><ref>https://github.com/xbmc/xbmc/pull/14082</ref>
* Improved use of BAND and ENSEMBLE (Vorbis and APE) tags. <ref>https://github.com/xbmc/xbmc/pull/11735</ref>
* Improved handling of duplicate MusicBrainzTrackID within the same album<ref>https://github.com/xbmc/xbmc/pull/12079</ref>
* Improved handling of Cue Sheets<ref>https://github.com/xbmc/xbmc/pull/12082</ref>
* Improved online scraping of additional artist and album information making better use of Musicbrainz IDs<ref>https://github.com/xbmc/xbmc/pull/12120</ref><ref>https://github.com/xbmc/xbmc/pull/12597</ref>
* Improved on clean installs, change default song sort order to Track Number <ref>https://github.com/xbmc/xbmc/pull/12834</ref>
* Improved FileItem::IsSamePath for albums and artists to prevent false matches<ref>https://github.com/xbmc/xbmc/pull/13585</ref>
* Improved album genre inconsistencies<ref>https://github.com/xbmc/xbmc/pull/13042</ref>
* Improved performance by avoiding unnecessary db access by GUI when app processing GUI_MSG_UPDATE_ITEM messages<ref>https://github.com/xbmc/xbmc/pull/13640</ref>
* Improved support for fetching local art for multi-folder albums (disc sets) <ref>https://github.com/xbmc/xbmc/pull/13769</ref>
* Changed Artist/Album Information Dialog <ref>https://github.com/xbmc/xbmc/pull/13672</ref>
* Changed Song Information Dialog <ref>https://github.com/xbmc/xbmc/pull/13533</ref>

=== Web Scrapers ===
* Added support for Python (script) based web scrapers for Kodi<ref>http://github.com/xbmc/xbmc/pull/9984</ref>
* Refactored and updated many XML based scrapers in Kodi for music, movies, tv shows, and music videos
* Updated music, movies, tv shows, and music video scrapers for Kodi
* ?

=== AudioEngine ===
* Added a new Sndio sink for [[AudioEngine#ActiveAE|ActiveAE]] for BSD, other BSD Unix based systems, and Linux<ref>https://github.com/xbmc/xbmc/pull/11962</ref>
* Improved the default cross-platform event driven active state machine pattern [[AudioEngine#ActiveAE|ActiveAE]] (Kodi's [[AudioEngine]])
* Improved ALSA sink for [[AudioEngine#ActiveAE|ActiveAE]] for Linux Desktop and generic Linux based Embedded Systems
* Improved PulseAudio sink for [[AudioEngine#ActiveAE|ActiveAE]] for Linux Desktop
* Improved OSS (Open Sound System) sink for [[AudioEngine#ActiveAE|ActiveAE]] for BSD, like FreeBSD and similar BSD Unix based systems
* Improved AUDIOTRACK sink for [[AudioEngine#ActiveAE|ActiveAE]] for [[Amlogic]]
* Improved Pi Audio sink for [[AudioEngine#ActiveAE|ActiveAE]] for [[Raspberry Pi]]
* Improved DirectSound sink for [[AudioEngine#ActiveAE|ActiveAE]] for Windows
* Improved WASAPI sink for [[AudioEngine#ActiveAE|ActiveAE]] for Windows
* Improved CoreAudio sink for [[AudioEngine#ActiveAE|ActiveAE]] for (Mac) OS X and iOS
* Improved Darwin sink for [[AudioEngine#ActiveAE|ActiveAE]] for (Mac) OS X and iOS
* Renamed AE_SINK to KODI_AE_SINK
* ?

=== Other ===
* Added a new unified setting for "Startup action" and added "Play TV/Radio"<ref>https://github.com/xbmc/xbmc/pull/12548</ref>
* Added support to build Kodi with support for Bluetooth<ref>http://github.com/xbmc/xbmc/pull/11137</ref>
* Added possibility for CMake build system to add additional libraries on install<ref>https://github.com/xbmc/xbmc/pull/12423</ref>
* Added and updated many audio visualization and screensaver addons for Kodi<ref>https://github.com/xbmc/repo-binary-addons</ref>
* Improved Kodi's JSON-RPC API
* Improved code stability, performance. and security, as well as general code clean-up in many core areas
* Improved compiling/building and code documentation (following doxygen coding guidelines)
* Changed to use spdlog for Kodi logging as well as improved and further optimized logging (including debug logs)<ref>https://github.com/xbmc/xbmc/pull/11833</ref>
* Changed XML format of setting values for Kodi's settings configuration<ref>https://github.com/xbmc/xbmc/pull/12277</ref>
* Updated and improved mappings for new and existing remote controls
* Updated default web interface (webinterface is called "Chorus2" and is currently at version 2.4.4)<ref>https://github.com/xbmc/xbmc/pull/11872</ref>
* Updated critical dependency libraries such as openssl, gnutls, and CMake (used to compile Kodi and its binary addons)
* Removed last dependencies of SDL (Simple DirectMedia Layer) which was hardware abstraction for input devices<ref>https://github.com/xbmc/xbmc/pull/12272</ref><ref>https://github.com/xbmc/xbmc/pull/11881</ref>
* Removed all glew (libglew library) dependencies in Kodi's code<ref>http://github.com/xbmc/xbmc/pull/11128</ref>
* ?

=== Android Specific ===
* Moved to Android API 26 and SDK 26 with NDK 18 as minimum (meaning at least Android 5.0 is still required)
* Added support for speech-to-text in Kodi OSD keyboard on Android TV (triggered by voice button on remote)
* Added support for Android to move the Kodi app to SD card<ref>https://github.com/xbmc/xbmc/pull/12168</ref>
* Added support for Android TV Leanback search and recommendations meta data from Kodi<ref>|https://github.com/xbmc/xbmc/pull/11901</ref>
** Default setting for Android TV Leanback suggestion to random unwatched movies and music albums<ref>https://github.com/xbmc/xbmc/pull/11963</ref>
* Changed Rendertype from GUILayer to VideoLayer for Android MediaCodecSurface<ref>https://github.com/xbmc/xbmc/pull/12097</ref>
* Changed to use NDK native C interface for Android MediaCodec (for performance gains)<ref>https://github.com/xbmc/xbmc/pull/11931</ref>
* Changed to support ZeroConf via native Android API (and deprecates mDNSresponder)<ref>http://github.com/xbmc/xbmc/pull/11393</ref>
* Changed to support network information via native Android API (and deprecates POSIX)<ref>https://github.com/xbmc/xbmc/pull/12243</ref>
* Changed handling of Kodi's Java interfaces via JNI for better consistency<ref>https://github.com/xbmc/xbmc/pull/12292</ref>
* ?

=== BSD Specific ===
* Improved Kodi support for [http://en.wikipedia.org/wiki/Berkeley_Software_Distribution BSD (operating system)] on FreeBSD, PC-BSD, and other similar BSD platforms
* Improved VAAPI (Video Acceleration API) support (requires VAAPI compatible hardware and drivers)
* Improved VDPAU (NVIDIA) Hardware Video Acceleration (requires VDPAU compatible hardware and drivers)
* ?

=== Linux Specific ===
* Added support for a generic DRM/KMS implementation using GBM to create surfaces and V4L2 for video acceleration<ref>https://github.com/xbmc/xbmc/pull/11955</ref>
* Added support for Mir windowing system (Mir 1.0) for Kodi<ref>http://github.com/xbmc/xbmc/pull/10898</ref> and added support for VAAPI on Mir using DRM<ref>http://github.com/xbmc/xbmc/pull/11040</ref>
* Added support for the middle mouse button on embedded platforms<ref>https://github.com/xbmc/xbmc/pull/11956</ref>
* Added support more yuv420p bitwidths for direct rendering on Linux<ref>https://github.com/xbmc/xbmc/pull/12479</ref>
* Added support for using VAAPI hardware video decoding with OpenGL ES<ref>https://github.com/xbmc/xbmc/pull/12113</ref>
* Added support for build Kodi with imx support using CMake<ref>http://github.com/xbmc/xbmc/pull/11288</ref>
* Moved the CMake build system to the top of the code tree (moved to root)<ref>http://github.com/xbmc/xbmc/pull/10446</ref>
* Improved support for UltraHD decoding / 4K resolution output when hardware supports it
* Improved ARM processor architecture (using [[Raspberry Pi]] as reference device)
* Improved OpenGL ES and EGL support (using [[Raspberry Pi]] as reference device)
* Improved VAAPI (Video Acceleration API) support (requires VAAPI compatible hardware and drivers)
* Improved VDPAU (NVIDIA) Hardware Video Acceleration (requires VDPAU compatible hardware and drivers)
* Improved XvBA (AMD/ATI) Hardware Video Acceleration (requires XvBA compatible hardware and drivers)
* Improved dedicated AMLCodec hardware accelerated video decoding support for Linux on Amlogic devices
* Removed the unused and unmaintained OpenMAX video decoder from Kodi's VideoPlayer<ref>https://github.com/xbmc/xbmc/pull/12197</ref>
* Removed support for autotools based build system for Kodi and binary addons (in favour of CMake)<ref>http://github.com/xbmc/xbmc/pull/10429</ref>
* ?

=== iOS Specific ===
* Added support for iOS 10.0 by adding support for compiling Kodi with Xcode 8 IDE and iOS SDK 10.0<ref>https://github.com/xbmc/xbmc/pull/10539</ref>
* Improved Apple VDADecoder Video Acceleration support for iOS (on iPad, iPhone, and iPod iDevices)
* Improved support for TVOS (Apple's iOS fork for Apple TV 4) in Kodi mainline
* Improved support for iOS on ARM64 (64-bit iOS)
* ?

=== OS X Specific ===
* Added support for compiling Kodi with Xcode 8 IDE for OSX 10.11 (El Capitan) and macOS 10.12 (Sierra)
* Improved Apple VDADecoder Video Acceleration support for (Mac) OS X
* ?

=== Windows Specific ===
* Added support to build Kodi for Windows 64 / Windows for Intel 64-bit (x86-64)<ref>https://github.com/xbmc/xbmc/pull/12065</ref>
* Added support for 3D LUT (3D Lookup Table) and dithering to Windows video renderer<ref name="WinRenderer re-work">https://github.com/xbmc/xbmc/pull/12475</ref>
* Improved support to compiling Kodi for Microsoft's UWP (Universal Windows Platform) APIs
* Changed the inner working of render buffers and rendering methods<ref name="WinRenderer re-work"/>
* Changed to using unicode win32 api methods<ref>https://github.com/xbmc/xbmc/pull/11780</ref>
* Changed windowing systems for screen saver handling on Windows OS platforms
* Changed to make Kodi for Windows platform independent of posix/main.cpp<ref>https://github.com/xbmc/xbmc/pull/12215</ref>
* Removed support for Windows Vista as the operating-system is no longer supported by Microsoft<ref>https://github.com/xbmc/xbmc/pull/11953</ref>
* ?

== References ==
<references/>

== See also ==
* [[Leia API changes]]
{{Changelogs}}

[[Category:Manual]]
[[Category:Leia|*]]
[[Category:Changelogs|18]]

Game add-ons

2018-10-26T12:57:14Z

Gamester17: /* See also */

<noinclude>{{mininav| [[Kodi Game]] }}</noinclude>

Status on ported currently existing game client addons for the new Game API made available in [[Kodi Game|Kodi Game branch]].

{{warning|These pages are maintained by the community, it only goes as far as [[w:fair use|fair use]], and this should not be considered as an endorsement for copyright infringement. The information on this page might also contain errors or be outdated. It might also contain ants, and their antsy antics. '''[[Kodi:General disclaimer|*]]''' }}

__TOC__
==Stand-alone game add-ons==
Stand-alone games or emulators that does not use the Libretro API.

Here will be a list of existing/ongoing and future/upcoming project for making new stand-alone game add-ons for Kodi:
* Project discussion: "NVIDIA Gamestream in Kodi" http://forum.kodi.tv/showthread.php?tid=220421
* Proposal: NVIDIA GameStream http://forum.kodi.tv/showthread.php?tid=220965
* GitHub repo: https://github.com/kodi-game/game.moonlight

==Libretro cores==
:{{Main|Libretro|Porting Libretro cores to game add-ons}}
The Game API in the [[Kodi Game|Kodi Game branch]] has a Libretro wrapper which is 1:1 compatibility with the libretro API, so all libretro cores are valid game add-ons. Libretro itself is a well defined interface to handle the communication between a frontend (Kodi with RetroPlayer) and an Emulator Core (e.g. nestopia).

Here is a list of Libretro cores, of which most already have been [[Porting Libretro cores to game add-ons|ported]] into game add-ons for Kodi, at least as an initial port, (you can see the status of each libretro core in the table below):



{| class="prettytable sortable plainlinks"
! Libretro core !! Platform emulated !! Version !! License * !! Supports VFS !! Supports Rewind !! Requires GL !! Status
|-
{{game add-on
| Name= [https://github.com/kodi-game/game.libretro.2048/blob/master/game.libretro.2048/addon.xml.in 2048]
| Platform= 2048 Game Clone
| Version= 1.0.0
| License= {{yes|Public Domain}}
| Supports VFS= {{yes|yes}}
| Supports Rewind= ?
| Requires GL= {{no|no}}
| Status= {{yes|done}}
}}
{{game add-on
| Name= [https://github.com/kodi-game/game.libretro.4do/blob/master/game.libretro.4do/addon.xml.in 3DO (4DO)]
| Platform= 3DO
| Version= 1.3.2
| License= {{no|Non-commercial}}
| Supports VFS= {{no|no}}
| Supports Rewind= ?
| Requires GL= {{no|no}}
| Status= {{yes|done}}
}}
{{game add-on
| Name= [https://github.com/kodi-game/game.libretro.beetle-bsnes/blob/master/game.libretro.beetle-bsnes/addon.xml.in SNES / Super Famicom (Beetle bsnes)]
| Platform= Super Nintendo Entertainment System
| Version= 0.9.26
| License= {{yes|GPLv2}}
| Supports VFS= {{no|no}}
| Supports Rewind= ?
| Requires GL= {{no|no}}
| Status= {{yes|done}}
}}
{{game add-on
| Name= [https://github.com/kodi-game/game.libretro.beetle-gba/blob/master/game.libretro.beetle-gba/addon.xml.in Game Boy Advance (Beetle GBA)]
| Platform= Game Boy Advance
| Version= 0.9.36
| License= {{yes|GPLv2}}
| Supports VFS= {{no|no}}
| Supports Rewind= ?
| Requires GL= {{no|no}}
| Status= {{yes|done}}
}}
{{game add-on
| Name= [https://github.com/kodi-game/game.libretro.beetle-lynx/blob/master/game.libretro.beetle-lynx/addon.xml.in Atari Lynx (Beetle Handy)]
| Platform= Lynx
| Version= 0.9.32
| License= {{yes|Zlib, GPLv2}}
| Supports VFS= {{no|no}}
| Supports Rewind= ?
| Requires GL= {{no|no}}
| Status= {{yes|done}}
}}
{{game add-on
| Name= [https://github.com/kodi-game/game.libretro.beetle-ngp/blob/master/game.libretro.beetle-ngp/addon.xml.in Neo Geo Pocket/Color (Beetle NeoPop)]
| Platform= Neo Geo Pocket (Color)
| Version= 0.9.36
| License= {{yes|GPLv2}}
| Supports VFS= {{no|no}}
| Supports Rewind= ?
| Requires GL= {{no|no}}
| Status= {{yes|done}}
}}
{{game add-on
| Name= [https://github.com/kodi-game/game.libretro.beetle-pce-fast/blob/master/game.libretro.beetle-pce-fast/addon.xml.in PC Engine/PCE-CD (Beetle PCE FAST)]
| Platform= PC Engine/PCE-CD
| Version= 0.9.38
| License= {{yes|GPLv2}}
| Supports VFS= {{no|no}}
| Supports Rewind= ?
| Requires GL= {{no|no}}
| Status= {{yes|done}}
}}
{{game add-on
| Name= [https://github.com/kodi-game/game.libretro.beetle-pcfx/blob/master/game.libretro.beetle-pcfx/addon.xml.in PC-FX (Beetle PC-FX)]
| Platform= PC-FX
| Version= 0.9.33
| License= {{yes|GPLv2}}
| Supports VFS= {{no|no}}
| Supports Rewind= ?
| Requires GL= {{no|no}}
| Status= {{yes|done}}
}}
{{game add-on
| Name= [https://github.com/kodi-game/game.libretro.beetle-psx/blob/master/game.libretro.beetle-psx/addon.xml.in PlayStation (Beetle PSX)]
| Platform= PlayStation
| Version= 0.9.44
| License= {{yes|GPLv2}}
| Supports VFS= {{no|no}}
| Supports Rewind= ?
| Requires GL= {{no|no}}
| Status= {{yes|done}}
}}
{{game add-on
| Name= [https://github.com/kodi-game/game.libretro.beetle-saturn/blob/master/game.libretro.beetle-saturn/addon.xml.in Sega Saturn (Beetle Saturn)]
| Platform= Saturn
| Version= 0.9.48
| License= {{yes|GPLv2}}
| Supports VFS= {{no|no}}
| Supports Rewind= ?
| Requires GL= {{no|no}}
| Status= {{yes|done}}
}}
{{game add-on
| Name= [https://github.com/kodi-game/game.libretro.beetle-supergrafx/blob/master/game.libretro.beetle-supergrafx/addon.xml.in PC Engine SuperGrafx (Beetle SGX)]
| Platform= PC Engine SuperGrafx
| Version= 0.9.38
| License= {{yes|GPLv2}}
| Supports VFS= {{no|no}}
| Supports Rewind= ?
| Requires GL= {{no|no}}
| Status= {{yes|done}}
}}
{{game add-on
| Name= [https://github.com/kodi-game/game.libretro.beetle-vb/blob/master/game.libretro.beetle-vb/addon.xml.in Virtual Boy (Beetle VB)]
| Platform= Virtual Boy
| Version= 0.9.36
| License= {{yes|GPLv2}}
| Supports VFS= {{no|no}}
| Supports Rewind= ?
| Requires GL= {{no|no}}
| Status= {{yes|done}}
}}
{{game add-on
| Name= [https://github.com/kodi-game/game.libretro.beetle-wswan/blob/master/game.libretro.beetle-wswan/addon.xml.in WonderSwan/Color (Beetle Cygne)]
| Platform= WonderSwan/Color
| Version= 0.9.35
| License= {{yes|GPLv2}}
| Supports VFS= {{no|no}}
| Supports Rewind= ?
| Requires GL= {{no|no}}
| Status= {{yes|done}}
}}
{{game add-on
| Name= [https://github.com/kodi-game/game.libretro.bluemsx/blob/master/game.libretro.bluemsx/addon.xml.in MSX/SVI/ColecoVision/SG-1000 (blueMSX)]
| Platform= MSX/SVI/ColecoVision/SG-1000
| Version= 1.0.0
| License= {{yes|GPLv2}}
| Supports VFS= {{no|no}}
| Supports Rewind= ?
| Requires GL= {{no|no}}
| Status= {{yes|done}}
}}
{{game add-on
| Name= [https://github.com/kodi-game/game.libretro.bnes/blob/master/game.libretro.bnes/addon.xml.in NES / Famicom (bnes)]
| Platform= Nintendo Entertainment System
| Version= 0.83.0
| License= {{partial|GPLv3}}
| Supports VFS= {{yes|yes}}
| Supports Rewind= ?
| Requires GL= {{no|no}}
| Status= {{yes|done}}
}}
{{game add-on
| Name= [https://github.com/kodi-game/game.libretro.bsnes-mercury-accuracy/blob/master/game.libretro.bsnes-mercury-accuracy/addon.xml.in SNES / Super Famicom (bsnes-mercury Accuracy)]
| Platform= Super Nintendo Entertainment System
| Version= 0.94.0
| License= {{partial|GPLv3}}
| Supports VFS= {{yes|yes}}
| Supports Rewind= ?
| Requires GL= {{no|no}}
| Status= {{yes|done}}
}}
{{game add-on
| Name= [https://github.com/kodi-game/game.libretro.bsnes-mercury-balanced/blob/master/game.libretro.bsnes-mercury-balanced/addon.xml.in SNES / Super Famicom (bsnes-mercury Balanced)]
| Platform= Super Nintendo Entertainment System
| Version= 0.94.0
| License= {{partial|GPLv3}}
| Supports VFS= {{yes|yes}}
| Supports Rewind= ?
| Requires GL= {{no|no}}
| Status= {{yes|done}}
}}
{{game add-on
| Name= [https://github.com/kodi-game/game.libretro.bsnes-mercury-performance/blob/master/game.libretro.bsnes-mercury-performance/addon.xml.in SNES / Super Famicom (bsnes-mercury Performance)]
| Platform= Super Nintendo Entertainment System
| Version= 0.94.0
| License= {{partial|GPLv3}}
| Supports VFS= {{yes|yes}}
| Supports Rewind= ?
| Requires GL= {{no|no}}
| Status= {{yes|done}}
}}
{{game add-on
| Name= [https://github.com/kodi-game/game.libretro.cap32/blob/master/game.libretro.cap32/addon.xml.in Amstrad CPC (Caprice32)]
| Platform= CPC
| Version= 4.2.0
| License= {{yes|GPLv2}}
| Supports VFS= {{no|no}}
| Supports Rewind= ?
| Requires GL= {{no|no}}
| Status= {{yes|done}}
}}
{{game add-on
| Name= [https://github.com/kodi-game/game.libretro.desmume/blob/master/game.libretro.desmume/addon.xml.in Nintendo DS (DeSmuME)]
| Platform= Nintendo DS
| Version= 1.0.0
| License= {{yes|GPLv2}}
| Supports VFS= {{no|no}}
| Supports Rewind= ?
| Requires GL= {{no|no}}
| Status= {{yes|done}}
}}
{{game add-on
| Name= [https://github.com/kodi-game/game.libretro.dinothawr/blob/master/game.libretro.dinothawr/addon.xml.in Dinothawr]
| Platform= Dinothawr Game Engine
| Version= 1.0.0
| License= {{no|Non-commercial}}
| Supports VFS= {{no|no}}
| Supports Rewind= ?
| Requires GL= {{no|no}}
| Status= {{yes|done}}
}}
{{game add-on
| Name= [https://github.com/kodi-game/game.libretro.dosbox/blob/master/game.libretro.dosbox/addon.xml.in DOS (DOSBox)]
| Platform= DOS
| Version= 0.74.0
| License= {{yes|GPLv2}}
| Supports VFS= {{no|no}}
| Supports Rewind= ?
| Requires GL= {{no|no}}
| Status= {{yes|done}}
}}
{{game add-on
| Name= [https://github.com/kodi-game/game.libretro.fbalpha/blob/master/game.libretro.fbalpha/addon.xml.in Arcade (FB Alpha)]
| Platform= Arcade (various)
| Version= 0.2.97
| License= {{no|Non-commercial}}
| Supports VFS= {{no|no}}
| Supports Rewind= ?
| Requires GL= {{no|no}}
| Status= {{yes|done}}
}}
{{game add-on
| Name= [https://github.com/kodi-game/game.libretro.fbalpha2012/blob/master/game.libretro.fbalpha2012/addon.xml.in Arcade (FB Alpha 2012)]
| Platform= Arcade (various)
| Version= 0.2.97
| License= {{no|Non-commercial}}
| Supports VFS= {{no|no}}
| Supports Rewind= ?
| Requires GL= {{no|no}}
| Status= {{yes|done}}
}}
{{game add-on
| Name= [https://github.com/kodi-game/game.libretro.fceumm/blob/master/game.libretro.fceumm/addon.xml.in NES / Famicom (FCEUmm)]
| Platform= Nintendo Entertainment System
| Version= 1.0.0
| License= {{yes|GPLv2}}
| Supports VFS= {{yes|yes}}
| Supports Rewind= ?
| Requires GL= {{no|no}}
| Status= {{yes|done}}
}}
{{game add-on
| Name= [https://github.com/kodi-game/game.libretro.fmsx/blob/master/game.libretro.fmsx/addon.xml.in MSX (fMSX)]
| Platform= MSX
| Version= 4.9.0
| License= {{no|Non-commercial}}
| Supports VFS= {{no|no}}
| Supports Rewind= ?
| Requires GL= {{no|no}}
| Status= {{yes|done}}
}}
{{game add-on
| Name= [https://github.com/kodi-game/game.libretro.fuse/blob/master/game.libretro.fuse/addon.xml.in ZX Spectrum (Fuse)]
| Platform= ZX Spectrum (various)
| Version= 1.1.1
| License= {{partial|GPLv3}}
| Supports VFS= {{yes|yes}}
| Supports Rewind= ?
| Requires GL= {{no|no}}
| Status= {{yes|done}}
}}
{{game add-on
| Name= [https://github.com/kodi-game/game.libretro.gambatte/blob/master/game.libretro.gambatte/addon.xml.in Game Boy / Game Boy Color (Gambatte)]
| Platform= Game Boy/Game Boy Color
| Version= 0.5.0
| License= {{yes|GPLv2}}
| Supports VFS= {{yes|yes}}
| Supports Rewind= ?
| Requires GL= {{no|no}}
| Status= {{yes|done}}
}}
{{game add-on
| Name= [https://github.com/kodi-game/game.libretro.genplus/blob/master/game.libretro.genplus/addon.xml.in Sega MS/GG/MD/CD (Genesis Plus GX)]
| Platform= Sega 8/16-bit (Various)
| Version= 1.7.4
| License= {{no|Non-commercial}}
| Supports VFS= {{no|no}}
| Supports Rewind= ?
| Requires GL= {{no|no}}
| Status= {{yes|done}}
}}
{{game add-on
| Name= [https://github.com/kodi-game/game.libretro.gw/blob/master/game.libretro.gw/addon.xml.in Handheld Electronic (GW)]
| Platform= Handheld Electronic
| Version= 1.6.2
| License= {{yes|zlib}}
| Supports VFS= {{yes|yes}}
| Supports Rewind= ?
| Requires GL= {{no|no}}
| Status= {{yes|done}}
}}
{{game add-on
| Name= [https://github.com/kodi-game/game.libretro.handy/blob/master/game.libretro.handy/addon.xml.in Atari Lynx (Handy)]
| Platform= Lynx
| Version= 0.97.0
| License= {{yes|Zlib}}
| Supports VFS= {{no|no}}
| Supports Rewind= ?
| Requires GL= {{no|no}}
| Status= {{yes|done}}
}}
{{game add-on
| Name= [https://github.com/kodi-game/game.libretro.hatari/blob/master/game.libretro.hatari/addon.xml.in Atari ST/STE/TT/Falcon (Hatari)]
| Platform= Atari ST/STE/TT/Falcon
| Version= 1.8.0
| License= {{yes|GPLv2}}
| Supports VFS= {{no|no}}
| Supports Rewind= ?
| Requires GL= {{no|no}}
| Status= {{yes|done}}
}}
{{game add-on
| Name= [https://github.com/kodi-game/game.libretro.lutro/blob/master/game.libretro.lutro/addon.xml.in Lua Engine (Lutro)]
| Platform= Lutro
| Version= 0.0.1
| License= {{yes|MIT}}
| Supports VFS= {{no|no}}
| Supports Rewind= ?
| Requires GL= {{no|no}}
| Status= {{yes|done}}
}}
{{game add-on
| Name= [https://github.com/kodi-game/game.libretro.melonds/blob/master/game.libretro.melonds/addon.xml.in Nintendo DS (melonDS)]
| Platform= Nintendo DS
| Version= 0.6.0
| License= {{yes|GPLv2}}
| Supports VFS= {{no|no}}
| Supports Rewind= ?
| Requires GL= {{no|no}}
| Status= {{yes|done}}
}}
{{game add-on
| Name= [https://github.com/kodi-game/game.libretro.meteor/blob/master/game.libretro.meteor/addon.xml.in Game Boy Advance (Meteor)]
| Platform= Game Boy Advance
| Version= 1.4.0
| License= {{partial|GPLv3}}
| Supports VFS= {{yes|yes}}
| Supports Rewind= ?
| Requires GL= {{no|no}}
| Status= {{yes|done}}
}}
{{game add-on
| Name= [https://github.com/kodi-game/game.libretro.mgba/blob/master/game.libretro.mgba/addon.xml.in Game Boy Advance (mGBA)]
| Platform= Game Boy/Game Boy Color/Game Boy Advance
| Version= 0.6.1
| License= {{yes|MPLv2.0}}
| Supports VFS= {{yes|yes}}
| Supports Rewind= ?
| Requires GL= {{no|no}}
| Status= {{yes|done}}
}}
{{game add-on
| Name= [https://github.com/kodi-game/game.libretro.mrboom/blob/master/game.libretro.mrboom/addon.xml.in Mr.Boom (Bomberman)]
| Platform= Mr.Boom
| Version= 4.1.0
| License= {{yes|}}
| Supports VFS= {{yes|yes}}
| Supports Rewind= ?
| Requires GL= {{no|no}}
| Status= {{yes|done}}
}}
{{game add-on
| Name= [https://github.com/kodi-game/game.libretro.mupen64plus/blob/master/game.libretro.mupen64plus/addon.xml.in Nintendo 64 (Mupen64Plus)]
| Platform= Nintendo 64
| Version= 2.5.0
| License= {{yes|GPLv2}}
| Supports VFS= {{yes|yes}}
| Supports Rewind= ?
| Requires GL= {{yes|yes}}
| Status= {{yes|done}}
}}
{{game add-on
| Name= [https://github.com/kodi-game/game.libretro.nestopia/blob/master/game.libretro.nestopia/addon.xml.in NES / Famicom (Nestopia UE)]
| Platform= Nintendo Entertainment System
| Version= 1.49.0
| License= {{yes|GPLv2}}
| Supports VFS= {{yes|yes}}
| Supports Rewind= ?
| Requires GL= {{no|no}}
| Status= {{yes|done}}
}}
{{game add-on
| Name= [https://github.com/kodi-game/game.libretro.nx/blob/master/game.libretro.nx/addon.xml.in Cave Story (NXEngine)]
| Platform= Cave Story Game Engine
| Version= 1.0.0
| License= {{partial|GPLv3}}
| Supports VFS= {{no|no}}
| Supports Rewind= ?
| Requires GL= {{no|no}}
| Status= {{yes|done}}
}}
{{game add-on
| Name= [https://github.com/kodi-game/game.libretro.o2em/blob/master/game.libretro.o2em/addon.xml.in Odyssey2 / Videopac+ (O2EM)]
| Platform= Magnavox Odyssey2 / Phillips Videopac+
| Version= 1.18.0
| License= {{yes|Artistic License}}
| Supports VFS= {{no|no}}
| Supports Rewind= ?
| Requires GL= {{no|no}}
| Status= {{yes|done}}
}}
{{game add-on
| Name= [https://github.com/kodi-game/game.libretro.pcem/blob/master/game.libretro.pcem/addon.xml.in PC (PCem)]
| Platform= PC
| Version= 12.0.0
| License= {{yes|GPLv2}}
| Supports VFS= {{yes|yes}}
| Supports Rewind= ?
| Requires GL= {{no|no}}
| Status= {{yes|done}}
}}
{{game add-on
| Name= [https://github.com/kodi-game/game.libretro.pcsx-rearmed/blob/master/game.libretro.pcsx-rearmed/addon.xml.in PlayStation (PCSX ReARMed)]
| Platform= PlayStation
| Version= 22.0.0
| License= {{yes|GPLv2}}
| Supports VFS= {{no|no}}
| Supports Rewind= ?
| Requires GL= {{no|no}}
| Status= {{yes|done}}
}}
{{game add-on
| Name= [https://github.com/kodi-game/game.libretro.picodrive/blob/master/game.libretro.picodrive/addon.xml.in Sega MS/MD/CD/32X (PicoDrive)]
| Platform= Sega 8/16-bit + 32X (Various)
| Version= 1.92.0
| License= {{yes|MAME}}
| Supports VFS= {{no|no}}
| Supports Rewind= ?
| Requires GL= {{no|no}}
| Status= {{yes|done}}
}}
{{game add-on
| Name= [https://github.com/kodi-game/game.libretro.pokemini/blob/master/game.libretro.pokemini/addon.xml.in Pokémon Mini (PokeMini)]
| Platform= Pokémon Mini
| Version= 0.60.0
| License= {{partial|GPLv3}}
| Supports VFS= {{yes|yes}}
| Supports Rewind= ?
| Requires GL= {{no|no}}
| Status= {{yes|done}}
}}
{{game add-on
| Name= [https://github.com/kodi-game/game.libretro.prboom/blob/master/game.libretro.prboom/addon.xml.in Doom (PrBoom)]
| Platform= DOOM Game Engine
| Version= 2.5.0
| License= {{yes|GPLv2}}
| Supports VFS= {{no|no}}
| Supports Rewind= ?
| Requires GL= {{no|no}}
| Status= {{yes|done}}
}}
{{game add-on
| Name= [https://github.com/kodi-game/game.libretro.prosystem/blob/master/game.libretro.prosystem/addon.xml.in Atari 7800 (ProSystem)]
| Platform= Atari 7800
| Version= 1.3.0
| License= {{yes|GPLv2}}
| Supports VFS= {{yes|yes}}
| Supports Rewind= ?
| Requires GL= {{no|no}}
| Status= {{yes|done}}
}}
{{game add-on
| Name= [https://github.com/kodi-game/game.libretro.quicknes/blob/master/game.libretro.quicknes/addon.xml.in NES / Famicom (QuickNES)]
| Platform= Nintendo Entertainment System
| Version= 1.0.0
| License= {{yes|LGPLv2.1+}}
| Supports VFS= {{yes|yes}}
| Supports Rewind= ?
| Requires GL= {{no|no}}
| Status= {{yes|done}}
}}
{{game add-on
| Name= [https://github.com/kodi-game/game.libretro.reicast/blob/master/game.libretro.reicast/addon.xml.in Sega Dreamcast (Reicast)]
| Platform= Sega Dreamcast
| Version= 0.1.0
| License= {{yes|GPLv2}}
| Supports VFS= {{no|no}}
| Supports Rewind= ?
| Requires GL= {{yes|yes}}
| Status= {{yes|done}}
}}
{{game add-on
| Name= [https://github.com/kodi-game/game.libretro.sameboy/blob/master/game.libretro.sameboy/addon.xml.in Game Boy / Game Boy Color (SameBoy)]
| Platform= Game Boy/Game Boy Color
| Version= 0.9.0
| License= {{yes|MIT}}
| Supports VFS= {{no|no}}
| Supports Rewind= ?
| Requires GL= {{no|no}}
| Status= {{yes|done}}
}}
{{game add-on
| Name= [https://github.com/kodi-game/game.libretro.scummvm/blob/master/game.libretro.scummvm/addon.xml.in ScummVM]
| Platform= Game engine
| Version= 2.0.0
| License= {{yes|GPLv2}}
| Supports VFS= {{no|no}}
| Supports Rewind= ?
| Requires GL= {{no|no}}
| Status= {{yes|done}}
}}
{{game add-on
| Name= [https://github.com/kodi-game/game.libretro.snes9x/blob/master/game.libretro.snes9x/addon.xml.in SNES / Super Famicom (Snes9x)]
| Platform= Super Nintendo Entertainment System
| Version= 1.54.1
| License= {{no|Non-commercial}}
| Supports VFS= {{yes|yes}}
| Supports Rewind= ?
| Requires GL= {{no|no}}
| Status= {{yes|done}}
}}
{{game add-on
| Name= [https://github.com/kodi-game/game.libretro.snes9x2002/blob/master/game.libretro.snes9x2002/addon.xml.in SNES / Super Famicom (Snes9x 2002)]
| Platform= Super Nintendo Entertainment System
| Version= 7.2.0
| License= {{no|Non-commercial}}
| Supports VFS= {{yes|yes}}
| Supports Rewind= ?
| Requires GL= {{no|no}}
| Status= {{yes|done}}
}}
{{game add-on
| Name= [https://github.com/kodi-game/game.libretro.snes9x2010/blob/master/game.libretro.snes9x2010/addon.xml.in SNES / Super Famicom (Snes9x 2010)]
| Platform= Super Nintendo Entertainment System
| Version= 1.52.4
| License= {{no|Non-commercial}}
| Supports VFS= {{yes|yes}}
| Supports Rewind= ?
| Requires GL= {{no|no}}
| Status= {{yes|done}}
}}
{{game add-on
| Name= [https://github.com/kodi-game/game.libretro.stella/blob/master/game.libretro.stella/addon.xml.in Atari 2600 (Stella)]
| Platform= Atari 2600
| Version= 3.9.3
| License= {{yes|GPLv2}}
| Supports VFS= {{yes|yes}}
| Supports Rewind= ?
| Requires GL= {{no|no}}
| Status= {{yes|done}}
}}
{{game add-on
| Name= [https://github.com/kodi-game/game.libretro.tgbdual/blob/master/game.libretro.tgbdual/addon.xml.in Game Boy / Game Boy Color (TGB Dual)]
| Platform= Game Boy/Game Boy Color
| Version= 0.8.3
| License= {{yes|GPLv2}}
| Supports VFS= {{yes|yes}}
| Supports Rewind= ?
| Requires GL= {{no|no}}
| Status= {{yes|done}}
}}
{{game add-on
| Name= [https://github.com/kodi-game/game.libretro.tyrquake/blob/master/game.libretro.tyrquake/addon.xml.in Quake 1 (TyrQuake)]
| Platform= Quake Game Engine
| Version= 0.62.0
| License= {{yes|GPLv2}}
| Supports VFS= {{no|no}}
| Supports Rewind= ?
| Requires GL= {{no|no}}
| Status= {{yes|done}}
}}
{{game add-on
| Name= [https://github.com/kodi-game/game.libretro.uae/blob/master/game.libretro.uae/addon.xml.in Amiga (P-UAE)]
| Platform= Commodore Amiga
| Version= 2.6.1
| License= {{yes|GPLv2}}
| Supports VFS= {{no|no}}
| Supports Rewind= ?
| Requires GL= {{no|no}}
| Status= {{yes|done}}
}}
{{game add-on
| Name= [https://github.com/kodi-game/game.libretro.vba-next/blob/master/game.libretro.vba-next/addon.xml.in Game Boy Advance (VBA Next)]
| Platform= Game Boy Advance
| Version= 1.0.2
| License= {{yes|GPLv2}}
| Supports VFS= {{yes|yes}}
| Supports Rewind= ?
| Requires GL= {{no|no}}
| Status= {{yes|done}}
}}
{{game add-on
| Name= [https://github.com/kodi-game/game.libretro.vbam/blob/master/game.libretro.vbam/addon.xml.in Game Boy Advance (VBA-M)]
| Platform= Game Boy Advance
| Version= 1.8.0
| License= {{yes|GPLv2}}
| Supports VFS= {{yes|yes}}
| Supports Rewind= ?
| Requires GL= {{no|no}}
| Status= {{yes|done}}
}}
{{game add-on
| Name= [https://github.com/kodi-game/game.libretro.vecx/blob/master/game.libretro.vecx/addon.xml.in Vectrex (vecx)]
| Platform= Vectrex
| Version= 1.2.0
| License= {{partial|GPLv3}}
| Supports VFS= {{yes|yes}}
| Supports Rewind= ?
| Requires GL= {{no|no}}
| Status= {{yes|done}}
}}
{{game add-on
| Name= [https://github.com/kodi-game/game.libretro.vice/blob/master/game.libretro.vice/addon.xml.in Commodore 64 (VICE)]
| Platform= C64
| Version= 3.0.0
| License= {{yes|GPLv2}}
| Supports VFS= {{no|no}}
| Supports Rewind= ?
| Requires GL= {{no|no}}
| Status= {{yes|done}}
}}
{{game add-on
| Name= [https://github.com/kodi-game/game.libretro.virtualjaguar/blob/master/game.libretro.virtualjaguar/addon.xml.in Atari Jaguar (Virtual Jaguar)]
| Platform= Jaguar
| Version= 2.1.0
| License= {{partial|GPLv3}}
| Supports VFS= {{yes|yes}}
| Supports Rewind= ?
| Requires GL= {{no|no}}
| Status= {{yes|done}}
}}
{{game add-on
| Name= [https://github.com/kodi-game/game.libretro.yabause/blob/master/game.libretro.yabause/addon.xml.in Sega Saturn (Yabause)]
| Platform= Saturn
| Version= 0.9.14
| License= {{yes|GPLv2}}
| Supports VFS= {{no|no}}
| Supports Rewind= ?
| Requires GL= {{no|no}}
| Status= {{yes|done}}
}}
|} 

<nowiki>*</nowiki> License is GPLv2 compatible

If something in the core matrix needs to be changed, leave a message in the forum.

== BIOS requirements ==
Some libretro cores require BIOS files to work, and those BIOSes must be placed in the system folder (with each BIOS being a binary file). For now you will need to find those BIOS files by yourself and and copy them to your system yourself as it may not be fully legal for Team-Kodi to provide them bundled with each libretro core that needs them. The reason for this is that these BIOSes are usually considered to be in an legal gray-zone and can be a little difficult to aquire, at least legally. For example, since all PlayStation emulators, like Beetle PSX & PCSX ReARMed, require a closed source BIOS file to work, and its BIOS file must be placed in the system folder on your emulator software (libretro cores in this case).

* See: https://github.com/libretro/Lakka/wiki/BIOSes and and http://www.lakka.tv/doc/Accessing-Lakka-filesystem/ (or see: http://github.com/libretro/Lakka/wiki/ROMs-and-BIOSes ). You should find the most up-to-date information here https://github.com/libretro/libretro-super/tree/master/dist/info and here https://github.com/libretro/libretro-database/blob/master/dat/BIOS%20-%20Merged.dat

=== BIOS requirement table ===
The table below lists all the required BIOSes which some emulators requires for each each emulated system, so if a systems BIOS is not listed here then it means that it should not require a BIOS file.

{|
| Warning! Linux is a case sensitive system. Please name BIOS files exactly according to this table.
|}
{| width="100%" class="datatable"
|-
! rowspan="2" | System !! rowspan="2" | BIOS file !! rowspan="2" | MD5 !! rowspan="2" | Comment
|-
!
|-
| 3DO - 3DO || panafz10.bin || 51f2f43ae2f3508a14d9f56597e2d3ce || ||
|-
| Atari - 7800 || 7800 BIOS (U).rom || 0763f1ffb006ddbe32e52d497ee848ae || ||
|-
| Atari - Lynx || lynxboot.img || FCD403DB69F54290B51035D82F835E7B || ||
|-
| Final Burn Alpha || || || BIOS goes next to the ROMs ||
|-
| DOOM || || || BIOS goes next to the ROMs ||
|-
| Magnavox - Odyssey2 || o2rom.bin || 562d5ebf9e030a40d6fabfc2f33139fd || ||
|-
| MAME 2003 || || || BIOS goes next to the ROMs ||
|-
| NEC - PC Engine - TurboGrafx 16 || syscard3.pce || 0754f903b52e3b3342202bdafb13efa5 || ||
|-
| NEC - PC-FX || pcfx.rom || 08e36edbea28a017f79f8d4f7ff9b6d7 || ||
|-
| Nintendo - Famicom Disk System || disksys.rom || ca30b50f880eb660a320674ed365ef7a || ||
|-
| Nintendo - Game Boy Advance || gba_bios.bin || a860e8c0b6d573d191e4ec7db1b1e4f6 || ||
|-
| Phillips - Videopac+ || o2rom.bin ? || || Same as Magnavox Oddessy2? ||
|-
| Sega - Dreamcast || dc_boot.bin || e10c53c2f8b90bab96ead2d368858623 || Goes under system/dc/ ||
|-
| Sega - Dreamcast || dc_flash.bin || 0a93f7940c455905bea6e392dfde92a4 || Goes under system/dc/ ||
|-
| Sega - Mega Drive - Genesis || bios_CD_J.bin || 278a9397d192149e84e820ac621a8edd || Japan ||
|-
| Sega - Mega Drive - Genesis || bios_CD_U.bin || 2efd74e3232ff260e371b99f84024f7f || USA ||
|-
| Sega - Mega Drive - Genesis || bios_CD_E.bin || e66fa1dc5820d254611fdcdba0662372 || Europe||
|-
| Sega - Saturn || saturn_bios.bin || f273555d7d91e8a5a6bfd9bcf066331c || ||
|-
| Sony - PlayStation || scph5500.bin || 8dd7d5296a650fac7319bce665a6a53c || Japan ||
|-
| Sony - PlayStation || scph5501.bin || 490f666e1afb15b7362b406ed1cea246 || USA (Can be renamed from scph7003.bin) ||
|-
| Sony - PlayStation || scph5502.bin || 32736f17079d0b2b7024407c39bd3050 || Europe ||
|-
| Sony - PlayStation Portable || ppge_atlas.zim || a93fc411c1ce7d001a2a812643c70085 || Goes under system/PPSSPP/ ||
|}

:Note that most of these BIOSes are not revered engineered releases but binary ROMs ripped from the EEPROM inside of an actual game console system hardware, so it is proprietary binary blobs (precompiled software binaries) which might still be under copyright depending on the console age and origins. It may be that some of those BIOSes are can be seen as Fair use since these game consoles are no longer sold and there is probabably no commercial value of them, but that is something that the XBMC Foundation need to talk about with attorneys about before being able to distributing such BIOS files as resource add-ons or bundled with each libretro core in an official repository.

=== What is a BIOS? ===
A BIOS (Basic Input Output System) is the startup code of a system and is required for certain emulators to work.

=== Where do I place the BIOS files? ===
You will need to place them into the System Directory (linux example for pcsx bios files: ~/.kodi/userdata/addon_data/game.libretro.pcsx-rearmed/system/ ).

Alternatively, you can place the into your Content Directory next to the game you are going to play.

Remember, since Linux is a case sensitive system, you have to rename the BIOS files according to this table so that the libretro cores will be able to find the BIOS files.

=== Why isn’t my BIOS working? ===
# Make sure the BIOS files are placed into the correct directory (see above).
# Make sure they are named correctly so the core can identify them.
# Make sure it’s the correct version/region of a BIOS.
# Make sure your files are not corrupted (bad source, broken download, etc.).
# Make sure to check the log for any errors.

==See also==
* [[Kodi Game|Gaming in Kodi]] - Index of game related articles
** [[Game management]] - A guide to managing game files for and in Kodi
*** [[Game playback controls]] - A guide that describes the player controls and menus for gaming in Kodi
*** [[Game controllers]] - Guides for configuring gamepads and jooystick controllers in Kodi
**[[Game add-ons]]
*** [[Porting Libretro cores to game add-ons]]
**** [[Libretro]]
** [[Game development]] - A guide to developing games for Kodi
** [[Compiling Kodi-Game|Compiling Kodi with RetroPlayer]]
** [[Compiling game add-ons|Compiling existing game add-ons]]

[[Category:RetroPlayer]]
[[Category:Gaming]]

Archive:Game OSD skinning

2018-10-26T12:56:39Z

Gamester17: /* See also */

{{mininav| [[Games]] {{l2| [[Development]] }} }}

<section begin="intro"/>Kodi's in-game OSD (on-screen display) allows the user to control the game, exposes button combos, and offers various settings. Skins compatible with Leia are encouraged to support the game OSD.<section end="intro"/>

== Game OSD documentation ==

[[File:In-game_menu.png|720px|The in-game menu]]

For an overview of how to use the game OSD, see:

* {{big|'''[[Game playback controls]]'''}}

The game OSD is extensively documented in a post on the forum:

* {{big|'''[[https://forum.kodi.tv/showthread.php?tid=336876&pid=2785831#pid2785831 Skinning guide for the game OSD]]'''}}

For general game skinning, see the thread containing the above post:

* {{big|'''[[https://forum.kodi.tv/showthread.php?tid=336876 Skinning games in Kodi Leia]]'''}}

=See also=
* [[Kodi Game|Gaming in Kodi]] - Index of game related articles
** [[Game management]] - A guide to managing game files for and in Kodi
*** [[Game playback controls]] - A guide that describes the player controls and menus for gaming in Kodi
*** [[Game controllers]] - Guides for configuring gamepads and jooystick controllers in Kodi
**[[Game add-ons]]
*** [[Porting Libretro cores to game add-ons]]
**** [[Libretro]]
** [[Game development]] - A guide to developing games for Kodi
** [[Compiling Kodi-Game|Compiling Kodi with RetroPlayer]]
** [[Compiling game add-ons|Compiling existing game add-ons]]

[[Category:Development]]
[[Category:RetroPlayer]]
[[Category:Gaming]]

Game management

2018-10-26T12:55:44Z

Gamester17: /* See also */

{{mininav| [[Games]]}}

= Game library =
Kodi does not have a game-library yet, although one is in development. Currently, games are managed using a basic file browser, and artwork is not yet supported.

To browse local or network files, the source can be added to the Games window. This is similar to how videos and music are added to Kodi. For more information on adding sources, see [[Adding video sources]].

===Game Launchers / Game Browsers===
Game Launchers / Game Browsers (Python script addons for Kodi) can provide a fuller game experience similar to that of a game-library, although configuration is sometimes required.

Note! The versions of Game Launchers / Game Browsers available in Kodi Addon Repository can be outdated. You can find the latest versions in the forum:
* <b>Advanced Emulator Launcher</b> - https://forum.kodi.tv/showthread.php?tid=287826
* <b>Rom Collection Browser</b> - https://forum.kodi.tv/showthread.php?tid=70115

= Game add-ons =
Kodi Gaming (RetroPlayer and Kodi Game API) window supports starting/running both [[libretro]] emulator cores and stand-alone games or emulators that does not use the Libretro API.

===Emulator Cores===
:{{Main|Game add-ons|Libretro}}
Kodi's Game API in the Kodi has a Libretro wrapper which is 1:1 compatibility with the [[libretro]] API, so all libretro cores are valid game add-ons. [[Libretro]] itself is a well defined cross-platform interface to handle the communication between a frontend (Kodi with RetroPlayer) and an Emulator Core (e.g. nestopia).

= Troubleshooting =
If a source is added but no games appear, then you are missing emulators that support your files. This will be fixed when Kodi is able to install emulators from the add-on store.

Alternatively, you can use the latest (experimental) "build" from the lead Kodi developer working on Kodi Games features and functions. These builds are typically an unmodified version of Kodi, but with all emulators installed.

Latest (experimental) builds are available here: https://github.com/garbear/xbmc/releases

==See also==
* [[Kodi Game|Gaming in Kodi]] - Index of game related articles
** [[Game management]] - A guide to managing game files for and in Kodi
*** [[Game playback controls]] - A guide that describes the player controls and menus for gaming in Kodi
*** [[Game controllers]] - Guides for configuring gamepads and jooystick controllers in Kodi
**[[Game add-ons]]
*** [[Porting Libretro cores to game add-ons]]
**** [[Libretro]]
** [[Game development]] - A guide to developing games for Kodi
** [[Compiling Kodi-Game|Compiling Kodi with RetroPlayer]]
** [[Compiling game add-ons|Compiling existing game add-ons]]

{{updated|18}}

[[Category:RetroPlayer]]
[[Category:Gaming]]

Game playback controls

2018-10-26T12:55:20Z

Gamester17: /* See also */

{{mininav| [[Games]]}}

<section begin="intro" />In Kodi, game playback can be controlled similar to movies. Pause, rewind and fast-forward are possible if supported by the emulator.<section end="intro" />

== Button combo reminder ==
Kodi uses button combos inspired by RetroPie (see [https://github.com/RetroPie/RetroPie-Setup/wiki/RetroArch-Configuration#user-content-hotkeys RetroPie documentation]). A reminder is shown the first time a game is played:

[[File:Game_help_message.png|720px|The help dialog]]

To open the game menu, press the buttons on your controller that best match <b>Select + X</b> as they appear on the SNES controller. On modern controllers, the <b>Select</b> button is called <b>Back</b> (Xbox), <b>View</b> (Xbox One), <b>Share</b> (PS4) and various others.

== Button combos ==
Games in Kodi can be controlled with the following button combos:

{| class="wikitable"
!Button combo !! Player action
|-
|<b>Select + X</b> || Pause/resume
|-
|<b>Select + Start</b> || Exit
|-
|<b>Select + Left trigger</b> || Rewind
|-
|<b>Select + Right trigger</b> || Fast-forward
|-
|<b>Select + Right stick</b> || Change volume
|-
|<b>Hold Start</b> || Pause/resume
|}

== In-game menu ==
The in-game menu allows for some basic playback controls and shows the button combos.

[[File:In-game_menu.png|720px|The in-game menu]]

== Gameplay settings ==
The Settings menu lets you control video, audio, input and emulator tweaks.

[[File:Game_settings_menu.png|720px|The game settings menu]]

=See also=
* [[Kodi Game|Gaming in Kodi]] - Index of game related articles
** [[Game management]] - A guide to managing game files for and in Kodi
*** [[Game playback controls]] - A guide that describes the player controls and menus for gaming in Kodi
*** [[Game controllers]] - Guides for configuring gamepads and jooystick controllers in Kodi
**[[Game add-ons]]
*** [[Porting Libretro cores to game add-ons]]
**** [[Libretro]]
** [[Game development]] - A guide to developing games for Kodi
** [[Compiling Kodi-Game|Compiling Kodi with RetroPlayer]]
** [[Compiling game add-ons|Compiling existing game add-ons]]

{{updated|18}}

[[Category:RetroPlayer]]
[[Category:Gaming]]

Game controllers

2018-10-26T12:54:47Z

Gamester17: /* See also */

{{mininav| [[Remote controls]] {{l2| [[Games]] }} }}
{{mininav| [[Kodi Game]] }}

<section begin="intro" />{{Kodi}} can use several different types of game controllers, gamepads, joysticks, and other game input devices.<section end="intro" />

== General guides ==
Once your controller is recognized by Kodi, follow this guide to configure the physical layout:
* {{big|'''[[HOW-TO:Configure controllers]]'''}}

Once your controller's layout is configured, you can change the Kodi actions for each button:
* {{big|'''[[HOW-TO:Modify joystick.xml]]'''}}

Now that your controller is working, share your button map with the world!
* {{big|'''[[HOW-TO:Share button maps]]'''}}

If you are using a version of Kodi that includes [[Emulators]], you can map each game platform separately:
* {{big|'''[[HOW-TO:Map multiple controllers]]'''}}

== Controller instructions ==
If your controller is not recognized by Kodi, follow the HOW-TO for your controller and operating system:

=== Windows ===
* {{big|'''[[HOW-TO:NVIDIA SHIELD controller on Windows 7]]'''}}
* {{big|'''[[HOW-TO:Wireless Xbox 360 controller on Windows 7]]'''}}
* {{big|'''HOW-TO:Fix iMON devices on Windows'''}}

=== Linux ===
* {{big|'''[[HOW-TO:X-Arcade Tankstick]]'''}}

=== PlayStation 4 controller ===
* {{big|'''[[HOW-TO:PlayStation 4 controller]]'''}}

=== NVidia Shield controller ===
* {{big|'''[[HOW-TO:Fix new controller dialog]]'''}}
* {{big|'''[[HOW-TO:Fix double button presses]]'''}}

== Troubleshooting ==
If buttons are being skipped while mapping your controller, you can try the solutions in this HOW-TO:
* {{big|'''[[HOW-TO:Fix buttons skipped while mapping]]'''}}

Krypton v17.0 has a bug where analog sticks get "stuck" ([https://github.com/xbmc/xbmc/pull/11571 fixed] in v17.1):
* {{big|'''[[HOW-TO:Fix stuck analog sticks on v17.0]]'''}}

If Kodi is started without the correct version of joystick support:
* {{big|'''[[HOW-TO:Fix Joystick Support error on startup]]'''}}

To disable joystick support entirely:
* {{big|'''HOW-TO:Disable Joystick Support'''}}

==See also==
* [[Remote controls]]
* [[Kodi Game|Gaming in Kodi]] - Index of game related articles
** [[Game management]] - A guide to managing game files for and in Kodi
*** [[Game playback controls]] - A guide that describes the player controls and menus for gaming in Kodi
*** [[Game controllers]] - Guides for configuring gamepads and jooystick controllers in Kodi
**[[Game add-ons]]
*** [[Porting Libretro cores to game add-ons]]
**** [[Libretro]]
** [[Game development]] - A guide to developing games for Kodi
** [[Compiling Kodi-Game|Compiling Kodi with RetroPlayer]]
** [[Compiling game add-ons|Compiling existing game add-ons]]

[[Category:Remotes]]
[[Category:RetroPlayer]]
[[Category:Gaming]]
[[Category:Manual]]

Game development

2018-10-26T12:54:19Z

Gamester17: /* See also */

{{mininav| [[Games]] {{l2| [[Development]] }} }}
{{mininav| [[Kodi Game]] }}

This page is about Kodi-Game branch of Kodi which tries to implement a gaming environment for Kodi. The goal is to start, stop and play video games like you can currently play video files. Kodi-Game constist of several addons and subsystems which should be described on this page to minimize confusion. The current [[development builds]] are based on Kodi 17 (Krypton) and introduces a lot of changes, and for this reason the information you can find on the forum and here in the wiki might be outdates and may not apply. Official repository is on [https://github.com/kodi-game github].

A related topic is [[Game OSD skinning]].

== End-users (non-programmers) ==
You are probably reading this because you would like to download a finished Kodi application or complete OpenELEC image with nice out-of-the-box experience. We are sorry but such build does not yet exist at the moment. This page will be updated with links to available builds if and when such release become available.

You can help still help if you are a more experienced computer user and are able to compile Kodi-Game branch yourself, please see the developers sections below. Also, spread the word about this project to your friends and family, we are sure they will enjoy it too as it matures.

== Developers (programmers) ==
If you are a C/C++ developer and like to help then great! Please checkout the [[Compiling Kodi-Game]], [[Compiling Game Add-ons]], and [[Porting Libretro cores to Game Add-ons]] articles to get started. Currently this build instruction is for Linux operating-systems on x86/x86-64 based hardware only.

You should be proficient in [http://en.wikipedia.org/wiki/Programming_language C/C++ programming language], and although not really required knowledge of [http://en.wikipedia.org/wiki/OpenGL OpenGL] or other [http://en.wikipedia.org/wiki/Multimedia multimedia] programming is a plus, as well as prior [http://en.wikipedia.org/wiki/Multi-platform cross-platform] or [http://en.wikipedia.org/wiki/Porting porting] development experience.

== Technical Overview ==
Kodi Game is the project name for all infrastructure changes which need to be made in the Kodi source code. This work also includes a highly modified input system ready for gaming requirements.

=== RetroPlayer ===
RetroPlayer is a new player core for Kodi Entertainment Center. It is similar to the video player and audio visualizer, but it plays games instead of movies and music. Player core that plays games using game add-ons. Despite its name, it can play all types of games, not just retro ones. Games can be paused, fast-forwarded, and rewound in realtime. Save states are created similar to bookmarks, allowing for quick browsing of the game's play history. 3D support (for N64, etc) is being worked on.

=== Game API ===
Game API ?

=== Game Add-ons ===
Stand-alone games or emulators that does not use the Libretro API. Possible examples could be, Nvidia GameStream via Limelight or WINE capture could possible through the Game API.

=== Libretro API===
:{{Main|Libretro}}
Libretro is a C-based interface between user-facing frontends and emulator backends. This frontend and backend concept allow several different (non-Kodi) frontend projects to use the same Libretro core emulators.<ref>http://forum.kodi.tv/showthread.php?tid=292270</ref>

Kodi's Game API has Libretro Wrapper which is 1:1 compatibility with the libretro API, so all libretro cores are valid game add-ons. Libretro itself is a well defined interface to handle the communication between a frontend (Kodi with RetroPlayer) and an Emulator Core (e.g. nestopia).

By ultilizing libretro, the Kodi Game project will also become a part of the larger software ecosystem based around libretro, this a other third-party projects use libretro as well as all to some degree collaborage and share code with upstream libretro.

==== Libretro Cores ====
An Emulator Core for Libretro API ([http://www.libretro.com/ www.libretro.com]) that does the actual work of emulating a system. Due to the common Libretro API interface it is possible to re-use good working and well tested emulators for the RetroPlayer platform. Every emulator that supports libretro will be relatively easily to integrate once the project matures.

=== Peripheral API ===
A way to interface DIY hardware with Kodi. Currently game controllers, and in the future also media readers for cartridge adapters.

=== Peripheral Add-ons ===
The peripheral add-ons provides access to many joystick and gamepad interfaces across various platforms. An input addon is used to map the buttons/axis on your physical input device, to the buttons/axis of your virtual system. This is necessary because different retro systems usually have different button layouts. A controller configuration utility is also in the works.

== Subsystem Architecture ==

*Game API - ?
**Game Client Addons - ?
**Libretro Wrapper - ?
*Hardware API - ?
** Peripheral API - ?
*** Peripheral Add-ons - ?
*** Peripheral Buses - ?
*** Input Library - ?
** Media Readers API - ?
** Input API - ?
*RetroPlayer - ?
** RetroPlayer Savegames - ?
====Architecture development discussions:====
* [http://forum.kodi.tv/showthread.php?tid=195552 Fitting RetroPlayer into Kodi]
* [http://forum.kodi.tv/showthread.php?tid=225126 Peripheral Input Documentation]
* [http://forum.kodi.tv/showthread.php?tid=224328 Porting Libretro cores to Kodi]
* [http://forum.kodi.tv/showthread.php?tid=211138 New input API discussion]

== Game add-ons ==
* [[Game Add-ons|Existing ported Game Add-ons]]
* [[Compiling Game Add-ons|Compiling existing Game Add-ons]]
* [[Porting Libretro cores to Game Add-ons]]
** [[Libretro]]

== Communication: ==
*freenode irc: #kodi-game
*kodi forum: http://forum.kodi.tv/forumdisplay.php?fid=194

== FAQ for Kodi-Game branch==
Common questions and answers regarding testing and development of Kodi-Game branch.

=== Mupen64plus (n64) is not working ===
Mupen64plus and some other emulators (such as PSP, Dolphin) requires OpenGL / OpenGL ES rendering extensions to libretro which is currently not implemented in the current upstream kodi-game branch. See [https://github.com/a1rwulf/xbmc a1rwulf's] repository for his "retrogl" implementations if you would like to help the work being done for these systems.

=== Is it possible to support system X on platform Y ===
Kodi Game branch includes a wrapper for [http://www.libretro.com/ libretro] to emulate multiple systems via emulator cores for its common libretro API. The current support matrix can be found in the [[Game add-ons]] wiki article.

=See also=
* [[Kodi Game|Gaming in Kodi]] - Index of game related articles
** [[Game management]] - A guide to managing game files for and in Kodi
*** [[Game playback controls]] - A guide that describes the player controls and menus for gaming in Kodi
*** [[Game controllers]] - Guides for configuring gamepads and jooystick controllers in Kodi
**[[Game add-ons]]
*** [[Porting Libretro cores to game add-ons]]
**** [[Libretro]]
** [[Game development]] - A guide to developing games for Kodi
** [[Compiling Kodi-Game|Compiling Kodi with RetroPlayer]]
** [[Compiling game add-ons|Compiling existing game add-ons]]

=External Links=
* [http://www.libretro.com/ Libretro]

[[Category:Development]]
[[Category:RetroPlayer]]
[[Category:Gaming]]

== References ==
<references/>

Compiling Kodi-Game

2018-10-26T12:53:57Z

Gamester17: /* See also */

{{mininav| [[Kodi Game]] }}

This tutorial will show you the necessary steps to compile and run with RetroPlayer from the Kodi-Game branch on an Ubuntu system.

== Where do I start on Linux? ==
General and distribution specific guides on HOW-TO compile Kodi for Linux from source code is available in this whis, and there is also an up-to-date README for Ubuntu Linux available in the [https://github.com/xbmc/xbmc XBMC Foundation git repo on GitHub].

The recommended '''Linux development platform''' is currently [[HOW-TO compile XBMC for Linux from source code|32-bit Ubuntu Desktop (for x86)]]. The code can be obtained by cloning the xbmc [http://git-scm.com/ git] repository hosted on [https://github.com/garbear/xbmc Github]. First use your package manager to install git on your system and then execute the following command to clone your own repository: <br />
<br /><code>
git clone git://github.com/garbear/xbmc.git
</code><br />
<br />
After the clone has completed, follow the compilation/development guide in the new repository ([[HOW-TO compile XBMC for Linux from source code|README.linux]]) to setup the required packages and so on. Team Kodi developers opinion is that the best thing to start with is just to take a look through the source code and try to understand how it all fits together. Test things out, find what works and what does not, then try and track down why.

Alternatively, you can [https://www.virtualbox.org/wiki/Downloads download VirtualBox] and follow this guide to install the required software: [[HOW-TO compile XBMC for Linux from source code|Ubuntu Desktop (32-bit for x86)]]. Besides from KDevelop, additional development tools that can be useful include Subcommander, Doxygen, Sysprof and PowerTop.

The performance of a virtual machine is not great as there is no 2D or 3D hardware acceleration support under a virtual machine, however it should work good enough to get a lot of development tasks done. Nice is also that you can install/run [https://www.virtualbox.org/ VirtualBox] on Windows, OS X and Linux. The free VirtualBox also enables you to share data seamlessly between the virtual machine and host computer, and also allows you to directly access USB 2.0 devices from within the virtual machine. To improve the performance of your virtual machine, you can increase the number of cores on a multi-core system that is assigned to your virtual machine.

== Compiling Kodi-Game branch and binary game add-ons ==
Start by following the steps in the [[HOW-TO:Compile_Kodi_for_Linux|Kodi compile HOWTO]]. The only difference is you will need to clone the RetroPlayer branch

<source lang="bash">
git clone https://github.com/garbear/xbmc.git
</source>

It is recommended that you build add-ons out-of-tree (other compiling options are available [https://github.com/kodi-game/game.libretro here]).

<source lang="bash">
mkdir binary-addons
cd binary-addons

cmake -DADDONS_TO_BUILD="peripheral.joystick game.libretro game.libretro.nestopia" \
-DCMAKE_BUILD_TYPE=Debug \
-DCMAKE_INSTALL_PREFIX=$HOME/workspace/xbmc/addons \
-DPACKAGE_ZIP=1 \
$HOME/workspace/xbmc/project/cmake/addons

make
</source>

== Run Kodi ==
Until button map data has been gathered, input needs to be configured manually. Execute <code>ActivateWindow(GameControllers)</code> (which is mapped to "t" until the window can be launched from the GUI).

[[File:Controller_configuration_utility.jpg|thumb|600px|left|Controller configuration utility]]

<div style="clear: both"></div>

From here, choose a controller, choose a button, and then press the key, button, or trigger that should map to the button. To control Kodi with a physical controller, it will need to be mapped to the "Default" controller. To control NES emulators, the keyboard or controller needs to be mapped to the "NES" controller in the configuration utility.

[[File:Mapping a button.jpg|thumb|600px|left|Mapping a button]]

<div style="clear: both"></div>

Once you have mapped a keyboard or controller to an emulator's platform's controller, you can control that emulator.

If you have troubles following this guide please write to the [http://forum.kodi.tv/forumdisplay.php?fid=194 forum] or ask for help in the #kodi-game IRC channel. This page will then be updated to be more helpful.

=See also=
* [[Kodi Game|Gaming in Kodi]] - Index of game related articles
** [[Game management]] - A guide to managing game files for and in Kodi
*** [[Game playback controls]] - A guide that describes the player controls and menus for gaming in Kodi
*** [[Game controllers]] - Guides for configuring gamepads and jooystick controllers in Kodi
**[[Game add-ons]]
*** [[Porting Libretro cores to game add-ons]]
**** [[Libretro]]
** [[Game development]] - A guide to developing games for Kodi
** [[Compiling Kodi-Game|Compiling Kodi with RetroPlayer]]
** [[Compiling game add-ons|Compiling existing game add-ons]]

[[Category:Development]]
[[Category:RetroPlayer]]
[[Category:Gaming]]

Porting Libretro cores to game add-ons

2018-10-26T12:53:17Z

Gamester17: /* See also */

{{mininav| [[Kodi Game]] }}

This tutorial will show you the necessary steps to port Libretro cores into [[Game Add-ons]] on an Ubuntu Linux system for the new Game API made available in [[Kodi Game|Kodi Game branch]].

* ''For how to compiling existing Game Add-ons for Kodi see [[Compiling Game Add-ons]], and for compiling Kodi Game branch itself see the [[Compiling Kodi-Game]] article''.

= Porting libretro cores to Kodi =
:{{Main|Libretro}}
* ? Can 'someone' with developer skills please copy instructions from http://forum.kodi.tv/showthread.php?tid=224328 to this wiki page?

=See also=
* [[Kodi Game|Gaming in Kodi]] - Index of game related articles
** [[Game management]] - A guide to managing game files for and in Kodi
*** [[Game playback controls]] - A guide that describes the player controls and menus for gaming in Kodi
*** [[Game controllers]] - Guides for configuring gamepads and jooystick controllers in Kodi
**[[Game add-ons]]
*** [[Porting Libretro cores to game add-ons]]
**** [[Libretro]]
** [[Game development]] - A guide to developing games for Kodi
** [[Compiling Kodi-Game|Compiling Kodi with RetroPlayer]]
** [[Compiling game add-ons|Compiling existing game add-ons]]

[[Category:Development]]
[[Category:RetroPlayer]]
[[Category:Gaming]]

Libretro

2018-10-26T12:53:00Z

Gamester17: /* See also */

{{mininav| [[Kodi Game]] }}

Kodi's Game API has Libretro Wrapper which is 1:1 compatibility with the libretro API, and all libretro cores can be ported game add-ons for Kodi. Libretro itself is a well defined cross-platform platform interface to handle the communication between a frontend (Kodi with RetroPlayer) and an Emulator Core (e.g. nestopia). Kodi uses libretro but libretro is its own seperate open source project developed by independent developers.

:{{Main|Game add-ons|Game development}}

For more detailed information about libretro please visit their website at:
* https://www.libretro.com/index.php/api/

=What is libretro?=
Download the [http://www.libretro.com/wp-content/uploads/2014/03/RetroArch-Libretro-Technical-Brochure.pdf RetroArch/Libretro Technical Brochure (PDF) from libretro.org website]

Libretro is a simple lightweight C/C++ API that allows for the creation of games and emulators. It is very simple in nature, yet very powerful. The simplicity of it all requires some explanation in order to truly grasp how useful it can be to your own projects. It works according to backend/frontend principle. Backend application talks with frontend by way of API. Facilitates input/audio/video/camera/location streams for use in games/media-players/graphics applications. With added value (shaders, rewinding, input support, etc).

When you choose to use the libretro API, your program gets turned into a single library file (called a ‘libretro core’). A frontend that supports the libretro API can then load that library file and run the app. The frontend’s responsibility is to provide all the implementation-specific details, such as video/audio/input drivers. The libretro core’s responsibility is solely to provide the main program. You therefore don’t have to worry about writing different video drivers for Direct3D, OpenGL or worrying about catering to all possible input APIs/sound APIs/supporting all known joypads/etc. This is none of your concern at the libretro core implementation level.

Any project that is ported to work with this API can be made to run on ANY libretro frontend – now and forever. You maintain a single codebase that only deals with the main program, and you then target one single API (libretro) in order to port your program over to multiple platforms at once.

Other projects benefit from our ever-expanding libretro core software library by implementing the libretro API inside their own projects. To this end, project such as Kodi (XBMC Foundation) have written a libretro wrapper/driver which follows the same concept as the reference libretro frontend, RetroArch.

Kodi's (with RetroPlayer) is frontend for Libretro. RetroArch is the official reference frontend, and it is only for gaming and is meant to be fast, simple, yet powerful, and is available on nearly all modern-day platforms. Other third-party platform-specific frontends for Libretro are currently in development, including Arcan and Minir. For more checkout: https://www.libretro.com/index.php/powered-by-libretro/

=Who Uses Libretro?=
While the most common use case for libretro has been console emulation, it is equally suited as a platform for almost any 2D game. For example, the NX Engine used in the popular freeware game Cave Story has been successfully ported to libretro, open sourced games like Quake and Doom have been ported to libretro, and the new freeware game Dinothawr supports libretro natively.

=Libretro GL/GLES/Vulkan=
Aside from retro-style games and emulators that depend on software rendering and where you’d typically need nothing more than the ability to render to a framebuffer, the Libretro API also allows you to target OpenGL, OpenGL ES (GLES), and Vulkan. This allows you to create libretro ports that use OpenGL, OpenGL ES (GLES), or Vulkanas part of their internal rendering.

From a portability perspective, we highly recommend that you try to target both so that your libretro GL port will work on both mobile (OpenGL ES) and desktop (OpenGL) computers.

=Why Should Developers Target Libretro?=
Software that targets the libretro API instantly gains access to all of the platforms that have libretro frontends available. That means your game is immediately available to those platforms’ users without worrying about input/audio/video drivers, compatibility issues or the myriad quirks of the underlying host system(s). Likewise, there’s no need to write specialized GUI code for each platform or to use esoteric–and often buggy–cross-platform toolkits, like Qt and GTK+.

Furthermore, once your game supports libretro, all of the libretro frontends’ other features come along for free, such as RetroArch’s real-time rewind, lag-concealing netplay, lossless video recording/streaming and cutting-edge post-processing shader support.

Perhaps best of all: libretro is an open specification that is 100% free to implement, with no licensing fees or hidden strings attached.

If you’d like to learn more about libretro, leave us a comment or chat with us on IRC at #retroarch on Freenode.

=Libretro’s design goals=

Libretro is the library programming interface. Programs get ported to this library and can then be run with any libretro-compatible frontend.

Our reference frontend is RetroArch. The two projects are not the same, and this is reflected in the licensing as well. RetroArch sticks to GPL version 3 whereas the libretro API is a MIT-licensed API.

===Some of the design goals for libretro===
: * Allow a non-kitchensink approach to crossplatform portability.
: * Allow a non-dependency heavy approach to crossplatform portability. Stick to just one header containing definitions for the necessary audio/video/input callbacks.
: * Care about being backwards compatible. Libretro’s ABI( Application Binary Interface) has never been broken in years, and old libretro frontends from years ago in most cases can still use libretro cores being created today.
: * By its very design enables programs to be ported to singular dynamic libraries which can then be loaded in and out of frontend applications thanks to the libretro API.
: * Forces you by its design to rethink what code belongs to ‘core land’ and what should belong to ‘frontend land’. Libretro cores ideally should have minimal to no dependencies on any system/OS-specific APIs so that the same libretro cores can work on any libretro-compatible frontend.
: * Designed with games, emulators and multimedia in mind. Libretro core ports resemble ports being done to standalone game consoles or mobile where the primary input device is not a keyboard and mouse (although libretro supports those as well).
: * Does not concern itself with external WIMP GUIs (since they are not portable), or anything that would tie itself to mainly desktop PC-usage. Libretro cores ideally have to work seamlessly on mobile, desktop PC and game consoles.
: * Requires you to link your libretro-ported program to a libretro frontend, leaves the libretro frontend creation part up to you or lets you select one of the mature libretro frontends already available.

=See also=
* [[Kodi Game|Gaming in Kodi]] - Index of game related articles
** [[Game management]] - A guide to managing game files for and in Kodi
*** [[Game playback controls]] - A guide that describes the player controls and menus for gaming in Kodi
**[[Game add-ons]]
*** [[Porting Libretro cores to game add-ons]]
**** [[Libretro]]
*** [[Game controllers]] - Guides for configuring gamepads and jooystick controllers in Kodi
** [[Game development]] - A guide to developing games for Kodi
** [[Compiling Kodi-Game|Compiling Kodi with RetroPlayer]]
** [[Compiling game add-ons|Compiling existing game add-ons]]

=External Links=
* [http://www.libretro.com/ Libretro]

[[Category:Development]]
[[Category:RetroPlayer]]
[[Category:Gaming]]

Games

2018-10-26T12:50:55Z

Gamester17:

{{mininav | [[Main page]]}}

Kodi v18 (Leia) and later features a "Games" window/section in the GUI from which you can launch and run games, including [[libretro]]-compatible [[Game add-ons]] which can run some games and a lot of different retro game-emulators natively from inside Kodi. New is also many an input manager with many game controller settings for configuring gamepads, joysticks, keyboards, and mouses, for use inside those games/emulators that are running natively inside Kodi's runtime.
== Topic navigation ==

{{Index two column
| image 1 = Book icon 1.png
| link 1 = Game_management
| link name 1 = Game Management
| description 1 = A guide to managing game files

| image 2 = Oxygen480-actions-media-playback-start.png
| link 2 = Game_playback_controls
| link name 2 = Game Playback Controls
| description 2 = A guide that describes the player controls and menus

| image 3 = Search blue.png
| link 3 = :Category:Gaming
| link name 3 = Index of game articles
| description 3 = A listing of game-related pages

| image 4 = Nuvola apps kthememgr.png
| link 4 = Game add-ons
| link name 4 = Game add-ons
| description 4 = Game add-ons for Kodi

| image 5 = Administration.png
| link 5 = Game_development
| link name 5 = Game Development
| description 5 = A guide to developing games in Kodi

| image 6 = Gamepad.svg
| link 6 = Game_controllers
| link name 6 = Game Controllers
| description 6 = Guides for configuring controllers
}}

{{updated|18}}

[[Category:Index]]
[[Category:Manual]]
[[Category:General topics]]
[[Category:RetroPlayer]]
[[Category:Gaming]]

Games

2018-10-26T12:50:13Z

Gamester17:

{{mininav | [[Main page]]}}

Kodi v18 (Leia) and later features a "Games" window/section from which you can launch and run games, including [[libretro]]-compatible [[Game add-ons]] which can run some games and a lot of different retro game-emulators natively from inside Kodi. New is also many an input manager with many game controller settings for configuring gamepads, joysticks, keyboards, and mouses, for use inside those games/emulators that are running natively inside Kodi's runtime.
== Topic navigation ==

{{Index two column
| image 1 = Book icon 1.png
| link 1 = Game_management
| link name 1 = Game Management
| description 1 = A guide to managing game files

| image 2 = Oxygen480-actions-media-playback-start.png
| link 2 = Game_playback_controls
| link name 2 = Game Playback Controls
| description 2 = A guide that describes the player controls and menus

| image 3 = Search blue.png
| link 3 = :Category:Gaming
| link name 3 = Index of game articles
| description 3 = A listing of game-related pages

| image 4 = Nuvola apps kthememgr.png
| link 4 = Game add-ons
| link name 4 = Game add-ons
| description 4 = Game add-ons for Kodi

| image 5 = Administration.png
| link 5 = Game_development
| link name 5 = Game Development
| description 5 = A guide to developing games in Kodi

| image 6 = Gamepad.svg
| link 6 = Game_controllers
| link name 6 = Game Controllers
| description 6 = Guides for configuring controllers
}}

{{updated|18}}

[[Category:Index]]
[[Category:Manual]]
[[Category:General topics]]
[[Category:RetroPlayer]]
[[Category:Gaming]]

Libretro

2018-10-26T12:40:31Z

Gamester17: /* What is libretro? */

{{mininav| [[Kodi Game]] }}

Kodi's Game API has Libretro Wrapper which is 1:1 compatibility with the libretro API, and all libretro cores can be ported game add-ons for Kodi. Libretro itself is a well defined cross-platform platform interface to handle the communication between a frontend (Kodi with RetroPlayer) and an Emulator Core (e.g. nestopia). Kodi uses libretro but libretro is its own seperate open source project developed by independent developers.

:{{Main|Game add-ons|Game development}}

For more detailed information about libretro please visit their website at:
* https://www.libretro.com/index.php/api/

=What is libretro?=
Download the [http://www.libretro.com/wp-content/uploads/2014/03/RetroArch-Libretro-Technical-Brochure.pdf RetroArch/Libretro Technical Brochure (PDF) from libretro.org website]

Libretro is a simple lightweight C/C++ API that allows for the creation of games and emulators. It is very simple in nature, yet very powerful. The simplicity of it all requires some explanation in order to truly grasp how useful it can be to your own projects. It works according to backend/frontend principle. Backend application talks with frontend by way of API. Facilitates input/audio/video/camera/location streams for use in games/media-players/graphics applications. With added value (shaders, rewinding, input support, etc).

When you choose to use the libretro API, your program gets turned into a single library file (called a ‘libretro core’). A frontend that supports the libretro API can then load that library file and run the app. The frontend’s responsibility is to provide all the implementation-specific details, such as video/audio/input drivers. The libretro core’s responsibility is solely to provide the main program. You therefore don’t have to worry about writing different video drivers for Direct3D, OpenGL or worrying about catering to all possible input APIs/sound APIs/supporting all known joypads/etc. This is none of your concern at the libretro core implementation level.

Any project that is ported to work with this API can be made to run on ANY libretro frontend – now and forever. You maintain a single codebase that only deals with the main program, and you then target one single API (libretro) in order to port your program over to multiple platforms at once.

Other projects benefit from our ever-expanding libretro core software library by implementing the libretro API inside their own projects. To this end, project such as Kodi (XBMC Foundation) have written a libretro wrapper/driver which follows the same concept as the reference libretro frontend, RetroArch.

Kodi's (with RetroPlayer) is frontend for Libretro. RetroArch is the official reference frontend, and it is only for gaming and is meant to be fast, simple, yet powerful, and is available on nearly all modern-day platforms. Other third-party platform-specific frontends for Libretro are currently in development, including Arcan and Minir. For more checkout: https://www.libretro.com/index.php/powered-by-libretro/

=Who Uses Libretro?=
While the most common use case for libretro has been console emulation, it is equally suited as a platform for almost any 2D game. For example, the NX Engine used in the popular freeware game Cave Story has been successfully ported to libretro, open sourced games like Quake and Doom have been ported to libretro, and the new freeware game Dinothawr supports libretro natively.

=Libretro GL/GLES/Vulkan=
Aside from retro-style games and emulators that depend on software rendering and where you’d typically need nothing more than the ability to render to a framebuffer, the Libretro API also allows you to target OpenGL, OpenGL ES (GLES), and Vulkan. This allows you to create libretro ports that use OpenGL, OpenGL ES (GLES), or Vulkanas part of their internal rendering.

From a portability perspective, we highly recommend that you try to target both so that your libretro GL port will work on both mobile (OpenGL ES) and desktop (OpenGL) computers.

=Why Should Developers Target Libretro?=
Software that targets the libretro API instantly gains access to all of the platforms that have libretro frontends available. That means your game is immediately available to those platforms’ users without worrying about input/audio/video drivers, compatibility issues or the myriad quirks of the underlying host system(s). Likewise, there’s no need to write specialized GUI code for each platform or to use esoteric–and often buggy–cross-platform toolkits, like Qt and GTK+.

Furthermore, once your game supports libretro, all of the libretro frontends’ other features come along for free, such as RetroArch’s real-time rewind, lag-concealing netplay, lossless video recording/streaming and cutting-edge post-processing shader support.

Perhaps best of all: libretro is an open specification that is 100% free to implement, with no licensing fees or hidden strings attached.

If you’d like to learn more about libretro, leave us a comment or chat with us on IRC at #retroarch on Freenode.

=Libretro’s design goals=

Libretro is the library programming interface. Programs get ported to this library and can then be run with any libretro-compatible frontend.

Our reference frontend is RetroArch. The two projects are not the same, and this is reflected in the licensing as well. RetroArch sticks to GPL version 3 whereas the libretro API is a MIT-licensed API.

===Some of the design goals for libretro===
: * Allow a non-kitchensink approach to crossplatform portability.
: * Allow a non-dependency heavy approach to crossplatform portability. Stick to just one header containing definitions for the necessary audio/video/input callbacks.
: * Care about being backwards compatible. Libretro’s ABI( Application Binary Interface) has never been broken in years, and old libretro frontends from years ago in most cases can still use libretro cores being created today.
: * By its very design enables programs to be ported to singular dynamic libraries which can then be loaded in and out of frontend applications thanks to the libretro API.
: * Forces you by its design to rethink what code belongs to ‘core land’ and what should belong to ‘frontend land’. Libretro cores ideally should have minimal to no dependencies on any system/OS-specific APIs so that the same libretro cores can work on any libretro-compatible frontend.
: * Designed with games, emulators and multimedia in mind. Libretro core ports resemble ports being done to standalone game consoles or mobile where the primary input device is not a keyboard and mouse (although libretro supports those as well).
: * Does not concern itself with external WIMP GUIs (since they are not portable), or anything that would tie itself to mainly desktop PC-usage. Libretro cores ideally have to work seamlessly on mobile, desktop PC and game consoles.
: * Requires you to link your libretro-ported program to a libretro frontend, leaves the libretro frontend creation part up to you or lets you select one of the mature libretro frontends already available.

=See also=
* [[Kodi Game|Gaming in Kodi]] - Index of game related articles
** [[Game management]] - A guide to managing game files for and in Kodi
*** [[Game playback controls]] - A guide that describes the player controls and menus for gaming in Kodi
*** [[Game controllers]] - Guides for configuring gamepads and jooystick controllers in Kodi
** [[Game development]] - A guide to developing games for Kodi
** [[Compiling Kodi-Game|Compiling Kodi with RetroPlayer]]
** [[Compiling game add-ons|Compiling existing game add-ons]]
** [[Porting Libretro cores to game add-ons]]

=External Links=
* [http://www.libretro.com/ Libretro]

[[Category:Development]]
[[Category:RetroPlayer]]
[[Category:Gaming]]

Libretro

2018-10-26T12:39:59Z

Gamester17: /* What is libretro? */

{{mininav| [[Kodi Game]] }}

Kodi's Game API has Libretro Wrapper which is 1:1 compatibility with the libretro API, and all libretro cores can be ported game add-ons for Kodi. Libretro itself is a well defined cross-platform platform interface to handle the communication between a frontend (Kodi with RetroPlayer) and an Emulator Core (e.g. nestopia). Kodi uses libretro but libretro is its own seperate open source project developed by independent developers.

:{{Main|Game add-ons|Game development}}

For more detailed information about libretro please visit their website at:
* https://www.libretro.com/index.php/api/

=What is libretro?=
Download the [http://www.libretro.com/wp-content/uploads/2014/03/RetroArch-Libretro-Technical-Brochure.pdf RetroArch/Libretro Technical Brochure (PDF) from libretro.org website]

Libretro is a simple lightweight C/C++ API that allows for the creation of games and emulators. It is very simple in nature, yet very powerful. The simplicity of it all requires some explanation in order to truly grasp how useful it can be to your own projects. It works according to backend/frontend principle. Backend application talks with frontend by way of API. Facilitates input/audio/video/camera/location streams for use in games/media-players/graphics applications. With added value (shaders, rewinding, input support, etc).

When you choose to use the libretro API, your program gets turned into a single library file (called a ‘libretro core’). A frontend that supports the libretro API can then load that library file and run the app. The frontend’s responsibility is to provide all the implementation-specific details, such as video/audio/input drivers. The libretro core’s responsibility is solely to provide the main program. You therefore don’t have to worry about writing different video drivers for Direct3D, OpenGL or worrying about catering to all possible input APIs/sound APIs/supporting all known joypads/etc. This is none of your concern at the libretro core implementation level.

Any project that is ported to work with this API can be made to run on ANY libretro frontend – now and forever. You maintain a single codebase that only deals with the main program, and you then target one single API (libretro) in order to port your program over to multiple platforms at once.

Other projects benefit from our ever-expanding libretro core software library by implementing the libretro API inside their own projects. To this end, project such as Kodi (XBMC Foundation) have written a libretro driver which follows the same concept as the reference libretro frontend, RetroArch.

Kodi's (with RetroPlayer) is frontend for Libretro. RetroArch is the official reference frontend, and it is only for gaming and is meant to be fast, simple, yet powerful, and is available on nearly all modern-day platforms. Other third-party platform-specific frontends for Libretro are currently in development, including Arcan and Minir. For more checkout: https://www.libretro.com/index.php/powered-by-libretro/

=Who Uses Libretro?=
While the most common use case for libretro has been console emulation, it is equally suited as a platform for almost any 2D game. For example, the NX Engine used in the popular freeware game Cave Story has been successfully ported to libretro, open sourced games like Quake and Doom have been ported to libretro, and the new freeware game Dinothawr supports libretro natively.

=Libretro GL/GLES/Vulkan=
Aside from retro-style games and emulators that depend on software rendering and where you’d typically need nothing more than the ability to render to a framebuffer, the Libretro API also allows you to target OpenGL, OpenGL ES (GLES), and Vulkan. This allows you to create libretro ports that use OpenGL, OpenGL ES (GLES), or Vulkanas part of their internal rendering.

From a portability perspective, we highly recommend that you try to target both so that your libretro GL port will work on both mobile (OpenGL ES) and desktop (OpenGL) computers.

=Why Should Developers Target Libretro?=
Software that targets the libretro API instantly gains access to all of the platforms that have libretro frontends available. That means your game is immediately available to those platforms’ users without worrying about input/audio/video drivers, compatibility issues or the myriad quirks of the underlying host system(s). Likewise, there’s no need to write specialized GUI code for each platform or to use esoteric–and often buggy–cross-platform toolkits, like Qt and GTK+.

Furthermore, once your game supports libretro, all of the libretro frontends’ other features come along for free, such as RetroArch’s real-time rewind, lag-concealing netplay, lossless video recording/streaming and cutting-edge post-processing shader support.

Perhaps best of all: libretro is an open specification that is 100% free to implement, with no licensing fees or hidden strings attached.

If you’d like to learn more about libretro, leave us a comment or chat with us on IRC at #retroarch on Freenode.

=Libretro’s design goals=

Libretro is the library programming interface. Programs get ported to this library and can then be run with any libretro-compatible frontend.

Our reference frontend is RetroArch. The two projects are not the same, and this is reflected in the licensing as well. RetroArch sticks to GPL version 3 whereas the libretro API is a MIT-licensed API.

===Some of the design goals for libretro===
: * Allow a non-kitchensink approach to crossplatform portability.
: * Allow a non-dependency heavy approach to crossplatform portability. Stick to just one header containing definitions for the necessary audio/video/input callbacks.
: * Care about being backwards compatible. Libretro’s ABI( Application Binary Interface) has never been broken in years, and old libretro frontends from years ago in most cases can still use libretro cores being created today.
: * By its very design enables programs to be ported to singular dynamic libraries which can then be loaded in and out of frontend applications thanks to the libretro API.
: * Forces you by its design to rethink what code belongs to ‘core land’ and what should belong to ‘frontend land’. Libretro cores ideally should have minimal to no dependencies on any system/OS-specific APIs so that the same libretro cores can work on any libretro-compatible frontend.
: * Designed with games, emulators and multimedia in mind. Libretro core ports resemble ports being done to standalone game consoles or mobile where the primary input device is not a keyboard and mouse (although libretro supports those as well).
: * Does not concern itself with external WIMP GUIs (since they are not portable), or anything that would tie itself to mainly desktop PC-usage. Libretro cores ideally have to work seamlessly on mobile, desktop PC and game consoles.
: * Requires you to link your libretro-ported program to a libretro frontend, leaves the libretro frontend creation part up to you or lets you select one of the mature libretro frontends already available.

=See also=
* [[Kodi Game|Gaming in Kodi]] - Index of game related articles
** [[Game management]] - A guide to managing game files for and in Kodi
*** [[Game playback controls]] - A guide that describes the player controls and menus for gaming in Kodi
*** [[Game controllers]] - Guides for configuring gamepads and jooystick controllers in Kodi
** [[Game development]] - A guide to developing games for Kodi
** [[Compiling Kodi-Game|Compiling Kodi with RetroPlayer]]
** [[Compiling game add-ons|Compiling existing game add-ons]]
** [[Porting Libretro cores to game add-ons]]

=External Links=
* [http://www.libretro.com/ Libretro]

[[Category:Development]]
[[Category:RetroPlayer]]
[[Category:Gaming]]

Libretro

2018-10-26T12:36:23Z

Gamester17:

{{mininav| [[Kodi Game]] }}

Kodi's Game API has Libretro Wrapper which is 1:1 compatibility with the libretro API, and all libretro cores can be ported game add-ons for Kodi. Libretro itself is a well defined cross-platform platform interface to handle the communication between a frontend (Kodi with RetroPlayer) and an Emulator Core (e.g. nestopia). Kodi uses libretro but libretro is its own seperate open source project developed by independent developers.

:{{Main|Game add-ons|Game development}}

For more detailed information about libretro please visit their website at:
* https://www.libretro.com/index.php/api/

=What is libretro?=
Download the [http://www.libretro.com/wp-content/uploads/2014/03/RetroArch-Libretro-Technical-Brochure.pdf RetroArch/Libretro Technical Brochure (PDF) from libretro.org website]

Libretro is a simple lightweight C/C++ API that allows for the creation of games and emulators. It is very simple in nature, yet very powerful. The simplicity of it all requires some explanation in order to truly grasp how useful it can be to your own projects. It works according to backend/frontend principle. Backend application talks with frontend by way of API. Facilitates input/audio/video/camera/location streams for use in games/media-players/graphics applications. With added value (shaders, rewinding, input support, etc).

When you choose to use the libretro API, your program gets turned into a single library file (called a ‘libretro core’). A frontend that supports the libretro API can then load that library file and run the app. The frontend’s responsibility is to provide all the implementation-specific details, such as video/audio/input drivers. The libretro core’s responsibility is solely to provide the main program. You therefore don’t have to worry about writing different video drivers for Direct3D, OpenGL or worrying about catering to all possible input APIs/sound APIs/supporting all known joypads/etc. This is none of your concern at the libretro core implementation level.

Any project that is ported to work with this API can be made to run on ANY libretro frontend – now and forever. You maintain a single codebase that only deals with the main program, and you then target one single API (libretro) in order to port your program over to multiple platforms at once.

Other projects benefit from our ever-expanding libretro core software library by implementing the libretro API inside their own projects. To this end, project such as XBMC have already begun writing a libretro driver based on the RetroArch reference libretro frontend.

Kodi's (with RetroPlayer) is frontend for Libretro. RetroArch is the official reference frontend, and it is only for gaming and is meant to be fast, simple, yet powerful, and is available on nearly all modern-day platforms. Other third-party platform-specific frontends for Libretro are currently in development, including Arcan and Minir. For more checkout: https://www.libretro.com/index.php/powered-by-libretro/

=Who Uses Libretro?=
While the most common use case for libretro has been console emulation, it is equally suited as a platform for almost any 2D game. For example, the NX Engine used in the popular freeware game Cave Story has been successfully ported to libretro, open sourced games like Quake and Doom have been ported to libretro, and the new freeware game Dinothawr supports libretro natively.

=Libretro GL/GLES/Vulkan=
Aside from retro-style games and emulators that depend on software rendering and where you’d typically need nothing more than the ability to render to a framebuffer, the Libretro API also allows you to target OpenGL, OpenGL ES (GLES), and Vulkan. This allows you to create libretro ports that use OpenGL, OpenGL ES (GLES), or Vulkanas part of their internal rendering.

From a portability perspective, we highly recommend that you try to target both so that your libretro GL port will work on both mobile (OpenGL ES) and desktop (OpenGL) computers.

=Why Should Developers Target Libretro?=
Software that targets the libretro API instantly gains access to all of the platforms that have libretro frontends available. That means your game is immediately available to those platforms’ users without worrying about input/audio/video drivers, compatibility issues or the myriad quirks of the underlying host system(s). Likewise, there’s no need to write specialized GUI code for each platform or to use esoteric–and often buggy–cross-platform toolkits, like Qt and GTK+.

Furthermore, once your game supports libretro, all of the libretro frontends’ other features come along for free, such as RetroArch’s real-time rewind, lag-concealing netplay, lossless video recording/streaming and cutting-edge post-processing shader support.

Perhaps best of all: libretro is an open specification that is 100% free to implement, with no licensing fees or hidden strings attached.

If you’d like to learn more about libretro, leave us a comment or chat with us on IRC at #retroarch on Freenode.

=Libretro’s design goals=

Libretro is the library programming interface. Programs get ported to this library and can then be run with any libretro-compatible frontend.

Our reference frontend is RetroArch. The two projects are not the same, and this is reflected in the licensing as well. RetroArch sticks to GPL version 3 whereas the libretro API is a MIT-licensed API.

===Some of the design goals for libretro===
: * Allow a non-kitchensink approach to crossplatform portability.
: * Allow a non-dependency heavy approach to crossplatform portability. Stick to just one header containing definitions for the necessary audio/video/input callbacks.
: * Care about being backwards compatible. Libretro’s ABI( Application Binary Interface) has never been broken in years, and old libretro frontends from years ago in most cases can still use libretro cores being created today.
: * By its very design enables programs to be ported to singular dynamic libraries which can then be loaded in and out of frontend applications thanks to the libretro API.
: * Forces you by its design to rethink what code belongs to ‘core land’ and what should belong to ‘frontend land’. Libretro cores ideally should have minimal to no dependencies on any system/OS-specific APIs so that the same libretro cores can work on any libretro-compatible frontend.
: * Designed with games, emulators and multimedia in mind. Libretro core ports resemble ports being done to standalone game consoles or mobile where the primary input device is not a keyboard and mouse (although libretro supports those as well).
: * Does not concern itself with external WIMP GUIs (since they are not portable), or anything that would tie itself to mainly desktop PC-usage. Libretro cores ideally have to work seamlessly on mobile, desktop PC and game consoles.
: * Requires you to link your libretro-ported program to a libretro frontend, leaves the libretro frontend creation part up to you or lets you select one of the mature libretro frontends already available.

=See also=
* [[Kodi Game|Gaming in Kodi]] - Index of game related articles
** [[Game management]] - A guide to managing game files for and in Kodi
*** [[Game playback controls]] - A guide that describes the player controls and menus for gaming in Kodi
*** [[Game controllers]] - Guides for configuring gamepads and jooystick controllers in Kodi
** [[Game development]] - A guide to developing games for Kodi
** [[Compiling Kodi-Game|Compiling Kodi with RetroPlayer]]
** [[Compiling game add-ons|Compiling existing game add-ons]]
** [[Porting Libretro cores to game add-ons]]

=External Links=
* [http://www.libretro.com/ Libretro]

[[Category:Development]]
[[Category:RetroPlayer]]
[[Category:Gaming]]

Xiaomi Mi Box

2018-10-26T12:07:34Z

Gamester17:

{{mininav|[[Devices]]|[[Android]]}}
{{device notice}}

{{Infobox information appliance| name = Xiaomi Mi Box S| image = [[File:Xiaomi_Mi_Box_S_2018.jpg|250px]]| manufacturer = Xiaomi| releasedate = October 22, 2018| os = [[wikipedia:Android TV|Android TV]] (initially installed with [[Android|Android TV]] 8.1 "Oreo")| soc = [[Amlogic]] S905X-H | cpu = ARM Cortex-A53 Quad-Core @ up to 2.0 GHz | graphics = ARM 5-core Mali-450MP GPU| display = Full HD (1080p) @ 60 fps and 4K Ultra HD (2160p) @ 60 fps | storage = 8 GB internal| memory = 2 GB DDR3 RAM| connectivity = HDMI 2.0a supporting 4K UltraHD @ 24/25/30/50/60 Hz video output (with (HDMI-CEC, HDCP 2.2, 10-bit color & HDR10 / Rec. 2020 HDR) and 24-bit/192 kHz audio output in 5.1 or 7.1, Bluetooth 4.2/LE+EDR, 1 x USB 2.0 (Type A), Dual-Band WiFi (802.11ac 2×2 MIMO)| dimensions = 101 x 101 x 19.5 mm}}

{{Infobox information appliance| name = Xiaomi Mi Box| image = [[File:Xiaomi_Mi_Box_2016.png|250px]]| manufacturer = Xiaomi| releasedate = October 3, 2016| os = [[wikipedia:Android TV|Android TV]] (initially installed with [[Android|Android TV]] 6.0 "Marshmallow")| soc = [[Amlogic]] S905X-H | cpu = ARM Cortex-A53 Quad-Core @ up to 2.0 GHz | graphics = ARM 5-core Mali-450MP GPU| display = Full HD (1080p) @ 60 fps and 4K Ultra HD (2160p) @ 60 fps | storage = 8 GB internal| memory = 2 GB DDR3 RAM| connectivity = HDMI 2.0a supporting 4K UltraHD @ 24/25/30/50/60 Hz video output (with (HDMI-CEC, HDCP 2.2, 10-bit color & HDR10 / Rec. 2020 HDR) and 24-bit/192 kHz audio output in 5.1 or 7.1, Bluetooth 4.0/BLE, 1 x USB 2.0 (Type A), Dual-Band WiFi (802.11ac 2×2 MIMO)| dimensions = 95 x 95 x 17 mm}}

<section begin="intro" />'''Xiaomi Mi Box''' and '''Xiaomi Mi Box S''' from Xiaomi here specifically refers to the 2016 released Xiaomi Mi Box with Android TV 6.0 and its successor the '''Xiaomi Mi Box S''' released in 2018 with Android TV 8.1, both includes a bluetooth voice remote with microphone for [[Google Assistant]] support. This is an affordable 4K UltraHD (2160p) resolution capable Android TV box based on [[Amlogic]] S905X SoC that as of yet, as an Android TV box, Xiaomi have given the impression that the firmware for these two boxes will be better maintained and supported in the long-run than most other Android TV boxes out there.<section end="intro" />

:Note! Both that first '''Xiaomi Mi Box''' released in 2016 and its successor '''Xiaomi Mi Box S''' from Xiaomi are targeting an international/global market and was both developed in partnership with Google's own Android TV team, and since their release they have inofficially replaced Google's own Nexus series of boxes. Xiaomi had before that released and still have also a whole series of other Android TV boxes made for the Chinese market that also called "Xiaomi Mi Box" (still being sold as Xiaomi Mi Box Enhanced / Xiaomi Mi Box Pro / Xiaomi Mi Box 3 / Xiaomi Mi Box 4), and while the hardware of those boxes made for the Chinese market are similar they have other firmware which do not include Google Play services support and will not be covered in this article.

Running the [[wikipedia:Android TV|Android TV]]6.0 operating system or later on a Amlogic S905X SoC (System on Chip), the Xiaomi Mi Box and Xiaomi Mi Box S comes with [[10 foot interface|remote friendly]] versions of Netflix, Vudu, Hulu, HBO, UltraFlix, Fox, Sling TV, Google Play Movies, and other video service clients, with many supporting videos in native 4K Ultra HD (2160p) resolution at up to 60 frames-per-second and HDR. The Android TV platform delivers good conversational voice search for the native Android TV (leanback) app via an integrated microphone inside the included game controller. These features of Android TV with Google Play support combined with good hardware and firmware makes it a very good convergence device when pairing with Kodi for media playback.

__TOC__
{{-}}

== Installing Kodi==
{{Main|HOW-TO:Install Kodi for Android TV}}

Normal "vanilla" builds of Kodi should run just fine on the Shield.

{{Google Play}}

== Launching Android apps within Kodi ==
{{main|HOW-TO:Launch Android apps}}
{{#lst:HOW-TO:Launch Android apps|extended intro}}
{{-}}

== Controls ==
You can use standard Bluetooth accessories, such as a wireless keyboard, mouse, or game controller.

=== Bluetooth remote ===
* Xiaomi Mi Box Remote.
* Other standard Bluetooth remotes (such as the Amazon Fire TV replacement remote) can be paired and should also work.

===Bluetooth Gamepads===
* Xiaomi Mi Game Controller

=== CEC ===
Generic Android-level CEC support is available on the Android TV platform, however Kodi will not see a CEC device directly, but instead just treat the it like generic input.

=== USB ===
USB port allows for various additional remote types, such as [[FLIRC]] IR dongle, various RF dongles, etc. Most of these devices will likely show up as a keyboard type input.

=== Other bluetooth devices ===
It should be possible to pair other bluetooth controllers and remotes to the Xiaomi Mi Box. Most of these devices will likely show up as a [[keyboard]] type input.

== 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.''}}

* ?

==References==
{{reflist}}
* ?

== Forum Links ==
* Kodi forum discussion threads about the 2016 release of Xiaomi Mi Box:
**General hardware discussion: http://forum.kodi.tv/showthread.php?tid=275083

= See also =
* [[Android hardware]]
* [[Android]]

=External Links=
* http://www.mi.com/en/mibox/ - Xiaomi Mi Box product page
** * https://www.android.com/tv/xiaomi-mi-box-s/ - Android TV official website page
* https://www.mi.com/us/mi-box-s/ - Xiaomi Mi Box S product page
** https://www.android.com/tv/xiaomi-mi-box/ - Android TV official website page

[[Category:Android]]
[[Category:Amlogic]]
[[Category:HTPC]]
[[Category:ARM]]
[[Category:Hardware]]

Xiaomi Mi Box

2018-10-26T12:05:38Z

Gamester17:

{{mininav|[[Devices]]|[[Android]]}}
{{device notice}}

{{Infobox information appliance| name = Xiaomi Mi Box S| image = [[File:Xiaomi_Mi_Box_S_2018.jpg|250px]]| manufacturer = Xiaomi| releasedate = October 22, 2018| os = [[wikipedia:Android TV|Android TV]] (initially installed with [[Android]] 8.1 "Marshmallow")| soc = [[Amlogic]] S905X-H | cpu = ARM Cortex-A53 Quad-Core @ up to 2.0 GHz | graphics = ARM 5-core Mali-450MP GPU| display = Full HD (1080p) @ 60 fps and 4K Ultra HD (2160p) @ 60 fps | storage = 8 GB internal| memory = 2 GB DDR3 RAM| connectivity = HDMI 2.0a supporting 4K UltraHD @ 24/25/30/50/60 Hz video output (with (HDMI-CEC, HDCP 2.2, 10-bit color & HDR10 / Rec. 2020 HDR) and 24-bit/192 kHz audio output in 5.1 or 7.1, Bluetooth 4.2/LE+EDR, 1 x USB 2.0 (Type A), Dual-Band WiFi (802.11ac 2×2 MIMO)| dimensions = 101 x 101 x 19.5 mm}}

{{Infobox information appliance| name = Xiaomi Mi Box| image = [[File:Xiaomi_Mi_Box_2016.png|250px]]| manufacturer = Xiaomi| releasedate = October 3, 2016| os = [[wikipedia:Android TV|Android TV]] (initially installed with [[Android]] 6.0 "Marshmallow")| soc = [[Amlogic]] S905X-H | cpu = ARM Cortex-A53 Quad-Core @ up to 2.0 GHz | graphics = ARM 5-core Mali-450MP GPU| display = Full HD (1080p) @ 60 fps and 4K Ultra HD (2160p) @ 60 fps | storage = 8 GB internal| memory = 2 GB DDR3 RAM| connectivity = HDMI 2.0a supporting 4K UltraHD @ 24/25/30/50/60 Hz video output (with (HDMI-CEC, HDCP 2.2, 10-bit color & HDR10 / Rec. 2020 HDR) and 24-bit/192 kHz audio output in 5.1 or 7.1, Bluetooth 4.0/BLE, 1 x USB 2.0 (Type A), Dual-Band WiFi (802.11ac 2×2 MIMO)| dimensions = 95 x 95 x 17 mm}}

<section begin="intro" />'''Xiaomi Mi Box''' and '''Xiaomi Mi Box S''' from Xiaomi here specifically refers to the 2016 released Xiaomi Mi Box with Android TV 6.0 and its successor the '''Xiaomi Mi Box S''' released in 2018 with Android TV 8.1, both includes a bluetooth voice remote with microphone for [[Google Assistant]] support. This is an affordable 4K UltraHD (2160p) resolution capable Android TV box based on [[Amlogic]] S905X SoC that as of yet, as an Android TV box, Xiaomi have given the impression that the firmware for these two boxes will be better maintained and supported in the long-run than most other Android TV boxes out there.<section end="intro" />

:Note! Both that first '''Xiaomi Mi Box''' released in 2016 and its successor '''Xiaomi Mi Box S''' from Xiaomi are targeting an international/global market and was both developed in partnership with Google's own Android TV team, and since their release they have inofficially replaced Google's own Nexus series of boxes. Xiaomi had before that released and still have also a whole series of other Android TV boxes made for the Chinese market that also called "Xiaomi Mi Box" (still being sold as Xiaomi Mi Box Enhanced / Xiaomi Mi Box Pro / Xiaomi Mi Box 3 / Xiaomi Mi Box 4), and while the hardware of those boxes made for the Chinese market are similar they have other firmware which do not include Google Play services support and will not be covered in this article.

Running the [[wikipedia:Android TV|Android TV]]6.0 operating system or later on a Amlogic S905X SoC (System on Chip), the Xiaomi Mi Box and Xiaomi Mi Box S comes with [[10 foot interface|remote friendly]] versions of Netflix, Vudu, Hulu, HBO, UltraFlix, Fox, Sling TV, Google Play Movies, and other video service clients, with many supporting videos in native 4K Ultra HD (2160p) resolution at up to 60 frames-per-second and HDR. The Android TV platform delivers good conversational voice search for the native Android TV (leanback) app via an integrated microphone inside the included game controller. These features of Android TV with Google Play support combined with good hardware and firmware makes it a very good convergence device when pairing with Kodi for media playback.

__TOC__
{{-}}

== Installing Kodi==
{{Main|HOW-TO:Install Kodi for Android TV}}

Normal "vanilla" builds of Kodi should run just fine on the Shield.

{{Google Play}}

== Launching Android apps within Kodi ==
{{main|HOW-TO:Launch Android apps}}
{{#lst:HOW-TO:Launch Android apps|extended intro}}
{{-}}

== Controls ==
You can use standard Bluetooth accessories, such as a wireless keyboard, mouse, or game controller.

=== Bluetooth remote ===
* Xiaomi Mi Box Remote.
* Other standard Bluetooth remotes (such as the Amazon Fire TV replacement remote) can be paired and should also work.

===Bluetooth Gamepads===
* Xiaomi Mi Game Controller

=== CEC ===
Generic Android-level CEC support is available on the Android TV platform, however Kodi will not see a CEC device directly, but instead just treat the it like generic input.

=== USB ===
USB port allows for various additional remote types, such as [[FLIRC]] IR dongle, various RF dongles, etc. Most of these devices will likely show up as a keyboard type input.

=== Other bluetooth devices ===
It should be possible to pair other bluetooth controllers and remotes to the Xiaomi Mi Box. Most of these devices will likely show up as a [[keyboard]] type input.

== 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.''}}

* ?

==References==
{{reflist}}
* ?

== Forum Links ==
* Kodi forum discussion threads about the 2016 release of Xiaomi Mi Box:
**General hardware discussion: http://forum.kodi.tv/showthread.php?tid=275083

= See also =
* [[Android hardware]]
* [[Android]]

=External Links=
* http://www.mi.com/en/mibox/ - Xiaomi Mi Box product page
** * https://www.android.com/tv/xiaomi-mi-box-s/ - Android TV official website page
* https://www.mi.com/us/mi-box-s/ - Xiaomi Mi Box S product page
** https://www.android.com/tv/xiaomi-mi-box/ - Android TV official website page

[[Category:Android]]
[[Category:Amlogic]]
[[Category:HTPC]]
[[Category:ARM]]
[[Category:Hardware]]

File:Xiaomi Mi Box S 2018.jpg

2018-10-26T11:55:46Z

Gamester17: Xiaomi Mi Box S (2018) with its Bluetooth Voice Remote

Xiaomi Mi Box S (2018) with its Bluetooth Voice Remote

Xiaomi Mi Box

2018-10-26T11:54:55Z

Gamester17:

{{mininav|[[Devices]]|[[Android]]}}
{{device notice}}

{{Infobox information appliance| name = Xiaomi Mi Box S| image = [[File:Xiaomi_Mi_Box_S_2018.jpg|250px]]| manufacturer = Xiaomi| releasedate = October 22, 2018| os = [[wikipedia:Android TV|Android TV]] (initially installed with [[Android]] 8.1 "Marshmallow")| soc = [[Amlogic]] S905X-H | cpu = ARM Cortex-A53 Quad-Core @ up to 2.0 GHz | graphics = ARM 5-core Mali-450MP GPU| display = Full HD (1080p) @ 60 fps and 4K Ultra HD (2160p) @ 60 fps | storage = 8 GB internal| memory = 2 GB DDR3 RAM| connectivity = HDMI 2.0a supporting 4K UltraHD @ 24/25/30/50/60 Hz video output (with (HDMI-CEC, HDCP 2.2, 10-bit color & HDR10 / Rec. 2020 HDR) and 24-bit/192 kHz audio output in 5.1 or 7.1, Bluetooth 4.2/LE+EDR, 1 x USB 2.0 (Type A), Dual-Band WiFi (802.11ac 2×2 MIMO)| dimensions = 101 x 101 x 19.5 mm}}

{{Infobox information appliance| name = Xiaomi Mi Box| image = [[File:Xiaomi_Mi_Box_2016.png|250px]]| manufacturer = Xiaomi| releasedate = October 3, 2016| os = [[wikipedia:Android TV|Android TV]] (initially installed with [[Android]] 6.0 "Marshmallow")| soc = [[Amlogic]] S905X-H | cpu = ARM Cortex-A53 Quad-Core @ up to 2.0 GHz | graphics = ARM 5-core Mali-450MP GPU| display = Full HD (1080p) @ 60 fps and 4K Ultra HD (2160p) @ 60 fps | storage = 8 GB internal| memory = 2 GB DDR3 RAM| connectivity = HDMI 2.0a supporting 4K UltraHD @ 24/25/30/50/60 Hz video output (with (HDMI-CEC, HDCP 2.2, 10-bit color & HDR10 / Rec. 2020 HDR) and 24-bit/192 kHz audio output in 5.1 or 7.1, Bluetooth 4.0/BLE, 1 x USB 2.0 (Type A), Dual-Band WiFi (802.11ac 2×2 MIMO)| dimensions = 95 x 95 x 17 mm}}

<section begin="intro" />'''Xiaomi Mi Box''' and '''Xiaomi Mi Box S''' from Xiaomi here specifically refers to the 2016 released Xiaomi Mi Box with Android TV 6.0 and its successor the '''Xiaomi Mi Box S''' released in 2018 with Android TV 8.1, both includes a bluetooth voice remote with microphone for [[Google Assistant]] support. This is an affordable 4K UltraHD (2160p) resolution capable Android TV box based on [[Amlogic]] S905X SoC that as of yet, as an Android TV box, Xiaomi have given the impression that the firmware for these two boxes will be better maintained and supported in the long-run than most other Android TV boxes out there.<section end="intro" />

:Note! Both that first '''Xiaomi Mi Box''' released in 2016 and its successor '''Xiaomi Mi Box S''' from Xiaomi are targeting an international/global market and was both developed in partnership with Google's own Android TV team, and since their release they have inofficially replaced Google's own Nexus series of boxes. Xiaomi had before that released and still have also a whole series of other Android TV boxes made for the Chinese market that also called "Xiaomi Mi Box" (still being sold as Xiaomi Mi Box Enhanced / Xiaomi Mi Box Pro / Xiaomi Mi Box 3 / Xiaomi Mi Box 4), and while the hardware of those boxes made for the Chinese market are similar they have other firmware which do not include Google Play services support and will not be covered in this article.

Running the [[wikipedia:Android TV|Android TV]]6.0 operating system or later on a Amlogic S905X SoC (System on Chip), the Xiaomi Mi Box and Xiaomi Mi Box S comes with [[10 foot interface|remote friendly]] versions of Netflix, Vudu, Hulu, HBO, UltraFlix, Fox, Sling TV, Google Play Movies, and other video service clients, with many supporting videos in native 4K Ultra HD (2160p) resolution at up to 60 frames-per-second and HDR. The Android TV platform delivers good conversational voice search for the native Android TV (leanback) app via an integrated microphone inside the included game controller. These features of Android TV with Google Play support combined with good hardware and firmware makes it a very good convergence device when pairing with Kodi for media playback.

__TOC__
{{-}}

== Installing Kodi==
{{Main|HOW-TO:Install Kodi for Android TV}}

Normal "vanilla" builds of Kodi should run just fine on the Shield.

{{Google Play}}

== Launching Android apps within Kodi ==
{{main|HOW-TO:Launch Android apps}}
{{#lst:HOW-TO:Launch Android apps|extended intro}}
{{-}}

== Controls ==
You can use standard Bluetooth accessories, such as a wireless keyboard, mouse, or game controller.

=== Bluetooth remote ===
* Xiaomi Mi Box Remote.
* Other standard Bluetooth remotes (such as the Amazon Fire TV replacement remote) can be paired and should also work.

===Bluetooth Gamepads===
* Xiaomi Mi Game Controller

=== CEC ===
Generic Android-level CEC support is available on the Android TV platform, however Kodi will not see a CEC device directly, but instead just treat the it like generic input.

=== USB ===
USB port allows for various additional remote types, such as [[FLIRC]] IR dongle, various RF dongles, etc. Most of these devices will likely show up as a keyboard type input.

=== Other bluetooth devices ===
It should be possible to pair other bluetooth controllers and remotes to the Xiaomi Mi Box. Most of these devices will likely show up as a [[keyboard]] type input.

== 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.''}}

* ?

==References==
{{reflist}}
* ?

== Forum Links ==
* Kodi forum discussion threads about the 2016 release of Xiaomi Mi Box:
**General hardware discussion: http://forum.kodi.tv/showthread.php?tid=275083
*Official Xiaomi pages and sites about this Mi Box:
** Xiaomi Mi Box product page: http://www.mi.com/en/mibox/

= See also =
* [[Android hardware]]
* [[Android]]

=External Links=
* https://www.mi.com/us/mi-box-s/
* https://www.android.com/tv/xiaomi-mi-box-s/
* https://www.android.com/tv/xiaomi-mi-box/

[[Category:Android]]
[[Category:Amlogic]]
[[Category:HTPC]]
[[Category:ARM]]
[[Category:Hardware]]

Xiaomi Mi Box

2018-10-26T11:50:16Z

Gamester17:

{{mininav|[[Devices]]|[[Android]]}}
{{device notice}}

{{Infobox information appliance| name = Xiaomi Mi Box S| image = [[File:Xiaomi_Mi_Box_S_2018.png|250px]]| manufacturer = Xiaomi| releasedate = October 22, 2018| os = [[wikipedia:Android TV|Android TV]] (initially installed with [[Android]] 8.1 "Marshmallow")| soc = [[Amlogic]] S905X-H | cpu = ARM Cortex-A53 Quad-Core @ up to 2.0 GHz | graphics = ARM 5-core Mali-450MP GPU| display = Full HD (1080p) @ 60 fps and 4K Ultra HD (2160p) @ 60 fps | storage = 8 GB internal| memory = 2 GB DDR3 RAM| connectivity = HDMI 2.0a supporting 4K UltraHD @ 24/25/30/50/60 Hz video output (with (HDMI-CEC, HDCP 2.2, 10-bit color & HDR10 / Rec. 2020 HDR) and 24-bit/192 kHz audio output in 5.1 or 7.1, Bluetooth 4.2/LE+EDR, 1 x USB 2.0 (Type A), Dual-Band WiFi (802.11ac 2×2 MIMO)| dimensions = 101 x 101 x 19.5 mm}}

{{Infobox information appliance| name = Xiaomi Mi Box| image = [[File:Xiaomi_Mi_Box_2016.png|250px]]| manufacturer = Xiaomi| releasedate = October 3, 2016| os = [[wikipedia:Android TV|Android TV]] (initially installed with [[Android]] 6.0 "Marshmallow")| soc = [[Amlogic]] S905X-H | cpu = ARM Cortex-A53 Quad-Core @ up to 2.0 GHz | graphics = ARM 5-core Mali-450MP GPU| display = Full HD (1080p) @ 60 fps and 4K Ultra HD (2160p) @ 60 fps | storage = 8 GB internal| memory = 2 GB DDR3 RAM| connectivity = HDMI 2.0a supporting 4K UltraHD @ 24/25/30/50/60 Hz video output (with (HDMI-CEC, HDCP 2.2, 10-bit color & HDR10 / Rec. 2020 HDR) and 24-bit/192 kHz audio output in 5.1 or 7.1, Bluetooth 4.0/BLE, 1 x USB 2.0 (Type A), Dual-Band WiFi (802.11ac 2×2 MIMO)| dimensions = 95 x 95 x 17 mm}}

<section begin="intro" />'''Xiaomi Mi Box''' and '''Xiaomi Mi Box S''' from Xiaomi here specifically refers to the 2016 released Xiaomi Mi Box with Android TV 6.0 and its successor the '''Xiaomi Mi Box S''' released in 2018 with Android TV 8.1, both includes a bluetooth voice remote with microphone for [[Google Assistant]] support. This is an affordable 4K UltraHD (2160p) resolution capable Android TV box based on [[Amlogic]] S905X SoC that as of yet, as an Android TV box, Xiaomi have given the impression that the firmware for these two boxes will be better maintained and supported in the long-run than most other Android TV boxes out there.<section end="intro" />

:Note! Both that first '''Xiaomi Mi Box''' released in 2016 and its successor '''Xiaomi Mi Box S''' from Xiaomi are targeting an international/global market and was both developed in partnership with Google's own Android TV team, and since their release they have inofficially replaced Google's own Nexus series of boxes. Xiaomi had before that released and still have also a whole series of other Android TV boxes made for the Chinese market that also called "Xiaomi Mi Box" (still being sold as Xiaomi Mi Box Enhanced / Xiaomi Mi Box Pro / Xiaomi Mi Box 3 / Xiaomi Mi Box 4), and while the hardware of those boxes made for the Chinese market are similar they have other firmware which do not include Google Play services support and will not be covered in this article.

Running the [[wikipedia:Android TV|Android TV]]6.0 operating system or later on a Amlogic S905X SoC (System on Chip), the Xiaomi Mi Box and Xiaomi Mi Box S comes with [[10 foot interface|remote friendly]] versions of Netflix, Vudu, Hulu, HBO, UltraFlix, Fox, Sling TV, Google Play Movies, and other video service clients, with many supporting videos in native 4K Ultra HD (2160p) resolution at up to 60 frames-per-second and HDR. The Android TV platform delivers good conversational voice search for the native Android TV (leanback) app via an integrated microphone inside the included game controller. These features of Android TV with Google Play support combined with good hardware and firmware makes it a very good convergence device when pairing with Kodi for media playback.

__TOC__
{{-}}

== Installing Kodi==
{{Main|HOW-TO:Install Kodi for Android TV}}

Normal "vanilla" builds of Kodi should run just fine on the Shield.

{{Google Play}}

== Launching Android apps within Kodi ==
{{main|HOW-TO:Launch Android apps}}
{{#lst:HOW-TO:Launch Android apps|extended intro}}
{{-}}

== Controls ==
You can use standard Bluetooth accessories, such as a wireless keyboard, mouse, or game controller.

=== Bluetooth remote ===
* Xiaomi Mi Box Remote.
* Other standard Bluetooth remotes (such as the Amazon Fire TV replacement remote) can be paired and should also work.

===Bluetooth Gamepads===
* Xiaomi Mi Game Controller

=== CEC ===
Generic Android-level CEC support is available on the Android TV platform, however Kodi will not see a CEC device directly, but instead just treat the it like generic input.

=== USB ===
USB port allows for various additional remote types, such as [[FLIRC]] IR dongle, various RF dongles, etc. Most of these devices will likely show up as a keyboard type input.

=== Other bluetooth devices ===
It should be possible to pair other bluetooth controllers and remotes to the Xiaomi Mi Box. Most of these devices will likely show up as a [[keyboard]] type input.

== 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.''}}

* ?

==References==
{{reflist}}
* ?

== Forum Links ==
* Kodi forum discussion threads about the 2016 release of Xiaomi Mi Box:
**General hardware discussion: http://forum.kodi.tv/showthread.php?tid=275083
*Official Xiaomi pages and sites about this Mi Box:
** Xiaomi Mi Box product page: http://www.mi.com/en/mibox/

= See also =
* [[Android hardware]]
* [[Android]]

=External Links=
* https://www.mi.com/us/mi-box-s/
* https://www.android.com/tv/xiaomi-mi-box-s/
* https://www.android.com/tv/xiaomi-mi-box/

[[Category:Android]]
[[Category:Amlogic]]
[[Category:HTPC]]
[[Category:ARM]]
[[Category:Hardware]]

Xiaomi Mi Box

2018-10-26T11:48:21Z

Gamester17:

{{mininav|[[Devices]]|[[Android]]}}
{{device notice}}

{{Infobox information appliance| name = Xiaomi Mi Box S| image = [[File:Xiaomi_Mi_Box_2018.png|250px]]| manufacturer = Xiaomi| releasedate = October 22, 2018| os = [[wikipedia:Android TV|Android TV]] (initially installed with [[Android]] 8.1 "Marshmallow")| soc = [[Amlogic]] S905X-H | cpu = ARM Cortex-A53 Quad-Core @ up to 2.0 GHz | graphics = ARM 5-core Mali-450MP GPU| display = Full HD (1080p) @ 60 fps and 4K Ultra HD (2160p) @ 60 fps | storage = 8 GB internal| memory = 2 GB DDR3 RAM| connectivity = HDMI 2.0a supporting 4K UltraHD @ 24/25/30/50/60 Hz video output (with (HDMI-CEC, HDCP 2.2, 10-bit color & HDR10 / Rec. 2020 HDR) and 24-bit/192 kHz audio output in 5.1 or 7.1, Bluetooth 4.2/LE+EDR, 1 x USB 2.0 (Type A), Dual-Band WiFi (802.11ac 2×2 MIMO)| dimensions = 101 x 101 x 19.5 mm}}

{{Infobox information appliance| name = Xiaomi Mi Box| image = [[File:Xiaomi_Mi_Box_2016.png|250px]]| manufacturer = Xiaomi| releasedate = October 3, 2016| os = [[wikipedia:Android TV|Android TV]] (initially installed with [[Android]] 6.0 "Marshmallow")| soc = [[Amlogic]] S905X-H | cpu = ARM Cortex-A53 Quad-Core @ up to 2.0 GHz | graphics = ARM 5-core Mali-450MP GPU| display = Full HD (1080p) @ 60 fps and 4K Ultra HD (2160p) @ 60 fps | storage = 8 GB internal| memory = 2 GB DDR3 RAM| connectivity = HDMI 2.0a supporting 4K UltraHD @ 24/25/30/50/60 Hz video output (with (HDMI-CEC, HDCP 2.2, 10-bit color & HDR10 / Rec. 2020 HDR) and 24-bit/192 kHz audio output in 5.1 or 7.1, Bluetooth 4.0/BLE, 1 x USB 2.0 (Type A), Dual-Band WiFi (802.11ac 2×2 MIMO)| dimensions = 95 x 95 x 17 mm}}

<section begin="intro" />'''Xiaomi Mi Box''' and '''Xiaomi Mi Box S''' from Xiaomi here specifically refers to the 2016 released Xiaomi Mi Box with Android TV 6.0 and its successor the '''Xiaomi Mi Box S''' released in 2018 with Android TV 8.1, both includes a bluetooth voice remote with microphone for [[Google Assistant]] support. This is an affordable 4K UltraHD (2160p) resolution capable Android TV box based on [[Amlogic]] S905X SoC that as of yet, as an Android TV box, Xiaomi have given the impression that the firmware for these two boxes will be better maintained and supported in the long-run than most other Android TV boxes out there.<section end="intro" />

:Note! Both that first '''Xiaomi Mi Box''' released in 2016 and its successor '''Xiaomi Mi Box S''' from Xiaomi are targeting an international/global market and was both developed in partnership with Google's own Android TV team, and since their release they have inofficially replaced Google's own Nexus series of boxes. Xiaomi had before that released and still have also a whole series of other Android TV boxes made for the Chinese market that also called "Xiaomi Mi Box" (still being sold as Xiaomi Mi Box Enhanced / Xiaomi Mi Box Pro / Xiaomi Mi Box 3 / Xiaomi Mi Box 4), and while the hardware of those boxes made for the Chinese market are similar they have other firmware which do not include Google Play services support and will not be covered in this article.

Running the [[wikipedia:Android TV|Android TV]]6.0 operating system or later on a Amlogic S905X SoC (System on Chip), the Xiaomi Mi Box and Xiaomi Mi Box S comes with [[10 foot interface|remote friendly]] versions of Netflix, Vudu, Hulu, HBO, UltraFlix, Fox, Sling TV, Google Play Movies, and other video service clients, with many supporting videos in native 4K Ultra HD (2160p) resolution at up to 60 frames-per-second and HDR. The Android TV platform delivers good conversational voice search for the native Android TV (leanback) app via an integrated microphone inside the included game controller. These features of Android TV with Google Play support combined with good hardware and firmware makes it a very good convergence device when pairing with Kodi for media playback.

__TOC__
{{-}}

== Installing Kodi==
{{Main|HOW-TO:Install Kodi for Android TV}}

Normal "vanilla" builds of Kodi should run just fine on the Shield.

{{Google Play}}

== Launching Android apps within Kodi ==
{{main|HOW-TO:Launch Android apps}}
{{#lst:HOW-TO:Launch Android apps|extended intro}}
{{-}}

== Controls ==
You can use standard Bluetooth accessories, such as a wireless keyboard, mouse, or game controller.

=== Bluetooth remote ===
* Xiaomi Mi Box Remote.
* Other standard Bluetooth remotes (such as the Amazon Fire TV replacement remote) can be paired and should also work.

===Bluetooth Gamepads===
* Xiaomi Mi Game Controller

=== CEC ===
Generic Android-level CEC support is available on the Android TV platform, however Kodi will not see a CEC device directly, but instead just treat the it like generic input.

=== USB ===
USB port allows for various additional remote types, such as [[FLIRC]] IR dongle, various RF dongles, etc. Most of these devices will likely show up as a keyboard type input.

=== Other bluetooth devices ===
It should be possible to pair other bluetooth controllers and remotes to the Xiaomi Mi Box. Most of these devices will likely show up as a [[keyboard]] type input.

== 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.''}}

* ?

==References==
{{reflist}}
* ?

== Forum Links ==
* Kodi forum discussion threads about the 2016 release of Xiaomi Mi Box:
**General hardware discussion: http://forum.kodi.tv/showthread.php?tid=275083
*Official Xiaomi pages and sites about this Mi Box:
** Xiaomi Mi Box product page: http://www.mi.com/en/mibox/

= See also =
* [[Android hardware]]
* [[Android]]

=External Links=
* https://www.mi.com/us/mi-box-s/
* https://www.android.com/tv/xiaomi-mi-box-s/
* https://www.android.com/tv/xiaomi-mi-box/

[[Category:Android]]
[[Category:Amlogic]]
[[Category:HTPC]]
[[Category:ARM]]
[[Category:Hardware]]

Xiaomi Mi Box

2018-10-26T11:47:06Z

Gamester17:

{{mininav|[[Devices]]|[[Android]]}}
{{device notice}}

{{Infobox information appliance| name = Xiaomi Mi Box S| image = [[File:Xiaomi_Mi_Box_2018.png|250px]]| manufacturer = Xiaomi| releasedate = October 22, 2018| os = [[wikipedia:Android TV|Android TV]] (initially installed with [[Android]] 8.1 "Marshmallow")| soc = [[Amlogic]] S905X-H | cpu = ARM Cortex-A53 Quad-Core @ up to 2.0 GHz | graphics = ARM 5-core Mali-450MP GPU| display = Full HD (1080p) @ 60 fps and 4K Ultra HD (2160p) @ 60 fps | storage = 8 GB internal| memory = 2 GB DDR3 RAM| connectivity = HDMI 2.0a supporting 4K UltraHD @ 24/25/30/50/60 Hz video output (with (HDMI-CEC, HDCP 2.2, 10-bit color & HDR10 / Rec. 2020 HDR) and 24-bit/192 kHz audio output in 5.1 or 7.1, Bluetooth 4.2/LE+EDR, 1 x USB 2.0 (Type A), Dual-Band WiFi (802.11ac 2×2 MIMO)| dimensions = 101 x 101 x 19.5 mm}}

{{Infobox information appliance| name = Xiaomi Mi Box| image = [[File:Xiaomi_Mi_Box_2016.png|250px]]| manufacturer = Xiaomi| releasedate = October 3, 2016| os = [[wikipedia:Android TV|Android TV]] (initially installed with [[Android]] 6.0 "Marshmallow")| soc = [[Amlogic]] S905X-H | cpu = ARM Cortex-A53 Quad-Core @ up to 2.0 GHz | graphics = ARM 5-core Mali-450MP GPU| display = Full HD (1080p) @ 60 fps and 4K Ultra HD (2160p) @ 60 fps | storage = 8 GB internal| memory = 2 GB DDR3 RAM| connectivity = HDMI 2.0a supporting 4K UltraHD @ 24/25/30/50/60 Hz video output (with (HDMI-CEC, HDCP 2.2, 10-bit color & HDR10 / Rec. 2020 HDR) and 24-bit/192 kHz audio output in 5.1 or 7.1, Bluetooth 4.0/BLE, 1 x USB 2.0 (Type A), Dual-Band WiFi (802.11ac 2×2 MIMO)| dimensions = 101 x 101 x 19.5 mm}}

<section begin="intro" />'''Xiaomi Mi Box''' and '''Xiaomi Mi Box S''' from Xiaomi here specifically refers to the 2016 released Xiaomi Mi Box with Android TV 6.0 and its successor the '''Xiaomi Mi Box S''' released in 2018 with Android TV 8.1, both includes a bluetooth voice remote with microphone for [[Google Assistant]] support. This is an affordable 4K UltraHD (2160p) resolution capable Android TV box based on [[Amlogic]] S905X SoC that as of yet, as an Android TV box, Xiaomi have given the impression that the firmware for these two boxes will be better maintained and supported in the long-run than most other Android TV boxes out there.<section end="intro" />

:Note! Both that first '''Xiaomi Mi Box''' released in 2016 and its successor '''Xiaomi Mi Box S''' from Xiaomi are targeting an international/global market and was both developed in partnership with Google's own Android TV team, and since their release they have inofficially replaced Google's own Nexus series of boxes. Xiaomi had before that released and still have also a whole series of other Android TV boxes made for the Chinese market that also called "Xiaomi Mi Box" (still being sold as Xiaomi Mi Box Enhanced / Xiaomi Mi Box Pro / Xiaomi Mi Box 3 / Xiaomi Mi Box 4), and while the hardware of those boxes made for the Chinese market are similar they have other firmware which do not include Google Play services support and will not be covered in this article.

Running the [[wikipedia:Android TV|Android TV]]6.0 operating system or later on a Amlogic S905X SoC (System on Chip), the Xiaomi Mi Box and Xiaomi Mi Box S comes with [[10 foot interface|remote friendly]] versions of Netflix, Vudu, Hulu, HBO, UltraFlix, Fox, Sling TV, Google Play Movies, and other video service clients, with many supporting videos in native 4K Ultra HD (2160p) resolution at up to 60 frames-per-second and HDR. The Android TV platform delivers good conversational voice search for the native Android TV (leanback) app via an integrated microphone inside the included game controller. These features of Android TV with Google Play support combined with good hardware and firmware makes it a very good convergence device when pairing with Kodi for media playback.

__TOC__
{{-}}

== Installing Kodi==
{{Main|HOW-TO:Install Kodi for Android TV}}

Normal "vanilla" builds of Kodi should run just fine on the Shield.

{{Google Play}}

== Launching Android apps within Kodi ==
{{main|HOW-TO:Launch Android apps}}
{{#lst:HOW-TO:Launch Android apps|extended intro}}
{{-}}

== Controls ==
You can use standard Bluetooth accessories, such as a wireless keyboard, mouse, or game controller.

=== Bluetooth remote ===
* Xiaomi Mi Box Remote.
* Other standard Bluetooth remotes (such as the Amazon Fire TV replacement remote) can be paired and should also work.

===Bluetooth Gamepads===
* Xiaomi Mi Game Controller

=== CEC ===
Generic Android-level CEC support is available on the Android TV platform, however Kodi will not see a CEC device directly, but instead just treat the it like generic input.

=== USB ===
USB port allows for various additional remote types, such as [[FLIRC]] IR dongle, various RF dongles, etc. Most of these devices will likely show up as a keyboard type input.

=== Other bluetooth devices ===
It should be possible to pair other bluetooth controllers and remotes to the Xiaomi Mi Box. Most of these devices will likely show up as a [[keyboard]] type input.

== 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.''}}

* ?

==References==
{{reflist}}
* ?

== Forum Links ==
* Kodi forum discussion threads about the 2016 release of Xiaomi Mi Box:
**General hardware discussion: http://forum.kodi.tv/showthread.php?tid=275083
*Official Xiaomi pages and sites about this Mi Box:
** Xiaomi Mi Box product page: http://www.mi.com/en/mibox/

= See also =
* [[Android hardware]]
* [[Android]]

=External Links=
* https://www.mi.com/us/mi-box-s/
* https://www.android.com/tv/xiaomi-mi-box-s/
* https://www.android.com/tv/xiaomi-mi-box/

[[Category:Android]]
[[Category:Amlogic]]
[[Category:HTPC]]
[[Category:ARM]]
[[Category:Hardware]]

Android hardware

2018-10-26T11:19:43Z

Gamester17:

{{mininav|[[Android]]}}
<section begin="intro" />For most [[wikipedia:High-definition video|high-definition video]]s (1080p or higher resolution), hardware video decoding is necessary for smooth video playback on most Android devices. Therefor this article contains a list of SoC chipset hardware, (SoC stands for "System on a Chip" which contain the CPU plus GPU and VPU circuits combination, and is also known as a "chipset"), as on Android platforms this SoC chipset is what can playback common video codecs smoothly using Kodi/XBMC.<section end="intro" />

The fact is, while some devices might be able to smoothly decode [[wikipedia:Standard-definition television|standard-definition video]]s and even some 720p or higher resolution videos using only software video decoding with raw CPU compute power, offloading a large part of video decoding tasks to an integrated VPU (Video Processor Unit) that is optimized specifically for this job is considered essential for almost all Android devices to be able to smoothly playback high definition videos.

==Basic requirements==
{{see also|Supported hardware}}
{{#lst:Supported hardware|Android}}

==How do I know what chipset I have?==
There are so many out there so it can something be difficult to find out, but these are some good websites for looking up the SoC (System on a Chip) chipset used in your Android hardware device:

* http://www.iboum.com - Digital media players
* http://gsmarena.com - Phones
* [[Wikipedia:Comparison of Android devices]]
* http://www.androidcentral.com/devices

Also as a reference you can compare different SoC (System on a Chip) chipset specifications on system-on-a-chip.findthebest.com as well as in http://docs.google.com/spreadsheets/d/1GT7I4P8MDlfYvRaL9Wv0NplQJryl54pO_6-9P3g7Fvk/

==Compatible chipsets==
These specific mass-market hardware SoC chipsets listed below should be capable at least partial hardware accelerated video decoding support for the more popular video codecs in the latest official Kodi builds for Android. Also understand that for some devices you might first need to upgrade the hardware firmware image on the device to achieve smooth playback at 1080p or higher resolution. Please contact your hardware manufacturer support for an updated system update firmware and apply that upgrade image before installing Kodi.

{{warning|These pages are maintained by the community and should not be considered an endorsement or recommendation. The information on this page might contain errors. It might also contain ants, and their antsy antics. '''[[Kodi:General disclaimer|*]]''' }}

{|
| A "|| {{yes}} ||" mark indicates that SoC (System-on-a-Chip) chipset should be able to decode those codecs at least 1080p in Kodi without issues.
|}
{| width="100%" class="datatable"
|-
! rowspan="2" | Chip<br />manufacturer !! rowspan="2" | SoC chipset !! rowspan="2" | Examples of media players / development boards running Android and using these SoC chipsets with Kodi support !! colspan="5" | Hardware video decoding !! rowspan="2" | Notes
|-
! H.264 !! MPEG-2 !! VC-1 / WMV 9 !! HEVC (H.265) !! VP9
|-
| Actions Semi || S500 / ATM7029 / ATM7039S / ATM7059 || Aceberry S500 devboard, ActDuino S500 Development Board, Allo SPARKY board, Kaiboer F5 Plus, LeMaker Guitar, LemonPi, Roseapple Pi Development Board || {{?}} || {{?}} || {{?}} || {{?}} || {{?}} ||
|-
| Actions Semi || S900 / ATM9009 || 96Boards Bubblegum-96 Development Board || {{?}} || {{?}} || {{?}} || {{?}} || {{?}} ||
|-
| ALi || M3733 || GoWarrior Tiger Development Board, Uyesee L100T2, Zidoo D1 || {{?}} || {{?}} || {{?}} || {{?}} || {{?}} ||
|-
| Allwinner || A31 / A31s / A33 || Justop Quadro, Mele A1000G/M8/M9, Measy B4K/U4K, VidOn Box, VidOn.me AV200 || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || <ref name="Open-source violator">Warning for open source violators that do not comply with Kodi's GPL license! There are a few SoC manufacturers, like example Allwinner and Realtek or media player using their chipsets, that violate the GPL license that Kodi (and XBMC before) is bound under. This type of violation done by forking and not releasing all source code that they integrate into Kodi / XBMC when they modify or add closed source code or non-complatible code. This is because Kodi's code is bound under an open source license that require that all code integrating with Kodi's own GPL project is also releasing under a GPL compatible license. Other that hurting the Kodi project by not contributing as required, the risk for end-users buying hardware that rely on open source violations is not getting any support for the official Kodi project.</ref>
|-
| Allwinner || A80 / A83T || Tronsmart Draco AW80, Rikomagic MK80 || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || <ref name="Open-source violator"/>
|-
| Allwinner || H2+ / H3 / H8 || Inphic i8, Orange Pi 2/Plus, Tronsmart Draco H3, Zidoo X1 || {{?}} || {{?}} || {{?}} || {{?}} || {{?}} || <ref name="Open-source violator"/>
|-
| Allwinner || H5 / A64 / H64 || Nobel64 Development Board || {{?}} || {{?}} || {{?}} || {{?}} || {{?}} || <ref name="Open-source violator"/>
|-
| [[Amlogic]] || AML8726-M1 / AML8726-M3 / AML8726-M6 / AML8726-MX / AML8726-MXS / AML8726-MXL || [[Pivos XIOS|Pivos XIOS DS/XS]], GameStick (by PlayJam), Geniatech ATV1220/ATV520/ATV1610, MyGica ATV420/ATV500/ATV1610, JynxBox M1/M6, Matricom G-Box Midnight MX2, [[WeTek Play]] || {{yes}} || {{yes}} || {{yes}} || {{no}} || {{no}} ||
|-
| [[Amlogic]] || S801 / M802 / S802 / M802 (formerly AML8726-M8) || Geniatech ATV582 / MyGica ATV582, Minix Neo X8/X8-H, Eny Technology ES8, Tronsmart Vega S89/S89-H, Beelink S82/S82H/M8, Xiaomi Mi Box Enhanced || {{yes}} || {{yes}} || {{yes}} || {{no}} || {{no}} ||
|-
| [[Amlogic]] || S805 / M805 / S806 / M806 / S812 || Eny Technology EM9/M8S/M8C/EM6Q-MXQ, Geniatech ATV585/ATV1810 / MyGica ATV585/ATV1810, Minix NEO X6 /X8-H Plus, [[ODROID|Hardkernel ODROID-C1]], Ugoos S85, SkyStream X5, Sumvision Cyclone X4, Xtreamer Wonder, Beelink S82 Plus, WeTek Core || {{yes}} || {{yes}} || {{yes}} || {{yes}}<br />{{smaller|(8-bit only)}} || {{?}} || <ref name="8-bit Main HEVC (H.265) profile support only">Some SoC's hardware video decoders like the one in Amlogic S805/M805/S806/M806/S812 and Rockchip RK3288/RK3368 are limited to only supporting the Main HEVC (H.265) profile, which means that they only support 8-bit color range and lower bit-rate, and they do therefor not support the Main10 HEVC or Main12 profiles which is uses for 10-bit and 12-bit color ranges respectivly, which also require support for higher bit-rates. This usually also means that they will not be capable of playing HEVC videos encoded in 4K (2160p) resolution at 60 FPS (frames per second). For more information see http://en.wikipedia.org/wiki/High_Efficiency_Video_Coding_tiers_and_levels</ref>
|-
| [[Amlogic]] || S905 || Beelink MINI MX, Geniatech ATV495/ATV1950, MyGica ATV49/ATV1950, [[ODROID|Hardkernel ODROID-C2]], Ugoos AM1/AM2 || {{yes}} || {{yes}} || {{yes}} || {{yes}} || {{?}} ||
|-
| [[Amlogic]] || S905D / S905M / S905X / S908 || [[Xiaomi Mi Box|Xiaomi Mi Box (2016)]] / Xiaomi Mi Box 3 / Xiaomi Mi Box S (2018) || {{yes}} || {{yes}} || {{yes}} || {{yes}} || {{yes}} ||
|-
| [[Amlogic]] || S912 || Beelink GT1, Eny Technology Enybox X2, Rikomagic MK22, Videostrong KM8 Pro || {{yes}} || {{yes}} || {{yes}} || {{yes}} || {{yes}} ||
|-
| Broadcom || BCM2836 / BCM2837 || || {{?}} || {{?}} || {{?}} || {{no}} || {{no}} ||
|-
| Broadcom || BCM28145 / BCM28155 || [[Amazon Fire TV Stick|Amazon Fire TV Stick (2014/2015)]] || {{yes}} || {{yes}} || {{yes}} || {{no}} || {{yes}} ||
|-
| Broadcom || BCM7250 / BCM7252 / BCM7252s / BCM72502 || Freebox Mini 4K, Infomir MAG350/MAG352, Smart Labs SML-482 || {{?}} || {{?}} || {{?}} || {{?}} || {{?}} ||
|-
| [[Freescale]]/NSX || i.MX 6 series (i.MX6 / i.MX6S / i.MX6SL / i.MX6D / i.MX6DL / i.MX6Q) || [[CompuLab Utilite]], [[SolidRun CuBox-i|SolidRun CuBox-i & CuBoxTV]], [[SolidRun Hummingboard]], [[UDOO|UDOO Neo/Duo/Quad]], [[Wandboard|Wandboard Solo/Dual/Quad ]] || {{?}} || {{?}} || {{?}} || {{no}} || {{no}} ||
|-
| [[Freescale]]/NSX || i.MX 7 series || || {{?}} || {{?}} || {{?}} || {{?}} || {{?}} ||
|-
| HiSilicon || Hi3798C / Hi3798M || HiMedia H7-II/M3/Q5-4K/Q5-IV/Q5X/Q10-IV, Open Hour Gekco, PixePlay KURO || {{?}} || {{?}} || {{?}} || {{?}} || {{?}} ||
|-
| HiSilicon || Hi3798C V200 || HiMedia Q10 Pro || {{yes}} || {{yes}} || {{yes}} || {{yes}} || {{yes}} ||
|-
| HiSilicon || Kirin 620 || LeMaker HiKey Development Board || {{?}} || {{?}} || {{?}} || {{?}} || {{?}} ||
|-
| Intel || Atom E3815 / E3825 || Intel MinnowBoard MAX Development Board || {{?}} || {{?}} || {{?}} || {{no}} || {{no}} ||
|-
| Intel || Atom x3 / x5 / x7 (x3-C3130 / x3-C3230RK / x3-C3440 / x5-8300 / x5-8500 / x7-8700) || UDOO x86 Development Board (Basic & Advanced), Up Board || {{?}} || {{?}} || {{?}} || {{?}} || {{?}} ||
|-
| Intel || Atom Z3530 / Z3560 / Z3580 / Z3735 || [[Google Nexus Player]], Minix Neo Z64 || {{yes}} || {{no}} || {{no}} || {{no}} || {{no}} ||
|-
| Intel || Celeron N3000 / N3050 / N3150, and Pentium N3700 || ASRock Beebox, Gigabyte BRIX|| {{yes}} || {{yes}} || {{yes}} || {{no}} || {{no}} ||
|-
| Intel || Core M3 6Y30 / M5 6Y54 / M5 6Y57 / M5 6Y75 || Intel Compute Stick || {{yes}} || {{yes}} || {{yes}} || {{yes}} || {{yes}} ||
|-
| Marvell || ARMADA 1500 Mini/Pro/Pro4K/Ultra || || {{?}} || {{?}} || {{?}} || {{?}} || {{?}} ||
|-
| MediaTek || MT5890 || Sony Android TV (2015 and 2016) || {{yes}} || {{yes}} || {{no}} || {{yes}} || {{yes}} <br />{{smaller|(4K TV only)}} ||
|-
| MediaTek || MTK6589 / MT6589 / MT6589T / MT6589M || || {{?}} || {{?}} || {{?}} || {{no}} || {{no}} ||
|-
| MediaTek || MT8127 || Amazon Fire Tablet (7", 2015), Amazon Fire TV Stick with Alexa (2016) || {{yes}} || {{no}} || {{no}} || {{yes}} || {{yes}} ||
|-
| MediaTek || MT8173 || [[Amazon Fire TV|Amazon Fire TV (2015)]] || {{yes}} || {{yes}} || {{no}} || {{yes}} || {{yes}} ||
|-
| MediaTek || MT8685 / MT8685A / MT8685B || UTStarcom MT8685/MC8685A/MC8685B, Xiaomi Mi Box Mini || {{?}} || {{?}} || {{?}} || {{?}} || {{?}} ||
|-
| MediaTek || MT8693 || Xiaomi Mi Box 3 Pro || {{?}} || {{?}} || {{?}} || {{?}} || {{?}} ||
|-
| MStar || MSO9180 / MSO9180D1R / MSO9280 / MSO9810 || Egreat A9, Kaiboer F5/Q6/C9-M, MeLE V10/X2000, UyeSee T1H, Tronsmart Pavo M9, Xtreamer Prodigy, Zidoo X9 || {{yes}} || {{yes}} || {{?}} || {{?}} || {{?}} ||
|-
| Nvidia || [[Tegra 3]] || [[OUYA]] || {{yes}} || {{no}} || {{no}} || {{no}} || {{no}} ||
|-
| Nvidia || [[Tegra 4]] / [[Tegra 4i]] / [[Tegra 4s]] || ZTE FunBox, Mad Catz M.O.J.O., NanoTech Nuvola NP-1 / NP-C / NP-H1, UTStarcom MC8768, Google ADT-1 (Android TV Developer Kit), [https://en.wikipedia.org/wiki/Shield_Portable Nvidia SHIELD Portable] || {{Yes}} || {{yes}}<br />{{smaller|(CPU)}} || {{?}} || {{no}} || {{no}} ||
|-
| Nvidia || [[Tegra K1|Tegra K1 (TK1)]] || Unuiga Game PC U1, Snail Games OBox, UTStarcom MC8718, [https://en.wikipedia.org/wiki/Shield_Tablet#Shield_Tablet_K1 Nvidia SHIELD Tablet K1] || {{Yes}} || {{yes}}<br />{{smaller|(CPU)}} || {{?}} || {{no}} || {{no}} ||
|-
| Nvidia || [[Tegra X1|Tegra X1 (TX1)]] || [[Nvidia SHIELD TV]] || {{Yes}} || {{yes}}<br />{{smaller|(CPU)}} || {{yes}}<br />{{smaller|(CPU)}} || {{Yes}} || {{yes}} ||
|-
| Qualcomm || Snapdragon 210 / 212 || || {{?}} || {{?}} || {{?}} || {{no}} || {{no}} ||
|-
| Qualcomm || Snapdragon 410 / 412 / 415 / 425 / 430 / 435 || DragonBoard 410c (Turn off "MediaCodec" HW acceleration). Nobel64 Development Board || {{yes}} || {{yes}} || {{?}} || {{no}} || {{no}} ||
|-
| Qualcomm || Snapdragon 600 || [[Amazon Fire TV|Amazon Fire TV (2014)]], Compulab Utilite2, DragonBoard 600c, Inforce 6410Plus Development Board, Intrinsyc Open-Q 600 Development Board || {{yes}} || {{yes}} || {{yes}} || {{no}} || {{no}} ||
|-
| Qualcomm || Snapdragon 610 / 615 / 618 / 620 / 625 || || {{?}} || {{?}} || {{?}} || {{?}} || {{?}} ||
|-
| Qualcomm || Snapdragon 617 || Lenovo Moto G4 || {{yes}} || {{yes}} || {{no}} || {{yes}} || {{yes}} ||
|-
| Qualcomm || Snapdragon 652 || Samsung Galaxy Tab S2 || {{yes}} || {{no}} || {{yes}} || {{yes}} || {{yes}} ||
|-
| Qualcomm || Snapdragon 800 / 801 / 805 || [[Razor Forge TV]] || {{?}} || {{?}} || {{?}} || {{no}} || {{no}} ||
|-
| Qualcomm || Snapdragon 808 / 810 / 820 || HTC M9 (Turn off "MediaCodec" HW accelleration) || {{yes}} || {{yes}} || {{yes}} || {{yes}} || {{?}} ||
|-
| Qualcomm || Snapdragon S4 || || {{yes}} || {{?}} || {{?}} || {{no}} || {{no}} ||
|-
| Realtek || RTD1195 (RTK 1195) || || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || <ref name="Open-source violator"/>
|-
| Realtek || RTD1295 (RTK 1295) || || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || <ref name="Open-source violator"/>
|-
| Rockchip || RK3066 || Imito MX1/MX2, Minix NeoG4/X5, MK808/802, Ugoos UG802/UG007 || {{yes}} || {{?}} || {{no}} || {{no}} || {{no}} ||
|-
| Rockchip || RK3188 || Jesurun DX05, Minix X7, MK802IV, MK809III, MK902, Ugoos UG007B, Tronsmart T428/MK908, CS968, CR11s, J22, GM282, LT88, T-R42, CS919-II, K-R42, CS918, MK888 || {{yes}} || {{yes}}<br />{{smaller|(CPU)}} || {{?}} || {{no}} || {{no}} ||
|-
| Rockchip || RK3036 / RK3126 / RK3128 / RK3288 || Firefly-RK3288, ChipSpark PopMetal, Uyesee G1H, Nagrace HPH NT-V6, Eny Technology EKB318/EKB328, Kingnovel R6/K-R68, Beelink R28, FireFly FirePrime Development Board, Ugoos UT3/UM3, Rikomagic MK902 II, Measy B4S, Ruach A20s, CloudMedia OpenHour, CloudnetGo CR12/CR13CR16, Tronsmart Orion R28, Youku Box K1, Unuiga Game Box 19-6R || {{yes}} || {{yes}}<br />{{smaller|(CPU)}} || {{?}} || {{no}} || {{no}} ||
|-
| Rockchip || RK3368 || Beelink i68, CloudnetGo CR18/CR13 Plus, Eny Technology EKB368, Himedia H7 III, Measy B4T, Ruach A20s-H, Rikomagic MK68, Tronsmart Orion R68, Zidoo X6/X6 Pro || {{yes}} || {{yes}}<br />{{smaller|(CPU)}} || {{yes}}<br />{{smaller|(CPU)}} || {{no}} || {{no}} ||
|-
| Rockchip || RK3228 / RK3228B / RK3228H || || {{yes}} || {{yes}} || {{yes}} || {{yes}} || {{?}} ||
|-
| Rockchip || RK3229 / RK3399 || Firefly-RK3399, MXQ-4K || {{yes}} || {{yes}} || {{yes}} || {{yes}} || {{?}} ||
|-
| Samsung || Exynos 3 Single (formerly Exynos 3110) || || {{yes}} || {{?}} || {{?}} || {{no}} || {{no}} ||
|-
| Samsung || Exynos 4 Dual/Quad series (formerly Exynos 4210 / 4212 /4412 / 4418) || [[ODROID|Hardkernel ODROID-U3/U2/X2]], FriendlyARM NanoPC-T1/NanoPC-T2 || {{yes}} || {{yes}}<br />{{smaller|(CPU)}} || {{yes}}<br />{{smaller|(CPU)}} || {{no}} || {{no}} ||
|-
| Samsung || Exynos 5 Hexa/Octa series (Exynos 5260 / 5410/ 5420 / 5422) || [[ODROID|Hardkernel ODROID-XU/XU2/XU3/XU3 Lite]], Arndale Octa || {{yes}} || {{yes}}<br />{{smaller|(CPU)}} || {{yes}}<br />{{smaller|(CPU)}} || {{no}} || {{no}} ||
|-
| Samsung || Exynos 7 Octa series (Exynos 7410 / 7420 / 7870) || || {{?}} || {{?}} || {{?}} || {{?}} || {{?}} ||
|-
| Samsung || Exynos 7 Octa (Exynos 5433) || Samsung Galaxy Tab S2 (SM-T815) || {{yes}} || {{no}} || {{yes}} || {{yes}} || {{no}} ||
|-
| Samsung || Exynos 8 Octa series (Exynos 8890) || Samsung Galaxy S7 (Europe) || {{yes}} || {{no}} || {{yes}} || {{yes}} || {{yes}} ||
|-
| Samsung || S5P6818 (Octa Core) || FriendlyARM NanoPi M3 || {{?}} || {{?}} || {{?}} || {{?}} || {{?}} ||
|-
| Telechips || TCC898x || || {{?}} || {{?}} || {{?}} || {{?}} || {{?}} ||
|-
| Texas Instruments || OMAP4430 / OMAP4440 / OMAP5430 / OMAP5432 || || {{yes}} || {{?}} || {{?}} || {{no}} || {{no}} ||
|-
| Texas Instruments || Sitara AM3358 / AM3359 || BeagleBoard Black || {{?}} || {{?}} || {{?}} || {{?}} || {{?}} ||
|-
| Texas Instruments || Sitara AM5728 || BeagleBoard-X15 || {{?}} || {{?}} || {{?}} || {{?}} || {{?}} ||
|}

== Common codecs currently without hardware decoding in Kodi ==
Videos encoded with these codecs can only be played back in Kodi using software video decoding using CPU, meaning no decoding tasks are offloaded to optimized VPU or GPU hardware. Many videos may still play back just fine at standard definition resolutions, while others might have severe issues with playback.

As platforms with faster CPUs come out for Android software video decoding using CPU will get better, but do not expect miracles from the average Android box. It still all can depend on how demanding the decoding of that particular video encoding is or how high resolution it uses, and how powerful the CPU is.

* H.264 Hi10P - No hardware decoders for [[Hi10P]] (High 10 Profile, also known 10-bit H.264) currently exist for any ARM hardware. Most H.264 Hi10P videos will not play smoothly as most ARM CPUs are just not powerful enough to software decode it fast enough.
* H.264 MVC - No open source software decoder or hardware decoding for [http://en.wikipedia.org/wiki/Multiview_Video_Coding MVC (Multiview Video Coding)] stereoscopic 3D video decoding currently exist for Kodi on any platform. Kodi relies on FFmpeg for software demuxing and decoding, so Kodi have to wait for FFmpeg to first add software decoding support of MVC for H.264, and for hardware decoding Kodi relies on the SoC chipset hardware manufacturer to add support for this to their SDK (Software Developer Kits) and for the media player box manufacturers to implement that into their firmware images.
* H.265 MVC (HEVC MVC) - No open source software decoder or hardware decoding for [http://en.wikipedia.org/wiki/Multiview_Video_Coding MVC (Multiview Video Coding)] stereoscopic 3D video decoding currently exist for Kodi on any platform. Kodi relies on FFmpeg for software demuxing and decoding, so Kodi have to wait for FFmpeg to first add software decoding support of MVC for H.265 (HEVC), and for hardware decoding Kodi relies on the SoC chipset hardware manufacturer to add support for this to their SDK (Software Developer Kits) and for the media player box manufacturers to implement that into their firmware images.
* RealVideo/RMVB (RV 8/9/10) - There is currently no support in Kodi for RealVideo hardware video decoding, though software decoding of RMVB videos is possible via FFmpeg but can struggle with high definition sources on older or low-end hardware.
* VP8 (WebM v1 video) and VP9 (WebM v2 video) - There is currently no support in Kodi for VP8 hardware video decoding, though software decoding of VP8 videos is possible via FFmpeg but can struggle with high definition sources on older or low-end hardware. Most hardware manufacturers have not even implemented API support for VP8 decoding in the firmware images of Android for their devices, and this is despite the fact that the WebM project licenses VP8 hardware accelerators (RTL IP) to semiconductor companies for 1080p encoding and decoding at zero cost. Nvidia and Rockchip and a few other less known companies does however provide hardware decoding of VP8 in their SoCs, for Tegra 4 and RK29xx respectivly. ARM, Broadcom, Texas Instruments, and Qualcomm as well as ZiiLABS, ST-Ericsson, and Huawei have all announced upcoming support for hardware acceleration of the WebM format and VP8/VP9 codecs. Intel have also let its intention known that they will add hardware-based acceleration for WebM and VP8/VP9 codecs in its future Atom-based chips if the format gains popularity. VP9 does howver to this date not appear to have hardware decoding support in all but the very newest ARM SoCs for Android, such as exanple Nvidia Tegra X1 (TX1) used in Nvidia Shield TV.

==Notes==
<references />

== Device specific info ==
Here are a few device-specific guides/help areas that the community has provided.

{{Device notice}}


<dpl>
category = HTPC
category = Android
format = ,{{list2|%PAGE%}}
</dpl>

{{updated|16}}

[[Category:Android]]
[[Category:Hardware]]

Supported hardware

2018-10-26T10:59:55Z

Gamester17: /* Android */

{{mininav|[[General topics]]{{l2|[[Hardware]]}}|[[Installing]]}}
{{see also|Devices and hardware}}
{{forum link2|1=Want to discuss or ask about what hardware is good for Kodi? Check out the [http://forum.kodi.tv/forumdisplay.php?fid=112 Hardware for Kodi subforum]}}
<section begin="intro" />Kodi is officially supported on a number of operating systems and hardware devices that are designed to be connected directly to a TV. Kodi runs well on what are relatively "underpowered" systems, thanks to hardware video decoding being common on nearly all supported platforms. These requirements don't include what might be required for some "advanced" features, such as PVR, which might require additional hardware. <section end="intro" />

== Android ==
{{see also|Android|Android hardware}}
<section begin="Android" />{{Warning|It is highly recommended for users to not make any hardware purchases in anticipation of running Kodi on Android without first researching the device you want to buy. Before you do buy, make sure multiple people have verified that it works! <big><u>'''''If in doubt, do not buy any hardware!'''''</u></big>}}
* Kodi v17 and later requires Android 5.0 or higher.
* x86 (Intel) or a NEON-compatible ARM-processor, (for example: Nvidia Tegra 3 and newer are fully supported by Kodi, while Tegra 2 and older are not).
* The main aim for the Android port of Kodi is to foremost target media-players/set-top-boxes/sticks that connect to a large screen television and uses a standard remote control as its main interface device, (that is the same market as for HTPC).<section end="Android" />

== iOS ==
{{see also|iOS}}
<section begin="iOS" />
=== ATV2 ===
<section begin="ATV2" />
* As of v15.0, Kodi no longer supports the Apple TV 2.<section end="ATV2" />

=== ATV4 ===
<section begin="ATV4" />
* Apple TV 4 is supported by Kodi. For step by step Installation guide, click the How-To guide below.<section end="ATV4" />

=== iDevices ===
<section begin=iDevices />*To '''[[HOW-TO:Install Kodi for iOS|install Kodi for iOS]]''' you must have one of the following:
** a jailbroken [[w:iDevice|iDevice]] running iOS 6.0 or higher
** a normal iDevice running iOS 6.0 or higher and a Mac running Xcode 7 and higher
* For hardware: iPad (1,2,3,4), iPad Air (1,2), iPad Mini (1,2,3), iPhone (4, 4s, 5, 5c, 5s, 6, 6+, 6s, 6s+), iPod touch (4, 5, 6).<section end=iDevices />
<section end="iOS" />

== Linux ==
{{See also|Linux}}

=== Desktop ===
<section begin="Linux" />
{| class="prettytable" style="background-color:#FFFFFF;"
! CPU
| x86 or x86-64 processor such as: Intel Pentium 4/ Pentium M, AMD Athlon 64 / Opteron, or newer CPU (that support [[w:Streaming SIMD Extensions|SSE2]], which all CPUs made within the last 10-years does).
* If your GPU/VPU does not support hardware video decoding then you will require a fast modern processor is required to decode some 1080p videos encoded in H.264, VC-1/WMV9, HEVC/H.265 VP9, etc
|-
! RAM
|
* '''Recommended:''' 1GB or more in a HTPC media player appliance-like computer dedicated for Kodi, and 2GB or more in a computer for multipurpose use.
|-
! Graphics
|
Kodi will run on most graphics cards made within the last 10-years or so, though for good hardware video decoding support a little newer graphics cards can be required. This includes most cards from AMD/ATI, Intel, or NVIDIA which support OpenGL 2.0 or later.

'''AMD/Intel'''
* '''Minimum:''' [[w:Mesa_(computer_graphics)|Mesa 11.3]] or later
* '''Recommended:''' [[w:Mesa_(computer_graphics)|Mesa 17.1]] or later (required for 10 bit HEVC)
|-
! Video decoding
| For hardware video decoding, which may be necessary on low-performance CPUs to playback 1080p content, make sure your GPU or VPU supports either VAAPI or VDPAU.

{| class="datatable" width="100%"
! !! ATI ( [[w:VDPAU| VDPAU]] or [[w:Video_Acceleration_API| VA-API minimum 1.7.1]] ) !! Intel ( [[w:Video_Acceleration_API| VA-API minimum 1.7.1]] ) !! Nvidia ( [[w:VDPAU| VDPAU]] )
|-
| '''Minimum without HW decoding:''' || [[w:Radeon|ATI Radeon RV710/M92 (HD 4300/4500)]] [[w:Unified Video Decoder#UVD enabled GPUs|Note: These are uvd2.2 cards]] || [[w:Intel HD and Iris Graphics| Arrandale / Clarkdale]] or newer || [[w:GeForce|Nvidia GeForce 6-Series]]
|-
| '''Minimum for HW decoding of 8-bit H.264 and VC-1:''' || [[w:Radeon|AMD/ATI Radeon HD 5000 Series]] or newer || [[w:Intel HD and Iris Graphics| Bay Trail /Sandybridge]] or newer || [[w:GeForce|Nvidia GeForce 8-Series]] or newer
|-
| '''Minimum for HW decoding of 8-bit HEVC (H.265) and VP9:''' || [[w:Radeon|AMD Radeon Rx 300 series]] or newer || [[w:Intel HD and Iris Graphics| Braswell / Skylake]] or newer || [[w:GeForce|Nvidia GeForce 900 series (GM20x)]] or newer
|-
| '''Minimum for HW decoding of 10-bit HEVC (H.265) and VP9:''' || Not available || [[w:Intel_HD_and_Iris_Graphic| Apollo Lake / Kaby Lake]] or newer || Not available
|}
|-
! Drive space
| The Kodi application generally only takes up between 100 to 200 MB of space, depending on how the binary is compiled. Technically speaking, if your hardware supports netbooting, you do not even require a internal storage for either the operating-system or for Kodi.
* '''Minimum:''' 4 to 8GB
* '''Recommended:''' 16GB or more
: Depending on how big your video library is. Most of the space required for Kodi comes from the images/artwork cache, which can be adjusted: [[HOW-TO:Reduce disk space usage]].
|}

{{note|There´s no 304.xxx driver for Ubuntu 18.04 available anymore from the "Graphic Drivers"-ppa. Users who are using GeForce 6-series cards should either stay on an older Ubuntu version or use newer cards}}
<section end="Linux" />

=== Embedded systems (ARM/MIPS-based hardware) ===
Other than OpenGL ES 2.0 graphics support being a must it is very hard to generalize Kodi hardware requirements for Linux-based operating-system distributions on ARM or MIPS based embedded systems. This is partially due to most of the work in this area still being early/on-going in development. For most ARM and MIPS-based devices, hardware video decoding support will also be needed for most high-definition videos, (and possibly even some standard-definition videos). Some newer and faster high-end ARM/MIPS chipset can decode some high-definition video using software video decoding, but those encoded with the latest video codecs.

'''Here are a few popular embedded hardware devices that are known to work with Kodi and Linux:'''

* '''[[Raspberry Pi]]''' - Hardware video decoding support for H.264, MPEG-2, and VC-1. GUI is responsive on most light skins. Official supported by many third-party JeOS (Just enough Operating System) Linux distributions made for Kodi such as [[LibreELEC]], [[GeeXboX]], [[Xbian]], and [[OSMC]]
* '''[[Cubox-i]]''' - Official supported by [[LibreELEC]], [[GeeXboX]] and [[Xbian]]
* '''Various "Android" boxes''' - can run reinstalled with a Linux firmware and boot directly into Kodi. Hardware video decoding for most video codecs, GUI is very responsive on most skins. Running Linux and Kodi on these "Android boxes" will likely result in better performance and enhanced playback capabilities than running Kodi under Android.

=== JeOS implementations for Kodi ===
{{main|JeOS implementations for Kodi}}
{{#lst:JeOS implementations for Kodi|JeOS for Kodi}}

== Mac OS X ==
{{see also|Mac OS X}}
<section begin="Mac OS X" />
*Kodi v17 requires Mac OS X 10.8 or later.
*Kodi v18 (and its nightlies) will at least require 10.9)
*All hardware requirements are the same as those for OS X 10.8. If your computer can run OS X 10.8 or later then your hardware should work just fine with Kodi.<section end="Mac OS X" />

== Windows ==
{{See also|Windows}}
{{Note|Due to changes in code it may be possible that older hardware/videocards are no longer supported. If starting of Kodi fails then try upgrading to last available drivers (or beta drivers).}}
<section begin="Windows" />
{| class="prettytable" style="background-color:#FFFFFF;"
! Windows Version
|
* '''Minimum:''' Windows Vista
* '''Recommended:''' Windows 10
|-
! CPU
| x86 or x86-64 processor such as: Intel Pentium 4/ Pentium M, AMD Athlon 64 / Opteron, or newer CPU (that support [[w:Streaming SIMD Extensions|SSE2]], which all CPUs made within the last 10-years does).
* If your GPU/VPU does not support hardware video decoding then you will require a fast modern processor is required to decode some 1080p videos encoded in H.264, VC-1/WMV9, HEVC/H.265 VP9, etc
|-
! RAM
|
* '''Recommended:''' 1GB or more in a HTPC media player appliance-like computer dedicated for Kodi, and 2GB or more in a computer for multipurpose use.
|-
! Graphics
|
GPU hardware must support at least level [[w:DirectX|DirectX version 9.0c]] however the GPU software drivers must support the [[w:Feature_levels_in_Direct3D#Direct3D_11| DirectX 11 Feature Level 9.1]] (which means the DX11 API has been implemented in the GPU software driver to be compatible with DX9 hardware)
|-
! Video decoding
| On low-performance CPUs to playback 1080p content then hardware video decoding maybe necessary.
{| class="datatable" width="100%"
! !! AMD/ATI !! Intel !! Nvidia
|-
| '''Minimum without HW decoding:''' || [[w:Radeon|ATI Radeon R300 Series (Radeon 9500)]] || [[w:Intel HD and Iris Graphics| Arrandale / Clarkdale]] or newer || [[w:GeForce|Nvidia GeForce 4-Series]]
|-
| '''Minimum for HW decoding of 8-bit H.264 and VC-1:''' || [[w:Radeon| AMD/ATI Radeon HD 3000 Series ]] or newer || [[w:Intel HD and Iris Graphics| Bay Trail /Sandybridge]] or newer || [[w:GeForce|Nvidia GeForce 4-Series]] or newer
|-
| '''Minimum for HW decoding of 8-bit HEVC (H.265) and VP9:''' || [[w:Radeon|AMD Radeon RX 300 series]] or newer || [[w:Intel HD and Iris Graphics| Braswell / Skylake]] or newer || [[w:GeForce|Nvidia GeForce 8-Series]] or newer
|-
| '''Minimum for HW decoding of 10-bit HEVC (H.265) and VP9:''' || [[w:Radeon|AMD Radeon 400 series]] or newer || [[w:Intel_HD_and_Iris_Graphic| Apollo Lake / Kaby Lake]] or newer || [[w:GeForce|Nvidia GeForce 8-Series]] or newer
|}
|-
! Drive space
| The Kodi application generally only takes up between 100 to 200 MB of space, depending on how the binary is compiled. Technically speaking, if your hardware supports netbooting, you do not even require a internal storage for either the operating-system or for Kodi.
* '''Minimum:''' 4 to 8GB
* '''Recommended:''' 16GB or more
: Depending on how big your video library is. Most of the space required for Kodi comes from the images/artwork cache, which can be adjusted: [[HOW-TO:Reduce disk space usage]].
|}<section end="Windows" />

{{Updated|17}}

[[Category:Manual]]
[[Category:Hardware|*]]
[[Category:Installation]]
[[Category:General topics]]

Kodi v18 (Leia) changelog

2018-10-26T10:53:28Z

Gamester17: /* Android Specific */

{{mininav|[[Releases]] {{l2| [[Leia]] }} }}

{{notice|Kodi's journey via non-alpha/beta v18 (Leia) releases is currently underway. As such, these new features/functions and API changes is a placeholder containing changes to the current Kodi mainline (the git master tree repository on GitHub). This is listing changes committed to the master branch after Krypton branching. The many features/functions and API additions, alterations or removal are only subject to change during the Alpha stages. The Beta stage is all about stability and bug fixing. }}
{{incomplete}}
{{future|18}}

{{see also|Kodi v18 (Leia) FAQ|Leia API changes|Releases}}

This is the Kodi Wiki version of a condensed changelog for the future Kodi v18.x version (codename: "Leia") releases with a summary of the most important core features and functions as well as other notable changes to key areas of the application software or its user interface. Please note that this condensed changelog version is not meant bug-fixes, nor minor refactoring or cosmetic changes.

== Changelog ==

=== Gaming (Games interface and Game Clients)===
Note! Also see "Input System (Input Manager and Input APIs" section for Input System related to game controllers
* Added a "[[Games]]" window to GUI (games are managed using a basic file browser as a game library does not exist yet)
* Added a RetroPlayer player core supporting [[Game_Add-ons|game clients addons]] as well as emulator cores via [[libretro]] API<ref name="RetroPlayer">RetroPlayer http://forum.kodi.tv/showthread.php?tid=164725</ref><ref>http://github.com/xbmc/xbmc/pull/11022</ref>
* Added extentions to Kodi's Addons AP to support Game Client Addons, supporting Kodi's VFS (Virtual File System), etc.<ref name="RetroPlayer"/>
* Added support for Game Client Addons as new type of addons with just-in-time emulator installation<ref name="RetroPlayer"/>
* Added a Games window and Game OSD (On-Screen-Display) entries to the GUI<ref name="RetroPlayer"/><ref>https://github.com/xbmc/xbmc/pull/12367</ref>
* Added a gaming and game configuration interface for Game settings to the GUI<ref name="RetroPlayer"/>
* Added support for Game Info Tags (game info tag) and exposed properties to Python list items<ref name="RetroPlayer"/>
* Added a savestate (savestate) manager to Kodi for games<ref>http://github.com/xbmc/xbmc/pull/11034</ref>
* Added initial support for basic gameplay persistence (auto-save & auto-load)<ref>https://github.com/xbmc/xbmc/pull/12434</ref>
* Added support for in-game (save RAM) saves<ref>http://github.com/xbmc/xbmc/pull/11380</ref>
* Added support for Keyboard players via Joystick Emulation<ref name="RetroPlayer"/>
* Added Game API acbstraction for game controller multitaps (a.k.a. hubs) including topology GUI display<ref>https://github.com/xbmc/xbmc/pull/13499</ref>
* Added Game API acbstraction to support gamepad/joystick remapping for games (per game-addon)
* Added Game API acbstraction to support keyboard remapping for games (per game-addon)<ref>https://github.com/xbmc/xbmc/pull/13374</ref>
* Added Game API acbstraction to support mouse remapping for games (per game-addon)<ref>https://github.com/xbmc/xbmc/pull/13482</ref>
* Added support for libretro API and game cores (emulators and games) that support it as binary addons
* Added [[Game_Add-ons|game clients addons]] for many popular third-party game console emulators and native open source games *
** ''* [[Game_Add-ons|Game clients addons]] for Kodi is changing quickly so checkout the [[Game_Add-ons|game clients addons]] article for a current list''
* ?

=== Live TV and PVR (Personal Video Recorder) ===
* Added new settings for 'Startup action' and add 'Play TV/Radio <ref>https://github.com/xbmc/xbmc/pull/12548</ref>
* Added support for global direct channel number input & global unique channel numbers<ref>https://github.com/xbmc/xbmc/pull/13135</ref><ref>https://github.com/xbmc/xbmc/pull/11434</ref>
** Added support for no delay on switch to previous channel with key 0 when using direct channel number input<ref>https://github.com/xbmc/xbmc/pull/13232</ref>
* Added context menu support for Estuary (skin) PVR home screen widgets <ref>https://github.com/xbmc/xbmc/pull/10870</ref>
* Added percent played progress bar to PVR info panel (for recordings) in Estuary (skin)<ref>https://github.com/xbmc/xbmc/pull/13338</ref>
* Added Info support to recently played channel widget to Estuary (skin) home screen <ref>https://github.com/xbmc/xbmc/pull/12254</ref>
* Added episode name to Live TV, recordings OSD sub label, and cleanup seekbar for Live TV in Estuary (skin) <ref>https://github.com/xbmc/xbmc/pull/12306</ref>
* Added Season/Episode info in Guide window and dialog in Estuary (skin)<ref>https://github.com/xbmc/xbmc/pull/13300</ref>
* Added support for next and previous buttons in OSD Timeshift window<ref>https://github.com/xbmc/xbmc/pull/14387</ref>
* Added feature to prefill recordings folder with timer title in the timer settings dialog<ref>https://github.com/xbmc/xbmc/pull/11679</ref>
* Added support for radio channel groups to the channelgroup manager<ref>https://github.com/xbmc/xbmc/pull/11877</ref>
* Added support for a 'Smart selection' of EPG events feature to the guide window<ref>https://github.com/xbmc/xbmc/pull/11782</ref>
* Added 'Go to date' context menu item to the guide window<ref>https://github.com/xbmc/xbmc/pull/13282</ref>
* Added support for channel groups selector to the guide window<ref>https://github.com/xbmc/xbmc/pull/13364</ref>
* Added possibility to switch between horizontal and vertical epg grid view to the guide window <ref>https://github.com/xbmc/xbmc/pull/11958</ref>
* Added support to sort content by channel number/channel name/last played, support sort order to the Guide window<ref>https://github.com/xbmc/xbmc/pull/14231</ref>
* Added support next/previous chapter in PVR recordings<ref>https://github.com/xbmc/xbmc/pull/13164</ref>
* Improved PVR seekbar and info dialog in Estuary (skin) <ref>https://github.com/xbmc/xbmc/pull/13158</ref>
* Improved PVR info panel, info dialog, and recordings window in Estuary (skin)<ref>https://github.com/xbmc/xbmc/pull/12416</ref><ref>https://github.com/xbmc/xbmc/pull/13255</ref>
* Improved support for enabling multiple PVR client addons<ref>https://github.com/xbmc/xbmc/pull/12959</ref>
* Improved support for for subchannel numbers support (ATSC)<ref>https://github.com/xbmc/xbmc/pull/13069</ref>
* Improved OSD Timeshift GUI<ref>https://github.com/xbmc/xbmc/pull/14316</ref><ref>https://github.com/xbmc/xbmc/pull/14386</ref>
* Improved the guide window for better consistency and readability <ref>https://github.com/xbmc/xbmc/pull/13402</ref>
* Changed GUI actions to eliminate duplicate and dead code (major GUI refactoring for PVR and LiveTV)
* Changed implementation of EPG search filter (EPG search dialog) completely<ref>https://github.com/xbmc/xbmc/pull/11570</ref><ref>https://github.com/xbmc/xbmc/pull/12001</ref>
* Changed Guide Window removing obsolete views "channel", "now" and "next"<ref>https://github.com/xbmc/xbmc/pull/10838</ref>
* Changed "play minimized" settings handling <ref>https://github.com/xbmc/xbmc/pull/11203</ref>
* Changed 'epg.lingertime' to an official setting, remove the respective advanced setting<ref>https://github.com/xbmc/xbmc/pull/12740</ref>
* Changed shared channel selection into an optional setting<ref>https://github.com/xbmc/xbmc/pull/13237</ref>
* Removed obsolete and unused setting 'pvrplayback.scantime' <ref>https://github.com/xbmc/xbmc/pull/12800</ref>
* Removed channel guide button from EPG event info dialog, add 'channel guide' to context menu<ref>https://github.com/xbmc/xbmc/pull/12526</ref>
* Removed setting 'hide connection lost warning' <ref>https://github.com/xbmc/xbmc/pull/11500</ref>
* Removed non-working recording settings defaults <ref>https://github.com/xbmc/xbmc/pull/11746</ref>
* Recordings window: Content view filter <ref>https://github.com/xbmc/xbmc/pull/11704</ref>
* PVR-Addon API changes <ref>https://github.com/xbmc/xbmc/pull/12028</ref><ref>https://github.com/xbmc/xbmc/pull/12303</ref><ref>https://github.com/xbmc/xbmc/pull/12552</ref><ref>https://github.com/xbmc/xbmc/pull/12609</ref><ref>https://github.com/xbmc/xbmc/pull/12660</ref><ref>https://github.com/xbmc/xbmc/pull/12689</ref><ref>https://github.com/xbmc/xbmc/pull/12755</ref><ref>https://github.com/xbmc/xbmc/pull/13228</ref><ref>https://github.com/xbmc/xbmc/pull/13720</ref><ref>https://github.com/xbmc/xbmc/pull/14002</ref><ref>https://github.com/xbmc/xbmc/pull/14086</ref>
* Added, updated, and improved PVR backend clients addons for popular third-party external [[PVR backend]] platforms:
** New: [[Add-on:Zattoo PVR Client|Zattoo PVR Client]] PVR Addon backend client maintained and available from Kodi's community
** New: [[Add-on:Teleboy PVR Client|Teleboy PVR Client]] PVR Addon backend client maintained and available from Kodi's community
** New: [[Add-on:Sledovanitv.cz PVR Client|Sledovanitv.cz PVR Client]] PVR Addon backend client maintained and available from Kodi's community
** [[Add-on:PVR Demo Client|PVR Demo Client]] dummy addon with fake (method stub) [[PVR backend]] for [[PVR]] skinning and regression testing
** [[Add-on:IPTV Simple Client|IPTV Simple Client]] PVR Addon backend client maintained and available from Kodi's community
** [[Add-on:FilmOn PVR Client|FilmOn]] PVR Addon backend client maintained and available from Kodi's community
** [[Add-on:Stalker Client|Stalker Middleware]] PVR Addon backend client maintained and available from Kodi's community
** [[Add-on:HDHomeRun PVR|HDHomeRun]] PVR Addon backend client maintained and available from Kodi's community
** [[Add-on:Digital Devices Octopus NET Client|Digital Devices Octopus NET Client]] PVR Addon backend client maintained and made available by [http://digitaldevices.de/home/ Digital Devices]
** [[Add-on:VU+ / Enigma2 Client|Enigma2 (Dreambox / Vu+ / DBox2)]] PVR Addon backend client maintained and available from Kodi's community
** [[Add-on:VBox TV Gateway PVR Client|VBox TV Gateway]] PVR Addon backend client maintained and available from Kodi's community
** [[Add-on:Njoy N7 PVR Client|Njoy Digital (N7)]] PVR Addon backend client maintained and available from Kodi's community
** [[Add-on:PCTV Systems Client|PCTV Systems (Broadway)]] PVR Addon backend client maintained and available from Kodi's community
** [[Add-on:Tvheadend HTSP Client|Tvheadend HTSP Client]] PVR Addon backend client maintained and available from Kodi's community
** [[Add-on:VDR VNSI Client|VDR VNSI Client]] PVR Addon backend client maintained and available from Kodi's community
** [[Add-on:MythTV PVR Client|MythTV PVR Client]] Addon backend client maintained and available from the Kodi's community
** [[Add-on:NextPVR PVR Client|NextPVR (former GB-PVR)]] PVR Addon backend client maintained and available from Kodi's community
** [[Add-on:Argus TV Client|Argus TV (former ForTheRecord)]] PVR Addon backend client maintained and available from Kodi's community
** [[Add-on:DVBLink PVR Client|DVBLink PVR Client]] Addon backend client maintained and available from Kodi's community
** [[Add-on:DVBViewer Client|DVBViewer Client]] PVR Addon backend client maintained and available from Kodi's community
** [[Add-on:MediaPortal PVR Client|MediaPortal PVR Client]] Addon backend client maintained and available from Kodi's community
** [[Add-on:PVR.WMC|WMC (Windows Media Center)]] PVR Addon backend client maintained and available from Kodi's community
* ?

=== Add-ons Framework, API, and Manager ===
For full changelogs of all Addons APIs, see [[Leia API changes]], [https://forum.kodi.tv/showthread.php?tid=324598 JSON-RPC], and [http://forum.kodi.tv/forumdisplay.php?fid=26 Add-ons] Development Forums
* Implemented a Python 3 interpreter inside Kodi (plus enforcing Python 2 & 3 compatibility in Leia addon repository)<ref>https://kodi.tv/article/attention-addon-developers-migration-python-3</ref>
* Implemented online binary addon repository from which Kodi can now automatically installs/updates binary addon<ref>https://kodi.tv/article/kodi-v18-binary-add-ons-repository</ref><ref>https://github.com/xbmc/repo-binary-addons</ref>
* Major refactoring of Kodi's core handling and GUI management of binary addons<ref>http://github.com/xbmc/xbmc/pulls?q=label%3A%22Binary+Addons%22+is%3Aclosed</ref>
* Added framework to support VFS (Virtual File System) as binary addons<ref>http://github.com/xbmc/xbmc/pull/8966</ref>
* Added framework support for binary addons for video decoder codecs<ref name="Addon video codec implementation">https://github.com/xbmc/xbmc/pull/12340</ref>
* Added framework support for binary addons for image (picture) decoder codecs
* Added extentions to Kodi's Addons API to support binary addons for video decoder codecs<ref name="Addon video codec implementation"/>
* Added extentions to Kodi's Addons API to support binary addons for image decoder codecs
* Added support for Python addons to use PyCryptoDome crypto module for decryption<ref>https://github.com/xbmc/xbmc/pull/11477</ref>
* Added option to pass HTTP cookies with AVOption to Kodi's Video Player<ref>https://github.com/xbmc/xbmc/pull/12257</ref>
* Added support to allow addons to edit all used controls on their processed window<ref>https://github.com/xbmc/xbmc/pull/12259</ref>
* Added support to allow Python addons to set the videoinfotag path<ref>http://github.com/xbmc/xbmc/pull/11012</ref>
* Added support to allow Python addons to get/set the dbid of a (music) listitem<ref>http://github.com/xbmc/xbmc/pull/10858</ref>
* Added support for mediatype to musicinfotag tag retrieving via Python API<ref>http://github.com/xbmc/xbmc/pull/11110</ref>
* Added support "int/float slider" to Kodi's Python API<ref>http://github.com/xbmc/xbmc/pull/11230</ref>
* Added support "setContent for mediawindows" to Kodi's Python API<ref>http://github.com/xbmc/xbmc/pull/11258</ref>
* Added help for load of shared library and allow the use of their own addon temp folder<ref>https://github.com/xbmc/xbmc/pull/12379</ref>
* Added support to inspect add-on dependencies prior to installation<ref>https://github.com/xbmc/xbmc/pull/12242</ref>
* Added ability to remove add-on settings upon uninstall<ref>https://github.com/xbmc/xbmc/pull/11499</ref>
* Changed to new addon gui interface for list items to use on addon window<ref>https://github.com/xbmc/xbmc/pull/12214</ref>
* Changed service addons to use event handlers instead of synchronous addon hooks<ref>https://github.com/xbmc/xbmc/pull/12370</ref>

=== Input System (Input Manager and Input APIs) ===
* Improved the input manager and input API system for keyboards, mouses, and game controllers<ref name="Controller input system">PR #8807 Controller input system http://github.com/xbmc/xbmc/pull/8807</ref>
* Updated "Peripheral Addons" for game controllers, gamepads, joysticks, and input peripherals profiles (in Kodi-game repo<ref>http://github.com/kodi-game/ kodi-game repo on GitHub</ref>):
** [http://github.com/xbmc/peripheral.joystick Joystick Controller Addon]
** [http://github.com/kodi-game/peripheral.xarcade X-Arcade (XGaming Tankstick) support for Kodi Addon]
** [http://github.com/kodi-game/peripheral.steamcontroller Steam Controller (gamepad) Addon]
** [http://github.com/kodi-game/kodi-game-controllers/tree/master/addons/game.controller.default Default Game Controller Addon (reference game controller addon based on Xbox 360 gamepad)]
*** [https://github.com/kodi-game/controller-topology-project/tree/master/addons PlayStation Game Controller Addon]
*** [https://github.com/kodi-game/controller-topology-project/tree/master/addons Nintendo NES Game Controller Addon]
*** [https://github.com/kodi-game/controller-topology-project/tree/master/addons Nintendo SNES Game Controller Addon]
*** [https://github.com/kodi-game/controller-topology-project/tree/master/addons Nintendo N64 Game Controller Addon]
*** [https://github.com/kodi-game/controller-topology-project/tree/master/addons Nintendo GBA Game Controller Addon]
*** [https://github.com/kodi-game/controller-topology-project/tree/master/addons Sega Genesis Game Controller Addon]
*** [https://github.com/kodi-game/controller-topology-project/tree/master/addons Sega Dreamcast Game Controller Addon]
* ?

=== GUI Engine (Skinning Engine) ===
For full changelog on changes to the skinning engine, see [[Leia API changes]] and the [http://forum.kodi.tv/showthread.php?tid=298565 Skin Development Forum]
* Added windows to support Games and Game OSD in the new default skins (Estuary and Estouchy)
* Added player process info dialog to Kodi's default skin (Estuary)<ref>https://github.com/xbmc/xbmc/pull/11718</ref>
* Added support for addons to use banner and ClearLogo<ref>https://github.com/xbmc/xbmc/pull/12244</ref>
* Added support for skins/gui to allow implicit container referencing for non-media windows<ref>http://github.com/xbmc/xbmc/pull/10883</ref>
* Added support for addons to add "Enable/Disable" to context menu<ref>http://github.com/xbmc/xbmc/pull/11124</ref>
* Added support for remember last used keyboard layout in GUI<ref>http://github.com/xbmc/xbmc/pull/11242</ref>
* Added support for ISO 639-2/T language code retrieval (required by libbluray)<ref>https://github.com/xbmc/xbmc/pull/12258</ref>
* Added window that display Kodi privacy policy in GUI settings under system info<ref>https://github.com/xbmc/xbmc/pull/10785</ref>
* Added support to map a key to browse for subtitle in video fullscreen window<ref>https://github.com/xbmc/xbmc/pull/11649</ref>
* Improved Kodi's GUI engine with optimizations for message handling and SmartRedraw<ref>https://github.com/xbmc/xbmc/pull/12213</ref>
* Improved Kodi's GUI engine support for scaling container layouts<ref>http://github.com/xbmc/xbmc/pull/11229</ref>
* Improved Kodi's GUI engine by allowing %-values for origin, camera and animation attribs<ref>http://github.com/xbmc/xbmc/pull/11233</ref>
* Changed so that context menu reloading loads async to aviod GUI lockup on wait<ref>https://github.com/xbmc/xbmc/pull/11841</ref>
* Updated guilib ABI (for libgui) to version 5.13.0<ref>http://github.com/xbmc/xbmc/pull/11306</ref>
* Updated keyboard layout for some languages and added support Croatian, Slovenian, and Thai (Kedmanee)
* Updated image resource addons (as example weather icons, weather fanart, studio logos, and genre icons)
* ?

=== Platform Independent Playback ===
* Added support for "InputStream" (input stream) addons to pass CryptoSession flags field<ref>https://github.com/xbmc/xbmc/pull/12428</ref>
* Added support for BD-J / Blu-ray Disc Java menu support (requires system Java runtime enviroment)<ref>https://github.com/xbmc/xbmc/pull/12339</ref><ref>https://github.com/xbmc/xbmc/pull/12310</ref>
* Added support for Blu-ray Disc detection and use provided meta data for Blu-ray Disc names<ref>https://github.com/xbmc/xbmc/pull/12488</ref>
* Added support for video buffers to be used by decoders and renderers<ref name="VideoPlayer updates for Leia">https://github.com/xbmc/xbmc/pull/12212</ref>
** Added support for platforms to register custom buffers, like example dma<ref name="VideoPlayer updates for Leia"/>
* Added a VC1-Packet bitstream parser implementation for improved VC-1 playback<ref>http://github.com/xbmc/xbmc/pull/11417</ref>
* Added and updated many (binary) audio decoder and encoder addons for Kodi
* Added a few (binary) video decoder addons for Kodi<ref name="Addon video codec implementation"/>
* Added a "RAW" (libraw based) image decoder addon to Kodi<ref>https://github.com/xbmc/xbmc/pull/11671</ref>
* Improved MMAL playback of H.264 MVC (Blu-ray 3D) stereoscopic video with framepacking decoding on Raspberry Pi
* Improved Stereoscopic 3D playback of 3D videos (as well as better 2D playback of 3D videos)
* Improved and enhanced Blu-ray support (including updated libbluray dependecies from the VideoLAN project<ref>https://github.com/xbmc/xbmc/pull/12305</ref><ref>http://git.videolan.org/?p=libbluray.git;a=blob;f=ChangeLog</ref>
* Improved support for "InputStream" (input stream) addons as system addons
* Updated "InputStream" (input stream) client addons for common network streaming protocols and popular services:
** [http://github.com/xbmc/xbmc/tree/master/addons/kodi.inputstream InputStream Addon (default reference InputStream Addon by Team Kodi]
** [http://github.com/mapfau/inputstream.test Test InputStream Addon (Test InputStream Addon for Kodi's new inputstream interface]
** [http://github.com/peak3d/inputstream.adaptive Adaptive InputStream Addon (InputStream Client addon for several manifest types)]
** [http://github.com/xbmc/repo-binary-addons/tree/master/inputstream.rtmp RTMP InputStream Addon (InputStream Client for RTMP streams using librtmp)]
** [http://github.com/peak3d/inputstream.mpd MPD (MPEG-DASH) InputStream Addon]
** [http://github.com/peak3d/inputstream.smoothstream SmoothStream InputStream Addon for MS-SSTR (SmoothStreamingMedia) Smooth Streaming Protocol]
** [http://github.com/mapfau/inputstream.nxmsl NXMSL InputStream Addon for Netflix style manifests over MSL]
* Updated FFmpeg multimedia codec and demux libraries to stable branch release version [http://www.ffmpeg.org/download.html#release_4.0.2 FFmpeg 4.0 (4.0.2)]<ref>http://git.videolan.org/?p=ffmpeg.git;a=blob_plain;f=Changelog;hb=release/4.0.2 FFmpeg 4.0.2 release changelog</ref><ref>https://github.com/xbmc/xbmc/pull/14212</ref>
* Removed certain audio codecs from core and made them into audio decoder and audio encoder binary add-ons
* Removed certain video codecs from core and made them into video decoder binary add-ons<ref name="Addon video codec implementation"/>
* Removed certain image codecs from core and made them into image decoder binary add-ons
* ?

=== General Library ===
* Added support to use the Favourites function in context menus<ref>https://github.com/xbmc/xbmc/pull/11967</ref>
* Added support for context menus to favourites home screen widget<ref>https://github.com/xbmc/xbmc/pull/11929</ref>
* Added support to "Sort By Date Added" in Music Video title node<ref>https://github.com/xbmc/xbmc/pull/12495</ref>

=== Music Library ===
* Added an option to rescan the music file tags for existing items in the library <ref>https://github.com/xbmc/xbmc/pull/11557</ref>
* Added processing of WRITER tag for ID3 v2, Vorbis and APE formats <ref>https://github.com/xbmc/xbmc/pull/11735</ref>
* Added processing of ARTISTSORT (TSOP), ALBUMARTISTSORT (TS02) and COMPOSERSORT (TSOC) tags to provide a sort name for artists. <ref>https://github.com/xbmc/xbmc/pull/11738</ref>
* Added a new dialog for selection of both artist and album scraper addons, and their settings.<ref>https://github.com/xbmc/xbmc/pull/12987</ref><ref>https://github.com/xbmc/xbmc/pull/12943</ref>
* Added additional artist data that Musicbrainz provides: type (person, group, orchestra, choir etc.), gender, and disambiguation comments that help to differentiate artists with the same name <ref>https://github.com/xbmc/xbmc/pull/12963</ref>
* Added an Artist Information Folder - a single location for artist artwork and nfo. This solves numerous issues related to artwork, artist data import and general folder and file structure <ref>https://github.com/xbmc/xbmc/pull/12891</ref>
* Added support for Extended Artwork, making the local art that is picked up automatically on scan configurable. <ref>https://github.com/xbmc/xbmc/pull/13352</ref><ref>https://github.com/xbmc/xbmc/pull/13848</ref><ref>https://github.com/xbmc/xbmc/pull/13491</ref><ref>https://github.com/xbmc/xbmc/pull/13101</ref><ref>https://github.com/xbmc/xbmc/pull/13871</ref>
* Added an option to prefer scraped album covers to embedded images <ref>https://github.com/xbmc/xbmc/pull/13812</ref>
* Added a filter to sort music items by media source <ref>https://github.com/xbmc/xbmc/pull/14012</ref><ref>https://github.com/xbmc/xbmc/pull/14082</ref>
* Improved use of BAND and ENSEMBLE (Vorbis and APE) tags. <ref>https://github.com/xbmc/xbmc/pull/11735</ref>
* Improved handling of duplicate MusicBrainzTrackID within the same album<ref>https://github.com/xbmc/xbmc/pull/12079</ref>
* Improved handling of Cue Sheets<ref>https://github.com/xbmc/xbmc/pull/12082</ref>
* Improved online scraping of additional artist and album information making better use of Musicbrainz IDs<ref>https://github.com/xbmc/xbmc/pull/12120</ref><ref>https://github.com/xbmc/xbmc/pull/12597</ref>
* Improved on clean installs, change default song sort order to Track Number <ref>https://github.com/xbmc/xbmc/pull/12834</ref>
* Improved FileItem::IsSamePath for albums and artists to prevent false matches<ref>https://github.com/xbmc/xbmc/pull/13585</ref>
* Improved album genre inconsistencies<ref>https://github.com/xbmc/xbmc/pull/13042</ref>
* Improved performance by avoiding unnecessary db access by GUI when app processing GUI_MSG_UPDATE_ITEM messages<ref>https://github.com/xbmc/xbmc/pull/13640</ref>
* Improved support for fetching local art for multi-folder albums (disc sets) <ref>https://github.com/xbmc/xbmc/pull/13769</ref>
* Changed Artist/Album Information Dialog <ref>https://github.com/xbmc/xbmc/pull/13672</ref>
* Changed Song Information Dialog <ref>https://github.com/xbmc/xbmc/pull/13533</ref>

=== Web Scrapers ===
* Added support for Python (script) based web scrapers for Kodi<ref>http://github.com/xbmc/xbmc/pull/9984</ref>
* Refactored and updated many XML based scrapers in Kodi for music, movies, tv shows, and music videos
* Updated music, movies, tv shows, and music video scrapers for Kodi
* ?

=== AudioEngine ===
* Added a new Sndio sink for [[AudioEngine#ActiveAE|ActiveAE]] for BSD, other BSD Unix based systems, and Linux<ref>https://github.com/xbmc/xbmc/pull/11962</ref>
* Improved the default cross-platform event driven active state machine pattern [[AudioEngine#ActiveAE|ActiveAE]] (Kodi's [[AudioEngine]])
* Improved ALSA sink for [[AudioEngine#ActiveAE|ActiveAE]] for Linux Desktop and generic Linux based Embedded Systems
* Improved PulseAudio sink for [[AudioEngine#ActiveAE|ActiveAE]] for Linux Desktop
* Improved OSS (Open Sound System) sink for [[AudioEngine#ActiveAE|ActiveAE]] for BSD, like FreeBSD and similar BSD Unix based systems
* Improved AUDIOTRACK sink for [[AudioEngine#ActiveAE|ActiveAE]] for [[Amlogic]]
* Improved Pi Audio sink for [[AudioEngine#ActiveAE|ActiveAE]] for [[Raspberry Pi]]
* Improved DirectSound sink for [[AudioEngine#ActiveAE|ActiveAE]] for Windows
* Improved WASAPI sink for [[AudioEngine#ActiveAE|ActiveAE]] for Windows
* Improved CoreAudio sink for [[AudioEngine#ActiveAE|ActiveAE]] for (Mac) OS X and iOS
* Improved Darwin sink for [[AudioEngine#ActiveAE|ActiveAE]] for (Mac) OS X and iOS
* Renamed AE_SINK to KODI_AE_SINK
* ?

=== Other ===
* Added a new unified setting for "Startup action" and added "Play TV/Radio"<ref>https://github.com/xbmc/xbmc/pull/12548</ref>
* Added support to build Kodi with support for Bluetooth<ref>http://github.com/xbmc/xbmc/pull/11137</ref>
* Added possibility for CMake build system to add additional libraries on install<ref>https://github.com/xbmc/xbmc/pull/12423</ref>
* Added and updated many audio visualization and screensaver addons for Kodi<ref>https://github.com/xbmc/repo-binary-addons</ref>
* Improved Kodi's JSON-RPC API
* Improved code stability, performance. and security, as well as general code clean-up in many core areas
* Improved compiling/building and code documentation (following doxygen coding guidelines)
* Changed to use spdlog for Kodi logging as well as improved and further optimized logging (including debug logs)<ref>https://github.com/xbmc/xbmc/pull/11833</ref>
* Changed XML format of setting values for Kodi's settings configuration<ref>https://github.com/xbmc/xbmc/pull/12277</ref>
* Updated and improved mappings for new and existing remote controls
* Updated default web interface (webinterface is called "Chorus2" and is currently at version 2.4.4)<ref>https://github.com/xbmc/xbmc/pull/11872</ref>
* Updated critical dependency libraries such as openssl, gnutls, and CMake (used to compile Kodi and its binary addons)
* Removed last dependencies of SDL (Simple DirectMedia Layer) which was hardware abstraction for input devices<ref>https://github.com/xbmc/xbmc/pull/12272</ref><ref>https://github.com/xbmc/xbmc/pull/11881</ref>
* Removed all glew (libglew library) dependencies in Kodi's code<ref>http://github.com/xbmc/xbmc/pull/11128</ref>
* ?

=== Android Specific ===
* Moved to Android API 26 and SDK 26 with NDK 18 as minimum (meaning at least Android 5.0 is still required)
* Added support for speech-to-text in Kodi OSD keyboard on Android TV (triggered by voice button on remote)
* Added support for Android to move the Kodi app to SD card<ref>https://github.com/xbmc/xbmc/pull/12168</ref>
* Added support for Android TV Leanback search and recommendations meta data from Kodi<ref>|https://github.com/xbmc/xbmc/pull/11901</ref>
** Default setting for Android TV Leanback suggestion to random unwatched movies and music albums<ref>https://github.com/xbmc/xbmc/pull/11963</ref>
* Changed Rendertype from GUILayer to VideoLayer for Android MediaCodecSurface<ref>https://github.com/xbmc/xbmc/pull/12097</ref>
* Changed to use NDK native C interface for Android MediaCodec (for performance gains)<ref>https://github.com/xbmc/xbmc/pull/11931</ref>
* Changed to support ZeroConf via native Android API (and deprecates mDNSresponder)<ref>http://github.com/xbmc/xbmc/pull/11393</ref>
* Changed to support network information via native Android API (and deprecates POSIX)<ref>https://github.com/xbmc/xbmc/pull/12243</ref>
* Changed handling of Kodi's Java interfaces via JNI for better consistency<ref>https://github.com/xbmc/xbmc/pull/12292</ref>
* ?

=== BSD Specific ===
* Improved Kodi support for [http://en.wikipedia.org/wiki/Berkeley_Software_Distribution BSD (operating system)] on FreeBSD, PC-BSD, and other similar BSD platforms
* Improved VAAPI (Video Acceleration API) support (requires VAAPI compatible hardware and drivers)
* Improved VDPAU (NVIDIA) Hardware Video Acceleration (requires VDPAU compatible hardware and drivers)
* ?

=== Linux Specific ===
* Added support for a generic DRM/KMS implementation using GBM to create required surfaces<ref>https://github.com/xbmc/xbmc/pull/11955</ref>
* Added support for Mir windowing system (Mir 1.0) for Kodi<ref>http://github.com/xbmc/xbmc/pull/10898</ref> and added support for VAAPI on Mir using DRM<ref>http://github.com/xbmc/xbmc/pull/11040</ref>
* Added support for the middle mouse button on embedded platforms<ref>https://github.com/xbmc/xbmc/pull/11956</ref>
* Added support more yuv420p bitwidths for direct rendering on Linux<ref>https://github.com/xbmc/xbmc/pull/12479</ref>
* Added support for using VAAPI hardware video decoding with OpenGL ES<ref>https://github.com/xbmc/xbmc/pull/12113</ref>
* Added support for build Kodi with imx support using CMake<ref>http://github.com/xbmc/xbmc/pull/11288</ref>
* Moved the CMake build system to the top of the code tree (moved to root)<ref>http://github.com/xbmc/xbmc/pull/10446</ref>
* Improved support for UltraHD decoding / 4K resolution output when hardware supports it
* Improved ARM processor architecture (using [[Raspberry Pi]] as reference device)
* Improved OpenGL ES and EGL support (using [[Raspberry Pi]] as reference device)
* Improved VAAPI (Video Acceleration API) support (requires VAAPI compatible hardware and drivers)
* Improved VDPAU (NVIDIA) Hardware Video Acceleration (requires VDPAU compatible hardware and drivers)
* Improved XvBA (AMD/ATI) Hardware Video Acceleration (requires XvBA compatible hardware and drivers)
* Improved dedicated AMLCodec hardware accelerated video decoding support for Linux on Amlogic devices
* Removed the unused and unmaintained OpenMAX video decoder from Kodi's VideoPlayer<ref>https://github.com/xbmc/xbmc/pull/12197</ref>
* Removed support for autotools based build system for Kodi and binary addons (in favour of CMake)<ref>http://github.com/xbmc/xbmc/pull/10429</ref>
* ?

=== iOS Specific ===
* Added support for iOS 10.0 by adding support for compiling Kodi with Xcode 8 IDE and iOS SDK 10.0<ref>https://github.com/xbmc/xbmc/pull/10539</ref>
* Improved Apple VDADecoder Video Acceleration support for iOS (on iPad, iPhone, and iPod iDevices)
* Improved support for TVOS (Apple's iOS fork for Apple TV 4) in Kodi mainline
* Improved support for iOS on ARM64 (64-bit iOS)
* ?

=== OS X Specific ===
* Added support for compiling Kodi with Xcode 8 IDE for OSX 10.11 (El Capitan) and macOS 10.12 (Sierra)
* Improved Apple VDADecoder Video Acceleration support for (Mac) OS X
* ?

=== Windows Specific ===
* Added support to build Kodi for Windows 64 / Windows for Intel 64-bit (x86-64)<ref>https://github.com/xbmc/xbmc/pull/12065</ref>
* Added support for 3D LUT (3D Lookup Table) and dithering to Windows video renderer<ref name="WinRenderer re-work">https://github.com/xbmc/xbmc/pull/12475</ref>
* Improved support to compiling Kodi for Microsoft's UWP (Universal Windows Platform) APIs
* Changed the inner working of render buffers and rendering methods<ref name="WinRenderer re-work"/>
* Changed to using unicode win32 api methods<ref>https://github.com/xbmc/xbmc/pull/11780</ref>
* Changed windowing systems for screen saver handling on Windows OS platforms
* Changed to make Kodi for Windows platform independent of posix/main.cpp<ref>https://github.com/xbmc/xbmc/pull/12215</ref>
* Removed support for Windows Vista as the operating-system is no longer supported by Microsoft<ref>https://github.com/xbmc/xbmc/pull/11953</ref>
* ?

== References ==
<references/>

== See also ==
* [[Leia API changes]]
{{Changelogs}}

[[Category:Manual]]
[[Category:Leia|*]]
[[Category:Changelogs|18]]