Hello,you can copy the geometry tree and use the copy in the other mode(s). You assign the different tree in the DMX Mode properties:

Hello, thank you for the request, i have noted it into the list of items to consider in the future.

Hello @Lennarthd1, you have done mostly good job on the profile. The issue is in colors (RGB) being set as default at 0, so make sure to bring colors to full, as @full will not do so. The next issue is in the Iris channel, the Physical From, To must be 0 to 1. There are other small things, but mainly that your 3D models are too detailed, perform some decimation on them, to be under the 1200vertices in total.

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

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

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.

@lohint click the three dots menu and select Delete:

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.

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, make sure to enable your Manufacturer page in the GDTF Share in the Edit Profile of your account. This page is useful for manufacturers providing GDTF files, as well as for software vendors who utilize GDTF and MVR in their software. Customize the page with your company logo and header image, we can then use this image for listing on the GDTF Share page. The header image of 4096px x 768px should be a good size to fit most situations. You can add posts, describing your product and the support for GDTF/MVR it provides. The page also provides listing of your GDTF files which you can share with your customers, see this example page. 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...)

Hi @Andriy K, thank you, sounds good. We have done a lot of work in the past to accommodate this. The GDTF spec got support for multiple geometry trees, we sped-up the multi-geometry tree rendering in the GDTF Builder, and i believe software using GDTF also improved over time. For us, things are a bit more complex but for you this should make your experience much better.

If you have the opportunity, please visit the GDTF booth at the Plasa 2024 show, at stand A69.

Hello Andriy, yes, we deal with the same issue. If i can advice you, duplicate the geometry tree and make the modes to use Break 1. We have quite a few devices where using multiple geometry trees is complicating things for us for several other reasons, so we stick to a single tree but have to deal with these DMX Break implementation issues. On gMA, you can patch but you must re-calculate yourself, because the software pushes the other breaks to another universe. You can also raise an issue with WV and MA. Cheers Petr

I have looked at the file in the builder. This is a good start, but you do need to tweak it to make visualization working: - Ideally, you should build the fixture up side down, as the GDTF specification says. This will in default view allow you to see the beams pointing down from the device. The up side down rotation of the models should ideally be done in an external 3D software. - the model of axis has it's origin point (the center or the pivot) outside of the model, this is why the rotation is not following the real fixture behavior. To fix this, in the 3D software where you created this model, you need to set the origin point to the correct place. - the beam geometries are inserted too deep into the geometry of the "axis", thus they cannot shine their beams out. Hope this helps

A random strobe has a random behavior. Having said that, it might be possible to link a global strobe attribute to a geometry parenting the sub-beams, then the trickle-down principle would make them to strobe together, in random way but together, if the used visualizer supports that.

Hello, this is not an oversight but it was a deliberate change from original version of GDTF. Each ChannelFunction has it's own default value as the LogicalChannel's default value is in many cases not valid for all ChannelFunctions. Also, when switching between ChannelFunctions, it was important to be able to tell to the system what value to load upon the change of the function. Kind regards Petr

Hello @CharlieWinter, repackaging and re-zipping GDTF and MVR is possible. It could be that gMA3 is not yet supporting compression of the zip archives and that they are expecting a zip but without compression, which is something you can typically set during the zipping process. Hope this helps Petr

Hello, you can make the beam large (like a tube) and set the Beam geometry's Beam Type to None or to Glow: See here: https://gdtf-share.com/share.php?page=home&manu=User+Test&fix=RGB+Tube I didn't test in gMA3 but i presume that it would work, Hope this helps, cheers Petr

If the effect uses 2 channels (16bit) and you want to enter the data in 8bit fashion (0-255 values), you somehow have to define the value for the second channel. In the input field, the first value (from the left) is what you most likely have in your DMX table, the second value (after the slash "/"), is most typically will be 0 for you, except for 255, which will be 255/255 (to have full maximum value). Hope this helps. Maybe discuss this with your R&D people, to have more clarity if needed... they will be able to help you too. cheers Petr

Hello @CarlosDVS, switching the input field between 8/16/24/32/% is just a view on how you enter the data. So by switching it to 8, you can enter your data in the 8bit, as per your DMX table... see for example here: When switching between these values, you can see what you values look like in different resolutions or a percentage: