This is what I call a beautiful error. The results are 100% unintended. After all this OLED stuff from @Stefan_Petrick , I had to try my hand at it too. The code is in the video description, and mainly uses beatsin8() to do all the dirty work.
http://www.youtube.com/watch?v=UvMb3Qi3Q4k
Nice! You’re making me want to get one too. 
Beautiful!
It looks like your display has plenty of pins available. Which ones are this?
I agree with these guys, very cool! Now I’m fighting the urge to order one. 
Stefan, it’s this one (linked in the video description): https://www.adafruit.com/products/1673
@Stefan_Petrick this display has an SD card slot on the back, the extra pins are for that. Because it’s RGB, it is slower than the monochrome one I imagine.
How many fps do you get with hardware SPI?
@Stefan_Petrick With this FPS code; https://gist.github.com/mixania/0043748bcb07d1b1aaba
I get ~640 FPS with this animation
That´s a lot. How much of them do you really see? If you move a vertical line every frame - how fast can you go before steps appear (tearing starts)?
@Stefan_Petrick With this code:
static byte x = 0;
display.drawFastVLine(x, 0, 95, WHITE);
if (x++ > 127) x = 0;
if (x != 0) display.drawFastVLine(x - 1, 0, 95, BLACK);
I get this: https://youtu.be/BIzgdkGCPZ8
Hard to judge if it is the camera or the display… how does this look in reality? Does it appear like a VLine or diagonal?
It is the display, there is distinct tearing. I have adjusted the display frequency via the library and have not been able to reduce the amount of tearing. It just looks like these displays are better suited for low frame rate stuff or find a breakout board that has the CLK line pin so you can sync the display.
Here is a capture of the screen with my phone camera, it looks the same in real life: https://photos.google.com/share/AF1QipOn1nBTudRaKlxGx4vVwvvTzySmi3Q4VIfurFYc6WCRtVIOuwdst2dodeAEeO033w?key=VF9oVlZIb0NYRXFPeUZVTWhFZjhEQ2JiaXpXWjNn