a big part of the problem with M-PC was portability and some trouble with visualization. we wanted each student to be able to go home and work on projects on their own time, using MSD to render their work. There was some licensing issue that I never understood, which meant that MSD could only be used on the
network, and for some reason only one or two students could work at the same time without the software crawling to a halt.
Also, MPC had little odd bugs (which I attributed to us having no
console.) It seemed that certain actions weren't consistent from session to session. Like sometimes you had to press enter twice, sometimes not. the faders and keypad would sometimes go away inexplicably... very frustrating. I didn't set up the
system, so much of it is a mystery to me.
So now as TA for the course, I've been tasked with finding a better solution, whatever that means. I will be making tutorial videos of whatever we end up going with. The professor is definitely design-oriented and wants as little confusion as possible, while also offering the students a decent picture of what automated lighting is all about. It's difficult to answer gafftapers question regarding our pedagogical goals because we're somewhere in the middle. The dept. is theater, film and dance, so there is definitely a broadway slant... we don't expect students to become rock concert programmers, but the final project (last year, at least) is a live concert with a modest moving lights rig.
maybe we're biting off more than we should, but with all the solutions out there I'm sure we can find something. I'm making a list of all the packages worth looking at. And then I'll test over the course of this semester so that we can try something new in the spring. I really appreciate all of your suggestions. Your opinions are invaluable.