Yep! Pixel data signals can be read by many strings at the same time. Each parallel path does not change how much calculation Pixelblaze has to do.
“Pixelblaze has a single output capable of supporting the various LED types up to 5,000 APA102 LED or 2500 WS2812 LEDs.”
Means that a very, very long string can be used before you hit hard limits. Practically, the maximum you would design a system for will depend on the frame rate you want to achieve, and for some patterns the memory available. Calculating a huge number of pixels will be slow, and the animation frame rate will be low and won’t look as smooth/fluid and would only be suitable for slow fading patterns.
For your number of pixels, 200, you will not run in to any of these limits or issues, and would have good frame rates and be able to run any of the patterns you like.
Here are the rendering benchmarks listed on the product page which can help you estimate your FPS
(frames per second) capability. I would note that it will be slightly lower for WS2812 type LEDs, and the tests were done with APA102 type LEDs, but you can still use this to get an idea:
Using included patterns as a benchmark, Pixelblaze V2 can generate between 12,000-45,000 pixels per second.
- 100 LEDs: 120-400+ FPS (very fast animations, special effects, POV)
- 1000 LEDs: 12-40+FPS (animations, backgrounds)
- 5000 LEDS: 2-4+ FPS (slow-fading backgrounds, ambiance)
From this data you can see that 200 pixels will give you very good frame rates on V2.
The new Pixelblaze V3 is on average 2.6X faster, while maintaining the same 5,000/2,500 pixel maximum:
||Extremely fast/smooth animations, special effects, POV (persistence of vision)
||Beautifuly smooth animations
||Gradual animations, fading backgrounds, ambiance