Anzeigen der neuesten Beiträge
0 Mitglieder und 2 Gäste betrachten dieses Thema.
Update 2: Users should be aware that an update to Android 4.2 appears to have temporarily broken XBMC support for all you Nexus and Cyanogenmod users (and anyone else running 4.2). Beta3 should be right around the corner, and we hope to have a fix in place by the time that rolls out.Controller SupportWithout a doubt, one of the most popular controllers for PC at present is the Xbox 360 Controller. It is invariably the most supported controller for all AAA title Windows games (along with numerous games being ported for Steam for Linux), so it was undoubtedly time for the controller to become fully plug and play compatible with XBMC. Thanks to the work of Shiretoko212, rowan.border, and all those who contributed in this thread, the previously outdated 360 keymap has been updated and dramatically improved so that now almost any 360 controller, regardless of version, should be immediately recognized by XBMC assuming a driver is in place. For those interested in using their 360 controller to control XBMC, check out this 360 button map to show what all the buttons do in XBMC.Audio FixesEasily the number one reported issue with Beta1 was a lack of sound in Windows. This issue was relatively simply resolved by switching from WASAPI to DirectSound as the default output. Users who prefer WASAPI can still easily switch back in System->Audio Output.Other FixesNeedless to say, there were numerous other fixes, including fixes to nodes and smartplaylists, the volume range of Airtunes in Windows, a speedup of EPG data importing, solving a minor files issue, and others. To see all the changes, feel free to refer to the Beta2 Git Changelog. Additionally, there are several other issues still being worked on, and more will likely crop up during Beta testing. If you would like to report an issue, please search for the issue in our forums first and report any verified bugs in Trac.
Hot on the heels of Beta 2, we are excited to release Beta 3. This release includes a number of fixes as we work to resolve issues that have cropped up since Beta 2 and also attempt to isolate some issues that still exist. For a quick run down of some of the big ones: - Users of Android 4.2 should now be able to install and run XBMC for Android. - The upgrade path of Windows users has been a little tricky. Users may upgrade to beta and discover the audio no longer works. This is due to a bit of trickiness with the AudioEngine upgrade. For Audiophiles to get the most out of AE, we recommend that you check out the AE Wiki entry. - For those Windows users who find themselves without sound, the simple fix is to go to System->system->Audio Output and switch WASAPI to DirectSound. Users doing a clean install of XBMC for Windows Beta 3 should have no problem. - PVR Addons have been included with XBMC for Windows, matching up with most other ports. - We are still only partially complete on translations for numerous languages, including Romanian, Japanese, Estonian, Bosnian, Serbian, Hindi, and more.
We would quickly like to take this time to announce the first release candidate for XBMC 12. Features for XBMC 12 include: HD audio support, including DTS-MA and Dolby True-HD, via the new XBMC AudioEngine Live TV and PVR support h.264 10bit (aka Hi10P) video software decoding for anime 64bit support in OSX to match the 64bit support in Linux Improved image support, allowing the database to accomodate numerous additional image types Support for the Raspberry PI Initial support for the Android platform Improved Airplay support across all platforms Improved controller support in Windows and Linux Advanced Filtering in the library Advanced UPnP sharing Translations now powered by TransifexAt this point, XBMC 12 is entirely feature complete. All changes from this point forward will exclusively include fixes for replicable bugs necessary to reach final release.To get this release candidate, please visit our download page.