Another tip for MyDMX users:
It's been long proven that dedicated hardware is often much more reliable than computer-based solutions. This is largely because the layer of complexity that a computer adds to the equation due to the operating system, drivers and other software conflicts that may or may not exist. One of the biggest tips with computer-based stuff for professional audio/AV/Video/lighting apps is to "harden" or streamline the OS to NOT run or include anything that isn't absolutely necessary in order to make the computer as robust, stable and reliable as is possible. On tours, guys will NOT update or upgrade their computers unless absolutely necessary. Why fix it if it ain't broke? Plus, one stupid fix could bring the whole thing crashing down. Too much of a risk, even with restore images handy, but that is a "time wasting" thing, having to reload your stable images, and time is NOT on your side at an event. Often, you go to your back-up computer, trash the "production" one for the event, then while in transit to the next location, re-load your production machine back to where it was.
I'm not saying MyDMX isn't reliable. It can be. I've had failures with it, but I've had problems as well. I'm not immune. But I have a solution many of you are not considering for a wide variety of reasons.
Should MyDMX fail, do you have a back-up solution? I do. I previously bought a DMX Operator back in I think end of 2001. I'm not saying "hey, go run out and buy a DMX Operator", but what I am saying is "you should thing about having a lighting controller of some sort readily available and programmed just in case...." This isn't necessarily cheap insurance as it may cost more than MyDMX. I know, one of the lures and appeals of MyDMX is that it costs less than even a DMX Operator(depending on when and where you buy it).
Let's think about this:
If your butt is on the line here and your MyDMX or your computer takes a big dump on you, what you gonna do? I'm not going to get into the Mac/PC debate, but it generally takes LESS time to get a Mac up and running than a PC, by often a factor of 5 or more. Even so, you might need to get updates, and that is still time consuming and Apple isn't immune to those sort of issues either.
But, getting your PC back up on-site is a time consuming venture. Even if you have a DVD or CD chock full of drivers and other software to install, this is time. Time is what you don't have. A back-up laptop is nice, but how many of us have that as an option? I do, but I don't carry it because it's a POS Dell netbook and that thing just pisses me off(WTF? No CD/DVD drive? Took me 2 weeks to set up a TFTP server and get the damn thing to boot over the network to pull in the OS so it could install XP Pro...)
No, you're gonna fail. It sucks, it happens. That's life. What you need is a DMX controller that you can pre-program for at least enough stuff to get you through your event. In my case, should MyDMX fail, I can swing a cable to my DMX Operator and keep on going.
This may sound simple, but it requires two bits of up front work. The first bit of work is fairly straight forward, and that is to program your lighting fixtures addresses to be compatible with both your MyDMX and your controller. In the case of my DMX Operator vs. MyDMX, I leave gaps in the addressed to accomodate logical control on the DMX Operator. The second part is much more time consuming, and that is programmning the controller. This is because it simply takes more time to do this. Some controllers have computer software to let you design and then dump it in to the controller. The thing that is great about this is that you can save your shows to disc. In the case of a DMX Operator, no such luxury.
Now, since following a few simple guidelines for dealing with MyDMX, I've not had any issues with it since then. Even so, my DMX Operator is quite literally inches away and a cable can be moved incredibly fast. Even though I've broken my rule by not programming much of it(my lighting changed and I've lacked the time, which is a crappy excuse), worse case is I can flop around on the DMX Operator and get by.
I'm not slamming MyDMX. Compared to my DMX Operator, which I really really like, MyDMX makes me feel like I was living in the stone age. MyDMX does all the stuff I had problems with by using a DMX Operator, namely I can't visualize things and MyDMX even has a 3D Visualizer. MyDMX does a lot of nifty things that are flat out impossible for a DMX Operator to do, such as looping and complicated movement sequences. We're talking a total lack of comparison as the products aren't on the same level as far as capabilities. The only general area they can compete in is pricing.
MyDMX puts a lot of "professional lighting console" power into a cost effective computer program. For what it offers and at the price, it is an impressive software platform.
I do recommend a few things for practicing. First, find a schematic to build a DMX Terminator, which is like nothing to do. Find another schematic which will show you how to make a super basic DMX tester. DO NOT use the 2-color LED version, I did that,it doesn't work worth a damn, use two LED's, works much better and takes just as long to make. Should you not have your lights handy, no doubt you've done work just using your MyDMX dongle. Plug in that basic tester so you can see the lights blinking. This will simulate load as the tester I made has 2 230-ohm resiters which end up providing not only testing capability, but also aacts as a terminator.
Examine your start-up procedure. First, just "do it" and notate what you do. Seriously. Even if it's "I plug in the dongle and fire up my computer". For most, it's starting up, then I have to disable things like wireless and turn off other things I use at home(like TightVNC, my scanner driver... stuff like that), and then plug in the dongle, wait for it to recognize and then I'm pretty much good to go, every single time. The key is to turn off crap you absolutely don't need. One thing I don't always need but can't easily turn off is my M-Audio drivers for my Firewire 410 interface, which I don't use all that often.