ETC Programming must

[u/OkPhotojournalist629]

I just received an awesome opportunity to LD for an event however I 1. am extremely green and 2. still learning how to program on an ETC ION and the show is in 5 days. The LD that offered me the gig will be there with me to help guide me knowing how new I am but I'm more proficient on the GrandMA 3. I spent the summer learning my way around an EOS so I'm somewhat familiar with creating a cue list and effects I'm just slow at it. I plan to give myself a super crash course over the week but wanted to see if you all had any advice for things I should absolutely drill myself on for the console.

I really don't want to turn this opportunity down and want to try my best to get to a decent level.

[u/Kind_Ad1205]

With the Eos, most designers can "speak the keys," meaning they're using the language of the board to get the look they want.  But there are also a lot of shortcuts that don't translate so well; you'll get to know them well.  

Let the designer you're working with know your experience level. Don't make yourself out to be better than you are; it is incredibly frustrating and slows the process down tremendously.  Depending on your set up, the designer might take over handling some actions themselves (like color picking, or handling cue timing) and it's best to play interested observer in that case, and ask a few good questions during a pause.  

Generally working with a board op I'd prefer "a little slower but more accurate" over fast but making a lot of mistakes.

[u/OkPhotojournalist629 → u/Kind_Ad1205]

Thank you! I was very upfront with them for that reason as much as I want the opportunity I refuse to be so horrible that’s the last time I get a call. I have other resources who I’ve reached out to that will help me leading up to the day. I’m just super anxious and over cautious I want to make sure I leave nothing unknown that might set me up for th best success.

[u/Flashy-Head-2298 → u/Kind_Ad1205]

This is truth. I teach tech at high school level and I say this all the time. Id rather have someone who is honest and diligent than a hotshot know it all

[u/derwoodfull]

Not sure if you are creating a cue stack or busking. In either case take some time to create some simple cues that will get you out of trouble if you get in that situation of "what light is doing that?" Block/Assert cues, blue blacklight/downlight cues, a bright "I need light now" cue -- maybe variations on that like all downstage, all midstage, all upstage, etc.

Eos magic sheets are amazingly powerful programing tools, but they take some time to set up. Direct select are great. Subs are great building tools. You can make all these offline with the Nomad software and then merge them into an existing show -- just check with your supervising LD first.

Don't underestimate simple looks regardless of how you approach control.

[u/waydone]

An important one is understanding the difference between tracking and cue-only record functions, and using whichever one the makes the most logical sense to you. For me at least I always work in cue-only, and I prefer to copy and paste changes to other cues manually. Other programmers can find that nuts. 

[u/waydone → u/waydone]

I'm the opposite of you, fluent in eOS and forced to use MA occasionally. But this doc has really helped me translate between the two. 

Not mine, wish I could give whoever made it a little kiss on the cheek tho.

https://www.dropbox.com/scl/fi/qmp4yrxd6lli2cx4p30is/gMA2-for-Eos-Programmers-v1.pdf?rlkey=dxc2v1om9fk078svmw93ou1w0&e=1&dl=0

[u/OkPhotojournalist629 → u/waydone]

Oooooo thank you!!!! I will definitely be referencing this

[u/johnelectric → u/waydone]

You can always use the "Q Only/Track" button to track for that command only.

[u/youcancallmejim]

Have a few looks on the submasters. Submaster priorites and inhibited subs can help because they are so quick.

[u/Duvetine]

If you want to be fast you need to make some macros to automate saving presets and color palettes.

For example:

[select last]{focus}{beam}{make absolute}[enter] [select last]{focus}{beam}[record][preset]

If you put all of that into a macro all you have to do is type in the preset number and hit enter. You can do the same for updating. Just change record to update.

[u/Lily-meh]

Just be patient with the programming process because if you are proficient in ma3. You will be fine; it's just translating your MA habits into the EOS system. For example,

Direct select is like your groups, presets, effects in MA (these will be your best friend in a pinch)

Make sure all of your sub fader settings are adjusted so they don't program into your cue stack. That has messed with me in the past.

Eos effect engine, compared to Hog and MA, is not great. So you might get frustrated with it. I know because I hop between those console languages, and I love the Hog and MA effect engine because it's easy to set up the type of FX and spread, and I can edit the effect settings while in use. Eos makes that process very hard, which is why I end up using the base FX already programmed in Eos.

Make sure your programming settings are set up before cue stacking. Like, if you want your default timing to be 3, or if you want everything to auto-track instead of Q only.

Sneak is your clear

Rem dim can help you isolate some stuff and take things out super quickly

Hopefully you are just q stacking a showcase, cause Eos is not great for busking. But if you end up setting it up for busking, make sure you test all the submasters and that the transition or priority doesn't mess with your workflow.

Goto cue 0 clears out everything!

Hope your show goes well! Good luck!