procontrol faders aren't accurate?

[uno1234]

Recently I've noticed that my procontrol faders "fall back" to a lower db once I release them.

i.e. I set the fader at -3.0 db, and upon release, the display on the PC shows the fader falling back to -3.3. Why is this?

I've also experienced other performance problems with my procontrol (see thread: "problems with record button on PC" @ http://duc.digidesign.com/ubb/Forum29/HTML/000249.html)

I wonder if it's the ethernet hub being used with only a main unit. Hmm.

[NCM engineering]

I have no problems with one main unit on an ethernet hub. It works fine in all 5 of my edit suites. I am not very hip on the automation. Have you tried the RECAL feature? It has cleared up stuff for me on hanging faders and strange jumps. Use the utility button to get to faders under tests, and select recal. Worth a note.
kelly

[uno1234]

Thanks! I'll try that.

[uno1234]

Is there a way of trashing procontrol's preferences? Or do I just trash the normal prefs on the mac to "reset" everything? I figure it's worth a shot, considering the problems I've been having.

[InSights7]

ProControl has a hard reset in the utilities menu, where you can reset it to factory specifications. My dim switch would not turn off once and I reset my ProControl and all was better.

------------------
Dan Matthews
InSight Sound Recording

[uno1234]

yeah, it didn't fix it.

when look at the fader level display on the pc, the faders fall back between -2.0 and +5.0, but everywhere else, the faders seem to be accurate.

how weird is that?

[Rubgomez]

I have also had a problem with inaccuracies in levels.
Has this ever happened to anyone? When I'm revising a session from stems, I load them into protool and set them at unity. I enable the write automation and proceed to write to the end. Why don't those buttons exist on the pro control, but that's another conference entry. Now my automation is in touch and for some reason my faders that were once at unity are now a couple dB down.
What's up with that!!!! So much for accurate write to the end.
I'm sorry that I didn't have an answer for you.

[uno1234]

this could be related to the 5.1 firmware bug, where the procontrol can send double messages to the system. We'll see if it's still a problem in 5.1.1.