Output Plugin for DMXC 2.10.2

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!


  • Hi,

    Can anyone help me?

    I developed my own PIC Microchip based Output Interface last year, which has been running fine until I decided to upgraded to DMXC 2.10.2, I was running DMXC 2.9.

    My output plugin is based on the Delphi example :- RGB_Led_Modul.

    My Interface commands namely:- Enables, Disables, Get_PluginName, Init and Term all work (I don't use Configure) but...

    procedure TOutputPlugin.SetChannel(Channel, Value: Integer);

    does not work any more... if I roll my installation back to DMXC 2.9 everything works as it should.

    Can anyone please give me more information on what has changed with regard to SetChannel ( I am aware of the channel count is now 1024 ), as I really want to give DMXC 2.10.2 a try?

    Any help will be highly appreciated.

    Kind Regards and thanks in advance
    Paul

  • Hi Guys,

    Can anyone please help me out?

    I still can't figure out why DMXC2.9 works fine with my interface and DMXC2.10.2 does not send channel data?

    Thanks in advance
    Paul

  • Hi!

    I think Stefan as our main programmer on the 2.x-Line changed something. Another interface shows problems as well (DMX4ALL).
    Sorry, you have to wait until he manages to pay attention on that topic.

    Hoc
    (also awaiting the dmx4all-update... :D)

    Mein Equipment:
    1x Hirn | 2x Augen (leicht defekt) |2x Ohren | 1x Mund |32x Zahn (zum Teil V1.5) | 1x Handundfuß-Interface
    *SCNR*

    Edited once, last by Hoc (April 30, 2009 at 1:05 PM).

  • Hi Hoc,

    Thank you for the update, I will wait... :O....in the mean time I will continue using DMXC2.9.

    Regards
    Paul

  • Hi Hoc,

    I found a solution and maybe it can assist with your problem, I tried increasing my DMXBuffer Array declaration from 512 to 1024 and my hardware is now working.... :D

    This is what I used to have in my DMXC output.dll...

    DMXBuffer: Array[ 0..512 ] Of Byte;

    I changed it to this and it now works...

    DMXBuffer: Array[ 0..1024 ] Of Byte;

    Maybe adjust the similar setting in the DMX4All.output.dll and give it a try...You see I load this array in the following way....

    procedure TOutputPlugin.SetChannel(Channel, Value: Integer);
    begin
    DMXBuffer[Channel] := value;
    end;

    ...as I run a thread in my output.dll that clocks out the channels via USB to my hardware...this gives me an idea to implement 2 universes..hmmmm.... :rolleyes:

    Hope this helps....Thanks anyway...

    Regards
    Paul...

  • Just before I saw your latest post I was digging through the SVN log since 2.9, but that could only confirm what I thought: There were only a few very minor changes and none of them had anything to do with SetChannel...

    I think your problem is now clear:
    For the "SetChannel"-call the internal VB error handling is setup to silently ignore errors (to not flood the user with error messages).
    When DMXC tried to set a channel >512 (which will happen through plugin initialization even if you do not use channels that high) your code would raise some kind of "out of bounds" exception because it tries to write to an invalid array location.
    The proper fix to your problem is to check wether the channel is below your array bounds and only then set the value, else ignore the setchannel request:

    if (Channel <= 512) {
    DMXBuffer[Channel] = value;
    }

    Your solution to increase the array size works for now, but it will fail again when DMXC oneday maybe supports >1024 channels...

    Stefan

  • Hi Stefan,

    I implemented your suggestion and all is fine. Working perfectly... :D

    Thanks for an awesome program.

    Regards
    Paul

  • 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.