Timer Record Bug 42 Timer Record carries on recording past the scheduled end

classic Classic list List threaded Threaded
6 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Timer Record Bug 42 Timer Record carries on recording past the scheduled end

Peter Sampson-2
Vaughan copied on this as Timer Record is his baby.


For the first time in a very long time I experience this long-standing
moonphase bug last night:
http://bugzilla.audacityteam.org/show_bug.cgi?id=42#c29

This morning I woke to a a still running 8 hours of recording that was scheduled to 
stop after 2 hours at 2am. 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 lauched was a clean empty Audacity window with no offer of recovery. When I had set up the TR last night I had pre-saved the project (empty) and then set
TR to automatically save on completeion. I attempted to open the Audacity project - I got an warning message of thousands of
orphan filles - I elected to continue without deleting those. The project them opened
as an empty project. On examining the folder in which I had saved the project I foulnd the .aup file (short
and terse) and a folder full of folders and .au files (10.5 GB 10,602 files 42 folders).


A number of things vex me about this:
1) I was fully expecting auto-recovery to work and was very surprised when it was not offered.

2) We go to all the bother of saving all the .au files yet never bother to periodically (say every
5 or ten minutes) save the .aup file. I would have been quite happy with 7 hours and 50 minutes
of project (trimming off the last 5:50).
3) Yes we do have instructions in the Manual for manual recovery from .au files with no or 
corrupted .aup file and no editing performed - but surely we could automate this process to automate
this task for users.

If we can write prescriptive instuctions surely that should be programmable.
Remember this is far from being the only way to be in the situation of requiring such a recovery,
the Forum has plenty of postings to attest to that.
I have to admit to feeeling more than daunted at thethought of tacking this mandraullically.

Thanks,
Peter.

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Audacity-quality mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/audacity-quality
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Timer Record Bug 42 Timer Record carries on recording past the scheduled end

Gale
Administrator
See if there is a ,tmp file with the expected timestamp where the
AUTOSAVE file should have been
( Users\<username>\AppData\Roaming\Audacity\AutoSave ).

If so, quit Audacity, rename the .tmp file to .autosave then try
launching Audacity.

If you recover manually, you can ignore d* folders with files
timestamped after 02:00.


Gale




On 27 June 2017 at 10:47, Peter Sampson <[hidden email]> wrote:

> Vaughan copied on this as Timer Record is his baby.
>
>
> For the first time in a very long time I experience this long-standing
> moonphase bug last night:
> http://bugzilla.audacityteam.org/show_bug.cgi?id=42#c29
>
> This morning I woke to a a still running 8 hours of recording that was
> scheduled to
> stop after 2 hours at 2am.
>
> 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 lauched was a clean empty Audacity window with no offer of
> recovery.
>
> When I had set up the TR last night I had pre-saved the project (empty) and
> then set
> TR to automatically save on completeion.
>
> I attempted to open the Audacity project - I got an warning message of
> thousands of
> orphan filles - I elected to continue without deleting those.  The project
> them opened
> as an empty project.
>
> On examining the folder in which I had saved the project I foulnd the .aup
> file (short
> and terse) and a folder full of folders and .au files (10.5 GB 10,602 files
> 42 folders).
>
>
> A number of things vex me about this:
>
> 1) I was fully expecting auto-recovery to work and was very surprised when
> it was not offered.
>
> 2) We go to all the bother of saving all the .au files yet never bother to
> periodically (say every
> 5 or ten minutes) save the .aup file. I would have been quite happy with 7
> hours and 50 minutes
> of project (trimming off the last 5:50).
>
> 3) Yes we do have instructions in the Manual for manual recovery from .au
> files with no or
> corrupted .aup file and no editing performed - but surely we could automate
> this process to automate
> this task for users.
>
> If we can write prescriptive instuctions surely that should be programmable.
> Remember this is far from being the only way to be in the situation of
> requiring such a recovery,
> the Forum has plenty of postings to attest to that.
>
> I have to admit to feeeling more than daunted at thethought of tacking this
> mandraullically.
>
> Thanks,
> Peter.
>
>
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Audacity-quality mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/audacity-quality
>

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Audacity-quality mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/audacity-quality
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Timer Record Bug 42 Timer Record carries on recording past the scheduled end

Peter Sampson-2


On Tue, Jun 27, 2017 at 3:19 PM, Gale Andrews <[hidden email]> wrote:
See if there is a ,tmp file with the expected timestamp where the
AUTOSAVE file should have been
( Users\<username>\AppData\Roaming\Audacity\AutoSave ).

If so, quit Audacity, rename the .tmp file to .autosave then try
launching Audacity.

Too late I've opened and closed several Audacity projects since then.


If you recover manually, you can ignore d* folders with files
timestamped after 02:00.

Too much hard work - the DJ now pihes his own off-the-desk recording
to Mixcloud - I'm listening to that.

But thanks anyway for the suggestions Gale.

Peter

 


Gale




On 27 June 2017 at 10:47, Peter Sampson <[hidden email]> wrote:
> Vaughan copied on this as Timer Record is his baby.
>
>
> For the first time in a very long time I experience this long-standing
> moonphase bug last night:
> http://bugzilla.audacityteam.org/show_bug.cgi?id=42#c29
>
> This morning I woke to a a still running 8 hours of recording that was
> scheduled to
> stop after 2 hours at 2am.
>
> 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 lauched was a clean empty Audacity window with no offer of
> recovery.
>
> When I had set up the TR last night I had pre-saved the project (empty) and
> then set
> TR to automatically save on completeion.
>
> I attempted to open the Audacity project - I got an warning message of
> thousands of
> orphan filles - I elected to continue without deleting those.  The project
> them opened
> as an empty project.
>
> On examining the folder in which I had saved the project I foulnd the .aup
> file (short
> and terse) and a folder full of folders and .au files (10.5 GB 10,602 files
> 42 folders).
>
>
> A number of things vex me about this:
>
> 1) I was fully expecting auto-recovery to work and was very surprised when
> it was not offered.
>
> 2) We go to all the bother of saving all the .au files yet never bother to
> periodically (say every
> 5 or ten minutes) save the .aup file. I would have been quite happy with 7
> hours and 50 minutes
> of project (trimming off the last 5:50).
>
> 3) Yes we do have instructions in the Manual for manual recovery from .au
> files with no or
> corrupted .aup file and no editing performed - but surely we could automate
> this process to automate
> this task for users.
>
> If we can write prescriptive instuctions surely that should be programmable.
> Remember this is far from being the only way to be in the situation of
> requiring such a recovery,
> the Forum has plenty of postings to attest to that.
>
> I have to admit to feeeling more than daunted at thethought of tacking this
> mandraullically.
>
> Thanks,
> Peter.
>
>
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Audacity-quality mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/audacity-quality
>

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Audacity-quality mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/audacity-quality


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Audacity-quality mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/audacity-quality
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Timer Record Bug 42 Timer Record carries on recording past the scheduled end

Gale
Administrator
On 27 June 2017 at 15:26, Peter Sampson <[hidden email]> wrote:

>
>
> On Tue, Jun 27, 2017 at 3:19 PM, Gale Andrews <[hidden email]> wrote:
>>
>> See if there is a ,tmp file with the expected timestamp where the
>> AUTOSAVE file should have been
>> ( Users\<username>\AppData\Roaming\Audacity\AutoSave ).
>>
>> If so, quit Audacity, rename the .tmp file to .autosave then try
>> launching Audacity.
>
>
> Too late I've opened and closed several Audacity projects since then.

Why is it too late? If the AUTOSAVE file got left over as a .tmp file
that is exactly the reason Audacity ignores it. You can do the rename
any time if the file is there to be renamed.

It makes no difference what projects you opened in the meantime.


Gale


>> If you recover manually, you can ignore d* folders with files
>> timestamped after 02:00.
>
>
> Too much hard work - the DJ now pihes his own off-the-desk recording
> to Mixcloud - I'm listening to that.
>
> But thanks anyway for the suggestions Gale.
>
> Peter
>
>
>>
>>
>>
>> Gale
>>
>>
>>
>>
>> On 27 June 2017 at 10:47, Peter Sampson <[hidden email]>
>> wrote:
>> > Vaughan copied on this as Timer Record is his baby.
>> >
>> >
>> > For the first time in a very long time I experience this long-standing
>> > moonphase bug last night:
>> > http://bugzilla.audacityteam.org/show_bug.cgi?id=42#c29
>> >
>> > This morning I woke to a a still running 8 hours of recording that was
>> > scheduled to
>> > stop after 2 hours at 2am.
>> >
>> > 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 lauched was a clean empty Audacity window with no offer of
>> > recovery.
>> >
>> > When I had set up the TR last night I had pre-saved the project (empty)
>> > and
>> > then set
>> > TR to automatically save on completeion.
>> >
>> > I attempted to open the Audacity project - I got an warning message of
>> > thousands of
>> > orphan filles - I elected to continue without deleting those.  The
>> > project
>> > them opened
>> > as an empty project.
>> >
>> > On examining the folder in which I had saved the project I foulnd the
>> > .aup
>> > file (short
>> > and terse) and a folder full of folders and .au files (10.5 GB 10,602
>> > files
>> > 42 folders).
>> >
>> >
>> > A number of things vex me about this:
>> >
>> > 1) I was fully expecting auto-recovery to work and was very surprised
>> > when
>> > it was not offered.
>> >
>> > 2) We go to all the bother of saving all the .au files yet never bother
>> > to
>> > periodically (say every
>> > 5 or ten minutes) save the .aup file. I would have been quite happy with
>> > 7
>> > hours and 50 minutes
>> > of project (trimming off the last 5:50).
>> >
>> > 3) Yes we do have instructions in the Manual for manual recovery from
>> > .au
>> > files with no or
>> > corrupted .aup file and no editing performed - but surely we could
>> > automate
>> > this process to automate
>> > this task for users.
>> >
>> > If we can write prescriptive instuctions surely that should be
>> > programmable.
>> > Remember this is far from being the only way to be in the situation of
>> > requiring such a recovery,
>> > the Forum has plenty of postings to attest to that.
>> >
>> > I have to admit to feeeling more than daunted at thethought of tacking
>> > this
>> > mandraullically.
>> >
>> > Thanks,
>> > Peter.
>> >
>> >
>> >
>> > ------------------------------------------------------------------------------
>> > Check out the vibrant tech community on one of the world's most
>> > engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>> > _______________________________________________
>> > Audacity-quality mailing list
>> > [hidden email]
>> > https://lists.sourceforge.net/lists/listinfo/audacity-quality
>> >
>>
>>
>> ------------------------------------------------------------------------------
>> Check out the vibrant tech community on one of the world's most
>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>> _______________________________________________
>> Audacity-quality mailing list
>> [hidden email]
>> https://lists.sourceforge.net/lists/listinfo/audacity-quality
>
>
>
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Audacity-quality mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/audacity-quality
>

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Audacity-quality mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/audacity-quality
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Timer Record Bug 42 Timer Record carries on recording past the scheduled end

Peter Sampson-2


On Tue, Jun 27, 2017 at 4:29 PM, Gale Andrews <[hidden email]> wrote:
On 27 June 2017 at 15:26, Peter Sampson <[hidden email]> wrote:
>
>
> On Tue, Jun 27, 2017 at 3:19 PM, Gale Andrews <[hidden email]> wrote:
>>
>> See if there is a ,tmp file with the expected timestamp where the
>> AUTOSAVE file should have been
>> ( Users\<username>\AppData\Roaming\Audacity\AutoSave ).
>>
>> If so, quit Audacity, rename the .tmp file to .autosave then try
>> launching Audacity.
>
>
> Too late I've opened and closed several Audacity projects since then.

Why is it too late? If the AUTOSAVE file got left over as a .tmp file
that is exactly the reason Audacity ignores it. You can do the rename
any time if the file is there to be renamed.

It makes no difference what projects you opened in the meantime.

In which case there wasn't on there - except for my later project late this morning.

Peter.
 


Gale


>> If you recover manually, you can ignore d* folders with files
>> timestamped after 02:00.
>
>
> Too much hard work - the DJ now pihes his own off-the-desk recording
> to Mixcloud - I'm listening to that.
>
> But thanks anyway for the suggestions Gale.
>
> Peter
>
>
>>
>>
>>
>> Gale
>>
>>
>>
>>
>> On 27 June 2017 at 10:47, Peter Sampson <[hidden email]>
>> wrote:
>> > Vaughan copied on this as Timer Record is his baby.
>> >
>> >
>> > For the first time in a very long time I experience this long-standing
>> > moonphase bug last night:
>> > http://bugzilla.audacityteam.org/show_bug.cgi?id=42#c29
>> >
>> > This morning I woke to a a still running 8 hours of recording that was
>> > scheduled to
>> > stop after 2 hours at 2am.
>> >
>> > 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 lauched was a clean empty Audacity window with no offer of
>> > recovery.
>> >
>> > When I had set up the TR last night I had pre-saved the project (empty)
>> > and
>> > then set
>> > TR to automatically save on completeion.
>> >
>> > I attempted to open the Audacity project - I got an warning message of
>> > thousands of
>> > orphan filles - I elected to continue without deleting those.  The
>> > project
>> > them opened
>> > as an empty project.
>> >
>> > On examining the folder in which I had saved the project I foulnd the
>> > .aup
>> > file (short
>> > and terse) and a folder full of folders and .au files (10.5 GB 10,602
>> > files
>> > 42 folders).
>> >
>> >
>> > A number of things vex me about this:
>> >
>> > 1) I was fully expecting auto-recovery to work and was very surprised
>> > when
>> > it was not offered.
>> >
>> > 2) We go to all the bother of saving all the .au files yet never bother
>> > to
>> > periodically (say every
>> > 5 or ten minutes) save the .aup file. I would have been quite happy with
>> > 7
>> > hours and 50 minutes
>> > of project (trimming off the last 5:50).
>> >
>> > 3) Yes we do have instructions in the Manual for manual recovery from
>> > .au
>> > files with no or
>> > corrupted .aup file and no editing performed - but surely we could
>> > automate
>> > this process to automate
>> > this task for users.
>> >
>> > If we can write prescriptive instuctions surely that should be
>> > programmable.
>> > Remember this is far from being the only way to be in the situation of
>> > requiring such a recovery,
>> > the Forum has plenty of postings to attest to that.
>> >
>> > I have to admit to feeeling more than daunted at thethought of tacking
>> > this
>> > mandraullically.
>> >
>> > Thanks,
>> > Peter.
>> >
>> >
>> >
>> > ------------------------------------------------------------------------------
>> > Check out the vibrant tech community on one of the world's most
>> > engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>> > _______________________________________________
>> > Audacity-quality mailing list
>> > [hidden email]
>> > https://lists.sourceforge.net/lists/listinfo/audacity-quality
>> >
>>
>>
>> ------------------------------------------------------------------------------
>> Check out the vibrant tech community on one of the world's most
>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>> _______________________________________________
>> Audacity-quality mailing list
>> [hidden email]
>> https://lists.sourceforge.net/lists/listinfo/audacity-quality
>
>
>
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Audacity-quality mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/audacity-quality
>

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Audacity-quality mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/audacity-quality


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Audacity-quality mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/audacity-quality
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Timer Record Bug 42 Timer Record carries on recording past the scheduled end

Peter Sampson-2
In reply to this post by Peter Sampson-2


On Mon, Jul 10, 2017 at 11:17 AM, Vaughan Johnson <[hidden email]> wrote:


On Tue, Jun 27, 2017 at 2:47 AM, Peter Sampson <[hidden email]> wrote:
Vaughan copied on this as Timer Record is his baby.

Haven't looked at that code in years, and won't have time in the near term. I think from discussions I've seen that it's been changed extensively.

I'm no expert, but I think it's mainlyt the outer wrapper layers that have changed
with the facility to autmatically save projects, export audio and (on Windows) close
the app or the PC down. I suspect the core timer management code is probably as
you wrote it Vaughan.

BTW it worked perfectly for me last Monday night with
1) an automatic save of the project tomy hard drive,
2) an automatic WAV export to a USB thumb brive (which I could grab early in the
morning just before driving down to Wimbledon)
3) closing down the PC (so it didn't overheat while I was at Wimbledon).


This bug is *very*moonphase ( I, personally haven't expereienced it in donkey's years)
and it did occur long before Mark added his automatic export/save/close - so I don't
believe it is anything that was introduced at that stage.

 

I read -quality.

That's good to hear :-))

Cheers,
Peter.
 

- V
 


For the first time in a very long time I experience this long-standing
moonphase bug last night:
http://bugzilla.audacityteam.org/show_bug.cgi?id=42#c29

This morning I woke to a a still running 8 hours of recording that was scheduled to 
stop after 2 hours at 2am. 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 lauched was a clean empty Audacity window with no offer of recovery. When I had set up the TR last night I had pre-saved the project (empty) and then set
TR to automatically save on completeion. I attempted to open the Audacity project - I got an warning message of thousands of
orphan filles - I elected to continue without deleting those. The project them opened
as an empty project. On examining the folder in which I had saved the project I foulnd the .aup file (short
and terse) and a folder full of folders and .au files (10.5 GB 10,602 files 42 folders).


A number of things vex me about this:
1) I was fully expecting auto-recovery to work and was very surprised when it was not offered.

2) We go to all the bother of saving all the .au files yet never bother to periodically (say every
5 or ten minutes) save the .aup file. I would have been quite happy with 7 hours and 50 minutes
of project (trimming off the last 5:50).
3) Yes we do have instructions in the Manual for manual recovery from .au files with no or 
corrupted .aup file and no editing performed - but surely we could automate this process to automate
this task for users.

If we can write prescriptive instuctions surely that should be programmable.
Remember this is far from being the only way to be in the situation of requiring such a recovery,
the Forum has plenty of postings to attest to that.
I have to admit to feeeling more than daunted at thethought of tacking this mandraullically.

Thanks,
Peter.


Virus-free. www.avast.com


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Audacity-quality mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/audacity-quality
Loading...