Audio Clips "sticking" to mouse cursor

[PihkaLT]

Hi! So this problem started yesterday and it's pretty much killed the workflow at our studio.

When editing Audio Clips' length in Arrangement, very often the mouse "sticks" onto the clip, like I still held the mouse button down. Won't come off. When I move my mouse with no buttons pressed, the clip just keeps on shortening or lengthening. After about a minute everything works again. Until at some point the cursor sticks again.

Anyone with the same problem? I found a thread on this forum from 2009 with similar issues, but it wasn't much help.

Using Live 10 Suite on Windows 10 Pro, i7 8700K, 48Gb RAM, RME RayDAT.

Thanks in advance,
Lasse / PihkaSound

[Tarekith]

Battery in the mouse dying?

[pottering]

Last time I saw a similar problem, it was the fancy non-standard mouse software.

[PihkaLT]

Yep, thought about the battery in the mouse dying too. Although this problem exists only in Live, not in for example Davinci Resolve. Changed the batteries anyway, no help.

What "fancy non-standard" mouse software are we talking about? I've got a seemingly standard Logitech mouse with no other software but Windows' own, as far as I know. Last time you saw this problem, what was the solution more precisely?

[pottering]

Searching my browser history for "mouse", I found a older post in another forum saying that "smooth scrolling setting in the Logitech software" caused them problems (though I was remembering another older post that is not in my browser history anymore).

[Tarekith]

Logitech has software you should install for their mice, it's called "Logitech Options". Try that and see if it improves scrolling, as there's some additional settings in the software that might help.

[PihkaLT]

Thank you for the advice everyone! I don't have the Logitech software installed. I will try it.

[TheCoil]

This happens to me too, I don't have a Logitech mouse either. It's infuriating.

[[jur]]

This happens to me too, I don't have a Logitech mouse either. It's infuriating.

Did you try using another mouse?
Did you update anything (e.g OS, drivers...) recently?

No need to create a duplicate thread, so I deleted it. Thanks.

[Froschfinger]

I have just reported this bug to Ableton, but wanted to chime in here: Did anybody find a solution, or is everyone still, like me, experiencing this problem on Live 11? As Live 11 is more intense on the CPU, this now happens even more often than in Live 10, and it's driving me nuts. It's not depending on any specific input device (tried different mouses and also a Wacom tablet throughout the years this has happened) as it seems, and affects both the Beta and stable versions of Live 10 and 11.

[knoxvilletim]

Hi ... Yes I'm having this issue but only on one audio sample. It doesn't happen on other audio samples. So for me at least, it isn't due to the mouse. I've tried consolidating the sample, changing the warp settings and it doesn't help. I'm going to try to continue to see if I can find a correlation with something else that may give insight into what's going on. Frustrating for sure!

[Tarekith]

There’s been a few reports of this, contact support@ableton.com and see if they can help sort you out.

[Froschfinger]

There’s been a few reports of this, contact support@ableton.com and see if they can help sort you out.

For me, they came up with rather general advice, like reducing CPU usage by freezing tracks, which didn't help a bit. Here's to hoping they'll find the problem.

[[jur]]

There’s been a few reports of this, contact support@ableton.com and see if they can help sort you out.

For me, they came up with rather general advice, like reducing CPU usage by freezing tracks, which didn't help a bit. Here's to hoping they'll find the problem.

Did you send them a live set containing the offending sample/clip?
Btw, if you drag this clip into a new set, does the problem still occur?

[Froschfinger]

There’s been a few reports of this, contact support@ableton.com and see if they can help sort you out.

For me, they came up with rather general advice, like reducing CPU usage by freezing tracks, which didn't help a bit. Here's to hoping they'll find the problem.

Did you send them a live set containing the offending sample/clip?
Btw, if you drag this clip into a new set, does the problem still occur?

From what I remember, I did send a Live set in which it happens. It though is almost always reproducible once a certain threshold of CPU usage is reached. In my case, as many others also reported, it's not the offending sample, but occurs with each and every MIDI and audio track in those sets. This has even increased in Live 11. Since it seems to be dependent on the CPU usage, of course new sets do not have this problem, be it with new or clips from one of those problematic sets.