| General topics
|Want to discuss or ask about what hardware is good for XBMC? Check out the Hardware for XBMC subforum|
XBMC needs a 3D capable GPU graphics hardware controller for all rendering. The required 3D GPU chips are common today in most modern computers, and even some set-top boxes. XBMC runs well on what (by Intel ATOM standards) are relatively underpowered OpenGL 1.3 (with GLSL support), OpenGL ES 2.0 or Direct3D (DirectX) 9.0 capable systems that are IA-32/x86, x86-64, or ARM CPU based.
When software decoding of a Full HD 1080p high-definition video is performed by the system CPU, a dual-core 2 GHz or better CPU is required in order to allow for perfectly smooth playback without dropping frames or giving playback a jerky appearance. XBMC can however offload most of the video decoding process onto GPU graphics hardware controller that supports one of the following types of hardware-accelerated video decoding: Intel's VAAPI, Nvidia's VDPAU, AMD's XvBA, Microsoft's DXVA, Apple's VDADecoder/VideoToolBox, OpenMAX, and Broadcom Crystal HD Enhanced Media Accelerator. By taking advantage of such hardware-accelerated video decoding, XBMC can run well on most inexpensive, low-power systems which contain a modern GPU.
1 Supported hardware by OS
It is highly recommended for users to not make any purchases in anticipation of running XBMC on Android without researching the device you want to buy. If you do buy, make sure multiple people can verify that it works! If in doubt, do not buy that hardware!
- Due to the nature of Android hardware it is hard to give exact minimum requirements, so instead the basic set of requirements includes at least:
- NEON compatible ARM processor, (for example: Nvidia Tegra 3 and later are fully supported by XBMC, while Tegra 2 and older Tegra probably will never be supported).
- Android 4.0 or later is supported, but Android 4.4 and later is recommended.
- Hardware decoding support in XBMC is likely a must for high definition video playback (720p or higher resolution). Do not expect this to work on any device until someone knowledgeable have specifically already tested it and can confirm hardware decoding support for that device. For more details on hardware video decoding support, see Android hardware.
- The main aim for the Android port is to initially target media-players/set-top-boxes/sticks that connect to a large screen television and uses a standard remote control as interface device, (that is the same market as for HTPC). However expect tablet/phone/touch/mobile/etc support to eventually improve with time.
- To Install XBMC on ATV2 you must have a jailbroken Apple TV 2 running versions 4.1 to 5.3
- XBMC only works on the second generation Apple TV (ATV2), which is the black version that outputs 720p. XBMC does not work on the newer third generation Apple TV (ATV3) that outputs 1080p (Full HD), because there is no jailbreak for the ATV3.
- To install XBMC for iOS you must have a jailbroken iDevice running iOS 4.0 through 7.1.2. (4.3 or higher recommended)
- For hardware: iPad (1,2,3,4), iPad Air, iPad Mini (1,2), iPhone (4, 4S, 5, 5c, 5S), iPod touch (4, 5).
|CPU|| x86 processor such as: Intel Pentium 4, Intel Pentium M, AMD Athlon XP/64, AMD Opteron, or newer CPU (that support SSE. Anything made in the last few years does.).
XBMC will run on most graphics cards made in the last few years, including hardware video decoding support. This includes most cards from ATI/AMD, Intel, or NVIDIA which support OpenGL 2.0 or later.
|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, VDPAU, OpenMAX, or CrystalHD.|
|Drive space|| The XBMC binary generally takes up between 100 to 200 MB of space, depending on how it's compiled. Technically speaking, if your hardware supports netbooting, you don't even require a hard drive for either the OS or XBMC.
It is very hard to generalize XBMC hardware requirements for Linux-based OSes on ARM hardware due to most of the work in this area still being early/on-going in development. OpenGL ES 2.0 is a must. For most ARM devices, hardware video decoding support will be needed for most HD videos (and possibly some SD videos). Some newer/faster ARM chips can decode some HD video using software video decoding.
Here are a few known Linux/ARM hardware devices that are known to work:
- Cubox-i - Official supported by OpenElec, GeeXboX, Xbian
- Raspberry Pi - Hardware video decoding for h.264, mpeg2, and VC-1. GUI is responsive on most light skins.
- Various "Android" boxes - can run Linux and boot directly into XBMC. Hardware video decoding for most video codecs, GUI is very responsive on most skins. Running Linux/XBMC on these "Android boxes" will likely result in better performance than running Android/XBMC.
- Pandaboard - GeeXboX is a good OS/XBMC distro for this platform. Limited support, as it is generally not a development target by Team XBMC.
1.4 Mac OS X
- XBMC v12 Frodo and later requires Mac OS X 10.6 and only runs on Intel Macs.
- OS minimum to run XBMC: Windows Vista.
- OS recommended: Windows 7, which is required for hardware video decoding.
- Windows Home Server and Windows Server are not supported but have been reported to work with some tweaks.
- For end-users the recommended minimum requirement is a x86-based computer, with a graphic adapter that supports DirectX version 9.0c.
- x86 (Intel/AMD-based) processor: with .
- SSE2 support
- Fast modern (last few years) dual-core processor is required to decode H.264 videos in FullHD (1080p) without the assistance of a hardware video decoder.
- ATI/AMD, Intel, or NVIDIA graphic controller.
- ATI Radeon R420 (X800) or newer supported, ATI Radeon R700 (HD 4000) or newer recommended.
- Intel GMA 950 (945G) or newer supported, Intel GMA X4500HD (G45) or newer recommended.
- NVIDIA GeForce 6-Series and newer supported, GeForce 8-Series and newer recommended.