my first vst plugin! a simple svf (state variable filter) lowpass, highpass, bandpass, notch for testing purposes mainly i would like to hear if there's any problems with the code! if it works in various hosts, if the win32 version is ok, etc.. axonlib, my app/vst framework is (or should be) portable and cross-compileable (the .dll is compiled for win32 from within linux with mingw32) but, as i don't have windows, i can't test it in it's native environment. there's been years since i've done any serious coding in windows, and almost nothing in linux, so i had ro re-learn everything, almost from scratch. both platforms.. and no external libs or frameworks is used, plain gdi/xlib only it seems to work as intended in wine, though. (how 'true' is wine, by the way?) 32-bit: windows: (130kb) linux: (109kb) when i have ironed out the most obvious bugs and issues, and finished the small final details, i will release it (framework, plugins, apps) as opensource, and start converting all my JS plugins to vst (win32/linux) - ccernn

Appears to be working under Reaper x86 in Windows 7/64 bit.

Played with it (automation, presets,... XP only) => works fine

First, very usable GUI. Now the nitpicks...Frequency as a 1 and the decimal fractions doesn't make a whole lot of sense. Am getting very harsh, almost feedback, sounds when using the modes badpass, highpass, and lowpass in the lower bandwidths around 0-30. Overall, if you can either iron those things out or limit the bandwidth from 100-30 to avoid those sound, it is a nice filter to work with.

new test 

some warnings: Mingw/GCC 3.4.2 Code:

Just some minor things (only regarding the code) that I noticed while quickly glazing at the code. For one the fact that there a lot of semicolons after function declarations, which shouldn't be there, though many compilers ignore it, while it is against the ISO (ANSI too(?)) standard as far as I know, so that could lead to problems when porting to different platforms/compile systems (just try compiling with gcc and the -pedantic flag on and it should give you an error for every semicolon where there shouldn't be one). Next thing I noticed were the datatype #defines in axDefines.h, while those defines will work on (most) 32bit systems they will be wrong on others and especially on 64bit systems, so why not use stdint.h's datatype defines for those, like: Code:

screenshot 

a little 'teaser' screenshot might indicate where we're heading... - ccernn

screenshot.png