Re: [Audacity-devel] Apply ExportDownMix on Cancellation of ExportMixerDialog
A free multi-track audio editor and recorder
Brought to you by:
aosiniao
From: Gale A. <ga...@au...> - 2012-12-17 00:49:46
|
| From "Sven Giermann" <gie...@fu...> | Sun, 16 Dec 2012 19:49:00 +0100 | Subject: [Audacity-devel] Apply ExportDownMix on Cancellation of ExportMixerDialog > I see your concerns regarding planned change of the whole Export process. > Maybe it might be better to have a separate Export Dialog, compared to Export Multiple. > BUT - having in mind the request, that some people would like to use Audacity as a simple Wave-Editor, I would not overload this - or another suggestion: > Leave the Export-Function as it is; even go further and spare out the custom channel mix completely. > At the same time rename the "Export Multiple" to "Advanced Export" and enable exportation of all tracks to a single file as a third option next to "Split files based on Labels/Tracks". Then the dialog could be further expanded to Channel Mix Options and so on. I can see what you are driving at in making File > Export the simpler choice with the fewest options. But we may sometime want custom mix options for Export Multiple itself, so might this be harder to present in something like the current Export Multiple dialogue if that dialogue chose between custom mix for straight export and custom mix for export multiple? A lot of (not especially advanced) users use Export Multiple so we have to be careful of not over-complicating that too. I would think straight export would have to retain the ability to do mixdown of multiple tracks to mono or stereo. I assume you agree? > But at this point I fear I am simply to young in using Audacity - maybe some of the "old boys" should discuss the right way to go. If you have some suggestions or decisions how to go, I am still willing to code this... > Don't get me wrong, but I wouldn't want to spend time in coding for something that is not wanted and I cannot decide things right now, as I'm not involved enough. > (so feel free to ping me, when you have some detailed wishes, what to be changed) I guess moving the "Use custom mix" Preference into a checkbox in the dialogue for straight export would be fairly uncontroversial and addresses the problem you raised, but it's unfortunate that is not easy to do. I agree that combining channel mixing options into a dialogue for encoding options could be confusing in itself. I'm inclined to put that on the back burner even though it is fairly easy to implement. > Apart from that: the mentioned bug should not be very hard to fix. > I will have to modify the ShowWarningDialog to accept further Buttons and to return the user choice. I will have a look at this and hopefully supply a patch within the next days. I see you have offered a patch now, thanks for that. Gale > From: Gale Andrews [mailto:ga...@au...] > To: aud...@li... > Sent: Sun, 16 Dec 2012 02:50:04 +0100 > Subject: Re: [Audacity-devel] Apply ExportDownMix on Cancellation of ExportMixerDialog > > > | From Sven Giermann <Gie...@fu...> > | Fri, 14 Dec 2012 08:53:51 +0100 > | Subject: [Audacity-devel] Apply ExportDownMix on Cancellation of ExportMixerDialog > > But I thought about a Preference like Dialog with the three different > > Panes (see attached screenshot). > > I just painted this screenshot for now - so please give me your > > feedback, if I should go on modifying all dialogs to be able to display > > in this Pane style. > > The size would not grow significantly and one would still be able to > > access all options. > > > > The point to discuss would be to either show this dialog every time > > AFTER selecting to filename - or simply by clicking on "Options..." > > WHILE selecting the filename. > > I would still feel it best to leave the Metadata Editor behaviour > as is until we decide to where to go with it. Not least that in > your proposed dialog people could easily miss the metadata > (which is the most important of the three nodes) unless you > initialised to it. And if you did that, I'd bet people would still > be missing the encoding options. > > Whatever the dialogue contains, I feel the key to the problem > that people can't find the encoding options is either to show > those options every time - ideally embedded in the current > dialogue or as a slideout - or modify the dialogue (at its simplest, > move the "Options" button to be (on Windows) under the > "Save as type" or under the drop-down list of file types). This > can be done. > > That would make it more reasonable to show a combined channel > mix and format options dialogue on clicking the Options... button - > we would be increasing the chance that people would find the > dialogue. Though I would not do that as a tree but with the > format options built into the one dialogue. > > > > But YES, I do see difficulties to add a radio button directly to the > > "Choose export filename", becaus there is no standard way in > > wxFileDialog. Starting with wxWidgets 2.9 (still unstable) they > > introduced some "Client part" in these dialogs - but I did not play > > around with this yet. > > I could have a look into how the Options button was added, but I fear to > > add more content would grow the dialog unnecessarily and to depend more > > on the used wxWidgets version. > > Yet another issue is that the "Export File" dialogue looks completely > different on the different platforms (on Ubuntu, the Options button > is the width of the dialogue and keyboard accessibility is poor - > TAB gets stuck in the file name). > > Although it would be a lot of work, I see a huge benefit in making a > customised dialogue for straight export as we do for Export Multiple. > It would give us a lot more flexibility (and consistency) in dealing > with the issues that you and others have noted. > > So sorry I am not really answering your question but I'm thinking > until we can modify the Export dialogue to some extent, what > you are proposing so far isn't going to be a huge help. A combined > channel mix/format options dialogue would be an advance, but > we couldn't I think reasonably have it pop up by default. > > Meantime can you see a decent fix for this: > http://bugzilla.audacityteam.org/show_bug.cgi?id=598 > > I'd be glad to see a patch for that. > > > Thanks > > > > Gale |