Hello all! I recently got a teensy 3.1 to play with controlling strips of WS2812b pixels and have been testing it out. Looks like fastled does not yet work (compiled but nothing or intermittent flickers). To use a 3.1 at the moment then you have 2 options - you can use the neopixel library or OCTOws2811 which works if you get the latest release candidate from here: http://forum.pjrc.com/threads/24796-Teensyduino-1-18-Release-Candidate-2-Available
older versions DO NOT work, except possibly RC1 of the same version. Interestingly i was using a 74HCT245 or similar but testing without it also works for a pretty long cable length which i didn’t expect, i was forced to use one with a teensy 3.0 using shorter runs on a previous project! I’m still going to use one anyway but if you’re short on room or parts then it’s worth a try 
Are you using the main download or did you try the 2.1 branch that I linked to earlier here, asking people to test w/the teensy 3.1? (https://github.com/FastLED/FastLED/archive/FastLED2.1.zip )
tried the main one then the 2.1 branch but got nothing working from either.
Hmm. FWIW, I’ve been successfully using FastLED with a Teensy 3.1 for a couple of weeks, albeit using P9813 pixels.
Ok, good to know, likely this means something in the cycle counts changed. I’ve been needing/wanting to re-write the teensy clockless code to be in line with what i’ve got with the, which I like and is quite a bit more flexible.
@Dave_Morgan Are P9813’s officially supported yet? I’ve got a hacked version working with them, but hadn’t heard that they made it into a release yet…
They’re in the 2.1 branch which we’re actively working on adding MCUs and chipsets to.
Awesome. Thanks!
I thought you had previously mentioned you were working on them.
Haha, my hacked version was running around 35 fps to update 350 P9813’s (teensy 3.0 controlled). Your 2.1 version is running the same exact code set at 130 - 180 fps (depending on what the lights are doing).
Well done sir. Well done.