Chris Needham

Right now, Peaks.js is tied to using a media element, so `setSource()` is there to change the `mediaElement.src` property and update the waveform view. I assume with `AudioBuffer`, you're not...

Hi Bartlomiej, Please let us know Linux distro and version you're using. Did you see the instructions for installing under Fedora in the ReadMe? Note that we have binary packages...

@itsmrwave Great to hear that you have this working!

This happens because the width of the container element for the overview waveform view is zero. Take a look [here](https://github.com/bbc/peaks.js/blob/master/src/main.js#L204) and [here](https://github.com/bbc/peaks.js/blob/master/src/main.js#L39). Are you passing your own template?

Hi @zachsa, I'd like to track down what's causing this. Are there any more details, or maybe a minimal example you can share?

Is your web server setting an `Access-Control-Allow-Origin` header in response to requests for the audio file or waveform data?

This is an interesting question. The current [customization API](https://github.com/bbc/peaks.js/blob/master/customizing.md) doesn't give you control over where the segment label is placed. I did a quick experiment: If you want the label...

I have not been able to reproduce this. I tested the build instructions in Docker using `alpine:latest`. Do you need to build your own Docker image or could use use...

Thanks for reporting this, and for including the code to reproduce the issue. This will help me investigate what's going on.

We may need to fix `Peaks.init()`, but the way I suggest you implement this is to call `peaksInstance.setSource()` to change the audio URL instead of destroying and re-creating the Peaks...