GDTF Generation: Capabilities and Limitations
The GDTF (General Device Type Format) was created to become a universal language of communication between lighting manufacturers, visualizers, and control consoles.
Our service, AI DMX Fixture Creator, takes over the most routine part of the work: it uses neural networks to parse PDF manuals and automatically generates DMX profiles (patches), saving you from having to manually type in hundreds of channels and values.
However, the industry is still in the phase of adapting to GDTF. Due to differences in the architecture of console operating systems, the same file can behave differently. Below we have gathered the main nuances you might encounter when importing generated profiles into popular lighting consoles.
What does AI DMX Fixture Creator do?
Before loading the file into the console, it is important to understand exactly what data our artificial intelligence extracts:
✅ DMX Structure
Channel names, value ranges (Ranges), default values, and functions (strobe, dimmer, positioning).
✅ Basic Physics
Pan/Tilt rotation angles (if specified in the manual text).
❌ 3D Geometry and Gobos
The AI analyzes text and tables. It cannot extract an exact 3D model of the fixture for the visualizer or render bitmap gobo wheel images. The generated GDTF will use basic geometry.
Limitations when importing into popular systems
GrandMA3
MA3 consoles read GDTF natively, as MA Lighting was at the origins of the format.
What you might encounter: The platform is extremely demanding on the structure of the 3D tree (Geometry Tree). Since the AI generates a basic template, the fixture will be perfectly controlled from the encoders, but in the 3D visualizer window it might look schematic. If the fixture is complex (multi-cell), manual tweaking of the geometry in Fixture Share may be required.
GrandMA2
What you might encounter: MA2 does not support direct import of .gdtf. You will need to use third-party converters (for example, on the GDTF Share website). During conversion, the profile will lose all 3D information and complex kinematics, turning into a classic XML profile for MA2.
ETC Eos (versions 3.2.4 and higher)
What you might encounter: Eos perfectly pulls the basic DMX logic, but does not yet support the import of multi-cell fixtures from GDTF. If you generated a profile for an LED bar with pixel mapping, Eos will load it as one long list of parameters. In addition, 3D models for the Augment3d visualizer are not transferred - the console will replace them with a standard Source Four. Always check the profile in the built-in Fixture Editor.
Avolites Titan
What you might encounter: Avolites' strict logic (IPCGBES) sometimes conflicts with non-standard channel names. If a function was named non-standardly in a Chinese manual, the AI will transfer it "as is", and Titan might not understand which encoder to put it on (for example, macros or combined Color/Gobo channels). Also, mapping for the built-in Capture visualizer often breaks.
Chamsys MagicQ
What you might encounter: MagicQ is quite omnivorous, but often stumbles over dependent channels (Mode Channels). If the strobe channel changes its function depending on the macro channel, this logic will most likely have to be added manually in the Head Editor. The built-in MagicVis visualizer also often requires manual replacement of the 3D template.
Onyx (Obsidian)
What you might encounter: Onyx works with basic GDTF files, but its strong point - the DyLOS engine - requires perfect data on colors (Color Emitters). Since PDF manuals rarely contain exact spectral data of diodes, color rendering on generated fixtures in complex gradients may require calibration.
Recommendations for users
We created the AI DMX Fixture Creator to save you 90% of the time it usually takes to create the basis of a profile. But the remaining 10% is adaptation for a specific console.
Checklist after importing generation:
- Check the patch: Make sure the number of channels (Footprint) matches the manual.
- Check the mapping: Turn the encoders on the console. If a function ends up in the wrong tab (e.g., strobe got into the Position section) - correct it in the console editor.
- Add visuals: Assign gobo images and select a suitable 3D model from your console's built-in library.