Audacity Forum

Emerogork wrote: ↑

Mon Jul 30, 2018 10:02 am

Unless it can be developed to start and stop hourly, and maybe with the capability to name tracks automatically, it is just a novelty for me and not of much use.

What you really need is this proposal (that I wrote a long time ago) implementing:
https://wiki.audacityteam.org/wiki/Prop ... mer_Record

Peter

A noble request it is but I might propose a much simpler approach and a smaller step. I suggest to add an option in the pull down menu for "After Recording Completes" which says "Restart Timer" and then ask how many times to repeat. All the code needs do is activate the OK button for the given number of times entered.

I am sure that the rest of the proposal, already in place, would require much more work as it appears to require a data base to implement.

Emerogork wrote: ↑

Mon Jul 30, 2018 12:09 pm

A noble request it is but I might propose a much simpler approach and a smaller step...

hahaha

Peter.

Emerogork wrote: ↑

Mon Jul 30, 2018 12:09 pm

I suggest to add an option in the pull down menu for "After Recording Completes" which says "Restart Timer" and then ask how many times to repeat. All the code needs do is activate the OK button for the given number of times entered.

I'm a big believer in using the right tool for the job. In this case (as described above), I don't think that Audacity is the right tool.
For the case of making a sequence of consecutive recordings, it would be much better for the app to stream the file direct to disk. Audacity does not do that. Audacity writes thousands of little data files in 32-bit float format. To save a file, the data needs to be read back from the disk, encoded in the appropriate format, written back to disk as an audio file, then clean up the thousands of data files - all before it can continue with the next recording.

The way that I would approach the task on Linux (my preferred operating system), would be to use a simple command line recorder, such as arecord or SoX, and a crontab script (similar to Windows scheduler) to start the job, name the files and close. The tasks could ovelap a little so as to avoid missing any of the recording between tasks (Audacity cannot do that).

I'm sure that a similar approach could be taken on Windows and Mac, but it's also likely that searching Google could bring up a ready made app designed specifically for this task (try searching for "surveillance voice recorder" or similar terms).

Emerogork wrote: ↑

Mon Jul 30, 2018 12:09 pm

I suggest to add an option in the pull down menu for "After Recording Completes" which says "Restart Timer" and then ask how many times to repeat. All the code needs do is activate the OK button for the given number of times entered.

Pyaudio could be worth looking at: https://people.csail.mit.edu/hubert/pyaudio/docs/