First and foremost,
EXCELLENT PROGRAM!
Gmail support is working spot on...a much welcome (arguably necessary) addition to the program!
As far as the tone detection, maybe it's just me but it seems to slightly lowball them? I created a few "clean" test tones in Audacity and checked to see what your program was detecting them as. Here are the results:
Actual: 500.0 - 1500.0 / Detected: 496.62 - 1489.86
Actual: 1232.0 - 2260.0 / Detected: 1223.68 - 2244.73
Actual: 2500.0 - 1500.0 / Detected: 2483.11 - 1489.86
Actual: 2807.0 - 1000.0 / Detected: 2788.03 - 993.24
According to my calculations, a 0.681% increase to the tone detection would get you almost dead on accurate across the spectrum. Can the detection algorithm be adjusted that way? Might not seem like a large %, but when you're trying to keep the tone tolerance setting as tight as possible to avoid falsing where systems use very close or mixed tones (454.6 P49 and 457.9 M116, for example), it works out to be quite a bit!
Can you make it so the "Play .WAV file after recording" option saves its state to the config file after SAVE & EXIT? I wouldn't use that option, and I keep forgetting to uncheck it each time I open the program.
Is it possible for the program to go back to listening while the email is being sent, or is that a limitation of the software platform? It locks up for as long as it takes to send the email, which might result in missed pages. Perhaps a way to send the emails to a background queue, thus freeing it up to resume monitoring?
How about a way to adjust the record time? I realize 30 seconds is good for most ideal systems, but when you have a system that sounds 4 sets of tones for a single dispatch, you're lucky to get maybe 10 seconds of the actual message! Ideally, an option to set the record time on a per tone set basis would be absolutely outstanding, however I would settle for an across the board ability to adjust it if that's not feasible.
Is it possible to have the output files follow a similar naming convention as the email subject, instead of "soundclip.wav" (with the obvious filename character limitations taken into account)? Attempting to archive a bunch of clips all with the same name would quickly become a chore.
I realize I hit you with a lot of stuff in this post, but I figure if you're putting this out there for people to beta test, I'm going to run it through its paces and give you honest feedback and suggestions! A few months ago I played around with the Snooper method of sending alerts you have on your site, but I feel this software you've written is so far a better method for a few reasons. Keep up the great work, I look forward to playing with new releases of it!