Re: [Audacity-devel] So now what? :-)
A free multi-track audio editor and recorder
Brought to you by:
aosiniao
From: <ma...@ga...> - 2007-05-20 02:46:01
|
| From Leland <le...@au...> | Sat, 19 May 2007 18:29:17 -0500 | Subject: [Audacity-devel] So now what? :-) | On 5/19/07 3:17 PM, "ma...@ga..." <ma...@ga...> | wrote: | > * Are all of the current features sufficiently complete as opposed to | > bug free (what about Batch processing?) or should parts or all of them | > be removed for 1.4.0 (what about FTP, Theme)? | FTP I can fix. Is this something that's desired for 1.4.0? It would be nice to have FTP in 1.4.0 if it can be made to upload the current Project but this looks like a lot of work and not vital for 1.4.0. I'm not sure how it would fit in with the Export dialogue - an FTP button additional to the Save button, then when you click the FTP button and choose what FTP site to connect to, the file is on its way? I think Richard felt it should export a local copy as well? My feeling is though FTP should probably be removed until it can upload the Project, as that is what most people will want it for? Until then, these seem to be issues with what we have now: * Download (on right click menu) freezes but can be cancelled safely * Sort by size and permissions does not work * current sort of list looks arbitrary (not alphabetical anyway) * Possibly needs "set permissions" on right-click menu * upload file and new folder works; upload folder does not seem to work * delete should work on DEL hotkey | > * Should we disable Advanced Mixing Options as James suggested? I am | > not sure I see the need myself to disable it as it is now working again for | > WAV/AIFF, | I'd think it should still be available in 1.4.0, but as you say, set to | turned off by default in Preferences. It is off by default so that does not need to be changed. I would like to see it in 1.4.0 as it works very smoothly but it will need highlighting in the Manual/publicity so it can actually be found, given it cannot easily be put in the File Save dialogue at the moment. | > though it is not offered with Export Multiple - is there any | > longer term intention it should be? | Would it make sense for Export Multiple since each track is going to a | separate file? Stereo tracks are handled automatically so you should need | the dialog for that would you? I think it would be useful you had say 6 tracks on screen and wanted to split into separate 5:1 files at labels e.g. three labels gives you three separate 5:1 files. As it is now, you are compelled to mixdown these three files to two channels if you want the convenience of splitting at labels rather than exporting three selected areas one at a time. Lack of advanced mixing for Export Multiple should not I think prevent its inclusion in 1.4.0 if it's time-consuming (presumably it should be disabled except in the above scenario where you have labels combined with more than one stereo or mono track), but I'd think we should be considering it after 1.4.0? | > I hope we won't lose sight of the remaining essential changes that were | > thought mandatory for 1.4.0 | > http://audacityteam.org/wiki/index.php?title=Release_Checklist | > | I just added 3 more today. Is the "random bits of silence during recording" cross platform or only thought to be Linux? Did you feel now these silences are inserted rather than missing audio? | > I've been discussing the "Alert for MP3 invalid "bitrate/sample rate | > combinations" | > | This should be okay now with the new dialog that prompts for a valid sample | rate. Is there still something I need to do here? Thanks for doing that dialogue - I did not know you had done it as you had not said, and I must have missed it in the CVS list. Looks nice (but note "sampel" in the dialogue title). I think the dialogue needs "don't show this again". My concern though is that now we are locking the input sample rate to the output rate (where it is valid) instead of allowing any downsampling that LAME would default to, we risk terrible quality output files. 1.3.2 would if you asked for a 44 100 Hz 32 kbps MP3 give you a 16 000 Hz 32 kbps MP3 because it allows LAME to downsample. 1.3.3 gives you the 44 100 Hz 32 kbps MP3 you wanted. But did you compare those 44 100 Hz 32 kbps and 16 000 Hz 32 kbps files I pointed you to which were encoded from the same high quality WAV file? http://www.gaclrecords.org.uk/audacitytestfiles.html The 44 100 Hz file is unlistenable in my opinion. So, what do we do - allow LAME to downsample as it recommends (and sounds as if it's essential)? Or as I think is best - throw a separate warning for these (fairly few) high sample rate/low bitrate combinations that are valid, but may sound dreadful? | | > There are other "essentials" where I do not know if things are moving e.g. | > James' Preferences option so that clicking on Effect "selects all" if there is | > not | > already a selection (I wonder if this needs a Preference - should it not just | > happen?); and "warn on close-tracks-and-exit, will lose those unsaved tracks". | > Note currently that 1.3.3 exits without even any "save changes?" dialogue if | > there are no open tracks, even if there have been tracks open which have | > now been closed. That is not acceptable. | > | What should happen? Just a verification dialog. Should this be one of the | "Don't ask me again" kind of dialogs? What "should" happen I think and is noted in the Release checklist is a "special" warning that the user is about to save a Project with no tracks, which will mean that any previous audio in the Project when tracks were open will be lost. The danger here is novices who think that closing a track "saves" it (like closing a file does). So they want to see something like: ? You are about to save an empty Project without tracks. This means when you reopen the Project, it will have no audio! Do you want to: Cancel - recommended. Use Edit > Undo to reopen any tracks you closed then File > Save Project Save changes - not recommended. Saves your Project with no audio content. Lose changes - Exit Audacity without saving a Project. All your changes will be lost. Arguably if they chose "Save Changes" they should be asked if they really mean to do this. Gale | | Leland | | | | ------------------------------------------------------------------------- | This SF.net email is sponsored by DB2 Express | Download DB2 Express C - the FREE version of DB2 express and take | control of your XML. No limits. Just data. Click to get it now. | http://sourceforge.net/powerbar/db2/ | _______________________________________________ | Audacity-devel mailing list | Aud...@li... | https://lists.sourceforge.net/lists/listinfo/audacity-devel | | | | Inbound message virus free. | Tested on: 5/20/2007 1:53:30 AM | | Outbound message virus free. Tested on: 5/20/2007 3:45:57 AM |