Chris Needham

> Ideally, waveforms scroll when the seeker reaches the end of the waveform, i.e., at the exact last timestamp of the rendered view when playing. Although you can provide an...

You are very welcome to try to fix this. Peaks.js listens for `click` and `dblclick` events from Konva, [here](https://github.com/bbc/peaks.js/blob/9c917f4db3cf1a30713e44dd9b562a217efbc390/src/waveform-zoomview.js#L146) for example. So you may also need to look at how...

I have not been able to reproduce this problem, using the [demo pages](https://github.com/bbc/peaks.js#demos). If I double-click on a segment, I see these events: ``` segments.click: {segment: Segment, evt: MouseEvent} zoomview.click:...

In case it helps, I think that the relevant code in Konva that generates click and dblclick events is [here](https://github.com/konvajs/konva/blob/07df75606631b1213a8283fac77775357c6b6ede/src/Stage.ts#L653).

With insert-segment mode, any click will result in creating a new segment (whether inside our outside an existing segment). I'd expect these new segments to become selected on creation, which...

Thanks, I think I understand what you want to do. Should Peaks.js automatically prevent creating a new segment if you click an existing segment in `no-overlap` mode? At the moment,...

This should be working now, please try out v3.2.3 and let me know what you think. Thanks!

I forgot to add code to reset the state on mousedown, so it would work the first time but not after that. I've just published another update.

This is because the waveform data doesn't have enough pixels to fit the canvas width. The easiest solution is to create the waveform with a lower number of samples per...

Currently, no, but I'm interested to enable this with DASH streaming, see https://github.com/bbc/peaks.js/issues/364.