u-he

aMUSEd · Post by **aMUSEd** » Fri Apr 06, 2012 8:07 pm

Crackbaby wrote:Incredible update! Multi threading works in EnergyXT (which i don't think is multithreaded in the first place?)

Yes and in NI Kore. Working very well

Urs · Post by **Urs** » Fri Apr 06, 2012 9:28 pm

4damind wrote:Multithreading needs more CPU power (20% for a 2-stacked voices with "great" accuracy) on a Core 2 Duo. May be this "improvement" goes in the wrong direction.

Sorry, Core2Duo has a memory bottleneck, just like my 2007 Mac Pro. It doesn't do much there...

Urs · Post by **Urs** » Fri Apr 06, 2012 9:29 pm

mabian wrote:I thought that a plugin couldn't use multiple cores because the DAW handles cores itself (and usually allocates all plugins in a track to same core).

Is it wrong? Or is it voodoo?

- Mario

It's possible. Halion uses it, Harmor does it and now Diva, and maybe a few more that I do not know.

(actually, disc streaming samplers would need to be multi threaded too)

Urs · Post by **Urs** » Fri Apr 06, 2012 9:33 pm

justin3am wrote:I haven't had a chance to check out a beta in a while. I definitely see big performance improvement on my Quad i7 MBP, not so much on the dual core machines I use for work. I can't wait till I get home to try it on the 12 core monster MacPro.

You're going to be lucky with the 12 core

The older pre-Nehalem Mac Pros do not benefit much (2 voices perform slower, 10+ voices use up all cores)

Has filter tuning changed? The last version I used was the release build and it seems like patches where I used the filter as an oscillator, are now out of tune. Not a big deal, I need to update my patches anyway, just wondering

Please send those patches to us. Clemens needs to look into that. We're not aware of any changes, but this rises a red flag. We do need to check this out before releasing anything.

xh3rv · Post by **xh3rv** » Fri Apr 06, 2012 9:57 pm

mabian wrote:I thought that a plugin couldn't use multiple cores because the DAW handles cores itself (and usually allocates all plugins in a track to same core).

Is it wrong? Or is it voodoo?

- Mario

I'm sure there's some voodoo

Multi-threading is like a factory designed by MC Escher - it makes practically infinite things and it looks like one can use a thousand conveyer belts in all sorts of combinations to do so, but it turns out it's only one conveyer belt with a lot of twists and tricks ... multiple cores is like multiple conveyer belts but they're in different buildings and have to be managed by the guy in the main building. Gets a little chaotic

I wouldn't swear on anything, but - generally there's sort of a global threading environment managed by the OS, communicating in relatively direct way with hardware. An OS will have a 'make thread' procedure that's called by a program; that should be the same inside a VST as a DAW in terms of, what sorts of requests it can make of that environment's resources.

justin3am · Post by **justin3am** » Fri Apr 06, 2012 11:06 pm

Urs wrote:
Has filter tuning changed? The last version I used was the release build and it seems like patches where I used the filter as an oscillator, are now out of tune. Not a big deal, I need to update my patches anyway, just wondering
Please send those patches to us. Clemens needs to look into that. We're not aware of any changes, but this rises a red flag. We do need to check this out before releasing anything.

Here you are, sir.
http://www.3amnoise.net/diva_filterdrones.zip
These were made with build 478. In that build, C3 is perfectly in tune and 4 octaves up is 6 cents below C7. Tuning is roughly the same across all filters.
In Diva 1.0.0, C3 is perfectly in tune and C7 is ~13 below. Tuning is roughly the same across all filters.
In Diva 1.0.1, C3 is ~1 cent below and C7 is ~17 below. Tuning is roughly the same across all filters.
In build 585, C3 is ~1 cent below and C7 is ~37 cents below. Tuning is still roughly the same across all filters.

phazedown · Post by **phazedown** » Sat Apr 07, 2012 12:19 am

delete-me

David Else · Post by **David Else** » Sat Apr 07, 2012 12:54 am

using diva 64 bit, a quad core q6700 / win7 64bit / reaper 64 bit - 256 samples ASIO buffers, it works fantastic in the new multithreading mode! i can now play patches fine that without multithreading just dissolve into crackling! no crashes here.

Urs mentioned there is an improvement in the sound of the transients in the new version, anyone picking up on that?

Funkybot's Evil Twin · Sat Apr 07, 2012 1:51 am

I'm getting more than a 50% performance increase with the new version on my i7. Nice job Urs, Clemons, and co.

Echoes in the Attic · Post by **Echoes in the Attic** » Sat Apr 07, 2012 3:34 am

Does this multi-threading not apply to Ableton Live? As far as I understood, Live assigns each track to a core and I didn't think there was a way around that for any plug-in. I've tested the new beta and haven't seen any different in cpu on the Live cpu meter but I can't say I've tested thoroughly the system cpu meter. If anything Live may be showing slightly more cpu from DIVA. I'm on a macbook pro i7 from last year. I am seeing however that it loads now the quality setting correctly as is stored in an Ableton rack so that's cool.

ezelkow1 · Post by **ezelkow1** » Sat Apr 07, 2012 3:44 am

Try it on a pad poly type patch, like the wash in the polys area. With 5 notes on the initial hit in divine I can get close to 50% in ableton. With multithreaded that drops to 25, you can flick it on and off and see the difference immediately.

Then again this is also windows x64, not sure if that makes a difference, but its still ableton

justin3am · Post by **justin3am** » Sat Apr 07, 2012 3:51 am

Echoes in the Attic wrote:Does this multi-threading not apply to Ableton Live? As far as I understood, Live assigns each track to a core and I didn't think there was a way around that for any plug-in. I've tested the new beta and haven't seen any different in cpu on the Live cpu meter but I can't say I've tested thoroughly the system cpu meter. If anything Live may be showing slightly more cpu from DIVA. I'm on a macbook pro i7 from last year. I am seeing however that it loads now the quality setting correctly as is stored in an Ableton rack so that's cool.

I'm also using Live on a 2011 i7 MBP, I'm using the Audio Unit. The difference is most notable for me on patches with stacked voices or when I play chords. Particularly when I play patches with lots of FM and high resonance.

On my MacPro, Diva in Divine mode is performing better than Bazille in some cases!

Echoes in the Attic · Post by **Echoes in the Attic** » Sat Apr 07, 2012 4:41 am

I did use a polyphonic pad to test - I used "Deep Space DIVA" (beautiful sound!)

But I'm using the VST in Ableton on OSX Lion. Maybe the optimization was AU only? Or maybe Ableton's cpu meter wasn't accurate? I opened the AU in Logic and that patch seemed higher than what was normal in the VST.

justin3am · Post by **justin3am** » Sat Apr 07, 2012 5:06 am

Echoes in the Attic wrote:But I'm using the VST in Ableton on OSX Lion. Maybe the optimization was AU only? Or maybe Ableton's cpu meter wasn't accurate?

I'm still on 10.6.8.
The CPU meter in Live is not accurate. It's as if it's just polling a single core or something. I was watching the Activity Monitor utility built into OSX.

xh3rv · Post by **xh3rv** » Sat Apr 07, 2012 5:07 am

Just a point that comes up a lot when Live's CPU usage does - the Live CPU meter only measures the busiest core. It's more truthful than an averaged overall meter, in a sense, because only one core has to max out for drop outs to occur. So overall CPU load is at most that number times the number of cores in use.

Echoes in the Attic wrote:Does this multi-threading not apply to Ableton Live?

Speculation - I'd imagine Ableton can run a single track as a thread or something like that, but VSTs are sort of a black box - Ableton can manage in and out but not the internals. I'm assuming VSTs can spawn threads by talking directly with the OS, so that's outside of a DAW's control.

u-he

KVR Audio

Diva update?