PitchSlap
02-07-2008, 11:32 AM
There are some options designed as workarounds for plugin compatibility (which I am grateful for), but sometimes it feels like I'm making global functionality sacrifices for the sake of a single plugin.
For example: 'Bypass audio while opening plug-in config window'
I would really prefer to have this off, but because ONE plugin requires it to work (Altiverb), I need to have it on.
Another example is 'Anticipative FX processing'. I need to have this option on otherwise the audio on my dual core starts crapping out around 50% CPU usage, but it also says this option should be "disabled for use with UAD plugins" which I use. A tough choice.
Basically I think that if there are options designed for compatibility with certain plugins, those options should ONLY apply to the troublesome plugins.
One solution I can think of would be to have these options in the right-click context menu for each plugin in the FX browser.
Just a thought, now back to making music... :)
For example: 'Bypass audio while opening plug-in config window'
I would really prefer to have this off, but because ONE plugin requires it to work (Altiverb), I need to have it on.
Another example is 'Anticipative FX processing'. I need to have this option on otherwise the audio on my dual core starts crapping out around 50% CPU usage, but it also says this option should be "disabled for use with UAD plugins" which I use. A tough choice.
Basically I think that if there are options designed for compatibility with certain plugins, those options should ONLY apply to the troublesome plugins.
One solution I can think of would be to have these options in the right-click context menu for each plugin in the FX browser.
Just a thought, now back to making music... :)