Protools plugin installation problem
I am having trouble building an automated installation for my plugin.
My target is Protools systems running OS X that have not had Max/MSP installed.
I first installed the Pluggo runtime 3.5.3 package. Then I installed my package which installs my custom external to /Library/Application Support/Cycling ’74/externals and my plugin to /Library/Audio/Plug-Ins/VST/Pluggo. Inspected the result, all files installed as expected. However, when running Protools, the plugin did not appear on the list.
Using finder, I copied the plugin to /Library/Audio/Plug-Ins/VST and the plugin was visible. So I altered my installation package to install the plugin to both /Library/Audio/Plug-Ins/VST/Pluggo and /Library/Audio/Plug-Ins/VST. However, after running the install the plugin still does not appear on the Protools list until I copy the plugin to /Library/Audio/Plug-Ins/VST using Finder. The package installed copy of the same file in the same location is not sufficient. The copy must be done in Finder ; "cp" at the terminal prompt does not do the trick.
My failure unit is running Protools 6.4 under OS X 10.3.9.
Any recommendations for installing a plugin so Protools will see it without the manual user operation?
I personally don’t do much work with pluggo development and perhaps
one of the other developers like David or Tim could comment better,
but given your problem description, a quick guess is that you may be
losing an important resource fork somewhere along the way. One quick
test would be to try the resource fork capable CpMac in place of cp.
This is part of the developer tools however, so it might not be a
viable option for deploying on user machines. Off the top of my head,
I can’t remember how to accomplish this in the absence of CpMac, but
I’m sure if you look online, you’ll find some solution.
Btw, under OS X 10.4, apple finally decided to make the standard cp
preserve resource forks. So it is a non-issue for users with Tiger
(doesn’t help much for those running Panther).
The ditto command line have a -rscr flag which preserve resource
forks. It was present from 10.1 (maybe before, but I can’t remember).
Thanks all for your assistance. We have a winner.
Adding a postflight script to my package to recopy the plugin and external
using "sudo ditto -rsrcFork" seems to have done the trick.
I’ll be trying it on other systems to be sure.