Ableton Forum

tintala wrote:since upgrading to 9.4 and cannot use Maschine anymore due to the cpu .

9.4 of what? Are you talking about a beta like 9.6b4?

I think it's safe to say something— I don't know… odd?—  happened with 9.6. Currently though in OS X 10.11 (El Capitan) in the Live 9.6.1b6 and b5 before that everything goes really smooth for me. It's like the issues never happened. Overall I'd say 9.6 feels like an improved version, but it's certainly possible that certain set ups will cope differently with any changes Ableton have made. I suppose that's nothing new in itself.

So is it caused by OS X 10.11?

pencilrocket wrote:So is it caused by OS X 10.11?

Sure, there could be a lowest common denominator like the OS but I don't think so. I for one have seen better performance than ever in 10.11 on a 2009, a 2012 and a 2015 MBP. The perception I arrive at is that the code changes in Live 9.5 and later seem to be targeting performance and efficiency (and many other things) and for whatever reason you may run into the occasional set up where there are sudden transient problems with performance, not without having to do some typical problem fixing set of actions. To me these have worked on the only box where I've seen issues (2009 MBP).

Iv had this issue with Traktor too. Turns out it was the multicore support in the options. Tried turning it off in Live 9.6 and instantly lost the spiking of the CPU meter.
Im running win 10, Live 9.6 x64. Hope this helps others.

I had similar problems but could figure out that it was due to the komplete kontrol vst. Using Massive or Kontakt directly resolved this.

i hope this will get fixed soon.

Stromkraft wrote:

pencilrocket wrote:So is it caused by OS X 10.11?

Sure, there could be a lowest common denominator like the OS but I don't think so. I for one have seen better performance than ever in 10.11 on a 2009, a 2012 and a 2015 MBP. The perception I arrive at is that the code changes in Live 9.5 and later seem to be targeting performance and efficiency (and many other things) and for whatever reason you may run into the occasional set up where there are sudden transient problems with performance, not without having to do some typical problem fixing set of actions. To me these have worked on the only box where I've seen issues (2009 MBP).

Since I've moved to a later 4-core MBP and while I've seen the occasional crash, like once or so, I have about no production issues whatsoever. I just moved my old SSD to the new one, after having taken licenses off it, adding them back with the new machine.

I have noticed crashes lately when there used to be none specifically when using NI, Battery, Reaktor and Guitar Rig. The crashes seem to be happening while using midi controllers.
The os Im using is OS X 10.11.4

I have messed around with Diva a bit, but most of the time I am running two tracks using NI stuff.

I am experiencing the opposite: my live set, with countless native and 3rd party plugins (snyths and FX) used 7.89 GB RAM and up to 40% CPU (Windows Task Manager), it's a pretty old lenovo laptop with 8 G RAM and a mobile i7 @ 2.8 Ghz.

With the update to live 9.6, the Task Manager reports 5.52 G RAM and 20% CPU, same live set same computer.

After a laptop crash 2 days before my last live gig (and spleepless nights fixing the junk) i was considering, for the first time in my life, to ditch windows (after 20 years music making with it) for apple, but it looks like i'll stay on Win7.

Emanresu0891 wrote: Reaktor

Which synths? I use Razor and Monark without any issues.

Did you investigate if Komplete Kontrol could be involved?

störgeräusche wrote:looks like i'll stay on Win7.

I'd recommend upgrading to 8.1. Things are quite stable. Install Classic Shell, and it's a slicker Win7. Win7 was EOL for mainstream support in January 2015, and is on "we're just patching things because some big enterprise customers won't switch right now" support. I can't think of any VSTs or music programs I use that have issues on 8.1. I use Acid, Live, Serato DJ, FL, and a bunch of other stuff without issues; even bridging 32-bit VSTs with jbridge works rather well.

Not that I had trouble with 7. And not that you should upgrade if it's a hassle in your situation. Just throwing out there that 8.1's nice if you're looking for an OS change.

contortrix wrote: I'd recommend upgrading to 8.1.

How do you do that these days?

contortrix wrote:

störgeräusche wrote:looks like i'll stay on Win7.

I'd recommend upgrading to 8.1. Things are quite stable. Install Classic Shell, and it's a slicker Win7. Win7 was EOL for mainstream support in January 2015, and is on "we're just patching things because some big enterprise customers won't switch right now" support. I can't think of any VSTs or music programs I use that have issues on 8.1. I use Acid, Live, Serato DJ, FL, and a bunch of other stuff without issues; even bridging 32-bit VSTs with jbridge works rather well.

Not that I had trouble with 7. And not that you should upgrade if it's a hassle in your situation. Just throwing out there that 8.1's nice if you're looking for an OS change.

I might consider it -even if I still believe in never changing a running system -it appears the problems of my laptop were hardware related, i deactivated the NVIDIA card and things run smoothly now.

Ahhhh, I haven't seen that one come up in a while. I've had nvidia in my laptops since about 2008 and never personally experienced this, though I recall it being a thing for several people with nvidia cards trying to run a DAW.

You probably have an nvidia driver causing latency issues.
http://www.resplendence.com/latencymon
http://www.thesycon.de/deu/latency_check.shtml

You may be able to find a driver that doesn't cause these latency issues, but that might take a lot of driver installs / uninstalls to identify.

contortrix wrote:Ahhhh, I haven't seen that one come up in a while. I've had nvidia in my laptops since about 2008 and never personally experienced this, though I recall it being a thing for several people with nvidia cards trying to run a DAW.

You probably have an nvidia driver causing latency issues.
http://www.resplendence.com/latencymon
http://www.thesycon.de/deu/latency_check.shtml

You may be able to find a driver that doesn't cause these latency issues, but that might take a lot of driver installs / uninstalls to identify.

i can confirm this. i had the issue on an XP machine circa 2007. i disabled Write Combining to resolve it.