MartinMueller2003 wrote:The reason the F16 is setting the max frame rate to 20fps when you have 1000 WS281x pixels selected is because that is the max rate that the WS281x protocol can refresh 1000 pixels.
Is this a restriction with the F16 itself? (The WS281X protocol at 800 KHz takes 30 usec/node so 1,000 pixels would be ~ 30 msec, equivalent to 33 FPS)
don
1024 is the controller max per port. The ws281x protocol limit is more like 1600 pixels per frame at 20fps. The controller will run up to 800 pixels per port at 40fps unless any strings are longer than 800 then it runs all ports at 20fps.
djulien wrote:Is this a restriction with the F16 itself? (The WS281X protocol at 800 KHz takes 30 usec/node so 1,000 pixels would be ~ 30 msec, equivalent to 33 FPS)don
The common choices in the show player are 25ms, 50ms and 100ms. The F16 is simply going to the next slower common frame rate. Your calculations forget the 150us inter frame gap. 50ms would stop being viable around 1300 nodes.
pixelpuppy wrote:1024 is the controller max per port. The ws281x protocol limit is more like 1600 pixels per frame at 20fps. The controller will run up to 800 pixels per port at 40fps unless any strings are longer than 800 then it runs all ports at 20fps.
Hmm. We are getting different numbers. My calculations show 40fps using WS281x pixels can support up to ~650 pixels. I tell generally people to stop at 600 (a nice round number).
600 is definitely a good number to use. Technically, according to ws2811 spec, 800 pixels should take just over 24ms. However, that doesn't really leave much time for anything else. Also, there are other issues that can come into play. See my writeup on the PiCap:
https://falconchristmas.com/forum/index.php/topic,10055.0.html
where a jump from 600 to 620 suddenly adds 5ms. Still no idea why.
