Thread: [Audacity-devel] Re Checklist clean up
A free multi-track audio editor and recorder
Brought to you by:
aosiniao
From: Gale A. <ga...@au...> - 2007-08-31 08:24:33
|
Hi James I saw your notes on the Checklist about greying out of effects. I was assuming that we were just ignoring the case of no audio tracks on screen as it is not really a great confusion. Personally I still don't think this warrants breaking our rule of greyed out menu items if the choice won't work even if all audio is selected. This creates its own confusions to say nothing of dialogues you have to OK and cannot disable if you want to select all when none. Another idea I've had which might help is that when you launch Audacity you get a dialogue box with "don't show me this again" checkbox. This may be useful on its own terms, but it can address the two outstanding issues (1) something like "to begin, you need an audio track on screen to work with.... to import audio (blah, blah). To start a recording set your device and input source (blah, blah) and press Record. This will actually help those who don't know where to start, don't want to look at the documentation then write in asking what they are supposed to do to record. (2) "Whenever you want to edit your recording or add effects to it, press the yellow Stop button if you are already playing or recording". We could even tell them straight out, if a menu item is greyed it means you have to select some audio first. Now is my logic wrong here in thinking if we went along with that, we only need a "select all on none" preference which is easy to understand and explain, and don't need a "greying out" preference option at all, because not enabling "select all on none" will turn it on? At the moment the Edit menu is a mix of some active greying with warnings and some greyed with no explanation - in particular you cannot copy audio unless you select it which is a definite newbie issue. I'd definitely suggest Edit > Copy, Cut and Delete joins Effects etc. as being available to click on when "Select all on none" is enabled. I'd vastly prefer menu choices that are invalid because selecting all won't make them work simply remain greyed out. Gale Outbound message virus free. Tested on: 8/31/2007 9:24:34 AM |
From: David B. <drb...@go...> - 2007-08-31 10:19:17
|
On 8/31/07, Gale Andrews <ga...@au...> wrote: > > I'd definitely suggest Edit > Copy, Cut > and Delete joins Effects etc. as being available to click on when "Select all > on none" is enabled. I'd vastly prefer menu choices that are invalid because > selecting all won't make them work simply remain greyed out. How often does a user want to copy of cut all the audio? Having to select something before copying, cutting etc. is the way all programs work (Are there any exceptions?). I'm not sure it's wise to deviate from this standard model. David. |
From: James C. <cr...@in...> - 2007-08-31 12:27:08
|
David Bailes wrote: > On 8/31/07, Gale Andrews <ga...@au...> wrote: >> I'd definitely suggest Edit > Copy, Cut >> and Delete joins Effects etc. as being available to click on when "Select all >> on none" is enabled. I'd vastly prefer menu choices that are invalid because >> selecting all won't make them work simply remain greyed out. > How often does a user want to copy of cut all the audio? Having to > select something before copying, cutting etc. is the way all programs > work (Are there any exceptions?). > I'm not sure it's wise to deviate from this standard model. > David. New users working with a single track might want exactly that behaviour. Those who don't want the select-all-on-none behaviour, myself included, would disable it. --James |
From: Gale A. <ga...@au...> - 2007-09-01 01:14:45
|
| David Bailes wrote: | > On 8/31/07, Gale Andrews <ga...@au...> wrote: | >> I'd definitely suggest Edit > Copy, Cut | >> and Delete joins Effects etc. as being available to click on when | >> "Select all | >> on none" is enabled. | > How often does a user want to copy of cut all the audio? Having to | > select something before copying, cutting etc. is the way all programs | > work (Are there any exceptions?). | > I'm not sure it's wise to deviate from this standard model. I don't have hard and fast evidence but I strongly suspect in entry level to medium difficulty editors the "standard model" is that when you open at least a single file, then by default the whole audio is selected (it may or may not be shaded so as to imply a selection area). I tried Goldwave and Wavepad and in both you can, immediately the file has loaded, simply cut or copy the whole track, or run an effect on the whole track. In Goldwave, if you import a second file, then all of both files are selected unless you make a selection area manually. If you import a second file into Wavepad, it selects all of that file and deselects the first one. In either program you can at least run further effects in the case where the program has selected what it believes is the most likely thing you want to do; in Audacity, you can do nothing further without selecting audio. Something else you cannot do easily in Audacity at the moment is run an effect on the whole track, pick spots out to hear what they are like, then run another effect on the whole track; once again you have to select all first. This soon gets to be a pain. Quite a few times it has been pointed out to us in no uncertain terms where the users are *not* novices that our behaviour is not what "other" editors do. David, it was your idea that when we select-all-on-none, the audio should be unselected after processing. As we are now proposing a Preference for select-all-on-none, I don't think we necessarily need to do that. One possible objection to unselecting after processing select all, might be that if the cursor was not at the start of the track when you ran the effect, then you can't hear the processed audio from the start without taking some further action. If anyone has views one way or the other, can they speak up? If we can do this right (hence the long discussions about it) I am pretty hopeful we can get keep everyone (more or less) happy. Gale Outbound message virus free. Tested on: 9/1/2007 2:14:38 AM |
From: David B. <drb...@go...> - 2007-09-01 10:37:41
|
Hi Gale, On 9/1/07, Gale Andrews <ga...@au...> wrote: > I don't have hard and fast evidence but I strongly suspect in entry level to > medium difficulty editors the "standard model" is that when you open at > least a single file, then by default the whole audio is selected (it may or > may not be shaded so as to imply a selection area). I tried Goldwave and > Wavepad and in both you can, immediately the file has loaded, simply cut > or copy the whole track, or run an effect on the whole track. I've just had a quick look at the Adobe Audition manual, and I think that what happens there is that if you cut or copy it uses either the selection, or in the absence of a selection all the audio. So my "standard model" was wrong, at least for audio editors. > David, it was your idea that when we select-all-on-none, the audio should > be unselected after processing. As we are now proposing a Preference for > select-all-on-none, I don't think we necessarily need to do that. One possible > objection to unselecting after processing select all, might be that if the cursor > was not at the start of the track when you ran the effect, then you can't hear > the processed audio from the start without taking some further action. If > anyone has views one way or the other, can they speak up? I still like adobe's model: when you apply an effect, cut, or copy if uses either the selection or all, but does not change the state of the selection. I think I trust adobe to make things useable (misplaced?). If the cursor is not at the start when you run an effect, you might well want to hear audio after the effect at the place you were listening to before applying the effect. David. |
From: James C. <cr...@in...> - 2007-08-31 12:23:26
|
Gale Andrews wrote: > Hi James > I saw your notes on the Checklist about greying out of effects. I was assuming > that we were just ignoring the case of no audio tracks on screen as it is not > really a great confusion. Personally I still don't think this warrants breaking our > rule of greyed out menu items if the choice won't work even if all audio is > selected. This creates its own confusions to say nothing of dialogues you have > to OK and cannot disable if you want to select all when none. So you're suggesting no warning dialogs where preveiously we had greyed-out, not ever. Instead a single preference: 'select-all-if-none' If selecting-all-if-none won't allow the effect, the effect stays greyed out. If you're playing the audio or recording, the effect stays greyed out. So there is no explanation for these greyed out cases. The user just has to figure out why. Select-all-if-none selects all audio in all tracks. That seems fine. If it helps newbies, great. I'd still have it switched off. > Another idea I've had which might help is that when you launch Audacity you > get a dialogue box with "don't show me this again" checkbox..... We > could even tell them straight out, if a menu > item is greyed it means you have to select some audio first. This sounds like a good idea to me. There must be an easy way to re-enable that splash-screen, for the case of an instructor showing the program to newbies, so we need to have the 'show-splash-screen' in the preferences too. [Implementation details: We have choice as to whether to use an internal wxHTML browser or launch an external browser. We have choice as to whether to store the text as a _("string") within Audacity, as a compressed file within Audacity or outside Audacity - where it might not be available My choices would be internal wxHTML, internal _("string") within Audacity, both choices made for ease of implementation. ] I think the text of this message and the text of the unrecognised-audio-format message should both be in the help documentation too. Gale - please write the exact text you propose for the splash screen dialog. > Now is my logic wrong here in thinking if we went along with that, we only > need a "select all on none" preference which is easy to understand and > explain, and don't need a "greying out" preference option at all... I don't know how puzzling the various greying outs are to users. To me it never is puzzling. I am sure there will be cases where the greying out is puzzling to some user - for example if/when there are effects which can work only on stereo or only on mono. What matters is that we deal with the great tide of new users who are baffled when they first see greyed out menu items. > I'd definitely suggest Edit > Copy, Cut > and Delete joins Effects etc. as being available to click on when "Select all > on none" is enabled. I'd vastly prefer menu choices that are invalid because > selecting all won't make them work simply remain greyed out. Control-c with nothing selected will then cut everything! Under most UNIX based operating systems control-c is used to terminate a process in a command shell by sending it a SIGINT. Without the select-all-on-none behaviour no 'harm' would be done by control-c. Take home message - no defaults will satisfy everyone or meet everyone's expectations. I'd say it's better to be logical and do the select-all-on-none behaviour in all cases, not just effects, as you suggest. Summary: - Add a splash screen help message. - Add a preference select-all-on-none - None of these explanatory dialogs 'select some audio' at all. That works for me, so unless there are howls from the gallery that is what we'll do. Will update the Checklist after waiting a little while for a responses. --James. |
From: Gale A. <ga...@au...> - 2007-09-04 07:23:32
|
| From James Crook <cr...@in...>=20 | Fri, 31 Aug 2007 13:25:19 +0100 | Subject: [Audacity-devel] Re Checklist clean up | Summary: | - Add a splash screen help message. | - Add a preference select-all-on-none | - None of these explanatory dialogs 'select some audio' at all. |=20 | That works for me, so unless there are howls from the gallery that is= =20 | what we'll do. Will update the Checklist after waiting a little whil= e=20 | for a responses. Having heard no dissent, have updated Checklist now.=20 Here is my stab at the content of a "splash-screen" except that if it doesn= 't=20 scroll, it looks as if there is too much there at present. Comments/questions about it: * The single square bracket stuff [] is OS-specific. If we are going to=20 go into detail about setting up recording I think we must have slightly= =20 different screens for Mac and Windows.=20 * [[ ]] are Wiki links. [[Troubleshooting]] will aim to pull together the= =20 problem identifying / solving content of the [[Recording Tips]] section= =20 of the Wiki is which is quite good but unco-ordinated and a certain=20 amount duplicated. Richard has also suggested a "Troubleshooting"=20 page on the main site (not just for recording problems). Views? * Is the Recording section of the splashscreen too long/detailed? I have=20 ignored monitoring as this needs a mention of playthrough which will further add to the length. Perhaps there should be a mention of software playthrough for the USB turntable users? Should the suggested content=20 just be put somewhere else and only linked to in the splash screen? * Does the content need something appended to it on the difference=20 between exporting a file and saving a Project (another common novice=20 issue)?=20 * Any thoughts if we need tooltip or Status Bar additions for the Record or= =20 Stop buttons to ram home the splashscreen message? =20 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D Welcome to Audacity 1.4.0! Let's get started! =20 To begin, the best way is to either import an audio file into Audacity,=20 or make a recording. =20 You can import files into Audacity by dragging them in, or use the File >= =20 Import > Audio command. File > Open does the same, but opens a new=20 Audacity window. These are the main formats Audacity will import for=20 you: AIFF, AU, FLAC, [M4A (only on a Mac)], MP2/MP3, OGG Vorbis, WAV. If your file is in some other format see (format help). If you want to impo= rt an audio CD, see [[how to import CDs]]. To start playing your imported audio, press the green Play button. To start recording, press the red Record button. Of course it's not quite= =20 that easy. There are three crucial settings you need to make: (1) The "Recording Device", set in the Audio I/O tab of Preferences. By default Audacity will choose the current system device, usually your=20 inbuilt sound device, so you may not need to set this. But if you're using = an=20 external USB or Firewire device such as a USB turntable, please check this= =20 device is selected as your recording device. =20 (2) The input source for your device, such as microphone, line-in [or stereo mix]. [If you're on Vista, choose your source in the "Recording=20 Device" on the Audio I/O tab as above.] [Mac info]. Otherwise, choose=20 your input in the dropdown selector on the right of the Mixer Toolbar. Note: many USB or Firewire devices won't have a choice of inputs, so=20 you can ignore this step =96 see the documentation for your device.=20 (3) Input Volume: Before recording for real, make a test recording to set the input level of your recording so that it's neither too soft or too loud.= =20 To do this, adjust the input volume slider on the Mixer Toolbar (by the=20 microphone symbol) so that when you record, the levels on the red VU=20 recording meter in the Meter Toolbar are close to (but not touching) the right edge of the scale.=20 There is more help if you're stuck: our Recording FAQs, our Tutorial "Your= =20 First Recording" in the Manual, and our Wiki [[Recording Tips]] especially the [[Troubleshooting]] section.=20 Editing: Audacity is a powerful editor, so you'll want to see what it can d= o with your imported file or recording. The main commands you will use are under the Edit menu (such as cut, copy and paste) and under the Effect menu (you= =20 can do things like boost the bass, change pitch or tempo, or remove noise). There are two rules when editing: (1) if you're still playing or recording,= use=20 the yellow Stop button, because you can't edit a moving track! (2) You'll s= ee that on occasion some of the menus or buttons are greyed out or say=20 "Disabled", according to what you are trying to do. This is normal. For exa= mple because you can't edit the audio while playing or recording, we grey out or= =20 disable commands until you press Stop. Commands can sometimes be greyed out or disabled for other reasons =96 for example you can't run effects un= til you have audio on the screen, and you obviously cannot paste audio unti= l you've cut or copied it to Audacity's clipboard. =20 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D Gale=20 Outbound message virus free. Tested on: 9/4/2007 8:23:32 AM |
From: David R. S. <dav...@sh...> - 2007-09-04 07:43:08
|
On Tue, 4 Sep 2007, Gale Andrews wrote: >To start playing your imported audio, > press the green Play button. > > To start recording, press the red Record button. Hi Gale, terrific instructions. Could you also include keyboard commands "... press the space bar or green button." "... press the space bar again or the red button." and r for record, space bar to stop recording. Assuming these keyboard shortcuts will stay in place for 1.4.0. Thanks David |
From: Gale A. <ga...@au...> - 2007-09-05 00:44:13
|
| From "David R. Sky" <dav...@sh...> | Tue, 4 Sep 2007 00:43:08 -0700 (PDT) | Subject: [Audacity-devel] Re Checklist clean up | On Tue, 4 Sep 2007, Gale Andrews wrote: | | >To start playing your imported audio, | > press the green Play button. | > | > To start recording, press the red Record button. | | Could you also include keyboard commands | | "... press the space bar or green button." | | "... press the space bar again or the red button." | | and r for record, space bar to stop recording. Assuming these keyboard | shortcuts will stay in place for 1.4.0. Hi David I think it depends what format the splash screen itself turns out to be in, and how tight the space requirements are for that. In principle it should be fine to mention something about keyboard shortcuts in the copy of the splash screen text that goes in the documentation, and point there to the page of the Manual that covers the keyboard bindings: http://www.audacityteam.org/manual/index.php?title=Keyboard_Shortcut_Reference If space is at a premium in the splash screen it might be better just to point to that link rather than mention one or two shortcuts without mentioning there are others. Also I was not sure about muddying the waters with keyboard shortcuts. Sighted novices are unlikely to be very interested in these and will typically be looking for buttons and graphics in the first instance. Gale Outbound message virus free. Tested on: 9/5/2007 1:44:11 AM |
From: David R. S. <dav...@sh...> - 2007-09-06 04:30:01
|
Hi Gale, Agreed - for someone who wants to use keyboard commands to do something, it does make more sense to point to a list of all of such commands. David On Wed, 5 Sep 2007, Gale Andrews wrote: > If space is at a premium in the splash screen it might be better just to point > to that link rather than mention one or two shortcuts without mentioning there > are others. Also I was not sure about muddying the waters with keyboard > shortcuts. Sighted novices are unlikely to be very interested in these and will > typically be looking for buttons and graphics in the first instance. > > > > Gale > > > Outbound message virus free. > Tested on: 9/5/2007 1:44:11 AM > > > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. > Still grepping through log files to find problems? Stop. > Now Search log events and configuration files using AJAX and a browser. > Download your FREE copy of Splunk now >> http://get.splunk.com/ > _______________________________________________ > Audacity-devel mailing list > Aud...@li... > https://lists.sourceforge.net/lists/listinfo/audacity-devel > |
From: James C. <cr...@in...> - 2007-09-09 18:08:46
|
Gale, Re: Splash screen text, Excellent on the information, but way way too long for a splash screen. Who will read it all? Since your message I have been thinking about a solution. Here's my suggestion. The splash screen is html and says something like: ================================================================== Welcome to Audacity 1.4.0! Let's get started! You may want to click on the hyperlinks below to read: * How to _play_back_ an existing sound file. * How to _record_ a new sound file. * How to _edit_ sound and _export_ for an mp3 player. This could save you from puzzling over why some functions in the _menus_are_greyed_out_ or why Audacity _isn't_recording_anything_ when you expect it to. Or you may prefer to just try using Audacity and see what you can do. You can always get back to these instructions by using the 'help' option in the menus, and then clicking on 'Start-Up-Message' Welcome to Audacity. ================================================================== [X] <- Tick to show this message at start up ================================================================== We now move your new text into those links. It's possible to have a small number of web pages built in to the program, so that Audacity will always find them, even if the main html help files are not where expected. That's what we'll do. Those linked pages should be of this kind. Only restriction is that I do not want images in those pages, as that is going to rapidly start increasing the minimum size of Audacity. By all means suggest changes to the wording, but do see if you can prevent the start up message getting longer. If you add any text, take out something else that is less important! If it is too long, people won't read it, and it defeats the purpose of giving a warning. Points raised.... The OS specific parts in [], the 'gold standard' would be to have different versions of the help files for the three platforms, plus an online version for the website that caters for all! That - in my view - is more work than we have resources for. We should have 'For-Mac' and 'For-PC' pages only where the differences are substantial. I think the text linked via wikilinks is useful, but not vital enough to merit being on the front page (splash screen). We can link to those wiki pages from the html help pages that are found from the splash screen. Particularly helpful for the troubleshooting page which may be updated post release. With recording on a separate page, we can now make that section longer, and add information about monitoring. The link on 'exporting' may help novice confusion over exporting/saving. I'm not keen to change the tooltips on record/stop. One reason is that 'play' already has text to tell you about shift for loop-play. Record should/could in future have text about shift for 'smart-record'. Gale, thank you very much for the wording(s). It is much easier to work forward from specific suggestions of how to solve a problem. --James. Gale Andrews wrote: > | From James Crook <cr...@in...> > | Fri, 31 Aug 2007 13:25:19 +0100 > | Subject: [Audacity-devel] Re Checklist clean up > | Summary: > | - Add a splash screen help message. > | - Add a preference select-all-on-none > | - None of these explanatory dialogs 'select some audio' at all. > | > | That works for me, so unless there are howls from the gallery that is > | what we'll do. Will update the Checklist after waiting a little while > | for a responses. > > Having heard no dissent, have updated Checklist now. > > Here is my stab at the content of a "splash-screen" except that if it doesn't > scroll, it looks as if there is too much there at present. > > Comments/questions about it: > > * The single square bracket stuff [] is OS-specific. If we are going to > go into detail about setting up recording I think we must have slightly > different screens for Mac and Windows. > > * [[ ]] are Wiki links. [[Troubleshooting]] will aim to pull together the > problem identifying / solving content of the [[Recording Tips]] section > of the Wiki is which is quite good but unco-ordinated and a certain > amount duplicated. Richard has also suggested a "Troubleshooting" > page on the main site (not just for recording problems). Views? > > * Is the Recording section of the splashscreen too long/detailed? I have > ignored monitoring as this needs a mention of playthrough which will > further add to the length. Perhaps there should be a mention of software > playthrough for the USB turntable users? Should the suggested content > just be put somewhere else and only linked to in the splash screen? > > * Does the content need something appended to it on the difference > between exporting a file and saving a Project (another common novice > issue)? > > * Any thoughts if we need tooltip or Status Bar additions for the Record or > Stop buttons to ram home the splashscreen message? > > > ========================= > > Welcome to Audacity 1.4.0! Let's get started! > > To begin, the best way is to either import an audio file into Audacity, > or make a recording. > > You can import files into Audacity by dragging them in, or use the File > > Import > Audio command. File > Open does the same, but opens a new > Audacity window. These are the main formats Audacity will import for > you: AIFF, AU, FLAC, [M4A (only on a Mac)], MP2/MP3, OGG Vorbis, WAV. > If your file is in some other format see (format help). If you want to import an > audio CD, see [[how to import CDs]]. To start playing your imported audio, > press the green Play button. > > To start recording, press the red Record button. Of course it's not quite > that easy. There are three crucial settings you need to make: > > (1) The "Recording Device", set in the Audio I/O tab of Preferences. > By default Audacity will choose the current system device, usually your > inbuilt sound device, so you may not need to set this. But if you're using an > external USB or Firewire device such as a USB turntable, please check this > device is selected as your recording device. > > (2) The input source for your device, such as microphone, line-in [or > stereo mix]. [If you're on Vista, choose your source in the "Recording > Device" on the Audio I/O tab as above.] [Mac info]. Otherwise, choose > your input in the dropdown selector on the right of the Mixer Toolbar. > Note: many USB or Firewire devices won't have a choice of inputs, so > you can ignore this step – see the documentation for your device. > > (3) Input Volume: Before recording for real, make a test recording to set > the input level of your recording so that it's neither too soft or too loud. > To do this, adjust the input volume slider on the Mixer Toolbar (by the > microphone symbol) so that when you record, the levels on the red VU > recording meter in the Meter Toolbar are close to (but not touching) > the right edge of the scale. > > There is more help if you're stuck: our Recording FAQs, our Tutorial "Your > First Recording" in the Manual, and our Wiki [[Recording Tips]] especially > the [[Troubleshooting]] section. > > Editing: Audacity is a powerful editor, so you'll want to see what it can do with > your imported file or recording. The main commands you will use are under > the Edit menu (such as cut, copy and paste) and under the Effect menu (you > can do things like boost the bass, change pitch or tempo, or remove noise). > There are two rules when editing: (1) if you're still playing or recording, use > the yellow Stop button, because you can't edit a moving track! (2) You'll see > that on occasion some of the menus or buttons are greyed out or say > "Disabled", according to what you are trying to do. This is normal. For example > because you can't edit the audio while playing or recording, we grey out or > disable commands until you press Stop. Commands can sometimes be greyed > out or disabled for other reasons – for example you can't run effects until you have audio on the screen, and you obviously cannot paste audio until you've > cut or copied it to Audacity's clipboard. > > > ======================== > Gale |
From: Gale A. <ga...@au...> - 2007-10-04 07:08:40
|
Hi Martyn I did check your envelope fixes as best I could and bar one oddity I could not find any problems. Restoration of envelope points was fine too after re-opening a Project (and that is now a Mac-specific essential to check). The oddity I had was as soon as I started to check, I had a problem with Edit > Split. I had a 4 second set of DTMF tones, made some envelope points then split at the cursor at one second which was very close to an envelope point. The audio from zero to 1 second then went to maximum amplification (Edit > Amplify showed no amplification was possible). The envelope points at 1 second were gone. I removed the track and recreated it with no envelope points and split created no problem. I then recreated the track with the same envelope points and the same maximisation occurred. I restarted Audacity and repeated the experiment with the same track and envelope points and could not then replicate it. Is there any possible reason for yet another inconsistency? I've left the envelope issue with splits as [Done] but added it to "Watching Brief" as well. Gale Outbound message virus free. Tested on: 10/4/2007 8:08:36 AM |
From: Martyn S. <mar...@go...> - 2007-10-09 23:34:55
|
Gale Thanks for checking. I take it most of the problems are confirmed as fixed. In order to repeat this problem I had to zoom in far enough to see individual samples. I could reproduce it if I put in an envelope point and then a split within 1.5 samples to the right (about 34microseconds). It's probably a rounding error. I don't think it has any meaningful significance in the real world and so I'm not even going to add it to my 'to do' list. I'll let the next person have a go, unless there is a 'real world' scenario where this would be a problem. Martyn Gale Andrews wrote: > > Hi Martyn > > I did check your envelope fixes as best I could and bar one oddity I could not > find any problems. Restoration of envelope points was fine too after re-opening > a Project (and that is now a Mac-specific essential to check). The oddity I had > was as soon as I started to check, I had a problem with Edit > Split. I had a > 4 second set of DTMF tones, made some envelope points then split at the > cursor at one second which was very close to an envelope point. The audio > from zero to 1 second then went to maximum amplification (Edit > Amplify > showed no amplification was possible). The envelope points at 1 second were > gone. I removed the track and recreated it with no envelope points and > split created no problem. I then recreated the track with the same envelope > points and the same maximisation occurred. I restarted Audacity and repeated > the experiment with the same track and envelope points and could not > then replicate it. > > Is there any possible reason for yet another inconsistency? I've left the > envelope issue with splits as [Done] but added it to "Watching Brief" as well. > > > Gale > > > > Outbound message virus free. > Tested on: 10/4/2007 8:08:36 AM > > > > |
From: Gale A. <ga...@au...> - 2007-10-11 01:03:44
|
| From Martyn Shaw <mar...@go...> | Wed, 10 Oct 2007 00:35:58 +0100 | Subject: [Audacity-devel] Checklist clean up | In order to repeat this problem I had to zoom in far enough to see | individual samples. I could reproduce it if I put in an envelope point | and then a split within 1.5 samples to the right (about 34microseconds). | It's probably a rounding error. I don't think it has any meaningful | significance in the real world and so I'm not even going to add it to my | 'to do' list. I'll let the next person have a go, unless there is a | 'real world' scenario where this would be a problem. Well I can only presume then that I happened to click close enough to the envelope point when it happened to me (i.e. amplification of audio before the split)? I was not zoomed in beyond seeing 1/10ths of seconds on the timeline. However it isn't I guess anything more than something to look for in the test build, and a very unimportant thing to look at after 1.4. Thanks Gale | | | Martyn | | Gale Andrews wrote: | > | > Hi Martyn | > | > I did check your envelope fixes as best I could and bar one oddity I could not | > find any problems. Restoration of envelope points was fine too after re-opening | > a Project (and that is now a Mac-specific essential to check). The oddity I had | > was as soon as I started to check, I had a problem with Edit > Split. I had a | > 4 second set of DTMF tones, made some envelope points then split at the | > cursor at one second which was very close to an envelope point. The audio | > from zero to 1 second then went to maximum amplification (Edit > Amplify | > showed no amplification was possible). The envelope points at 1 second were | > gone. I removed the track and recreated it with no envelope points and | > split created no problem. I then recreated the track with the same envelope | > points and the same maximisation occurred. I restarted Audacity and repeated | > the experiment with the same track and envelope points and could not | > then replicate it. | > | > Is there any possible reason for yet another inconsistency? I've left the | > envelope issue with splits as [Done] but added it to "Watching Brief" as well. | > | > | > Gale | > | > | > | > Outbound message virus free. | > Tested on: 10/4/2007 8:08:36 AM | > | > | > | > | | ------------------------------------------------------------------------- | This SF.net email is sponsored by: Splunk Inc. | Still grepping through log files to find problems? Stop. | Now Search log events and configuration files using AJAX and a browser. | Download your FREE copy of Splunk now >> http://get.splunk.com/ | _______________________________________________ | Audacity-devel mailing list | Aud...@li... | https://lists.sourceforge.net/lists/listinfo/audacity-devel | | | | Inbound message virus free. | Tested on: 10/10/2007 1:44:43 AM | | Outbound message virus free. Tested on: 10/11/2007 2:03:46 AM |