|
This section is actively undergoing a major edit for a while. To help avoid edit conflicts, please do not edit this section while this message is displayed or contact the editor (Xemo2011) of this page. | This page was last edited at 20:17, 31 October 2013 (UTC) 4042 days ago. |
Hint:
25.5.2013: UPrenner: create the article page
30.10.2013 UPrenner: work-in-progress
30.10.2013: UPrenner article ready, just update of pictures
If you are a native speaker, please Help us and review this
Overview
The command box delivers a simple, open surface for the live business. With the command box DMXControl can be controled in all modules by button. So e.g. DMX channels can be set on predefined values of devices, start/stop effects, the audio player start/stop, changed attitudes of the sound Analyzer etc.
In addition, the command box can be started with a second screen and/or touch screen ideally to have direct control over DMXControl.
Description
By the free programming of the individual buttons one, operation environment which is adapted to the claims of one's own and graphic can be made for DMXControl. This makes sense primarily on events because one must have opened only a window (command box window) and can control all actions from there openly. By use of banks up to 1000 buttons are possible for 20 at a matrix of 10 x 10 or 4000 buttons at a matrix of 20 x 20. The number of buttons is variably adjustable. With the mouse or about a direct input about the keyboard the number of buttons can be adjusted.
 |
Adjusting the buttons with the mouse is limitedly on a matrix of 20 x 20. By a direct input also higher values can be entered. That it makes no more sense depending on monitor as of a certain size it can do at considerably higher values also to falls refrained come. |
The variable command box window can be adapted to the corresponding requirements in his size. The button are scaled so that they are distributed evenly on the window. Through this window has space also for other made on the monitor to itself ( e.g. Graphical view ). A text, a color, an icon and a corresponding order can be assigned to every badge (see fig. 1).
| Picture 1: Design example of the command box |
| Picture 1: Design example of the command box |
Controls
The checking box is located in the upper part of the command box window « Programming mode & raquo; (see) fig. 2, you can change with which between the programming mode and the User mode.
| Picture 2: Checkbox to serve between Programming mode and User mode |
| Picture 2: Checkbox to serve between Programming mode and User mode |
To cover button with commands, the command box must be switched over into the programming mode. By clicking on the checking box the input mask appears in the upper area (see fig. 3).
| Picture 3: The input mask |
| Picture 3: The input mask |
| |
In the live business the programming mode must be turned off, i.e. the using mode must be active! |
The matrix size of the command box can be adjusted in the input mask in the upper area, i. e. the number of button per line as well as the number of lines per bank.
A changing the matrix size additionally is possible. Changing the line count is relatively easy, only when changing the column number the button are thrown in a mess.
Since the button can be moved in the programming mode by Drag and Drop, one can the buttons then sort themselves again. When moving the buttons the button in front of which a black vertical line is is taken in the old place and inserted in the place before the button. All buttons between this move themselves, what is requiring habituation at the beginning of something. But if one has seen through the system, it gets simpler.
With the button on right above « Reset button » an occupied command box button can be reseted (deleted), it is for this the corresponding button to select and then the button « Reset button » operating.
The occupancy of the corresponding button is announced at the table after choice of a button. If the button isn't occupied yet, seems under button name becomes the corresponding button with his index number as well as the standard color gray and at module Deactivate shown .
| Button name: | A name of one's own can be listed in the field button name by a click on the field for the button which then appears on the button afterward, too. | |
| Color: | By a click to the field color the color palette window in which one can select the color of the button opens. | |
| Icon: | At a click on the icon field a file browser in which one can select and load a corresponding graphic for the button opens. The file format is restricted to the following graphics: bmp; dib; gif; jpg. The size of the picture should amount to 64 x 64 pixels therefore be square. | |
| Module: | At the click to the field module a drop down list from which one can select one of the modules available in DMXControl opens.
The following modules can be selected: Disabled: Audio: Audiotrack: BeatTool: Chasers: Command line: Command box: Cue libary: Cue list: Devices: DMX output: DMXIn remote: Group selection: Joystick: Master: Midi Remote: OSC receiver: Sound Analyzer: Submaster: Textbook: |
 |
Plugins which support a control by the command box also seem additional here. This shall exemplarily be called MadMaxOne plugin here. |
| MadMaxOne Plug-In: Using command on the plugin MadMaxOne. | ||
| Device/Function: | The corresponding functions of the module are selected by a click in this field be able to depending on select module, or the device to be mentioned. | |
| Channel: | By a click in this field an appropriate channel for a device can be adjusted or depending on module and function a corresponding action can be assigned. | |
| Flags: | At a click on the field flags a dropdown list with which the corresponding flags can be put or deleted opens.
The following flags can be selected: Toggle mode (T): Use specified value (O): Ask for value (A): Ignore value 0 (I): | |
| Value: | By a click in this field a corresponding value can be deposited quickly for a device or a function. |
| |
Both at ' '“Using indicated value“and“Questioning on value“the entered value is a per cent value in the area of 0. 000% to 100. 000% ' '. A input of values 0 to 255 or 0 to 65535 isn't possible here. |
Module commands
- Modul: Command box
- Meaning from device/function and channel
| Device/Function | Description | Channel | Description |
|---|---|---|---|
| Bank | A choice of this function there is the possibility of accessing the different banks (1-10) about the order in the command box. | Next | The next bank selects. |
| Previous | The previous bank selects. | ||
| Bank 1 to 10 | Direct choice of one of the ten banks. | ||
| Button | With the function button orders already made can be cloned in the command box or used in other modules. | Button name | Name of the button which shall be used. |
Meaning of the Flags:
| Flag | Meaning | Description |
|---|---|---|
| T | Toggle mode | The Flag »Toggle mode« result in the function's being set by the first call and being reset by the second call. |
| O | Used specified value | The Flag »Used specified value« result in the being assigned to the appropriate channel of the value in the openings' value. This value isn't DMX value 0 to 255 but a per cent value 0. 000 to 100. 000% |
| A | Ask for value | The Flag »Ask for value« result in the opening at call of the order of an input window in which the per cent value can be entered. |
| I | Ignore value 0 | The Flag »Ignore value 0« result in the being ignored of a value of zero. Do you need at some orders to ensure a correct function. |
Tip(s)
- Chasers can be put on command box buttons by Drag & Drop.
- An on/off mode of the buttons is coupled to the flag toggle mode of the command. The buttons seem visually depressed until the next click here durably, too.
- In the programming mode the buttons can be moved by Drag & Drop. To this the button must be let off exactly between two buttons (there where the line appears).
You shall go exemplarily using the effect module into the possible attitude for select effect in this place. « Channel », is come in to « flags » and « value » only on the entry fields « module », « devices/function » since the entry fields « button name », « color», and « icon » are individual input fields. You find a list of all possible attitudes above.
| Start the chaser | Stop the chaser | Start/Stop the chaser | |||
|---|---|---|---|---|---|
| Module: | Chasers | Module: | Chasers | Module: | Chasers |
| Device/Function: | Selected | Device/Function: | Selected | Device/Function: | Selected |
| Channel: | Start | Channel: | Stop | Channel: | Start/Stop |
| Flags: | -,-,-,- | Flags: | -,-,-,- | Flags: | T,-,-,- |
| Value: | - | Value: | - | Value: | - |
| Set acceleration of chaser | Set intensity of chaser | Chaser next step | |||
|---|---|---|---|---|---|
| Module: | Chasers | Module: | Chasers | Module: | Chasers |
| Device/Function: | Selected | Device/Function: | Selected | Device/Function: | Selected |
| Channel: | Set acceleration | Channel: | Set intenstity | Channel: | Next step |
| Flags: | -,O,-,I | Flags: | -,O,A,- | Flags: | -,-,-,- |
| Value: | 50 | Value: | - | Value: | - |
| |
The following points have to be taken into account at the above examples:
|
| |||||||||||||