|
|
| (23 intermediate revisions by 5 users not shown) |
| Line 1: |
Line 1: |
| The current stable release of XBMC (v11 "Eden") does not support the [[wikipedia:h.264|h.264]] Hi10P profile, but [http://mirrors.xbmc.org/nightlies/ current nightly builds] and [http://mirrors.xbmc.org/snapshots/ monthly builds] do (Pre-v12 "Frodo"). ''(monthlies are considered more stable than nightlies, but are still pre-release and may contain bugs.)''
| | {{mininav| [[Video library]] }} |
| | Hi10P (also called "10-bit") is a profile of the [[wikipedia:h.264|h.264]] video codec. It has recently become popular in the anime scene for video encodes. The first stable version with Hi10P support is v12 (Frodo). As of v13 (Gotham), Kodi will automatically use multi-thread (multi-core) software video decoding for Hi10P videos, allowing for better performance on low-end processors. |
|
| |
|
| The first stable version with Hi10P support is planned to be XBMC v12 (Frodo).
| | == Hardware requirements == |
| | Hi10P won't work on most ARM or even some Intel ATOM processors. Hi10P can't be hardware decoded (which is to say, no one currently makes hardware decoders for them and no company plans to add Hi10P hardware decoding in the foreseeable future), which is what a lot of low-power devices require for smooth video playback (such as the Raspberry-Pi, Android, ATOM processors, and some AMD APU systems). Thus, Hi10P requires CPU/software decoding. |
|
| |
|
| ==Hardware requirements==
| |
| Hi10P won't work on ARM or even Intel ATOM processors (maybe one day, but none of the current ones in 2012 would do it). Hi10P can't be hardware decoded (which is to say, no one makes hardware decoders for them and no company plans to add Hi10P hardware decoding in the foreseeable future), which is what Raspberry-Pi, Android, ATOM processors, and some AMD APU systems require for playback smooth demanding video (Hi10P is very demanding). Thus, Hi10P requires CPU/software decoding.
| |
|
| |
|
| A safe bet would be at least a core2duo processor (or equivalent AMD) or higher. | | A safe bet would be at least a Core 2 Duo/Celeron G530 processor (or equivalent AMD) or higher. |
|
| |
|
| ----
| |
| {{hidden|1=Older unofficial build information
| |
| |2=
| |
| ==Unofficial builds==
| |
| ===Windows===
| |
| *XBMC with replacement DSPlayer has been updated for XBMC v11 (Windows only). See '''[[DSPlayer]]''' and http://dsplayer.passion-xbmc.org
| |
| *2012-04-05 XBMC Windows build by forum user Maruchan: https://hotfile.com/dl/152001382/69c900c/XBMCSetup-20120405-fc6564d-dx.zip.html
| |
| *2012-04-02 XBMC Windows build by forum user Shine: http://www.mediafire.com/?p08gpzy8p8ipxvz
| |
| *2011-12-09 XBMC Windows build by forum user bambi73: http://www.mediafire.com/?e9h77fr86d04zef
| |
|
| |
|
| ===Linux===
| | Some (most?) ARM processors are not powerful enough to software decode it, and no hardware decoders exist for it. As faster ARM CPUs come out this will get better, but don't expect miracles from the average Android box. |
| *[[OpenELEC]] 2.0 beta 4 has gained 10-bit support (due to pulling in the updated ffmpeg version from Frodo to fix another problem).
| |
| **OpenELEC 2.0b4 release announcement: http://openelec.tv/component/k2/item/244-openelec-20-beta-4-released
| |
| *[[OpenELEC]] can now be compiled against the current XBMC source (no PVR). Do not ask for support for OpenELEC Frodo builds except in the discussion thread below.
| |
| **Instructions: http://openelec.tv/forum/68-audio/30233-hd-audio-passthrough-is-it-possible-to-bitstream-dtshd-and-dolby-truehd-over-hdmi?limit=20&start=100#33708
| |
| **Discussion thread: http://openelec.tv/forum/20-development-discussion/33540-building-against-xbmc-master-branch
| |
| **Pre-compiled builds (Generic-only): https://www.dropbox.com/sh/ezz725y7xtm9rba/uUnw2UkMhh
| |
| *[[XBMC for Linux]] can be compiled to use an external install of ffmpeg (which would support Hi10P).
| |
| *Build/install script from forum user zyro: https://github.com/zyro/ffmpeg_xbmc
| |
| | |
| ===Mac OS X===
| |
| *None known at this time.
| |
| | |
| ==External players==
| |
| XBMC can be set up to use an '''[[external players|external player]]''' for video playback, while still using XBMC for the interface.
| |
| ===Windows===
| |
| *[[forum:43511|Forums:External Player Support Thread on the XBMC forums]]
| |
| *[[forum:116724|Forums:Working External Player Solution]]
| |
| ===Linux===
| |
| *?
| |
| ===Mac OS X===
| |
| *XBMC set up to use VLC or MPlayerX will work.
| |
| }}
| |
| ----
| |
| | |
| ==See also==
| |
| *[[forum:106051|XBMC forum thread about Hi10P support]]
| |
| | |
| [[Category:How-to]]
| |
Hi10P (also called "10-bit") is a profile of the h.264 video codec. It has recently become popular in the anime scene for video encodes. The first stable version with Hi10P support is v12 (Frodo). As of v13 (Gotham), Kodi will automatically use multi-thread (multi-core) software video decoding for Hi10P videos, allowing for better performance on low-end processors.
Hardware requirements
Hi10P won't work on most ARM or even some Intel ATOM processors. Hi10P can't be hardware decoded (which is to say, no one currently makes hardware decoders for them and no company plans to add Hi10P hardware decoding in the foreseeable future), which is what a lot of low-power devices require for smooth video playback (such as the Raspberry-Pi, Android, ATOM processors, and some AMD APU systems). Thus, Hi10P requires CPU/software decoding.
A safe bet would be at least a Core 2 Duo/Celeron G530 processor (or equivalent AMD) or higher.
Some (most?) ARM processors are not powerful enough to software decode it, and no hardware decoders exist for it. As faster ARM CPUs come out this will get better, but don't expect miracles from the average Android box.
Video library