HTML5 audio sprites -- Holy Grail or Programmers Hell
summary
Grepolis merges 150+ short effects into one audio sprite and plays fragments by setting currentTime and watching the timeupdate event; OGG files compress ~8% smaller than MP3. Tests show sequential playback cuts memory roughly to half the memory used by separate audio elements and eliminates many network requests, but creating multiple elements for simultaneous clips drives CPU and RAM up — 10 sounds at once spikes CPU as browsers rebase currentTime and fire unreliable timeupdate callbacks.
AI-written summary · about
chapters (8)
- 0:00Start
- 8:18Audio sprites - idea of implementation
- 8:45Audio sprites - Hints about files preparation
- 10:02Size of files - comparison
- 10:51Measurements - sprites
- 11:13Measurements - datasets
- 14:18Size of files - datasets
- 14:41Loading speed factors
related talks
48mMaking Realtime Audio-Visuals
05mSync HTML5 audio with CSS3 animation
25mMonster Audio-Visual demos in a TCP packet
22mWhat Happens When the Music Starts? The Architecture of Browser Audio
37mThe Web Audio Explanation I Wish I Had
38mReal time front-end alchemy
33mogv.js: Rebuilding the Web Video Stack From Scratch in JS
29mA GIF Odyssey