I thought it over. Just sent out the versions working for two different plugins to anyone donated.wesleymayhem wrote:I'm very excited about being able to use two different plug-ins... When do you think that might be available??? Thanks.
Christian
I thought it over. Just sent out the versions working for two different plugins to anyone donated.wesleymayhem wrote:I'm very excited about being able to use two different plug-ins... When do you think that might be available??? Thanks.
Could you explain this further?Shy wrote:A funny request: stereo mode (not left/right. just stereo, or maybe stereo/stereo with on/off switch for each)
Well, at the moment I like the fact, that Electri-Q is one of the only EQ, that has this feature...aud.io wrote:Christian, while you're at it, how do you like the idea of an "any eq linearizer" utilizing that reverse treatment trick? It would have to introduce latency of course but it would be very cool nevertheless.
Actually, I wouldn't do it the way you do with a plugin splitter/merger. I'd simply create a plugin host like EnergyXT/FL Studio that itself is a VSTi if so desired. However, it all comes down to how you treat the plugin interface and in my opinion, the most important part, how quickly you can make it switch presets (somekind of pre-loading of plugins is needed for a live set where setups use different plugins) on the fly without any glitches. This is still one of the advantages of some hardware synths and vital for live playing.Christian Budde wrote:It's probably really a bit ambitious, since with the current VST architecture this would mean to process the hosted VST plugins sample by sample (to have an accurate automation). Depending on the plugin hosted, this might lead to a huge overhead. The mda plugins for example create a copy of the initial states before entering a more effective loop for each sample. After that the states are stored back. While this is a good strategy for blocks, it is probably a lot overhead sample based processing. Also some plugins might fail with this strategy entirely, since they rely on SSE code (using 4 samples at one time). It might work, but increase the CPU consumption by a factor of 4.bmanic wrote:Anyhow, perhaps more people will now warm up to the idea of merged plugins, aka virtual racks. I've been trying to get people/developers warmed up to this kind of idea for quite a long time already, although my vision has been a bit more ambitious (internal VST parameter modulators like LFO's, Envelopes, step sequencers, sample triggers etc).
Now imagine all this stuff with multiple VSTi synths/samplers + VST effects, all internally possible to be modulated by LFO, envelopes etc. This would also provide fast preset loading and an excellent opportunity for 3rd party professional patch programmers to create amazing "effect rack banks" for the masses.
Still, with all these issues I think it is doable, but at least not for me. You also have to face several compatibility problems, since you do not only have to ensure the created plugins work in every host, but also to work with every plugin. I mean basically it's possible this way to help plugins, which might not work in one host, that they do after the treatment, but it is more likely the opposite happening.
Just some thoughts about this. Anyway I hope that this opens the world a little bit towards your idea. I would be glad to see something like this in the future...
Kind regards,
Christian
I really hope this can be done. If i want to compress the bass with one version of the plugin, and there is no bypass, then i have to run the high end into the compressor as well. On some plugins this means all sorts of annoying fiddling to avoid the high end getting compressed too, and on some others its impossible to avoid compression.It would be REALLY nice if there was some kind of a bypass or thru for each plugin since not all plugs have a bypass/thru mode. seems like it would cut out half the cpu if for instance i just wanted to process the side signal and not the mid. I don't know if this is possible or even something you'd consider implementing but just thought i would mention it.
Submit: News, Plugins, Hosts & Apps | Advertise @ KVR | Developer Account | About KVR / Contact Us | Privacy Statement
© KVR Audio, Inc. 2000-2026