Posts by JPK

    Now, its time: The next DMXControl 3.2 livestream with your questions goes live on Saturday, 2020-05-23. In this thread we will collect your questions. We try to summarize these questions again and then answer as many as possible. For this purpose we have summarized the rules for the questions:

    Rules for the questions:

    • One or more questions can be asked per person or per post.
    • Questions can be asked about the functionality of individual program parts of DMXControl 3.2.
    • Questions can be asked about possible implementations of an use case.
    • Questions like "When will this certain feature come?" etc. will be not answered, because this Q&A is about the handling of DMXControl 3.2.

    Your :dmxclogo DMXControl-Team :dmxclogo

    Hi,

    Bye the way: what is the significance of 'mindmx = "191" maxdmx ="128"' in the example - with mindmx > maxdmx?

    back then in the beginning of DMXControl 3, we defined that maxval is always greater than minval, because both parameter define the minimum and maximum possible value in a device function block. We also defined that Mindmx and maxdmx describe the position of minval and maxval. Therefore, if mindmx is greater than maxdmx you get a ramp down from maxval to minval while increasing the dmx value from mindmx to maxdmx. This behavior is designed for device functions like wheel rotation where the higher rotation speed is at the lower end of the device function block.

    Regards

    JP

    Hi,

    there are two types of errors in the DDFs. On the one hand are syntax errors, so the XML has a wrong structure. In this case, DMXControl 3 can not parse it and mark it as corrupted. You can find those errors for example with Notepad++ and the plugin "XML Tools". On the other hand there could be logical errors in the XML so that some parts are not in the way DMXControl 3 would expect them to be. In this case DMXControl would give you some information about whats wrong with it.


    So as mentioned, in your case the XML has a wrong structure. This mistake was a hard one to find, but finally, I found it. You accidentally added a space caracter in the "dmxchannel" parameter of "tilt". After fixing this, the xml structure checker of XML Tools in Notepad++ can not find problems any more. So it should be loadable in DMXControl 3 (what I've not tried yet, so there could be some other logical problems in it, I have not found).


    If you have finally fixed the DDF, you may upload it in our DDF Library (https://dmxc.org/ddfs) so everyone can find and use it :)

    Hi and welcome in our Forum,

    I have created a device definition file (xml) for a moving head unit (Event Lighting M1H200W), but now, how do I get the file recognised by the project explorer.

    There is a User Device Folder for DDFs. You can find it by opening the start menu and browsing to the DMXControl 3 folder. There you can find the link to the users device folder. Just copy your xml file into the folder. If you have allready added your device xml to the folder and it is not in the list, then the kernel should give you some warnings what is wrong with it.

    Best regards

    JP

    Copying a cue is must easier than DMX2, I can literally just copy and paste it from a cue list without even loading it.

    Correct :)

    Editing a cue, I load it in to the progammer (and this will then show it in Stage View?) and I can edit it from there and then save?

    Yes, you can load it in the Programmer via the "Edit in Programmer" function. As Johannes already said, the Stage View is a tool to display what is going on with the devices. So it shows a mixture of the properties in the Programmer and all running cuelists. When the cue is loaded in the Programmer, then you can change it by changing the Properties via the usual ways (Device Control,...) and then save it to the according cue.


    If you wander if your project has a problem just add it here to a post and then I can look into it and try to find the problem :)

    Hi,

    I've tried to do the same in DMX 3 but it saves no values at all.

    the reason for this is the fact that DMXControl 3 detects, if you change a device property and store this value in the programmer. By adding a cue to the cuelist, DMXC 3 uses the values in the programmer. But if you start a cue, the values of this cue are send to the HAL (to match the property values to DMX values) and are not send to the programmer. Thats why there is no value to save there, if you just start a cue. But: There are two ways to acheve your expected result. Which one you should use is defined by the expected result. If you just wand an exact copy of a cue, you can simply copy&paste it. In this case jusr do a rightclick on the cue you want to copy and click on the "Copy Cue" entry in the now opened popup menu. In the target position in the cuelist (it can even be another cuelist than the one in which the souce cue is in) do also the right click and hit "Paste Cue".


    If you don't want an exact copy but most of it, you can just copy&paste the cue and edit it. To do this, just open the popup menu for the cue after pasting it again and click on "Edit in Programmer". With this command, all Parameter Values of the cue are loaded into the programmer. Now you can change the paramters and if you are finnished, just hit the update button on the left. If you want to abort this editing process, clear the programmer. This is the second way, but there is a way "2.5": Just edit the source cue in the Programmer, delete all parameters, you don't want to copy and then hit the "Add Cue" button on the left side. From there the process is as usual. The only thing to remember is to clear the programmer afterwards and not to hit the update button (because you are in editing mode for the source cue).

    Regards

    JP

    Hi and welcome in this forum,

    when you add a cue, a little window should pop up (the Programmer Filter). Here you can select which properties you want to save. Just click here on "All" on both sides. But a "Save All"-Preselection is not implemented in DMXControl 3 yet. But to understand why you search for this functionality, maybe you can explain a little bit more about your setup (theater, disco etc.) and what you want to do. If I can understand your situation, maybe I can show you the way it is intended to be done in DMXControl 3 :)

    Regards

    JP

    Hi,

    this sounds like you have accidentally changed the Grand Master. Therefor, the device control shows the saved value and the Stage View gives you the returning value (after the Grand Master). To fix this problem just open the Master Panel (in the menu via "Controls" => "Master") and put the Grand Master to 100%.

    Regards

    JP

    Hmmm, as mentioned in the specs of those 3W LED modules, they have a beam angle of 120°. This and with the fact that they have only 3 watts would lead to a very low amount of light and I would say, that this is not enough in bright areas. But maybe, you can buy just two or three of them to build up a prototype. Them you can see, if they are bright enough.


    P.S.: I would not use LED stripes because their beam angle is usually even higher.

    Hi,

    for which kind of application do you want to use your fixtures? 3 watt LED modules can be seen, but they are not very bright. Usually, LED fixtures contain at least 4 to 7 LEDs of that kind (or with much more power) to produce a certain ammount of light output. But on the other side maybe the brightness is enough for your kind of application. Therefor just tell us, what you plan to do with those fixtures.

    regards

    JP

    Hi,

    yes, we have some (unfortunately really old and partly outdated) English tutorials. You'll find them in our Wiki. https://wiki-en.dmxcontrol-pro…le=Tutorials_DMXControl_3 We know that this is not a good situation, but the German Tutorial is in the same situation. But with tutorials you can start to understand, how DMXControl 3 is working. For the newer features, we have some "Did you know?" News in our news section: https://forum.dmxcontrol-proje…cle-list/5-schon-gewusst/ I hope, this will guide you with your first steps in DMXControl 3. If you have any questions, then ask them here in the Forum :)

    Regards

    JP

    Since DMXControl 3.2 is now released and some of you might have questions, we are planning another Live Q&A in December 2019. In this thread we will collect your questions. We try to summarize these questions again and then answer as many as possible. For this purpose we have summarized the rules for the questions:

    Rules for the questions:

    • One or more questions can be asked per person or per post.
    • Questions can be asked about the functionality of individual program parts of DMXControl 3.2.
    • Questions can be asked about possible implementations of an use case.
    • Questions like "When will this certain feature come?" etc. will be not answered, because this Q&A is about the handling of DMXControl 3.2.

    Your :dmxclogo DMXControl-Team :dmxclogo

    Hi,

    yes, to use the binary switcher and use it to stop the cuelist if the button signal is not "true" is one (the) correct way to implement this :) Some advanced ideas could possibly be showed in one of our Did you know? posts in the special week ;) So stay tuned :)


    Feedback: The midi input itself already supports feedback, so you can change the intensity of the button light, if it is pressed by the input function itself. But the input assignment can not give a feedback to midi yet. One reason for that is, that there were so many other things to do in the IA and we had to make a cut in order to get the basic features done. The other thing is, that midi feedback is in some cases more complicated than a feedback to other input types (thats why we have already a feedback function for the new softdesk). The midi feedback should take motor fader feedback into account too. But motor faders have a mechanical delay, a transient change of the input value towards the target value and such a fader can be blocked (other than controls on the softdesk). So we think about integrating some advanced functions like a feedback loop detection or a blocking detection to protect controls on the midi devices to handle those challenges. Thats why it is not included yet.

    Regards

    JP

    Hi,

    this is a problem, Microsoft introduced with their august update. There was a bug in this update which crashes the support for a special function in Visual Basic (which is the programming language of DMXControl 2). But now there are specific updates to encounter this problem. You will find a table of required updates separated for every current Windows version in the following post of mine: Fehler 5 "Translator" nach Win-Update 1903 To add the according update, you normally only have to start the update process once again (manually) and the correct fix should be selected and installed. If not, select the fix you see in the linked table and install it by hand.

    Regards

    JP