Ableton Forum

Hi,

I have a very simple set - one audio track containing a 30 second wav. I have zero plug-ins loaded, zero Live devices, and the CPU meter reads about 2-3% when playing the file.

(MOTU Ultralite buffer settings are fine at 80% CPU set-up test, so I should have plenty of buffer.)

However, when I slice that wav to midi, I get an audible click/pop.

This can't be correct behaviour, right?

There's a really good torrent of 8.0.1 and it's stable as fuck!

Honest...

Z.

Rinsemeister wrote:There's a really good torrent of 8.0.1 and it's stable as fuck!

Honest...

Z.

??? What's that got to do with anything?

Everything...............

I was just trying to be helpful in a humorous kinda way.

I have used a CRACK and found it to be free from a lot of
the shit that is complained about on this forum.

Go figure............

Z.

Not like the text bollox that I've just had to deal with......

Z.

OS X users

Download and install the application "Coolbook" (http://www.coolbook.se). Turn the CPU load slider up until the clicks disappear (likely needs values higher than 5). This will force your CPU into its highest clock-rate and effectively turn off Speedstep.

The CPU Load slider is available in the free trial version, switching the CPU clock to a fixed state is only available for paid users. Unfortunately it doesn't work as promised on current Core2Duo Macs unless you are doing some more trickery (and even then the CPU load slider remains the best working option).

Windows Users

Open Task-Manager, right-click on Live.exe and change Live's "Priority" to "Realtime".

You can also try to defeat Speedstep by running some additional CPU load in the background (like Prime95 which runs at lowest priority).

If you are using Bootcamp on a Mac you also need to perform several tweaks, including turning off KBDMGR.EXE (I made a script for that), updating your WLAN driver and checking your graphic-card driver's behavior: http://www.rme-audio.de/forum/viewtopic.php?id=4320

Non Bootcamp/Mac users might want to have a look at the possible tweaks as well.

T1mur wrote:OS X users

Download and install the application "Coolbook" (http://www.coolbook.se). Turn the CPU load slider up until the clicks disappear (likely needs values higher than 5). This will force your CPU into its highest clock-rate and effectively turn off Speedstep.

The CPU Load slider is available in the free trial version, switching the CPU clock to a fixed state is only available for paid users. Unfortunately it doesn't work as promised on current Core2Duo Macs unless you are doing some more trickery (and even then the CPU load slider remains the best working option).

Windows Users

Open Task-Manager, right-click on Live.exe and change Live's "Priority" to "Realtime".

If you are using Bootcamp on a Mac you also need to perform several tweaks, including turning off KBDMGR.EXE (I made a script for that), updating your WLAN driver and checking your graphic-card driver's behavior: http://www.rme-audio.de/forum/viewtopic.php?id=4320

Non Bootcamp/Mac users might want to have a look at the possible tweaks as well.

Timur - you've been allowed back on here? Give me $10 and I'll try the Coolbook route...

Like I already wrote, you can use the free trial version of Coolbook for using the "CPU Load" slider!

No, I'm still banned, but as you can see by all the "essay writing" spam the forum currently doesn't check who is creating accounts. So I thought I make use of the minutes before I'm caught and try to help some people.

Nope, didn't make any difference at load = 5, 6 & 7. 10 killed my soundcard. Only change in sound was that my fans went into overdrive.

Great "advice".

Sorry for the inconvinience. If producing 100% CPU load kills your soundcard you should worry about its driver quality though.

Seems as if in your case the click is produced by the slice function and not by a CPU/buffer problem.

PS: The reason for your fan turning up with the "CPU Load" slider of Coolbook is just that: it creates CPU load (which in turn keeps Speedstep from clocking down your CPU).

T1mur wrote:Then in your case the click is obviously produced by the slice function and not by a CPU/buffer problem.

Where did I say it was a CPU/buffer problem? I just posted the config for Ableton support's information including info about no plugins or devices (e.g. it's not a look-ahead problem). To say the click is obviously produced by the slice function brings zero additional information.

T1mur wrote:The reason for your fan turning up with the "CPU Load" slider of Coolbook is just that: it creates CPU load (which in turn keeps Speedstep from clocking down your CPU).

Please stop explaining the blindingly obvious as if it's useful new information.

I don't see what gets you upset. I suggested one possible solution to your problem and it didn't help. There are plenty of unrelated things happening on a computer that can produce clicks. It's not like the Slice function *has* to be the cause, it could just be the victim. Whatever... just forget that I tried to help you and go on living a happy life.

T1mur: Sorry, fixed.

Bye,
Dom

Thanks Dom.

Regarding the original issue - it's pretty much reproducible - any extra info/files you need to fix it?

Edit: I guess this should be in the Live 8.0.x Beta Bugs forum, not here anyway...

fake_account wrote:I'd like to apologize for having misunderstood the original issue. I did not realize that the clicks are so very specifically bound to the Slice function, but thought this to be just an example of overall click-experiences.

Timur? Again?