There are actually quite a few options for controllers when it comes to this hobby. Being new to the topic of running rgb pixels in a show, I did a bunch of reading on the different aspects that may affect which one I choose. The only thing I do know is that I do not care for using light-o-rama products as I feel they put me into that ecosystem that seems to cost more to do what I want, versus some other options.
That pretty much leaves me with the common options that someone was nice enough to put into a table on a site for easier comparison – http://nutcracker123.com/nutcracker/rgb_controllers/.
Rather than focus on price first, I should look for a controller that covers my basic needs (as I understand them). Below are some of the main things I am thinking about in my decision making and why they matter.
Note: Keep in mind that I am a complete noob at this stuff and I could be completely wrong about anything I write.
Warning: This post will be long as I work through all this.
Availability Now? Can I get any of these controllers in the next few months to start playing? Here is the problem with that… some of these are done via group buys mainly on certain forums (linked on my Handy Links area above), while others are available year-round. Given the timing of this research, according to forums, almost everything will have a group-buy/pre-sale starting up this month. Most also do other buys/sales throughout the year so if you don’t have to have something “now”, really you have an open field. Keep in mind that some pre-sale products have extras ordered and the manufacturer may have some on hand.
E.131 vs Pixelnet/Renard/DMX? It seems the question here is really whether I want to use a usb serial dongle (like I had for light-o-rama before using the mp3director) that connects from the show machine (maybe a Raspberry Pi) to the controller… or if I want a controller that hooks up to a network like any other device by having and IP and communicating via that network to other stuff like the show machine. I am pretty sure that I want E.131 support, as it is a familiar technology, so that removes the F16V1 and Zeus-16 off the list.
E.131 Multicast vs Unicast? I am not sure which direction to go because I do not know enough yet. A quick summary is available on this page. Given that I am not sure, having both as an option is good, but perhaps not necessary as many others in the forums just do multicast. Regardless, if I want both it removes the RonP -64 controller.
Do I want to put it together? Really this just affects price, but in one case (SanDevices E682) that is almost 1/2 the cost. Honestly, I am going to limit my soldering to wires and not deal with boards/chips. Perhaps if someone does like to solder this kind of stuff, it would be a great price savings.
How many outputs? Obviously what you want here depends on what your application is for that controller. In my case, I plan on using one controller for all my show and have a backup. The large pixel tree would be easier to do with power injection, otherwise I would use over 1/2 the outputs. Regardless, going for a 16 output board seems smart based on my clustered layout and less to maintain. As the chart only shows the 16 channel versions of most manufacturers, not anything to remove based on this. If anything the F16v2 ability with the daughter board to hit 32 outputs (albeit with 1/2 original pixels per output) would be a possible benefit.
Pixels per output / max channels? Here is what I see as a big difference between these board options. More seems better is my first impression. As long as I inject power, I see a difference of 2040 (unicast on E682) vs 10880 (F16v2) to be a huge one. I could see going over 2000 pixels in the future and if I want backup controllers that means going with the E682 would require 2 more @ $190 each. Despite the heavy usage of the E682, I think I have to remove it as an option.
Really at this point I am down to 3 boards. PixLite 16, AlphaPix 16v2, and F16v2. Just to make sure I can’t rule any out by price, I note that they are all within about $10 of each other. No help there.
I can now look at handy features of each that would tip one way or another.
Simultaneous protocols? Probably not something I care about yet as I am looking to use 2811s everywhere, but if I did the F16v2 can run a different protocol per output where the other 2 can only do one per controller. Speaking of 2811, I note that they each support the main protocols and a smattering of others that I guess are used in some situations. GECE (GE Color Effects) is kinda cool but only supported on the F16v2.
Some visual output on-board? Well, the AlphaPix 16v2 and the F16v2 have one while the PixLite 16 has none. The AplhaPix uses a LCD w/ 2 lines while the F16v2 uses a 128×64 OLED. I understand that the AlphaPix also can be configured via the display while the F16v2 just uses it for output (temps/IP address/etc). I like visual stuff. PixLite loosing ground for me.
Any other notables? The AlphaPix can handle more amps (likely more important if you are doing 5v PSU). It also has unlimited free hardware support via phone/email. I like that. F16v2 has 2x the max pixels, gamma correction if my pixels have different whites I guess, 5v dc output (is this only if you use 5v PSU?), and potential to connect with a Raspberry PI directly in the future (1 box to house them all and in the darkness… light them?).
After looking at all this, it is a tough call… especially with the prices so close during pre-sales and the fact I would be likely buying from holidaycoro already and may hit a free shipping level (essentially decreasing the cost further of the AlphaPix).
In the end… I have decided on the Falcon F16v2.
Next up will be double checking everything and making the decision of going RGB or not.