• Date
    Wayne Simpson
  • Date
  • Replies 7 replies
  • Subscribers 184 subscribers
  • Views 4014 views
  • Users 0 members are here

Simple "Go" and "Back" macros: trouble with "Back"

On my Ion, I want to write simple "Go" and "Back" macros to trigger whatever cuelist I have loaded on the master fader. I want to use these as events so the gaffer can hold a little two-button momentary switch I made and trigger and back a cuelist via the analog input. Got the "Go" macro to work fine, just by deleting the cuelist number (which automatically populates) in the macro editor. It reads, "Go_Cuelist Fader Master_User". However, the "Back" macro, recorded similarly, doesn't work. Just recording a "Back" command live records a "Back" command in the macro, that doesn't trigger it, I tried adding "Fader" and Master_User" commands after, that also doesn't work. Suggestions?

Parents
  • On my setup it recorded Back_Cuelist 1 and that worked ok.

    What version are you running, this was on 2.5.2
  • in reply to Mike A

    If I select a cuelist number, it works fine... I am using a bunch of cuelists, though, and I would like it to be generic and just tie it to the master fader instead of a specific cuelist. (Worse comes to worse, I could always edit the macro to reflect the cuelist I'm using before we do the cues, I suppose). I'm running 2.61

  • in reply to Wayne Simpson
    i'm running 2.6.2 an i don't think it's working as intended. Go is dynamically looking up which cuelist currently is assigned to the master, but Back always remembers the cuelist it was learned on.
    i'm not sure which of both is the intended behaviour but it probably should be the same for both...
  • in reply to ueliriegg
    Yes, that's what I determined. I tried many permutations of the macro command syntax, it does seem weird that they're different. I do hope if it gets fixed they leave the option to make the commands generic. Very useful.
  • in reply to Wayne Simpson

    Okay, issue solved, sort of... although it appears that you can record a generic "Go Master Fader" macro, it still seems to be tied to the specific cue list which was active when it was written. So my solution will be to edit the Go & Back macros to reflect the current cue list when I want to use the remote trigger. Here it is in all its glory. (Actually a prototype of pine, the real one will be mahogany). Using standard 5-pin data cable, though I only need pins 1, 2, and 3 for this application (+12v, contact 1, and contact 2. Works great! Possible next version to include a lock-out switch on the +12v side, to prevent accidental triggers.

  • in reply to Wayne Simpson
    Looks good.

    One way of making the editing easier is to have a 3rd macro that just contains the cue list number and then reference that in the other two, that way the edit is just enter the number in the one macro.

    ie the back macro would be

    Back_Cuelist Macro_Button 99

    and then if macro 99 just has 5 in it it will do a back on cue list 5. Using macros to store values is a kind of poor man's variables in macros like the $xxx ones on some competing desks.
Reply
  • in reply to Wayne Simpson
    Looks good.

    One way of making the editing easier is to have a 3rd macro that just contains the cue list number and then reference that in the other two, that way the edit is just enter the number in the one macro.

    ie the back macro would be

    Back_Cuelist Macro_Button 99

    and then if macro 99 just has 5 in it it will do a back on cue list 5. Using macros to store values is a kind of poor man's variables in macros like the $xxx ones on some competing desks.
Children
Related

www.etcconnect.com