Posts by Andreas



    The Stage tab lets you define objects that divides the whole Schedule into different physical Location, and are userdefinable top-level objects in the object-tree, each with its own bounding box and own origin/zero-point. Use multiple stages if your system covers multiple venues, rooms or stages.

    A 3D Window (Formerly known as Stage Window) will visualize one Stage (or Room, Venue etc)

    With the Stages concept you can visualize different venues/stages/rooms in different 3D Windows, within the same showfile

    Try to get familiar with the Filter button. (shaped as a funnel in the top right) When your object tree grows, using Filters to only see what you want is a big help for navigation.

    If you want to filter on your own terms, not only by Fixturetype, or DMX address etc, head over to the Layer and Class tabs, and create your person grouping preferences.

    e.g. Layers: Floor, Roof etc

    e.g. Class: Wash, Spot

    assign the appropriate Layers and classes to your fixtures, and use Filters to easily find your Wash fixtures that are on the Floor.

    Unfortunately the background properties didn't make it to the "List Appearance x " response in the commandline feedback window in this very first release version.

    It seems however even if not being exposed by commandline feedback you can still manipulate these properties by syntax.

    Please try the property names BackR, BackG, BackB and BackAlpha, with decimal 8bit values (0-255)

    Be aware that this syntax likely will change in future version, for consistency in property naming and value format

    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.

    the conversion from gma2 library to gma3, of this fixture with two tilt heads, corrupts the attribute setup creating two attributes for the same tilt function, confusing the phaser editor.

    attached is a showfile, where as a quickfix, I have removed this problem

    the fixture however will not visualize properly without a total rewrite of the fixtureprofile.

    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"