I had the same issue with presenting a simple interface to the operator.
I won't go into the issues with Windows Mic test here. Suffice to say it won't do what I need. No idea about Windows Speaker test.
I’m only using SoundLab to run curves and save them to disk, and then display the results after I’ve smoothed, normalized, and checked them against the test limits.
I’m using VB for the GUI. The rest is done in either a dll or in VB.
To drive SoundLab I’m using AutoIt:
I place my program windows on top of the SoundLab windows (forced on top, so the normal menus are hidden).
I then generate a number of script files on the fly to save, and load curves back into SoundLab. I load the scripts and drive SoundLab through AutoIt.
As mentioned, I also save data, and do things like warn if the reference mic curve is too old, send an email to the supervisor if network connectivity was lost, etc.
Here are a couple of quick screen shots to give you and idea on the operator interface.
It’s far from elegant, but it’s been working pretty well.
I have a separate program I developed for creating limits and doing some batch analysis.
It’s a more “finished” program, and if you’re curious, here is the help file. (CHM format so save it to disk to view.). Of course it was developed specifically for my own needs.