I'm often processing my audio files offline in Cubase adding preamp, tape of Nebula and other plugins from other companies. Processing audio files plugin by plugin is taking time. I was wondering if you know or if it's possible to open many plugins in one "special" plugin or do you know a simple way to do that ?
If you are just processing tracks, why not set up as many plugins as you can in a chain?Why do you need them all hosted in a "special" plugin like the DDMF Metaplugin? That is great for saving presets with multiple plugins, but if it is just for processing (like batch processing to take the fx offline and save CPU), you don't need another plugin to host them. Maybe I am not understanding fully what you need.
[quote="RJHollins"]I also use MetaPlugin inside apps like Reaper because it allows me to split a stereo track and treat each side separately ... very handy.[/quote]
That's an interesting idea, but because Reaper is so darned flexible, I have always split almost all stereo files into foldered mono L/R tracks anyway, so I have always been able to process the sides of the stereo track uniquely without the need to use another plugin. Almost all of my work is treated like multiple mono tracks, it is a habit from my analog days. This has been a real brain saver on many occasions when making processing decisions. So I myself am still not convinced why a person would need to host chains in a separate plugin.
[quote="DavidMeShow"]Thanks guys ! MetaPlugin seems to be perfect for what I need. I use a lot of Nebula instances and saving presets in MetaPlugin is going to save time in the future. :)
test it before with the demo version !!!
it works great with all my algoplugs and allows for nice processing experiments and templates of your needs. BUT there was one bug with nebula in the past, which the developer was not able to find. it prevented nebula from detecting the right samplerate, when you open a saved instance. workaround is to open every instance inside metaplugin after loading it and reload the program. that is a showstopper, when working with many nebulainstances inside metaplugin. saved presets of metaplugin load with the default samplerate of 44.1 khz. i don't know, if the actual version is working better in that respect. mathias