What´s going on here? Beside the animation number,

What´s going on here? Beside the animation number, the frame rate and the spectrum analyzer we see down left the difference of the 63 Hz and the 100 Hz band and the sum of all 7 audio bands (the line). You could imagine the line chart as the VU-level over time except that the data is not weighted towards the low bands.
Down right we see the intensity of 5 audio bands in case they are above a magic threshold. All this happens while (to be precise: before) the animation is running @700+ fps.
In the background you see the reflection of 288 leds.
http://www.youtube.com/watch?v=ZtzaDzRVkV8

Is that Tom Thum?

Curious in this, is the code online ?

@Greg_Norman the short answer is yes. For the long one have a look here at the comments: https://plus.google.com/115124694226931502095/posts/EuH3KUgrDdM

How did you get the display updating so fast? Are you mostly sending block-copy commands to the OLED controller?

What bitrate are you pushing to the display?

All the image processing happens on the Teensy. So I send always complete frames via SPI. By hardware SPI as fast as the display can digest the data. The tricky part is the local scrolling. Tricky because the screenbuffer is organized vertical, one byte represents 8 vertical pixel. So instead of (slow) single bit checking and manipulating I work with 8 pixel high columns which can be transfered very quickly by using FastLEDs memcpy8 and memmove8. And I tuned the DrawLine and DrawPixel functions. Like getting rid of boundary checks, replaced vertical lines by memset8 and similar stuff. I hope that helps as an inspiration how to speed things up, @Luminous_Elements .

Ah, so you’re doing everything in 1-bit monochrome. Did you roll your own graphics environment, or did you butcher Adafruit_GFX like I’m well on my way to doing?