Posts by dherderich


    May it be the case, that the record button is not grayed out, but you renamed the timecode object in the pool?

    Or is maybe the timecode object locked?

    Possibly a screenshot of what you want to describe can be helpful.

    Please note also, that you record the events in a timecode and not in a timecode slot.

    Not directly, but you can create a macro with this command:

    Menu "MatricksOverlay"

    When you assign the macro to an executor you can create a keyboard shortcut to reach the executor.

    When you have a crash, please reach out to the tech support or your local distributor.

    Please provide them the show file, the steps to do in order to recreate the crash, and the crash log(s) (if not already uploaded via the world server).

    Go to the gma3_library folder and from there you can reach datapools/plugins and media/images where you have to put the plugin itself and the images.

    Within the gma3_library folder structure the files can be used by any future version. With the old instructiions using the gma3_vx.y.z-folders you would have to copy the files for each new version.

    You could create your own "DMX camera feature" via a plugin, that reads out the DMX channels of a patched MArker fixture.

    These DMX values can be recalculated with defined dimensions into XYZ coordinates. These coordinates can be applied to a camera. After refreshing the camera in the 3D window, the new position of the camera can be recognized in the 3D window.

    When the plugin does this 30 to 60 times in a second the movement looks not so bad.

    The position of the MArker fixture can be stored into cues with fade times.

    This is from the v1.7 release notes (Other Enhancements section):

    The fixture type editor now displays if there will be conflicts between the default value and the defined channel functions and channel sets, e.g., in case that the channel functions do not cover the set default value. In this case Show conflicts will be displayed at the bottom of the fixture type editor. Tapping it opens a pop-up that tells where the conflict is located.

    In addition, the name cell of the affected DMX Mode and the name cell of the affected attribute will be highlighted with a red font color, and the corresponding values will be highlighted in orange.

    The 1. in front was the identifier for the global pool. But this concept got never further developed in grandMA2. In grandMA3 these are now the data pools.

    No longer need the preceding "1." anymore either, just "macro_number.macro_line"

    If you want to trigger macro lines from other data pools, then add DataPool in front, for example Call DataPool 2 Macro 3.1 (Second data pool, third macro, first line)

    As long as you want to trigger a macro of the currently selected data pool, it is not necessary to add the DataPool-part to the command.

    But if I Move or Copy it ignores the empty spaces

    Copy Collection at Group 10 :thumbdown:

    Unfortunately, this cannot work, as Collect is targeting the object index. When group 2 and 4 are empty, there is no index it can collect.

    Internally your collection is then only Group 1, 3, and 5. Without any gaps.

    I believe that note is left-over from earlier in the development process, and should be getting corrected (at least, in the online version of the notes).

    This one is now corrected in the online version of the help:

    Release Notes 1.7 - Release Notes - Help pages of MA Lighting International GmbH

    That's actually really handy to know as I hadn't had that explained in this way before.

    So it wasn't a bug at all, just a different way of the functionality working.

    Yes, that's also the reason why this is mentioned in the What's Changed section in the release notes. And not as a fixed bug.

    If I have a Fixture in color black (0,0,0), enable Program XFade then change the color to red (100,0,0) then move the fader to 10% the resulting Red value is something like 27% and not 10% as expected. Is it trying to do some fance CIE adjustment, and if so is it backward?

    This can be the case depending on the emitter data of the used fixture type.

    The IP2 on nodes is used for the MANet connection (but you can select the interface also within the grandMA3 software on the node itself to use the other IP). The first line of the IP is the secondary IP address of the interface and is mainly used for broadcast protocols, for example, Art-Net (at the moment only when the node is running in Mode2).