I have uploaded my version of WDL/IPlug to github which has many enhancements.

IPlug is a liberally-licensed and simple-to-use C++ framework for developing cross platform audio plugins and targeting multiple plugin APIs. Originally developed by Cockos, IPlug has been enhanced by the myself and several other people and now builds VST2, VST3, AudioUnit and RTAS plugins. It can also produce standalone Windows/OSX audio/midi apps and apps for Apple's IOS devices, all from the same code.

more info here

http://forum.cockos.com/showthread.php?t=91811

oli

Having used it for a couple of plug-ins already and easily porting my old win plug-ins to OSX AU/VST, I can safely say this is a holy grail of plug-in coding. I've used JUCE before, and in my opinion this is even simpler to use, and the pre-made project templates are a big plus for easily deploying to different platforms. The license is also not horribly expensive (like Juce) for commercial projects. I was getting really sick of using Vst GUI as well, and this is simply better, and making some nice custom animated controls is rather fun (I'm excited about OpenGL support as well).

If you've been making VST plug-in for a while, either using only the VSTSDK or using Juce, you'll probably pick this up and start using it efficiently in no time (my only real hurdle was learning to use Xcode since I'm only really used to Windows).

I recommend trying this out.

Are you able to compile for RTAS without the SDK?

Of course not...Even if someone had figured that out, he could not distribute the results of his efforts without getting into legal problems with Avid.

Right. So absolutely no help there at all.

I would not call it "absolutely no help at all", if the RTAS support in Oli's code is at the level what JUCE offers. In that you could code your plugin so it works as VST/AU and if Avid later grants you the RTAS SDK, it wouldn't be a full effort to do the RTAS version. AAX plugins only for ProTools are around the corner anyway, though...

As far as I know, compiling for RTAS is basically a matter of copying the SDK over into the right folder and hitting compile. But as other have said, it's really up to Avid to grant you the SDK.

Right. And as they're completely useless and don't respond to our applications, we're still as dead in the water as ever.

It's alright. I doubt they're going to survive what they're about to pull on their customers. Still, I'd like to support legacy RTAS systems.

I uploaded two tutorial videos for setting up WDL-OL to build on OSX and Windows. Make sure to watch in HD, else you won't be able to read any text.

http://www.youtube.com/watch?v=POP_z0dAn9c

http://www.youtube.com/watch?v=uWitp7EOWVA

Enjoy my dulcet tones

oli
Last edited by hibrasil on Wed Jun 27, 2012 11:11 pm; edited 1 time in total

new version on the next branch with support for AAX-Native, and many other improvements.

https://github.com/olilarkin/wdl-ol/tree/next

Excellent work.
It's tempting to switch from VSTGUI to this. One thing that concerns me though is the liberal use of mutex locks in iPlug, even in processReplacing. Are they really necessary, have they caused problems in RTAS/AAX?

Well, they are necessary, but could/should be replaced with a better solution (lock-free message queue or something). One day I'd like to do that but so far I haven't had any problems

new version pushed to github with lots of improvements

Such as?

off the top of my head...

AAX Native support
parameter grouping (AU/VST3)
bus/io labelling (VST3/VST2)
multiple output busses (e.g. drumsynth) (AU/VST3)
sysex support (VST2/AU), thanks Tale
better xcode projects, sharing of precompiled headers = faster builds,
fixes in some examples, and a couple more of them
IControls can be associated with multiple parameters
IControls can display param value and param name in another (specified) control on GUI edit
better support for Xcode4 and latest apple compiler
fix key press stealing in FLStudio / S1
automatic gui maker (sliders/knobs)

for details check the git commit logs.