eamonbrady

I have been fooling around today developing simple plugins that use the csound~ external. The plugins use csound 5's phase vocoder streaming opcodes and work fine in Ableton BUT IN PRO TOOLS only one of them gets loaded (there are 2 plugins in my pluggo plugins folder that use the csound external). The thing is it seems to load whichever plugin comes first alphabetically. Just to reiterate I dont get this problem in Ableton Live, just pro tools 7.3.1. The plugins work perfectly in Ableton; any ideas what might be causing this?

I have been fooling around today developing simple plugins that use the csound~ external. The plugins use csound 5's phase vocoder streaming opcodes and work fine in Ableton BUT IN PRO TOOLS only one of them gets loaded (there are 2 plugins in my pluggo plugins folder that use the csound external).  The thing is it seems to load whichever plugin comes first alphabetically. Just to reiterate I dont get this problem in Ableton Live, just pro tools 7.3.1. The plugins work perfectly in Ableton; any ideas what might be causing this?

pluggo-and-csound

Sounds like it could be a unique ID conflict - did you

by any chance make one plug by copying part of the

If you copied the plugconfig object, the two will

have the same ID no, and whilst this may not be such a

big deal in Live, Pro Tools doesn't like it. Making a

new instance of plugconfig should sort it out,

> I have been fooling around today developing simple

> plugins that use the csound~ external. The plugins

> use csound 5's phase vocoder streaming opcodes and

> work fine in Ableton BUT IN PRO TOOLS only one of

> them gets loaded (there are 2 plugins in my pluggo

> plugins folder that use the csound external). The

> thing is it seems to load whichever plugin comes

> first alphabetically. Just to reiterate I dont get

> this problem in Ableton Live, just pro tools 7.3.1.

> The plugins work perfectly in Ableton; any ideas

> OS X.4.8, 1Ghz G4 powerbook, maxMSP 4.6

Sounds like it could be a unique ID conflict - did you
by any chance make one plug by copying part of the
other ? 
 If you copied the plugconfig object, the two will
have the same ID no, and whilst this may not be such a
 big deal in Live, Pro Tools doesn't like it. Making a
new instance of plugconfig should sort it out,
cheers
Roger

>
> Hi there,
>
> I have been fooling around today developing simple
> plugins that use the csound~ external. The plugins
> use csound 5's phase vocoder streaming opcodes and
> work fine in Ableton BUT IN PRO TOOLS only one of
> them gets loaded (there are 2 plugins in my pluggo
> plugins folder that use the csound external).  The
> thing is it seems to load whichever plugin comes
> first alphabetically. Just to reiterate I dont get
> this problem in Ableton Live, just pro tools 7.3.1.
> The plugins work perfectly in Ableton; any ideas
> what might be causing this?
>
> thanks
>
> Eamon.
>
>
> OS X.4.8, 1Ghz G4 powerbook, maxMSP 4.6
>
>
>


Of course, silly me!! I really should have spotted that one. Thank you very much roger,

Of course, silly me!! I really should have spotted that one.  Thank you very much roger,

i think that in CS5 it is still true that the csound

i think that in CS5 it is still true that the csound
max object can not be instantiated.


 My plugins are working fine now that I altered plugconfig ID. Csound 5 has a lot of powerful new features that really compliment MSP (particularly, the PVS opcodes, I think are pretty cool!!) Anyway, thanks again

Not true anymore, go here: http://www.davixology.com/csound~.html. My plugins are working fine now that I altered plugconfig ID. Csound 5 has a lot of powerful new features that really compliment MSP (particularly, the PVS opcodes, I think are pretty cool!!) Anyway, thanks again 

i interesant you csound~ pluggos
send - please
my mail  zak@lreri.lviv.ua


thank you very much
I have
Supertrance.pat
see http://audiomasher.com/programs.html
send????????????


Pluggo and csound~