Posts by dherderich


    I'm not sure that the Page, Fader, Knob and Key do,

    It is a remapping.

    If the sender sends /Slider instead of /Fader to address the fader of an executor, you can set the cell in the Fader column to Slider.

    The off time is no longer a property of the executor.

    The sequence has now always an OffCue like a normal cue. The fade time you set for the OffCue is the OffTime.

    Yes, it works.

    Check, that the Merge Mode of the universe is not set to Off. When you set it to HTP, then you should see immediately the incoming values.

    Load Previous and Load Next the intendend commands for this action, but yours work also.

    Why does it only work on consoles in your opinion?

    Transition: How long the crossover from one step to the next step is.

    Acceleration: Describes the transition curve for the last half (of the transition) into the step.

    Deceleration: Describes the transition curve for the first half out of the step.

    Acceleration Step 1|Step 1|Deceleration Step 1|Acceleration Step 2|Step 2|Deceleration Step "|....

    Open the phaser window, create a 2 step phaser with dimmer values and play around with transition, acceleration and deceleration, and you will easily see, how they react.

    A cue part is a sub-part of cue.

    A cue part has its own cue timing (fade, delay, etc).

    In grandMA2 you could store your programmer only into 1 cue part. Therefore, you had to store each single cue part, you wanted to use , within a seperate action of getting values into the programmer and then storing them into the desired cue part.

    Now with grandMA3 the programmer is also able to handle part, which are called then programmer parts.

    There is a dedicated Prog. Parts window available where you can see all parts the programmer has active at the moment.

    The fixture sheet has also a button in the title bar, called Part, which displays in which part of the programmer you are currently working.

    By default, you're working in Part 0, which was also the default in grandMA2 when storing a cue.

    When storing now a cue, and the programmer has several parts active, the part structure will be stored also into the cue.

    Parts are often used to separate different fixtures (e.g., stage, audience, etc.) or different purposes (e.g., dimmer, color, gobo, etc.).

    In grandMA3 when calling a phaser preset into the programmer the software will automatically create a new part in the programmer for the values of the phaser. Each different phaser will be put into a new part.

    All static stuff is located in part 0.

    This makes it later possible to distinguish the different effects when editing the cue. Think of a dimmer phaser and a color phaser, which should run independetly. If they would be in one part together, it will be nearly impossible to distinguish from which phaser you are now editing the values.
    This becomes more important when doing effects on the same parameters (grandMA1 multi line effects).

    Hope this clarifies it a bit. ;)

    It defines into which part in the programmer the preset will be put upon calling the preset.
    When storing then the content of the programmer into a cue, the programmer parts will be stored correctly into separate cue parts.

    I can't reproduce this crash.

    Can you get in contact with the TechSupport and provide them your show file where it crashes and a step by step description of what they have to do to reproduce the crash?

    Yes, this is the chat when being connected to the World Server (= green world symbol on the right-hand side of the command line). With the chat command you can send chat commands into the main chat room. At the moment there is only the main chat room available.

    Midi Index >> Note/CC number + 1 (MIDI range 0-127, MA3 range 1-128)

    This is a bug which will be fixed within one of the next releases.

    Trigger On: If this threshold is reached when increasing the value, the target will be "executed".

    Trigger Off: If this threshold is reached when decreasing the value, the target will be "switched off".

    I think this could be tested with Temp as key function.

    Create a grandMA2 show file with these fixture profiles, convert the patch of this grandMA2 show file via Backup menu in grandMA2 to an grandMA3 show file (at the moment only the patch with fixtures and fixture types will be exported. More to come later.).
    This file can be loaded in grandMA3 and from there you can export the fixture types as converted (from grandMA2) fixture types and use them in other grandMA3 show files.