[pluggo] Re: Problem with Audiounit Scan
Ben Bracken
ben at cycling74.com
Thu May 29 11:10:16 MDT 2008
- Previous message: [pluggo] Re: Problem with Audiounit Scan
- Next message: [pluggo] Max5 Pluggo runtime suggestion...
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Edo,
We have tested on our system with a 500+ plug-ins and not been able to
duplicate this problem. There is a Pro Tools 7.4 specific issue with
certain plug-in combinations, but this does not affect AudioUnit Scan.
The first thing I would suggest is to make sure that all of your
Pluggo-based plug-ins are compatible with the latest version of Pluggo,
3.6.1. If you have older Pluggo based plug-ins floating around that
were not compiled with Max/MSP 4.6+, this will cause problems. If you
don't know, please contact these third party developers to see if they
offer Pluggo 3.6.1 (UB) compatible versions.
If you are getting errors that relate to duplicate plug-ins being
scanned, this means that there is a pluggo uniqueid being used more than
once. Again, you will need to contact the third party developer for
support regarding this.
What it boils down to is that if all of the Cycling '74 Pluggo-based
plug-ins are working fine when other plugs are not present, it means
that there is a conflict with the third party plugs you are using. For
example, Capsella requires an additional support framework to be
installed, so make sure you have all of the extra bits for these.
-Ben
Cycling '74 Support
edo wrote:
> Hello!
>
> I just want to see if anyone has any hint to resolve my problem that lasts since I installed Pluggo, almost 1 year ago...
>
> It seems that the Audiounit Scan process has a limit to the number of VST Pluggos that can be wrapped. I have Pluggo and Hypno (latest versions) and if I add some Pluggo based plugins from other developers (Daevl.Makr, capsella, audioo etc.), the last in the list are not wrapped at all. I noticed that the exclusion is based on alphabetical order: if I put a "Z" before the "Pluggo" name of the folder, than some of the plugs contained in that folder (the ones with name starting with "W" "X" "Z") will be excluded. The same apply if I put a "Z" in front of the "audioo" name ("Z audioo"): then the plugs contained in the "Z audioo" folder won't be wrapped.
> My system: Dual G5 2,7, OSX 10.4.8, Pluggo 3.6.1, Hipno 1.1.1, Max/MSP 4.6.3, Jitter 1.6.3.
>
> I made infinite try-outs, trying all possible combinations. All I can say is that it seems to me that there is a limit to the number of the VST Pluggos than can be wrapped: this number seems to be 246.
>
> Recently I bought Mode and guess what? Adding the Mode plug-ins cut other plug-ins that before could be wrapped. I take the Mode folder out of the VST folder and voila, those plugs are wrapped again! But if I call the Mode folder "Zode", so that it is the last folder containing pluggo plug-ins to be scanned, the plugs contained are not wrapped.
>
- Previous message: [pluggo] Re: Problem with Audiounit Scan
- Next message: [pluggo] Max5 Pluggo runtime suggestion...
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
