jks

I've found the problem. I'm trying to get a release together as soon as I can. But it's much more difficult these days.

I’ll bet this happens if there’s a delay determining the local IP. Although I don’t know why that would be. That should occur almost immediately. I’ll take a look.

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.

Okay, the bug is that where you say echo "Selected antenna: $sel" you need to say antennas i.e. plural. This is because most of the backends have the possibility of mixing antennas and hence returning multiple antennas selected at the same time. The parsing of the response is fixed and looks for "antennas" specifically.

Your script is very good. I had the impression you didn't quite know what to do. But it's absolutely fine. Here's a version with a simulation mode (SIM=1) I used to find the problem without actually having the raas4 hardware:

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.

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.

What happened to your previous script? It was much closer to being correct. That vibe thing is crap.

Your AntSW_ShowBackend function needs to return info in the exact format as shown below (example from the beagle-gpio backend). A version number as second parameter is missing. The number of channels 3rd parameter is missing the "ch" directly after the number. A "mix" or "nomix" 4th parameter needs to indicate if the switch can mix antenna selections.

Get rid of that case ... esac stuff at the end.

AntSW_ShowBackend() {
  ...
  echo "beagle-gpio v2.0 10ch mix not-applicable"
  ...
}

This has been a problem in the past, but is not known to be an issue currently.

The most sensitive test of dropped samples is to run the FAX extension. The slightest dropped sample will cause the image to become progressively more shifted (i.e. lines looking broken) as the image rendering proceeds. I tried this just now on several Kiwi running the most recent software version and all seemed well. An example image is below. All those lines should not have any offsets or breaks. The 400 pixel tall FAX viewport at 120 LPM represents 3.33 min of reception. So no dropped samples over that time period.

Have you tried different browsers? One factor in the audio is that the browser's scheduling of the Javascript audio processing must not have any realtime performance hits. Otherwise samples can be lost. But that's a browser problem not a Kiwi problem.

The audio and waterfall use completely different mechanisms and so any glitching should not be correlated. If they are that may point to network issues.

Yes, it is possible the Ethernet on the Beagle is beginning to fail. Specifically the Ethernet PHY chip. There was trouble with this some years ago that seemed to be a bad batch of PHY chips, although this was never conclusively proven.

You could consider replacing the Beagle with a new Seeed BeagleBone Green. Roughly $50 USD + VAT. Be careful not to use any other Beagle type. Specifically not the Seeed BeagleBone Green Wireless. It is not physically compatible with the Kiwi board. If you can find the older BeagleBone Black that will work also. But make sure it is a "rev C" board that has 4 GB eMMC (not 2 GB).