Running water lights: how flow effects work, and how to tune them
A running-water light does not move. Nothing travels along it. Groups of LEDs switch on and off in sequence and your visual system assembles that into motion — which is why the settings that control it are about timing, not about speed in any physical sense.
Two completely different products with the same name
"Running water", "chasing", "flowing" and "sequential" get used interchangeably in listings, but they cover two hardware types that behave differently. Knowing which you have determines what you can tune.
Fixed-group chase
The strip is divided into a small number of hard-wired groups — often two, three or four — and the controller switches between them. The pattern is built into the wiring, so you can change how fast it cycles and which colour it uses, but not the shape of the movement. Flow always steps by one whole group.
Addressable flow
Every LED, or every small cluster, has its own address. The controller decides individually what each one shows on every update. Movement can be any length, any direction, any number of simultaneous pulses, and it can be smooth rather than stepped.
You can tell them apart in ten seconds. Set the light to a slow flow and watch a single transition. If light jumps in visible blocks that are always the same size, it is a fixed-group chase. If the leading edge advances a little at a time and you can see a gradient between lit and unlit, it is addressable.
The question we get most: can my RGB strip be made to chase? No, and no app or firmware will change it. On a plain RGB strip all the LEDs share three connections, so whatever you send arrives at every LED simultaneously — the strip is physically incapable of showing two colours at once. Chasing requires either separate wired groups or per-LED addressing. If the strip shows one colour at a time across its whole length, that is the end of the story.
Segments and pixels are not the same number
On addressable lighting there are two counts, and mixing them up is behind most "the effect does not fill my strip" reports.
- Pixel count — how many independently controllable points physically exist. This is a property of the strip. Count them or read it off the specification.
- Segment count — how many groups the effect is drawn in. This is a setting. Ten segments on a 100-pixel strip means each segment is ten pixels wide and they all change together.
Segment count is a resolution control for the effect. Fewer, larger segments give bold blocky movement that reads clearly from across a room. More, smaller segments give fine smooth movement that reads well close up and can look like nothing at all from a distance. Neither is a quality setting — it is a viewing-distance setting.
Set the pixel count correctly first. In our apps it is the Pixels entry in the settings pop-up. If the controller is told the strip has fewer pixels than it does, the effect stops short and the tail of the strip sits dead or frozen. If it is told there are more, the pattern is compressed and the last part of it never appears. Either symptom looks like a hardware fault and is a single number in the device settings. Count the pixels on the physical strip — the listing is sometimes for a different length of the same product.
What flow actually looks like
These are previews from our own control app, drawn on a coiled strip the way it sits on the reel before you install it. The coil is worth looking at rather than a straight line: it shows the same thing every installer discovers, which is that a flow effect reads by its direction and its wavelength, not by any single frame.
App effect previews, not photographs. Two things a preview cannot show you: on a real installation the strip is usually partly hidden in a channel or behind a cove, which softens every edge, and a long run has visibly more travel time end to end than a short one at the same speed setting.
Speed: what it actually controls, and its two limits
The speed setting changes how long each frame is held before the pattern advances. Two hard limits sit at either end of the range, and knowing them saves a lot of fiddling.
Too slow and it stops reading as motion
Below roughly one step every half second, your eye stops linking successive frames into movement and starts seeing them as separate events — lights blinking in turn rather than something flowing. If a slow setting looks like blinking rather than flowing, that is why. The fix is to increase segment count rather than speed: smaller steps at the same rate read as motion again, because each individual change is smaller.
Too fast and it stops reading as motion the other way
Past a certain rate the whole strip appears uniformly lit with a slight shimmer. The pattern is still there but it is advancing faster than your visual system can resolve, so it averages out. Fast flow always looks better on a strip with a high pixel count, because the movement per frame is smaller relative to the whole.
The useful middle for most decorative installs is a full traverse of the run in one to three seconds. Longer feels sedate, which suits a quiet room. Much shorter looks frantic and, on camera, turns into strobing.
Direction, and why it matters more than it should
Direction reverses the order the controller works through the chain. Simple in the app, but the result depends on how you installed the light, and that is where confusion comes from.
The chain starts at the controller. That is the origin, always. So "forward" means away from the controller — and if you mounted the controller at the right-hand end of a run, forward looks like right-to-left movement. On a symmetrical install, two runs wired outward from a central controller will flow in mirror-image directions when both are set to forward, which is either exactly the effect you wanted or exactly not.
Our advice, learned from installs done the hard way: decide which way you want movement to go, then mount the controller at that end of the run before fixing anything down.
Fixing direction in software afterwards works, but not for every effect. Some built-in modes have direction baked into the mode itself rather than exposed as a setting — in our apps they come as matched pairs, Magic Forward and Magic Back, and you choose between them rather than flipping a switch. If an effect you like only runs one way and has no direction control, look for its counterpart in the list before concluding it cannot be reversed.
Two practical notes from that screen. The speed control carries a numeric value, so when you find a setting that looks right, write the number down — it is far easier to restore than a slider position. And Auto Play cycles through modes on its own, which is a good way to audition effects on a new install and a poor way to leave a finished one, because it will eventually land on something that does not suit the space.
Where flow effects genuinely earn their place
Flow works when there is a line for the eye to follow. It falls flat when applied to a shape with no obvious path.
| Works well | Why |
|---|---|
| Eaves, rooflines, fascia runs | A long unbroken line with a natural start and end. Flow traces the outline of the building |
| Stair nosings | Discrete steps map naturally onto discrete segments, and the direction can follow travel |
| Handrails, corridor edges, coving | Long, continuous, seen along their length rather than across |
| Vehicle exterior trim | Strong lines, and sequential movement reads clearly at a glance |
| Works badly | Why |
|---|---|
| Behind a TV | Movement in peripheral vision competes with the picture. Bias lighting is the right answer here — see TV backlight sizing |
| Under kitchen cabinets | It is task lighting. Moving task lighting is worse task lighting |
| Short runs under about a metre | The traverse is over before it registers. Use a fade or a breathe effect instead |
| Bedrooms, if it stays on | Continuous movement in a dark room is far harder to ignore than continuous light |
A word about vehicles
Sequential flow is popular on cars and motorcycles, and it is the one application where the settings are not purely a matter of taste. In many countries the colour, position and flashing behaviour of anything visible from outside a vehicle is regulated, and a decorative flow effect can put a vehicle out of compliance even when the original lamps are untouched. We cover the specifics in car interior ambient lighting and motorcycle rear lighting. Read one of those before planning an exterior flow install.
Common questions
The flow stutters or hesitates at one point every cycle
A repeatable hesitation at the same physical place points at a joint in the run — a connector where the data signal is marginal. It is repeatable because it is physical. A stutter that moves around, or affects the whole run, is more likely to be the controller being asked for a very high update rate on a large pixel count.
Colours are right but the movement is backwards
Direction setting, or the controller is at the other end of the run than you assumed. Neither is a fault.
The first few pixels behave differently from the rest
Check the pixel count setting, and check whether the strip's first segment is a different length than the others — some strips have a partial group at the head, and the effect will treat it as a full one.
Colours come out wrong entirely
That is channel order, not the flow settings. Correcting the pin sequence covers it.
Which app runs a running-water light?
Our dedicated running-water controllers run on LightsPlay; general addressable strip runs on Magic Lantern. The mapping for all forty categories is here.
Ask us if you are planning a long outline run and want the pixel count and speed sanity-checked.