Chris Needham

Which streaming server / library are you using? Related: https://github.com/bbc/peaks.js/issues/189

Thanks. Seeking probably isn't working because the browser isn't caching all the audio, and it can only seek within time regions it has cached. For that to work, you can...

Initialising without waveform data currently isn't possible, but I guess it could be made to work by providing the duration, sample rate, and zoom level (samples per pixel), then use...

Another issue is that resampling the waveform data (for the overview waveform) blocks user interaction. If you look at a performance trace, how much time is spent resampling and how...

I've just done a couple of tests. Here's a performance trace with a 28MB waveform, which is taking about 400ms to download the .dat file (on localhost) then 1.2 seconds...

Another approach is to change `Peaks.init()` to take the audio sample rate and waveform samples per pixel values. These should be enough to initially draw the time axis labels and...

@mikkelwf I haven't tried this, but it may be possible to do this already by passing in a custom player object (see doc/customizing.md) when you call `Peaks.init()`, where the player...

By default, clicking the waveform changes the playback position (seek). When the playback position reaches the edge of the view, it updates the visible range. This will prevent the seeking,...

How would you like it to work? Possibly something like this? ```js peaksInstance.on('zoomview.click', function(event) { event.preventSeek(); }); ```

This is more complicated than I thought. Seeking doesn't happen inside Peaks `click` handler, instead it uses `mouseup`. That means simply adding a `preventSeek()` isn't going to work. I tried...