Re: [Audacity-quality] [Audacity-devel] Some high return features/fixes for 2.0.2?
A free multi-track audio editor and recorder
Brought to you by:
aosiniao
From: Steve t. F. <ste...@gm...> - 2012-07-11 11:57:15
|
On 11 July 2012 12:01, Gale Andrews <ga...@au...> wrote: > > Summary: Vaughan asked for a prioritisation; my priority is > similar to the order I listed the issues in before, viz: > > 1 Snap To (P2 on bugzilla) > [2 Audio Cache - now removed from Prefs. ] > 3 Default the selection format in Generators to last used > 4 Improve Chain export features > 5 Export to directory the file came from > 6 Export Multiple passthrough of common metadata > 7 Fix or replace GVerb > 8 Import files end-to-end > 9 Control gain sliders on all tracks. Overall +1 I think there's some close calls on priority order and if a developer sees a fix for any of them and wants to go for it "out of order" I'd have no objection at all. They all need fixing eventually. I keep thinking that I'd like to move 8 and 9 higher up, but I don't want to move any of the others lower down :=) > > Ideally I like to see 1 through 6 completed. If there is a "simple" > solution to 9, I'd move it up to 6 or 7. > > A few more comments in line. > > | From Bill Wharrie <bi...@go...> > | Tue, 10 Jul 2012 21:07:22 -0400 > | Subject: [Audacity-quality] [Audacity-devel] Some high return > | features/fixes for 2.0.2? >> > ----- Original Message ----- >> > From: Gale Andrews <ga...@au...> >> >> > Details: >> > >> > All these cause frequent angst to users, due to crashes, being left >> > with reduced functionality with no idea how to correct it, or being >> > un-necessarily asked to go through repetitive hoops to perform >> > what should be a simple task. >> > >> > "Votes" means votes on Wiki Feature Requests. >> > >> > * Snap To: >> > http://bugzilla.audacityteam.org/show_bug.cgi?id=436 >> > >> > Reported almost daily. Discussed here: >> > http://sourceforge.net/mailarchive/message.php?msg_id=27402899 >> > >> > and maybe elsewhere. I prefer some kind of fix to make it harder >> > to click on, while retaining it in Selection Toolbar (e.g. a button), >> > rather than e.g. turn Snap-To off when zoomed in. Or we could >> > have a box pop up when you enable Snap To. >> >> I don't know if I'd characterize it as a "bear trap" - it is too easy to get out of. >> To me this is akin to a photoshop user setting the crop tool to an 8 by 10 ratio >> then being bewildered when the crop tool is constrained to an 8 by 10 ratio. > > Completely agree with Peter's response. I think most users are not > consciously enabling the feature. No-one I have asked who fell into > the problem were aware they had switched the feature on, or that > it even existed. > > And what about the hours of support and users' time wasted on > this? > > >> However, if it is felt it *must* be changed, I'd support keeping the >> checkbox as is, with a warning (with "don't show again" option) >> when setting it to On. Yet another warning preference. > > Indeed, and using the warning as an "education". > > On balance I still mildly prefer to move the checkbox to the end > of Selection Toolbar and see if that caused sufficient reduction > in complaints. > > >> > * Chains. Add export format options (to save having to start then >> > cancel manual exports just to set the export format option for >> > the Chain). Add export sample rate so that Chains are not halted >> > by sample rate/bit rate mismatches. [Secondary: Add AIFF, >> > Other Uncompressed Files and FFmpeg formats exports]. All these >> > have circa 20 votes. >> >> No opinion as I never use chains. > > Neither do I, but clearly these are important issues for those > who do, as you can see on the Forum. > > >> > * Export Multiple: Checkbox in dialogue to pass metadata through >> > to all exported files automatically, otherwise you get a screen >> > to OK on for each exported file. It saves having to File > Open >> > Metadata Editor to add tags before export, which is unintuitive. >> > (35 votes) >> >> Wasn't this discussed before, and weren't there reasons what it >> was either difficult to implement or not a good idea? > > Leland made a patch a long time ago which did not work properly > (don't recall details). I think the discussion prior to that was > on whether the checkbox proposed for the Export Multiple dialogue > should also appear in Preferences. If we go for this one in 2.0.2 > I can find more details. > > The primary issue though is that in 1.2.6 the common metadata was > passed through to all the exports; now if you have 15 songs and > don't know the workaround, you have to hit OK 15 times when > exporting. > > > ---- > > Audio Cache: I am interested to see how many users will be > opposed to this removal. Most of those who report crashes are > on fast machines with at least 4 GB RAM and I am surprised at > the number who (apparently consciously) enable it. I'll comment > in the bug on recent evidence gathered as to behaviour of this > feature. > > ---- > > I moved GVerb down in priority as reverb is a very important > effect and we may want to spend more time on this than we > have for 2.0.2. AFAIK there is little support in LADSPA for > Presets, but there is in LV2 if we ever complete LV2 support. > I don't think we should wait for LV2 to take action about reverb > (note that on Linux we don't even ship a reverb). > LADSPA plug-ins certainly can support presets. Presets for LADSPA plug-ins are supported with Ardour, Calf Host, Guitarix, Jack Rack and many other LADSPA hosts. Most of these also provide nice, user friendly graphical interfaces for LADSPA plug-ins rather than the extremely basic and user hostile (well not friendly anyway) GUI that Audacity provides. Audacity does not support presets with LADSPA plug-ins, so that must be a limitation of Audacity, not of LADSPA. Presets CAN be used with GVERB (Gverb presets are supported in Ardour and I've seen references to presets in the Gverb code). This would resolve the bulk of the complaints about Gverb, though there are still the major limitations that it's not very good for "ambient" reverb and it is mono. As Audacity ships with several LADSPA plug-ins and supports very many more, I think there is potentially an excellent "ROI" for bringing Audacity's LADSPA support up to scratch. If we want a theme for a future release, adding good LASPA support (at least for bundled effects) could be a good theme and seen as a major enhancement. Steve > > > > > Gale > > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > Audacity-quality mailing list > Aud...@li... > https://lists.sourceforge.net/lists/listinfo/audacity-quality |