(Windows) Automation doesn't work correct

Having trouble with LMMS? Ask about it here.
When I make an automation to some parameter ,close and open my project, LMMS assigns it to an other, random parameter. I'm running it on windows 10 64bit.
What version of lmms are you using?
igg.go123 wrote:
Tue Jun 05, 2018 1:09 pm
::
First, 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
LMMS assigns automation to an other, random parameter.
Sounds like automation-ID loss, so you are talking about copied blocks of automation -right?
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
musikbear wrote:
Wed Jun 06, 2018 10:57 am
igg.go123 wrote:
Tue Jun 05, 2018 1:09 pm
::
First, 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
LMMS assigns automation to an other, random parameter.
Sounds like automation-ID loss, so you are talking about copied blocks of automation -right?
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

I think i'm using windows pro
I'm using lmms 1.2.0 rc5
igg.go123 wrote:
Wed Jun 06, 2018 12:14 pm
I think i'm using windows pro
I'm using lmms 1.2.0 rc5
Ok.. But have you tried what i wrote -redrag the controller into the automation-block?
If that 'fixes' it, it is a known issue, nothing need to be done now, but if not, its a new one, and devs have to look at that too
musikbear wrote:
Wed Jun 06, 2018 10:57 am
igg.go123 wrote:
Tue Jun 05, 2018 1:09 pm
::
First, 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
LMMS assigns automation to an other, random parameter.
Sounds like automation-ID loss, so you are talking about copied blocks of automation -right?
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
I also noticed that happends with copied chanels.
igg.go123 wrote:
Wed Jun 06, 2018 6:05 pm
I also noticed that happends with copied chanels.
DO this!
-redrag the controller into the automation-block!
does it solve the problem?