motorized device

[grego mondo]

Hi, goodyear and michelin !!

I use a Xtouch mini and other midi controllers (not motorized) I tried to assign the same control change to a pot of the Xtouch and to that other controller, that works fine.
I have one fader midi learned to that controller(s) and whatever controller I move the fader moves (great)
I told that fader that he is a motorized device, so when I move the fader (with the mouse) I receive the info on the X touch pot as wanted ...
BUT :
When I move my other controller (that moves my fader) I don't get the X touch pot moving (lighting would be correct) until I update my motorized device
SO :
I guess data's are send to the device only if the fader is changed from computer and not if it's changed from a midi signal (to avoid a loop in the motorized device)

MY QUESTION (at last)
Is there a way to change this behaviour ?

If not I still can update the motorized device when I need it but I would like to use it as a visual loopback

hope my english is clear (is my mind clear enought ?)

[nay-seven]

If i understand correctly, us a first knob, invisible, midi learned by your other controller, >pass if change> your X touch knob ?

[grego mondo]

Nice trick, thanks but I try to control a rack fader
maybe I can have this fader midi-learned (motorized) by my X touch and an invisible knob that is "bind-learned" by my fader ?

[nay-seven]

you can use the same system linked to the gain out inlet of a rack settings module

[grego mondo]

thanks