Which VST SDK version and GUI framework should I learn and use?
-
- KVRer
- 5 posts since 6 Oct, 2005
I have not been active in music software for a long time but am considering doing so now. I wrote lot's of MIDI and DSP related code in the old days before VST.
Which VST SDK version should I develop with at this time for commercial products? Will I have compatibility problems if I develop in VST 3.x?
Which cross platform GUI framework should I spend time learning?
--Bob Hoke
Which VST SDK version should I develop with at this time for commercial products? Will I have compatibility problems if I develop in VST 3.x?
Which cross platform GUI framework should I spend time learning?
--Bob Hoke
Bob Hoke
-
- KVRist
- 128 posts since 15 Aug, 2012 from Western Australia
VST SDK 2.4 is more well supported with more resources. Try RackAFX?
- KVRian
- 509 posts since 1 May, 2006 from lancaster, pa
I like tools like Juce and WDL/IPlug. They allow you to write once, and deploy on multiple targets. I personally use WDL/IPlug because it is free for closed-source development. You can take look at it here(http://www.cockos.com/wdl/). Juce (http://rawmaterialsoftware.com/juce.php) is very popular and has an active community. For open-sourced projects it is free. For closed source, it costs.
I guess it is a trade-off. Juce costs for closed-source, but there is a lot of support. WDL/IPlug has a smaller community, but it is free.
...incidentally, the version that I am using (WDL-OL) can deploy on VST2 and VST3, as well as AU, RTAS, and others. I also agree that for now, VST2 is still more wide-spread.
I guess it is a trade-off. Juce costs for closed-source, but there is a lot of support. WDL/IPlug has a smaller community, but it is free.
...incidentally, the version that I am using (WDL-OL) can deploy on VST2 and VST3, as well as AU, RTAS, and others. I also agree that for now, VST2 is still more wide-spread.
-
AdmiralQuality AdmiralQuality https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=83902
- Banned
- 6657 posts since 10 Oct, 2005 from Toronto, Canada
IMHO, VSTSDK 2.4 and VSTGUI 3.6 (RC2) from here...
http://sourceforge.net/projects/vstgui/ ... GUI%203.6/
http://sourceforge.net/projects/vstgui/ ... GUI%203.6/
-
- KVRist
- 231 posts since 15 Apr, 2012 from Toronto, ON
Why not VSTGUI 4? Given the problems you're having with 3.6 on OS X, wouldn't 4 be better to start with? It works perfectly fine for me in both OS X (UB, 32-bit/64-bit, and Windows).AdmiralQuality wrote:IMHO, VSTSDK 2.4 and VSTGUI 3.6 (RC2) from here...
http://sourceforge.net/projects/vstgui/ ... GUI%203.6/
-
AdmiralQuality AdmiralQuality https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=83902
- Banned
- 6657 posts since 10 Oct, 2005 from Toronto, Canada
I'm not having any problems with 3.6. Once I switched to RC2 the tutorial example compiled fine for all platforms. I didn't have to change a thing.LemonLime wrote:Why not VSTGUI 4? Given the problems you're having with 3.6 on OS X, wouldn't 4 be better to start with? It works perfectly fine for me in both OS X (UB, 32-bit/64-bit, and Windows).AdmiralQuality wrote:IMHO, VSTSDK 2.4 and VSTGUI 3.6 (RC2) from here...
http://sourceforge.net/projects/vstgui/ ... GUI%203.6/
I do however have a bunch of custom controls that were subclassed from an earlier version of 3.6 that don't seem to work with the VSTGUI deprecations disabled (which apparently we need to make 3.6 work with OSX x64). So in MY case I have months of coding and years of testing that I have to consider throwing away and starting over on. Not a problem for the OP or anyone else though.
As for VSTGUI 4, I still see lots of people having lots of problems with it on the mailing list. And my first attempts were very discouraging as well. You feel it's ready for prime time?
-
- KVRist
- 231 posts since 15 Apr, 2012 from Toronto, ON
Oh ok. Good thing you got that figured out. Bummer about having to possibly start over after all that testing though.AdmiralQuality wrote:I'm not having any problems with 3.6. Once I switched to RC2 the tutorial example compiled fine for all platforms. I didn't have to change a thing.LemonLime wrote:Why not VSTGUI 4? Given the problems you're having with 3.6 on OS X, wouldn't 4 be better to start with? It works perfectly fine for me in both OS X (UB, 32-bit/64-bit, and Windows).AdmiralQuality wrote:IMHO, VSTSDK 2.4 and VSTGUI 3.6 (RC2) from here...
http://sourceforge.net/projects/vstgui/ ... GUI%203.6/
I do however have a bunch of custom controls that were subclassed from an earlier version of 3.6 that don't seem to work with the VSTGUI deprecations disabled (which apparently we need to make 3.6 work with OSX x64). So in MY case I have months of coding and years of testing that I have to consider throwing away and starting over on. Not a problem for the OP or anyone else though.
As for VSTGUI 4, I still see lots of people having lots of problems with it on the mailing list. And my first attempts were very discouraging as well. You feel it's ready for prime time?
I've noticed that too on the mailing list regarding VSTGUI 4. Still, I have had few issues with it. Admittedly, I haven't gone super complex with my GUIs yet, but considering it's still in version 4.0.1, perhaps 3.6 is the safer bet for now.
-
AdmiralQuality AdmiralQuality https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=83902
- Banned
- 6657 posts since 10 Oct, 2005 from Toronto, Canada
I'm working on some other things at the moment that don't require Poly-Ana's fancy knobs, so I'm quite good with VST 2.4/VSTGUI 3.5(RC2). It's a huge relief to finally have a project that compiles for all 4 platforms. (In fact 6 as I've added Symbiosis to it to make AU!)
I now have a template that's going to make new product development VERY rapid. I'm excited! Platform schism has been a huge headache for years, will be wonderful to leave that behind. (Now watch Apple break everything next week.
-
- KVRist
- 290 posts since 20 Jul, 2009 from Helsinki, Finland
Hello,
I remember you were building with Xcode 3.x, i'm on Xcode 4. Now i'm trying with older Base SDKs. Could you tell me which OS X SDK version you managed to build the tutorial against please? Which compiler you are using?
I'm trying to build 32-bit VSTi OS X version using VST SDK 2.4 rev 2 and VSTGUI 3.6. With VSTGUI i've tried both the latest from SVN and RC2, neither links.AdmiralQuality wrote:I'm not having any problems with 3.6. Once I switched to RC2 the tutorial example compiled fine for all platforms. I didn't have to change a thing.
- KVRian
- 1184 posts since 24 Feb, 2012
mfa wrote:Hello,
I'm trying to build 32-bit VSTi OS X version using VST SDK 2.4 rev 2 and VSTGUI 3.6. With VSTGUI i've tried both the latest from SVN and RC2, neither links.AdmiralQuality wrote:I'm not having any problems with 3.6. Once I switched to RC2 the tutorial example compiled fine for all platforms. I didn't have to change a thing.I remember you were building with Xcode 3.x, i'm on Xcode 4. Now i'm trying with older Base SDKs. Could you tell me which OS X SDK version you managed to build the tutorial against please? Which compiler you are using?
I recommend you to download juce, build the introjucer and create projects to taste. You'll have a working VST/AU configurations for almost any development tool within seconds. Inspect these project setting, or move on with JUCE.
If it doesn't work, JUCE is FULLY documented.
Fabien from Tokyo Dawn Records
Check out my audio processors over at the Tokyo Dawn Labs!
Check out my audio processors over at the Tokyo Dawn Labs!
-
- KVRian
- 1256 posts since 15 Mar, 2007 from Yorkshire, England
I learned VST2.4 since VST 3 was not so well supported but I think now I will switch to VST 3 and use the interfaces (it now comes with) to provide 2.4 wrappers. Thing is 2.4 is troublesome!, its relatively simple but primitive and hence prone to different interpretations by Daw makers. It has a sort of hacked together feel to it. Anyway just my current thinking, once I get going with 3 I may find it is just as bad 
-
- KVRist
- 290 posts since 20 Jul, 2009 from Helsinki, Finland
Well it's tempting,FabienTDR wrote:I recommend you to download juce, build the introjucer and create projects to taste. You'll have a working VST/AU configurations for almost any development tool within seconds. Inspect these project setting, or move on with JUCE.
If it doesn't work, JUCE is FULLY documented.
Anyway, i think i'm getting my plugin working on OS X 32-bit with Base SDK version 10.5 and 10.6.
- KVRian
- 1184 posts since 24 Feb, 2012
Oh, I was only talking about the project settings. You know, just as a reference. The introjucer is always a reliable reference regarding these things, even if you don't use the JUCE lib at all.mfa wrote:Well it's tempting,FabienTDR wrote:I recommend you to download juce, build the introjucer and create projects to taste. You'll have a working VST/AU configurations for almost any development tool within seconds. Inspect these project setting, or move on with JUCE.
If it doesn't work, JUCE is FULLY documented.but as i'm developing freeware i can't pay for the closed source licence, have to stick with the free tools.
Anyway, i think i'm getting my plugin working on OS X 32-bit with Base SDK version 10.5 and 10.6.
Fabien from Tokyo Dawn Records
Check out my audio processors over at the Tokyo Dawn Labs!
Check out my audio processors over at the Tokyo Dawn Labs!
-
AdmiralQuality AdmiralQuality https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=83902
- Banned
- 6657 posts since 10 Oct, 2005 from Toronto, Canada
"Mac OS X 10.6"mfa wrote:Hello,
I'm trying to build 32-bit VSTi OS X version using VST SDK 2.4 rev 2 and VSTGUI 3.6. With VSTGUI i've tried both the latest from SVN and RC2, neither links.AdmiralQuality wrote:I'm not having any problems with 3.6. Once I switched to RC2 the tutorial example compiled fine for all platforms. I didn't have to change a thing.I remember you were building with Xcode 3.x, i'm on Xcode 4. Now i'm trying with older Base SDKs. Could you tell me which OS X SDK version you managed to build the tutorial against please? Which compiler you are using?
I think your linking problem may be some Core Audio libs they famously left out of XCode 4.
Let me know if you figure out how to get it to compile in XCode 4.x. Someday I'll need to know.

