BECOME PART OF THE COMMUNITY - Sign up here
  • All fixtures at the same time or one after the other?

    At the same time, this example would work. But be careful, no fog or other effect should be addressed via a dimmer.

    Line No. 1: Fixture 1 Thru At 100 Fade 10

    Wait Colum of Line 1: 40

    Line No. 2: Fixture 1 Thur At 0 Fade 10

    Selects Fixture 1 and all behind it, sets the value to hundred in a FadeIn of 10 sec.

    Waits 40 seconds from the start of the first command.

    And then fades out all fixtures again in 10 seconds.

    Timing must be switched on in the header (yellow font).

    --
    once upon a time at a venue with a dot2 XL-F

    now learning Chamsys at work - "Prev Head"-Button is at the right from "Next Head"-Button. ||

    at home and as a Freelancer GMA2-OnPC Setup with Command- and Faderwing

  • Possibly the "Exec Time" is activated and set to zero. This overwrites the fade times. Or the "Master Rate" is activated and is set to a small divisor.

    This applies to all fade times.

    --
    once upon a time at a venue with a dot2 XL-F

    now learning Chamsys at work - "Prev Head"-Button is at the right from "Next Head"-Button. ||

    at home and as a Freelancer GMA2-OnPC Setup with Command- and Faderwing

  • A cheeky work around you could always do is it create executors down the page that have a fade time on a cue for intensity moving to 100.

    Then you can just add the macro line to trigger the executor that has the fade on the cue. You could also add as much as you wanted to the cue stack to minimize the length of your macro lines.

    You can then also go into your "importexport' folder and see executor cue stacks you have created, listed as "sequences". These can be moved between shows, but also, you can again open it in a text document and extract the syntax to add to your macros should you desire to do so.

    Rhett Grantham-Smith

    Production Manager

    Venue Manager

    Lighting Designer

    Visual Artist

    Edited once, last by Rhett Grantham-Smith (May 20, 2024 at 2:46 AM).

  • No need to use an Executor for something like that. There are Macro presets. (you can also use the CMD in an executor to run a macro preset, or just run it straight from the preset)

    Mark Sneider has a good course on Dot2 Macros on Udemy. Here's a preview...

    External Content youtu.be
    Content embedded from external sources will not be displayed without your consent.
    Through the activation of external content, you agree that personal data may be transferred to third party platforms. We have provided more information on this in our privacy policy.

  • *To create a macro that implements fade times on a rig check, there are not predefined macros for that. You have to add in script into the predefined macro in your folders.

    You would need to create a macro that builds a cue stack for your rig check, or runs through it, personally i prefer it to save first then run through it off the cue when i require.

    Getting the cue stack to save from the macro with Triggers set to times and times set for the fade is slightly more involved, and time consuming, you can just build the whole cue stack, and then implement these steps as a whole post macro line being run.

    Here is an sample example of the Rig check i have added to my prefefined macros of my dot 2s. It sits at macro #47 (after a Auto create macro i made for my palletes, executors and faders etc on #46)

    (this is based off turning on your console on a new show, of-course you can load your shows with this built in already, i create these so any console around my company can auto create their rig checks with a predefined macro in their consoles, along with pallet, executor and fader building macros.)


    </Macroline>
    </Macro>
    <Macro index="46" name="RIG CHECK">
    <Macroline index="0">
    <text>Fixture 1 thru please</text>
    <info>Selects all Fixtures</info>
    </Macroline>
    <Macroline index="1">
    <text>Store at executor 0.1.1 please</text>
    <info>Stores cue stack</info>
    </Macroline>
    <Macroline index="2">
    <text>Label Cue 1 "Select Fixtures"</text>
    <info>Selects Preset Type</info>
    </Macroline>
    <Macroline index="3">
    <text>at presettype "Control"</text>
    <info>Selects Preset Type</info>
    </Macroline>
    <Macroline index="4">
    <text>Store at executor 0.1.1 please</text>
    <info>Stores cue stack</info>
    </Macroline>
    <Macroline index="5">
    <text>Select "Create Second Cue"</text>
    <info>Stores 2nd Cue</info>
    </Macroline>
    <Macroline index="6">
    <text>Label cue 2 "Select Control"</text>
    <info>Selects Preset Type</info>
    </Macroline>
    <Macroline index="7">
    <text>Attribute "LampControl" at 100 pelase</text>
    <info>Lamps On Fixtures</info>
    </Macroline>
    <Macroline index="8">
    <text>Store at executor 0.1.1 please</text>
    <info>Stores cue stack</info>
    </Macroline>
    <Macroline index="9">
    <text>Label cue 3 "Select Control"</text>
    <info>Selects Preset Type</info>

    Rhett Grantham-Smith

    Production Manager

    Venue Manager

    Lighting Designer

    Visual Artist

    Edited once, last by Rhett Grantham-Smith (June 3, 2024 at 2:59 AM).

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!