Re: [Audacity-devel] Timer Record changes

[Gale A. <ga...@au...>]

    | From Vaughan Johnson <va...@au...> 
    | Wed, 30 May 2007 05:27:56 -0700
    | Subject: [Audacity-devel] Timer Record changes
    | Committed some changes to Timer Record:
    | Actually, for performance, I had set the timer interval to 1 second. Was 
    | also checking < rather than <=. Changed it to check <=, and made the 
    | interval 1/2 second, so now it's usually some fraction of a half-second 
    | too long, rather than usually some fraction of a second too short. 
    | Actually, in debug mode with a heavily loaded machine, it can be a bit 
    | longer than a half-second too long, but it should never be short now.
    | There's always going to be some error, but I could make the timer 
    | interval much smaller, if you think it's necessary. Since you can 
    | specify the duration only to the second, I think a 1/2 second is close 
    | enough for most applications, but let me know.
  
Another person replying to this thread I think suggested Audacity should try to 
detect start of recording and then start timing. I am not sure about the 
mechanics of that, but as it is now, the Timer Record (though still very accurate) 
is much less accurate about the length of time it's asked to record for than the
operation where you ask it to record 10 seconds exactly by selecting that length 
of track with "play other tracks while recording" enabled. 

For example, could it actually launch recording say 0.5 seconds before the time 
it's asked to start, which should mean it starts (and ends) recording pretty close
to the dot anyway, but then simply try and record for that set length as accurately 
as possible, and not care about the actual time on the clock it was supposed to 
stop?


    | + Bug 267: "...when setting up a timer recording for the next day, only 
    | about 2.5 seconds are recorded instead of the full length set."
    | 
    | Can't replicate. Maybe I don't get the description. I set the system 
    | time to a few minutes before midnight, set Timer Record to record for 5 
    | minutes, starting at 00:01, and it recorded the full 5 minutes.

I wonder if the issue is not the actual time of day/night but the length of 
time the process is waiting to record before it starts?  


    | PS: Regarding the idea of auto-saving after Timer Record finishes, isn't 
    | it enough that Audacity has auto-save now?

Yes I suppose so in terms of safety, but it would be much nicer if user came 
home late/tired in the late evening in the knowledge that a Project had been 
saved to the name chosen, rather than with the thought that perhaps they 
"should" drag themselves to the computer to save the Project. 


Gale 



Outbound message virus free.
Tested on: 5/30/2007 7:37:59 AM