Kevin Reid

Also, the view-that-is-not-a-waterfall (why don't we have an unambiguous simple name for that yet) already has some minimal unscientific filtering (it tries to take samples across the span of one...

Improved in commit e62d1ada13a0b8af4e13b416932b6e57ec4f05fa. > For some reason I haven't yet tracked down, the difference signal > is weak, which is why the output was basically mono. Now I've amplified...

The stereo decoding was happening after FM deemphasis, which accounts for the weakness of the difference signal. That's fixed in f8d959c1f761be3197f124421e50e00affb7fd78. However, there is still an extreme sensitivity to the...

Which browsers, exactly? In Chrome, I would guess this is due to the newly enabled [autoplay restrictions](https://developers.google.com/web/updates/2017/09/autoplay-policy-changes), but that shouldn't trigger on repeated visits to the page. Is it really...

That sounds like the AudioContext isn't running (the sawtooth is the audio buffer repeatedly filling up and being thrown out). Please check the console for messages.

Sorry, I mean the browser console.

In my experience, that message can appear even if the AudioContext is working normally. Could you please copy the _entire_ console text so I can see the sequence of messages?...

OK, unfortunately, that's essentially the same set of messages I see routinely. I've got some ideas, but it'll probably be a few days before I have them out for you...

I pushed 446e6dd45ffbbebf82812e2d4bb2b521984d5746 which adds debug logging. For me, on reloading, I get this for a log: ``` main.js:95 Loading plugins… main.js:95 Connecting to server… ws-stream.js:72 The AudioContext was not...

I also notice in your log that the audio stream is running in ScriptProcessor mode rather than AudioWorklet mode. This is surprising. Could you specify exactly which Chrome version you're...