All of this could be easier resolved if UA would have just renamed their plugins with separate names to designate UAD1 vs UAD2 versions. The only remaining issue is whether I can create versions which are separate in Sonar 32. What a PITA, but it works and is the only way to get UAD1 plugins to load into UAD1 cards and UAD2 plugins to load into UAD2 cards in Sonar 64. This then creates renamed, for example “UAD 1176.64”, versions which are separate from the UAD 1176 (the UAD1 version).
#Uad plugins 2 plugin 64 Bit
I pulled up JBridge and created 64 bit versions of the UAD2 plugins (over twenty and you have to do this one at a time). The Sonar scanner errors out on all of the renamed plug ins. Next step was to try renaming all of the UAD2 based plugins with a different name i.e. The plug in scanner intermittently picks up that there is a difference between two plugins with the same name and registers them both. The second of the two Neve 33609s actually loaded into the UAD2 card. This time the scanner came up with two entries for Neve 33609s compressor plugins but the rest of the UAD plugins had only one entry. It was apparent that the Sonar plug in scanner cannot differentiate that these two files, with the same name, though they reside in different locations, are different. So the LA2A.dll in the UAD1 directory has the same exact name as the version in the UAD2 directory. To make matters even more so, UAD names each plugin with the same name regardless of its directory location. Next I reviewed the entries for each plug in and discovered that some in fact indicated they were located in the UAD2 directory even though they were loading into UAD 1 cards. Therefore, all of the plugins were loading to the UAD1s telling me that Sonar is only scanning and registering the UAD1 plugins. There is no set of UAD1 plugs vs UAD2plugs listed in Sonar. I was wondering how does Sonar know which of the three cards to load.
Jumping back over to Sonar I reviewed the entries in the plug in tool and there was only a single set of plugins listed for each UAD plug in, one 1176, one LA2A and so on. The first was the UAD1 folder where all of the plugins reside and below this a UAD2 folder where a duplicate set of plugins reside.
It seemed odd that only the UAD1 plugins were loading.ĭrilling down into the UAD directory I came across two subdirectories. I didn't notice under Vista if some had been loading on the UAD2 while others on the UAD1. Maybe it’s because I was loading a new OS but for the first time I noticed all of my plugins were loading only on the UAD1 cards. I installed the new UAD 5.5 drivers, downloaded the auth.
#Uad plugins 2 plugin upgrade
8.5.1 plug-in-scanner & UAD plugins My recent upgrade to Windows 7 and the challenges with going from Vista 64 to this new OS has prompted a re-examination of my perspective on UAD plugins, not to mention an awakening about the plug in tool in Sonar.įirst, I have two UAD1 cards, a PCI, a PCIe and a UAD2 Solo card.
0 kommentar(er)
