Batch-export to AU Preset utility for factory presets in Plugins & VI libraries you own
-
- KVRer
- 7 posts since 5 Oct, 2005
How much would you pay/give for a utility that can batch-export to AU Preset files the plugin proprietary factory presets for Plugins and VI libraries you own?
You do not have the required permissions to view the files attached to this post.
Last edited by dstenning on Fri Jul 17, 2026 12:24 pm, edited 1 time in total.
-
- KVRer
- Topic Starter
- 7 posts since 5 Oct, 2005
Example of automatically created AU Preset directories including sub categories
You do not have the required permissions to view the files attached to this post.
-
- KVRAF
- 3060 posts since 6 Jul, 2013
I’ve always done this myself with custom automation scripts using Keyboard Maestro, and can basically handle pretty much anything now - some plugins are very bad behaving in this regard, so some plugins are more challenging to do than others. I’ve done at least a quarter of a million presets over the years, and most of them are available on LogicProHelp as I share the factory presets on a dedicated thread for other people that own the plugins to use.
It’s a pretty niche thing, there are people like myself that prefer the consistency of having presets in Logic’s (rudimentary) preset browser, but a lot of people are happy enough with using plugins’ internal preset browsers.
It would be interesting to see how you are handling more complex taggable preset browsers though, usually when exporting these you have to make some choices about how you export…
Edit: Looking at your screenshot, it seems you're essentially doing this more or less how I approached it, by remotely driving the plugin interface - so you're not doing anything I'm not already doing as such.
It’s a pretty niche thing, there are people like myself that prefer the consistency of having presets in Logic’s (rudimentary) preset browser, but a lot of people are happy enough with using plugins’ internal preset browsers.
It would be interesting to see how you are handling more complex taggable preset browsers though, usually when exporting these you have to make some choices about how you export…
Edit: Looking at your screenshot, it seems you're essentially doing this more or less how I approached it, by remotely driving the plugin interface - so you're not doing anything I'm not already doing as such.