Posts by JPK

    Hi,

    sorry but I cant find the English forum,

    you wrote in the right place :). We mixed up all english and german sub forum because we hope that this will increase the visibility of english posts.

    am finding that all the vertical blue value bars are full on at startup.

    Can you give us some screenshots of what you mean, because I could not find out which blue bars you mean (there are some in DMXC 2)

    Regards

    JP

    Hi,

    try it with this DDF. It is a first draft and not completed yet. But you can now control some basic functions of your device. Only the gobos and the color / gobo strobe channel (which I have to ask how to define it) are not functional. The rest should work fine.

    Regards

    JP

    Hi and a warm welcome in our comunity :),

    unfortunately there is no information about creating DDFs (device definition files) in our DMXControl tutorials. We have only a description of the DDF syntax in our german wiki ?( But I will help you and create the DDF for you. The only thing you have to do is to make good pictures of the gobos of your device (open color filter, as less distortion as possible, good contrast,...) and the order of that gobos. Those images are needed because DMXControl 3 use them for internal calculation in the hardware abstraction layer (H.A.L.) to choose the right gobo.

    Regards

    JP

    Hi, did you mark the Plugin in the PluginAdministrator? If not, go into the program folder of DMXControl 2. There is a tool called PluginAdministrator.exe. Run this program and mark all plugins in there. After that, DMXControl should start without any warnings and the Plugin for your interface should be startable.

    Regards

    JP

    Hi and a warm welcome to this forum,

    when you speak of a USB Interface cable do you mean the DMXKing ultraDMX Micro?. Unfortunately, we have no specialized output plugin for this Interface. But I read on their homepage that the API of this cable interface may be complaint with the ENTTEC USB Pro API. So you can try to link your cable interface with this output plugin.

    kind regards

    JP

    Edit: Oh, Stefan was a little bit faster ^^

    Hi,

    a few days ago, someone already asked this question in the German section of the forum. We took this question in our weekly meeting and asked our developers to explain how the relative functions works. Unfortunately they said that the relative function is still under construction and not working properly yet. However, this function was not intended to mix different Effects with it. It's an easy way to add e.g. a value of 10 to the position of differently rotated moving heads. So it supports you while configuring your light scene. For a good way to save positions etc. relatively in Cues, we need some more internal discussion. But to keep it in mind, I started a ticket in our bugtracker (FS#3137 : Relative Änderungen in Cue speicherbar machen (ticket is written in German)).

    Regards

    JP

    Hi,

    first of all we need some more information about your setup to give you the right hints to get your setup working. You're using DMXControl 3, right? Which DMX-Interface/Adapter do you have? What have you already configured (software settings, DMX-Interface etc.)? If we have those information, we then can do the next steps as following (as a little teaser for the next steps to do): At first you set up the communication from DMXControl to your lights. Then your lights will be set to the correct address. The third step is to generate fixture definitions for DMXControl so that the software know, how your lights are controlled. The last step will be the programming of cues for your light scenes.

    best regards

    JP

    Hi,

    I looked in the thread of your last post and I saw that it was listed in the german area. I moved it now to the english section. Can you see it now? If not, probably a change of the language in the filter settings (on the top right corner of the list box of a subforum).

    Regards

    JP

    Hi,

    you are right. In the current version of DMXControl 3 (3.1 series) there is only one beam per device. As a workaround you have to add a fixture in the software for every pixel of your device. Then you can assign effects on these pixel fixtures. For a better handling, you can also assign all pixels of a device to a device group. Then you have allready the correct order stored in the group and you can easiely program your chaser by assigning effects on the group.


    In future (3.2 or 3.3 series) you will be able to assugn multiple beams to one device. With this multibeam-devices you will be able to add your device with it's pixels as a single device.

    regards

    JP

    Hi and a warm welcome to this forum :),

    you have to select the specific cue by clicking on the area right in front of a cue row in the cuelist editor. Then, the whole row should be highlighted and then you can alter or delete the cue. In addition: Did you try to do a double click on a specific cue in the cuelist? If yes, just do a single click and afterwards do a right click on the cue entry. Now you should see a popup menu with different options like editing the cue in the programmer or delete the cue.

    best regards

    JP

    Hi,
    is your account a local administrator? If not, try to start DMXControl 2 with admin privileges. They are needed to register the plugins at program start (and deregister them at termination). Does this helps?
    Regards
    JP

    Hi,
    we will add the text book module in one of the future DMXControl 3 versions. But unfortunately, I cannot say which version this would be. There are some other parts of DMXControl, which have to be fixed first (Input Assignment, Softdesk,...). I realy need the text book too and therefor I use DMXControl 2 a lot in my productions.
    Regards
    JP

    Hi and welcome in our forum,
    this could be a bug in the output functions of DMXControl 3. With the Update from 3.0.2 to 3.1 the developers have changed the scale of those parameters (from 0 - 255 into 0 - 1). Maybe there is still a scalling issue in it. Can you please add a ticket in our ticket system (https://dmxc.org/bugs). Although the Bugtracker is in german, you can add english tickets. Just click on "neue Aufgabe anonym anlegen" and add the description. Please refer to this thread as well because of your attached ddfs.
    regards :)
    JP

    This configuration can be done in the interface settings. I don't know, how this works in QLC+ but there should be a configuration dialog for the interface. If not, you can use the configuration tool in the project achive of the nodle. With it, you can not configure every parameter, but there is a "fast" and a "save"-configuration (you find it under "parameter")

    Hi,
    this maybe comes from the absolute correct DMX signal of the nodle. Some DMX devices doesn't support that, because the manufacturer use cheap components. To solve this problem, you can change the dmx signal parameters in the nodle (thats the reason, why we add such a function). Just change the break time a little bit (about 5 - 10 digits) and try it again. If this doesn't help, do another change till you came to a change of about 50 or 60 digits. Then start to change the mark time too. Beware, the smaler the change is, the better is the refresh rate of the DMX signal. So it is important to do as few changes as posible.


    Regards
    JP