Vital - Released

[Teksonik]

when i open vital (standalone), i get between 17-35% cpu usage; right now (in logic, as a plugin), i've got 8 instances of vital running, with complex patches, and dense chords... and averaging 50-100% cpu (with a single peak at 256%!), but no stuttering, or pauses.

Did you test a single instance with the INIT patch at idle with GUI opened and closed ?

Does having the GUI open make a significant difference in CPU demand ?

[fisherKing]

Did you test a single instance with the INIT patch at idle with GUI opened and closed ?

Does having the GUI open make a significant difference in CPU demand ?

single instance with the init patch:
GUI closed, logic is at 2.9%

GUI open, logic is at 16.1%

fyi, the percentage is not static, especially with vital's GUI open...

[Teksonik]

That'd pretty much that I'm getting. This is on my internet computer i5 3470, Onboard Intel graphics

GUI Open:

i5 GUI Open.png

GUI Closed:

i5 GUI Closed.png

Studio Computer i7 8700K. nVidia 1050 Ti Graphics

Open:

GUI Open.png

Closed:

GUI Closed.png

[mabian]

Innocent question... is it possible to change something in the appearance? I know it sounds a bit childish but I can hardly stand the purple tint used for the waveforms...

- Mario

[Teksonik]

Not yet. Custom themes or user colors have been suggested but I imagine it's pretty far down on the list of priorities right now.

For the record I'm not a fan of the purple either or the green but can live with them.

[RexBanner]

I love the purple. But I also love pastel colors.

[revvy]

Yup. Love me some purple and green, Vital looks sweet on my iMac screen.

[DanielPL]

That'd pretty much that I'm getting. This is on my internet computer i5 3470, Onboard Intel graphics

You are comparing different CPUs by looking at the overall system processor usage. Without getting into details, leaving CPU speed considerations etc., please note that 15% usage of CPU with 4 cores (4 threads) is about 60% usage of a single core and 4% usage of CPU with 6 cores (12 threads) is about 48% of a single core.

[Markin]

On my system Vital is running ok. Not excessive by any means.
It becomes Cpu intensive when I add more modulation sources.
And start upping unison voices without considering the possible consequences.

[Teksonik]

That'd pretty much that I'm getting. This is on my internet computer i5 3470, Onboard Intel graphics

You are comparing different CPUs by looking at the overall system processor usage. Without getting into details, leaving CPU speed considerations etc., please note that 15% usage of CPU with 4 cores (4 threads) is about 60% usage of a single core and 4% usage of CPU with 6 cores (12 threads) is about 48% of a single core.

I'm simply reporting the readouts with Vital's GUI open and closed, Init Patch, no other apps running, no audio being processed, plugin at idle.

I thought Matt might find the information useful. For the record Vital runs fine on both systems but I don't ask my internet computer to do anything more than run a single instance of any plugin.

[neverbeeninariot]

Some CPU usage observations.

Firstly, this is completely non-scientific, obviously... I picked a similar(ish) sounding pad that was fairly close in terms of cpu use across all the VST's with their GUI's closed. The release was adjusted so that voices were not accumulating, and looped 9 bars of a 3 note chord.

Secondly, they are radically different synths.

The measurements are Reaper's reported: Total CPU, Track CPU, and RT CPU - the max value over 4 loops was recorded. Specs: Core i7 4790, 32GB RAM, Nvidia GTX 760, Win10, Reaper 6.18 x64, 64 sample buffer on a Saffire Pro40. Total CPU at idle: 0.4%, Real-Time CPU at idle: 1.2%.

What surprised me most of all was the increase in RT CPU when a track was record armed.

Anyway, caveats in mind, here are the results, for what they are worth.







Edit: Added GFX card.

[Jorgeelalto]

Some CPU usage observations.

Firstly, this is completely non-scientific, obviously... I picked a similar(ish) sounding pad that was fairly close in terms of cpu use across all the VST's with their GUI's closed. The release was adjusted so that voices were not accumulating, and looped 9 bars of a 3 note chord.

Secondly, they are radically different synths.

The measurements are Reaper's reported: Total CPU, Track CPU, and RT CPU - the max value over 4 loops was recorded. Specs: Core i7 4790, 32GB RAM, Win10, Reaper 6.18 x64, 64 sample buffer on a Saffire Pro40. Total CPU at idle: 0.4%, Real-Time CPU at idle: 1.2%.

What surprised me most of all was the increase in RT CPU when a track was record armed.

Anyway, caveats in mind, here are the results, for what they are worth.

You don't have a graphics card right?

[neverbeeninariot]

Nvidia GeForce GTX 760 4GB

[ReleaseCandidate]

What surprised me most of all was the increase in RT CPU when a track was record armed.

That's Reaper's (and other DAWs) way to optimize tracks.

[AJYoung]

Regarding the LFO's... (reposted from the presets thread cause this is the main theead)

If one is using Loop Point mode, then select a particular point as the start point, then move the point, the start point stays where the point was. Not sure if that is intended behavior or not.

The "Loop point" is actually the position of the Phase control (bottom slider). It's not locked to a specific point.

That'll probably clear up some confusion on the other modes too. For example, sustain envelope was probably only triggering on release because the phase was set to zero, the far left.