Hey guys,I know I saw something like this quite sometime ago regarding motorized faders that wouldn't move because they jumped off track, or the belt that moves the fader "de-railed" itself and no longer moves the fader.Specifically this happened on a X32 of mine and it's not under warranty. I'm guessing it couldn't be that difficult to remove the side caps, remove a few screws and attempt to repair it myself by placing the belt back on track.. If any of you have experience in performing this task would be greatly appreciated.Thanks!
Hi Sam-Call the Behringer "care" facility in Nevada and see if you can order a couple of faders and have a local tech replace the defective one.I think someone fixed a jumped belt (or Joe from Berry discussed it) over on Soundforums dot net.
It probably doesn't need replacement, a large number of early units (including ours, we received one of the first units shipped to Canada) have an issue with faders coming off the belt, in our case someone had their hand on DCA 6 fader and changed the fader bank causing the belt to fall off.Our repair tech was able to fix the fader, as well as all the faders on the board per Behringer's instructions. We were covered under warranty, I'd call someone at Music Group and see if they would help you it since it is an acknowledged issue with early units.
in our case someone had their hand on DCA 6 fader and changed the fader bank causing the belt to fall off.
The first time I pressed send on faders on an X32, I had my other hand in the way and a fader hit my hand. It didn't cause any damage but made me wonder if there is any sort of collision detection, and if so, how does it recover?Any ideas?Steve.
More expensive consoles have touch sensitive faders, in particular the SC48 won't move a fader if you have your hand on it, then when you remove your hand the fader will snap to position.I'm not aware of any budget digital consoles with this feature.
Correct, X32 and several others are NOT touch sensitive. Controlled by pulley/gear and belt.
Page created in 0.17 seconds with 24 queries.