The Ask: Follow the Fire ANSWERED

Photo by Adam Wilson on Unsplash

***

Mark LaPierre is a programmer in film and television based out of Albuquerque.  He grew up in live entertainment and has been a designer/programmer for musicals, concert dance, live music, circus and corporate.  Mark is a proud member of IATSE, an ETC Eos trainer and an enthusiastic trainer of many other platforms and subjects.  He offers Zoom console training as well as in person.  If you enjoy his content, please consider commenting on his posts on the website to appease the Algorithm.  

3 comments

  1. John V. - Reply

    I just did 24 separate cues on a separate cue list that contained intensity and the effect for each pixel. I’m glad your solution worked for you. For me, pushing a fader up means there is too high a risk of me overshooting and turning on fire before the actor gets to that pixel. I’d rather mash the go button 24 (or 12) times and lag behind the actor a little bit because that’s what it would look like in real life.

    • admin - Reply

      Obviously- your answer is totally legit. But my concern- and the reason I did it how I did it- is I’ve known far too many actors. (I used to be one.) I was worried in one take, he might decide to light from the other side, or start in the middle. The scene was rehearsed only once, so to say it was rough is an understatement. The Inhibitives helped me to be ready basically no matter what he did.

  2. Steele - Reply

    Finally got around to doing this!

    Working in Onyx, I started by dumping my tubes into one of the pre-made fire effects I have in Dylos (the pixel mapping engine). For the wipe reveal, my first thought was to create an override that would drive the pixels to zero one at a time, 24 cues. But I forgot a quirk of Onyx: Dylos playbacks always run at a higher priority than other playbacks, even if they are set to higher priority. So that didn’t work. My next thought was similar to your solution: add another Dylos zone, over the two generating the fire effect, with a black block that pans across to reveal the effect. I recorded this masking zone to it’s own override playback, and Onyx has a neat feature called “Q-Blender”, basically you can set it so moving the fader moves you through the cues. This eventually worked, but it took a lot longer than I thought it would. I actually got the black mask working “live”, in the programmer fairly quickly, but I wanted it on a playback and that took quite a bit of fiddling.

    In thinking about mine and your solutions, it occurs to me I could have just moved the entire Dylos zone source supplying the fire effect, pan that from off frame left to right, it should achieve what we need.

    This was a good exercise. I thought it was going to be fairly easy, but once I got into it I realized there were some details to sweat I hadn’t anticipated. It also points up a drawback with relying on pixel engine effects in Dylos: they can be very fiddly. Several parameters have to be all set exactly right or it doesn’t work at all. Onyx has, unfortunately perhaps, focused on developing their Dylos engine so much they have neglected to upgrade some basic effects features, like a random waveform. Dylos is great per se, it rivals something like Resolume (if I understand that correctly) for video effects, but it’s such a rabbit hole you can quickly get lost in it.

Leave a Reply to John V. Cancel reply

Your email address will not be published. Required fields are marked *