very weird problem… always had no problems using FastLED with WS2811’s for projects. got them out again for an installation and they were acting funny – tried w/ 3 different arduinos – all producing same problems (i think timing related). i initially thought the WS2811’s were messed ,but i have DMX controller for them and they are working absolutely fine.
I haven’t changed/updated any drivers that I am aware of, but is it possible that a Java library got updated and now the timing is messed up at the compiler level?
i’ve reprogrammed the 3 arduinos on win/ubuntu, all producing same errors). i do not wish to use DMX to control this matrix display
(Folks, once again, for quicker answers to questions when asking for support PLEASE INCLUDE: the version of the library that you are using, the version of arduino that you are using, the specific hardware that you are using, and what OS you are running under)
Given the above comment (the request is even under the about this community blurb on the side) - what version of FastLED are you using, what version of the arduino software are you using, and specifically, what arduino hardware are you using?
Try the FastLED 3.1 branch - there’s bunch of 1.6.x issues that were fixed on the 3.1 branch. Also, the atmega 168 isn’t terribly well tested, which is to say not at all (I don’t have any 168 based hardware here).
(The biggest issue is the compiler version that arduino is using, and on Linux systems, that compiler version is sometimes changed when it hasn’t been changed on the main arduino distribution, this causes problems as the asm code for ws2811 and friends is fairly tight and fairly precise, and different versions of gcc insist on mangling it in different ways)
You may encounter the issue on all OS’s with arduino 1.6.x (as there were multiple major compiler changes between 1.0.5 and 1.6.x) - please, again, upgrade to the FastLED3.1 before doing any further testing - there’s been a bunch of fixes related to the WS2811 on that branch.
