Midi Plugin

  • Hi - I'm upgrading from DMX control 2 to 3 after the recent windows upgrade problem.

    I'm currently creating new DDF's for all my light fixtures, and am now looking at learning the basics of the software in order to setup my first light show.


    I have tried installing the Midi plugin. With DMX control 2, I used a APC mini controller to control my lights.

    I have copied all of the (unzipped) files from the Midi plugin download to both the kernel/plugins and gui/plugins folders, but can't see any instance of the plugin on the DMX control GUI, or any way to enable it. Is there another file that I need in order for the plugin to work, or is there a specific place that I need to place the files / other option that I need to enable. I seen there was another post here on the forum about a file missing from the download - but the post was marked as resolved (with no replies).


    I haven't even started to program any of my light shows yet, but wanted to get the software functional before I went any further.


    Many thanks in advance.

  • JPK

    Approved the thread.
  • Hi and welcome in our forum,

    because the Midi-Plugin is not build with our code signing certificate and because it is "from the internet" (as Microsoft say), you have to unblock all files individually. To do so, do a right click on every single file of the plugin and go into the property window. There is a "unblock" button. After clicking this button for every file, the plugin should appear in the plugin manager. However while using the plugin there could be in some corner cases a deadlock and the DMXControl 3 GUI crashes (the kernel keeps running). But after reconnecting to the kernel with another GUI, the midi plugin doesn't load correctly and you could not use it until you restart DMXControl 3 in total. In DMXControl 3.2 (which will hopefully be released in the next few weeks) the midi functionality is integrated in DMXControl 3 itself and the bug is fixed. So I would recommend you to start trying DMXControl 3 now with some cuelists and not to pay that much attention on the midi input and the Input Assignment. Especially the second one is replaced in total and you have to redo your connections anyway when updating from 3.1.3 to 3.2.

    JP

    im Falle eines Falles klebt Gaffa einfach alles, denn Gaffa ist dein Freund und Helfer :thumbup:

  • Hi JP,

    many thanks for the reply :-)


    I'm going to go ahead and setup some cuelists, and use the softdesk to control everything for now, and then have a look again at the midi controls one the new version is released.


    I think that I'm going to have some more questions, as there are a few things that I can't work out how to do yet (such as with DMXcontrol 2 you could assign chasers into groups, so only one chaser from within that group could run at a time).


    Thanks again,

    Gaz

  • I think that I'm going to have some more questions, as there are a few things that I can't work out how to do yet

    Feel free to ask them if they came up :)

    (such as with DMXcontrol 2 you could assign chasers into groups, so only one chaser from within that group could run at a time).

    DMXControl 3 has a quite similar thing, called cuelist groups. To add a new cuelist group just go to the project explorer and open the "cuelist group" folder. Add a new group (e.g. via right click into the right part of the project explorer) and drag&drop the cuelists you want to group on the group entry in the tree. The last step is to go into the group settings via right click => Properties (if you have multiple groups you can select all of them and do the following changes for all at once). There you change the cuelist start behavior from "None" to "single list running". Now the cuelists in the group behave in the same way as in DMXControl 2.

    im Falle eines Falles klebt Gaffa einfach alles, denn Gaffa ist dein Freund und Helfer :thumbup:

  • HI JP,

    Thanks for the info!


    I've added some cues for a light, and then grouped them together in a cuelist group.

    Using the softdesk, I've added some buttons to control the light, and have set the softdesk buttons to toggle.

    All the buttons have then been added to the cuelist via settings, (dragged over to the Go / Stop section of the cuelist).


    Everything works. When I press button 1, light cue 1 starts. When I press it again, light cue 1 stops.

    But, if I've pressed button 1 to start cue 1 - and then press button 2 to start cue 2, button 1 stays pressed, cue 1 stops and cue 2 starts.

    Is there anyway to also combine the buttons in softdesk so that only one button in a 'group' can be pressed?


    I'm also saving my project file to onedrive, which means I can work on my project from any location - and also have a current backup if a laptop should go down.

    Everything saves fine, apart from the settings (which includes my softdesk mapping). Is there a way to also save the settings along with the project?


    Best regards,

    Gareth.