Multi pixel fixture

[OGSON fixtures]

When writing a library for a multi-pixel device, e.g., a 21x21 RGB matrix, the device takes up over 1,300 channels. Is there any way to create something similar to a multipatch from the GrandMA system, but at the GDTF level, so that it would later be readable by GrandMA?

[Petr Vanek - Robe]

Hello, yes, you can use Geometry References in GDTF, this allows you to define an element once and use it many times via the geometry tree, it is then used by grandMA3.

[OGSON fixtures]

Hey. Thanks for the reply. I know how the reference works, and it's not what I'm looking for.

For example, we have the aforementioned 21x21 RGB pixel matrix. The idea is to create a mode that can route the signal to a group of pixels to reduce the number of necessary parameters without having to change mode on device.

In a 21x21 RGB system, there are 1323 channels, but if we create a matrix of 9 pixel groups, we create a 7x7 matrix, which takes up 147 channels. The idea is similar to multipatching in MA, to send a single RGB signal to physical pixels 1-9. The idea is to create a multipatch, but from the library level.

I expect this isn't feasible, but it's worth asking. Perhaps this is also a note to MA and to you about implementing a new feature, in an era where the number of parameters is multiplying like Easter bunnies 😉

 

cheers

[Petr Vanek - Robe]

What you want to look at are DMX breaks on Geometry References, you can define them either in Channel Function directly, or on the Geometry Reference, if you enable the Break Overwrite. The Break will create a new "DMX patch address" in gMA3. See more below.

The fact that you can create this on the Geometry (Break Overwrite) allows you to do other things too, for example we define a single geometry tree for the Spiider and in some DMX modes, by using the Break Overwrite, we can define different offset (for RGB vs RGBW channels):

 

cheers

Petr

[OGSON fixtures]

masterpiece! thanks