Light up every 20th one green and every tenth one red or something, that will help you see how many meters/pixels pretty quickly and you won't have to manually count them, except the last few if you care to be that accurate.
I used it once a couple years ago. It was helpful, but the pixels have to show up in the video. I assume in this case half of them are on the back of the tree...
I would just take note of which controller ports, and how many pixels per string, and which branch they follow. Then, since this is 2D, make a polyline that follows the branches (on background image) and assign that many pixels. You can assign the counts per polyline segment if it ends up off...
That. Everything is near to a controller, and I use the controller ports for power, and if you are doing that you may as well send data too... so, I might have split a dozen ports to get below 300 (spooky tree, fan arches, radio, come to mind) and this was easy because I used standard 50- and...
Well, it's finally done. The show runs at 100 FPS (pay no mind to the P5 panel). Please enjoy this glimpse into my questionable life choices.
At some point, I will write about the adventure in some detail on my site.
So you're saying that the strings have the number of pixels that you ordered, and that the number of pixels on the xLights model matches that, but the two don't meet?
When you are pushing the prop, you should be following the wiring diagram in xLights, and this will show the numbers... the last...
The 750 limit on the Baldrick is per port, so it really does 6000 total. You'd likely use more than one port for the mini tree. I'd probably do 200 seeds per port, that's a very simple way that will work and minimize the amount of joining you need to do and is easy to set up in the software...