import / export user-defined macros

Help for Audacity on Windows.
Forum rules
ImageThis forum is for Audacity on Windows.
Please state which version of Windows you are using,
and the exact three-section version number of Audacity from "Help menu > About Audacity".


Audacity 1.2.x and 1.3.x are obsolete and no longer supported. If you still have those versions, please upgrade at https://www.audacityteam.org/download/.
The old forums for those versions are now closed, but you can still read the archives of the 1.2.x and 1.3.x forums.
Post Reply
rajahb
Posts: 4
Joined: Sat Nov 24, 2018 4:25 pm
Operating System: Windows 10

import / export user-defined macros

Post by rajahb » Sat Nov 24, 2018 4:36 pm

OS: Windows 10 Pro x64 build 17134
Audacity version: 2.3.0

Is there any way to export the macros I've created so I can import them onto another computer?

I've searched the install directory but cannot figure out where user defined macros are stored.

I've also searched audacity help, this forum, audacity faq, general google search. No luck finding any information regarding loading/saving/importing/exporting user-defined macros.

waxcylinder
Forum Staff
Posts: 14687
Joined: Tue Jul 31, 2007 11:03 am
Operating System: Windows 10

Re: import / export user-defined macros

Post by waxcylinder » Sat Nov 24, 2018 5:12 pm

I thinks James is planning to write an Import/Export for Macros at some stage …

But until then there us a workaround.

You should find a Macros folder inside your Audacity settings folder.

On Windows this is C:\Users\<your username>\AppData\Roaming\audacity

you can copy the Macros folder or any macros from within that folder and thus move them to another computer.

WC
________________________________________FOR INSTANT HELP: (Click on Link below)
* * * * * FAQ * * * * * Tutorials * * * * * Audacity Manual * * * * *

rajahb
Posts: 4
Joined: Sat Nov 24, 2018 4:25 pm
Operating System: Windows 10

Re: import / export user-defined macros

Post by rajahb » Sun Nov 25, 2018 4:51 am

Thanks waxcylinder - the workaround worked perfectly!

Post Reply