Jump to content

GDTF Forum

All Activity

This stream auto-updates

  1. Yesterday
  2. Last week
  3. Earlier
  4. 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... :) ++
  5. > 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.
  6. 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
  7. 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
  8. 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 :) ++
  9. 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
  10. 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
  11. Does D::Light support macros? We could add the Control Macros to our Robe device files. Please let me know, thank you Petr
  12. great !!! please keep in mind that as D::Light now parse gdtf files, thousands of theater compagny (large or small) have access to it :) best regards, Nicolas
  13. 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
  14. 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. ++
  15. 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.
  16. 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 ? ++
  17. 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
  18. Hello @Benjamin Jurina, try approaching the manufacturer directly with your request, they might not be on this forum... Best regards Petr
  19. Thank you. We will correct the typo.
  20. Hi, does anybody build an GDTF File for the LCPro ShowLED C6? I'm pretty new in the whole GDTF topic and I'm trying to get through the GDTF Builder, but it didn't worked. So my Question is if anybody has already a file or could build one? Thanks for your help.
  21. Hi, in T1 Profile it's written "Slow t ofast" I guess instead of "Slow to fast" Attached the description.xml corrected ++ description.xml
  22. 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
  23. 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.
  24. Hello @rubiolbernat, the builder already contains an error parser, you can see it on the last tab - Summary - Errors. Cheers P.
  25. How long typically does it take to have an account activated? I was able to get on the forum with no problem but when I go to "Share" it tells me my account is not activated? Any assistance would be greatly appreciated.
  26. May I suggest that newer versions of the gdtf builder include a fixture tester, which will greatly improve the workflow and usability. I don't know if its tecnically possible, but it will be great.
  27. Hello @Petr Vanek, Thank you for the update. I will update my GDTFs and look forward to this development!
  28. 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
  1. Load more activity
×
×
  • 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.