Chris Needham

That's not currently possible, as all the views are based on the same (single) waveform and media player.

It looks like the Windows build of audiowaveform doesn't handle non-ASCII characters on the command line. For now, I can only suggest renaming the file, as a workaround.

Peaks.js does not currently have an option where you can give it your own `WaveformData` object. If you generate the waveform data JSON server-side, you can use the `dataUri` option...

This library does not support real time input at this time.

I'd really like to get to a fully working example with HLS and Peaks.js. I recommend checking the length of the audio segments, audio sample rate, and scale value. Try...

Ah, good point. I'm happy to pick this up, unless you're already working on it?

We have a `.concat()` method for joining two waveforms, so it could make sense to add this. Can you describe your use case in a bit more detail, though?

OK, so could it work in the same way as [Array.slice()](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Array/slice)? This code would return a new WaveformData instance containing the waveform from `startIndex` to `endIndex`, leaving the original `waveformData`...

I can't promise when I'll be able to look at this, but if you (or anyone else) wants to work on it and send a pull request, I can give...

Yes, it was inspired by the wav format. There's documentation for it [here](https://github.com/bbc/audiowaveform/blob/master/doc/DataFormat.md).