Blizzard Lighting ProKontrol MH
$329.99
Blizzard Lighting ProKontrol MH (Blizzard Pro Control MH)
Perfect For Moving Head Fixtures!
The ProKontrol™ MH is a professional universal intelligent lighting controller with RDM protocol compatibility. Once properly patched it’s the perfect controller for any moving head fixture, allowing ease of use with its dedicated PAN and TILT wheels. With the ProKontrol™ MH, you can control up to 32 fixtures composed of 18 channels each.
Programs can be triggered by music, midi, automatically or manually. You can also run up to 5 chases, and all the scenes can be executed at the same time!
On the surface of the ProKontrol™ MH, you will find a variety of programming tools such as 16 universal channel sliders, quick access “Movement” and built-in “Color Effect” buttons, plus an LCD display indicator for easy navigation of all controls and menu functions.
And the all-metal enclosure means you’re getting one tough unit, which will last for many years to come!
Take Kontrol™ of your lights like a pro with the ProKontrol™ MH!
Features:
• DMX512 standard with RDM protocol compatibilty.
• 512 DMX channels
• Controls up to 32 fixtures, each with up to of 18 DMX channels
• Fixture starting addresses and channels can be soft patched
• 32 chases, able to run 5 chases simultaneously
• 32 scenes, all scenes are able to be operated simultaneously
• 9 built-in effect buttons for moving head fixtures, plus 7 built-in color effect buttons
• USB port for firmware updates and data backup
• Sound control via built-in microphone
Specifications:
Weight & Dimensions
• Length 19 inches (48.26 cm)
• Width 5.1 inches (13 cm)
• Height 3.1 inches (7.9 cm)
• Weight 1.4 lbs (3 kg)
Power
• Operating Voltage DC9V, 800mA max (From included power supply)
Thermal
• Max. Operating Temp. 104 degrees F (40 degrees C) ambient
Control
• Protocol USITT DMX-512
• DMX Channels 512
• Output 3-pin XLR Female
Warranty
• 2-year limited warranty
Great console for the money. Easy to program. 32 fixtures and 32 chases and 32 scenes. Effect built in movements are helpful. I use with LED pars and moving heads and it does well with both. The ability to save settings to a usb stiick is useful. My shows look like they were done on a GrandMA but instead on a budget console. I like it.
Quite a few "good" reviews of this board floating around on the web, I figured I'd give it a try. Unfortunately I've quickly found that it's not that great. This is definitely a starter board!<br /> <br /> My setup is 4 MHLs, 4 spiders, 4 derbys, and 10 par cans.<br /> <br /> The nice thing about this board is that it is one of the few that support all 512 channels in the price range. It's also got room for 32 pre-defined fixtures, where most of the other <$300 boards support less than 20. Also, for the novice user, it has some pre-defined movements for MHLs, and some color macros for par cans. That's about where the good stuff starts to fall off tho.<br /> <br /> Programming is a bit wonky on the board, and the manual presents information in an attempt to be logical, but misses the mark a bit. First off, remapping the channels is necessary and critical if you want any of the macros to work. So, be sure you do that for all your fixtures. I also found that it was important to move any OTHER functions of the lights away from channels 1-5, and pan/tilt (17/18), or you might get some funky behavior. Once I got all the channels mapped, and mapped out other channels to follow the alignment of 1-5, things got much much easier! Also, this board has a Dedicated "white" channel, which is very nice for LED fixtures, where a lot of other boards are just RGB.<br /> <br /> So, channels remapped, I started to program. This is where the manual fails completely. So, you select your fixtures and apply a movement macro, adjust the offsets and movement ranges to get them pointing where you want them, and ..... the lamps aren't on, and the color macro buttons don't work in conjunction with the movement macros You have to apply lamp controls manually while the movement macros are applied. So I got them all set and added them to a scene. I then went on to program the spiders, and added them to the scene.<br /> <br /> This is where the board fails completely and is why I said this is a novice board. It cannot handle more than one "batch" of movements at the same time. So, if you have 2 sets of moving lamps, and you want them to do different things such as criss-crossing beams with opposing vectors, this board cannot do it. Only one movement macro can be running at a time.<br /> <br /> in my setup, I have the MHLs programmed on scene 5 and the spiders on scene 10. Turn on scene 5 and the MHLs start moving in the desires program. As soon as I hit scene 10 to add in the spiders, the spiders start moving, and the MHLs immediately return home and stay there. The lamps control I programmed on scene 5 continues so they are basically pointing at the ceiling with the lamps on. Turn off scene 10, and the scene 5 program resumes controlling the movements again.<br /> <br /> And before you ask, no there are no overlapping controls in the scenes, and I performed a complete reset and reprogram twice because of this. I also tried rearranging the scenes and many different combinations of scene control. Every time, I ran into the same problem. You cannot have 2 moving head scenes with macros going at the same time. This is a major drawback for a board that is advertised as having stackable scenes.<br /> <br /> Here's another weird behavior solution for you. If you are playing around with some fixtures, and let's say that you have some color set. Moving along, you select a scene, get into it, forget where you were, play with some other lamps to build the scene, and then deselect that scene, only to discover that your first lamps start doing something unexpected. It's because you left them with that color selection from earlier on. The lesson here is that when you are done messing with settings of a fixture, you have to manually return all the faders to 0 in order to blank the fixture. Many boards on the market assume a complete separation between live and program mode, this board does not. This is hard to explain. The best thing I can tell you is this: if your lamps are doing something weird between scenes, just select them and flip all the faders back to 0 again to stop sending whatever signals are going on, then you can return to playing with scenes.<br /> <br /> Another significant problem I ran into several times while is as setting things up is that the board gets "stuck" from time to time, and certain channels continue to send certain controls beardless of what lights and faders are set to. On no less than a dozen occasions during the programming, one or more lights would continue to do something even after I had I applied a scene or whatever. I know this is the board itself because if I disconnected the dmx line, the fixture would stop. Plug the cable back in and it returned to doing the same thing again, so I had to reboot the board several times. I really hope this doesn't happen during the show.<br /> <br /> After beating my head on the desk for a while, I also discovered that trying to program a single scene with many things going on is going to give you a huge headache. Since this board allows for stacked scenes, I would seriously recommend that you make each scene simple to control one type of fixture, and then stack them to control all the fixtures during the show.<br /> <br /> Finally, here is a failure of the manual, and you may consider this an annoyance or a nice feature. The way I have the board set up finally, this works well for me. Your mileage may vary. The manual states that "the last scene selected takes priority". What this should say is "the HIGHEST scene selected takes priority". Per the manual for example, this would suggest that if I have scene 6 applied, and I want to jump to scene 4, then scene 4 would take priority as long as it is selected, and then when I deselect 4, 6 would take over since it was the last selected scene. In reality however, this does not work, because scene 6 is higher than 4, not related to the order they are selected. Once I figured this out, I started programming my scenes with progressively more going on in the higher scene numbers. I also programmed scene 16 in a "full auto sound control" mode. So what this allows me to do, and why I like it, is that I can set a basic mood in the lower scenes, then as the music changes, I can add or remove lights simply by leaving that mood scene set, and stack on higher scenes. As I deselect lights, or during dramatic pauses or if I want to use strobes or whatever, that basic mood is set in the background, so it will always be on, and when I deselect my main lights, the floor doesn't truly go dark because that basic mood is already set. If I want the floor to go dark, I can unselect that basic scene, or possibly program a higher scene for momentary control that overrides everything. Actually I might move my full auto sound to scene 15, and then use 16 as a momentary dramatic pause. The basic mood sets could be a handy function for scenes 1-16 (page 1) and then you could do your main programming on scenes 17-32 (page 2). Again, your mileage may vary. You might find this to be useful, or not.<br /> <br /> So, all in all, this is definitely a novice board for sure. Programming was a bit wonky until I figured out what the board was doing that the manual didn't say, and I'm really disappointed that the movement macros cannot be stacked, that's a huge bummer. However now that I finally figured out what all the limits and capabilities are, I've got it programmed to a relatively acceptable condition at least for the immediate need.<br /> <br /> For as simple as dmx is, it sure seems like a real disappointment that it's so hard to find a board that makes it easy for entry level users. Just give me a friggin desk or 8u tall board with more buttons to select functions, no "pages" on any button or slider bank, and better macro control for $500. Or add in a midi input control so I can use a keyboard to quickly select functions.<br /> <br /> One final note: I have a $35 knock off Chinese version of the Chauvet Obey 40 to compare this blizzard board to. The blizzard offers 2 functions that the Obey doesn't. First, it has the movement macros which are nice. Second, it allows for stackable scenes. But after having beat my head on the desk trying to figure out the differences between the manual and reality, and the limits and capabilities of the board, I would say that it is almost more feasible and economical to buy 4 of the knock off ones for $35 each, than spend double the cost for the blizzard. But, each to their own I suppose.<br /> <br /> In the long run, I am probably going to move to LightJockey.<br /> <br /> TL;DR: I hope you have a good understanding of DMX controls, and plenty of time to set up the board BEFORE you set up the fixtures. This board is a very odd combination of "novice & limited", and "not easy to program". Also, pay attention to the order in which you program scenes, as higher scene numbers take priority.
