Progress toward "2.0" I just wanted to share an update on the library as

Progress toward “2.0”
I just wanted to share an update on the library as we move toward a full “2.0” release. Dan and I are both eager to get to a full “2.0” release, making sure that we squash all the known bugs before we do, so that “2.0” can be a solid dependable platform to build on while we begin work toward the next version of the library. (And make some art of our own.) (And relax a little.)

To the best of our knowledge, there are two outstanding issues with RC2: (1) a conflict when passing colors as long (32-bit) integers, and (2) a timing bug affecting some WS2812B strips. A big Thank You goes out to the folks who brought these to our attention! As soon as we have the patches for these two problems integrated and tested, we’ll make “RC3”, and if there are no further issues, that code will become “2.0”.

If I had to guess, I’d say that it’ll be “before Halloween”, but if we get serious new bug reports, we’ll take the time to fix them. We’re quite serious about wanting “2.0” to be rock solid.

Looking forward after that, we’ll probably do a relatively quick “2.1” release with support for the Arduino Due and friends (e.g., the new DigiX). Then we’re going to sit back and think a little, and consider what comes next. We have a bunch of ideas, but they’ll need a little time to gel, and we want to pause to think about the bigger picture a little, too.

So, the short version is: expect an “RC3” in the coming weeks, with nothing more than a couple of bug fixes, and if nothing new goes wrong, we’ll stamp it “2.0”, and pop some champagne. Please do report any new problems you find, and thanks for all the help so far.

Mark, I presume you mean “expect an RC4”…?
RC3 has been up on Google Code since Aug 1.

Sorry, yes: expect an RC4 in the next couple of weeks with these two bug fixes!

Will the final 2.0 include DMA? I’ve been playing with Octo, but would strongly prefer to keep using the archaically named FastSPI.

We’re not going to add any new features or support in “2.0” beyond what’s already there; at this point “2.0” is just a couple of bug-fixes away.

I know Dan’s done a bunch of experimentation with DMA, but then again, he lives in California where it’s legal.

I’m a little late to reply, but this is great news & I want to say thanks to both of you for your work on this incredible library!