FR: Task Scheduler, Win 7, Audacity 1.3 Beta

[Edgar]

@Emerogork2

Add the benefit of being to access the program through a command line interface. I would like to invoke a batch file from the Windows Task Manager to start and another batch file to stop a recording at given times in a schedule.

This is probably quite trivial to accomplish; see this thread for the basics:

Unattended command line processing

http://home.wavecable.com/~edgarmusgrove/index.html#UnattendedAudacity This is not really intended for the user who is unfamiliar with the Audacity source code and C++ programming! When you run this app from the CLI there will be NO GUI you will have to watch for the command prompt to return to know it is finished. It is really intended for unattended batch processing (I set it running in a batch process with hundreds of file when I go to bed and all is finished in the AM). If you have a spe…

add a new CLI switch -doStartRecording (or whatever you like) and -doStopRecording (the matching functions are in Menus.cpp (OnRecord & OnStop). If you need help getting Audacity compiled just ask and I will get you up and running. If the programming is too difficult I can help with that as well.

@Emerogork2

Second to having that access, how about settings in Audacity that would automatically invoke when audacity is called from the task manager. Have an instance of audacity “know” to start recording when called and know how long to record then save.

“called from the task manager” ???

This would also be doable if you had CLI switches: -startTime & -recordLength plus -saveName
but getting the saveName parsed given spaces are allowed would be a bit tricky. One option would be to not allow spaces (but remember this has to be a fully qualified path: x:foldername.extension) in the supplied name; another would be to require that -saveName be the last switch with everything following (spaces and all) being the string composing the fully qualified path.