Why the move to HTML5 audio #2762
Replies: 1 comment 3 replies
-
Good question! Web AudioWeb Audio (specifically a BufferSourceNode) as the default playback mechanism was originally picked because we already used Web Audio to decode the audio. The decoded buffer was just passed to a BufferSourceNode directly, and played. Web Audio prosThe pros of this approach were:
Web Audio cons
HTML5 AudioNow, HTML5 audio also has downsides, but a lot of benefits too. HTML5 Audio pros
HTML5 Audio consThe downsides are:
ConclusionTo conclude, we were getting quite a few complaints about the Web Audio performance/memory issues, and the answer was always "Use |
Beta Was this translation helpful? Give feedback.
-
Hello, I would like to ask why you decided to fully move to HTML5 Audio in version 7. Isn't the web audio API way more powerful? I mean I have seen that there is a way to use the web audio API nevertheless but still.. I'm pretty new in the field and maybe there is something I don't understand so I would appreciate if you could elaborate. Thanks and regards.
Beta Was this translation helpful? Give feedback.
All reactions