A sceenshot of the actual plugin example
More similar examples in C code can be found here
The code crosscompiles with 100% identical code to Windows and Linux and make 64-bit and 32bit plugins.
It subrogates the VST2 license by only using the ABI. Yes! the vst2 format will be alive and kicking forever. This makes it possible to make plugins to use in the majority of all music programs.
The code is written entirely in C code, a language that is the most commonly used for audio applications for hardware, and it's a much simpler language than C++ to learn, and will also give the fastest possible plugs possible, with the highest amount of compatibility.
I would check out the RST Framework examples There you will find several templates and examples. And take one of the examples and tweek that file. Make a change and compile and check out the difference by loading the plugin into a music program. And here can you information about the plugin GUI toolkit ikiGUI
To make this available this code-base only uses the vst 2 ABI.
It's proven in court that you can't protect a API from common usage according to the the U.S. Supreme Court’s April 5 ruling in Google LLC v. Oracle America Inc. in 2021. And it's certainly the case that you can't protect an ABI with copyright within all reasonable doubt. And any resemblance of the original API is well motivated as it's not even prohibited to make use of the original API without any violation of any original VST2 licenses.
This makes compiled binaries for the most amount of music programs, with the least amount of code and dependencies.
I have kept the code size as low as possible, and made it compatible with Linux and Windows without any third party libraries, relying only on well established standards. This will make it compatible to the most systems even when compiling on a Linux machine and compile to Windows. And if you are a Linux user, then you can test your Windows plugs running Wine on Linux without problems.
Is a cross platform GUI library for plugins. That uses almost no code at all.
You can find out more about it here
The core concept in ikiGUI is simplicity, so it's not much to learn, and will give fewer compatibility issues with you plugins.
To compile a 64-bit Linux plugin it can be done with a command like...
gcc delay_fx.c -o plugin.so -fPIC -shared
If you want to compile 32bit linux plugins on a 64bit machine install...
sudo apt-get install gcc-multilib
...and use the -m32 flag for GCC with a command like...
gcc delay_fx.c -o plugin.so -fPIC -shared -m32
Install the needed compiler commands with...
sudo apt -y install mingw-w64
If you want a 64-bit Windows plugin compile with a command like...
x86_64-w64-mingw32-gcc delay_fx.c -o plugin.dll -fPIC -shared -lgdi32
And if you want to make 32bit Windows plugs use a command like...
i686-w64-mingw32-gcc delay_fx.c -o plugin.dll -fPIC -shared -lgdi32
MinGW-w64 can be used to compile the code on Windows. I would recommend downloading TDM-GCC and downloading the installer named tdm64-gcc-10.3.0-2.exe Then after that you should be able to compile from the CMD command prompt. You can compile with the example with a command like...
gcc delay_fx.c -o plugin.dll -fPIC -shared -lGDI32
...to make it generate the plugin .dll for you. There is also many other ways to install MinGW-w64 for making 64bit plugs. If you want a cross platform IDE for developing you can mabe try out CodeLite or Code::Blocks or EclipseIDE or use a simple editor that can run commands as you don't need any build scripts to compile this. Examples of text editors that can run the single command needed for compilation is for example Geany or Sublime Text.
The code will soon be dual-licensed for a small fee for closed source projects. More info later.