After adding peaks to the load parameters, events stop firing

If I just use the wavesurfer.load(url) method, the file is loaded and the events fire without any problems, for example “ready”:

wavessurfer.on('ready', function() {
	wavessurfer.play();
});

If I add peeks as parameters, an image of loaded peeks appears, but not one event is fired anymore:

var peeks = [0.0022365502,0.27022097,0.018188005,-0.289925, ...more values... 0.16755348];
wavesurfer.load(url, peeks);

I am using the latest version of wavessurfer.js: unpkg.com/wavesurfer.js@6.3.0/dist/wavesurfer.js

[alexey-v-paramonov]

Same problem here. If there is a file URL and peaks data - “ready” event is not fired with “WebAudio” backend (“waveform-ready” if not fired as well). Version 6.3.0. As a temporary workaround I am calling .play() right after the .load() call, catch “ready” event (that is getting fired then) and immediately call .pause() inside my “ready” hook. Then “ready” event is generated properly and I can add regions to my waveform.

[bobfang]

Same problem here. If there is a file URL and peaks data - “ready” event is not fired with “WebAudio” backend (“waveform-ready” if not fired as well). Version 6.3.0. As a temporary workaround I am calling .play() right after the .load() call, catch “ready” event (that is getting fired then) and immediately call .pause() inside my “ready” hook. Then “ready” event is generated properly and I can add regions to my waveform.

this workaround solves the problem for me. thank you! in my case, i am not supplying the duration of the audio clip when loading (since the audiowaveform json output doesn’t carry this information).