I'm not familiar with Ableton, but is it possible it's just not very efficient with CPU usage? Or that it stresses that particular chip in a particular way? A bit of Googling has revealed that:QuoteAlthough marketed as a dual-core processor, the A6-4455M includes only one module with two integer-cores and and floating-point core. As a result, the CPU is not a true dual-core processor.IIRC effects are done with floating-point mathematics, so it could be that the chip essentially has only 1 core for processing audio.The site also mentioned the chip has something of a "turbo" mode that bumps up the clock speed by a few hundred mHz. I'm not sure if it's triggered automatically under load, or if it has to be manually set. (My Atom required you to manually activate it with the system tray icon.) Short of getting new hardware, I'd look into that, and also the power-saving settings.
Although marketed as a dual-core processor, the A6-4455M includes only one module with two integer-cores and and floating-point core. As a result, the CPU is not a true dual-core processor.
Sharing resources between cores implies a lower peak through put, but not that you somehow only have one core. Separate decode logic will mean that you can very much still benefit from two threads, since its very rare to actually be bottlenecked by FPU on x86. Even if you're working with FP, its very hard to actually saturate all the FPU functional units, so having two cores feeding them will be beneficial.
By that definition, Hyper-threading is more cores and my i7-2600K is an 8 core CPU.
Katatsumuri, try removing (un-installing, not disabling) any and all anti-virus or other "security" software and trying again. It could be trying to scan Ableton's data files when it accesses them and causing the CPU load and disk contention.
What happens when you use the standard audio device instead of Asio4all?
About the number-of-cores issue: what about the multicore support button in the settings of ableton? should I turn it off or on? (it's on now)