Missing Packets/Underrun

Hi

I have been trying to make sure there is no rf getting back into the shack. I am however still seeing the following in the console for WFServer:

ALSA lib pcm.c:8545:(snd_pcm_recover) underrun occurred
ALSA lib pcm.c:8545:(snd_pcm_recover) underrun occurred
2025-05-06 11:16:59.353 "::ffff:192.168.100.199" : Received token request
2025-05-06 11:16:59.353 "::ffff:192.168.100.199" ( "Control" ): Sending Token response for type:  5
2025-05-06 11:17:20.097 "::ffff:192.168.100.199" ( "Audio" 1 or more missing packets detected, previous:  "0x99e7"  current:  "0x99e9"
2025-05-06 11:17:20.119 udpServer : sending request for missing packet :  "0x99e8"
2025-05-06 11:17:20.120 "::ffff:192.168.100.199" ( "Audio" ): Missing SEQ has been received!  "0x99e8"
ALSA lib pcm.c:8545:(snd_pcm_recover) underrun occurred

What could be the cuase of this?

Is it something to be concerned about?

Thanks

JT

Missing packets are usually a consequence of network issues, wfview uses the same protocol as the Icom OEM software, which is based on UDP. Many consumer grade network devices (switches and access points) often struggle with high numbers of UDP packets (upwards of 200 per second are typical for 16bit 48K audio), but the occasional missed packet is nothing to worry about, you may get a 20ms audio dropout for a single missed packet though.

Hi Phil

Thanks.

It always happens when keying up and then is stable. Any ideas how else I might prevent it. PI is running WFserver and directly connected to IC7300 via USB. So not sure its network related?

For sure blame the USB cable to start… Get a shielded one, and pass it a couple of times thru’ a ferrite ring - no more than 2 or 3 times, and secure it with a cable tie. If it continues, do the same to all the cables connecting to the PI, and maybe get an metal case for the PI. There are plenty out there, from simple thin pressed boxes to full-on billet that has been machined into a heat-sink jacket.

Hi

Yes PI in metal case has USB shielded with cores on.

I will add a core to the netowork cable. The PI is POE so that is the only other cable to it.

Will test and revert back