It would be very convenient for me so that I won’t have to make a special trip to the computer when I run my test programs.
One timer recording is to run from 3am Saturday to 2am Sunday (Yes, 23 hours) Then another track is to record from 3am Sunday to 3am Monday (yes 24 hours). They are not recording at the same time, just set and timing for the same time.
If I could set both of these on the same computer then I could sleep through the night and not have to get up, go to the lab, only to do a restart of the timer recording for the second track.
I could sleep through the night
I believe you only get one Timer Event and I’m pretty sure you can’t automate it with Macros. Somebody will post.
I would do the job in three passes and make the one in the middle long enough to sleep.
The only way you can do this right now is to use two different computers.
We have a long-standing proposal in the Wiki: https://wiki.audacityteam.org/wiki/Proposal_Multi-event_Timer_Record
Some reasons that the devs have held off from this are how to deal with Audacity when it is in yje intervening state between
a) Is Audacity “open for business” on that interregnum (or locked and inaccessible)?
b) If so, what happens when you’re live using Audacity and bump up against the next Timer Record start?
live using Audacity and bump up against the next Timer Record start?
Or overlapping events. You know somebody is going to want to stop one and start the next at the exact same time. No gaps.
I think the only graceful way out (other than two computers) is make a third event longer than one sleep.
Topic moved to “Adding features” section of the forum.
@Emerogork: we also have a long-standing Feature Request for this:
Would you like me to add your vote?
If another vote might make it work out, please do.
I was hired by a company to do something almost exactly like this and it turned out that the best solution was to “trick” Audacity into running two copies of itself at the same time. That part was trivial, at least on Windows - change the application name and product ID on one of the copies to AudacityX (in their case, I made one version Audacity1 and the other Audacity2). This required changing two strings; the Audacity developers would also prefer that a small handful of other strings be changed to distinguish that this version of Audacity is not the “official” version (if this is the only change you are making, only the 2nd needs to have its name changed and the “about” details modified).
Done - but don’t hold your breath (we are a very small part-time volunteer team with fewer developers that the fingers of one hand).
I can do that by logging in as two separate users and having instances of Audacity under each user - the tanglement of how they interact with the system’s audio resources is a bit of a can-of-worms