Re: [Audacity-devel] timeshi2.ny Time Shifter 2

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

    | From "David R. Sky" <dav...@sh...> 
    | Fri, 21 Sep 2007 10:31:13 -0700 (PDT)
    | Subject: [Audacity-devel] timeshi2.ny Time Shifter 2
    | modified timeshi2.ny is attached, an error message is generated if you 
    | enter non-numeric value(s).

That's fine. Thanks.  

Re: the wording:

1) Instead of saying "a dash prefix", I'd just say "any prefix" .. it's a bit 
confusing to mention a dash and a minus in the same line. In any case if 
we do settle for backwards latency correction being called positive, then
we might have to reverse the meaning of this, so that they enter a "-" for 
forwards shifting. Your tool is not specifically for latency correction, but  
some users are going to be confused by a backwards shift on the screen 
being deemed positive in one place and negative in another. 

2) This is probably my fault but we have "If your selected audio" then (next
sentence) "If your audio selection". I suggest making those phrases identical.

So what are your views on the preceding white space problem? If you need
to run a separate plug-in to convert preceding white space to silence (rather
than do it in timeshifter), I don't think it's worth it. If that's the case I would
suggest adding these lines after the current second line:

If you have empty space preceding your audio clip, you can convert the space
to silence to prevent truncation. Simply select the track then choose Mix and 
Render from the Tracks Menu. 

Of course this is wrong for 1.2.6, which should be "Quick Mix from the 
Project Menu." Perhaps for the version we upload to source you want to say 
Mix and Render, and if uploading a version to 
http://audacity.sourceforge.net/download/nyquistplugins

you want to have Quick Mix? 


    | Markus, I'm cc'ing this to you specifically, since the check for 
    | non-numeric values triggers the above error message when I enter
    | 
    | 10,5
    | 
    | instead of the north american
    | 
    | 10.5.
    | 
    | Do you get the same error message, or does it work fine in German 
    | Audacity? (I use the numberp predicate function to check whether the 
    | value(s) are numeric.)
    | 
    | I suspect fractions of a millisecond will not be called for though, so 
    | this may be a mute point.

The point about Germans entering commas for decimal points would be 
of general applicability in built-in effects but where I looked (even if 
language is changed to German) Audacity disregards commas, so if you 
ask for 7,625 percent in Change Tempo, you will get 7 percent, but will 
get 7.625 percent exactly if requested.
 

Gale 



Outbound message virus free.
Tested on: 9/22/2007 1:15:44 AM