Jump to content

GDTF Forum

dmueller

Moderators
  • Posts

    70
  • Joined

  • Last visited

  • Days Won

    7

Posts posted by dmueller

  1. Hi Nikolaus,

    Unfortunately there is a bug in grandMA3 that causes Master set to 'Grand' and 'Group' to behave in the same way. In grandMA3, a logical channel with master 'Group' should not react to the grand master. With 'Grand', however, both a group master and the grand master should have an effect.

     

     

  2. Hi @r2.square

    There are several possibilities when selecting a subfixture within a parent-child structure and changing the value of an attribute via the encoder:
    1) The attribute exists at the level of the selected subfixture -> the value of the channel of the subfixture changes.
    2) The attribute does not exist at the level of the selected subfixture, but its parent has a channel with this attribute -> the value of the parent's channel changes.
    3) The attribute exists at the level of the selected subfixture and its parent has a channel with the same attribute -> only the value of the subfixture's channel changes.

    With 2) it is possible to control the pan/tilt of the main fixture even if I have only selected one subfixture. The same applies to the effect channels in your case.
    Select fixture 1.1 and turn the encoder of the FX1 channel. The value of the effect channel will change as the value change is passed on to the parent.

    I could imagine that you may have stumbled across the bug that if you select subfixture 1.1, open the FX1 channel's calculator and select one of the pre-defined channel sets for the effects, no value change occurs. I will create a ticket for this bug at MA.

    I hope I understood your question correctly.

    With kind regards,

    Daniel

    • Like 1
  3. Hello Brothers,

    Thanks for the report. The connection of the grandMA3 to the GDTF Share is now working again.

    Best regards,
    Daniel
    GDTF Team

    • Like 1
    • Thanks 1
  4. Hi @Paolo.Prolights,

    issue with this GDTF file is that it is a compressed zip. A GDTF file shall be uncompressed zip.

    After I removed the compression the parser of the grandMA3 library correctly parsed the name of the fixture.

    I can recreate that patching the fixture fails in grandMA3. I have to take a closer look what is the reason for this behavior.

    Kind regards,

    Daniel

  5. The GDTF Builder 1.3.12 is now online.
     
    Improved in this release:

    Fixed: it was not possible to enter values for the property Beam Diameter of geometry type “Beam”. 

    Fixed: DMX values were not properly recalculated when copying a channel function to another DMX channel that had another resolution. 

    Fixed: it was not possible to reorder mode master containers by drag ‘n’ drop. 

    Fixed: parsing errors in the fixture template „Moving Mirror”. 

    Improved stability. 

  6. Unfortunately, you found a bug in the grandMA3 Visualization. It seems that ColorAdditive Attributes on the same level of the kinematic chain but in different geometries (Led4Eck, Led Rund) are mixed together to the same color instead of being independently controllable for each of the geometries.

  7. The 3D visualization of the grandMA3 in version 1.0 does not visualize all attributes yet. For example, the visualization of the framing is one of the attributes that is not supported in the current version.

  8. Hi MattG,

    nice idea. I'm afraid that it will become confusing and complex if this kind of linking would be done in the xml. I would suggest having something like a "apply changes to the same channel in other/selected modes" functionality in the builder for quick editing of several modes at once. 

    What do you think @mgeasey@clearallvisualsllc.com ?

    Cheers,
    Daniel

  9. I will have access to an LED strobe in my office next week. I will do some real-life tests with it.

    I guess the visualizer has to handle the behavior of Duration vs. Rate and when the strobe as a result of both values is full = wash.

    This is taken from the manual of the Robe Colour Strobe:

    image.thumb.png.9ff96f4db18d943eedc9e7fdeb4dfdb0.png

    I think handling this with a mode dependency would only be a "hack" for visualization. 

    Cheers,

    Daniel

  10. How would it be in real life? Duration and Rate have to be at full to have the LED stay on?

    I had a look at the Atomic 3000 LED.

    Duration is 7-650 ms

    Rate is 0,289-16,67 Hz

    Does the LED stay on if the duration is > 1/f ?

    For example if the Duration is 500 ms and the rate is higher than 2 Hz?

  11. I guess I found the issue. The GDTF export of the grandMA3 does not export the file with the custom name of the channel function but with the default name (which is "Name of the Attribute <blank> Index of the channel function -> e.g. Dimmer 1).

    If I change the name of a channel function in the GDTF Builder, upload the file and open it again in the builder everything is fine.

    The grandMA3 displays the custom name of a channel function only when you edit a fixture type. The encoder bar does not display the name of the channel function but the pretty name of the attribute that is assigned to the channel function. 

    Pretty names of attributes in grandMA3: If you import a fixture type that has custom pretty names for its attributes these custom pretty names will only be used in the grandMA3 if the attribute does not exist. If the attribute already exists in the attribute definition (Menu - Patch - Attribute Definitions) the grandMA3 will use the properties of the existing attribute. This is the same behavior as it is in grandMA2.

×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.