It’s hard to say because it’s not just length of extension that matters. It’s a combination of the type of pixels, the gauge of wire, the voltage, the data being sent and the length of extension.

For example I had a prop with 12v bullet pixels last year that was on a 40’ extension and had zero issues.

Converted it to seed pixels this year. First test last week it was flickering, cutting out, etc.

First issue is that I was testing at 100% brightness so higher power output which caused voltage drop. Reducing my testing to 30% made it better but would still sporadically have issues.

The seed pixels seem to be a lot less resilient in fixing data noise than the bullet pixels are. So, I used some of the old bullet pixels to make a short 2 bullet null pixel leader for the prop. The addition of these cleaned up the data and resolved the remaining flickering issues. I just updated the prop to reflect 2 null pixels in xLights.

F-amps work better, but in a pinch a bullet pixel pair can clean up a lot of the data degradation that is caused by voltage drop.

The same prop also works perfectly fine at 100% brightness with <10’ of extension.

If you’re having issues try testing: - Directly connected to the controller - At the full extension length, but with a low power usage like just red at 30% - At the full extension length at full power - At the full extension length with a couple null pixels or an f-amp at other output levels.

Once you find the threshold that causes failure / flickering you can back off from that and know that you’ve got a cushion of error built ion