small performance test

[geoffroy]

Hi

Here is a small test using Ableton Live 4 demo and Energy XT demo.
Download Energy XT at :
http://www.xt-hq.com/

Ganymed vsti at :
http://www.stefan-kuhn.net/

Then
1. turn on task manager in windows and swith to "performances" tab.
cpu = between 0 and 1%
2. launch energy xt, right click, folders, and point to your vst folder, then options, and configure your midi in, out, and asio output (I took 512 samples)
3. press F3, click on "Ganymed" and drag it to the main window
cpu = between 1 and 5%
4. play C3 / C4 on your keyboard at about 60 bpm
cpu = 8 to 13%
5. close energy xt, open live demo, configure your vst folder, midi in and asio output with the same latency (512 samples)
6. remove all tracks except one midi track
7. put ganymed on the midi track
cpu = 6 to 18 %
8. play C3 / C4 on your keyboard at about 60 bpm
cpu = 18 to 32 %

so it seems in one case, ganymed takes up to 12% of the cpu (energy xt), and on the other case, it takes up to 26% of the cpu (live demo).

OK, these are not the same apps, but it seems that live needs more cpu power to handle vst and vsti. Am I wrong ? Is it due to my setup ? Would you like to try with other vstis and with the full version ?

Best regards

geoffroy

[Frank Hoffmann]

Which Audio Buffer Size have you set in Energy XT? Set Energy XT and Live to 128 Samples and repeat the test.

Frank

[geoffroy]

Like I said, the latency was 512 samples for both Energy Xt and Live, as it's the latency suitable to my Firewire Audiophile (running on my PC desktop, Athlon 2400 +, Windows 2000).

But here is the test with 128 samples

1. turn on task manager in windows and swith to "performances" tab.
cpu = between 0 and 1%
2. launch energy xt, right click, folders, and point to your vst folder, then options, and configure your midi in, out, and asio output (latency = 128 samples)
3. press F3, click on "Ganymed" and drag it to the main window
cpu = between 4 and 10%
4. play C3 / C4 on your keyboard at about 60 bpm
cpu = 12 to 18%
5. close energy xt, open live demo, configure your vst folder, midi in and asio output with the same latency (128 samples)
6. remove all tracks except one midi track
7. put ganymed on the midi track
cpu = 7 to 18 %
8. play C3 / C4 on your keyboard at about 60 bpm
cpu = 17 to 34 %

Same kind of results.

Any hint ?

Best wishes

geoffroy

[geoffroy]

by the way, the task manager reaches 98 % of the CPU when Live writes 60% CPU.