.And why is this (without getting to technical).My only workaround with 5.X is setting the cpu affinty to 1 cpu (winxp) from time to time.It is not really possible to answer this without "getting technical".What is the main difference between the 4.X and the 5.X audio engine in live.
Could you please explain this a bit more? What kind of problem do you get in Live 5.x you can "fix" by bounding Live 5.x to one of the two processor cores?My only workaround with 5.X is setting the cpu affinty to 1 cpu (winxp) from time to time.
Do you have a Live 4 set which when playing in Live 5.x needs significant more CPU? Could you send it to me? (only the .als, no samples)4.X was great and i still use it for final rendering,While 5.X is a real CPUhog
.I was just wondering what changes where made to the audio engine since its cpu usage is much hihger then with 4.X.Like the cpu usage jumps from 70 % to 110 % and then back to 80 % and so on....with 4 VSTi's (Vaz modular,Z3ta+) and 6 live effects.It's almost impossible to make a .als file without haveing the plugins installed, but i will surely try.As for the workaround by setting the affinty to one of the cores,is something i figured out experimenting with different projects.When i'm arrangeing clip's where you need quick GUI respons i use both cores with live,but when i'm working with single instruments and tweaking the sound i use one core...strange? maybe, but it makes the cpu usage more stable.I did not take it as such one, so no problem.This was not ment to be a "Trash Live 5 Tread".
