<table border=1><tr><td> <dtml-var "dance2005img.net.tag(REQUEST, pdcookie='1')"><p> Our network in the booth of the theater </td></tr></table>
<table border=1><tr><td> <dtml-var "dance2005img.editcode.tag(REQUEST, pdcookie='1')"><p> Dave editing the code, probably between rehearsals </td></tr></table>
<table border=1><tr><td> <dtml-var "dance2005img.fog1.tag(REQUEST, pdcookie='1')"><p> The stage lighting after a fog effect ran, which is why you can see the beams </td></tr></table>
<table border=1><tr><td> <dtml-var "dance2005img.fog2.tag(REQUEST, pdcookie='1')"><p> More fog and beams. Each of these lights has its own dimmer, which has its own DMX address. See http://darcs.bigasterisk.com/light9/show/dance2005/patchdata.py for the names we gave to all the addresses we used. </td></tr></table>
<table border=1><tr><td> <dtml-var "dance2005img.gyro.tag(REQUEST, pdcookie='1')"><p>
Dave is holding the excellent "gyromouse":http://www.gyration.com/gyromouse.htm and looking at feedback on a giant display in the window of the booth. We can see the display's red bar in reflection. With the gyromouse and Dave's fine gyrocomposer program, we can select lights and set levels while we're working on the lights. In the past, one person would have to sit in the booth on a headset to push knobs around. This is the first time we've had a remote control.
</td></tr></table>
<table border=1><tr><td> <dtml-var "dance2005img.showbooth.tag(REQUEST, pdcookie='1')"><p> Here's a view of a live show from the booth. The left monitor shows an active curvecalc program; the middle laptop is running ascoltami (and alsamixer). </td></tr></table>
This show is now checked into darcs (except for the music files).
<br>
Some of our post-mortem notes about the project:
to set the house dimmers all to 68, somehow get to setting up each dimmer, and when you see the dimmer attrs, hit 'dmx#' button to get to the screen that assigns the dmx channel to that dimmer. then enter or cancel to get to type the next dimmer number. we change 68..72 all to 68.
next year 2006, please do hardware stuff first. there weren't enough colors or side posts. front row could have been all colors. sill was impossible because the back was black and the cyc lights went too far down. strobe and fog were good.
normalized wavs would be nice. beat detection would be really good. get a new audacity, export the pieces of a mix into separate curves
curvecalc: typing 'within' should make a curve, which you could edit. the curves need numbers and scales. i should be able to grab a segment and adjust its two ends. the point dragging obviously needs to not crunch points like it currently does. we sohuldn't have to add, those should be separate curves and you can use multiple terms on one submaster. the view could conserve rows by stacking curve A and B on the same row if all their non-zero features are at totally distinct times.
usb chippy with 512ch would be great. there were comm problems with dash. see io/parport.c for more notes.
dmxserver has a bug where it doesnt recalc upon forgetting a client. only when another client sends a change do we see the forget
star needs usb mouse. we didnt have a good mouse this year- the pad will click sometimes, and gyro would move and click sometimes.
there was a timing bottleneck for putting effects into songs. many music effects should have been animated ahead of time, but we didn't do it.
asco needs the precision back. dump mpd and use something else
the music post time is too long.
put a sensor in the curtain for worklights
get a BCF2000 motorized fader midi controller http://www.behringer.com/BCF2000/index.cfm?lang=ENG