Hi all, I'm currently on a flight, which leaves me with time to think. Dangerous! I'm writing this on my phone, so please excuse any typos. As I've mentioned a couple of times, I'm hoping to start playing with the WS2812 LEDs soon. For those that don't know, they are a 5050 sized RGB LED with a build in driver, so you talk to them via one wire. And they chain together. Once I get code working to actually drive them, it occurs to me that I might want to play back a small sequence of cues. Most of the stuff I make is controlled by an external data source, so this isn't something I have dealt with much. Actually, I did it only once before, and the method I used was to store a bunch of values in various tables. I then read them back (I think 4 per second), and used the stored values for PWMing some LEDs. Not elegant, but it worked. For a larger project, this method could be expanded to read the data off of an SD card. The data rate should be high enough to read enough updates to refresh the LEDs at say, 30Hz, and a 2GB card would have enough space for a ridiculous amount of data. I'm wondering if there's a better way to do this. Conceivably I could implement some sort of dimming engine, so that each saved state would also have a time value associated with it. The engine would take the cue, calculate the difference from the present state, divide it up over the time value, and execute the fade. That might be nice for data storage and manipulation, as then I don't need to have 20 cues if I'm doing a simple 5 second fade (assuming my old 4Hz update rate). However, the engine might be tricky to write. So, am I missing something? Looking forward to watching where this discussion leads! Josh --=20 A common mistake that people make when trying to design something completely foolproof is to underestimate the ingenuity of complete fools. -Douglas Adams --=20 http://www.piclist.com/techref/piclist PIC/SX FAQ & list archive View/change your membership options at http://mailman.mit.edu/mailman/listinfo/piclist .