#pixelcontroller

Look ma! No hands. OSC over wifi. #blinkdom

One of the the problems with making software is that it doesn’t film well. There’s nothing to touch and a lot of reading, in different languages, and in symbols.

For the last few days we’ve been trying to get everything to talk to each other. The goal is to allow anyone near the pixel wall to be able to control it, say to turn it off or change the visuals. Using the pieces already in…

Preparing for the Move

The panels staying together just standing still is a given. What happens when we try to move them? In a truck. Downtown. Up elevators. The bottles are loosely held in the frame by the LED strands that are secured by the caps so from the front you can’t remove a bottle. If you pull real hard, you can probably break the wires and black out 50 LEDs at a time.

  Besides acting…

Update: New Color Output Tests

Today after:

re-checking all wiring

testing network setup

reviewing software configurations

updating the PixelPusher to firmware 1.17

And getting feedback from the creators of both PixelPusher AND PixelController through forums and Github tickets, we are happy to announce…

PixelPusher Results: [tboot_label color="success"]PASS[/tboot_label] PixelController 2.1.0-RC1 Results: [tboot_label…

Time to Shrink It Down Part 2

We’ve already tried to run the pixel wall completely from a Raspberry Pi. It works but the animations slow down or stutter.

2 x 2 x 2 is NOT 8

The next device to attempt is a CuBox-iPro4. It shipped with Android but we quickly re-kicked it with Ubuntu. Using a helpful hint from Jas at HeroicRoboticsthe maker of PixelPusher, we installed the Oracle JVM 1.8. This version has performance…