Different results in decodeAudioData?

I'm creating a little music-engine where a collection of mp3's can be
grouped and seamlessly looped. Due to the nature of mp3s, this requires to
set the actual looping points of all mp3 in the decoded data beforehand, so
we know exactly which bytes to play.

I set the looppoints for some testfiles at home, but when i checked the
project at work, i noticed that they were all placed incorrectly, so it
seems that different browsers can decode mp3files differently (this was all
in chrome btw). Is this just how it is, and will my method therefor not
work crossbrowser (without me having to set those looppoints for each
brower+version)?


Peter

Received on Tuesday, 12 February 2013 14:41:20 UTC