KVR Audio is the Internet's number one news and information resource for open standard audio plugins. We report new releases, product announcements and product updates (major and minor) for all VST Plugins, DirectX Plugins and Audio Units Plugins. We manage a fully searchable audio plugin database (updated daily), and offer many free member services including user reviews, product update notifications and a very active discussion forum. We also host official support forums for many plugin developers plus the official Receptor support forum.
Plug-in Database: Virtual
Instruments, Effects & Hosts
Banks & Patches
Download & Upload
Plug-in Ratings
by KVR Members
Wiki: Tutorials,
Audio Lexicon, ...
Listen to Music
by KVR Members
Search
KVR

Google Powered Search:

in new window

KVR Powered Plug-in Search:

AuthorTopic: CPU Killers.... BONES..?
Andywanders
Posted: 9th September 2004 18:00
Hey Bones, please don't be offended by this, I have a lot of respect for you as a developer and a musician. But I have to ask...

Why do your new Killer synths use so much CPU..?

One instance, with no other plugins, is using up to 25% on my P4. If they add up, then there's no way to use more than 2 or 3 at a time (with other plugs like delay).

So how do you make your tunes...? Rendering..?
Andywanders
Posted: 12th September 2004 02:57
Bump

Question
autloc
Posted: 12th September 2004 03:01
I noticed this, too - karmaKiller took 10% cpu on my 1.6 GHz Pentium M for one note. Not knowing that much about SE, I assumed it was because it was a synthedit synth, but perhaps there's just some really expensive or non-optimised block in there?
quincy
Posted: 12th September 2004 04:11
I can't be sure, buti suspect that synthedit synths suffer the same overheads as using an interpreted programming language. There must be some runtime element that does the work, but it still has to "interpret" your synthedit designs real-time.

That said, they can be optimised too, but its probably not that easy. I'm just learning synthedit, and its tough! Shit!
Sonic Assault
Posted: 12th September 2004 18:00
Hey Bones, I don't know if you caught this but SE had a bug in the 1-> to Many module that was causing a real hammering on the CPU load. I don't know if the new kILLERs are using any of these modules, but Jeff fixed the bug in Beta 0.956.8

If they do, it might pay to compile them again with the latest beta.

All the Best... Jez

Having said that Sinthecyza! 1 and 2 can really mash the clock cycles - Why don't you buggers get a copy of FREEZE and an Athlon and stop worrying about yer underpowered Intels Laughing Wink
BONES
Posted: 12th September 2004 18:01
Mostly its because all but 2 or 3 presets have DUAL unison ON which uses a hell of a lot more CPU but makes everything superFAT like me. I think if you turn it off your CPU will be much happier but your ears may not. I always make sure that the VCA Enveleope RELEASE is as low as possible [usually zero] to minimise overlap of notes. That saves a lot of CPU in DUAL Mode.
SE is unavaoidably more of a CPU hog than a hand-coded synth because of its modular structure. I think these synths are far more efficient than any of my previous efforts which is why I feel that they can handle 16-note polyphony.
Overall, these synths don't use any more CPU than JX Synth which is a fair achievement in my books.
Kim (esoundz)
Posted: 12th September 2004 18:58
BONES wrote:
Mostly its because all but 2 or 3 presets have DUAL unison ON which uses a hell of a lot more CPU but makes everything superFAT like me.


You are superfat? Very Happy

Forever,




Kim.
BONES
Posted: 13th September 2004 01:30
Sonic Assault wrote:
Hey Bones, I don't know if you caught this but SE had a bug in the 1-> to Many module that was causing a real hammering on the CPU load. I don't know if the new kILLERs are using any of these modules, but Jeff fixed the bug in Beta 0.956.8

Thanks for the heads-up. OTTOMH [off the top of my head] I know there are a few Many -> 1's but I'll have another gander when I get home tonight.
Forum topics in the archive are read only. New posts should be made in the main KVR Forums.
Disclaimer:
All communications made available as part of this forum and any opinions, advice, statements, views or other information expressed in this forum are solely provided by, and the responsibility of, the person posting such communication and not of kvraudio.com (unless kvraudio.com is specifically identified as the author of the communication).