-
Welcome to the General Discussion forum for UAD users! Please note that this forum is user-run, although we're thrilled to have so much contribution from Drew, Will, and other UA folks! Feel free to discuss both UAD and non-UAD related subjects! 1) Please do not post technical issues here. Please use our UAD Support Forums instead. 2) Please do not post complaints here. Use the Unrest Forum instead. They have no place in the the General Discussion forum. Threads posted in the wrong forum will be moved, so if you don't see your thread here anymore, please look in the correct forum. Lastly, please be respectful.
Big Secret
- Thread starter Yiannis
- Start date
Actually it isn't DP 4.6 per se that caused the problem with our MISO plugins, it was the MAS AU Support bundle that was installed with 4.6 (which is v1.4). Check to see if you are using that version of MAS AU support.bundle (located in /Library/Audio/Plugins/MAS/).Yiannis said:
If you run the 4.6 installer again it will install 1.4 and you'll see the AU presets but have the MISO problem with UAD-1 v3.9.They have a bundle which acts like a \"translator shell\" for the AU plugins. To DP's defense it actually works quite well and it technically isn't like other wrappers where a new plugin file is actually created and referenced separately that the original. \"Wrapping\" has gotten a bad rap since in the beginning most wrappers worked very poorly which really isn't the case anymore.
I'm sure MOTU's wrapper works satisfactory, but wrapping is not a good idea if one is interrested in having a optimal enviroment.
A wrapper will always, by it's nature, add overhead. Even though I know examples where the wrapper itself is pretty impressive, the overhead will still always add up depending on how many plugins one wants to use. In the end that could mean the difference between a plugin or two or sometimes even more.
A wrapper will always, by it's nature, add overhead. Even though I know examples where the wrapper itself is pretty impressive, the overhead will still always add up depending on how many plugins one wants to use. In the end that could mean the difference between a plugin or two or sometimes even more.
Yikes. You couldn't have picked a worse canidate to bring forward. :wink:
I'm afraid you're quite mistaken. Waves have had tons of performance and compbalitity issues and their wrapper have been the centerpoint of discussions all over different forums. Nuendo/Cubase SX users had it particularly bad some time ago.
I remember reading about people pulling their hear out because of Waves' choice not to do actual VST plugins. I could never figoure out how they could charge as much for wrapped plugins in the first place; I'll be the first to admit I think Waves plugins are abit overrated. But that's an entire different discussion and one that have been covered by many people before.
Another thing I might add is that I don't feel comfortable having to wait for a 4th party to supply me with the additional code I need to eg. make plugins compatible with the latest AU or VST standard. Such should always be the responsibility of the plugin developers themselves.
I'm afraid you're quite mistaken. Waves have had tons of performance and compbalitity issues and their wrapper have been the centerpoint of discussions all over different forums. Nuendo/Cubase SX users had it particularly bad some time ago.
I remember reading about people pulling their hear out because of Waves' choice not to do actual VST plugins. I could never figoure out how they could charge as much for wrapped plugins in the first place; I'll be the first to admit I think Waves plugins are abit overrated. But that's an entire different discussion and one that have been covered by many people before.
Another thing I might add is that I don't feel comfortable having to wait for a 4th party to supply me with the additional code I need to eg. make plugins compatible with the latest AU or VST standard. Such should always be the responsibility of the plugin developers themselves.