Re: [Audacity-devel] timeshi2.ny Time Shifter 2
A free multi-track audio editor and recorder
Brought to you by:
aosiniao
From: David R. S. <dav...@sh...> - 2007-09-22 07:52:21
|
Thanks Gale. I heard only one error on the ;info line: commands.from. Other than that if you like it, I'm satisfied with it too. Corrected plug attached. Thanks for pointing out the release terms being on the second line under author - I hadn't known about or even really thought about it, I had just put it at the end of the ;info line automatically. It sounds "more professional" where you put it. :-) I like the 500ms default time shifting, it won't throw an error message if someone accidentally clicks 'enter' without entering a shift value. *shrug* As with so many discussions on the list, it could be argued in favor either way. I didn't realize latency correction was applied after recording - this makes sense of course. So we agree that negative time shift values move audio backwards when negative. Thanks! David -- David R. Sky http://www.shellworld.net/~davidsky/ On Sat, 22 Sep 2007, Gale Andrews wrote: > > | From "David R. Sky" <dav...@sh...> > | Fri, 21 Sep 2007 21:21:17 -0700 (PDT) > | Subject: [Audacity-devel] timeshi2.ny Time Shifter 2 > | To answer your question about working with white space in > | Nyquist - as you pointed out, Nyquist plug-ins do not currently > | recognize this as audio (silent or otherwise). > | So what I would do (if such a plug-in was desired - the equivalent of > | making a short audio selection then copying to a second track) would have > | the user set > | the start and end time or percentage values, then the plug-in would > | simply turn > | the audio outside the "selection" boundaries to zero volume. (A lot > | simpler than how I had originally thought about this). > > Hi David > > OK this is my last shot at it. I moved the release line to underneath your > authorship line as this is what most Nyquist plug-ins do. I changed the > first two sentences to save space and make them less repetitive. To save > changing the plug-in again when 1.4 comes out (we could not then > have a reference to pre 1.4 in it), I fudged the instructions on converting > white space to silence by referring to "Mix". I think it's clear enough. Also > made the default to 500 rather than a value that will give an error, but > change it to what you will. > > | Regarding using positive versus negative time shift values - I'm going to > | leave backward time shifting in as negative values. This is so much more > | intuitive for time shifting - moving already-existing audio backward in > | time. > | Latency correction is a somewhat different abstract model, which > | involves audio in the moment it's recorded. I'm going to leave that > | thread for others to discuss. > > I agree of course that a negative value is much more understood for > moving audio backwards. The latency correction where we are discussing > negative or positive values is done after recording. If it's still felt that > backwards shifting should be called a positive correction there (there is an > argument for that, though I am unconvinced) then I think it should be > clarified in the Preference itself. > > > Gale > |