Which VST SDK version and GUI framework should I learn and use?

DSP, Plugin and Host development discussion.
RELATED
PRODUCTS

Post

AdmiralQuality wrote:Let me know if you figure out how to get it to compile in XCode 4.x. Someday I'll need to know.
Thanks for the reply!

The tutorial 2 in VSTGUI from SVN builds on Xcode 4.6.2 using Apple LLVM compiler 4.2. There are some modifications that need to be done though.

I needed to copy the Mac OS X 10.6 SDK into the Xcode bundle into /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs (SDKs are no longer in /Developer/SDKs). SDK 10.7 onwards fail to compile due to undefined (deprecated) symbols. I had to download 3.x Xcode installation image and extract the 10.6 SDK from the package, which included navigating into some hidden directory whose name i can't remember.

The

Code: Select all

VSTGUI_ENABLE_DEPRECATED_METHODS=0
needs to be defined as it already is in the VSTGUI tutorial.

Then i had some odd linker error

Code: Select all

Undefined symbols for architecture x86_64:
  "_OBJC_CLASS_$_NSMutableOrderedSet", referenced from:
      objc-class-ref in libarclite_macosx.a(arclite.o)
  "_OBJC_CLASS_$_NSOrderedSet", referenced from:
      objc-class-ref in libarclite_macosx.a(arclite.o)
  "_objc_autoreleasePoolPush", referenced from:
      ___ARCLite__load in libarclite_macosx.a(arclite.o)
  "_objc_retain", referenced from:
      ___ARCLite__load in libarclite_macosx.a(arclite.o)
     (maybe you meant: _objc_retainedObject)
ld: symbol(s) not found for architecture x86_64
clang: error: linker command failed with exit code 1 (use -v to see invocation)
But this got fixed by setting Implicitly Link Objective-C Runtime Support to No

That's all i had to do. I hope this will help you and others.

Post

FabienTDR wrote:
mfa wrote:
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.
Well it's tempting, :) 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. :wheee:
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.
Thanks! This is good to know.

Post

Sorry if this has been told before, but just my opinion:

VST 2.4 and JUCE. :D Still haven't seen nothing that can't be done with those two combinations ( From the DSP point of view ).

If you're on OS X, well, please let me know how you're doing with XCode 4, I am still using Xcode 3.x
Free MIDI plugins and other stuff:
https://jstuff.wordpress.com
"MIDI 2.0 is an extension of MIDI 1.0. It does not replace MIDI 1.0(...)"

Post

umd wrote:Sorry if this has been told before, but just my opinion:

VST 2.4 and JUCE. :D Still haven't seen nothing that can't be done with those two combinations ( From the DSP point of view ).

If you're on OS X, well, please let me know how you're doing with XCode 4, I am still using Xcode 3.x
Another big +1 for Juce + VST 2.4. I really don't see the point in supporting VST3, VST2.4 is pretty much universal and while there are many hosts which don't support VST3, I've yet to hear of a VST3-only host which *doesn't* support VST2.4.

As for Juce, you said that you're developing freeware plugins and don't want to pay for a license, not sure why you can't just make them open-source and use the open-source license for Juce. I never understood why people would make closed-source freeware anyways, why not just free the source as long as you're not planning to make money from it? :P

Post

umd wrote:If you're on OS X, well, please let me know how you're doing with XCode 4, I am still using Xcode 3.x
XCode 4 so far so good, but please notice that i'm building with OSX SDK 10.6 which IIRC doesn't ship with Xcode 4. VSTGUI caused some headache, notably CFileSelector, that i needed to change to use the raw extension instead of the fancy Apple UTI's for a file filter. The COptionMenu needed some tweaking too, although i've never truly understood how on earth that's supposed to work in the first place. There might have been some other minor issues, but nothing really bad. So far i've tested on Cubase, Reaper and Ableton Live.

Post

sqook wrote:As for Juce, you said that you're developing freeware plugins and don't want to pay for a license, not sure why you can't just make them open-source and use the open-source license for Juce. I never understood why people would make closed-source freeware anyways, why not just free the source as long as you're not planning to make money from it? :P
I guess it's more less the same reason as for why a magician never reveals how the trick is done. :P And the difference between having an occasional laugh at the best of the worst hacks and being constantly embarrased by them. :) Open source is absolutely wonderful but horribly serious and boring at the same time. It's an art on its own.

Post

mfa wrote:The COptionMenu needed some tweaking too, although i've never truly understood how on earth that's supposed to work in the first place.
COptionMenu works mechanically just fine straight out of the box in VSTGUI 3.6 RC 2. It's that it wants to use integer indexes in a system that otherwise wants normalized 0.0 to 1.0 float values that's the problem. (And is also a problem on Windows.) I fix it with some ugly hacks in editor::valueChanged() that fix the value before setParameterAutomated() is called.

Post Reply

Return to “DSP and Plugin Development”