2009
Man, I have a hard time coming up with a metaphor to start this post off. I was originally going to go with Roman mythology, where in the Pantheon of UI and DSP designers, Roger Linn was around Hercules stature, and then I closed it off with a baseball reference, and sadness and despair ensued. So I just deleted that fucker, much to the relief of historians and sports fans everywhere, and I'll begin anew:
Wow. Roger Linn releases a native plug-in. It's built using Max and requires the Pluggo runtime. It's $99. Mr. Linn, all due respect, but you're about to learn the hard way how things are out here in the bleachers.
posted October 31, 2009 by PhilTH
posted October 31, 2009 by PhilTH
I have a general sense that guitar pedal makers haven't had stellar success jumping to software. Years ago, effector13 did so for about a week, earlier this year Empress did so with a tremolo plugin to little fanfare. I imagine this one will be forgotten pretty quickly.
posted October 31, 2009 by shamann
@Anybody who will listen. I agree with ya'll that this is some foolishness on Linn's part. I personally refuse to pay period for something not hard coded in C/C++. All that synthedit shit has the same sound basically. Now Max/Msp is better than Synthedit (IMO), but this plugin just doesn't have much mojo...Like others have pointed out pluggo's future is bleak, so no long term support. Also, can't Big Seq2 do every thing this does? And with personality I might add. Closing thought, this looks like a gui from windows 95 or some shit.
posted October 31, 2009 by aeon
posted October 31, 2009 by boobs
Business aside, it's a damn shame. We've been approached by many guitar pedal manufacturers to do plug-ins of their products. We took on two very well known examples, and in both cases we didn't get much past the UI. A lot of boutique pedals rely on unstable circuit configurations, and it's really difficult to get them to work in our modeling software. But our experience in this department has shown that it's basically pointless to try and pull off the boutique pedals.
Not so for something like the Adrenalinn, which is DSP through and through. There's no earthly reason the algorithms couldn't be ported to C and hung on a nice plug-in UI; as such, there's _really_ no earthly reason to use Pluggo. I mean, making a plug-in from scratch in the era of VST2.4 and AU ain't the easiest thing in the world, but it's gotta be easier than manufacturing a hardware unit.
I ultimately feel kind of bad, because I know _exactly_ and intimately what is involved in making something like that, and to see this come out is really a drag. (Business issues aside, as I said.) I mean, I like the shiny as much as the next guy.
-CR
posted October 31, 2009 by Chris Randall
posted October 31, 2009 by chaircrusher
"We didn't include AdrenaLinn III's drumbeats, amp modeling, note-triggered filter modulation or reverb, but we figured you'd have plenty of plug-ins to do those things."
Yeah, thanks I already do have those things. Just like I already have folders full of shitty, ugly-ass vsts made in modular programming environments like max and synthedit, which I never use. I need another buggy, inexcusably cpu-heavy, wacky filter plug-in like I need a hole in my head, but thanks.
And yes, I know it's buggy and cpu-heavy, because I've never used any plug-in made in a modular environment that wasn't. It's just par for the course. The difference is, yours is $99, while my folder full of shitty synthedit plug-ins was free. Thanks though, Roger.
Aren't most of the hardware DSP boxes programmed in C or C++ these days anyway. Like Chris just said, what's so hard about just porting the code to vst? I'm sure it's not cakewalk, but they've already built the hardware for Christ's sake. It's not like this is amateur hour. I guess it's just possible for someone to be THAT clueless about things outside of their immediate industry.
posted October 31, 2009 by afreshcupofjoe
_aKido
posted October 31, 2009 by aKido
posted October 31, 2009 by bcomnes
