July 28, 2011

Workin' For A Livin'...

by Chris Randall

It's been an exciting (interesting?) couple of weeks here at Audio Damage Command And Control. Adam and I decided, for reasons that aren't entirely clear to either of us any more at this juncture, that we would finally tackle the Big Bear, and release our next product as a VST3.

The VST3 SDK was updated to a new stable release a month or so ago, and in this release is the ability to also build VST2.4 and AudioUnit, off the VST3 base plug-in. These aren't "wrapped" as such, but are the real deal, just using a different base than the VST3. They necessarily lack the extra features that VST3 has (moreso in the case of VST2.4, as AudioUnits and VST3 plugs are remarkably similar in feature-sets.) We also, since we were making such a big jump anyhow, decided to switch from VSTGUI 3.6, which we've been using since Tattoo, to VSTGUI 4.

On the Windows side of things, it was relatively (!!!) painless, but when we moved to OS X, things got pretty hairy for a while there. Yesterday morning, I was actually about to lobby for bagging the whole idea and going back to the Old Way of doing things, but as luck would have it, Adam found the Issue, which turned out to be our fault, not Steinberg's. Now the VST3 on OS X is merrily working away.

Anyhow, long story short, if you're wondering where I've been for the last few days, it was a combination of that, some legal troubles (I was arrested for doing graffiti, or "street art" as I like to call it but the police in Tempe don't, of all things), and various other demands on my time, including an iOS contract I took without, perhaps, thoroughly thinking through the ramifications of same. In that respect, the iOS contract and the arrest are remarkably similar.

Adam is on his way to Wyoming, of all places, for the next few days, which will allow me to finish the iOS thingy, and we can return to our regularly scheduled vitriol. In the mean time, this is an open thread. Questions? Comments? Criticisms?


Page 2 of 3

Jul.28.2011 @ 5:53 PM
What were you painting / on ?

iOS contract issue .... Any insight or forewarnings ?

Good luck on both . IMHO the only thing worse than the laws themselves is the lawyers that go with them .

Jul.28.2011 @ 7:04 PM
You paint w/o a lookout ?

I want to see pics.

And I hope you exercised your right to remain silent.

I got bagged in Queens about 17 years ago for the same thing.

Got clocked in the jaw by the cop said I was lucky he didnt "Bleed" me.

Adam X / Traversable Wormhole has a huge Graffiti resume.

link [www.flickr.com]@N04/

He did some work with waxtrax way back, aint you did some work with them too?

Jul.28.2011 @ 7:06 PM
That link is broke as fuck... search flickr for Vendalism's photo stream.. dude is a big influence to art and musicwise...cool as hell in person...his more famous brother is fuckin bigheaded..

Jul.28.2011 @ 7:13 PM
I wish Yamaha would make a poly AT controller to go with Cubase's Note Expression VST3 tech. Weighted 88-key controller, wooden keys, keep it under $1500 and I'm there. You can buy $10k guitars but no one makes a MIDI controller for over $300.

Jul.28.2011 @ 7:30 PM
$300? synthetic, the Haaken Continuum would like to speak with you: link [www.hakenaudio.co...]

Jul.28.2011 @ 8:02 PM
Doepfer LMK Joint me thinks is over a G.

Jul.28.2011 @ 10:12 PM
Wade Alin
I think an arrest over 40 counts for like 8 arrests under 30, so we're all even Steven now.

Jul.29.2011 @ 8:27 AM
As an iOS guy that's considering porting something over to VST, I'd love to hear more about your rationale for going to VST3. Up until now I assumed the easiest thing was VST 2.4 + Symbiosis and read nothing but invective about VST3.

Jul.29.2011 @ 10:40 AM
Chris Randall
VST3 is very difficult; it is (like all VST SDKs) hideously under-documented. On top of that, the examples provided don't make much sense.

I wouldn't recommend it for a first attempt, honestly. There is a vast pool of existing knowledge about making VSTs in the form of the two mailing list archives, KvR's DSP forums, and many open-source projects to look at. None of that exists for VST3. I couldn't, in candor, make a compelling case to start with that. The VST2.4 / VSTGUI 3.6 combination is a much better starting point.

Our rational is mainly in that we would like to future-proof our workflow. When Steinberg deprecates 2.4, we want to be able to have existing resources, rather than having to scramble like we did with 64-bit, or the Intel switch, or the VST 2.4 switch. (The latter was quite simple, fwiw.) We also want to have a single build target, and this seems to give us that.

But you gotta know plug-ins, and know how the different DAWs interact with them, to pull it off. VST3 is most assuredly an advanced format, and not a good starting place.


Jul.29.2011 @ 11:07 AM
Making it easy to build 2.4 and AU from the VST3 SDK was a smart move, they probably should have done that from the get-go to encourage early adoption.

What hosts support VST3 these days? I haven't kept up with any news of that sort.

Page 2 of 3



Sorry, commenting is closed for this blog entry.