Chris Needham

Closing as not-planned, because I won't be able to distribute binaries due to patent implications.

I have added JSON support in https://github.com/bbc/audiowaveform/commit/dccc7ade7f20f63f161e4c1ab700605234e843d2.

So instead of `slice()` which would return a new object, a `trim()` method that removes data from the existing object?

The distinction I was thinking of was `slice()` which leaves the original waveform unchanged, vs `trim()` (or some other name) which would modify the original waveform object in-place.

I've added a `slice()` method, now available in v4.4.0, here's the [API documentation](https://github.com/bbc/waveform-data.js/blob/master/doc/API.md#waveformDatasliceoptions).

Sorry for the delay in replying. On my laptop, with DirectX9 selected, and any screen mode other than "Current Screen Resolution", entering full screen causes BeebEm to enter a loop...

Sorry for taking so long to follow up. I have now added your icons to the master branch, so will be in the next version release, coming soon. Thanks again....

I've now added FSD support.

I don't think this should be removed. At a minimum we need to describe how they're coordinated, the need for named contacts in each organisation, relevant W3C groups, listing in...

I think that's fine. The original intent behind the suggestion was for OSP to potentially support tightly synchronized playback between agents (e.g., sub 10ms). That would require an additional timeline...