Plugalyzer icon indicating copy to clipboard operation
Plugalyzer copied to clipboard

Command-line VST3, AU and LADSPA plugin host for easier debugging of audio plugins

Results 9 Plugalyzer issues
Sort by recently updated
recently updated
newest added

What I did: 1. Downloaded CLion 2. Downloaded Visual Studio with Clang support 3. Cloned appropriate version of branches (blue links in readme) 4. Loaded project into CLion 5. Built...

I think Plugalyzer could be even more useful if we could load vstpresets directly. From what I found it seems pretty straightforward; I'd give it a go myself but haven't...

enhancement

any chance a version can be built including hosting VST2? I realize you can't provide the VST2, headers. Maybe some instructions for how we can build that?

Closes #15. @steveschow Please build and test whether this suits your needs - I wasn't able to find a free MIDI processing AU/VST within a reasonable time.

This is most likely 100% out of scope for the time being and might belong in a tool that uses plugalyzer. I'd like to store reference audio files in my...

enhancement

I mainly write midi plugins. Would be great if we could capture midi output to check the results.

enhancement

Closes #13. @wrenchse please test and report back, as I don't have any VSTs with presets on my Mac.

This makes it possible to parse only the (debug) output of plugins without having to sift through the entire output of the Plugalyzer command.

enhancement

Now that this project is growing, I feel like we should use a proper logging library that supports different log levels, such as error, warning, info. One suitable candidate is...

enhancement