Diva 1.1 Final (beta testing finished)

[Howard]

Even if the CPU stays at a reasonable amount from time to time i get audio drop outs but i am not able to reproduce this at any time. If i play that preset for around 30-60 seconds with different speeds (speed with which the notes are hit) i could reproduce this at least once at that period.

Are you playing manually, or triggering from the sequencer? The former is more fun (IMHO), but only the latter will give you consistent results...
Whatever, one obvious reason why increasing the "speed of playing"will affect CPU-hit is that more notes are either gated or in Release (i.e. active) at the same time.

[Ingonator]

Even if the CPU stays at a reasonable amount from time to time i get audio drop outs but i am not able to reproduce this at any time. If i play that preset for around 30-60 seconds with different speeds (speed with which the notes are hit) i could reproduce this at least once at that period.

Are you playing manually, or triggering from the sequencer? The former is more fun (IMHO), but only the latter will give you consistent results...
Whatever, one obvious reason why increasing the "speed of playing"will affect CPU-hit is that more notes are either gated or in Release (i.e. active) at the same time.

Hi Howard,

i played manually, also to get results that are related to "real playing".
Of course i know that this is based on overlapping notes but that's something which happens often in the "real world".
Anyway with the new update is much more usable for polyphonic sounds even if i will not use Divine mode as a standard mode. Maybe i'll use it while rendering if possible. Those problems should be finally solved when i get a new PC sometimes this year. My PC with the Q6600 is around 4,5 years old now.
At the time when i was still playing computer games every day (now i play only rarely and only quite old games) i got a new CPU (and graphics card maybe too) around every year (sometimes every second year)...


Ingo

[iamyourfather]

Just had to post about the funniest patch I have ever seen in the new wobble bank with the question "what the Queen has in her coffee ?" in the info ...


Patch name : KORGI CREAM

On a more serious note, everything seems to be working fine .... looks to good to go

[Examigan]

Without reading through 12 pages...is the demo version updated now also?

I'd like to try it again to see if my PC might handle it better now

[djanthonyw]

The demo is the same as the full version. When you enter your serial number to register it, it turns into the full version.

[Examigan]

The demo is the same as the full version.

Cool! I'll go check it out now

Thanks dj

[Gonga]

Could Ingo's 32-bit OS, or the memory limitation, be factors also?

[phazedown]

delete-me

[Ingonator]

someone else posted about underrunns with multicore, but I experienced it and have some more info. Just been running a test I'm on a macbook pro with core i5 one instance of Diva in an empty Live set. I've used v1 of diva quite a bit and could generally run my cpu pretty hot until I got underruns.

my buffer is set to 64 and I generally have no problems with that until my cpu get's up high. testing a 3note chord in diva default patch multicore turned off cpu hit's 23% no sound problems. switch multicore on play chord cpu drops to 18% (nice) but I consistently get underrun drop outs

I changed my buffer to 128 and tried it again, the cpu load is reduced and the underruns lessen, but still occasionally get a pop I can add notes until cpu hits around 45-50% and they become slightly more frequent if I turn multi-threading off I don't get them. I'll just keep multi threading off for now, but man I'm excited to take advantage of that cpu boost.

I was just reading this and it seems to fit into what i observed myself (see my posts above). Using the "multi-threaded" switch drastically reduces the CPU use with Divine mode (was 100+ % with 3 note chords in the old version) but even at below 50% CPU (display in Ableton Live 8 ) i get occasional audio drop outs (could not be reproduced at any time).
Maybe this is due to the fact that the older Quad Core CPUs like my Core 2 Quad Q6600 are not fully supported by the update. Urs mentioned it is more for newer ones like i5 or i7.
Anyway like already mentioned even without the "multi-threaded" switch there is a big improvement in the performance.
Currently the best quality/performance ratio with my system is with "multi-threaded" off and Great accuracy.

1. Multicore Support

Finally play as many voices as you like on selected systems! This needs multicore system with on-cpu-memory-interface like i5, i7, Nehalem.

The first i7 CPUs with the Nehalem architecture were released in 2008 while the Core 2 Quad Q6600 ("Kentsfield" architecture) was released in 2007 (i got mine in November 2007). The Q6600 could miss the built-in memory controller of the Nehalem.


Ingo

[Howard]

I noticed a bit of mess on page 11/12/13 of the manual: The transparent image was on page 11 before. Now the saw/tooth/subosc aren't at their place anymore.

Yep - sorry about that. Already fixed for the release version (those graphics were not set to "move with text" in Pages)

[hakey]

Just had to post about the funniest patch I have ever seen in the new wobble bank with the question "what the Queen has in her coffee ?" in the info ...

Patch name : KORGI CREAM

There goes my knighthood.

(was going to turn it down anyway)

[PAK]

reasoning about the weird nature of your bug gave rise to an amazingly simple answer. We have something that counts the time but that is an integer number that only goes to 2147483647. After that it became negative, which somehow was a bug.

Consider this fixed in the next version!

Hi Clemens,

Yep, it really seemed like it might have been some awkward code interaction. Glad it turned out to be something relatively simple for you to fix!

We're closing in
Rev. 655

- No more crashes after long silence

Just to confirm, I left this build running for the last 48+ hours and everything's still behaving rock solid. Really nice to see this bug finally nailed!

Thanks guys

[Kaboom75]

Diva 1.1 has fixed all my problems with Diva \o/

Every thrid key press or so silent fixed


Ableton sessions with multiple Divas loading with crackel/ no sound Fixed

Some presets no sound or crackle fixed


Tested it over six days ran perfect no bugs that I can find. CPU usage on my i7 3.8 Ghz has had a huge improvment even with mulitiple divas at the same time.


Now I want a digital version of DIVA with Yamaha FS1R moduals :)

Thanks U-he team you are gods.

[Urs]

Now I want a digital version of DIVA with Yamaha FS1R moduals

tonight I was outbid on an FS1R on ebay

[oish1]

I've been playing around with this version of Diva all weekend, all in the latest version of Live 8 on a macbook pro i5

The conclusion at least for me is while turning on multi-threading reduces the cpu it increases the amount of audio dropouts by a substantial amount. I tested this in new tracks using just Diva and in my old tracks containing Diva. in every case turning on multi threading and replaying the track always increased the amount of audio dropouts. and in one case on a track with 3 instances of Diva turning on multi-threading actually increased the cpu use instead of decreasing it. I'm not sure if it's my setup, diva, or live. Has anyone else had similar issues?