Re:license question
2011/08/05 14:47:32
(permalink)
Thanks Scott. Good to know.
May I ask you another question directly, as you sure have a lot of experience?
On my main machine, I have a dedicated music drive "G:". On this drive, my cubase/sonar/reaper projects reside, as well as the audio/midi file library, and a folder "VST2 Plugins\Native", with subfolder "VST2 x32" and "VST2 x64", which both have subfolders per vendor etc...
I use jBridge and automap.
First I automap every x32-plugin, the copy all "*(Automap).dll"s over to a folder "VST2 PlugIns\(DAW)\!untested" (for each Cubase, Sonar and Reaper). The same goes with x64-plugins, which overwrite the equally named x32-plug. I delete unequally named but equal x32-plugs (like "Typrell.dll", and "Tyrell(x64).dll", and then run jBridge to Bridge x32-only-plugs to x64 with the same folder.
After testing, I sort the automap and corresponding jBridge dlls to categorized folder "VST2 PlugIns\(DAW)\(category)\..."
However, it's a lot of work, but it paid so far.
So, I have a folder "G:\Library\VST2 PlugIns\..." as well as a folder "G:\Library\VST2 Content", with subfolders "factory", "ThirdParty" and "User"... etc...
My question now is: What is the best way, to have plugins available on both maschines, without too much of a maintanenca hassle, like running plug-installers on both machines (where allowed), copying "dll"s of plugs without installers and mainten updates....
I thought I'd just make the G:\ network available and bind it on the second machine?
How do others do such things?