Re: Different results in decodeAudioData?

By setting looppoints, i mean what you propose: manually add metadata for a
soundfile, defining the start and end sample-index on the decoded audio
(the resulting Float32Arrays).

if you go here: http://petervandernoord.nl/jslooper/default.htm
and...
- click 'from json'
- click the sound that appears in the left field (will load in the display)
- navigate to the place where the sound 'starts' (there's a lot of silence
at the beginning), which takes 4 clicks on the >> button (and then a few
back with the < button.

... then here at my homecomputer the looppoints (blue colored pixels are
outside of the looprange) are not set correctly, while they are at my work.
since those points havent changed (they're in the json), the only
conclusion is that the resulting arrays are different on these two machines.

btw, clicking in the wavewindow itself will set the starting looppoint
(shiftclick sets the end), so don't do that if you want to check those
points.





2013/2/12 Joseph Berkovitz <joe@noteflight.com>

> HI Peter,
>
> I'm not sure what you mean by "set the loop points" since MP3 loop points
> aren't decoded into an AudioBuffer by Web Audio as far as I'm aware.
>
> In looping externally loaded samples I've found it best to encode loop
> points in a separate file of metadata that is read in its own XHR, rather
> than attempting to load loop points into the browser as part of the MP3
> file (which I've never tried to make work).
>
> On Feb 12, 2013, at 9:40 AM, Peter van der Noord <peterdunord@gmail.com>
> wrote:
>
> 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
>
>
> ... .  .    .       Joe
>
> *Joe Berkovitz*
> President
>
> *Noteflight LLC*
> Boston, Mass.
> phone: +1 978 314 6271
> www.noteflight.com
> "Your music, everywhere"
>
>