Timer recording does not want to stop !

[Gale Andrews]

Iv'e just noticed we've got linking back in 1.3.13 - no idea how to use it or what it's for though ...

See http://forum.audacityteam.org/viewtopic ... 16&t=32127


Gale

[bgravato]

Instead of the parameters being start time and end time, it could be start time and duration...

Bruno,

you can already do that - in the setup dialog box for Timer Record there are three input boxes:
1) Start Date and Time
2) End Date and Time
3) Duration

Setting the duration in box 3 will change the end time in box 2 and vice versa.

In order to emphasize that it's the duration that is relevant, maybe the order could change to:
1) start time
2) duration
3) (estimated) end time

Adding an "estimated" prefix to the end time would be suggestive of what really happens.
Also the manual should have a note on that regard... (sorry if that's already covered, I didn't rtfm...)

[Gale Andrews]

In order to emphasize that it's the duration that is relevant, maybe the order could change to:
1) start time
2) duration
3) (estimated) end time

Adding an "estimated" prefix to the end time would be suggestive of what really happens.
Also the manual should have a note on that regard... (sorry if that's already covered, I didn't rtfm...)

I've added more text to the Manual.

I would imagine the assumption is that people are thinking more of the end time (that show ends at 9 pm) than the duration).

I'd think adding (estimated) probably makes more complications than are worth trying to explain, especially while behaviour isn't yet predictable.


Gale

[bgravato]

I remember when I used to use mythtv to record programs from tv... When I wanted to enter a manual schedule the parameters were "starting time" and "duration" there was no "ending time". I never felt it was awkward... it always felt that was normal... probably because that was the only option available... Ppl get used to what they have available

[waxcylinder]

So can you download again Peter and work with that version? Apart from the patch, it is still built against 2.8.11.

ok - the two timed recordings that I did last night with Nikolay's patch worked absolutely fine. Both were one hour five minute recordings one of which straddled midnight. Both were made without pre-saving a project so the temp files were in play.

I will continue to use this vn. for timed recodings to test it more.

WC

[phabaudac]

On last Sunday (yesterday) I tried again to run a timed recording (I am still using Audacity 1.3.13-alpha-May 15 2010, linked against widgets 2.8.10).
The start time was set to 21:00 and the duration to 1:00. Again, the recording did not stop at the expected end time (22:00) and I had to kill Audacity to stop it. Before killing it, I noticed that the panel with elapsed time and remaining time had frozen approximately half an hour after the record had started (screen saver disabled). I don't know whether both misbehaviors are related. Also, unfortunately I forgot to disable pulseaudio before the recording started, so pulseaudio remains suspect...

[Gale Andrews]

On last Sunday (yesterday) I tried again to run a timed recording (I am still using Audacity 1.3.13-alpha-May 15 2010, linked against widgets 2.8.10).
The start time was set to 21:00 and the duration to 1:00. Again, the recording did not stop at the expected end time (22:00) and I had to kill Audacity to stop it. Before killing it, I noticed that the panel with elapsed time and remaining time had frozen approximately half an hour after the record had started (screen saver disabled). I don't know whether both misbehaviors are related. Also, unfortunately I forgot to disable pulseaudio before the recording started, so pulseaudio remains suspect...

I don't expect the screen saver freeze and the timer record freeze are related - you got the timer freeze when no screen saver came on.

It would be better if you could first test ordinary (not Timer) recording to test the effect of disabling Pulse when you have the screen saver (only) enabled and the screen-sleep (only) enabled.

If you get around to compiling Audacity, you can try Nikolay's patch to see if that helps the Timer Record "not stopping" problem. I think 2.8.10 or 2.8.11 probably won't make any difference - it doesn't on Windows.



Gale

[waxcylinder]

Well Iv'e used the the 1.3.13 vn with Nikolay's patch for several recordings now (c. 10 or so) and it hasn't failed yet, always honouring the proper stop time <<touches wood quickly>>

Will continue to test this vn with my future time recordings.

WC

[phabaudac]

On last Sunday (yesterday) I tried again to run a timed recording (I am still using Audacity 1.3.13-alpha-May 15 2010, linked against widgets 2.8.10).
The start time was set to 21:00 and the duration to 1:00. Again, the recording did not stop at the expected end time (22:00) and I had to kill Audacity to stop it. Before killing it, I noticed that the panel with elapsed time and remaining time had frozen approximately half an hour after the record had started (screen saver disabled). I don't know whether both misbehaviors are related. Also, unfortunately I forgot to disable pulseaudio before the recording started, so pulseaudio remains suspect...

I don't expect the screen saver freeze and the timer record freeze are related - you got the timer freeze when no screen saver came on.

It would be better if you could first test ordinary (not Timer) recording to test the effect of disabling Pulse when you have the screen saver (only) enabled and the screen-sleep (only) enabled.

If you get around to compiling Audacity, you can try Nikolay's patch to see if that helps the Timer Record "not stopping" problem. I think 2.8.10 or 2.8.11 probably won't make any difference - it doesn't on Windows.

Gale

Hello Gale,
I was speaking about the time control panel freezing (not Audacity freezing): In the case I report above, Audacity _did not_ freeze, it just "forgot" to stop the recording at end time. Only the panel which displays elapsed and remaining time while recording did freeze.
That said, yes, I have to try Nikolay's patch. I just lack of time for doing it for the time being...

[phabaudac]

Well, maybe it has an error in the system of the timer recording so it doesn’t stop. Try to check the system of your timer recording like the setting. However you also try to search in online using the google search, maybe you can found some tips that related in your problem.

My <SPAM URL removed>

I recently bought a new PC (the previous one was 8 years old !) with a decent though low cost processor (Athlon II X2 250) : now Audacity works perfectly and I have no longer any trouble with timer recording (I am still using Ubuntu 10.04 + Audacity 1.3.12-beta + Terratec Aureon 5.1 PCI).
Pierre

Moderator Note: Pierre, user Dalton has been removed as a spammer, as he/she posted a link to a non-related commercial website - reviving an old thread to do so ...