Diva andStudio one odd cpu behavior

[OreoSplitter]

When I add an instrument to a new track diva doubles it's usage. It goes from using say 30 percent on one core to 30 percent on two of them. If I disable and re-enable diva usage goes back to normal, one core, until I add another instrument. Even disabling a different instrument causes diva to use a second core.

I am not talking about clicking the activate button in the mixer. It's the enable/disable feature when right clicking an instrument in the instr tab to reset diva or disable other instruments.

This does not occur with any other vst. Any else have this problem?

[Urs]

Is that with Diva's MultiCore option enabled?

[Funkybot's Evil Twin]

Can you elaborate when you say, "when I add an instrument to a new track diva doubles it's usage?" What you're doing isn't clear to me, it sounds like you already have Diva in a project, but then you add another instrument? Or are you adding another instrument/MIDI track feeding that same instance of Diva?

Please walk us through the steps in detailed like this (just an example):

1. Click and drag Diva from the browser to a new instrument track
2. Turn on multi-core in Diva
3. Create a new instrument track in the arrange window
4. Route this to Diva
5. Look at the Performance meter, should be doubled
6. Disable and and Activate Diva via the power button on the instrument track

Result: CPU usage is back to normal.

If you can be that detailed, I can try to reproduce here. Also, are you on Mac or Windows?

[OreoSplitter]

Create a track with diva. Load up some patch and notes that uses a lot of cpu so this is noticeable. I did not have multicore checked in diva. So far diva has not used more then 50 percent cpu.

Create a new track with a new instrument that uses hardly any cpu like zebra or Mai Tai. Now instead of using one core, it looks like the usage has been duplicated using 2 cores. If I disable and enable diva it goes back to using one core.

Even disabling an instrument causes diva to duplicate its usage. For example start a new song with just zebra playing. add diva to a new track. I see it using one core. Then disable zebra (from instr tab, right click on it, disable). All of a sudden it is now using two, identical usage. So more usage when the only thing done has been disabling and instrument.

The performance screen in studio one looks normal through out all of this. It does not show more or less usage but in a program called process explorer where it shows per core its very noticeable. Task manager shows same thing.

windows 10.

[Funkybot's Evil Twin]

I don't have Process Explorer but I tried to reproduce your issue with the newest Diva beta from last week and didn't see this issue. Here's what I did:

1. Blank project
2. Loaded up Diva (multi-core off) on a new instrument track
3. Added an instance of OB-XD
4. Began recording some chords in Diva (using 22% of one core in S1, about 5% in task manager)
5. Stopped and recorded some sustained chords in OB-XD (using about 9% in S1, Task Manager now showing between 8-9% CPU)
6. Turned off power to Diva using the Instrument menu and played the track (CPU drops in Task Manager to about 3%)
7. Turned back on power to Diva and played the track (CPU is right back where it was before in Task Manager, between 8-9%)

So I'm not seeing any doubling there.

[OreoSplitter]

Try this.

1 new song. load diva. Create a midi event with a bunch of notes.
2 loop and hit play. check cpu usage.
3 stop. Add a new track with Mai tai instrument.
4 hit play (both should be active) and see if diva uses an extra core.
5 disable Mai tai from instrument tab (right click, disable), hit play and see cpu usage.

Something is off. Loading a saved project with just diva gives one core. but if i load a project with any other instruments it uses 2 nearly identical usage. Think i just need to try it on a fresh windows install.

[Funkybot's Evil Twin]

Try this.

1 new song. load diva. Create a midi event with a bunch of notes.
2 loop and hit play. check cpu usage.
3 stop. Add a new track with Mai tai instrument.
4 hit play (both should be active) and see if diva uses an extra core.
5 disable Mai tai from instrument tab (right click, disable), hit play and see cpu usage.

Just tried this following your steps. Result: there's some light CPU activity on a second core (probably my limiter on the master buss) after loading Mai Tai, but disabling Mai Tai and or Diva doesn't cause the behavior to change in any unexpected ways. The load balancing seems normal here. I don't think Diva is the issue here. My guess is it's either just S1's load balancing doing something strange on your PC, or perhaps something strange in your PC setup. Maybe hit up the S1 forums and see if anyone else gets similar results.