71–80 of 99 posts
If imitation is the sincerest form of flattery, feature requests must be the next-sincerest. With that out of the way, I'd love to see: * Standard playback widgets: volume, position slider, etc. * A way to link songs, e.g. http://jsmad.org/play/114578 Fantastic work!
(edit: typo)
Earlier quoted context omitted.
From what I hear,the HTML5 tag implementation quality varies wildly. It hasn't been used much in production for desktop-targeted web apps. It is, however, quite popular on the iPlatforms, because you have no Flash there! As far as I can tell, jsmad is not going to replace the HTML5 audio tag on mobile devices. However, it does constitute a nice legal workaround for MP3 in desktop browsers such as Firefox. It gives ac…
At 50% cpu utilization this is very impractical outside tech demos.
Earlier quoted context omitted.
From what I hear,the HTML5 tag implementation quality varies wildly. It hasn't been used much in production for desktop-targeted web apps. It is, however, quite popular on the iPlatforms, because you have no Flash there! As far as I can tell, jsmad is not going to replace the HTML5 audio tag on mobile devices. However, it does constitute a nice legal workaround for MP3 in desktop browsers such as Firefox. It gives ac…
At 50% cpu utilization this is very impractical outside tech demos.
Firefox 4.0+ AND Chrome 13.0+ are supported. However, Web Audio API doesn't seem enabled in Chrome 13 by default, just go to 'audio:flags', check "Web Audio", then click the "restart browser" button and it should work.
If the site isn't loading for you (I was getting nginx errors for a bit before it finally loaded for me), here's the github repo: https://github.com/nddrylliog/jsmad
Earlier quoted context omitted.
Yes, as said in the README, the audio output doesn't work on Chrome. I have no idea why - audiolib.js should support it. Maybe we're just using it wrong? If the audiolib.js dev is here or anyone else has a clue, it'd be very welcome.
Really? It's working on Chrome 13 for me, though because of how Chrome slows down JS execution when you switch to another tab, things can get... funky.
Firefox 4.0+ AND Chrome 13.0+ are supported. However, Web Audio API doesn't seem enabled in Chrome 13 by default, just go to 'audio:flags', check "Web Audio", then click the "restart browser" button and it should work.
How did you find working with Firefox's AudioAPI and Chrome's Web Audio API, how do they compare? What drawbacks and advantages did you find working with each of them?
Earlier quoted context omitted.
At 50% cpu utilization this is very impractical outside tech demos.
Yes, please help optimize it.
As a wise Keanu Reeves once said, "Woah." Is there any upper limit you've found with bitrates, etc.? Also, what was the most difficult part in building this?
Been playing 320kbps Stereo flawlessly afaik. The bitrate is really not much of an issue. Browsers have a much harder time dealing with binary XHRs, huge typed arrays, huge strings, and a real fucking lot of arithmetic operations. I think the most difficult part was the debugging. Jens Nockert, Matthias Georgi & I finally used node.js and carefully diff'd the output from minimad.c (the canonical libmad example) and j…