DPI:

Would you be willing to share any of your production documentation?

Hal Eagar:

OK let me find some...

How about "Disposable Men"since it's going out on tour again next week I've had to use my documentation to figure out how to do it again.  This documentation is great for packing and seting up the show, but of course has none of the cues which are in the stage managers book only.  And does not cover the software setup.   I think I may have written that up, but maybe I just brain dump it to the video operator?   This time I'll try to write it up and add it to this post perhaps.   A video of the piece is of course as I mentoned also a key part of the documentation to see what it is you are trying to recreate.

Pack List and Wireing Diagram

Tech Rider

For reference here are some photos of the show being refrenced here.

DPI:

Where do you get content?
Found footage
Shoot it
Use live
3d or animation
Where do you find it?

Hal Eagar:

For my own designs I will tend to try and create it as much from scratch as possible; make it from whole pixels as it were.  That way it's less limited by what you can find, and it all matches a common visual style.  What that means 3D or 2D animation mostly, a lot of 3DS Max, VRML, and Flash.  The big problem with that approach is that it takes so much time that what you get limited by is your own time, but maybe that's always the case.  And sometimes it could be just 3D or vector art but often I use lots of photos, and they are 95% found materials as opposed to shot myself.   I also like to try and keep the animations procedural, and data driven.  Puppets really, that way you can make as much as you need on the spot.  

But again that's a lot of work.

I also like to work with live video, because you get to make it every night like the puppeteerd animation, and you can make as much as you need. 

Or I like someone else to be bringing in all the video and I put it together, then the design is in the where when how, not the what.  I really feel it's mostly their design then, particularly because they probably have an idea of where and when they want to see it.  But I still really enjoy that process.

DPI:
 read full post »

DPI:

Do you like to use hardware or software? PC/Mac vs. DVD/Mixer?

Hal Eagar:

I prefere Software over hardware all the way. I'm a programmer so that's pretty obvious for me. But to go into the details the fact that I can get the software to do a lot of various things that that would each take a different piece of hardware and the fact that I can re use the computer just about every day not just when i'm running a video effect is a big plus. And because it's a general purpose machine it's easy to find a computer when you need one too.

Also as i've mentioned I like realtime generated animation and the type of uber flexability that you can get with a software system. I guess that a dvd player is as easy to find as a computer, but the computer is more flexable.

Not everything is possible with just a general purpose pc of course. I have my bag of add ons and extra little devices. Scan converters, video capture devices, DA's, switches etc... But they are all pretty cheap mass market stuff just like the computer itself. Besides being cheap, mass market stuff is easy to replace. So although it's less dependable than really high end video gear it's pretty solid (After all it's meant for the masses) and easily replaced or backed up.

I know a lot of people are afraid of using computers because they fear failure. And some people say they don't trust hard drives.
 read full post »

DPI:

Do you like finished tools or programming environments? Watch out/grid vs. Isadora/jitter/vvvv ?

Hal Eagar:

I prefer tools. But not too raw. The question does not even go so far as to suggest Java, C, or other such viable options, I guess it really should. But that's too raw for me. I am in a hurry and want the hard work done for me. Sure in a framework or using libraries that work is done but like I said I'm in a hurry, and I'm lazy too.

What was it Lary Wall said were the virtues of a good programmer. Laziness, Hubris, and Impatience.

So anyway I love Isadora that hits the sweet spot between flexible programing and ease of use. That spot is probably different for everyone. It may be watchout for some or java for others.

And I do think jitter is awesome, but I may be a little too lazy for it, when Isadora gets me there faster.

I also love flash, it also hits the spot for me; easy but powerful. And it's growing in features like crazy. Maybe it's getting too complex and it might be just as easy to use some other framework to do some jobs I do with flash. But it really has features and strengths across a large spectrum of uses and styles. So why learn another system, I'm hooked in to just focusing on getting really proficient in this one.

DPI:

How do you document your work on a show? Video, pictures, ground plans? Wiring diagrams? Written instructions?

Hal Eagar:

If I'm building the show and running it, I rarely get around to any real technical documentation, but if I'm handing it off to someone then I try and do as much as possible. And when I pack up and back up a show I try to do at least a nice long text description of the setup.

I've tried taking photos of a setup, but it always seems useless. The video of what the piece looks like is really useful though. It may not help you remember any of the tricks of the video system, but it's great for trying to recreate the piece.

I really like to color code my wiring diagram, and I seem to almost always have the flash
IDE open on my computer so I'll end up doing a wiring diagram with little
handmade graphics of the video devices in flash. I also like to build it in layers, so you can
output a diagram of all the VGA cable, and of all the composite cable, and of
all the computer cable separately.

I figure I really ought to be using a drafting program but, it works so far.

But at least 50% of the documentation is just in a textual description of how everything should work, and what order to do things in.

And if possible what things to check if something is going wrong.
 read full post »

DPI:

Do you find that your designs are reproduceable? Why or why not?

Hal Eagar:

I used to run the shows I designed, for various reasons; from there was no separate operator budget to its more work to make it easy for someone else to run. Also I like the idea of the live animation and the ability to change things from day to day, that I enjoy kind of playing the video system like a instrument. Of course I tended to build them like that because otherwise I'd get board running the show myself as well.
Anyway that made it harder, but not impossible to reproduce, just more dependent on my brain than a book.

But now I'm living in the permanent time crunch that comes with being a parent so I'm always planning to have someone else run the show. I think this probably changes the way I create a show, less fiddly controls, just the crucial things.
That means that I do manage to put just about all the info needed to reprocude it into a book, or at least into someone else's head.   It may not stay in that person's head, and the book might not have enough info, since re-mounting the production is not my focus while putting it together, but it's a good start.
 read full post »

DPI:

How do you hand off a show? What is that training process? How do you work with that? Do you also take on one of those? Or share work with a designer in another area? Or work as a team? Or do you run your own shows?

Hal Eagar:

Well really the operator has to be there for the final tech, and learn to feel the show in some way. I find that video is usually not called by the stage manager, at least not the way it's done in shows I work on. I suppose it's possible, but we're talking about many hundreds of cues, so the video operator needs to be as autonomous as possible.

Maybe that's asking too much but that's how it feels to me. Unfortunately I think I usually just end up dumping way too much information at the operator at once. I'm not sure there is any other way to do it, at least not on a theatre schedule.

Generally they will watch me working for a day, and I'll try and tell them what I am doing. And in the process I often think of several more things that I could be automating. Then they get dropped in the hot seat and figure things out, while I hang around over their shoulder filling in. And this hopefully gives me time to automate those last few things, and to write up the debugging sheet etc...