It seems that there is quite a bit of a delay between when packet loss happens and I hear the alert. I was trying to correspond actual network usability issues, with events in Pingplotter -- and the delay between the Pingplotter graphing the issue and sounding the wave file, as WAY off... I tried another wav file (Window's ding.wav, with similar results). Is there a way around this?

I tried the latest beta - and not only is there a delay, the sound doesn't stop!

I reloaded 2.6 (I could just load it in place, right?)

Thanks

Hello.

Reloading 2.6 works in-place. Some of the changes you may have made in 3.15 beta 2 may not carry "back", but everything should work.

As for the delay in starting the alert, this probably has to do with the settings on the alert. If your alert settings require looking at more than one sample, then it may take multiple samples for the alert to fire. For best results if you want your .wav file to fire on each lost packet, set "Samples to Examine" to 1, and Alert when "1" or more samples are over your threshold.

Another possibility for the delay is that PingPlotter waits for a period of time for a timeout. If you unplug a network cable and PingPlotter is set to wait for 10 seconds (9999ms, the default) before it sees a timeout, then the alert won't go off immediately when you unplug the network cable - you'll have to wait for the timeout period to elapse. You can change this in Edit -> Options, Packet. "Timeout Speed". 1000 or 1500 usually works pretty well unless you're expecting long response times as normal.

There is a bug in the 3.15 beta 2 release - alerts don't turn off right, and they are sometimes unreliable turning on. That will be fixed in the next build.

- Pete