Audacity Forum

BTW 2.3.1 is currently only an alpha test build - you should be working with 2.3.0 (which still has the same bug).

WC

This is a known bug that we are aware of - it is proving hard for us to track down as we can't reproduce it on any of our testers' or developers' machines.

And although it's a bit annoying - it does no harm, just dismiss that dialog.

WC

Yes you will - but if you are going to do this you may as well do all the work in Audacity - just ensure that you only make the new MP3 export right at the very end. If you want safety copes as you work than export temporary WAV files.

WC

Did you try to get it from here: https://www.audacityteam.org/download/
our official download website

WC

Ok, I can change the Directories setting to my network folder (something strange there, though). This would be fine for now. I couldn't do that when I was testing - how did you achieve that ? When exporting with macro, I get a confirmation pop-up window. Any way to get rid of that? I don't see a co...

yes, just use Transport > Rescan Audio Devices

WC

This because what a Macro does when working on a file or set of files that you give it to process to produce exports, is to create a folder called cleaned in the same file location that your files to be processed came from. In your case the file input files would have been in C:\Users\My_account\Doc...

Batmensch wrote: ↑

Tue Jan 01, 2019 7:15 am

I have heard that it actually samples at 44056 rather than 44100. In any case, where would I set these options? In Audacity?

1) In the Quality tab of Preferences -
2) in the dropdown menu for Default Sample Rate
3) select Other
4) type in your preferred rate
5) Press the OK

WC

Not a bug, but, thanks again for the way the track solo/muting works in this version. Previously it had been a bit fiddly, but now its perfect :) Thanks for the feedback - I, too, think it's easier to use the (default) way it is now. Folk with more complex needs acn always change their preferences ...

I cannot reproduce this on W10 with the latest release 2.3.0 or the previous 2.2.2 release - nor on the latest test alpha for 2.3.1

WC