Posts by Andreas


    Rex & Sille,

    The gma3 Fixture Schedule is a representation of the real world.

    The real world includes not only lighting fixtures, but also any other physical items.

    When you hang a fixture on a truss, or put a floorcan on a drum-riser, they all need to be able to be connected in the same object tree, - you should recognize this from gma2 3D

    for virtual, nonphysical relations, e.g. "Wash Lights" you have two dimensions, Layer and Class, which can be used to group items you feel belong together, across any physical relations, which you later can filter by.

    Please also remember that this is version

    I am sure that we in the future will see improvements in workflow on the subject of importing scenery and other custom objects.

    to my understanding the "Setup Mode" is a "BlindEdit Mode"

    with the "Setup Mode" enabled, you can make (multiple) changes to your Network DMX-configuration, which doesn't affect network output until you switch off the "Setup Mode" again.

    This enables you to change configuration without transmitting unwanted network DMX while you change properties.

    e.g you are sending Artnet to Net 1 Universe 2, and you want to change it to Net 2 Universe 3.

    Enable "Setup mode"

    Change Net from 1 to 2

    Change Universe from 2 to 3

    Disable "Setup mode"

    without setup mode you would have transmitted on Net 2 Universe 2 for a brief moment.

    Further toggling of the Setup mode would not affect output (unless you make changes while it is enabled)

    You need to use a screen that natively supports displayport. (that actually has a displayport (DP) connector inbuilt)

    Typically there are two different types of adapter cables from DP to HDMI, Passive and Active adapters:

    The passive adapter cables requires a Dualmode Displayport source.

    - the grandMA3 does not have a Dualmode Displayport output

    The active adapter cables requires power from the Displayport source

    - the grandMA3 does not supply power on the Displayport output

    To enable realtime instant playback, (- both in gma2 and gma3), any referenced presetvalues are "cached" locally inside the sequence, rather than being looked-up every time.

    In version , please use the regular workflow of making changes in the programmer, then Update (or Store /merge) to update the content of Presets, and at the same time properly automatically trigger the internal procedure that propagates your changes into the cues by updating its cache.

    If you in version want to change the content of the preset by other means, e.g. by copying other objects into it, through a macro, you will have to add a Recast command in your macro as well, to trigger this cache-update manually.

    1. try pressing the Stomp key, then "Color" in the encoderbar, before picking yellow in the colorpicker.

    2. Width is the time for a given step expressed in percentage of the speed

    3.Yes, there are still room for improvements in the graphical presentation in the phaser window

    While we all have big expectations for the new grandMA3 software, please don't forget that just now, she is still a baby, - born last week.

    She is smarter than her 10 years older sister was – when she was born, which again was smarter than her elder sister at that same age.

    You will however need to give her some time to grow, develop and mature, before she will surpass her elder siblings as they appear today.

    the onPC system requirements specify a minimum of 6th generation processor, while I believe your Lenovo Y70-70 has a 4th generation processor?

    from generation 6 and above the bus speed is 8 GT/s, over 50% more than the 5 GT/s of generation 5, 4 and below.

    Maybe the reduced bus speed becomes a bottleneck, even if your system otherwise should be powerful enough

    The proper syntax for a generic toggle macro would utilize the Default keyword and object-labels, and look something like this:

    Edit ScreenContent Default."WindowFixtureSheet"."FixtureSheetSettings" Property "ProgOnly"

    If you have multiple FixtureSheets on one screen that should toggle individually, the macros would need to know the index of each window,

    In both your views the fixturesheets apparently was created as the first and the fourth window:

    ProgOnly A

    Edit ScreenContent Default.1."FixtureSheetSettings" Property "ProgOnly"

    ProgOnly B

    Edit ScreenContent Default.4."FixtureSheetSettings" Property "ProgOnly"

    actual MIB behaviour depends on the content of your cues, both on dot2 and gma2.
    - to get the same behaviour, you need to have the same content in your dot2 cuelist and your gma2 cuelist.

    please load your dot2 file in the gma2 and compare in trackingsheet the content of cue 2 in your gma2-file vs dot2-file.

    Pulling up the dimmer for the fixtures which should prepare/MIB is not a workaround, it is the intended workflow, - the nonzero dimmervalue is the actual flag that indicates that MIB should be performed

    Cue 1 fixtures 1 thru 10 dimmer at 0%
    Cue 2 fixtures 1 thru 10 Full, with tilt at -45 degree and Soft Dimmer effekt for dimmer, fade time 4s

    Be aware that as the dot2 only has absolute dimmer-effects, you weel need to pull up the dimmer prior to starting the effect, as (for your convenice on dot 2) the effect is automatically stomped, if you apply the static value after the effect has been called

    I would expect any issues is more likely to be cased by switching to battery power than by disconnectng the node.
    Check your Powersave options.
    Most laptops will by default will enter powersavemode when runing on batteries, reducing the overall performance of your computer, like lower the CPU clockspeed, switching from dedicated to intergrated graphic etc etc., which is not good for GPU hungry applications (like 3d and onPC)