Is the Hardware settings ping result meaningless for my location?

[VE3MEO]

Jamulus OS reports ~30ms and 'ping too high' on hardware on which the client on Windows 10 is seeing 9-11ms on servers 100-120km away. At what target does the test ping?

I've yet to get the client running under Jamulus OS. The audio hardware probe gets hung up on HDMI.

[VE3MEO]

The client on Jamulus-OS is seeing pings comparable to what the client previously saw using Windows 10 on the same hardware (9-11ms). The warning message from the hardware probe is misleading.

[Laurent Schwartz]

Thx for reporting !

I'll check that.

[Laurent Schwartz]

The speedtest command line which i use to probe the network, provides a web service which operates automatically to the nearest server available.

In your case, the nearest server is too far for the ping time to be relevant ...
I added some more testing and changed the message given to the end user. But if the server is far, i can not say if internet connection is good enough ...

I will search for better solution ... Any help on this topic is welcome !

For HDMI sound cards, this is a known bug .... Just select your sound card to be tested rather than testing all sound cards and please avoid HDMI ones.

[Peter Goderie]

Can't you just ping the google nameserver 8.8.8.8 as reference ? That should automatically be the nearest server.

For me in The Netherlands the Hardware Settings ping is always over 40 mSecs but the 8.8.8.8 Ping time is just 10 mSec.
Also I think the 10 mSec as maximum limit is a bit demanding, since the overall delay is what counts and an overall delay less than 50mSec is most of the time still achievable with ping times up to 25 mSec.

My advise would be:
ping <= 15mSec == OK
ping > 15mSec and <= 30mSec == WARNING (Check your overall delay !)
ping > 30mSec == ERROR