Would putting plugs on a separate drive improve anything

[evilstudios]

Would putting plugs on a separate drive improve anything.

I have never heard of anybody trying this but there must be somebody who has. Would this help especially with high tack and plugin count sessions.

[Southsidemusic]

Plugins should never be moved from the OS system drive and you would have to move the plugin folders and there is no way to point to new locations for Pro Tools, also why on earth would you do this? If you have issues with your system there are other ways to improve than messing with plugin locations

Christopher

[Becharax]

Only sample libraries .... Structure, Kontakt, Omnisphere etc ... will provide you with a boost when placing them on a separate drive

[Shan]

Originally Posted by evilstudios

Would putting plugs on a separate drive improve anything.

I have never heard of anybody trying this but there must be somebody who has. Would this help especially with high tack and plugin count sessions.

It's best to keep everything in their default location. Samples for VI's are fine on a separate drive, as mentioned above. I've done many experiments with VI's and RAM disks back in the day. There were subtle benefits, but these sorts of things don't need to be done with the new audio engine. As far as regular plug-ins like eq, comps etc, just keep them where they are.

Shane

[evilstudios]

I thought it might help the automation to dense warnings because having the plugs on a different drive would be one less task for the system drive to process.
I have not tried it yet and it doesn't seem as though anybody favours the idea so Im not going to if nobody thinks it will improve the performance of my system.
thank you.

[Darryl Ramm]

Nope, totally irrelevant.

The plugin parts that live in the plugin folders all get read and loaded into memory at Pro Tools startup. And they need to be where they are. And nothing happens with their disk images after that, wether automation is involved or not.

If you are having a specific problem with automation, start a new thread with a relevant title, describe your system carefully (after reading the "Help Us Help You....") link above and clearly describe what you are automating and when the error happens and how to reproduce the problem if you know and what trouble shooting steps you have tried. If this only happens with specific plugins etc. then that is a very useful clue. Temporarily moving all third party plugins out of their plugin folders and seeing if this problem still happens may be a useful test. Searching DUC and Google for your specific error message is often helpful.

[evilstudios]

I just wanted to know if any person has actually tried this with good results.

[Craig F]

back up your system and try it, or not

[Darryl Ramm]

Or repeatedly hit yourself in the head with a hammer. That may help improve things as well, it is unclear, and I can't find anybody who has tried that already--so how do we know if it will help or not? Just lots of folks who seem confident it's the wrong thing and not worth trying...

[evilstudios]

Ill try it on you first