Re: [Audacity-devel] Checklist clean up
A free multi-track audio editor and recorder
Brought to you by:
aosiniao
From: Gale A. <ga...@au...> - 2007-08-29 03:50:01
|
| From "David R. Sky" <dav...@sh...> | Tue, 28 Aug 2007 06:04:33 -0700 (PDT) | Subject: [Audacity-devel] Checklist clean up | David: If by "select all" you mean "select all in the current | track", I agree with this. | I wouldn't want to apply a single effect to _all_ the tracks unless | I'm at a _final_ stage of editing all the tracks, such as final | fade-out. Hi David This was David B's first idea of a "smart select all" and I have said why personally I don't like that. We need something so that if no audio is selected and you apply an effect, the entire audio on the screen has the effect applied to it, because that is what novices expect to happen, and that is what many more experienced users want to do instead of having to "select all" first every time they want to do something on the entire audio. David B agrees too, *if* we can process the entire audio without selecting it. If you only have the audio for one of the tracks selected, the effect will of course only be applied to that selection. If you have made a different error, and got no tracks selected, then under your idea of a smarter selection, you are going to get all the tracks selected anyway for the length of the selected time range, because there is no other decision you could sensibly make. If every time a user selects no audio, then all audio on screen is selected, this is I think much more understandable and predictable if you are not sure as a VI user what precise case of no audio selected caused the problem. We have as a priority aim-to to add a beep after lengthy processing has been completed - incidentally I would want a Preference to turn that off! Would you as a VI user find it useful to have that beep irrespective of length of process, as I'm thinking you might? Anyway, if we had a beep (maybe a different sound) that sounded when all audio on screen had been selected as a result of the user not selecting any, wouldn't that help? If you hear the beep, and you were not intending to select all (in the sense of CTRL + A), simply CTRL +Z. This might also be the solution if we can't implement David B's second idea which I rather like, of select-all-when-none processing all, but not selecting it. | There's also the "weirdness" that when I have created a long track | 1, then generate a short audio piece in track 2, when I select | track 2's audio by "home shift+end", there is a long period of | silence appended to the newly-generated audio, which takes a long | time to process with certain effects. | Is this feature deliberate, to make tracks equal length? If you press HOME with the short track selected, then END, you are moving the cursor to the end of the Project, in this case to the end of the long track. If you press SHIFT + END instead of END, you are extending the selection area from the cursor point at the start of the short track to the end of the Project, but providing you have only the short track selected (which would show by its Track Panel being shaded were you able to see it) any effect will apply only to the short track. No silence is generated in the short track, but if you press spacebar to play, the audio will play to the end of the Project because SHIFT + END has selected the entire time range. If you only want to select the audio to the end of the short track, but not extend the time range to the end of the Project, then with only the short track selected, you need Edit > Select > Cursor to End. There is no hotkey but the route on the keyboard is ALT E S S ENTER C. But if you do that with both tracks selected, the audio of both tracks will be selected, and any effect will be applied to both tracks. Gale Outbound message virus free. Tested on: 8/29/2007 4:50:01 AM |