i am a little bit frustrated by C74 focusing on undertaking this huge project for Ableton users, when the current version of their own product for their own users still lacks one of the most useful and applicable features of previous versions.

I must sign this petition too…. I thought they would have sorted this out awhile ago…

As a programmer, I can also appreciate how annoying it has been to maintain support for the ever-shifting VST ‘standard’, even though I am a major pluggo user.

brad
http://music.columbia.edu/~brad

Well that makes me sad as well. But I am intrigued by these
plans Cycling is making to replace it. Can you shed some light on
the details of these new plans? Is it something beyond M4L?

Well the problem is I can not load my Max5 patches in Max4.
Presentation mode, File browser, zooming, etc. are huge
improvements and make patching easier and faster for me.
What good is a new patching environment if I can not use it?
I don’t have time to maintain two versions of a patch. To
be quite honest with you, Max5 is so nice to work in
that using Max4 is painful now.

right, that makes sense.

for some reason i was assuming that most pluggo plug-in
are only consist of 20 objects and can be (re)built in
a few minutes in max 4. but of course after more than a
year of max5 you might have a bunch of new max5 objects
and abstractions and all this plus you are used to patching
in 5.

-110

very exciting news… but….

I love this business, the software and the people but… pluggo has repeatedly shown their unfavorable side …

this really hurts.

I bought pluggo twice. developing plugins was a decent part of my business. now developing plugins isn’t even supported on my computer and still i was told pluggo would be updated. only now do i receive this unofficial rumor that the software is officially dead.

The reason people buy software is that there is an understanding and faith that it continues to function decently. thats the same reason i buy software that requires an authorization key. i have faith that the company will keep my software authorized indefinitely. people expect that if you replace one app with another, you don’t kill the first in the interim.

I’m your biggest fan. honest. One of the reasons is transparency. Having personal, continuing support from such intelligent minds is amazing. But pluggo has felt like the run-around from the beginning. Come on guys step up and say *something* officially. Im not going all zolt on ya here. Business is business but be honest!

I can understand the convenience of having Max opened up inside Ableton, but if pluggo were developed instead, one could simply convert patches to VSTs then use those VSTs within not only Ableton, but Cubase, Renoise, Digital Performer, etc. etc. With Pluggo, it wasn’t just Max 4 Live, it was Max 4 any audio application with VST support (which is a lot). M4L seems only mildly more convenient since you don’t have to convert the patch to a pluggo patch, and you don’t have to open Max. Big whoop.

I am personally responsible of 65 licenses that I would upgrade, and there is no way I am going near live for many reasons. I am certain there are a lot of us out there!

pa

oli

or should I rephrase

which is necessarily not the ideal tool for most users…

pa

Live is really not my cup of tea.

Nevertheless, i’ve planned to buy it anyway with m4l, because it seems c74 has chosen Ableton to give us a timeline, instead of building a new one.

But it won’t help people who *need* to work with other workstations, *with* their pluggos…

f.e

For the short term the solution will certainly be restricted to Max and Live. But in the long run it may evolve to a new standard format for integration of different audio applications in general.

However I still hope Pluggo for Max 5 will come in a decently close future. Qui vivra verra…

oli

Me too guys.

Dan

“Another thing that won’t work is Pluggo plug-ins based on Max 4. These will need to be converted to a new format based on Max 5. Unfortunately, this new format is unlikely to be ready when Max 5 is first released. If your life revolves around plug-in development, you’ll probably want to wait to upgrade until we change our plug-in support to work with the new core environment.”

By using the term “unlikely”, it made it seem like pluggo was right around the corner for Max 5, that it might even be possible it would be released when Max 5 was released. Could someone from C74 please explain why it has been so time consuming to develop pluggo for Max 5 and why you are now ditching it all together (much to the frustration of a large amount of your users)?

I also read this article http://www.cycling74.com/story/2009/1/15/112631/799 to better understand why M4L is so much better than pluggo. To me, it seems that with M4L you’ll be able to use Max inside Ableton to manipulate and synthesize audio and to manipulate and generate midi information………this is different from using patches as VSTs in what way exactly? Oh – Max is now “inside” Ableton…..so what?