Macros

Hi Guys,

I'm programming the ion for the first time and wanted to know of any macros that people find usfull.

Cheers.

George.

On a previous console, I had a bunch of macros for turning some specific work lights on or off (since I never used the room enough to learn the channel numbers).

On the Ion, the only macro I have clears and resets the parked channels to the base room look (safety and aisle lights on at 80%).  Since the parked channels don't load with a show, if you add a parked channel for a show, it won't clear when you re-load your default house patch/sub system.

I have no DMX devices, only conventionals.

>Hi Guys,

>I'm programming the ion for the first time and wanted to know of any macros that people find usfull.

have fun.

Hi there.

jumping in a little late, but Here's a couple that I do use regularly:

[block] [enter] [block] [enter] [clear]
We call this "cleanup" and it removes unintended partial blocks (lower case b's in the flags field).

[undo] [redo] [enter] [clear]
The current release of EOS software has the three blank keys above [Params] mapped to macro 801-803. I make one of these into a replacement for {redo} because I don't like the placement of the redo softkey. (The [undo] in the macro is because you have to open the undo window to do a redo command.)

[out] [next] [@] [full] [enter]
I do this one because if I have a designer who wants to 'next' through some lights, they never remember to use the {chan check} command. So I throw a "next" and "last" macro on the direct selects or the 801-803 keys for speed. It's messier but it's faster.

I also write a few macros that I can call up from the remote to check scrollers and stuff.

So not a ton, but I think the other stuff I write are mostly show-specific.

HTH

Stephen Graham
Seattle, Wa

How about "CHAN 1 <ENTER><CLEAR> on an  RVI button  so the designer can get back to page one.

Although this command looks simple, when put into a macro it doesn't work.  The reason is that the macro playback doesn't wait for actions to complete before sending out the next keystroke.  I found this a common problem with any macro that causes a display change.  The fix is to use MACRO_WAITs at key points in your macro:

CHAN 1 <ENTER>MACRO_WAIT 1<CLEAR>