I noticed some changes to the OctoWS2811 library that have had a negative impact on performance.
The change with the most impact on performance was this one:
https://github.com/PaulStoffregen/O...11530cd#diff-baf1e8544e6d4607249cff6356e85e46
There's a delay(1) in the MK20DX256 case in OctoWS2811::show(). Is there any reason for that? 1ms is quite a lot of time.
Then there was this change:
https://github.com/PaulStoffregen/O...a5cf39a#diff-baf1e8544e6d4607249cff6356e85e46
Here, the previously configurable frameSetDelay has been hard coded to 300us. Previously it was 50us for 2811. I see the commit comment that 300us is required for newer WS2812B pixels, but what is the reason for not keeping this as configurable?
The change with the most impact on performance was this one:
https://github.com/PaulStoffregen/O...11530cd#diff-baf1e8544e6d4607249cff6356e85e46
There's a delay(1) in the MK20DX256 case in OctoWS2811::show(). Is there any reason for that? 1ms is quite a lot of time.
Then there was this change:
https://github.com/PaulStoffregen/O...a5cf39a#diff-baf1e8544e6d4607249cff6356e85e46
Here, the previously configurable frameSetDelay has been hard coded to 300us. Previously it was 50us for 2811. I see the commit comment that 300us is required for newer WS2812B pixels, but what is the reason for not keeping this as configurable?