Just for clarity, as I have posted earlier, Add Track works fine for setting up timed recordings. Simply recording without pre-defined stop points or track lengths works fine too. At this point, I’m just trying to help trace an apparent problem with Timer Record in 2.1.2 by trying out various suggestions from Gale. The laptop is working fine.
At this point, I’m just trying to help trace an apparent problem with Timer Record in 2.1.2 by trying out various suggestions from Gale. The laptop is working fine.
In my opinion, you will never find it by gazing intently in one place. You don’t know the laptop is working fine until you resolve the problem.
Does Audacity 2.1.1 or 2.1.0 work?
Time events work by comparing the desired time to the computer time. An event triggers when they match. You can get missed triggers when either of them is damaged or wrong.
It would be very valuable to know if either of the earlier two Audacity versions works.
2.1.2 is the only version of Audacity I’ve used. I don’t have earlier versions.
As I said, you could download 2.1.1 from http://www.oldfoss.com/Audacity.html. You can download the ZIP of 2.1.1 to try it and then just delete it if you don’t want to keep it. I think you will find 2.1.1 does not have the problem.
I have 2.1.2 and am experiencing the exact same problem as the original poster. I’ll try the workarounds, but wanted to give some feedback.
Bit of an older post, but just wanted to say it’s affecting me too. The older version of audacity was fine (think it was a 1.3). Windows 10. HP G56 laptop. AVG antivirus (but with audacity added into the safe apps).
OldFoss no longer hosts Audacity 2.1.1, so if necessary you can obtain 2.1.1 here: http://gaclrecords.org.uk/legacy/ .
I just wanted to note that I have the same problem. I have not used this feature for a long time until today. I need to archive about 1700 church tapes, so I need to do a bunch of 30 minute recordings. I downloaded and upgraded first, to 2.2.2. Not sure what was running before, but I think this feature worked.
This is one of our longest standing bugs #42: Timer Record occasionally carries on recording past the scheduled end, requiring force quit
It was originally logged just over eight years ago now and we’ve never been able to get to the bottom of it. The problem being is that it mostly doesn’t happen and when it does it’s only very occasionally - so we can’t find a set of reproducible steps to make this happen - it it fails consistently for you then we would very much like to know what steps you take that cause it to occur.
I myself got bitten by it once in the middle of last year: http://bugzilla.audacityteam.org/show_bug.cgi?id=42#c29
But other than that I use Timer Record every week and it works just fine.