Just a question for our 3rd party devs and anyone else who wants to chime in.
I'm wondering if I should go the Nebula route or the vst acqua effects route. I don't feel like I really need Nebula and the gigs of libraries that come with it when I'm really just after a couple decent eq's, preamps, and maybe some tape.
I would much rather "limit" myself to these options and work with a nice interface.
BUT, the Acqua effects are very limited as of right know, and I don't want to start a collection only to have to turn around and buy Nebula later on because of a lack of acqua development.
So, Devs, Giancarlo - Is Acqua going anywhere, or should I steer clear. Do you plan on "acquasizing" existing libraries?
Thankyou for the helpful response. I stand by some of my prior post, but even if there are issuses with compressors and workflow, I can't deny that Nebula has one very important thing going for it - sound.
I really would like to see more 3rd party devs to customize their interface using the Acqua engine. Also, I am curious on how the Acqua engine and development utilizes shared resources, Nebula server etc. A bit more info on the matter would be nice, or maybe I missed the info somewhere?