I think my system is even better, had to check 8 cores intel, 2.7 ghz with boost up to ghz, 16 gb ram, 1tb
Rme Interface and Reaper daw version 3.7x
I think my system is even better, had to check 8 cores intel, 2.7 ghz with boost up to ghz, 16 gb ram, 1tb
2.7 GHz is fairly weak. Any chance that is a laptop CPU?DCrown wrote: Tue Feb 07, 2023 8:58 pmI think my system is even better, had to check 8 cores intel, 2.7 ghz
I mean the computer you make music with not the one you write your posts on KVR with!
Let logic prevail!EnGee wrote: Tue Feb 07, 2023 10:56 pm But I need to provide info so the others can understand and compare to their systems. Yes, all systems are different, but there is a reason for the performance. It is not random!
i use it for cooking, i just have to hit a note on Pigments and after couple of seconds it is ready for some eggs with baconEnGee wrote: Tue Feb 07, 2023 10:56 pmI mean the computer you make music with not the one you write your posts on KVR with!
You can't afford buying a new system? or you just like misery?
My pc is not weak, it runs all the plugins I ever wanted without issues, my daw has not crashed even one time the last 7 years, before I had pro tools with some crashes and a different pc, my biggest project is with about 90 tracks and tons of plugins, average tracks / project about 50- 60
I have tested it, and I have for your first example in Ableton with 3 voices a peak around 70% and after some fraction of a second it goes to 42-44%, for the second example with 16th notes it‘s between 8-9%. My CPU is i7-10700. So the results are, let‘s say, similar.EnGee wrote: Tue Feb 07, 2023 7:50 amThat's on average for the factory presets. Why? What's strange?! How much these two presets hit your cpu?SamDi wrote: Tue Feb 07, 2023 7:30 am And we are talking about a midclass CPU here. Clearly patches can get complex. But an average from 10 to 20% ?
Below are two screenshots from my Windows 11/ Ryzen 5800X PC (My Mini Mac is about similar, more or less).
Here is a chord of three notes for a Pad:
PhasePlant - Blue Messiah Pad.jpg
and here is single note repeated fast for a bass:
PhasePlant - Classic House Bass.jpg
Glad to hear it's working for you!DCrown wrote: Wed Feb 08, 2023 5:58 am My pc is not weak, it runs all the plugins I ever wanted without issues, my daw has not crashed even one time the last 7 years
Do you think the main focus or strength of pp is sound design and creating own presets? Was it promoted that way by the dev when it was released? I am just curious and think pp is a pretty good synth. Do most people use pp for sound design?SamDi wrote: Wed Feb 08, 2023 9:40 amI have tested it, and I have for your first example in Ableton with 3 voices a peak around 70% and after some fraction of a second it goes to 42-44%, for the second example with 16th notes it‘s between 8-9%. My CPU is i7-10700. So the results are, let‘s say, similar.EnGee wrote: Tue Feb 07, 2023 7:50 amThat's on average for the factory presets. Why? What's strange?! How much these two presets hit your cpu?SamDi wrote: Tue Feb 07, 2023 7:30 am And we are talking about a midclass CPU here. Clearly patches can get complex. But an average from 10 to 20% ?
Below are two screenshots from my Windows 11/ Ryzen 5800X PC (My Mini Mac is about similar, more or less).
Here is a chord of three notes for a Pad:
PhasePlant - Blue Messiah Pad.jpg
and here is single note repeated fast for a bass:
PhasePlant - Classic House Bass.jpg
I had a small look on the other patches and I have rather said, that they are between 5 and 10% for one note, but that‘s for sure not objective, because I just looked at lead and bass sounds, not complex pads or whatever.
So yes - your statements are true: the patches are partly real CPU hogs.
What I am wondering about: Phase Plant itself isn‘t very CPU consuming. It‘s very efficient implemented and because I mostly make patches myself I didn‘t realize that patches are that complex.
Take your first example: the Blue Messiah Pad uses like 38(!) instances of oscillators, if I counted correctly. I am not sure, if I would regard that a good sound design in terms of "what do you do to achieve a certain sound" and I assume one could reach similar results with much less waste of CPU time.
What is also pretty CPU consuming for many patches is the fact that they use some polyphonic effects, but this is clear that you will need much CPU power, if you want to use this.
BTW, I have my problems with all the PP presets (including the expansions, because I have a subbscription). Normally I make most presets myself, but curretnly I experiment to achieve things with preset sounds. Unfortunately all the PP sounds seem to fit very bad to my exisitng project, but I cannot really express, why this is the case. It's like some sheen and shimmer is missing.
To be honest, also after this discussion, I have the impression that most presest are like "lets stack enough oscillators and effects together and it will sound good somehow", instead of using the possibilites smartly and that the sound designers exactly know what they do.
Fazit: PP - CPU light; PP stock presets - CPU heavy
Yes! It is a big preset! There are some like this one especially in the Pad and similar categories. Of course it is better to make our own presets. Personally, I don't use that much oscillators and effects! Two oscillators with some unison and little bit of effects. Anyway, I believe some presets are for demonstrating more than to be used.SamDi wrote: Wed Feb 08, 2023 9:40 am
Take your first example: the Blue Messiah Pad uses like 38(!) instances of oscillators, if I counted correctly. I am not sure, if I would regard that a good sound design in terms of "what do you do to achieve a certain sound" and I assume one could reach similar results with much less waste of CPU time.
What is also pretty CPU consuming for many patches is the fact that they use some polyphonic effects, but this is clear that you will need much CPU power, if you want to use this.
Submit: News, Plugins, Hosts & Apps | Advertise @ KVR | Developer Account | About KVR / Contact Us | Privacy Statement
© KVR Audio, Inc. 2000-2026