It does not matter what I set as the Macro output directory in the Edit->Preferences->Directories, the MP3 export file is not created there, but in the c:\users\defaultuser\Documents\Audacity\macro-output folder. If it didn’t exist, Audacity will create it.
A very interesting phenomenon, because It worked approx. for 10 exports, not once after that. Reset Configuration has also no effect.
Is this a general service computer? One that has a bunch of different jobs?
What were the jobs after the last good export—even though it would seem to have nothing to do with this problem? Skype, Zoom, Meetings, and other programs change computer configurations when they run, for one notable example.
It is also possible that you have more than one version of Audacity installed on your machine, and that you have somehow invoked the older version.
To eliminate this as a possibility, uninstall all versions of Audacity. You can also spot-check both C:\Program Files and C:\Program Files (x86) for an “Audacity” subdirectory. Then re-download and install from here: Audacity ® | Downloads
If the project has been Saved, then the exported files will be saved in a folder named “macro-output”. The “macro-output” folder will be in the location specified in Directories Preferences.
If the audio in the project came from an imported file as its initial step (that is, it is a named project), the “macro-output” folder will also be in the location specified in Directories Preferences.
I am working with e-books. Every time I finished a part of a book, I have to go to the macro-output folder, and copy back the exported mp3 file to the project directory.
It is really annoying. I think a parameter is exactly what it is - nomen est omen - to do whatever I want with it. If I want to put the macro output in a specific folder, then let me put it where I want it. Seriously. I really wonder, what is the purpose of this (or any) configuration parameter if it can’t take any value I set.