Fighting faders

[PTGuy]

I am having another problem with faders fighting back when I try to move them (generally at the beginning of a session). If I try to move the fader it acts like it doesn't want to move and sometimes even snaps back to unity but if I move the volume line down with the mouse the fader will stay down.

Any ideas?

[Bart HLH]

Burst into the same problem now and then. When I mouse click the fader on screen it wakes up again.
I'm on D-Command.

[Chris Lambrechts]

could be a grounding issue ?

Is the unit properly grounded ? is the grounding in the room ok ? - and I'm talking PS ground here , not audio.

Next time you open a session and you expect to be in a situation that will likely 'provoke' the fighting faders try this :

put your fingers well on top of a few faders and wait a second or so before you move the faders. But do pay attention that you are well on top of the faders. How does this go ? Do you feel them fight back or not ?

Now ... let's asume they DO move without fighting ... next time you do the same thing but you wait less long before moving the faders. See what this tells you.

In general the faders should have a pretty fast reaction time after touch. In fact ... you shouldn't be able to notice any latency between touch and move.

report back and tell us what that gives.

[ishur]

I've found that I almost always need to touch the top of the fader for a fraction of a second before moving it or it "fights" me even if automation is off. I assumed this was just normal behavior.

[Reckless Erik]

It is indeed a question of "touch". I have found that the best response is touching the top of the fader with the fingertip. Trying to "flick" the fader with my fingernail or non-organic material results in a fight!!!
Sensitive stuff,
Nick

[mix109]

I will agree with Erik
Yes it indeed a question of 'touch' Even using the thumb on the bottom of the fader will produce the this 'Fighting Back' behaviour
I have gone thru a lot of talkin about this with the Digi people and never got a reasonable answer.
Power outlets have been checked and swapped, but no results.
So you must actually....ride the fader :-]

[DigiTechSupt]

It is indeed a question of "touch". I have found that the best response is touching the top of the fader with the fingertip. Trying to "flick" the fader with my fingernail or non-organic material results in a fight!!!
Sensitive stuff,
Nick

This is normal behavior. Touching the fader creates a change in capacitance that disengages the fader motor. Touching the fader with anything that doesn't conduct electricity will not create the necessary capacitance change.

Is this the situation for you, Arthanor?

[acacia]

I'm on a 24 channel D Command. Utility > Reset seems to clear things for a while when it gets bad. I have to touch the fader firmly for a brief second or two before I can make a move. Some times that doesn't help and I have to reset things. My technical power / ground is great! Monster Pro 3500, all technical power outlets supplied through Surgex SX20 with isolation transformer between not technical panel and large isolated ground... Hasn't always been like this. I don't recall having this issue earlier in PT Vr. 7.3. Been too busy to chase, glad to find I'm not alone. Digi this is more than just a poor touch issue at least once or twice a day I have to reset to get a fader to respond. I always use the underside of my finger. No fingernails, flicking... Tends to be more of a fader pack issue.

[acacia]

Forgot to add... FW Ver. 7.3.0.125, PT 7.3.1 cs3, G5 dual 2.7 Netgear eathernet hub

[mtung]

I am very pleased to read this thread to see that it isn't just me!

I am also experiencing this with both D-commands that we own. Sometimes I can get the faders to come back to life by putting the unit in touch test mode, and then grabbing four at a time I press down kind of firmly and then run them up and down a few times. Sometimes this doesn't work at all. It seems to be a little like it has a mind of it's own. Overall, the faders are mostly fighting these days.

This problem has been going on for quite a while and has continued regardless of software version and/or firmware version. I am using a netgear ethernet hub but have disconnected for testing and the problem remains with or without the hub.

Hope this can shed some more light on the problem so that we can get a fix.

mike