I have written about this before, but I wanted to collect more data before posting again. This is a continuation of this thread: Really? Can no one explain how to interpret the numbers in bottom right corner? - #4 by eliggett
I’m trying to understand if the latency number can help me determine why I get this strange delay.
This is a problem I have had all time since I started with wfview close to a year ago. Across all versions and upgrades.
The fault description is like this:
Let’s say wfview has been up and idle for a few hours. If I press TX and start talking into the mic, visually I can see that the remote and the client vfview goes into TX and thus the physical radio. But I’m still having receive audio in my headphones. It can take up to 4 seconds, or in extreme cases a lot longer, before rx audio is muted in the headphones. Similarly at the end of the tx sequnce, I press receive and the physical radio switches to rx, which is confirmed visually. But audio is still muted. After up to 4 seconds, the rx audio finally comes back in my headphones.
If, I quit wfview on both sides and restart, latency is low, around 200-300 ms. The latency is consequently building up again to 1000-4000 ms until next restart.
I have caught this behavior on a screen recording. It’s rather extreme, the latency here is 21 seconds, because I intentionally left the connection up for several days to illustrate the problem. Of course I can reset the connection every so often, but that only helps to get rid of the symptoms. It’s not curing the root cause.
This is what you can see in the screen recording:
5s mark: tx is clicked. I talk into the mic. One can see that visually on both the remote and the client. But I still have receive audio in my headphones. You can see that on the sound properties window also seen in this screen capture. The level bar indicates the audio I have in the headphones.
27s mark: Receive audio mutes which you can see in the sound properties window. In wfview you can see that I’m continuing to modulate tx.
43s mark: you can see how the client and remote returns to rx. But there is still no audio in the headphones. This is confirmed in the audio settings window.
1m:04s mark: I finally get RX audio back in the headphones, which is confirmed by the audio settings window.
The second screen recording shows the same thing but at 1400ms latency.
Client: Windows 11 PC, i5 with 16gb RAM. Ethernet to fiber modem and 100Mb speed to ISP.
Remote: Windows 11 PC, i3 with 8gb RAM. Connected to router with wifi. Wifi signal strength is
-50dBm, considered to be “a good connection” by the Wifi-analyzer app. Router connected to ISP on 100MB fiber.
Here are links to the screen recordings (hope the sharing works)
Long version: https://1drv.ms/v/s!Ar4cpJa3-82mx55R-eu2v3bL8bUEoQ?e=pu3kgc
Short version: https://1drv.ms/v/s!Ar4cpJa3-82mx55Qq5IyOYUYs-bDjg?e=VnePfA