I am a Software Engineer and a hobbyist singer/music producer. As one would expect, I would like to explore combining these two worlds and create plugins of my own
I started on September 8, 2024 with a similar story.
Go to the second link you posted, and follow the link in the README, which will take you to the list of commands you must run in order to begin building out of source. Iāll copy them here for convenience:
mkdir MyNewPlugin
cd MyNewPlugin
git init
git submodule add https://github.com/iPlug2/iPlug2.git
cd iPlug2/Examples/
./duplicate.py IPlugEffect MyNewPlugin MyManufacturerName ../..
cd ../..
git add MyNewPlugin
#could also add VST3_SDK etc submodules, but need to modify plug-in VisualStudio and Xcode projects
#git submodule add https://github.com/steinbergmedia/vst3sdk.git VST3_SDK
#git submodule update --recursive
git commit -a -m "initial commit"
Just run those commands. You will end up duplicating an example as your starting point, so choose the example that most closely matches what you aim to build. In other words, substitute āIPlugEffectā in those commands if youāre not building an effect.
Your first objective is to get the example successfully built. From there you can start editing things.
Here is a random piece of advice that I learned later than I should have: Store state in your plugin instance, not in your controls. Your controls should modify state and not store it, as new control instances are attached each time your GUI reappears.
Full disclosure: I was half asleep when I read an email reply to this thread, and I thought it was a customer for a product on my website. I didnāt realize my replies to the email were made public in this thread, so if something seems off here, thatās why.
Anyways, it was great meeting Kashish and talking about getting started with iPlug2. Thanks for this awesome framework! Iām excited to share my plugin when itās complete.