XBMC 12 Frodo - Release Candidate 2
We would quickly like to take this time to announce the second 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, including Airplay audio in XBMC for Windows to match the other platforms
- Improved controller support in Windows and Linux
- Advanced Filtering in the library
- Advanced UPnP sharing
- Translations now powered by Transifex
At 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.
Fixes between RC1 and RC2 include resolution of incorrectly disabling audio devices due to faulty detection, which should resolve all or most “audio suddenly stops altogether” complaints, along with numerous other stability enhancements and minor fixes. For the full list, visit our Github milestones for RC2. As always, please do not report bugs or other issues in Github. If you need to report a verified bug, feel free to use Trac.
To get this release candidate, please visit our download page.
Let us know what you think of this release candidate in the comments below, or, if you like, via the donation button at the top of the page.
If you have any problems read the Frodo FAQ and don’t hesitate to post about them in our forums and report verified bugs in Trac.
@ Dave,
I also get buffering over a wired network occasinally. Its not even limited to very high bitrate items, can be small MKVs such as TV episodes.
When playing a video, if you bring up the seekbar, you can see the buffering in the seekbar, its a ghosted fill level that seems to bounce around 95-100%, but I guess it gets tripped up now and again.
I’ve never seen this on Eden, only since Frodo Betas / RC.
i can confirm the problem with hd movies (h264 720p, dolby 5.1). i run xbmc on my laptop.
it used to work fine with eden and when updating to a frodo beta, i had to review my audio settings.
after reading some suggestions, i found my speaker configuration set to 2.1. after setting it to 2.0, things are working again.
Sorry, may I ask a quick question? I have read (Frodo FAQ 1.16), and searched the forums, but it is not clear…
If I am using Frodo RC2 on all my devices, and I “export video library” separate, and save my poster and fanart to my NAS (and that is now being saved as .jpg)…
Do I no longer have a need for the .tbn files that were exported to my NAS? Can I delete the .tbn files to save space?
@xbmclover
Changing the audio settings from Directsound to Wasapi fixed this issue for me at least so could be worth a try.
Hugely disapointed. Very slow navigating the menus, very slow opening files on any source, in-movie subtitle search doesn’t work, …
The AAC to AC3 encoding doesn’t seem to work in RC2. It was working fine in the beta version. I’ve tried flipping AAC Capable Receiver ON/Off but no luck. Otherwise the software is incredible.
@Depro
Using Android or Raspberry Pi, any chance?
What OS are you using?
I’m using for Windows and menu navigation is as quick as ever, opening a 10GB .mkv still in rars takes about 1-2 seconds and in-movie subtitle search works flawlessly.
Might just be that you need to make a fresh install and not upgrade your old one?
@nedscott
Thanks for the reply Ned, but I guess I’m missing something. If I go in to Files then the Video_TS folder I can see the VOB’s and select then play them individually. So how do I set XBMC to play them in sequence complete with normal menus, what am I doing wrong?
What I’m reffering to is that it would be nice to be able to add the folder to the library with just a thumbnail instead of requiring full meta to do that. Of course the Video_ts and Audio_TS are sub folders to the movie folder. This should be no different than just inserting the DVD in to my DVD drive except I’ve ripped them to my HD…..
Thanks for your help!
This version works fantastic for me. I skipped v11 because the interface always lagged when using HD3000. I installed this onto a USB like I had previously for v10 but for some reason none of my settings are saved across a restart. Is there something additional I have to do?
@Rexy
Use a play button instead of a select button. If you have a keyboard press “P” on the folder.
Im running beta 2 on Huawei G300 amazed how well it works, just wanted to say thanks for all your hard work on the android versions, cheers
@natethomas
Windows 7 X64, SPDIF Passthrough to receiver
When I install the XbmcUbuntu RC2 on my intel core 2 duo with ATI HDMI video card. It installs fine but upon first starting up, it just sits in a loop where it tries to load the main dashboard but fails and then tries to go back to the login screen, but also fails. Its just a loop of flashing screens.
I’m adding movie and tvshow directories. I see the data is being scraped but it is not being displayed when I click the directory under files or under library. I know I’m adding the data properly as I’ve done it a million times not to mention the same tv shows and movies were scraped properly in eden. And like I said, shouldn’t be a scraping problem as I can’t even see it under files.
Is there a newsletter registration to get to know about updates and releases?
Like, delivered email? No. But you could always subscribe to the RSS feed.
Hardware acceleration still not available on Android (Samsung Galaxy S III) and thus playback is choppy at best and heavily pixelated (artifacts). Video has no issue when using other third-party video players downloaded from Google Play.
Not interested in comments about hardware acceleration not supported due to number of devices out there. If third-party video players freely available from Google Play can support hardware acceleration, there is no reason XBMC can’t as well.
Either turn it on or remove the .APK from download – this is junk until hardware acceleration is supported. Do NOT submit this to Google Play without hardware acceleration enabled.
@nedscott
That works, thanks!
So just to triple check, no one else is getting compressed/blurry album artwork… I am alone on this one?
I understand Feature Requests are closed now.
But, I for One would appreciate greatly if you could find a way to discriminate between Subtitling between Live TV (i.e. PVR / DVR et.al), and those in TV Shows & Movies (Where most of that Stuff is Anime or Japanese Movies in Japanese of course).
Currently it’s kind of a PITA to have to jam though 11+ remote presses to just toggle this on or off is not cool.
@David Poole
Did anyone force you to download it? No you chose to, so maybe you should stop being so ungrateful. The devs give their time to give you a product. Also its clearly mentioned that the android version is experimental, maybe they should just shut down the project entirely because its not at 100% finished.
Maybe you should ask for your money back you idiot.
@David Poole
This is already answered in the Android FAQ, but the reason why other players can do it but we can’t is because those other players are either using closed source code or have signed NDAs to gain access to technical specs that we don’t have. Because XBMC is open source we cannot use those methods.
Hardware video decoding is already working on several AMLogic based Android devices, right now.
XBMC for Android’s main aim is to get on inexpensive set-top boxes, not your stupid phone. That will come as a side effect, but is not the main point. XBMC is all about the 10 foot interface, and most people don’t use their phones from 10 feet away.
Now, let me get this straight, you are demanding that we remove test-builds because it’s not complete? Do you understand the point of test-builds? Betas? Do you understand that XBMC is a project that lives off of community contributions? The entire point of telling people about these test-builds, Android or not, is to get help in developing XBMC.
I’m considering just deleting your comment, because assuming good faith, you can’t be this stupid. You must be drinking or be suffering from some kind of brain damage, and this really isn’t fair to you to keep your comments public.
@Ichijoe
Something to look at, indeed. However, you can toggle subtitles on/off by using a single keyboard/remote button press. See http://wiki.xbmc.org/index.php?title=Keyboard and http://wiki.xbmc.org/index.php?title=Keymap
nedscott, why even bother replying to such idiotic posts like that.
Plex is a better app for people who want things on their phones, or since phone storage is limited there’s no point having scraped info so just use a standard video player.
Looking forward to the day when I can purchase an android set top box that does frame rate sync and load XBMC on it.
RC3 was just released
Unless I’ve missing something in the Wiki, or misunderstood the pages I’ve found, it seems like there’s an issue with WTV or DVR-MS content in 1080p. The video playback is jerky (presumably frames getting dropped) and the audio is a hair out-of-sync. I think I’ve got everything configured correctly per the AudioEngine guidelines, but can’t seem to overcome this.
I’ve tried RC2 on two different Windows 7 x64 machines, one hooked-up to an AV Reciever via HDMI doing passthru to 5.1 surround; the other hooked-up to a USB-based Logitech sound-bar. Results on both machines for WTV/DVR-MS content recorded at 1080p is the same – jerky playback due, presumably, to missed frames. With or without hardware acceleration enabled, CPU utilization remains below 30%.
Any advice on what else to try, or where to look?
hi,i have a problem using both versions(11 and 12). both of them doesn’t connects to internet on my laptop. i use wifi at home.i tried making changes but none of them worked for me.is there any setting to be done in laptop?
pls help.
@natethomas
Switching to WASPAI from Direct Sound seemed to fix the ACC encoding issue in RC3.