Chris Needham

I have no plan to add a floating point output format, as it increases the file size for no benefit, and we'd have to add an equivalent binary (.dat) format,...

You're right. The number ranges are mentioned in the [file format documentation](https://github.com/bbc/audiowaveform/blob/master/doc/DataFormat.md).

Do you mean the absolute min/max possible values (i.e., -128/+127), or the measured values `min(data)` and `max(data)`? The former can be inferred from the `bits` field in the JSON. BTW,...

audiowaveform doesn't currently accept JSON files as input. It could be added, but it's not been a high priority so far because (in our use), we create and store the...

Thanks @greedybro. I guess We could provide .deb files as part of the audiowaveform release process. If anyone is interested in contributing a solution and documentation for that, please let...

This isn't something we've considered so far. An approach you could use is similar what Peaks.js does for drawing the waveform: - Compute and store the spectrogram data from `AnalyserNode.getByteFrequencyData()`...

I'm sorry, this isn't supported. At present, Peaks.js is currently only designed to show waveforms for pre-recorded audio. I'd be happy to consider adding this feature if any contributor is...

Sure, look at [WaveformZoomView.pixelsToTime()](https://github.com/bbc/peaks.js/blob/5727854ff2823d2c6aedac8cec89808d1d0669e7/src/waveform-zoomview.js#L431) - pixels are the waveform data points, scale is number of audio samples per pixel, and sample rate is audio samples per second.

> Hello again > sorry I have a question again, :) No problem :-) > what's the reason that it doesn't support? It has a limitation or just the team...

Yes, this sounds like a good feature to add.