sl1200mk2 Posted April 4 Share Posted April 4 Hi, generally in manufacturer docs it's written that user must hold value during 5s or 3s in order to access function. This is true for resets, lamp On/Off, etc... I do not found in gdtf files such information. Am I missing something? best regards, nicolas Quote Link to comment Share on other sites More sharing options...
Petr Vanek Posted April 18 Share Posted April 18 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 Quote Link to comment Share on other sites More sharing options...
sl1200mk2 Posted April 18 Author Share Posted April 18 Hi Petr, ok... does it mean I have to modify all fixture's personality that require this field? or is it something manufacturer have to do ? ++ Quote Link to comment Share on other sites More sharing options...
Petr Vanek Posted April 19 Share Posted April 19 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. Quote Link to comment Share on other sites More sharing options...
sl1200mk2 Posted April 19 Author Share Posted April 19 which is a pitty... I saw console where you need to hold the button during 5sec before lamp goes off... I didn't knew I can edit them myself, i'll try. thanks. ++ Quote Link to comment Share on other sites More sharing options...
Petr Vanek Posted April 21 Share Posted April 21 Does D::Light support macros? We could add the Control Macros to our Robe device files. Please let me know, thank you Petr Quote Link to comment Share on other sites More sharing options...
sl1200mk2 Posted April 21 Author Share Posted April 21 (edited) Hi Petr, if by Macros you mean an hold time for Control Functions, then yes :) It would be very nice if you could plug your Robe files with Control Macros. best regards, nicolas Edited April 21 by sl1200mk2 Quote Link to comment Share on other sites More sharing options...
Petr Vanek Posted April 21 Share Posted April 21 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 Quote Link to comment Share on other sites More sharing options...
sl1200mk2 Posted April 21 Author Share Posted April 21 thanks for the link. so not yet, DL does not know about MacroDMX xmlNode. But if you have an example file I can write the parse for it :) ++ Quote Link to comment Share on other sites More sharing options...
Petr Vanek Posted April 22 Share Posted April 22 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 Quote Link to comment Share on other sites More sharing options...
sl1200mk2 Posted April 25 Author Share Posted April 25 Hi Petr, thanks, it works for me (see attached pict). 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? also do you plan to update them for 'Power / Special Functions' offset? (offset 6) also, could you please fix the "Slow t ofast" typo :) best regards, Nicolas Quote Link to comment Share on other sites More sharing options...
Petr Vanek Posted May 4 Share Posted May 4 > 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. Quote Link to comment Share on other sites More sharing options...
sl1200mk2 Posted May 5 Author Share Posted May 5 Hi Petr, thank you for your answer and your plan to update the rest of Special functions. IMHO it's the responsability of console manufacturer to ensure that value is held "at least" for the duration defined by the manufacturer. in D::Light case in means that value is held for 4.5s as you defined it to be 4s, I would much prefer that duration in gdtf files reflects what manufacturers says... :) ++ 1 Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.