As mentioned in an original thread I played each instrument 16 notes at the same time, on both i set oscillator Unison at 16, 2 oscillators each.
Original thread: viewtopic.php?t=591044&start=45
There is nothing like that activated and gui was closedtasmaniandevil wrote: Fri Dec 23, 2022 7:01 pm Btw, as other elements, like the oscillator and filter visualization will also affect the CPU, it's best to always close the plugin GUI completely when trying to do feature performance tests.
Oh, and do not record arm the tracks you want to compare.
Some hosts will have an increased CPU demand if the track is armed for real-time recording.
Instead, create MIDI clips and play those clips.
I had the newer version installed, but i asked support to recieve older version installer because newer one started to cause Crashes inside FL Studio.Urs wrote: Fri Dec 23, 2022 7:28 pm Your preset was made with Hive 2.1.0, revision 11037. That's the one before we implemented aggressive resource balancing. This version always processes all modulators and everything, simply because that's faster with real world patches. It does however compute less nicely for such performance tests, which as what led to Hive 2.1.1 (apart from M1 support).
Hive 2.1.1 has, among other things,
- Better resource management for improved CPU performance
https://u-he.com/products/hive/releasenotes.html
It was part of our "performance update" which is the version I was talking about in the other thread and which was used for my own measurements.
What other 24 db filter would be easier on CPU?Urs wrote: Fri Dec 23, 2022 7:17 pm Well, thank you for the preset.
You got filters on, and not cheap ones, for starters. The Hive preset has spread, the Dune one doesn't. I think that made a difference, not sure.
Would be cool to have the Dune preset as well.
Im sorry, didnt ment to do that. But i installed the latest version and i must say thats quite an improvement. Still not CPU efficient as Dune 3, but really significant improvement (both guis closed)Urs wrote: Fri Dec 23, 2022 7:36 pm So, you were aware the whole time that you were using a version from before the performance update?
I mean it's a pity that the newer version would crash for you, that's normally not the case.
But asserting that the optimisation we made wasn't effective simply because your experience is based on a version that does not have this optimisation... I must say, that's pissing me off. What a waste of time.
Submit: News, Plugins, Hosts & Apps | Advertise @ KVR | Developer Account | About KVR / Contact Us | Privacy Statement
© KVR Audio, Inc. 2000-2026