It's a wierd bug in the initial audio loading. I have yet to reproduce it in any browser so I'm unsure how to solve it.
