I want to buy a Waves plugin to use in Mulch (Windows), so I downloaded the latest Waves installer/manager software and installed the demo of the particular plugin I want to use. Waves plugins don't work with simple .dll files, it installs everything into its own folder and then puts a single .dll file into your VSTPlugins folder. All good so far, only in Mulch when I click on that WaveShell.dll to add a plugin, nothing happens. :( It is the 32 bit version, so should work.
I've hads other plugins not load in Mulch recently too, wheras it always used to be one of the best/most stable hosts that would run almost everything.
I can't speak for Windows, but only some of them work on OSX anyway... and AM being 32-bit, they are total CPU hogs. Just keep those for postproduction in your DAW of choice.
Cheers, but it's for mastering and I do all my mastering in Mulch and wanted to demo the Abbey Road Mastering suite, but it looks like it's just not gonna happen.
Also never heard of 32 bit plugs using more resources than 64 bit, is that really the case?
Nah, just talking out of my ass. You're probably right. Maybe a different story if your patches are simple, but IME using plugins in general within AM is a real CPU strain.
Cheers. It's fine foir mastering, do everything with 32 bit plugs at 24/96, but then I'm only ever working on stereo tracks, so track count is precisely, well, two... ;)
If we ever get 64 bit support and multi-thread/processor support as promised on the Mulch roadmap, we'd be sure to see CPU overhead go way down with current patches.