Back in the late 1980’s and early 1990’s, the digital era of the lighting industry had yet to define a standard for unifying data exchange between fixtures. Every manufacturer had its own proprietary control language and controller for programming their own fixtures. What that meant for shows back then was a different controller for each type of manufacturer was needed if mixed together in a rig.
This caught the attention of some industry professionals, and at USITT in 1986-1990, DMX512 was conceived and refined. Manufacturers didn’t begin to catch on to the need for a single common control language at first, and continued to push towards having their own controllers. Eventually, however, consoles like the Wholehog 1 came on the scene and programmers began to demand a single control surface for all types of fixtures. Manufacturers of lighting fixtures began to listen, and slowly abandoned their proprietary languages in favor of using DMX as the primary control language. Today, of course, DMX512 is the industry standard, and newer protocols like sACN are becoming options as well.
There are still opportunities for forward-thinking companies to collaborate and make the lives of their end-users easier, however. Two recent game-changing initiatives to arrive on the scene are the General Device Type Format (GDTF) and My Virtual Rig (MVR). Jointly developed by MA Lighting, Robe and Vectorworks, this new data exchange platform between lighting consoles, fixtures, and previz applications greatly improves the design to programming workflow.
I had the opportunity to attend the GDTF session at the 2018 Vectorworks Design Summit, and later I spent some time with developers from MA Lighting for some additional information. And now, with the announcement in March 2019 of the availability of GDTF 1.0 and MVR, I’m certain that what we’re seeing is the beginning of a powerful new way of communication between devices. Let’s take a closer look at this exciting new data exchange platform.
What is GDTF?
Before discussing the specifics, let me give you an example of why GDTF and MVR are powerful. As a lighting designer and programmer, I’m often in the seat of creating the lighting plot, the patch, the lighting paperwork, and the previz model. If you’ve been in those seats on a project, you likely know that there are constant updates to information across all platforms that have to be coordinated in each location. In the early days of lighting design and programming, that could mean updating the plot in one program, then opening the console and typing in the changes, then opening the paperwork files and updating the changes, then opening the previz model and making the changes, again and again until the rig is patched and all changes are complete. Very time consuming! Granted, consoles like the grandMA have come a long way from those days by being able to receive patch information from applications like Vectorworks via an XML file, and Vectorworks has certainly taken steps to allow for importing and exporting fixture data between apps like Lightwright. But these necessary steps have remained disconnected for the most part, and the workflow doesn’t readily flow between programs. Enter GDTF and MVR.
GDTF 1.0 and the My Virtual Rig (MVR) file format are used to create a two-way connection between planning, previz, and console systems. These file types are now fully implemented into Vectorworks 2019, Vision 2019, and grandMA3. And the GDTF file format is currently supported by 20 other manufacturers including Robe, ETC, Martin, AVOLITES, SGM, and Green Hippo, to name a few.
The Power of GDTF and MVR
GDTF is an open source, unified data exchange format stored in an XML file that contains valuable fixture information including:
- Fixture name
- Short fixture name
- Manufacturer
- Fixture description
- 3D model geometry (3DS)
- DMX mapping
- DMX modes- channels and channels functions
- Wheels
- Physical descriptions of emitters, filters, and color of the light
- Attribute groupings
- Date and user stamp on all uploaded GDTF files
The ideal situation is that each manufacturer of any type of lighting fixture will create its own approved GDTF files for each fixture and make them available on their websites; these files can then be imported into any application that supports GDTF (such as Vectorworks). The value to manufacturers in creating GDTF files is in retaining ownership of writing the fixture file and its details, rather than a third-party developer. This lends assurance that all the subtleties of a fixture are included in the file for seamless accessibility in connected applications.
The fixture builder on GDTF-share.com.
On the GDTF-share.com website, a web-based fixture builder is available for manufacturers to build their approved GDTF files. The files are then added to searchable online database for anyone to access. The web-based builder isn’t restricted to just manufacturers. Users can build and create GDTF files too.
MVR is an XML file that provides a complete 3D model with data describing the different fixtures’ locations in the scene and contains all the GDTF files for the lighting fixtures used in a design. When exported from Vectorworks, it can then be imported into any previz program that supports MVR, such as Vision, or a lighting console like grandMA3. MVR files contain geometry for objects in the scene including:
- Fixture
- Focus point
- Truss
- Video screen
- Other scene objects
So by using GDTF and MVR, the more efficient GDTF/MVR workflow looks like this:
- Designer draws the lighting plot in Vectorworks;
- Designer selects a Fixture Mode from the manufacturer approved GDTF for each fixture in the plot;
- Designer exports the file as an MVR;
- Designer (or programmer) imports the MVR into the Lighting Console, previz system, etc.
With the collaboration between Vectorworks, Robe and MA Lighting, a new unified data exchange platform is taking shape in our industry. The advantages of moving toward incorporating this type of format enables us, as end users, to achieve a more efficient workflow. And in this business, we all know that time is money, so we are always scanning the horizon for ways to make our workflows and processes simpler and more efficient. And the lesson we’ve learned since those early days of DMX… if end users ask for these types of tools often enough, manufacturers will eventually embrace them. When that happens, the industry as a whole improves. So, the time is now to reach out to your favorite lighting manufacturers and start asking them to support GDTF… we’ll all be glad you did!
