Shameless Plugs™



Introduction

My desire to create plugins started a long time ago, around the time when we had just left the old millennium behind and ushered in the current one.
Back then, DirectX plugins were still a thing (and maybe they still are but nobody's paying attention), and I remember visiting a small software shop, in Vienna where I lived at the time, in order to purchase one legal copy of Visual Studio 6.0 (not entirely sure about the exact version, but it can't be far off).
Well, that never got off the ground.
I was working as a Delphi 7.0 developer, and that meant being spoilt rotten by its goodness and luxury, so getting used to C++ simply wasn't going to happen.

(I did try to use Delphi to create VST2 plugins; however, I never found the available Delphi VST SDK to be stable enough for serious development.)

Humble beginnings

Not long after that, I discovered SynthEdit, and I did manage to create a VST plugin with it, a guitar amplifier simulator, which included a speaker cabinet simulator section.
It wasn't very good, and I am not going to divulge what it is.
You can still find it online, and maybe you have used it.
Maybe you even like it.
But if you ever ask me whether a particular plugin is that old crusty plugin, I will neither be able to confirm nor deny it.

Then life happened, and I largely abandoned my attempts at creating plugins.

Fast-forward to 2020, and the world found itself in a pandemic.
Life largely stopped happening, and most people, including me, were stuck at home for the most part.

This time it's serious

That's when I started reviving my old desire to create audio plugins.
I looked into various frameworks, to see what would be most suitable.
I also looked into languages other than C++, but unfortunately C++ is still the dominant language.

Of course I checked out Juce, and I can tell it's big, and I'm sure it's sophisticated, and I guess it's the rockstar of the plugin framework world, but I didn't like the licence, and I didn't like the fact that it would cost money that I didn't really have for me to get rid of a very unprofessional looking nag screen.

Then I tried RackAFX, as well as its core ASPiK on its own, and I have to say, these are in and of itself excellent possibilities, and I did achieve quite good results, and fairly quickly.
However, because the sole maintainer, the brilliant Will Pirkle, is a very busy lecturer and author in all things DSP, updates are few and far between, and there isn't any real community surrounding it that I would need if I ever got stuck.
And this is all rather unfortunate, because Will Pirkle's software is brilliant.
I call on all experienced C++ developers to contact Will and offer to help maintain and expand the RackAFX and ASPiK projects, because they deserve better.
For one excellent example of successful development using RackAFX, check out Exe Consulting's guitar and bass amplifier simulator plugins, as well as some other projects.

And then there was iPlug2.
iPlug2 is light, and easy to use.
It has a community that is much more active than the almost nonexistent RackAFX / ASPiK community, although much smaller than the Juce community.
In fact it is so small that if you ask a question on e.g. Discord, it will very probably be iPlug2's lead developer Oli Larkin who answers the question (or doesn't answer it, if he deems the question to be not relevant enough to iPlug2).
Would I recommend iPlug2 to anyone, programming beginner or veteran, who wants to get started with plugin development, or who already makes plugins in some other way but wants to switch?
Absolutely.

First releases

My first plugin using iPlug2 was going to be DirtyQ, a simple EQ, with added saturation (in fact, the first iterations were made using RackAFX).
It's not quite there yet, but it does incorporate some interesting technology I developed that serves to make the saturation sound more gentle and smooth: a tilt EQ section.

I'm sure DirtyQ will be released some day, but at some point for some reason I decided to use that technology to create a more basic plugin, and release that first instead: TildeQ.
TildeQ has only the tilt, and the low and high cut from DirtyQ.

Next came The Dom, a signature plugin for Dom Mcsweeney (see the Acknowledgments), who had at that point become a tireless beta tester and sounding board.
The Dom, again, uses the tilt technology, but internally only, where it is used to shape the sound both before and after the saturation circuit.

Future

A number of future plugins are planned; stay tuned, bookmark this page, subscribe to Shameless Plugs' YouTube channel, and join Shameless Plugs' group on Facebook, The Shameless Plugs Victims Support Group.

It is my intention to release a free version as well as a paid version of each plugin.
The free versions (will) offer basic, yet useful functionality, whereas the paid versions will offer a more luxurious feature set.

Acknowledgements

I would like to thank, in no particular order (please refresh this page a few times to see how seriously I take that), the following amazing people, without whom any of this would've been entirely impossible:

Impressum

Contact: info@shamelessplugs.net

Back to top ^