Same behavior as the bug reported below, except that I'm seeing it in Google Chrome, when HTML5 is used as the audio:
For now, the workaround we're using is to set soundManager.preferFlash=true so that we use Flash by default instead of HTML5.
All in all, SM2 is a great widget. Keep up the good work.
EMPLOYEE0Firstly, thanks - for feedback and bug reports, and ideally if SM2 is useful also, that's good. :)
Chrome has had some pretty nasty HTML5 audio playback issues as of version 16 and newer, from what I've been hearing, and this is part of the reason why SM2 defaults to preferring Flash for the time being - as playback via Flash is very stable.
It'd be interesting to hear if you can reliably reproduce this issue on the SM2 homepage with preferFlash=false, in a Webkit browser.
If you have more details on the version of Chrome and OS, bonus!
I have been using SM2 for more than a year and can confirm this. I have two sets of audios: mp3 + ogg and I have written a set of rules for browsers. IE9 seems to be the least problematic: HTML5+mp3 without ANY problems.
Firefox, Opera and Chrome seem to work well with HTML5+ogg.
Chrome & Safari have problems with HTML5+mp3 and Safari (plus IE9) will not play ogg using HTML5, of course.
IE8/IE7 will, of course always need Flash and the same applies to less known browsers.
Chrome really seems to behave differently from one version to another which is quite a nuisance. Anyhow, the quality of HTML5 .ogg support in so many browsers is quite a nice surprise.