DMX (on the web as BlenderDMX) is an entertainment and architectural DMX lighting visualization and rendering tool designed to offer a free, easy, and fully packed solution for Lighting Designers.
Device definition is based on GDTF Specification, utilizing the Fixture library on GDTF Share, with support for static and moving devices, LED bars, lasers, cameras and more.
FAQ, Getting Started Guide and full User Guide are available.
Have questions? Check out the FAQ or ask in the Discord group.
IO operations for GDTF import and MVR Import/Export are fully integrated into Blender, providing smooth native experience with Drag-and-Drop and Operator Presets.
Related fixture data (GDTF files) can be Exported and Imported as a Project data zip file.
The source code is completely open source under the GPLv3 license and openly available on GitHub. Feel free to inspect, share, and contribute!
DMX for Blender is using General Device Type Format (GDTF) and My Virtual Rig (MVR) - open-source file formats that let you share anything with anyone.
For full details, read the blog post here.
This release contains support for new attributes (Gobo2, Iris, CTC, CTO, CTB, PanRotate, TiltRotate) and more. The Shader three had to be completely re-organized and gobo loading needed to be refactored. There is a migration procedure in place, but very likely, older .blender files will not project gobos correctly. Re-editing fixtures might be needed. It is also possible that previously recorded keyframe animations will not work right away and will need re-adjustments. Sorry for the inconvenience. Read more details in the blog post here.
Complex fixtures can now be controlled via the new Subfixtures menu, allowing precise selection of fixtures' geometries and controlling of only attributes attached to these geometries.
Changelog:
This extension requests the following permissions:
Import GDTF devices. Import/Export MVR scenes and project data
For GDTF Share, sACN, Art-Net, OSC, PSN, MVR-xchange
Thanks for the submission. Pretty impressive. I can't fully test the add-on, I'm not familiar with this workflow, but some general notes:
@nickberckley , thank you for the review, i changed the link.
Links: i now set Discord invite as the Report issues link. As for github issues, these are intended as developer related, not for user support, which tends to happen... the community at discord can help them much faster :)
As for the terminal messages: this is intentional at this point. It is showing what changes have been done to .blender files saved in older versions of the Extension. As i do not presume regular users to look at the terminal at all, they should not be troubling them, unless they have an issue, when they do have a look. Then there is a logging level, set to Error by default, so after this migration step, the user is fully in control what to log and display into terminal.
Thanks
There has been an update to the terms of service, where we added a "Branding" section to improve the presentation of extensions. Please check it out! https://extensions.blender.org/terms-of-service/
Hello, thank you. Do you have any suggestion on how we should proceed? Our extension is named BlenderDMX and before investing the time into porting it to 4.2's extension system, i explicitly checked that naming and not mentioning Blender is not required. For documentation we also run BlenderDMX.eu site. Calling it just DMX is problematic, as that name is too generic. Rebranding/renaming after four years is also problematic and will cause loss of the community. I am not sure what i should do...
Thanks for the kind reply. While the guidelines for branding Blender-related products are available at https://www.blender.org/about/logo/, they should have been made more prominent on this website from the beginning. Apologies for that.
I see that your product/brand has been around for a few years already, and understand the impact this request has. My advice would be to call it "DMXControl", "DMXDesigner" or similar. By choosing such name, you can couple it with a "for Blender" tag line. For example "DMXDesigner for Blender", or "DMXDesigner, add-on for Blender".
With Blender growing in popularity, the amount of projects using "Blender" as a prefix for their name is growing and that often generates confusion on how official they are. For this reason I'm reaching out to most of them suggesting a rename. I'll work on a blogpost on blender.org to share this information more widely, and present it as a positive message for the community of Blender extensions and content creators.
To be clear: the goal is to push brand diversity in the Blender ecosystem, and not to shut down functional, well maintained and well presented projects like yours.
Let me know if you have any question - or feel free to write me at francesco at blender.org
Hi, The system flagged the extension as carrying wheels which are not officially present on Pypi. Could you please explain how you are creating these?
I understand that there is an overlap between "DMX for Blender" team and some of the Python libraries. I wonder why the versions used are not yet on Pypi though.
This is because i develop both the python-gdtf, python-mvr, python-psn and recently special wheel was created for the io_scene_3ds by the developer of the library, this was just for us, to make distribution easier, rather then vendoring. For example for python-mvr, i am not planning to release a new wheel to pypi yet, as i want to see the feedback and fix eventual issues.
I see the wheel distribution much better then vendoring, due to the need to make modification to all files in the vendored libraries to ensure correct imports, so if you rely on the wheels to always exist in pypi, this can be problematic.
Sign in to comment.
Ready for review