On OS X 10.7.5. Audacity 2.13 Dec 19 (I think anything after 2.1.0) won’t work with Timer Record.
Trying to complete a Timer Record by either using all the time in the timer or by pressing the stop just continues in the continual recording. Force-quitting the app is the only way to stop recording.
I know there has been trouble getting this to reproduce based on other messages. So if it would help to make a vmware environment of 10.7 to reproduce the problem because the dev’s don’t have a 10.7 system please let me know and I can try to do that and upload it.
Right now it’s a big issue because basically the bug kills any use on these old machines when Timer Record is needed (which is on every digitization for me.)
Also the date dialog seen here shows the wrong formatting of Monday, Day, Year as it no longer matches the local set in the system. We don’t use DD/MM/YYYY in the U.S. and it can be very confusing when dealing with days and months that are similar in number. The format should ideally match the system pref’s data preference.
Are you sure that 2.1.1 has this problem? For the small number of people on Windows who have this problem, the recommendation is to go back to 2.1.1.
Thanks for the offer, but VM’s are not suitable for reproducing bugs that are connected with Audio I/O. I am not a developer, but I should be getting an older Mac after Christmas that can run Lion (and Snow Leopard), so I will have the ability to test then.
The most useful thing you could do right now would be to try 2.1.1 from http://gaclrecords.org.uk/legacy/. If 2.1.1 has the problem, it is not the same bug that is affecting some Windows machines.
Have you ever tried recording standard stereo from the built-in input to see if Timer Record fails in the same way?
Even that seems machine-specific or possibly specific to different versions of OS X/macOS. I was not able to reproduce it on El Capitan when I had that, after changing system language to US and rebooting.
Please test that in 2.1.1 (as above) too, if you can.