Why you keep getting a computeSpectrum Security Error
Probably one of the worst and most frustrating bugs.
Turns out computeSpectrum will NOT work if ANOTHER Flash is using audio. Meaning if you have a Flash that using SoundMixer.computeSpectrum one of those super annoying security sandbox runtime errors will pop up on the browser if YouTube, GMail, or any other Flash using audio is opened.
The fix? There is no fix. No, security.allowDomain won’t work. No, placing crossdomain.xml all over your server won’t work either. The only thing one can do is catch the error (or use areSoundsInaccessible()) and have something else happen in between. This bug is especially annoying for game developers like me who are working on a game that uses the computeSpectrum to generate content…
Grrr… So annoying.
Encourage Adobe to fix this by voting for it.
3 comments to “Why you keep getting a computeSpectrum Security Error”
May 2nd, 2010 at 9:46 pm
[...] Unfortunately, the reason for the error and the options available were not very pleasing. I found this blog post that seems to explain it correctly. Apparently, if flash is running more than one swf using audio, [...]
July 9th, 2010 at 6:35 am
than how the hell do other popular sites cope with this?? e.g. myspace’s player?
December 21st, 2010 at 10:17 am
About MySpace, that’s probably because its player does not respond to sound : if you listen to a song with silence in it (or if you turn volume to 0), you can see it keeps on moving the exact same way.