Hi Petr, thanks you for your answer. I've adapted the strategy in my software, so now it's painless for me. best regards, Nicolas

Hi there, I created an add-on for importing .gdtf and .mvr files into Blender3D. It is possible to control the fixtures with custom attributes or just to check if a MVR was properly exported, maybe some are interested in it. Here is the link to the add-on: Scene MVR (.mvr) and GDTF (.gdtf) Here the link to the github page: io_scene_mvr

Hi Nicolas, interesting. I have tested this Martin file and can confirm the issue. As Martin does not utilize the GDTF Builder to create the fixture files, i suggest that you contact them and i am sure they will follow up. Theoretically, we could try to handle this in the GDTF Share, but there are risks associated with changing of the uploaded data. We will discuss it. What i would suggest the most is to unzip with better default permissions, or run something like chmod -R +xrw models on the unzipped files, which then always allows you to remove them later. Cheers Petr

Hi, this file for example Martin_Professional@ELP_PAR@20241107NoMeas.gdtf have 555 permission on some folders. I don't know if it's a usual practice but in my app I decompress .gdtf files, use what I need and then *delete* extracted files/folders. But with 555 permission I'm screwed. Is there's a way for you guys to prevent/modify permissions? for all of files to be at least 755? best regards, nicolas

We have deployed some quality of life improvements to the GDTF Share, revision listing page: The "Open in GDTF Builder" button is now available above the Wheel previews The DMX modes listing now displays channel count per Mode in Plain View DMX modes are collapsed if a revision has more than one DMX Mode. DMX Mode is expanded if there is only one The DMX modes section now has the same background like comment section to visually separate it from Revision history and "Who tagged the revision"-section.

GDTF will be exhibiting at LDI 2024 on the Booth #2145 . Visit our booth for: Live Demos: Experience GDTF and MVR in action and see how it can transform your projects. Exclusive Insights: Manufacturers, join industry leaders to discuss how you can best support your customers. Fun Swag: Pick up your new favorite GDTF t-shirt and other goodies. Registration available here.

Hi @r2.square, some of the complex fixtures' behavior, especially in the context of a visualizer, cannot be easily described. Controlling is typically not affected by it. There have been discussions about it and also a few internal prototypes, see for example this and the linked issue, which lately tried to shift from concrete to a bit more abstract definition, to help to nail down the requirements. Kind regards, Petr

I just recently started drilling down into GDTF and stumbled upon what I found to be an unfortunate limitation. I'd love to discuss with more experience GDTF users. Background: For the sake of this discussion I'm focusing on my setup of a grandma3 console and Martin Mac One fixtures. The Mac One has a single effects channel (22) which triggers effects across its two geometries, Beam and Backlight. Values 0 to n trigger Beam effects. Values n+1 to 255 trigger Backlight effects. Martin has defined a ton of Logical Functions along with corresponding Channel Sets. Martin has bound DMX Channel 22 to the Base geometry. This has a serious of consequences: grandma3 created two sub fixtures Beam and Backlights. The complete range of "mixed" effects (beam and backlight effects combined) is available when selecting the main fixture. When selecting just one of the sub fixtures, e.g. Beam, the Backlight effects are still offered, though they obviously do not make sense on the Beam sub fixture. When selecting just one of the sub fixtures, Channel Sets stop working completely, even those, that would apply to the selected sub fixture. (Not sure whether this is a grandma3 bug or what's the reason for this.) Wouldn't it make sense to allow binding of Logical Channels to geometries, instead of exclusively allowing to set it on a per DMX Channel level? If this would be supported, I could ideally: Create a single DMX Channel 22, along with all Channel Sets relevant to the complete fixture and bind it to the Base geometry. Add a Logical Channel for All-things-Beam along with all Beam related Channel Sets and bit it to the Beam geometry. Add a Logical Channel for All-things-Backlight along with all Backlight related Channel Sets and bit it to the Backlight geometry. I think, this would greatly enhance the usability and clean up some of the Encoder Bar clutter, that we find all too often when using more complex fixtures. As I said, I'm relatively new to the inner workings of GDTF. If what I'm describing is already supported in some other way, I'd love to hear how. Thanks for looking into this and happy discussing!

@ACME-Lighting I edited the gdtf file you posted and have attached it to this post. Unfortunatly the solution with the relations it is not working with CTO, Strobe and Colorwheel, it only works with ColorAdd RGBL. Now both modes are working, maybe you have to add some virtual dimmers if you want to dim the rings and beams seperately. ACME@TORNADO__(TB_5_IP_)@Changes_by_Sille.gdtf

Dear @ACME-Lighting, yes, as pointed out by NRG Sille, we have looked into this in Robe and provided some guidance and ideas in this post. There still are limitations when describing some of these complex devices and the GDTF Group has been looking at different ways to solve this in the future. One of the possible proposals is described here.

Mr. NRG Sille, thank you for your reply. According to your method and some of our own thinking, we have written the light library so far, which can realize the separate control of beam area and LED light ring area. The main use is to virtual channel all sub-beam and sub-LED aura, and then use the "override" function to realize joint control. As shown in Figure 1, the beam is cyan and the light ring is white. However, there are still two problems: 1. The second set of colors cannot be defined in the light library function, as shown in Figure 2, so we use the customization function to customize the second set of colors (for the led light ring). The first set is used for beam), as shown in Figure 3, but this definition cannot be reflected in 3d, and the light ring can only light the full value. 2. We used the same method to deal with the CTO and COLOR functions of beam and found that the CTO and color functions of beam would affect the LED halo, as shown in Figure 4 and Figure 5, and would influence each other in the stroboscopic function area. Either shutter1 or shutter2 alone controls both the beam and the led ring area. I will put the light library file below, please give a light teacher help to look at. ACME@TORNADO__(TB_5_IP_)@TORNADO__(TB_5_IP_)-11-5-7-daijiejue.gdtf

I also meet the same questiohn

@ACME-Lighting I started a discussion about this some time ago, there is no proper solution for some problems yet. I tried it with a reference on a referenced head and it works with the beam but not with the ring. The reference wich comes first in the list always works but the second reference did not link in a test with MA3. Here is the link to the discussion:

Dear Mr. Peter, there is a lamp named Tornado, which has five independent lamp heads that can rotate vertically around and back, and each lamp head has an independent main beam and lamp head lamp ring. At present, there is a mode that requires each lamp head to move vertically around and back, while requiring the overall control of the main beam and lamp ring of the five lamp heads. This means that each lamp head has its own corresponding DMX channel control, but the five main beams of the five lamp heads have only one channel to control (or only four RGBW color channels to control the color of the five main beams as a whole). There is only one channel to control the five light rings of the five lamp heads (or only three RGB color channels to control the overall color of the five lamp heads). At present, I use the reference function to compile each main beam and lamp ring, and control the main beam and lamp ring of the five lamp heads jointly by controlling the properties of the referenced objects. At the same time, each lamp holder has its own function of moving around and back, but I failed, because the DMX value of the reference object must be defined to use the reference function, and I cannot skip this link. I would like to ask Mr. Peter if there are other ways to achieve this function.

Hi @Petr Vanek - Robe, thanks for reporting. Kind Regards.

OK. Thanks.

@lohint click the three dots menu and select Delete:

Hello, I might have missed something, but I cannot figure out how do I delete a library I've uploaded to gdtf-share thanks

Hi @Paolo.Prolights, thank you for the report. I think what happened is this: originally when implementing it we had the first (original) geometry there 2x. We eliminated this but it seems that while we no longer have the first geometry duplicated 2x, we lost the address of the first one. I will report this.

Hi there, Has anyone had anything to do with this feature? I honestly can't get it to work properly. As for online duplication, no problem. What happens with the rectangle is this: I add pixel 1 under a normal geometry (top level), I define the pixel as a geometry reference of another top level, as always. I create a dmx mode and add at least one channel associated with the geometry reference otherwise it would not be possible to set the offset in the properties of the gerometry reference, in this case for me it is 1 as it is the first. I select this geometry and try to create a duplication with arrange using rectangle. Count X=21, Count Y=3, Count Z=1, Offset X=24, Offset Y=24, Offset Z=0, Address Offset=4 (As for RGBW pixels). What happens is that all the geometric alignment is correct but the offset count starts from 5 and no longer from one. In practice, it adds the value 4 to the starting value one, but in doing so it is all out of phase by 4 addresses. This function seems to only work by leaving address offset at 1 in the duplication tool. Can anyone tell me how to make this tool work properly? Thanks. Kind Regards.

Manufacturer moderation Manufacturers have special power that allows them to manage "their" manufacturer folder/category to keep it organized. To use their "moderator" tools, there is a "Moderator" in the "Show" filter: This allows manufacturers to rename the name of their folder. This is why Robe folder is called "Robe Lighting" while the name of our company is "Robe lighting s.r.o.": Moderating operations can be done on device "subfolders" or on individual files - folders can be merged and renamed: Individual files can be also moved around or have their Revisions renamed: Individual files can also be set to hidden for public by setting their status to WIP (work in progress): Manufacturer's pages Each manufacturer also has a dedicated page with a representative listing of the files for their devices, here is what it looks like: Hope this helps Petr

For device manufacturers who provide or would like to provide GDTF files for their devices, we provide extra features in the GDTF Share and in the GDTF Builder, like brand category management, manufacturer landing page or download only (no upload to GDTF Share) option in the GDTF Builder. There is a dedicated section in the forum and also a monthly manufacturers meeting about GDTF and MVR. Account registration If you are a device manufacturer, your first step would be to register a free account in the GDTF Share (https://gdtf-share.com/). Then continue and register in the GDTF Forum (https://gdtf-share.com/forum/) with the same email. Often companies use info@... or gdtf@... email, to have company wide address not linked to a single individual. Make sure to use an email from a domain which clearly asserts connection with the brand. Get in touch After creating the account, use the Contact us page and let us know the email address you used in the GDTF Share and in the Forum, so we can mark your account as a manufacturer. This will give you the possibility to manage your manufacturer brand in the GDTF Share and will provide you with special access in the GDTF Forum, which is the place to ask further questions about GDTF. Once you let us know the email used for registration, we will also add your email to our list of manufacturers who receive an invite to the monthly GDTF/MVR manufacturers meeting, where we discuss progress, proposals and questions. Past meeting notes and meeting recordings are available in the GDTF Share Forum, in a dedicated, Manufacturers only accessible section area, link here. Enable manufacturer page As for being listed on the GDTF website in the Manufacturers section, please send us your brand logo as a png image on transparent (alpha) background with a resolution of 512 x 512 pixels and also in the GDTF Share enable your Manufacturer page in the Edit Profile of your account: This then provides nice listing of your files which you can customize and share with your customers, see this example page. The page can be customized with logo, header image and news posts: Information about GDTF Share moderation tools for manufacturers: To create GDTF files, the GDTF Builder application is used (https://fixturebuilder.gdtf-share.com/). To learn about the GDTF Specification, GDTF Share, GDTF Builder and more, please see the Documentation resources post:

Hello all, we have released another big update to the GDTF Builder. There is new functionality, improvements and bug fixes. New features: Add 2D geometry workflow - upload 2D geometries, position them and view in 3D space Add support for Gamut collect and add Gamut linking to DMX channel function Show an arrow indicating Laser geometry direction Show Magnet geometry in 3D space Support DMX Macro Channel Function linking Display Builder build number in status bar Improvements Add undo/redo for fixture properties like weight, leg height, and operating temperature Improve the spinner animation during file upload to the GDTF Share Improve DMX error checking - ensure linking of Wheel Slots to ChannelSets where applicable Improve geometry rendering performance Allow to unset Connector type When editing wiring objects, ensure that correct geometry is displayed Do not allow to enter restricted characters for revision text Show error if Emitter/Filter names are not unique Display correct wildcard number of the main attribute Bugfixes Fix link to correct documentation CIE Color Conversion Fix When duplicating mode containing virtual channels, ensure that relations followers remain linked Fix macro duration undo function Fix Beam geometry diameter indication arrow being placed in wrong position Fix displaying wildcard attributes Fix Uploading a specific GDTF which could cause TypeID collision Emitter tooltip "Luminous Flux" fix

Documentation Resources for GDTF Introduction Start by registering a free account on the GDTF Share, this allows you to use the GDTF Fixture builder and also to join this GDTF Forum and ask questions. GDTF Builder GDTF files are created in the free to use GDTF Fixture builder - a web based editor to create and modify GDTF files. There are several documentation resources for the GDTF Builder: How to Create a GDTF Lighting Fixture YouTube video series from 2024. Introduction to the GDTF Builder YouTube video series. GDTF Builder manual describes creation of a GDTF file from start to the end. How to articles, describing dedicated topics in more detail, for example Wheels, Virtual channels or Prisms. Robe Knowledge Sharing (RKS) articles on the GDTF forum, describe particular domain knowledge to depth, for example basics on 3D positioning, orientation and rotations or 3D geometry preparations. GDTF Share The GDTF Share is a platform for the exchange of GDTF files. It provides a central repository, connected with a GDTF file editor, for upload, search and download of GDTF files, with powerful filtering and management system for users and GDTF files creators. GDTF Share manual - explains how to create a free account, how to navigate the GDTF Share and how to upload, manage and download GDTF files. How to Create an Account for the GDTF Builder and GDTF Share Tutorial YouTube video series. Other resources for the GDTF Specification The GDTF Specification is the text of the DIN SPEC 15800:2022-02 also known as GDTF Version 1.2. GDTF Spec documentation on this server. GDTF & MVR Specification working repository on GitHub GDTF Forum - ask questions about GDTF & MVR here FAQ - answers for questions frequently asked by manufacturers and entertainment professionals

One of the often raised questions about GDTF is "which data is required to be included inside GDTF files". This can be dependent on the use-case for the file and it is always subjective, but here we try to summarize the issue to provide a hierarchical approach to understanding user needs. GDTF Data expectation per use-case: Use case → Control Planning Previz Rendering Feature ↓ Fixture name essential essential essential essential Manufacturer essential essential essential essential RDM complementary Description complementary essential essential essential Product image complementary essential essential essential 2D thumbnail complementary essential complementary complementary Operating temperatures complementary Weight essential Leg height essential complementary complementary 3D model template essential essential essential essential 3D model real fixture complementary complementary complementary essential 3D model PBR workflow peripheral Beam model basic shape essential essential Beam model real world complementary complementary 2D model symbols complementary Gobo images essential complementary complementary essential Prism slots complementary complementary essential Color slots essential complementary essential Animation wheels complementary complementary essential Virtual channels (dimmers, tilt…) essential Channel dependencies complementary DMX (control) description essential essential essential DMX Macros complementary Beam data complementary complementary essential Colors (emitters, filters) complementary complementary essential Movement speeds complementary complementary essential Movement acceleration complementary complementary essential Movement ranges essential complementary complementary Movement directions essential complementary complementary DMX profiles (curves) complementary complementary complementary Subphysical properties peripheral Wiring object data (Power usage...) complementary GDTF Data expectation combined: Essential Nice to have Like to have Basic metadata Fixture name Manufacturer RDM Description Product image 2D thumbnail Operating temperatures Weight Symbols Leg height 3D model template 3D model real fixture 3D model PBR workflow Beam model basic shape Beam model real world 2D model symbols Media Gobo images Prism slots Color slots Animation wheels Control Virtual channels (dimmers, tilt…) Channel dependencies DMX (control) description DMX Macros Physical measurements Beam data Colors (emitters, filters) Movement speeds Movement acceleration Movement ranges Movement directions DMX profiles (curves) Subphysical properties Wiring object data (Power usage...)