I just came from a project that required heavy use of HTML5 audio, and let me tell you that the 15+ ffmpeg calls during the audio build step were the least painful part of the process.
HTML5 audio in iOS is a bit of a black box, with variable, unpredictable and undocumented behaviors between iOS5 through 7. These guards are intended to shield users from obnoxious behavior, but in the process, make the feature useless for everyone else.
You get one HTML audio element whitelisted in response to a user-initiated event, so you need a "click anywhere to do something useful!" screen. Also, you've got that one element to work with, so something like sound effects with a background track is out of the question.
Once you've got a whitelisted element, you can then re-use that element to play individual sounds by swapping out the src attribute of that single whitelisted audio tag, which queues a new web request and plays back the sound whenever the web request finishes... which is usually several seconds after you wanted it to play.
This happens regardless of whether or not the sound has been played before; the result isn't cached locally.
So, if you want to produce something remotely workable, you do audio spriting and never switch out to a different audio file. You create a build step that pulls in all of your audio, all of your sound files, puts them together into a single wave file, generates an audio atlas, and re-encodes audio to mp3, wav and ogg to hit all the major players (rinse and repeat for other channels of audio). Which works on most devices, but iPads decide to ignore currentTime assignments on that audio track, so the whole thing is kind of botched.
That's before we try to get stuff predictably working in IE, which can go anywhere from screwing the whole thing up to unpredictably mutating volume levels. That's before we support Firefox, which doesn't loop audio like everything else does and randomly stops playing audio. That's before we support Android, which exhibits different behaviors across the stock browser and Chrome, and so on, and so on.
If you want to play a single audio track in one or two desktop browsers, then sure, the technology is somewhat ready for you. Codecs are the least painful part of the problem. Anything beyond that is a travesty.
So true. We're trying to build a web-based online anatomy trainer, which plays success/failure sounds when you click right/wrong, but also add a voiceover with the anatomy term being spoken out.
We experience very sketchy behaviour across platforms and browsers (especially mobile). We're relying on SoundManager which seems solid, but doesn't solve all problems. I wonder if anybody else has any suggestions / experience to make things easier somehow?
Did IT in an medical library in a university. The douchey doctors/professors spent a lot of money on a homegrown AV system connected to computers to accomplish part of that task, so I hope you can turn a buck off that. Seems cool.
I agree in theory, but I think that breaking the mold slightly will help it grow past a cool tech demo.
I'm mainly comparing this against using SoundCloud directly, or something like turntable.fm. A big feature I like is being able to +favorite a song that I like, or buy the album, so anything that causes me to lose context greatly devalues the app.
And for the cookies, it's really just the background and comment preferences. Maybe the cookie could be named .cmdfmrc or something?
Oddly, I can play most stuff, but not drum & Bass. It just says
Found! Playing 'Drum & Bass' genre, yay!
The song is ended (but the melody lingers on)
Welcome to cmd.fm!
Use 'help' command to see available commands
I also prefer TUI over Ajax GUI but here I think we don't have the tools and environment that define a real TUI. For example, can I pipe the genre list to grep or sort or awk? Can I script a player in a cronjob? I doubt it (cannot check because on a phone)
Sure it does. Just press i to enter insert mode. You have to do this for a couple of things to work (ie direct links to .swfs). It sucks to do, but I'm not going to give up Vimium to avoid having to enter insert mode every now and then.
Long ago, there was music, call it pop. Much time passes and the same music is still played, but it has been renamed folk. Edison, got involved and the guy on the Martin discovered Fender so now they call it folk rock. Just to be clear, folk didn't go away, it is still around and thriving---fix your genres please :)
If not already, you should use Sound Manager 2 http://www.schillmania.com/projects/soundmanager2/ and its api. It's amazing. It auto selects HTML5 or Flash on both pc and smartphones. It even checks if people have flashblock enabled and tells them to "click here to enable flash".
I've used it on 2 projects before http://timeforzen.com and http://residentevilradio.com (it can also stream from shoutcast servers.) I've got HTML5 disabled on those 2 projects because it was still beta and glitchy at the time the feature was introduced.
Also, usually the exact moment when I want to look up the name of a track that I like is when it just finishes playing. This is also the exact time when this interface removes the name of the track and replaces it with the new 'now playing' song. Please keep a record of all songs played in the scrollback!
if you had telnet/rest or any other standardly documented access point, I could schedule stations with a cron script. Have a hardware button with an arduino. The sky is the limit.
The way it is now, it's just a toy. nothing other than a slightly more inconvenience to use than pandora. it doesn't really add anything different. Well i could emulate keystrokes and expose an API myself, but then i could already do that emulating mouseclicks in pandora anyway.
This is absolutely fantastic! I'd love a native Alfred style Option + Space interface so I could quickly chop and change between the music because having to switch to Chrome then the right tab is cumbersome. This is really great however, excellent job.
This is certainly an interesting idea, definitely appeals to the programmer/hacker type. Its not a service for everyone since it looks complicated and scary to someone who has never opened a terminal before. I think this is fun though and you did a good job!