jks

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).

Okay, I fixed this. Wasn't too bad. Will be in the next release.

Will allow any future internal extensions that use the waterfall to work also (currently our WSPR and FT8 internal extensions only use the audio stream).

If it's really only two characters it might be that operating at 9600 baud will be okay. You'd just have to try it and see what happens as far as any realtime impact.

From the CHANGE_LOG file:

I checked the code, and I had added something. But in looking at it I see what I did wasn't quite right.

So I have something now that I think will work. Will be in the next release..

I have the web server log and that's all I need. tcpdump when anything more specific required.

I'm not going to continue talking about this since we don't know who's reading the forum.

Not following this in detail because I'm so busy. But try and run this at 115k baud at least to avoid impacting the Kiwi realtime performance (i.e. causing the audio to break). That was my experience when I added the CAT output option that also used /dev/ttyUSB0 (and /dev/ttyASB0 if necessary).