61–70 of 75 posts
Earlier quoted context omitted.
Same for my Firefox Aurora, even though I think it supports the Web Audio API (not sure, though if it's really up to date).
I run the Firefox Nightly and it doesn't support Web Audio either. Shouldn't that be happening soon?
I enjoyed creating a song with it (lyrics/melody), but I didnt understand the gaming mechanics.
Earlier quoted context omitted.
I run the Firefox Nightly and it doesn't support Web Audio either. Shouldn't that be happening soon?
Firefox was the first with a Web Audio API. Google has an alternate API. Neither one is a standard. Both are great ground for experimentation though.
Mozilla's Audio Data API is available since FF4.
Web Audio API has been enabled in Chrome 13 or 14, before it was off by default. Probably appeared shortly after FF4 (?)
Such non-standardization sucks balls if you ask me.
These guys should make HTML5 standards and stick to it. Not make the standard evolve every NEXT day saying "oh look its what HTML5 is now!"
That's absolutely non-standard and annoying as hell.
"Oops! Your browser doesn't support Web Audio." Meanwhile, Adobe just announced that the Unreal Engine runs in Flash Player 11. That's AAA quality 3d gaming in the browser (and not just Chrome). I am so bored with "HTML 5" game (that aren't even HTML 5 official spec) announcements getting such a ridiculous amount of play. Imagine if someone went out to E3 in 2011 and announced that they just came up with this crazy T…
The Quake Engine has been running inside browsers for ages. Also if you speak about portability. Flash really isn't very portable when you compare it with the platforms supported by Webkit. Flash has always been a huge mess when it comes to this. Webkit and Gecko are pretty much up to date, but many people hardcode browser checks instead of just asking whether the browser supports certain stuff. I think that's the bi…
And why should Gecko support Web Audio API? You see, they got Web Audio Data instead. Not compatible of course. None are standard.
So flash does beat them and HTML5 on that very topic.
Earlier quoted context omitted.
The Quake Engine has been running inside browsers for ages. Also if you speak about portability. Flash really isn't very portable when you compare it with the platforms supported by Webkit. Flash has always been a huge mess when it comes to this. Webkit and Gecko are pretty much up to date, but many people hardcode browser checks instead of just asking whether the browser supports certain stuff. I think that's the bi…
What portability. I mean, Web Audio API is supported by only Chrome and Safari (so that's not "webkit". Sure Flash ain't better. But hey! None of this is standardized. And why should Gecko support Web Audio API? You see, they got Web Audio Data instead. Not compatible of course. None are standard. So flash does beat them and HTML5 on that very topic.
The Web Audio API is a much more fleshed out API, built on the higher level audio APIs used in professional sound apps. You can use it to process raw buffers, but you can also use it sequence and compose many effects on audio buffers with very low latency timing requirements without having to write time critical javascript DSP code and hope for the best that no delays or scheduling skew creep in.