Thanks for the inputs.
If this should be a OS issue, then why is'nt the issue present in all the applications?
I'm on Windows 10 too though. And the OS can be relevant to fix the issue, without it's a OS issue as such.
The problem is that automap do show you touch a control on you controller - so there are contact, but when you move a control on your controller, then nothing happens in the automap. The automap graphics do not show you move a control on your controller. It only show that control is touched.
If you try to use your mouse to move the graphic control in the automap, then it's the same. It can't move anything.
If anything haapens, then for example the encoders swirps, like the OP mention.
If you try to change the range settings, then it jump back to the wrong behvior the moment you touch the control. And in the first place, there should'nt be this wrong range setup at all.
In my view, this is'nt about creating your own maps or not.
Please Arturia, what can you say about this? It look like it can be a plugin issue, where parameters send out the wrong values and polarities, and interrupt correct behavior. Has adaption to your own controllers and/ or to NKS anything to do, with this? Why does'nt this work?
younusmogul. It's great if you contact Arturia support. Please return if you get it to work. It could save time for Arturia to answer here.
