Jump to content

GDTF Forum

All Activity

This stream auto-updates

  1. Today
  2. Saying you used 'default' visualizations...then. Well...again, I would have to venture a guess that it is the end user platform[Visualizer--VW--you don't diagram your control config] not correctly reading how the file is structured....and it then becomes a question to those parties...Vectorworks, Vision, etc... I am working under this axiom: This site and the share site are being produced and maintained by those parties involved with pioneering the formats and thus; if things are visualizing here and not in the end of your workflow chain...well, the problems are lying somewher
  3. I used the basic fixture models. Would this cause this?
  4. Yesterday
  5. When you constructed the fixture in the webBuilder...and when you Imported your 3DS files[if custom], did you see the model rendering in the builder? Did you use default fixture models? I'm gonna speculate that it's Vision and/or VW reading the MVR file incorrectly. The web builder references the 3DS files and packs them up in the MVR/suitcase/container, so, if you extract or unpack the MVR file you'll find the 3DS in a nested folder...seemingly just fine. I think Vision and/or VW is not finding the nested asset...within the MVR structure. Just my guess, though....since it is n
  6. Last week
  7. Hey everyone,I recently built some GDTF fixtures and imported them into Vectorworks. Then I assigned the GDTF fixture mode to the correct fixture. However, when I import then file into Vision using MVR, I only see the beams and not any of the actual fixture. I could control most of the fixtures features but the position was wrong. All of the fixtures I made are by Vello Lighting and this was my first time creating fixtures in GDTF. What error could I have made in my process?
  8. Earlier
  9. Hi Petr, Just sent you an email with the file. Thanks, Patrick
  10. We have tested and all seems ok from this side of the world. Is the file still giving you issues @ARRI-GDTF? If yes, any chance to post it? Thank you
  11. Hi @ARRI-GDTF previously, it could be due to size (the break off was around 5MB) but that limit was removed. I Just tested with about 5MB file (4,775,196 bytes) and all went smooth. But our guys have reported some hiccups yesterday too, from what i know, server configuration was being updated slightly, so this could have been it. Please try now, but from what i can see, it should be all OK.
  12. Is there a maximum size for the GDTF file? I am working on a complex fixture with more than 72 different mode configurations. Have a couple more modes to enter, which are basically copy/paste with some channels removed. Keep receiving ""Upload failed, try again later" message. Was thinking it might be a server issue, but problem persists today. File size is just over 3MB.
  13. My solution: model and export in MM....only thing I've gotten to work in the Builder to compensate for this.
  14. I made similar experience with my own 3ds exporter - the 3ds format does not store any scaling units, only factors. The Masterscale chunk is for defining the units, but the conversation to the builder is always meters to millimeters. I have the same issues the other way around - if I export a 3ds from vectorworks, my importer scales it up by factor 1000
  15. Hello @chris@stagelitedesigns.com, it is up to every manufacturer to do this work and some are already working on it. Do not forget that MA2 profiles dealt pretty much only with DMX. GDTF is solving much broader scope - DMX and channel dependencies, media (gobos and animations), prisms, 3D models, physical data (angles, color and spectral data) and also physical speed data (rotations, time of movement, acceleration). This means much more work and it does not happen overnight, but i would suggest that you contact the manufacturer of your lighting fixtures and ask for GDTF files, becau
  16. Yes, the very intention of GDTF is that the format itself is open and free to implement and use, the builder is free to use and intentionally it encourages you to upload the file publicly online, as the whole intention of GDTF has been to fix the issue of proprietary vendor lock in formats. It still allows design studios to design custom stuff for clients either via Builder and delete, or via custom software implementations, which are very simple, given the open and also readable nature of the whole specification. We do not do any dark pattern stuff on the server or in transit to keep or look
  17. David -- Thanks for the clarification. I thought I must be missing something. For the time being, I'll use the "upload then delete" strategy. All I'm trying to do is make lots of edits to fixture definitions I'm testing before releasing them to the wild.
  18. Currently, uploading is the only way to generate a copy of the GDTF file, it dupes the file, one for public Sharing...one for your 'desktop' or other location of storage. Upload to generate the file, then go to public Share site and delete your upload...heavy handed but the only way at the moment to get a 'hardcopy' of your work in the proper format. Good luck! NB: deleting in this manner 'should' keep your work somewhat proprietary and under your control. Once it's at 'Share', for any period of time...it's exposed to the General Public on the interWeb. Anyone can tak
  19. I'm new to the GDTF builder. I would like to experiment with creating and/or modifying existing fixtures and download my work in progress to test on my console. It appears that there's no way to do this -- you seem to be required to upload any changes made to GDTF-Share before you can download the resulting .gdtf file. Or am I missing something? I would prefer to be able to use the editor, download a draft version of the GDTF, test it, and make additional changes before uploading/sharing the final version. Is there any way to do this?
  20. Hello, Has anyone heard when we will get the addition of some manufacture made profiles for entire lines of fixtures uploaded? It seems like the GMA3 software is waiting for this? There are the MA2 fixtures you can use but they are not accurate in the new software. Hope that makes sense......
  21. Hello @walter.lutzu, thank you for the report. I believe this was already addressed, but am not sure if that version has been released yet (this is more for the VW forum), but let me add @klinzey of VectorWorks here in copy (thank you Kevin!), cheers Petr
  22. Hello everybody! I've a strange problem: fixture in a place and beam in another... Exported mvr from vw with gdtf mode. I tried with different fixtures. This happens only with last Vision release (25.0.4.549680). With previous release all works well.
  23. The GDTF Builder 1.3.12 is now online. Improved in this release: Fixed: it was not possible to enter values for the property Beam Diameter of geometry type “Beam”. Fixed: DMX values were not properly recalculated when copying a channel function to another DMX channel that had another resolution. Fixed: it was not possible to reorder mode master containers by drag ‘n’ drop. Fixed: parsing errors in the fixture template „Moving Mirror”. Improved stability.
  24. Hi all, we have released a big update of the GDTF Builder, which includes several months of work on improvements, bugfixes and features. Our main focus has been on enhancing the user experience of the editing workflow and on eliminating bugs. To help to reduce crashes and issues, we have now deployed Sentry.io, application monitoring platform, to help us to reproduce bugs and fix issues faster. This is the reason why we have re-enabled the consent with Terms of use screen, on first signing in. The list of changes is very long and includes more then 100 items, let me describe few of t
  25. Dear @Paolo.Prolights, this looks like good work, few changes here and there, mostly nit-picking: - RDM missing, but might not be included - you use "Parent physical" in most places, which is mostly fine, except Wheels, where you should use ChannelSet PhysicalFrom/PhysicalTo values, to indicate whether the these are proportional or step values - the models is slightly bigger then needed (vertex wise) but i would not change it - if i understand it right, the Strobing could all be within one ChannelFunction, with ChannelSets defining the Slow/Medium/Fast DMX + PhysicalFr
  26. Hi @tk11de, on the beginning of this week, we have rolled out a big maintenance update to the builder, which (besides a bunch of good new features) includes several fixes against data loss. Kind Regards Petr
  27. Dear all, it is great to see all the interest in GDTF specification, GDTF Builder and also the GDTF Share. As the Share is a source of data for several different interested parties with different levels of needs and understanding, we have to ensure that the content provided in the Share remains organized and useful. The GDTF Share usage policy is given by Terms of use, available here: https://gdtf-share.com/help/terms_of_use_gdtf_help.htm This short document explains principles used for moderation of the content in the GDTF Share which we will start to be enforcing, to keep the GDTF
  28. >I built it initially in grandMA3 v1.1.4.2, and then exported it as gdtf to tweak in the builder.  Thank you for the report. I think @dmuellerwill be interested in this. I will also report to the Builder team.
  1. Load more activity
×
×
  • 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.