@ddas - The particular js that is used in this theme (http://kolber.github.com/audiojs/) was developed to be very light and so the developers decided to not build in support for ogg... personally a fatal mistake IMHO. There is a fork on the github for it that adds support, but it also changes a lot of other stuff and I actually haven't been able to get it to successfully work in my tests, and the forking developer has not responded to me.

@Molitor - Im aware of the limitations of Firefox, but it's more in there format support. I've seen js implementations that appear to work better then the current one used. I am looking at modifying the theme to use something different as soon as I find the time, but any assistance or suggestions would be awesome.. Im not afraid to tack on a little more $$... :D That banner at the bottom is calling you.. :P

No, you can use MP3 for all modern browsers with this theme.

This brings up a really important point. Concerning audio formats, unfortunately, there is no one audio format that works in ALL browsers in HTML5 (see http://html5doctor.com/native-audio-in-the-browser/). So we are forced to create (at least) two formats for every song we need to upload so that the browser can have fallbacks.

How do we do this inside Nocturnal, which appears to already have a great in-built system for handling audio files? How do we tell it that it should use song1.mp3 but fall back to song1.ogg if the browser doesn't like the mp3?

Unfortunately this is a FireFox-related limitation in how it handles the audio HTML 5 tag. The good news is that FireFox is pretty good about releasing updates lately (they went from 4.0 to 7.0 in about a month!), and I know they're working on improving HTML5 support.

While in development I have noticed that the performance of the audio player is very unreliable, even on your demo site. Clicking on the first audio and then skipping the next one and clicking before the first one starts to play causes a huge lag and inconsistency in the loading bar animation on the Left Column. Also when clicking through quickly, sorta "channel surfing" if you will causes these same issues, and also inconsistency in the for the played/length numbers. I know that firefox only really does well with ogg, so I was wondering the best route to do this side by side with mp3. Or if it is possible to sub out the js for something a little more robust?