Unfortunately that sounds like a faulty touch circuit.
If you are connected to cubase and move the fader in the daw screen, does
the physical fader move with it? If it does, that means the communication from
cuebase back to console is fine. The alias return address should not be used,
it was for setting up a console controlling an engine over the internet.
I'll see if I can dig up any old service docs, but if the touch chip is
faulty, they only way to get it going will be to replace the chip on the board
(if it's still available)... I'll set what other info I can find for you.
Sent from my phone
From: James D'Arcy <james@xxxxxxxxxxxxxxxxxx>
Sent: Tuesday, January 19, 2021 6:08:55 PM
To: tangousers@xxxxxxxxxxxxx <tangousers@xxxxxxxxxxxxx>
Subject: Faders not working with Cubase/Nuendo
I have been given a Tango 1 recently and I am attempting to get it up and
running with my Cubase DAW. I am able to connect successfully and update the
various edit commands to successfully control the DAW transport controls,
However, I am experiencing weirdness with the faders. The symptom is that
whenever I touch a fader the connection indicator flickers. By connection
indicator I mean the small attenuator display at the bottom of the channel
strip: instead of staying on lit solidly it flickers on and off quite fast. The
fader moves but not easily - it's quite a jerky feeling beneath the finger.
Note that this is different from attempting to move the fader with a pencil or
your fingernail where the fader puts up a fight and flicks back to its original
position when released.
I am wondering if this is a comms error wherein the command is sent but the
reply is not making it back. I have tried disabling the firewall on the DAW
with no effect. I have not fiddled with the firewall on the Tango console yet
Would this be related to the :aliased return IP address" setting on he console?
I have not tried this with any other DAW other than Cubase.
All suggestions welcome