ForumsSoftware ← 2 Aalto instances -> CPU 700% in Ableton Live (fixed)

Hi,

killer synth, but oftentimes whenever i load an Ableton Live set with 2 or more Aaltos, everything crawls to a halt.
i7-2600k / fresh Win 7 64bit install / Live (32bit host)
A fix would be very much appreciated.

Kind regards
d

This is definitely not typical, so we have to figure out what is causing it. What if you close the Aalto interfaces but leave the sounds running?

Sorry about the delay!
So far the problem has only appeared upon loading a live set (so no GUIs are visible). I then press play and everything crawls to halt. Sound is running, but drum'n'bass style slow'n'stretchy if you know what i mean.
BUT! I just discovered that if i then press stop, delete both Aaltos, CTRL+Z twice, i.e. undo so that the Aaltos are re-inserted, everythings back to normal...
That's good enough for me but if i can be of further assistance, let me know. Might be an Ableton bug after all. GFX is ATI 6850 btw.

Can you get this to happen by running up your CPU use in some other way? The Aalto instances should not be sharing any state, so maybe it's not that you have two of them but that the CPU load is high. Maybe install the DIVA demo or something to hog a comparable amount of CPU :-)

If you get a chance... thanks

Nah, it's not the cpu load. After deleting and re-inserting (same patch) the Aaltos i have maybe a 10% cpu load. My Sandy Bridge is a beast - and i am broke... : )

I ddid not mean "maybe you should get more CPU" but "maybe Aalto is failing under high CPU load." This would explain one working but two not working. I can't think of any other reason two Aaltos would fail where one worked. But I'll see if I can reproduce this.

here's an 18kb set: http://dl.dropbox.com/u/40718/del.als

Just two Aaltos, running my cpu up to 2500% according to Live's meter.

OK, downloaded and will check out soon.

was going to ask if you could reproduce my problem...but upon loading the set i can t reproduce it myself. Using a different audio driver at the moment though so maybe thats the culprit. feel free to delete the thread!

What was the previous audio driver you were using? It would be great to know in case someone else has the problem.

thanks
Randy

Native Instruments Audio 2 DJ...will investigate further once i get the chance!