LMMS • Forums

Every so often, when I try to use an automation track, I can't associate it with a control, like volume or pitch, because the control just flies back to where it was without applying it to the automation track. This has only happened to me when using the macOS version of LMMS, it does not do this on the Windows build.

First off, Welcome to the Forum Srinpy !
Here are all important links:
http://lmms.io/forum/viewtopic.php?f=1&t=4740
-A few rules and useful forum instructions
If you like to introduce yourself, to the community, go here:
http://lmms.io/forum/viewtopic.php?f=4&t=4480

Srinpy wrote: ↑

Thu Jun 06, 2024 10:33 pm

Every so often, when I try to use an automation track, I can't associate it with a control, like volume or pitch, because the control just flies back to where it was without applying it to the automation track. This has only happened to me when using the macOS version of LMMS, it does not do this on the Windows build.

That sounds like a bug
What version of lmms do you have installed, and is it from our hp?
I dont have any MAC so i have no insight in this, btw
I only know one MAC-USER so i will refer this to him.

Srinpy wrote: ↑

Thu Jun 06, 2024 10:33 pm

Every so often, when I try to use an automation track, I can't associate it with a control, like volume or pitch, because the control just flies back to where it was without applying it to the automation track. This has only happened to me when using the macOS version of LMMS, it does not do this on the Windows build.

Confirmed. Similar issues have been reported in the past. One workaround was to hold the "Option" key after "Option" + dragging has started. It doesn't work, but "Ctrl" sort of does. The timing is really hard to get right because you have to start clicking with "Option" and then hit "Ctrl" before you've moved the mouse.

LMMS is open source, so any help with the code is greatly appreciated. Most of our fixes were submitted by users like you.

https://github.com/LMMS/lmms/issues/2890
https://github.com/LMMS/lmms/issues/3745

So it turns out letting go of Command before dropping also fixes this. We're still looking into how to fix it properly though.