Now that's a dev who responds to their users. I appreciate the change. I have downloaded the new version, and will test it out here in a bit. Again, thank you.

 

Looks very neat. Nice job, props!

 

That's awesome, I'm not sure what to use to compile programs these days though. I don't really get how to use python or github.
By the way Al Bundy is the greatest human to ever live. #33 Polk High Al "Touchdown" Bundy, he scored 4 touchdowns in the 1966 City Championship game against Andrew Jackson High.

 

I like Reaper, and bought it and now find other DAWs a bit frustrating, but ...
...the handling of plugin menus is quite annoying in Reaper.
The inability to have plugin subfolders is annoying.
And very annoying to have plugins removed from my own directory in "Folders".
I'd rather have the shortcut remain and to just get an error if the plugin is actually missing.

At least one can put the plugin shortcuts in multiple folders, as many belong in multiple categories.

Unless i am mistaken, the "Folders" directory is the only one which is actually to be for the user's customization.
Is that true?

 

I can prepare manual how to make it from code, or you can download build form build folder in codeberg repo.
build-UAC will ask you for elevated rights,
build-nonUAC will not, but elevated rights are required for renaming files in plugin directories.

 

I created a pull request on Codeberg to build an executable, merge if you wish.

I'm not entirely sure how to publish the artifacts in there, and might be better if it's done in the main branch.

 

Hmm... CLAP has an info tool at https://github.com/free-audio/clap-info, I'll take a look if it can vomit out relevant information.

Also... I'll try to patch in Linux support as Python makes it simple to determine the underlying OS, might be simple to crowbar macOS support (AUs need to be scanned for this, but this is dead simple).

 

Nothing helps to defeat plugin-Alzheimer like an excel sheet. It allows me to write down notes per plugin, categorize, search (the notes, too!), filter.
But I admit, a shortcut on the desktop is not very sexy.

 

Cool program.

Runs and compiles fine on Linux it just doesn't understand yabridge and or .so files. It'll disable a plugin but the DAW thinks it's still there. Good luck to you if you manage to make this program work. This software looks very convenient; good luck to all involved.

 

thanks for testing
I think I can solve issues with Linux. Basically program is looking for .vst3 .dll and .clap file extension omit all other files. I could try add LV2 and add option to looking for .so pair in yabridge folder.

 

Default VST2 path won't work for most people, because the default has been Program Files/Steinberg forever, and most installers default there too. Aside that, you could be into something with this. Good work.

 

I'm working on some code to handle these, it needs to be fixed that we can do multiple paths for a given plugin format though.

Code:

 plat = platform.system()
    platform_paths = {}

    match plat:
        case "Windows":
            platform_paths =  {
                "VST3": r"C:\Program Files\Common Files\VST3",
                "VST2": r"C:\Program Files\Common Files\VST2",
                "CLAP": r"C:\Program Files\Common Files\CLAP",
            }
           

        case "Darwin":
            platform_paths = {
                "CLAP": r"/Library/Audio/Plug-Ins/CLAP",
                "VST2": r"/Library/Audio/Plug-ins/VST",
                "VST3": r"/Library/Audio/Plug-ins/VST3",
                "AU": r"/Library/Audio/Plug-Ins/Components",
            }
           

        case "Linux":
            platform_paths = {
                "CLAP": r"/usr/lib/clap",
                "VST3": r"/usr/lib/local/vst",
                "YABRIDGE": r"",
                "LV2": r"/usr/local/lib/lv2"
            }

And likewise for extensions. Then there's also CLAP_PATH (and others) environment variables, nothing too bad though.

 

So nice thank you bro!

 

Alright, committed initial code for Linux (CLAP, LV2 etc.) and Mac (Audio Units), and made a pull request.

 

I compiled your commit, for some reason vst3 and lv2 are not showing however yabridge and clap appear to be working perfectly. Did I do something wrong?

 

No, my paths are probably way off, and I probably missed a spot making the changes to scanning. I'll have a looksie once I get to boot to Linux. Thanks for testing though!

I've got an old Mac on standby, I'll try there as well.

 

That sounds awesome, Codeberg is a program to compoile code?

 

Codeberg is a project management/repository site for open source code (usually). Github would be the most known equivalent. The project itself is written in python so you would need to install python to compile this project. However pre-compiled binaries are shared in the "build" folders if you're interested in trying his cool project.

 

ah ok I see, come froma visual basic background myself but I'm talking 20+ years ago lol

 

Quick build instructions for the latest:

• Get Python from https://www.python.org/downloads/ if you're using Windows, select "Add python.exe to PATH". (Linux and macOS* should have this installed). Log out and log in again, or restart your computer.

• Get the latest code from https://codeberg.org/deathroit/f-ing-simple-plugin-manager

• Extract the .zip file somewhere convenient, open a command prompt there and run build.bat (Win) or build.sh (Linux/Mac)
• Go to created dist folder and look for the directory f-ing-simple-audio-plugin-manager, copy that folder where ever you want and run the executable
• Alternatively you can cd to src in the command prompt and just run python f-ing-simple-audio-plugin-manager.py from there
• Edit the paths.conf to your liking, the default paths might not work for you

*) Older versions of macOS might have too old of a version of Python, ask me if you need any guidance with that