Rodrigo

So I've lost touch with MaxMSP since Max5 came out.

Now, due to being back in school, I'm getting back into the idea of using it.

Before 'quitting' I had been using Max 4.6, and Hipno, to handle the processing side of things.

From what I've read, Pluggo is no longer supported by Max5, but I'm not sure what that means.

I'm not looking to create plugins, or alter/edit plugins etc...

Is it possible to simply load a Hipno vst plugin, into Max5 vst~ ? Or any other way for that matter(inside MaxforLive?)

I really like the sound of those plugins, and they weren't exactly cheap, so it would be very unfortunate to not be able to use them, other than in Logic or whatnot.

So I've lost touch with MaxMSP since Max5 came out. 

Now, due to being back in school, I'm getting back into the idea of using it. 

Before 'quitting' I had been using Max 4.6, and Hipno, to handle the processing side of things. 

From what I've read, Pluggo is no longer supported by Max5, but I'm not sure what that means.
I'm not looking to create plugins, or alter/edit plugins etc... 

Is it possible to simply load a Hipno vst plugin, into Max5 vst~ ? Or any other way for that matter(inside MaxforLive?)
I really like the sound of those plugins, and they weren't exactly cheap, so it would be very unfortunate to not be able to use them, other than in Logic or whatnot.


anyway-to-usehear-hipno-plugins-in-max-what-does-not-supported-mean

As I understand it , it is the Max5 changes for MaxForLive that were the final straw that broke the (Pluggo) Hipno's camels back. So, no not in MaxForLive.. unless they are completely re-coded for the new environment.

Same for all the pluggos, pluggo packages: the most popular of the pluggo plugs were ported to MaxForLive , and there was a discount in purchasing MaxForLive to owners of pluggo packages (I owned all, got the same discount as owners of Hipno). Hipno seemed to involve a lot of proprietary extenals code..the wild ui surfaces, etc. I suspect a lot could be ported to MaxForLive, or implemented in some other environment (AU, VST3), but *I* don't have the seed money to get the devs freed up enough to do this, and I would bet that even if they want to do it, they need to work on things with more solid returns than porting their old set of plugins, hoping that they sell *better* this time, only without a larger company (c74) managing the sales/promotion.

Sorry, i miss 'em too..Got all that running on my older system with osX10.4 and MaxMsp 4.6... I just need to fix that silly power supply that cuts off after an hour or two...it's only a 10 yo computer,;).

Same for all the pluggos, pluggo packages: the most popular of the pluggo plugs were ported to MaxForLive , and there was a discount in purchasing MaxForLive to owners of pluggo packages (I owned all, got the same discount as owners of Hipno). Hipno seemed to involve a lot of proprietary extenals code..the wild ui surfaces, etc. I suspect a lot could be ported to MaxForLive, or implemented in some other environment (AU, VST3), but *I* don't have the seed money to get the devs freed up enough to do this, and I would bet that even if they want to do it, they need to work on things with more solid returns than porting their old set of plugins, hoping that they sell *better* this time, only without a larger company (c74) managing the sales/promotion.
Sorry, i miss 'em too..Got all that running on my older system with osX10.4 and MaxMsp 4.6... I just need to fix that silly power supply that cuts off after an hour or two...it's only a 10 yo computer,;).
just my tuppence, ymmv, pax, l&k,
good luck!
Charlie


I thought the whole point of pluggo was that it created self standing plugins.

So there's no way to use Hipno (or any pluggo) with any current C74 product at all?

it means that you can not host pluggo plug-ins in vst~in max5, that was only possible

between 4.5-4.6, older and newer versions of max do not support it.

it means that you can not host pluggo plug-ins in vst~in max5, that was only possible
between 4.5-4.6, older and newer versions of max do not support it.


http://www.youtube.com/watch?v=8TQ_f1wmq0U

Oooh, I wonder how long that will last before the stop supporting it too?!

Plugtastic is still in development, based on the open-source Jamoma Foundation, Jamoma Graph, Jamoma DSP and Jamoma Audio Graph frameworks. When building using Plugtastic, you get a plugin built using Xcode and C++, and the compiled version will be entirely independent of MaxMSP, while depending on the Jamoma Frameworks.

Cool stuff Trond. Are you and Tim planning to support any custom GUI in the compiled plugin? Also any plans for cross platform support (e.g. VST on Windows)?

Cool stuff Trond.  Are you and Tim planning to support any custom GUI in the compiled plugin?  Also any plans for cross platform support (e.g. VST on Windows)?

i just listened to kr0p3r0m-a9ff_trk-38.0.5.mp3 it sound s bit like 110 on plugtastic. :D

While Trond has been incredibly supportive and insightful, he is also a bit of an innocent bystander. So if something here stinks, you have to blame me and not get upset at Trond :-).

My plan for Plugtastic is to take one small step at a time in an iterative process. If the AudioUnit with a generic interface is successful enough to pay for more development, then we can take another step and do a custom UI. If that is successful enough to pay for more development, then we can look at VST, etc.

Hopefully, this approach will prevent me from getting in over my head with support etc.

You specifically ask about VST on Windows. To do that I would probably need to hire someone, so the required success of the other steps is substantial. FWIW, I'm updating my progress on development using the 74objects twitter feed @ 

While Trond has been incredibly supportive and insightful, he is also a bit of an innocent bystander.  So if something here stinks, you have to blame me and not get upset at Trond :-).

My plan for Plugtastic is to take one small step at a time in an iterative process.  If the AudioUnit with a generic interface is successful enough to pay for more development, then we can take another step and do a custom UI.  If that is successful enough to pay for more development, then we can look at VST, etc.

You specifically ask about VST on Windows.  To do that I would probably need to hire someone, so the required success of the other steps is substantial.  FWIW, I'm updating my progress on development using the 74objects twitter feed @ http://twitter.com/74objects

Thanks Tim - well here's one person that's rooting for you!! Thanks re: the Twitter feed - unfortunately I'm not much of a Twitterer....

Thanks Tim - well here's one person that's rooting for you!!  Thanks re: the Twitter feed - unfortunately I'm not much of a Twitterer....


since we all love to have these objects, why don't you give people a site where we can make a donation for those projects. It might generate some steam for it.

Hi Tim,
since we all love to have these objects, why don't you give people a site where we can make a donation for those projects. It might generate some steam for it.


Anyway to use/hear Hipno plugins in Max? (what does "not supported" mean)