Jump to content

GDTF Forum

Search the Community

Showing results for tags 'rks'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • Announcements
    • Announcements & Newsletters
  • GDTF General
    • General
    • Frequently Asked Questions FAQ
    • Off Topic
  • GDTF Builder
    • Release Notes
    • Discussions
  • Technical Discussions
    • Technical Discussion GDTF
    • Technical Discussion MVR

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start



About Me

Found 4 results

  1. Before you define any physical attributes, you have to make sure to understand how positioning, rotation and orientation is defined in GDTF. 3D space definition GDTF defines this this way: The metric system consists of the Right-handed Cartesian Coordinates XYZ: X – from left (-X) to right (+X), Y – from the outside of the monitor (-Y) to the inside of the monitor (+Y), Z – from bottom (-Z) to top (+Z). For a device, everything starts for you with your 3D model. Here is GDTF definition: The device shall be drawn in a hanging position displaying the front view. That results in the pan axis is Z aligned, and the tilt axis is X aligned. 0,0,0 – center base plate. So this means: the device is upside down the origin point (0,0,0) is in the center of the base plate (meaning, not in the center of the base model, not at the "end" of legs) you draw the device with it's front in the direction of the -Y axis (facing you in the builder) by placing the "pigtail" model, you indicate the location of the panel with connectors or the power cord the positioning and orientation is how it must be done in the 3D model, especially for the base, because the top geometry (often the base) cannot contain any extra defined position (offsets) and/or rotations If you for example decide that the "front of your device" is where the connector panel is, this would be the result: Rotation Here is GDTF definition: The metric system consists of the Right-handed Cartesian Coordinates XYZ. Let me re-phrase this as this is basically the right handed rule: The right thumb points along the Z axis in the positive direction. Positive rotation is shown by fingers curled in the direction of rotation. When viewed from the top or Z axis the system is counter-clockwise. The top here is you, naturally looking at your hand: The counter-clockwise sounds strange, but because in real life you often "observe" it from the bottom, you consider this "normal" for screw threads and so on, because to screw them in, you turn them to the right. This is how it looks applied to the model/geometry, indicating pan/tilt: So when viewed from the top: Positive values are increasing values, so angles from 0° to 360°, from -360° to 0° of from -360° to 360° are positive, angles from 0° to -360°, from 360° to 0° or from 360° to -360° are negative. When defining angular ranges, you typically start from center (0°) and define - and + ranges. Based on this, you can determine how to correctly fill values for pan/tilt angular ranges, gobo rotations and so on. In the builder You can also use the Builder to show you the positioning (translate) and rotation (rotate), you can choose a mode to manipulate the model: Centered: Model: Displayed values: Moved "to the front", to negative values on Y axis: Model: Displayed values: Rotated "in positive (CCW)" direction: Model: Displayed values: Hope this helps Petr
  2. One of the advantages and ideas of GDTF is a central repository - GDTF Share, connected with a GDTF file editor - the GDTF Builder. Using the Share is pretty straight forward - you can upload, search and download files... but in reality there is much more going on behind the scenes. The Share contains powerful filtering and management system to ensure that this repository is kept nice and tidy, while at the same time any random person still can upload a GDTF creation of their own for others to use. Lets look at that... Searching and filtering Users can search the Share easily: Each file "belongs" to a "folder" of the vendor/manufacturer of the device and then a "subfolder" named by this "device name", with relevant filters: 1) filter for a manufacturer 2) filter for a device name File can be released to the public or can be in a Work in progress (WIP) release state. The WIP status is assigned to files by default and allows authors to keep working on their files and continuously saving their progress... plus their filters: Files are divided into being created by "users" and "manufacturers", the Share then contains respective filters: There are also various tags like "tested in 3D", tested in real world... and their respective filters: File upload To ensure that files are well organized, the upload process contains several steps to assign manufacturer and device. The Upload icon is up at the top: You can choose a file: And Proceed: Manufacturer is automatically detected, but you can also choose if if required: Same for the device name: At the end of these dialogs, you can review everything and can name the revision plus set the status (Released or Work in progress): Manufacturer moderation Manufacturers have special power that allows them to manage "their" folder 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: 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
  3. First steps of getting into GDTF... let's get right into it. Accounts Create and account in https://gdtf-share.com/ so you can access the Share, Builder and the Forum. Sign into the forum at least once, so your account is activated here. If you are an industry related vendor (for example a manufacturer) drop an email to info@gdtf-share.com , together with brief introduction about who you represent and your Share username. This will provide you with the possibility to enable manufacturer account in the Share and invite to the monthly GDTF manufacturer's interfacing meeting and discussion. If you are after the formal GDTF Specification, get the DIN SPEC 15800:2020-07 . As this is an official DIN document, distribution is possible only through the DIN publishing body, Beuth in this case. https://www.beuth.de/en/technical-rule/din-spec-15800/324748671 GDTF Authoring To create the GDTF files, best way is to use the Builder. There is a quick manual here, so make sure to check it out. But there is nothing like just doing it, over an over again. As with any tool, it is very simple to make a simple basic file, but it takes time to learn the tiny details. Get some inspiration from existing files, the Share offers a lot, we at Robe have also been creating files for all new (and even older) fixtures, so this can serve as a lot of inspiration. Here are few examples to get you started: Very simple tungsten device even without dimmer (but the file provides a single channel control for visualizing purposes), Patt 2013. A typical discharge spot , a moving head fixture, the BMFL, with gobos, prisms, iris... using Mode Dependencies and other features required for a moving head device. A multipixel but single RGBW controlled small LED beam, the LEDBeam 150. For a linear LED unit, check out the VC-Strip 25 8x1. Going up with complexity, a multiring LED wash fixture, the LEDWash 800. For a fixture with many DMX modes and Mode Dependencies, look at the Orbiter. If you need an example of quite complex pixel controlled LED fixture, Tarrantula can be an example. This is also showcasing custom 3D model for the beam pixel lens. Start with visualizing right away Several manufacturers are working on their GDTF implementation. Check out what they are offering and maybe ask for support if not announced yet. You can also use GDTF files right away with either MA3 or VW Vision and although there is always room to implement more niche details, most features needed for the real day to day operation already work very well. Start with a basic device and see what it looks in the visualizer. This allows you to work without a physical fixture and you can explore and test even complex depths of GDTF possibilities. DMX controlling versus general device description For basic DMX controlling, very simple GDTF file is all that is needed, so i would suggest to start with that, but GDTF offers much more, from the 3D models through connectors to real world physical parameters. For that, you will need real measurements of real devices, but again, you can try any values for the start, to get a feel how to enter them into the builder and what the visualizing looks like. Consuming GDTF data If you are more into utilizing and using the GDTF data, definitively check out the DIN Spec as per above. Also, look at the GDTF XSD file and PR for a Schematron validation file (kindly provided by @Janng ). There is also the libMVRgdtf parsing library (ask for access through the info@gdtf-share.com email as per above), or if you like to use GDTF fixtures in a 3D game engine, you might also like to check out the Unreal Engine GDTF implementation, described for example here. As the GDTF format is completely open and there are already some well performing devices files in the Share, is it simple to start with implementation and do some experiments of what the GDTF can provide you with. Hope this helps Petr
  • 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.