I missed a part of your question 20fps results in slightly choppy transitions when you are trying to do a smooth fade or color change over time. Call it a bit of flicker that you may sense rather than see. 40fps reduces that effect too something the eye cannot see.
And one more thing. 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. Set it to 600 pixels and you will be given the option to use a 40fps refresh rate.
MartinMueller2003 wrote:And one more thing. The reason the FPP 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. Set it to 600 pixels and you will be given the option to use a 40fps refresh rate.
OK, thanks for the detail, I think I understand it better now.
-mc
MartinMueller2003 wrote: Set it to 600 pixels and you will be given the option to use a 40fps refresh rate.
I think I know what you meant, but that wording can be misleading. You are not given the option. The controller will use a fixed rate of 40fps unless any string port is configured over 800 pixels then it uses a fixed rate of 20fps.
I know this is going to make things more confusing, but the entire concept of multiple independent frames at different layers in the show equipment running asynchronously can be a hard concept to get through. On with my response:
That is the controller WS281x frame rate for the controller. That is a seperate frame rate from your show frame rate. This is where things can get very confusing. Some controllers use an internal frame and resend the last data they have received from the show player at that rate. Other controllers send the data over and over as fast as they can (the controller internal frame rate can go up as the pixel string length goes down). Yet other controllers send the data they receive from the show player once (they do it as fast as they can) and then stop sending anything (PX1 and ESP do this).
The next layer of frames is the rate at which the show player sends data to the controllers. This is the frame rate most people are referring to when they talk about 'the' frame rate. You configure the show player to send data to the controller at a fixed rate. I use a frame rate of 25ms (40fps) many people use 50ms (20fps). The show player will send the data to the controller at the selected rate, even if the controller cannot send the data out to the pixels at that rate. A good controller will overwrite the internal data with the new data and send the new data to the pixels as soon as it can (the next frame).
The less expensive controllers (like the PX1 or the ESP) would end up dropping the data if it did not have enough room to buffer it. The buffering available in a device like the ESP is pretty small and sending it too much data can result in lost transitions that look like lag. The PX1 has a 250 byte buffer and the sending device (show player etc) may be buffering the frame data so you could get lag due to a serial link speed that does not support your show frame rate.
I hope this helps a little.
