First, Welcome to the Forum igg.go123 !
Sounds like automation-ID loss, so you are talking about copied blocks of automation -right?LMMS assigns automation to an other, random parameter.
musikbear wrote: ↑Wed Jun 06, 2018 10:57 amFirst, Welcome to the Forum igg.go123 !
Here are all important links:
http://lmms.io/forum/viewtopic.php?f=1&t=4740
-A few rules and useful forum instructions
Sounds like automation-ID loss, so you are talking about copied blocks of automation -right?LMMS assigns automation to an other, random parameter.
They are not assigned to something 'random'
All you have to do, is to re-drag the controller into the 'rogue' automation block. Both the connection and the curve will be re-established.
Best time to do this, is emediately after a block of automation has been copied.
Its a bug. It will be fixed
@zonk : eg its #3781
If i was wrong, and this was not it, then please post your:
* OS subtype (home-pro(?)
* lmms version
Ok.. But have you tried what i wrote -redrag the controller into the automation-block?
I also noticed that happends with copied chanels.musikbear wrote: ↑Wed Jun 06, 2018 10:57 amFirst, Welcome to the Forum igg.go123 !
Here are all important links:
http://lmms.io/forum/viewtopic.php?f=1&t=4740
-A few rules and useful forum instructions
Sounds like automation-ID loss, so you are talking about copied blocks of automation -right?LMMS assigns automation to an other, random parameter.
They are not assigned to something 'random'
All you have to do, is to re-drag the controller into the 'rogue' automation block. Both the connection and the curve will be re-established.
Best time to do this, is emediately after a block of automation has been copied.
Its a bug. It will be fixed
@zonk : eg its #3781
If i was wrong, and this was not it, then please post your:
* OS subtype (home-pro(?)
* lmms version