Most pixel strings are sold in lengths of 50 and 100 but I'm thinking the better length should be 42 and 84. I'm sure almost all of you know why but for those that don't those counts allow for the maximum number of pixels in one universe.
So the question is would you prefer 21, 42 and 84 or 25, 50 and 100.
timon wrote:Most pixel strings are sold in lengths of 50 and 100 but I'm thinking the better length should be 42 and 84. I'm sure almost all of you know why but for those that don't those counts allow for the maximum number of pixels in one universe.So the question is would you prefer 21, 42 and 84 or 25, 50 and 100.
If the pixel controller supports spanning of pixel outputs across universe boundaries, then there is really not a need to worry about using a specific string length to match a universe size. A single string can be part of a universe, a full universe, or more than 1 universe, it really doesn't matter.
50 pixels is a common size since that's about the max with 5V pixels before getting into trouble because of voltage drop. This is less of an issue with 12V pixels so they often come in longer lengths.
In general, to maximize the capacity of a controller, you want to run out of outputs and universes at about the same time. If you use short strings you will use up all of the outputs first, if you use very long strings then you will run out of universes first.
timon wrote:those counts allow for the maximum number of pixels in one universe.
Why not just modify the software or firmware to use multiples of 50, so it would better match the pixel strings?
don
Single universe controllers cannot have more than 170 pixels, 510 out of 512 channels, so with 50 pixel strings you cannot go more than 150. It's not software but the DMX specification. With 42 per string you can can get 168 pixels or 504 out of 512 channels.
With E1.31 controllers that can span multiple universes across a single string you can get around this.
