The next version of XBMC (Dharma) is now available

XBMC

Almost missed this one.

Unfortunately I’ve not had a chance to play with it on my home cinema setup because I switched off the machine just before I went away for the holiday season. But reading through the list of changes and finally having a little dabble on my laptop confirms this will be the first thing I’ll do when I get home.

XBMC 10.0 “Dharma” is ready for consumption. Those who have been following development know that add-ons are the main focus of this release. In the past, in order to find a new skin, you would have to dig through the forums, find a link, and hope it worked. Ditto for plugins, scrapers, etc.

Those days are over. All of these things are now available within XBMC, no need to put down the remote to find new content or change the look of your HTPC. Just head to the “add-ons” section in the system menu. At the time of this writing, there are 11 different skins available, all with distinct looks and personalities. But we didn’t stop there. Want to watch your favourite youtube videos? Listen to some web radio or podcasts? Install a web interface to control your living-room experience, or even one to manage your media? It’s all available in the new add-ons system. Even before the final release, we have seen an average of 50,000 add-on downloads per day. It’s time for you to see what many others have discovered! And remember, the best part is that the add-ons are very much alive. New ones are being added every day, and current ones are continuously updated.

So finally XBMC has caught up with Plex in regards to plugins and scrapers. The full change log is here.

Hacking the Pacemaker (progress)

Pacemaker Manager

At last a break through, someone (musicinstinct2) has cracked the way the pacemaker adds and removes music to the SQLlite database.

My initial experiments involved using the sqlite database browser to open up music.db and enter track information. Then manually copy the tracks over to the device, making up random hash values (as I couldn’t work out how Tonium were creating these hashes). It works! The device doesn’t rely on any particular naming convention, whatever is in the filename field in the database (music.db) is used by the device to load the track.

Fantastic…! Now this is cracked and Musicinstinct2 is working on a open source client to manage tracks. The next stage is to crack and understand the XML file which is attached to every single track uploaded on the device. The bulk of the data in stuck in a XML element called realBeatLocations.

I expect it won’t take long before we have the whole thing pretty much cracked. What would make things move along quicker is if Tonium would publish the source as it was created under the GPL.