Submasters, Macros, and Magic Sheets

I have an ETC Puck running Nomad software for control; no physical console. We use buttons on Magic Sheets to toggle submasters on and off. I have a macro that dims submasters:

Sub 605 Thru 607 @ 70 Sneak 2 [Enter] [Clear_CmdLine] [Enter]

And another to raise the subs:

Sub 605 Thru 607 @ Full Sneak 3 [Enter] [Clear_CmdLine] [Enter]

However returning the subs to full with the second Macro prevents using the Magic Sheet submaster buttons from turning on / off those subs. I have to go to the command line and manually turn off the subs in order for the Magic Sheet to work as expected again. Is there something I should add to the Macro to release control of the Subs?

Parents Reply
  • Hi Ryan. 

    Using the Macros with this syntax does not allow you to toggle those subs on and off because Macros are not toggalable.

    Hitting the MS Button 1 (Macro 34) sets your sub to full. Hitting it again will set it to Full again.

     Hitting MS Button 2 (macro 33) will set your sub to 70. If you hit Button 1 after it will set the Subs to full and with Button 2 they are back to 70. you wont be able to turn off the subs if you don't have a button to set the subs to 0.

    Maybe this is the issue?

Children
  • Yeah, you need another macro with a button.

    Sub 605 Thru 607 @ 0 [Time] 3 [enter]

    In this example I would use Time rather than Sneak. Sneak removes manual values from selected channels. And what your doing is moving a virtual fader so to speak.

    AND you want to run this kind of macro in the Background, your screenshot shows it's on Foreground, this interferes with your commandline.

  • Sneak is perfectly fine for controlling the fade times in your syntax.

    [Sub 605 at Full Sneak 3] acts identically to [Sub 605 at Full Time 3] when controlling Subs.

    If you want to fade in manual values, you're actually forced to use sneak.

    [Chan 1 at 5 Sneak Time 3] fades Chan 1 to 50 in 3 Seconds
    [Chan 1 at 5 Time 3] sets Chan 1 to 5 in 0s and sets a discrete cuefade time of 3.

    I do agree though, that the Macros should run in background mode, since if you're not on an empty command line, you might get a syntax error or unexpected behaviour of the macro. 

Related