Stage Lighting
Atmosphere Lighting
Accessories
Signature Series
Events
FX Machines
View All
Your moving head feels jerky because the movement data is too coarse, the mechanics or sensors are fighting you, or your signal and power path are glitching. High-resolution 16-bit pan and tilt provide the fine control needed for glassy-smooth sweeps, while 8-bit control and poor infrastructure exaggerate every bump. Here is how to tell which cause you have and fix it.
From Smooth Sweep to Twitchy Robot: What “Jerky” Really Means
“Jerky” can mean different pain points on show day. Sometimes the beam steps from point to point instead of gliding, especially when you run ultra-slow sweeps. Sometimes it jitters randomly as if the motor is shaking, or it snaps back and forth like it is losing position. Other times it looks more like flicker than motion, where the head jumps unexpectedly or resets mid-cue.
Each version has a different cause. 16-bit pan and tilt is the main tool for smooth slow movement, which means low-resolution control can show up as visible stepping when you slow things down. Poor mounting, bad calibration, or dirty moving parts can also introduce physical stutter even when your DMX math is perfect. Broken belts, misaligned sensors, damaged driver chips, or overheated motors can all make a head shake, lose steps, or lock up mid-move rather than tracking a path cleanly. On top of that, unstable DMX or power often makes fixtures flicker, randomly jump, or misbehave in ways that feel “jerky” even though the motor itself is fine.
The way out is to untangle which part of the chain is causing your particular jerk: control resolution, mechanics and sensors, or signal and power.
Inside the Fixture: Pan, Tilt, and Resolution
Pan is the horizontal swing of the head; tilt is the vertical nod. Both are motor-driven and have defined limits, and understanding each fixture’s movement range is the foundation of smooth control. Every movement cue is really a series of tiny DMX values being fed into those motors.
DMX controllers send values from 0 to 255 on each control channel to drive functions like pan and tilt. That means a basic movement channel is divided into a few hundred discrete steps. When one coarse channel is responsible for the head’s entire pan arc, and you stretch a slow move over that distance, the eye can start to see each micro-step, especially in haze and on long throws. That is the “stair-step” look.
16-bit pan and tilt resolution goes a step further. In practice, this means the fixture uses a high-resolution mode that lets you slice that same physical movement into far finer increments. Instead of jumping from one coarse position to the next, the head can land in very small intermediate points, which is why 16-bit is so closely tied to jitter-free slow movement.
Higher resolution alone does not fix bad programming or broken mechanics, but it raises the ceiling of what is possible. On a fast club sweep the difference might be subtle; on a slow ballad or a camera-tight shot, it is the line between visible stepping and broadcast-ready motion.
8-bit vs 16-bit: Feel, Pros, and Trade-offs
Different DMX channel modes are not just menu clutter; they are movement personalities. Compact beginner rigs often default to simple modes with fewer channels, while advanced “extended” modes allocate extra data for things like 16-bit pan and tilt, advanced color mixing, and fine control. In extended modes on modern hybrid fixtures, each head can consume several dozen channels, while basic modes keep the footprint closer to a dozen or so channels.
You can think of 8-bit vs 16-bit pan and tilt like this:
| Movement Mode | How Motion Feels on Stage | Where It Shines | Trade-offs |
|---|---|---|---|
| 8-bit pan/tilt (coarse) | Steps are more visible on very slow sweeps and long throws; fast moves still look energetic. | Small rooms, simple DJ rigs, shows where movement is mostly fast and aggressive. | Uses fewer DMX channels but limits how smooth you can make subtle or camera-visible moves. |
| 16-bit pan/tilt (high-resolution) | Moves look noticeably smoother on slow fades and precise hits; beams can creep slowly without visible stepping. | Theater, wedding first dances, broadcast, and any show with slow, emotional looks or long distances. | Consumes more DMX channels and may require better planning of universes and console layouts, but dramatically improves the polish of motion. |
The practical difference is most obvious in two situations. The first is a slow, wide pan or tilt across the room: in 8-bit you will often see micro-jumps in the beam, while 16-bit lets that same sweep feel like one continuous flow. The second is when you try to land repeatedly on the same tiny point, such as a logo gobo on a backdrop. High-resolution pan and tilt make those hits feel confident instead of “almost there.”
Buyer’s guides for professional fixtures list pan and tilt speed and accuracy as core comparison metrics, alongside brightness and color systems. 16-bit pan and tilt matters because programmers and audiences can visibly tell when movement resolution is holding back the show.
Why Your Head Still Jumps in 16-bit: Mechanics, Calibration, and Control
Even with 16-bit enabled, a moving head can still twitch, overshoot, or stutter. That is when you stop blaming resolution and start checking the rest of the chain.
Loose Hardware, Belts, and Motor Shake
Mechanical problems translate straight into visible jerk. When pan or tilt belts break, manual movement feels loose and offers little resistance, and the fixture fails to track properly until the belt is replaced. Motor shaking or lost steps can also come from shorted motors that damage driver chips, or from loose screws on gobo and color wheels. Those issues make the mechanics wobble as the motor tries to move, which reads as jitter on stage.
Dirt or debris can block the pan or tilt path, and overheating can damage motors so that they grind instead of gliding. Check belts and motors regularly for grinding or jerky motion, and make sure fixtures sit on stable, level mounts rated for their weight with a healthy safety margin. When the mount flexes, the audience sees every bounce as a micro-jerk in the beam.
If your movement looks rough even in internal test programs, with no DMX connected, you are likely in this mechanical zone. At that point, tightening hardware, replacing belts, cleaning debris, and servicing damaged motors or driver boards are the fixes, not menu tweaks.
Lost Steps and Dirty Sensors
Position feedback is the brain behind smooth pan and tilt. If X and Y axes lose steps or cannot position correctly, the culprits are often dust blocking the optocoupler, a misaligned optocoupler board, loose or broken belts, or incorrectly tightened stepper-motor mounting screws. The Hall sensor and magnet gap also need to be in the right range so the fixture can accurately find its “home” position.
When a head keeps drifting off target, a full reset and reprogramming often restore calibration. If misalignment persists even after that, damaged motors or control chips can be to blame. Regular calibration of pan and tilt zero points using the fixture’s built-in routines, combined with cleaning dust from moving parts and tightening screws, keeps movement free of friction and binding.
When sensors are dirty or misaligned, the fixture thinks it is somewhere else. The result is a head that overshoots, “hunts” around the correct position, or snaps back halfway through a cue. None of that is a resolution problem; it is about giving the fixture a reliable sense of where it actually is.
DMX and Power: The Invisible Jerky Generator
Control and power are the invisible rails your motion rides on. Most flicker is a configuration or infrastructure issue: bad DMX cables, loose connectors, incorrect addressing, overloaded chains, or unstable power, not mysterious fixture “bugs.” Best practices include using true DMX-rated 120 Ω cables, keeping runs within the DMX limit of about 1,000 ft (300 m) and 32 devices per line before adding a splitter, and adding a 120 Ω terminator to stop reflections. Flickering or random behavior is most often a DMX issue, and adding a terminator at the last fixture often cures it.
Signal errors do not just make intensity flutter; they can cause sudden jumps in pan and tilt when the head receives corrupted position data. Give each fixture a unique DMX address with proper channel spacing so that fixtures do not fight over the same data. Long chains with too many fixtures can also weaken the signal, so use an opto-isolated DMX splitter once a line approaches 32 devices.
On the power side, voltage dips and interference can destabilize electronics, leading to resets or twitchy behavior. Overvoltage spikes or an unstable supply can even damage components, and unstable power can make output look dim or flickering, so use stable, surge-protected sources. When your moving head randomly snaps back to home mid-song, that can be a motor, but it can just as easily be a power hiccup.
If multiple fixtures misbehave together, treat DMX and power as prime suspects before you start blaming the individual heads.
A Fast, Real-World Workflow to De-Jerk Your Moving Heads
You do not need a lab bench to fix jerky movement; you need a disciplined order of operations. This order works under show pressure.
Start by isolating one fixture. A simple first step is to connect your controller directly to a single moving head, bypassing the rest of the chain. Set that head to a mode that offers 16-bit pan and tilt or “fine” movement where available. Run a very slow, wide pan and tilt from the console, then try the fixture’s own internal test or auto mode as a comparison. If the movement is rough in both, you are almost certainly looking at mechanical, sensor, or calibration issues. At that point, inspect belts for looseness or breaks, clean dust from vents and movement paths, check for blocked pan or tilt mechanisms, and make sure sensors and mounting hardware are solid.
If the internal tests look smooth but the console-driven moves are jerky, aim your attention at control and programming. Confirm the DMX address matches the fixture mode and that you have not overlapped channels with another head, since addressing mistakes are a top control problem. Then look at how you are programming movement. Use gradual acceleration and deceleration rather than instant speed changes, build smooth sweeps, and balance effect speeds so transitions feel smooth rather than jumpy. If your cues tell the head to jump from a dead stop to full speed, you will see that aggression even in 16-bit.
When the test head is solid, rebuild your DMX path. Swap in known good DMX cables, keep total run lengths reasonable, plug a DMX terminator into the last fixture, and, if you are running many heads, consider adding a splitter to lighten the load on each run. Keep power clean by feeding fixtures from stable, grounded sources away from big inrush devices like fog machines and large amplifiers, following power best practices.
Finally, zoom back to aesthetics. Moving heads are there to lift the mood, not just show off motion. Once your heads are physically smooth, use 16-bit resolution for the emotional beats where you want slow sweeps and precise hits, and reserve faster, more aggressive movement for drops and hype moments where micro-stepping is less visible. High-resolution pan and tilt is not about showing off to other techs; it is about making the movement feel effortless for the crowd.
Programming Tips for Smoother Movement
Once the hardware and signal check out, remaining roughness usually comes from how the move is programmed.
Smooth the move in one place
Give position changes a fade of a second or more instead of snapping. Many fixtures also have a pan/tilt speed channel that slows the motors internally; check the DMX chart, because on many models a value of 0 is the fastest setting. Use one or the other; if both are slow, the head lags and lands late. On a basic controller that only sends coarse 8-bit pan and tilt, try the fixture method: set the cue fade to zero and let a slower speed value set the travel time, so the motor driver moves in its own fine steps instead of following coarse ones.
Shape the path, not only the end points
A crossfade can let one axis finish before the other if the pan and tilt fade times or the speed channel differ. Match the fade on pan and tilt, or build the move with the console's effects engine and waveforms as a line, circle, or figure eight so both axes move together, then set size and speed. On a flat wall or floor, any pan/tilt move traces a slight curve, so place the end points to suit. Shallow arcs at low speed suit slow songs; tighter shapes at higher speed suit drops.
QLC+ line effect for point-to-point moves
In QLC+, a fade between two scenes can move the coarse and fine pan and tilt channels separately, which shows up as a hitch partway through the move. A workaround shared on the QLC+ forum is to use an EFX with the Line algorithm instead. Set the run order to single shot, the direction to forward, and turn off the relative option so coarse and fine channels travel together. To move from position P1 to P2, set the EFX center to (P1 + P2) ÷ 2 and the width to |P2 − P1| ÷ 2, then do the same for tilt with the height. Check the EFX preview first, because one cycle can run to the far end and back. For several heads, put each EFX into a collection and run the collections in a sequence so the heads move together.
FAQ
Do I really need 16-bit pan and tilt on every show?
Not always, but you absolutely need it wherever slow, controlled movement is a feature, not background noise. 16-bit is the main tool for jitter-free slow movement, and pan and tilt speed and accuracy matter as much as brightness and color mixing when you choose fixtures. If you are lighting theater, weddings, broadcast stages, or long-throw venues where cameras or guests stare at the beams for more than a second, high-resolution movement pays off immediately. In a small bar where your heads mostly snap or spin quickly, 8-bit can be acceptable and saves DMX channels, but it will always limit how smooth you can go if you later upgrade the show.
Why do my moving heads look smooth in auto or sound-active mode but jerky on the console?
That is a classic sign that the fixture’s mechanics and sensors are healthy, but your external control is letting you down. Moving heads can run in sound-active or auto modes without any DMX controller, and they often move smoothly there because the internal programs are tuned to the hardware. When you switch to a console and the motion becomes steppy, the issue is usually the DMX mode, addressing, or programming. Different DMX modes change how many channels and what resolution your pan and tilt get, so check that you are actually in a high-resolution mode. Then use gentle fades, smooth speed curves, and well-shaped movement paths instead of abrupt jumps that force the head to slam between points.
Will better power and cables fix jerky movement by themselves?
They will not turn 8-bit into 16-bit, but they can eliminate random jitters and resets that masquerade as movement problems. Poor-quality DMX cables, missing terminators, long overloaded chains, and unstable power are frequent causes of flicker, random behavior, and automatic resets. Cleaning up your infrastructure is like giving your movement a smooth road to drive on. You still need high-resolution modes and smart programming to get truly smooth motion, but without solid power and signal, even the best fixture will dance like it is hitting potholes.
Why does the beam curve instead of moving in a straight line?
A moving head swings the beam on two axes, so on a flat wall or floor any pan/tilt move traces a slight curve, whether it comes from a crossfade or an effect. A crossfade can also let one axis finish first if the fade times or the speed channel differ. Match the fade on pan and tilt, or use a line effect so both axes move together, and place the end points to suit the curve.
Use 16-bit modes where slow moves matter, keep belts, sensors, and mounts in good shape, and run clean DMX and power. That fixes most jerky movement.
