I continue to make progress even if it is exceedingly slow by the standards of you competent lot.

I have added record and play lamps. The play lamp extinguishes itself when the current WAV file has finished playing. To determine when the lamp should switch off I could divide the file length by 11,000 (khz) that would give me a rough length of the play time. Instead, I am counting the length during recording and then adding that duration number to the unique filename given to each output WAV file. When playing I use that duration and extract it to send to a timer that extinguishes the lamp after the duration plus one second. There is probably a more elegant method using mciSendString querying the play state or similar but it works and it'll do.

I'm adding automated backups and archiving to the data. In addition I am adapting it to use other file/folder sharing utilities such as Google Drive or Onedrive, if they can share files and folders and cause a resource to appear locally to Windows then my program can use it.

My programming partner is developing the javascript version simultaneously and it runs mainly on Mac OSX, he is having trouble recording MP3 files using the Mac OS, it wants to create M4A format files only. It seems OSX wants to restrain you from using industry standard file formats and it does not seem to have the same level of API access to do this or that as we expect from Windows.