Chris Needham

This is currently not possible, but it's a good use case.

The duration is reported in the output as `Frames decoded`, 7.164 seconds in this example: ``` $ audiowaveform -i test_file_stereo.mp3 -o test.json -b 8 Input file: test_file_stereo.mp3 Format: Audio MPEG...

For WAV files, the output is a bit different - you can use the `Frames` (reported from the WAV file header) or `Read x frames` (the number of frames actually...

Yes, the `--width` and `--height` options only apply when creating PNG images. For JSON output you'll need to set the `--zoom` option (or `--pixels-per-second`).

The calculation you need to obtain the `--zoom` value for a given image width and audio duration is [here](https://github.com/bbc/audiowaveform/blob/master/src/WaveformGenerator.cpp#L85). Rounding errors mean the resulting JSON isn't exactly the length you...

At the moment, only solution is to either truncate or pad the data to the desired length. You're not the first person to request this, see also #41, #104, #108.

I'd like to take a look at the MP3 file, if you're able to share it with me (either here or by email if you prefer).

This is likely related to https://github.com/bbc/audiowaveform/issues/49. Your MP3 file has an information frame at the beginning, which audiowaveform skips over, and this could explain the difference you see at the...

audiowaveform does not use the same MP3 decoding as Audacity, so I think the question should be: does the visualisation agree with the audio you hear, in Peaks.js? Matching Audacity...

These events are emitted before the cursor is moved (and the audio playback position changed). There currently isn't a way to prevent the default behaviour. Can I ask what the...