KVR Audio

a1audio.de · Post by **a1audio.de** » Wed Sep 04, 2013 5:08 am

sound_dev wrote:
HcDoom wrote:Proper multicore support is a must imo. Why stress one core when you can divide the workload on other cores? I mean, that's why we have multicore cpu at first place.
you think that 20% load of each of 2 cores is better than 40% load of one core?

come on ... 2 cores with 51% is in fact better than 1 core with > 100%
(plus these beloved little dropouts)

piastro · Post by **piastro** » Wed Sep 04, 2013 5:48 am

Trancestorm wrote:
piastro wrote:I'm curious: will the multicore support be implemented in future versions?
already has, because i maxed my old notebook out with one supersaw patch and all 2 cores got used playing it.

Wrong. There is no multicore support in Spire. At least for me.

Right now I'm on OSX 10.8, Logix pro x, there's a instance of Spire with maxed cpu use - it stays within one core in any scenario unlike, for example, Di*a

trusampler · Post by **trusampler** » Wed Sep 04, 2013 5:54 am

I just loaded 48 Spire instances in Studio One, armed and recorded all parts, n the cpu isn't over 25% this is also while playing 4 finger chords, I'm sure different patches on each instance would eat more cpu, but not much more.

This is on winx64,i7 at 4ghz

pinkpanther · Post by **pinkpanther** » Wed Sep 04, 2013 7:47 am

trusampler wrote:I just loaded 48 Spire instances in Studio One, armed and recorded all parts, n the cpu isn't over 25% this is also while playing 4 finger chords, I'm sure different patches on each instance would eat more cpu, but not much more.

This is on winx64,i7 at 4ghz

Good for you. They should change system requirements to overclocked i7 processor

Ameyah Audio · Post by **Ameyah Audio** » Wed Sep 04, 2013 9:42 am

piastro wrote:
Trancestorm wrote:
piastro wrote:I'm curious: will the multicore support be implemented in future versions?
already has, because i maxed my old notebook out with one supersaw patch and all 2 cores got used playing it.
Wrong. There is no multicore support in Spire. At least for me.

Right now I'm on OSX 10.8, Logix pro x, there's a instance of Spire with maxed cpu use - it stays within one core in any scenario unlike, for example, Di*a

Win7 SP1_64 Enterprise, AMD QL62@2,0GHz underclocked to 1,0GHz. and it was indeed using both cores for it in Ableton Suite 9.0.5_32
tested with different presets aswell.

piastro · Post by **piastro** » Wed Sep 04, 2013 10:24 am

Trancestorm wrote:
piastro wrote:
Trancestorm wrote:
piastro wrote:I'm curious: will the multicore support be implemented in future versions?
already has, because i maxed my old notebook out with one supersaw patch and all 2 cores got used playing it.
Wrong. There is no multicore support in Spire. At least for me.

Right now I'm on OSX 10.8, Logix pro x, there's a instance of Spire with maxed cpu use - it stays within one core in any scenario unlike, for example, Di*a
Win7 SP1_64 Enterprise, AMD QL62@2,0GHz underclocked to 1,0GHz. and it was indeed using both cores for it in Ableton Suite 9.0.5_32
tested with different presets aswell.

Maybe it's because of different programming approach for Win and Osx.. anyway, on Mac, Logic and Live hard tests show that Spire lacks multicore support. Hope it will be added..

HcDoom · Post by **HcDoom** » Wed Sep 04, 2013 1:20 pm

sound_dev wrote:
HcDoom wrote:Proper multicore support is a must imo. Why stress one core when you can divide the workload on other cores? I mean, that's why we have multicore cpu at first place.
you think that 20% load of each of 2 cores is better than 40% load of one core?

OFC it is.

4damind · Post by **4damind** » Wed Sep 04, 2013 2:04 pm

"According to Steinberg, the Cubase VST Performance ASIO meter actually displays how hard the audio card driver is working and how much capacity is left before you will experience pops and crackles. In practice, whatever is being measured, comparing the Cubase ASIO meter reading with that of the Windows Task Manager on a multi-core PC shows that Cubase indicates how close any one of the cores is getting to 100 percent occupied."

(from a SOS QA)...

With my testings, multi-thread support will increase the CPU usage because of the overhead needed to synchronize different threads on different cores but lowers the ASIO load (can be easy verified with plug-ins supporting this like Diva).

Elektronisch · Post by **Elektronisch** » Wed Sep 04, 2013 4:30 pm

Its only 7 instances and NOT EVEN PLAYING ANYTHING, CPU 99, hows that ?

Futhemore, it seems this happens only on FL Studio 11. I have tried running on reaper, nothing similar happens.

Vullcan · Post by **Vullcan** » Thu Sep 05, 2013 4:40 pm

AUTO-ADMIN: Non-MP3, WAV, OGG, SoundCloud, YouTube, Vimeo, Twitter and Facebook links in this post have been protected automatically. Once the member reaches 5 posts the links will function as normal.

themachinelt wrote:Its only 7 instances and NOT EVEN PLAYING ANYTHING, CPU 99, hows that ?

(http://postimg.org/image/v6bwnesf1/)

Futhemore, it seems this happens only on FL Studio 11. I have tried running on reaper, nothing similar happens.

Try set option "Use fixed size buffers" in FL Studio.

Ameyah Audio · Post by **Ameyah Audio** » Thu Sep 05, 2013 11:25 pm

i can load 7 spires on the CPU i posted above - that 5 years old AMD QL62 and i get like 10% in idle which is fine - assuming i got also firefox running and ableton. looks like OSX needs then a multicore fix.

playing with the stepper, awesome feature - worth waiting for it.
is there a way to reset it? because i totally murdered it.

is it normal that the Stepper takes alot more cpu as the OSC in supersaw mode?

nIGhT-SoN · Post by **nIGhT-SoN** » Fri Sep 06, 2013 6:59 am

This looks better, lower cpu usage, ok to be used in projects, but if you lower it even more, this will become the next Sylenth1. I don't know how, but Dune managed to make that synth use so little cpu power even when you are using a lot of detuned voices, neither Sylenth1 is that friendly. In fact Sylenth1 is quite a cpu hog when it comes to a lot of voices per osc compared to Dune.

recursive one · Post by **recursive one** » Fri Sep 06, 2013 7:17 am

nIGhT-SoN wrote:This looks better, lower cpu usage, ok to be used in projects, but if you lower it even more, this will become the next Sylenth1. I don't know how, but Dune managed to make that synth use so little cpu power even when you are using a lot of detuned voices, neither Sylenth1 is that friendly. In fact Sylenth1 is quite a cpu hog when it comes to a lot of voices per osc compared to Dune.

Unfortunately, Dune does not sound as good as Sylenth or Spire at unison patches.

fgimian · Post by **fgimian** » Fri Sep 06, 2013 1:24 pm

I must admit that the sustain pedal problems are quite a pain. Reveal Sound,is there any chance you can repair them please?

Ameyah Audio · Post by **Ameyah Audio** » Fri Sep 06, 2013 2:15 pm

soundpalace wrote:I must admit that the sustain pedal problems are quite a pain. Reveal Sound,is there any chance you can repair them please?

havnt noticed, could you explain me? that i can test it here?

recursive one wrote:
nIGhT-SoN wrote:This looks better, lower cpu usage, ok to be used in projects, but if you lower it even more, this will become the next Sylenth1. I don't know how, but Dune managed to make that synth use so little cpu power even when you are using a lot of detuned voices, neither Sylenth1 is that friendly. In fact Sylenth1 is quite a cpu hog when it comes to a lot of voices per osc compared to Dune.
Unfortunately, Dune does not sound as good as Sylenth or Spire at unison patches.

i agree there, kind of hate the supersaw programing in dune - it sounds so cold to me, nothing compared to Sylenth1/Spire.

took me yesterday like 5 mins to find the volume knob

and that after using Spire since 0.9.8 for like 10 hours.
Spire

Spire Synthesizer