> In the manual it's written: To activate following functions, stop in DMX value for at least 3 seconds. > Why did you set 4s in the macros? This is because if the timing on the console is not precise (for example 2.9 sec instead of 3.0), the macro would not execute on the device We see this frequently with controllers. As 3 is the minimum value ("at least 3 seconds") , defining it 4 is OK. >also do you plan to update them for 'Power / Special Functions' offset? (offset 6) Do you mean for the rest of the Special functions? Yes, we can. >also, could you please fix the "Slow t ofast" typo 🙂 I re-reported this to our library maintainer.

Hi Nicolas, the T1 Profile now contains several macros: ColorControl macros (these use just one channel + timing) and also few Control macros (Display on/off) (it uses the control channel + shutter channel + time). You can see the updated file here: https://gdtf-share.com/user.php?name=Robe+Lighting+s.r.o.&page=fixtures&fixtureID=2522 Btw, there is an API for software vendors to access the share programmatically, you can email info@gdtf-share.com for access. Larger companies use this API for syncing the share to their own access server. Cheers Petr

Hi Nicolas, by macro i mean this: https://github.com/mvrdevelopment/spec/blob/main/gdtf-spec.md#macro-collect Does D::Light support that? I tried to figure it out but i could not find out. It is like a dynamic pallet, provided by the device file. Cheers Petr

Does D::Light support macros? We could add the Control Macros to our Robe device files. Please let me know, thank you Petr

PL&S has published their calendar, you can find GDTF related talks here (click through each day): https://pls.messefrankfurt.com/frankfurt/en/programme-events/events.html#/?day=2022-04-26&q=GDTF https://pls.messefrankfurt.com/frankfurt/en/programme-events/events.html#/?day=2022-04-26&q=MVR https://pls.messefrankfurt.com/frankfurt/en/programme-events/events.html#/?day=2022-04-28&q=15800

The author of the file can add this in or you can also modify the file yourself but I am not sure what the uptake is in the DMX consoles at this point for the DMX Macros.

Hello @sl1200mk2, You can do this via the DMX Macro (Macro in the Builder). This allows you to specify required channels and timing. Kind Regards Petr

Hello @Benjamin Jurina, try approaching the manufacturer directly with your request, they might not be on this forum... Best regards Petr

Thank you. We will correct the typo.

Hello @Align_Design, it takes few minutes max. Are you using the same login? Make sure to sign in on the front page: Kind regards P.

Hello @rubiolbernat, the builder already contains an error parser, you can see it on the last tab - Summary - Errors. Cheers P.

Hello @Beglec NV, there is the idea for linking GDTFs but that is not yet developed further. You could probably either do this in MVR or what i would do is that i would make a GDTF for each product at this point. Kind regards Petr

Hello Juan, let me pass this request to our GDTF library team. You can also contact them directly at libraries@robe.cz . We will create the GDTF file which you can then convert into MA2 in the MA share converter. Kind regards Petr

Hello, most likely this is not visualized in MA yet, let me add @dmueller in cc to confirm this (thank you Daniel). Kind regards Petr

Thank you @Paolo.Prolights, i can replicate the issue and it has been reported. Cheers P.

Hello @sl1200mk2, these are "Virtual channels" - they do not control anything via DMX directly but can be used for example to create a virtual dimmer by adding a relation: or allow to control a geometry in a visualizer. So the T11 virtual channels allow the operator to set things like tilt, zoom... in visualizer, based on real physical world values, so visualization can correspond to the real unit. Hope this helps. Cheers Petr

Hello @sl1200mk2, the sets are used in this way to tell the visualizer and the console the exact physical value for exact DMX value in cases where the relationship is not linear. In GDTF 1.2 this is solved by using curves which define relation between physical values and DMX values. In GDTF 1.1, we work around the issue by filling the channel sets. Historically, the builder required the name to be filled in so we did, but this was corrected and the name can be empty, which we try to do now. We will erase the channel set description, this will allow you to identify it as possible to skip and when 1.2 starts being widely used, we will stop using channel sets for this workaround.

Hello @Paolo.Prolights, this should be fixed. At this point i have not tested the fix so please try it and report here in case the issue persists. Thank you, P.

The validator for the Share is currently work in progress and at the moment there is no public API for the validation. You can use the XSD schema for offline machine validation if needed. Kind regards P.

Thank you, this is a small thing. Reported.

Thank you for the request @Paolo.Prolights, i have added it to the request list. Cheers P.

Thank you @Paolo.Prolights for the report, i replicated the issue and reported to the developers. Cheers P.

Hi @Paolo.Prolights thank you for the report, we will check this. Cheers P.

Hello @tibert to search for the files, you need to use the GDTF Share: https://gdtf-share.com/share.php?page=home I am not sure of the detailed name and if it exists or not, but you can check here: https://gdtf-share.com/share.php?page=home&query=chauvet&man=1&fix=1&rev=1&use=0 cheers Petr

Hello, you import individual models, i would suggest to look at some of the videos, mainly look at the training section here: https://www.youtube.com/channel/UCkn8qU02YTkjPdeVEeQPjVQ/playlists Also, look at this forum post, explaining this topic: cheers Petr