Macros are not exporting the files in the Audacity 3.0.2 windows 10

Hi There,
in the previous versions of the audacity, after applying macros the audacity use to create a new folder “macro-output” and save all the files automatically to it. But now macros are working fine BUT they aren’t exporting the audios. e.g, I created a macro of which steps are 1) Normalizing, 2) Noise reduction, 3) Limiter, and finally 4) Export. it is performing all the 3 steps but is not exporting the final file nor creating a new folder “macro-output”. So, I export all the files manually.

Any Help would be much appreciated.

Nauman(ACX Editors)

The export location was changed for Audacity 3.0.2

See the What’s New… page in the 3.0.2 Manual:

The default location on Windows is: C:\Users<your username>\Documents\Audacity

You can change that to a location of your choice in Directories Preferences.


Hi Peter.
Thank you very much for your prompt response. Does this mean that now audacity will not create a new folder “macro-output” automatically in the same folder(where the files are already present)?

Thanks again and have a great day.

Audacity will create the “macro-output” folder in the Macro output directory. You can specify where you want the Macro output directory to be in Preferences, as shown here:

It does not create a “macro-output” folder in the same folder as the input files, unless that happens to be your chosen Macro output location.

Thank you very much, Steve.

By the way, this was a great feature(creating the folder automatically in the same directory where the files are) but, thank you for your kind help.

I’m hoping that behaviour will be restored as an option in a future version of Audacity, but in the meantime, there’s a Nyquist plug-in available here that can be added at the start of a macro to automatically set the output folder to the same location as the imported file:

Instructions for installing and enabling Nyquist plug-ins on Windows:

Yes I agree, it was a great feature, creating the folder automatically in the same directory where the files are.
I hope they bring it back in the next Update.

Why did it need to change? Granted, I am on MacOS, and not sure if it changed in that version, but I am still on 2.4.2 and am certainly not moving to 3.x now if it did. I use this EVERY day. I would go nuts and be very hindered in my workflow if I had to deal with one central location for the macro output.

A lot of users requested that the location should be customizable. The change was in response to user demand.

Thanks for the reply. Would it make sense then to add, in addition to a customizable, settable path, to include an option for the previous behavior?
Such as an unspecified path will default to same as source files?

That was what I hoped would happen, but it didn’t.
I posted a feature request here: