Is the source code going to be available? At least for the device libraries? Even documenting the library interfaces, so that one might be able to use them directly?
Source Code?
-
RobCashwalker -
September 1, 2004 at 5:44 PM -
Thread is Resolved
We proudly present: The release of DMXControl 3.3.3!
On September 29, 2026, we held our release show for DMXControl 3.3.3. During our usual “hour-long” session, we showed you all the new features in this version and what it now has to offer.
Read all about it in the corresponding news article: We proudly present: The release of DMXControl 3.3.3!
-
-
In the documentations section there is a tutorial how to create your own device files using XML...
Or do you want to write PlugIns for DMXC? If it's that, your not alone...
At the moment we discuss useful interfaces in DMXC to communicate with custom plugins.Stay tuned! In few weeks you will know more

BTW: DMXC is FREE software not OPEN software.
-
Quote
In the documentations section there is a tutorial how to create your own device files using XML...
While I was wondering if anyone has made some more generic profiles for basic lights instead of all these moving lights, this isn't what I was looking for. I should have been more precise.
Quote
Or do you want to write PlugIns for DMXC? If it's that, your not alone...
At the moment we discuss useful interfaces in DMXC to communicate with custom plugins.Stay tuned! In few weeks you will know more

I think so.... I mean the DMX Transmitters. For example, the Manolator is an extension of the Kristof Nys project - 256 channels. I'd like to make a library for it. Looking at the device libraries, I can see that they provide universally compatible interfaces to DMX Control. To make my own, I'd need to have a clear definition/description of what inputs/outputs are expected for each. Besides, what's up with Kristof's transmitter isn't 'checked' on the transmitter page?
Quote
BTW: DMXC is FREE software not OPEN software.True, but some of the transmitter projects are. And I believe the GPL requirs that any 'derivative work' must be GPL too. Which only goes as far as the DLL. If it were hardcoded in the EXE like freestyler (I think) then it would include DMXControl. It wasn't entirely clear what licensing scheme is intended for DMX Control. Its free that's all that really matters. But the DLLs should remain open.
-
I thought that part of the GPL license means:
Sources which are based on sources under the GPL license must be plublished again under the GPL license.DMXC doesn't use any GPL code in it's core, so Stefan can't be forced to publish the source

For the transmitters you rely on there is no dll-source but the protocoll as a text. So the just the schematic, the layout and the firmware is GPL...
On the other hand I think a tutorial or a "dll frame" would be more useful as the raw code ::) ...We'll discuss it!
BTW: I might be wrong, but I think there is a working dll for the Manolator already written... On Sunday I will know more.
PS: basic lights are controlled with the "generic dimmer". If there was any use for more profiles, they would be already made?!?
-
Hi!
> On the other hand I think a tutorial or a "dll frame" would be more useful as the raw code ...We'll discuss it!
The "framework" for output-plugins is already available.
We decided to distribute it by mail rather then a download from the homepage, so we know who has the framework. This way we can easily spread updates to the interface specification.
If you want to have the framework, please write a short mail to info@dmxcontrol.de
> BTW: I might be wrong, but I think there is a working dll for the Manolator already written... On Sunday I will know more.
Yes, support for the Manolator is already incuded in the Kristof Nys-DLL.Stefan
-
Souko
April 9, 2018 at 8:29 PM Moved the thread from forum Technical issues [v2] to forum Help and Support [v2]. -
Newly created posts will remain inaccessible for others until approved by a moderator. The last reply was more than 365 days ago, this thread is most likely obsolete. It is recommended to create a new thread instead.