jks

Based on the info on kiwisdr.com I'm pretty sure your ISP is blocking all incoming connections. So using the DUC doesn't help with that. Your only solution is to use the Kiwi proxy service which was enabled by default on your Kiwi-2. You can change the proxy configuration to use your call instead of the serial number in the proxy URL as you did with DUC.

Yes, totally different code. Same principles though.

Unfortunately none of this surprises me. A number of years ago Chrome had a bad audio problem. There was someone else who went to battle on the Chrome bug tracker, so I just sat back and waited. It was an ugly fight, but months later Chrome finally admitted there was a problem and fixed it. I was much too busy to get involved directly. I just told everyone to use a different browser temporarily.

@smg No. The entire point of this project is for the Kiwi to not be yet-another-IQ-generator using external PC software. And all the associated headaches. There are plenty of existing solutions for that.

If ever I feel I have no alternative but to go that way then that's the day I pull the plug. There's no point in continuing.

So I would guess this is an issue with Windows and Chrome/Edge not being able to deliver the Javascript realtime requirements for the resampler. The fact that you're not getting any Kiwi under/overruns and the Qlen is stable kind of confirms that.

This entire project is built on the idea that browsers live up to their promise of providing stable, well documented platforms for delivering content/media. And over the years I've been constantly disappointed in the delivery on that promise. I guess I shouldn't be surprised.

I need to know the answers to these questions: How are you recording? Browser audio through a virtual sound card to an app? Kiwi record function to a browser downloaded file? Kiwirecorder Python app to a file or netcat stream?

I looked at a couple of Kiwi (one local, one far) by using the Kiwi record function (record button left of mute button) which downloads a .wav file at the approx. 12 kHz sample rate. Doing so factors out the Javascript code that does upsampling from 12 kHz to the native audio rate the OS is expecting (e.g. 44.1 or 48 kHz). I looked through an entire minute of samples in each case and didn't see anything amiss.

Under/overruns of the resample buffer are reported in the control panel, "Stat" tab, "Audio" line. The system audio rate is shown followed by the audio queue size. If the size goes to zero there's an underrun and if it goes too high an overrun. But usually such an even produces a very large disturbance in the audio. Not just a few msec of drop.