Posts by JPK

Because DMXControl Projects e.V. will be affected by article 13 of the new copyright act of the EU, we participated in actions for the #SaveYourInternet movement. Therefore, all of our websites were offline at March 21, 2019 for 24 hours. See Directive on Copyright in the Digital Single Market

    Hi,

    well yes, there is no support for a DMXControl 2-like custom control panel anymore. But there is a reason for that. We have unified the access to device properties in the device control on the right side of DMXControl 3. Just select the fixture in the Stage View and the device properties will pop up in the device control. There is now also an inbuilt support for RGBx-Colors (e.g. RGBWAUV, lime, indigo etc.). So you now only specify the color-channel in the DDF and if needed the position in the color circle. DMXControl 3 then adds the color entry in the device control and a possibility to control the specified color. Slider and dropdowns are also supported in the device control. But they are now automatically generated according to the specified device properties. For example DMXControl 3 adds a slider for the amber property by clicking on the amber entry in the device control and the arrow on the right side of this entry. An example for dropdowns is attached. Just add a "rawstep" block in the DDF.


    You are right, there is very few documentation especially in english. But we have now for a few months a DDF documentation in our german Wiki https://wiki-de.dmxcontrol-pro…index.php?title=DDF_DMXC3 It is not translated yet, but maybe it is helpful for you anyway to determine, how to specify the device properties in the DDF. And if you have any questions about that, just ask here in the thread / forum :)

    regards

    JP


    Edit: The DDF for the Eurolite PS-4 HCL should be in a way similar to the DMXC3 DDF of the ADJ HexPar 5P RGBWAUV (12CH Mode). If you attach the manual / DMX address table then I can create a DDF for you. The other way would be you create the DDF and attach it here with the address table and I will review it for you :)

    In this thread you can post your questions about DMXControl 3, which we will address in the livestream on 2019/03/09 at 8pm. We will sort them and try to address as many of them as possible. However, depending on the number of questions, we cannot guarantee that we will be able to answer all of them. The basis is DMXControl 3.1.3.


    Questions can be of the following types:

    • General questions about operation
    • Questions about functions of DMXControl 3
    • Questions on how to proceed in DMXControl 3 in certain cases
    • Questions about specific tags in DDFs or in the DDF creation process
    • Questions about handling interfaces (general)

    Questions that are not answered because they are not the target of this livestream:

    • "When does DMXControl X or Program X be available?";
    • "When does function X be available in DMXControl 3?";
    • Questions about a specific DMX interface
    • Questions about specific DDFs
    • Questions about DMXControl 2

    Hi,

    as far as I understand, you want to be flexible to mix some intensity + position cues in one cuelist with colors and gobos assigned on different executors, right? I ask this because for proper functionality, every executor in DMXControl 3 needs to be linked to a cuelist. Therefor you have to create a new cuelist for every property selection. Let me explain it with a little example: We want to select between some different gobos on some moving lights via executors. Lets say we have five different gobo scenes we want to choose of. We then create five cuelists and give them individual names. We then set up the cues. Every gobo scene is saved to one cue in one of the five cuelists. Afterwards we assign all five cuelists (one cue long each) to five executors. Now we can start those five gobo scenes by press play on one of the five executors. But we have to do one other thing. We have to stop the cuelists too. Therefor we create a cuelist group and assign all five cuelists to this group. There is an option in the settings of the cuelist group called "Cuelist start behavior". Here you select the "Single list running" entry. From now on only one cuelist of those five cuelists can run at the same time. If you start another one, the current cuelist running will be stopped automatically. You can now do this procedure for every device property / set of device properties you want to control via executors. There are also optional things to set up: Cues have usually a fade time and the cuelists a release time other than zero. For color scenes started with executors this is a good thing. But with gobos or devices with color wheels you maybe want to switch the cuelists without any fade. So you have to set both mentioned values to zero.

    Regards

    JP

    P.S.: I hope my post is understandable :S

    Hi,

    at first let's start with the DDFs folder. In your Windows start menu there should be a folder for DMXControl 3. If you open it, there should be a link to the custom DDF folder (I hope, this link is translated into english, otherwise the links name is the german "Eigene DDFs" (Own DDFs)). If you follow the link, you enter a folder, were you can place all your custom DDFs. I searched in our Device Library https://ddf.dmxcontrol.de/devices;search=chauvet but could not find any suitable DDF. So you have to write your own one for this fixture. Unfortunately our DDFCreator is not up to date and we haven't translate our DDF structure definition (https://wiki-de.dmxcontrol-pro…index.php?title=DDF_DMXC3) yet. But if you post a DMX chart of your device , I will create a DDF for you.


    2 and 3: Yes, there is a kind of user manual. You will find it under the following link: https://wiki-en.dmxcontrol-pro…le=Tutorials_DMXControl_3 This tutorial is very old and some things have been changed since the creation of this documentation. But you should get some information for a first step into DMXControl 3. The way to save cues in a cuelist are the same as back then. But here are the basic steps: Set up your light scene by selecting the devices / groups in the stage view and change the values in the device control on the right side. After that, you can save this scene to a cue by clicking on the button "Save as cue" on the left Side of the DMXControl window. You will now be asked, which device functions should be saved. By clicking on "ok", you save your scene to a new cuelist. This cuelist should now pop up and you can edit it further.


    Well as I mentioned, the tutorial doesn't represent the current state of the software. We work hard do update our documentation but this will take some time (because we have not enough manpower).


    I hope I could help you with my post. If you have any further questions, just ask :)

    Regards

    JP

    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