Forums > MaxMSP

Pluggo in Max 4

September 22, 2013 | 2:58 pm

Hello patchers!
I just got back to Max4.6 exclusively to create a few plugins but I have no experience with pluggo as of today and I thought some of you might!

a) In the manual it keeps mentioning about RTAS but in fact you can only export VST. Am I missing something?

b) Is there a way to make a "side-chain" with pluggo?

c) The manual says that you can test you plugins out without going to a DAW everytime, but I don’t get it!

Any help would be very appreciated!
Thanks!


September 22, 2013 | 7:09 pm

i am still using and building those, too.

a)
it is both. same plug-ins and same runtime installer, but works as AU/VST/RTAS.

b)
not directly. but using [plugsend~], a plug-in replacement for [send~], you can send audio from one plug-in to another.

c)
actually i cant rememerb how that worked, i think in maxmsp v 460 you shoould actually be able to open them with the vst~ object.

but why do you want to do this?

for testing audio and messages, parameters and programs, you can do that just fine with the uncompiled plug-in patch.

otoh, for testing complicated GUI stuff, parameter automation or inter-plug-in audio communication such as required for your sidechain, you should really test this in the host program where you need it to work later.
these things can be host program dependent, and stuff eventually works differently from program to program.

p.s. sending audio between plug-ins is not easy. logic audio 5-6 for example might totally freak out when pluggo is trying to do that. other programs might cripple the buffer between plug-ins when you jump in the song position. it generally works, but handle with care and dont expect someone helping you.

with everything else i will be glad to help. ;)

-110


September 22, 2013 | 10:39 pm

Thank you Roman!

My main goal is to build RTAS for now. How would you export them in order to use them into PT?


September 23, 2013 | 1:02 am

Build your plug-in as if it were a vst and drop it into your vst/Pluggo folder, then run the plug scanner app that’s in the Pluggo dev folder – I can’t remember it’s name and I’m not at my Max 4/Pluggo machine right now, but it will scan your Pluggo folder and make them available to Pro Tools.
Depending on your version of Pro Tools, you should then be able to access from within PT – it’s still working in PT 9, but I can’t speak for 10 or 11,
Cheers
Roger


September 23, 2013 | 1:30 am

Thanks Roger it makes a lot more sense now!

I got the problem solved. The readme said I was going to find the AudioUnit Scan in the Pluggo folder, but it installed it in the main Applications one (Mac).

Cheers,
Tazio


September 23, 2013 | 7:48 am

u should consider to use the left and right channels for sidechaining, use a second copy of the pluggo for the other channel, and move the tracks in protools likewise. also only a workaround, but without any latency and stutter issue risks.


September 23, 2013 | 12:45 pm

Good thinking Roman!!


September 24, 2013 | 1:41 am

It works like a charm! :)
I noticed that my plugin is listed in the AudioSuites list too, but sadly it didn’t work… PT prompted me an I/O error -36.
I’d be awesome to have AS but the RTAS are already gold for me.


September 24, 2013 | 3:16 am

As a matter of interest, what version of PT are you using?
I seem to remember that I was having some weirdness with AS versions in PT9 – I think only the first plug in the menu would load, or something like that…
Good to know there are others still flying the flag for Pluggo!
Cheers
Roger


September 24, 2013 | 9:32 am

PT9 but it was the only AS of the list!

Cheers


September 24, 2013 | 10:07 am

now that cycling decided to totally kill the pluggo forums (it was online for several years but not linked from anywhere) i should maybe start to catch sheeps for my sect at yahoogroups? ;)


Viewing 11 posts - 1 through 11 (of 11 total)