Leo wrote this above - and as Leo basically is in charge of design for Audacity, I suspect your request is unlikely to happen.
BTW I’m minded to agree with Leo, I really dislike preferences bloat - Audacity already has far too many prefs settings.
Peter
I understand. But personally for me the option “set project rate” is needed only, that an exported file would have normal sample rate and not for anything else.
But this is not how Muse have (re)implemented this.
In the past the Project Rate dictated the rate at which any audio file was exported - and as this was a somewhat “hidden” setting in preferences (not showing at export time)many users ended up unknowingly with audio files at rates they did not want.
The other change that Muse made was to take away the “hidden” “silent” change of project rate when the user imported their first audio file with a different rate to the project rate.
Now what Muse have implemented is a clear user setting for the export rate directly in the export dialog.
Personally, I think these changes are a big improvement.
Peter
It’s right. But I just say, that the required changes in the dialog should better be made automatically, using Macros, rather than maually with the risk of forgetting, not paying attention, making a mistake. Current version makes users enter the changes manually, bacause there’s no other way.
By the way, is “joint stereo” still present in Audacity version 3.4.0 and later? It seems to me that not. Where did it disappear? You’ve redone “Export” so that I can hardly recognize it! Too many changes at once, it’s hard to re-learn, better gradually. (((((
Joint Stereo is actually still present in Audacity 3.4.x - in fact it is now the only option (and hence no radio button choice). Although it says “Stereo” in the export dialog, it’s actually “Joint Stereo”.
Muse decided to remove the pure Stereo option for 3.4.0 and onwards.
AFAIK I think this only applies to MP3 exports.
Peter
Here’s a way to work around the problem for now - create a (short) silent file with a 48000 sample rate, and import that before anything else, so it sets the project’s rate. I’m not saying it’s the best solution, but it should work.
Over ‘goof proofing’ ends up as ‘smart proofing’ also. Please let the people make their mistakes and learn (natural selection at work) without reducing everything to the lowest common denominator…
I still haven’t receieved an answer, how I can normally, with no efforts export in 48000 hz. May be, to develop a new program, similar to FFMPEG, which would convert imported files into the wanted rate?
This doesn’t work here because most choices you can make for audio have barely any impact. 44.1 vs 48k is one of them, MP3 320 CBR vs V0 is another example. In a double blind experiment you won’t be able to tell the difference. And without noticing the mistake, the “and learn” part won’t happen.
I also disagree with the “smart proofing”. You’re still perfectly capable of setting the rate upon exporting. You also could work around the current shortcomings, such as
Yes, I’m making Audacity a bit more awkward to use for powerusers at the moment, and it’s for the benefit of the majority of users. Incidentally, proper and in-depth scripting of Audacity itself is something we want to do, but we have to refactor a 20 year old codebase before that makes sense. As they are right now, macros are very fragile anyway.
And harder to debug than Excel spreadsheets …
Peter
I could be wrong, but the “old” export was better. Maybe, to get back to the old without further ado?
The old exporter
Going back to it is not viable for us, but is viable for you: Just use an older version.
It’s clear. Let’s say, there’s one single track imported to the project rather than two or more tracks with different original sample rates. Is it possible in this case to make export remember somehow the last value used, simirlaly to channel mode “Mono-Stereo”, bit rate mode “Preset”, “Quality”, Save location? Why does it remember all the others and not remember sample rate? In general, I ask to refine a little.
It’s possible, certaily, to use an older version. But in future more and more versions will release. The problem will repeat, I can’t move on them. (((((((((((((((
It’s right, the sounding differs very slightly. But I suggest, that a program should provide an opportunity to apply the settings, a user chooses. In fact I’m deprived this choice, as it’s unacceptable to switch sample rate each time.
Rather than change the current export behavior - I would prefer it if Muse would make the Export commands in Macros have configurable parameters.
That way:
a) you would be able to create an MP3 export macro that had precisely the settings you always want - and you would be able to make a custom shortcut to invoke that Macro.
b) It would also benefit users (including a lot of Voice Over users) who want an Export Selected Audio.
Peter.
This topic was automatically closed after 30 days. New replies are no longer allowed.