Ok, but you do get my point though I hope if one had ten such plugins or instances in a project. The cpu would be giving issues before one note is even played.Urs wrote:I feel very compelled to lift the idea of a "stand by during silence" option off of the other great emulation that came out recently.zvenx wrote:Secondly I especially wish it used less cpu especially when it wasn't triggering any audio (yes ED pointed me to why it doesn't), I would have loved that as an option at least.
Uhhh... that was Urs saying he is going to address thatzvenx wrote:Ok, but you do get my point though I hope if one had ten such plugins or instances in a project. The cpu would be giving issues before one note is even played.Urs wrote:I feel very compelled to lift the idea of a "stand by during silence" option off of the other great emulation that came out recently.zvenx wrote:Secondly I especially wish it used less cpu especially when it wasn't triggering any audio (yes ED pointed me to why it doesn't), I would have loved that as an option at least.
rsp
Well, I'll be doing more extensive testing over the weekend for sure... Proper audio interface, try my other DAWs, look for errant background processes and memory consumption, and so on.fluffy_little_something wrote:The variation in CPU load from one computer to another seems extreme. When my old AMD system handles it way better than Deastman's i7 laptop, things are getting really weirdDoes that plugin prefer certain settings (DAW sample rates etc.)? Or multi-threading?
i have an HP desktop from 2010 with a Core2 Quad Q9505 @ 2.83gHz.deastman wrote:I have a 2 year old Dell Inspiron i7 laptop, and most of the presets are maxing out my CPU.
Can you run 6 or more instances without glitching? I was seeing up to 25% usage for a single instance in my DAW but only 35% or so for 8 instances, so don't trust your DAW's CPU meter. Try to max it out in terms of glitches, and how many instances it took to make those happen.Sequent wrote:You guys talking about cpu issues made me nervous. Seems to be about 19-20% on this end. A little bit more for some of the heavier patches, and that's with a bunch of other effects and processors running. I can live with that, whereas I could not really live with Diva or something like the Softube modular. I've been down this road before and I know that what seems like a heavy load now, will probably be like nothing a computer or two down the road. But in the meantime, I think it's very usable (at least for me). So, a big thank you to Urs and team. You guys have just handed back to me my old Pro One, and that brings back many memories and makes me very happy.
When synced to host you need the "Clock" setting which also works for the Arp. The clock settings go from 8/1 to 1/64.digidennis wrote:no multiplier on the LFO when synced to host?
To me it seems weird that the LFO rate is dependent on the SEQ rate ( if both are host synced ), should have its own multiplier - the knob is there.Ingonator wrote:When synced to host you need the "Clock" setting which also works for the Arp. The clock settings go from 8/1 to 1/64.digidennis wrote:no multiplier on the LFO when synced to host?
Submit: News, Plugins, Hosts & Apps | Advertise @ KVR | Developer Account | About KVR / Contact Us | Privacy Statement
© KVR Audio, Inc. 2000-2026
)
