Pluggo unPlugged

CJ Miller · Joined: Jan 07, 2007 Posts: 371 Location: 127.0.0.1

http://www.cycling74.com/story/2009/5/14/101259/594

C74 have decided to no longer offer Pluggo, Mode, Hipno, and Upmix. Anybody who has been waiting for Pluggo support in Max5 would tell you that there must be issues here. Anyway, DavidZ says that stuffing a Max/MSP runtime environment into people's plugin architectures has been a headache, and only getting worse with VST3 on the scene.

As many have likely heard, C74 are focussing their efforts on Max for Live, which offers a similar - but far more integrated - idea for users of Ableton Live 8. Personally I do not enjoy loop-based production, so I am probably not going to bother with Live 8. But M4L might just induce me to try it again, last version I tried was IIR Live 5.

This whole Pluggo situation does not affect me too much. I still use Max 4.1 (with Nato!) in OS9 and 4.5. I have yet to make the leap to Max5, and even when I do I will still have "frozen" systems for using older externals and libraries. Still, it did come as a shock.

moodchannel · Joined: Jun 11, 2009 Posts: 22 Location: new york city

I think this sucks... because max 5 is far superior of a user experience when patching. I think they should have disclosed this at the time of the upgrade that pluggo was *never* going to be upgraded.

max for live is great... for live users. for me all it does is eliminate pluggo... which was a functionality I was specifically waiting to be upgraded.

I would even be happy if they charged for pluggo building capability separately!

parasitk · Joined: Sep 21, 2008 Posts: 69 Location: NYC

I'm pretty bummed about this as well, as I'm a big Pluggo user. I use Live to a couple specific things, but quite irregularly. Max For Live is kinda useless to me. I was just starting to get into Max/MSP as well. Sad

BobTheDog · Posted: Mon Jun 15, 2009 5:15 am Post subject:

Well I use Live and am still pissed off, not much use for my Logic work is it!

EdisonRex · Posted: Mon Jun 15, 2009 6:15 am Post subject:

I have Pluggo and Hipno and use many of the plugins regularly under DP6. I've had a lot of issues with Max5 in general, and haven't been using it as much as a result. Most of my programs haven't been clean ports. Which kinda sucks for me since I paid for the upgrade and am still running Max/MSP 4x.

Sigh. At least this explains part of my problems with it.

BobTheDog · Posted: Mon Jun 15, 2009 7:37 am Post subject:

Its the same for vst development in Max, stuck with 4.

CJ Miller · Joined: Jan 07, 2007 Posts: 371 Location: 127.0.0.1

It is unfortunate... I know that there is a bit of marketing and/or philosophy behind their decision, but I think that they really did spend some time trying to bring Pluggo to Max5. But after a while they gave up.

I do not mind having frozen systems! I can run the latest and that does not prevent me from still using old setups. Yes, I'd love to try Pluggo in Max5. But I actually do most of my Max work in v4.1 (MacOS 9.2.2), with Pluggo, NATO, and lots of other old apps. Even though I prefer X I just never time to update the way I work. Sometime I was going to update to Max5/Jitter and I wanted Pluggo to come along. Still, I'll plug along using it with Max4.1 and Logic 6.4

GovernorSilver · Posted: Wed Aug 05, 2009 1:11 pm Post subject:

I've been out of the loop for a while when it comes to Max... So you can't make a Max patch that runs as an AU plugin in Logic?

BobTheDog · Posted: Wed Aug 05, 2009 11:00 pm Post subject:

Max 4 can (With pluggo runtime installed on target machine), Max 5 can't.

GovernorSilver · Posted: Thu Aug 06, 2009 12:58 pm Post subject:

Shame about that. I will continue to wait to upgrade from my Max/MSP version 3 license.