Version 2.1.3 (and 2.2.1) hangs up on "Timer Record"

Help for Audacity 2.x.x on Windows.
Forum rules
ImageThis forum is for Audacity 2.x.x on Windows.
Please state which version of Windows you are using,
and the exact three-section version number of Audacity from "Help menu > About Audacity".


Audacity 1.2.x and 1.3.x are obsolete and no longer supported. If you still have those versions, please upgrade at https://www.audacityteam.org/download/.
The old forums for those versions are now closed, but you can still read the archives of the 1.2.x and 1.3.x forums.
Turbofiat124
Posts: 12
Joined: Sat Dec 23, 2017 7:41 pm
Operating System: Windows 10

Re: Version 2.1.3 hangs up after 12 seconds on "timer record

Post by Turbofiat124 » Tue Dec 26, 2017 11:07 pm

waxcylinder wrote:
FL Coast wrote:I am having the same issue with Audacity 2.21 on a Windows 10 machine. The timer stops at 11 or 12 seconds while Audacity continues to record. Task Manager is the only way out. I have repeated the issue with varying timer lengths with the same results.
This sounds like the moonphase bug that we know about (as I wrote above) but we have no idea what causes it: https://bugzilla.audacityteam.org/show_bug.cgi?id=42

None of the developers or QA folk can reproduce this with any regularity (or even at all) whicjh makes it very hard to track down

WC
I tested Audacity on my Windows XP SP3 machine and it works with no problems at all. I made a 2 hour test clip and it's currently converting the file from .WAV to MP3 format right now. So it must be an issue with Windows 10. I've kind of been out if the loop for awhile but I remember with Windows 7 there is a compatibility option that can be turned on if some programs won't run right. Too bad , most software was backwards compatable up to XP. I've got a bunch of MS DOS and 3.11 programs that run on XP just fine.

kozikowski
Forum Staff
Posts: 40426
Joined: Thu Aug 02, 2007 5:57 pm
Operating System: OS X 10.9 Mavericks
Location: Los Angeles

Re: Version 2.1.3 hangs up after 12 seconds on "timer record

Post by kozikowski » Tue Dec 26, 2017 11:41 pm

It's a nasty surprise. Windows 10 is not a Windows upgrade. It's a new OS and software has to be written or certified for it. Some software happens to accidentally work most of the time, but those can be time bombs.

Koz

waxcylinder
Forum Staff
Posts: 9434
Joined: Tue Jul 31, 2007 11:03 am
Operating System: Windows 10
Location: Manchester, UK

Re: Version 2.1.3 hangs up after 12 seconds on "timer record

Post by waxcylinder » Wed Dec 27, 2017 11:51 am

Turbofiat124 wrote:I tested Audacity on my Windows XP SP3 machine and it works with no problems at all. I made a 2 hour test clip and it's currently converting the file from .WAV to MP3 format right now. So it must be an issue with Windows 10. I've kind of been out if the loop for awhile but I remember with Windows 7 there is a compatibility option that can be turned on if some programs won't run right. Too bad , most software was backwards compatable up to XP. I've got a bunch of MS DOS and 3.11 programs that run on XP just fine.
I struggle to believe that it is a problem with Windows 10.

have been running Audacity on Windows machines for over 10 years now and all of that time I have been recording 1 and 2 hour shows unattended overnight every single week - and since the 1.3.x Beta series of "releases" I have only experienced this once (and with no obvious cause - that one being set up exactly the same as all the others). Over that Time I have run this on desktops and laptops running XP, Windows-7 and latterly Wiindows-10 (I skipped W8).

I wrote in the bug thread back in September 2013
I am a very regular user of Timer Record, using it several times a week to timeshift radio shows and internet webcasts. Whilst it used to exhibit this behaviour for me occasionally with the early-mid 1.3.x releases I can safely say that I do not recall this happening ever on either the 2.0.3 release nor the 2.0.4 alphas that I have tested regularly on. Nor has this occurred during 2.0.4 RC1 testing.

In January this year I wrote there:
Over the past months I have been using the Timer Record on latest alpha nightlies on my W10 laptop 3 times a week (or more) with one to two hour recordings and it has never failed to honor the set timings, always completing accurately on time and with no over-run.

At the end of June this year for the first time I encountered this bug (on W10) - and lost the recording:
I experienced this moonphase bug for the first time in a very long time last night waking to a a still running 8 hours of recording that was scheduled to stop after 2 hours. The Timed Recording could not be stopped with the Stop button - I was forced to use Task Manager to abort the Audacity app.

On re-launching Audacity I was fully expecting to see Auto-recovery do its job- but no, all it launched was a clean empty Audacity window with no offer of recovery.
I attempted to open the Audacity project - I got an warning message of thousands of orphan files - I elected to continue without deleting those. The project them opened as an empty project.


Subsequently I have continued to use Timer Record for these weekly 1 and 2 hour unattended project recordings all on Windows 10 and with no problem at all, with Audacity terminating the recording at the scheduled time anfd successfully making the requested automatic project save and automatic export of a 16-bit WAV file.


What puzzles me is that I used to get this a lot in the early to mid 1.3.x beta series, but partway through 1.3 Betas and an in subsequent 2.x.x release the problem (mainly) does not occur - except that every now and again the problem raises its ugly unexplained head.

None of the developers can offer me any clue as to what changed in mid 1.3 series that caused the reduction in the occurrence of this bug - so it remains a moon-phase mystery.

I have tried to get the original developer of Timer Record to have a dig into this - but he is otherwise occupied with paid-for employment and other projects.

Peter
________________________________________FOR INSTANT HELP: (Click on Link below)
* * * * * FAQ * * * * * Tutorials * * * * * Audacity Manual * * * * * Audacity Wiki * * * * *

waxcylinder
Forum Staff
Posts: 9434
Joined: Tue Jul 31, 2007 11:03 am
Operating System: Windows 10
Location: Manchester, UK

Re: Version 2.1.3 hangs up after 12 seconds on "timer record

Post by waxcylinder » Wed Dec 27, 2017 11:55 am

Turbofiat124 wrote:One reason I installed Audacity was to record a radio program from 11 to 7 ...
Turbofiat, are you recording from an FM Tuner feeding an external USB soundcard to feed the PC? Or are you recording a webstream?

Reason I ask is that Gale Andrews wrote in the bug thread back in Feb 2016:
Where we know the device concerned for the 2.1.2 reports, it is a USB recording device.

Peter
________________________________________FOR INSTANT HELP: (Click on Link below)
* * * * * FAQ * * * * * Tutorials * * * * * Audacity Manual * * * * * Audacity Wiki * * * * *

waxcylinder
Forum Staff
Posts: 9434
Joined: Tue Jul 31, 2007 11:03 am
Operating System: Windows 10
Location: Manchester, UK

Re: Version 2.1.3 (and 2.2.1) hangs up on "Timer Record"

Post by waxcylinder » Wed Dec 27, 2017 1:02 pm

Since users Turbofiat and FL Coast both report in this Forum thread that this errant behaviour occurs at the 10 second mark or so, I decided to do a little testing (based on earlier reports in the bug thread of excessive CPU usage by Timer Record - https://bugzilla.audacityteam.org/show_ ... ?id=42#c26).

So, testing on my whizzy new(ish) 256 SSD W10 laptop I find:
a) Normal recording consumes just under 3% of CPU
b) Initially Timer Record consumes 3% of CPU
c) After 8-10 seconds Timer Record CPU shoots up by 400% to 15% or so - and continues that way

So it looks as though some Timer Record event occurs at the 8-10 second mark - but what it is I have no idea (but this may offer a clue).

Peter


Update:
I also note that when Time Record is underway (testing on W10 on 2.2.1 and 2.2.2 alpha) for the first 8 seconds or so when the CPU usage remains low the sliders are nicely static. After that time the sliders in the Mixer Toolbar and the Transcription Toolbar flicker as though they are being (unnecessarily) redrawn. I also observe similar occasional flickering of the icons in the Device Toolbar.

With normal recording no such flickering occurs.
________________________________________FOR INSTANT HELP: (Click on Link below)
* * * * * FAQ * * * * * Tutorials * * * * * Audacity Manual * * * * * Audacity Wiki * * * * *

Turbofiat124
Posts: 12
Joined: Sat Dec 23, 2017 7:41 pm
Operating System: Windows 10

Re: Version 2.1.3 hangs up after 12 seconds on "timer record

Post by Turbofiat124 » Wed Dec 27, 2017 3:56 pm

waxcylinder wrote:
Turbofiat124 wrote:One reason I installed Audacity was to record a radio program from 11 to 7 ...
Turbofiat, are you recording from an FM Tuner feeding an external USB soundcard to feed the PC? Or are you recording a webstream?

Reason I ask is that Gale Andrews wrote in the bug thread back in Feb 2016:
Where we know the device concerned for the 2.1.2 reports, it is a USB recording device.

Peter
On my Windows 10 machine I was using an old AM/FM/SW radio with a mono to stereo adapter plugged from the earphone jack into the line in Port on the computer. And set to record on mono.

On my XP machine I was using my cell phone but a stereo 3.5mm cable.

waxcylinder
Forum Staff
Posts: 9434
Joined: Tue Jul 31, 2007 11:03 am
Operating System: Windows 10
Location: Manchester, UK

Re: Version 2.1.3 hangs up after 12 seconds on "timer record

Post by waxcylinder » Wed Dec 27, 2017 4:39 pm

Turbofiat124 wrote:On my Windows 10 machine I was using an old AM/FM/SW radio with a mono to stereo adapter plugged from the earphone jack into the line in Port on the computer. And set to record on mono.

On my XP machine I was using my cell phone but a stereo 3.5mm cable.
OK so no USB device just the onboard soundcards - thanks for the information.

Peter.
________________________________________FOR INSTANT HELP: (Click on Link below)
* * * * * FAQ * * * * * Tutorials * * * * * Audacity Manual * * * * * Audacity Wiki * * * * *

Turbofiat124
Posts: 12
Joined: Sat Dec 23, 2017 7:41 pm
Operating System: Windows 10

Re: Version 2.1.3 hangs up after 12 seconds on "timer record

Post by Turbofiat124 » Wed Dec 27, 2017 4:56 pm

I also meant to add I was using the FM radio on my Moto Z cellphone. Verizon blocked the FM radio for a few years until someone filed a complaint with the FCC. Apparently it illegal to hinder someone from listening to free broadcasts in the United States. Verizon did it so they could sell more expensive data like having to use Tune-in radio just to receive local radio.

Turbofiat124
Posts: 12
Joined: Sat Dec 23, 2017 7:41 pm
Operating System: Windows 10

Re: Version 2.1.3 hangs up after 12 seconds on "timer record

Post by Turbofiat124 » Fri Dec 29, 2017 5:29 pm

waxcylinder wrote:
FL Coast wrote:I am having the same issue with Audacity 2.21 on a Windows 10 machine. The timer stops at 11 or 12 seconds while Audacity continues to record. Task Manager is the only way out. I have repeated the issue with varying timer lengths with the same results.
This sounds like the moonphase bug that we know about (as I wrote above) but we have no idea what causes it: https://bugzilla.audacityteam.org/show_bug.cgi?id=42

None of the developers or QA folk can reproduce this with any regularity (or even at all) which makes it very hard to track down

WC
I initially though this "Moon phase" you guys were talking about was a web browser but I that must be Pale Moon or Moonlight.
I tried to do a search on this moon phase but everything that pops up is based on the actual moon.

kozikowski
Forum Staff
Posts: 40426
Joined: Thu Aug 02, 2007 5:57 pm
Operating System: OS X 10.9 Mavericks
Location: Los Angeles

Re: Version 2.1.3 (and 2.2.1) hangs up on "Timer Record"

Post by kozikowski » Fri Dec 29, 2017 8:24 pm

It is based on the actual moon. It's a metaphor for an undesirable event that might appear every 30 days or so. Almost impossible to troubleshoot.

A far older metaphor is "top-dead-center" where a single-cylinder farm motor would occasionally stop at the end of the work day with the moving cylinder at the exact, perfect top of its travel making it all but impossible to start the next day—for no apparent reason.

That's not to say there aren't steps that can be taken. The range of efforts is not limited to making it better. It's valuable if someone can reliably make it worse.

"If I overload my machine with activities, it fails once a day rather than once a month."

Koz

Post Reply