Building a new version of MDBT42Q with different libraries.

Thanks - that's a handy one to know as well. Do you know if those separate 255 byte transfers can be chained such that there isn't a pause in the SPI clock? I guess that might screw up the idea of using it as a general purpose neopixel driver.

As mentioned above though, without any concurrency from SPI you're not really going to see that much difference between using hardware SPI or the software SPI implementation though.