English DMXC-Wiki - User contributions [en]

Cue list DMXC2

2014-03-26T18:24:42Z

DominicjpgacgftlfToyama: /* Overview */

{{Chaptertitle_DMXC}} 

{{Hint|25.10.2013: UPrenner: create the article page 25.10.2013 UPrenner: work-in-progress 
25.10.2013: UPrenner article ready, just update of pictures '''If you are a native speaker, please Help us and review this article
}} 
{{NavigationTop-Man2
| LinkBackwards = Scenes_DMXC2
| TextBackwards = Scenes
| LinkForwards = Chasers_tool_DMXC2
| TextForwards = Chasers tool
}}
{{Start-LaTeX}}
==Overview==
With the cue list several cues can be sequenced. This offers you the possibility of organizing the individual cues at an event with predefined expiration time. This module is similarly suitable for theater events and comparable events.

{{Picture_with_subtitle |DMXC2_Manual_cue_list_new_cue.png|1|Create a new cue|center}}

Per cue which takes effect however only within the cue list or an effect a one dazzling time as well as a duration you (describe in the Chasers tool) as hold time can be indicated.
Values of a cue remain active on the version until they are overwritten explicitly, for example by another cue.

All cues are managed in the cue library and can be chosen and reused from there.

==Description==

One or several cues form a cue list. The maximum number of cues per cue list is only limited by the resources of your computer. Playing a cue list means the sequential execution of all individual cues under consideration of the the one dazzling time and duration (hold time). The cues can also manually be further switched. Several cue lists can expire at the same time (parallel operation).

E. g. you use the cue tool at theater applications and everywhere there where it suffices, simple cues after a particular duration (hold time) further add-on. The cue tool works resource loading substantially less than the [[chaser_tool_DMXC2|chaser tool]]. The cue list is always worked off sequentially and to be more precise as of the cue which is just highlighted. For the beginning of the play, so the first entry must be highlighted.

==Controls==

{{Picture_with_subtitle |DMXC2_Manual_cue_list_window.png|2|The cue list|center}}

So that the button « GO & raquo; the manual further wiring can work, the following conditions must be filled for:

*The cue list must be represented (Button » play « is clicked).
*The respective cue must have '''manually''' as a duration (hold time) (adjust time to zero and one then still reduce tenths). If a duration (hold time) is adjusted, this is taken into account which yes also can be quite practical (to let e.g. a sequence of light atmospheres go with firm times and switch to the next cue manually only later again).
*The cues must be marked with the checking box (hook), they otherwise are deactivated. 

At a right click on the cue name opens himself a context menu with the menu item « Set color . . . « a color palette window opens where a color can be selected for the cue name.

{{BoxHint
|Text = If HTP is not necessary, so HTP turn it off in the [[Program_settings_DMXC2|program settings]] (depends on the cue definition).
}}

==Module commands==

* Modul: '''Cue list'''

* Meaning from ''device/function'' and ''channel''
{| class="wikitable centered"
|- style="vertical-align:top;"
!style="width: 105px"| Device/Function
!style="width: 195px"| Description
!style="width: 105px"| Channel
!style="width: 195px"| Description
|- style="vertical-align:top;"
|style="width: 105px" rowspan="5"| Select
|style="width: 195px" rowspan="5"| The further order is applied to the currently select cue list. (The Command selects at this function the makes no sense)
|style="width: 105px"| Start/Stop
|style="width: 195px"| The command ''Start/Stop'' starts/stops the select cue list at automatic expiry. (The command should be used in connection with the T flag.)
|- style="vertical-align:top;"
|style="width: 105px"| Start
|style="width: 195px"| The command ''Start'' starts the select cue list at automatic expiry.
|- style="vertical-align:top;"
|style="width: 105px"| Stop
|style="width: 195px"| The command ''Stop'' stops the select cue list at automatic expiry.
|- style="vertical-align:top;"
|style="width: 105px"| G O !
|style="width: 195px"| The command ''G O!'' executes the next cue from the Szeneliste.
|- style="vertical-align:top;"
|style="width: 105px"| Scroll to current cue
|style="width: 195px"| The command '' scroll to current cue'', forces the current cue to scroll to the visible window area.
|- style="vertical-align:top;"
|style="width: 105px" rowspan="2"| Next Previous Other entries
|style="width: 195px" rowspan="2"| The further command is or into the dropdown named cue list used on the currently next or previous cue.
|style="width: 105px"| Select
|style="width: 195px"| Selects the next (previous) cue list or the one selected in the dropdown ''device/function''.
|- style="vertical-align:top;"
|style="width: 105px"| Start/Stop Start Stop G O ! Scroll to current cue
|style="width: 195px"| see above
|}

Meaning of the ''Flags'':
{| class="wikitable centered"
|- style="vertical-align:top;"
! style="width: 35px"| Flag
! style="width: 105px"| Meaning
! style="width: 460px"| Description
|- style="vertical-align:top;"
| style="width: 35px; text-align:center"| T
| style="width: 105px"| Toggle mode
| style="width: 460px"| The Flag »''Toggle mode''« result in the function's being set by the first call and being reset by the second call.
|- style="vertical-align:top;"
| style="width: 35px; text-align:center"| O
| style="width: 105px"| Used specified value
| style="width: 460px"| 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%
|- style="vertical-align:top;"
| style="width: 35px; text-align:center"| A
| style="width: 105px"| Ask for value
| style="width: 460px"| 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.
|- style="vertical-align:top;"
| style="width: 35px; text-align:center"| I
| style="width: 105px"| Ignore value 0
| style="width: 460px"| 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)==

*As follows one can configure cue lists so that the following one is activated and started when reaching the end of a list: An command cue is with the order at the end of every cue list ''' cue list > Next & gt; Start ''' to insert.
*There is an accumulation of the fade and permanent times to synchronize the list with a time code for longer scene lists since the version 2. 12.
{{End-LaTeX}}
{{NavigationTop-Man2
| LinkBackwards = Scenes_DMXC2
| TextBackwards = Scenes
| LinkForwards = Chasers_tool_DMXC2
| TextForwards = Chasers tool
}}
[[de: Effektsequencer_DMXC2]]
[[Category: DMXControl 2]]

Channel view DMXC2

2014-03-26T18:21:10Z

DominicjpgacgftlfToyama: /* Tip(s) */

{{Chaptertitle_DMXC}} 

{{Hint|20.5.2013: JKuehn: create the article page 25.10.2013: work-in-progress by UPrenner 
25.10.2013: UPrenner article ready, just update of pictures '''If you are a native speaker, please Help us and review this article
}} 
{{NavigationTop-Man2
| LinkBackwards = output_plugins_DMXC2
| TextBackwards = Output Plugins
| LinkForwards = Scenes_DMXC2
| TextForwards = Scenes
}}
{{Start-LaTeX}}
==Overview==
The channel overview displays a general overview of the current channel status of DMX signals. Information about the current channel values, the channel assignment, and the source of the channel value are represented here.

==Description==
You can see and adjust directly the channel value of every single DMX channel in the channel overview. This module serves in the disco area to analyze to test ticks or around an unknown device configuration mainly. The channel overview is primarily the individual light atmospheres helpfully in the theater area at being clear to it and the generation. E.g. you also can test the effect of procedures into the DDFs with this window since the DMX values of the individual channels are shown.

{{Picture_with_subtitle |DMXC2_Manual_channel_overview_window.png|1|The channel overview|center}}

The individual channels are represented in the middle part of the channel overview into tabular form. Every cell represents one of the altogether 1024 of DMXControl supported DMX channels. In turn each of these cells is subdivided into several areas which contain different information.

{{BoxHint
| Text =
{{(!}}
!Information: Channel representation
{{!-}}
{{!}}
{{!}}
{{!}} style="text-align: left;"{{!}}The channel number which gives the address of the appropriate channel is in the left upper corner of the cell. An advertisement for the channel value which shows the intensity of the appropriate channel from 0 to 255 is on the right side. A joist represents the channel intensity graphically besides that on the left.

Directly you show under this, to which function the channel in the assigned device heard or which equipment function he heads. The name of the corresponding device is a line in a gray field represented below. If a device has several channels, the gray field reaches to all appropriate channels.

A colored marking which announces the source of the channel value is shown on the lower part of the cell. The assignment of the color to the source has to be taken from the lower part of the channel overview.

{{!}}
{{Picture_with_subtitle |DMXC2_Manual_channel_overview_channel_representation.png|2|Description of the channel information|250px|center}}
}}

{|
|-
| The channel chosen currently is marked by a red frame. Click in one of the cells to select another channel. The value of the chosen channel can be changed by the Slider on the left window edge. However, a multiple selection of channels is also possible with the help of the Shift and Ctrl buttons. ||
{{Picture_with_subtitle |DMXC2_Manual_channel_overview_channel_multiple_selection.png|3|multiple selectionof channels in the channel overview|500px|center}}
|}

==Controls==
====Button Out/In====
With the button « Out » or « In » in the lower left corner you adjust, whether the DMX-out or DMX in values is shown. Channel values are, only then shown case the active version Plugins DMX into support in the DMX in view.

====Slider====
A Slider which is used to adjust the value of the select channels is directly over this button.
The scrolling up joist on the right side serves to scroll by the indication of the channels merely.

====Double-click on channel====
Double-click through one an input window in which new DMX value can one want to enter for the select channel by keyboard opens on a channel (cell in the channel overview).

====Marking several channels====
Buttons ''''Shift'''' and ''''Ctrl'''' can with the Windows typical channel areas are selected which have changed by the Slider or the scrolling up wheel on a value at the same time for themselves.

====Changing channel value with mouse wheel====
With a mouse with scrolling up wheel the values of the active highlighted channel can get high or scrolled down in 10s steps.

====Channel On/Off with Space-button====
With the Space button you can switch one or several highlighted on (DMX value 255) or turn (DMX value 0) off.

====Source overview====
In the lower area of the channel overview everyone is shown to sources possible for the version and provided with a colored marking, through what one can identify the source for the channel value version of a channel. Every source has his own mixer channel.
{{Picture_with_subtitle |DMXC2_Manual_channel_overview_source.png|4|Details of all possible DMX value sources.|center|650px}}
The entry '''unknown source''' puts the public mixer channel, which all program parts of DMXControl which don't have a mixer channel of their own use. The sources are unknown because the mixer channel cannot be assigned to any tool by DMXControl directly.

==Tip(s)==

The window '''channel overview''' also can be used to test a new equipment. Any DMX channel (even without a Device Definition) may be set here. Simply select channel and use the Slider on the left. Of course the start address of the device has to be taken into account.

{{BoxHint
| Text =
With the space bar you can toggle between the channel values '''0''' and '''255'''.
}}
{{End-LaTeX}}
{{NavigationTop-Man2
| LinkBackwards = output_plugins_DMXC2
| TextBackwards = Output Plugins
| LinkForwards = Scenes_DMXC2
| TextForwards = Scenes
}}
[[de: Szenen_DMXC2]]
[[Category: DMXControl 2]]

Channel view DMXC2

2014-03-26T18:09:49Z

DominicjpgacgftlfToyama: /* Overview */

{{Chaptertitle_DMXC}} 

{{Hint|20.5.2013: JKuehn: create the article page 25.10.2013: work-in-progress by UPrenner 
25.10.2013: UPrenner article ready, just update of pictures '''If you are a native speaker, please Help us and review this article
}} 
{{NavigationTop-Man2
| LinkBackwards = output_plugins_DMXC2
| TextBackwards = Output Plugins
| LinkForwards = Scenes_DMXC2
| TextForwards = Scenes
}}
{{Start-LaTeX}}
==Overview==
The channel overview displays a general overview of the current channel status of DMX signals. Information about the current channel values, the channel assignment, and the source of the channel value are represented here.

==Description==
You can see and adjust directly the channel value of every single DMX channel in the channel overview. This module serves in the disco area to analyze to test ticks or around an unknown device configuration mainly. The channel overview is primarily the individual light atmospheres helpfully in the theater area at being clear to it and the generation. E.g. you also can test the effect of procedures into the DDFs with this window since the DMX values of the individual channels are shown.

{{Picture_with_subtitle |DMXC2_Manual_channel_overview_window.png|1|The channel overview|center}}

The individual channels are represented in the middle part of the channel overview into tabular form. Every cell represents one of the altogether 1024 of DMXControl supported DMX channels. In turn each of these cells is subdivided into several areas which contain different information.

{{BoxHint
| Text =
{{(!}}
!Information: Channel representation
{{!-}}
{{!}}
{{!}}
{{!}} style="text-align: left;"{{!}}The channel number which gives the address of the appropriate channel is in the left upper corner of the cell. An advertisement for the channel value which shows the intensity of the appropriate channel from 0 to 255 is on the right side. A joist represents the channel intensity graphically besides that on the left.

Directly you show under this, to which function the channel in the assigned device heard or which equipment function he heads. The name of the corresponding device is a line in a gray field represented below. If a device has several channels, the gray field reaches to all appropriate channels.

A colored marking which announces the source of the channel value is shown on the lower part of the cell. The assignment of the color to the source has to be taken from the lower part of the channel overview.

{{!}}
{{Picture_with_subtitle |DMXC2_Manual_channel_overview_channel_representation.png|2|Description of the channel information|250px|center}}
}}

{|
|-
| The channel chosen currently is marked by a red frame. Click in one of the cells to select another channel. The value of the chosen channel can be changed by the Slider on the left window edge. However, a multiple selection of channels is also possible with the help of the Shift and Ctrl buttons. ||
{{Picture_with_subtitle |DMXC2_Manual_channel_overview_channel_multiple_selection.png|3|multiple selectionof channels in the channel overview|500px|center}}
|}

==Controls==
====Button Out/In====
With the button « Out » or « In » in the lower left corner you adjust, whether the DMX-out or DMX in values is shown. Channel values are, only then shown case the active version Plugins DMX into support in the DMX in view.

====Slider====
A Slider which is used to adjust the value of the select channels is directly over this button.
The scrolling up joist on the right side serves to scroll by the indication of the channels merely.

====Double-click on channel====
Double-click through one an input window in which new DMX value can one want to enter for the select channel by keyboard opens on a channel (cell in the channel overview).

====Marking several channels====
Buttons ''''Shift'''' and ''''Ctrl'''' can with the Windows typical channel areas are selected which have changed by the Slider or the scrolling up wheel on a value at the same time for themselves.

====Changing channel value with mouse wheel====
With a mouse with scrolling up wheel the values of the active highlighted channel can get high or scrolled down in 10s steps.

====Channel On/Off with Space-button====
With the Space button you can switch one or several highlighted on (DMX value 255) or turn (DMX value 0) off.

====Source overview====
In the lower area of the channel overview everyone is shown to sources possible for the version and provided with a colored marking, through what one can identify the source for the channel value version of a channel. Every source has his own mixer channel.
{{Picture_with_subtitle |DMXC2_Manual_channel_overview_source.png|4|Details of all possible DMX value sources.|center|650px}}
The entry '''unknown source''' puts the public mixer channel, which all program parts of DMXControl which don't have a mixer channel of their own use. The sources are unknown because the mixer channel cannot be assigned to any tool by DMXControl directly.

==Tip(s)==

The window '''channel overview''' also can be used to test a new equipment. Being able to want to change arbitrary DMX channels (simply select channel and use the Slider on the left) even without DDFs through which the channel configuration of single equipment can be found out. Of course the start address of the device has to be taken into account.

{{BoxHint
| Text =
With the space bar you can toggle to and fro at which between the channel values '''0''' and '''255''' is suitable to particularly the be clear. E.g. through this headlights can very fast at or turn off.
}}
{{End-LaTeX}}
{{NavigationTop-Man2
| LinkBackwards = output_plugins_DMXC2
| TextBackwards = Output Plugins
| LinkForwards = Scenes_DMXC2
| TextForwards = Scenes
}}
[[de: Szenen_DMXC2]]
[[Category: DMXControl 2]]

MIDI remote control DMXC2

2014-03-26T18:07:11Z

DominicjpgacgftlfToyama: /* The configuration window */

{{Chaptertitle_DMXC}} 
 
{{Hint|25.10.2013: UPrenner: create the article page 02.10.2013: UPrenner: work-in-progress 
02.02.2013: UPrenner article ready, just update of pictures 02.02.2013: UPrenner pictures updated 
'''If you are a native speaker, please Help us and review this
}} 
{{NavigationTop-Man2
| LinkBackwards = Joystick_control_DMXC2
| TextBackwards = Joystick control
| LinkForwards = DMXIn_remote_control_DMXC2
| TextForwards = DMXIn remote control
}}
{{Start-LaTeX}}
==Overview==
{{Picture_with_subtitle |DMXC2_Manual_MIDI_remote_control_activate.png|1|MIDI-Fernsteuerung|right}}
The MIDI remote control enables DMXControl to use MIDI protocol. Unlike the DMXIn remote control the MIDI remote control only uses a word size of 7 bits so that only values of 0 to 127 over the protocol are transferred.
Apart from little MIDI keyboards, there is the Behringer BCF2000 or BCR2000 as well as Korg nanoKONTROL 2 or Pioneer CDJ 350 also.
It is advisable to review the reference documentation here: Wikipedia <ref> MIDI on Wikipedia http://de.wikipedia.org/wiki/Musical_Instrument_Digital_Interface </ref>
 
 
 

==Description and configuration==

Some of the best known midi controllers are well:
* BCF2000/BCR2000 von Behringer <ref>BCF2000 http://www.behringer.com/de/Products/BCF2000.aspx </ref>
* Korg nanoKONTROL 2
* Pioneer CDJ-350

But also almost every keyboard (instrument) can be used with a MIDI input, or usb to midi interface.
MIDI devices which connect via USB also work.

The configuration files of the BCF2000 are shown in the pictures.

===The configuration window===
DMXControl needs to know about new MIDI interfaces. If your interface or device was not recognized on launch, you should enable it now.

Under the menu « Settings » choose configuration and choice of the corresponding MIDI device are carried out « MIDI remote control » here. If your device does not appear in the MIDI in/out port list then you should try reinstalling your device drivers.

After choosing the MIDI in device, you will be able to see incoming MIDI message appear in the bottom of this window.

{{BoxHint
|Text = It should be respected, however, on this that the subsequent configuration with « MIDI Learn » only work when the MIDI remote control is deactivated in between (see picture ''active voice'').
Furthermore a simultaneous use of the MIDI port of (a device) works together with another program (e. g. Winamp control about Xor MIDI Control) only the original (not Windows) drivers of the manufacturer (here: Fame).
}}

===Config of MIDI channel configuration===

{{Picture_with_subtitle |DMXC2_Manual_MIDI_remote_control_control_elements.png|2|MIDI remote control configuration, control element|center}}
Since the first configuration at the simplest one with this one « MIDI Learn ». It is, is come in to the configuration here preferably in this way to make function. Changes can be carried out by hand later any time.
To the better overview one should which one give the control elements the name of the assigned control element as long as one still knows « New control element » which button heard. (One most simply leaves renaming, « enter key », with this one).
E.g. sensible Nammen would be fader 1, fader 2 etc. or button C, button C sharp etc. or Poti 1, Poti 2 etc.
The names one are subject to alteration, should, however, be chosen correspondingly so that it is known also after quite a long time still around which control elements.

===Configuring the command assignment===

{{Picture_with_subtitle |DMXC2_Manual_MIDI_remote_control_command_assignment.png|3|MIDI remote control configuration, command assignment|center}}

After the controller was included in the upper list and named completely, you can do this one order corresponding to control elements in the register rider command assignment assign now.

For the individual control elements every functionality can be chosen, it already is used of the keyboard control or the command box like you.

E. g. with the name ''Show1'' then passes the possibility of assigning a corresponding order to the individual control elements by production of a new bank, under module then becomes at all control elements « deactivates » shown. 
The individual table columns have following meaning and functions.
{|style="padding:20px;"
|- style="vertical-align:top;"
| style="text-align:right" | '''                 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:''' no module selected.

'''Audio:''' Using command on the module audio.

'''Audiotrack:''' Using command on the module Audio track player.

'''BeatTool:''' Using command on the module Beat Tool.

'''Chasers:''' Using command on the module Chaser.

'''Command line:''' Using command on the module Command line.

'''Command box:''' Using command on the module Command box.

'''Cue libary:''' Using command on the module Cue libary.

'''Cue list:''' Using command on the module Cue list.

'''Devices:''' Using command on the module Devices in the graphical view.

'''DMX output:''' Using command on the module DMX output.

'''DMXIn remote:''' Using command on the module DMXIn remote.

'''Group selection:''' Using command on the module Group selection.

'''Joystick:''' Using command on the module Joystick control.

'''Master:''' Using command on the module Master.

'''Midi Remote:''' Using command on the module Midi remote.

'''OSC receiver:''' Using command on the module OSC receiver.

'''Sound Analyzer:''' Using command on the module Sound analyzer.

'''Submaster:''' Using command on the module Submaster.

'''Textbook:''' Using command on the module Textbook.
|}
{{BoxHint
|Text = Plugins which support a control by the command box also seem additional here. This shall exemplarily be called MadMaxOne plugin here.
}}
{|style="padding:20px;"
|- style="vertical-align:top;"
| style="width: 110px; text-align:right" |   ||     || '''MadMaxOne Plug-In:''' Using command on the plugin MadMaxOne. 
|- style="vertical-align:top;"
| style="text-align:right" |'''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.
|- style="vertical-align:top;"
| style="text-align:right" | '''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.
|- style="vertical-align:top;"
| style="text-align:right" | '''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):''' With the T flag a button can be configured as on/off switch button.

'''Use specified value (O):''' With the O flag lets himself in, written down on the field, apply per cent value to the module/device.

'''Ask for value (A):''' With the A flag a value written down more petition tightly on it can be applied to the module/device. At the click on the configured button an input window in which the value can be entered opens.

'''Ignore value 0 (I):''' The handing over of a value of zero at not depressed button is ignored.
|- style="vertical-align:top;"
| style="text-align:right" | '''Value:''' ||     || By a click in this field a corresponding value can be deposited quickly for a device or a function.
|}
{{BoxHint
|Text = 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.
}}

==Controls==
The configuration of the control elements is carried out this one elements almost analogously [[DMXIn-Fernsteuerung_DMXC2|DMXIn control]] to this one. Every control element corresponds to a midi channel whose value is used for the configured order.

{| style="width:100%"
|-
!colspan="2" style="text-align:center"| Start the chaser !!colspan="2" style="text-align:center"| Stop the chaser !!colspan="2" style="text-align:center"| Start/Stop the chaser
|-
| style="text-align:right" | '''Module:''' || Chasers ||style="text-align:right"| '''Module:''' || Chasers ||style="text-align:right"| '''Module:''' || Chasers
|-
| style="text-align:right" | '''Device/Function:''' || Selected ||style="text-align:right"| '''Device/Function:''' || Selected ||style="text-align:right"| '''Device/Function:''' || Selected
|-
| style="text-align:right" | '''Channel:''' || Start ||style="text-align:right"| '''Channel:''' || Stop ||style="text-align:right"| '''Channel:''' || Start/Stop
|-
| style="text-align:right" | '''Flags:''' || -,-,-,- ||style="text-align:right"| '''Flags:''' || -,-,-,- ||style="text-align:right"| '''Flags:''' || T,-,-,-
|-
| style="text-align:right" | '''Value:''' || - ||style="text-align:right"| '''Value:''' || - ||style="text-align:right"| '''Value:''' || -
|}

==Module commands==

* Modul: '''MIDI remote'''

* Meaning from ''device/function'' and ''channel''
{| class="wikitable centered"
|- style="vertical-align:top;"
!style="width: 100px"| Device/Function
!style="width: 200px"| Description
!style="width: 100px"| Channel
!style="width: 200px"| Description
|- style="vertical-align:top;"
|style="width: 100px" rowspan="3"| Bank
|style="width: 200px" rowspan="3"| At choice of this function, there is the possibility of accessing the different benches about the command in the MIDI remote control.
|style="width: 100px"| Next
|style="width: 200px"| The next bank selects.
|- style="vertical-align:top;"
|style="width: 100px"| Previous
|style="width: 200px"| The previous bank selects.
|- style="vertical-align:top;"
|style="width: 100px"| Bank name
|style="width: 200px"| Direct choice of the defined benches about bank namens.
|}

Meaning of the ''Flags'':
{| class="wikitable centered"
|- style="vertical-align:top;"
! style="width: 35px"| Flag
! style="width: 105px"| Meaning
! style="width: 460px"| Description
|- style="vertical-align:top;"
| style="width: 35px; text-align:center"| T
| style="width: 105px"| Toggle mode
| style="width: 460px"| The Flag »''Toggle mode''« result in the function's being set by the first call and being reset by the second call.
|- style="vertical-align:top;"
| style="width: 35px; text-align:center"| O
| style="width: 105px"| Used specified value
| style="width: 460px"| 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%
|- style="vertical-align:top;"
| style="width: 35px; text-align:center"| A
| style="width: 105px"| Ask for value
| style="width: 460px"| 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.
|- style="vertical-align:top;"
| style="width: 35px; text-align:center"| I
| style="width: 105px"| Ignore value 0
| style="width: 460px"| 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)==

'''Flags:''' You click in this column, you a context menu is shown if two option in which or one can turn off: 
– Receive: Switch on this option if the MIDI order shall be processed at reception. 
– Send: Switch on this option if the MIDI order shall be sent if the corresponding value changes in the program. 

The banks are, stored the control elements however global in the project folder. You therefore should at a bill of exchange on another computer with the pile And go function provide it best this also gets this file changed on the new computer.

Be recommended can, the software midi OX, since one can test hereby whether the device also is attached also correctly and signals arrive in the PC. One can find the program here: of course one can http://www.midiox.com/zip/midioxse.exe test the function ability of the interface also with MIDI Sequencer programs.

One uses one a normal midi keyboard ("piano buttons") should so the buttons mark themselves with stickers best behind the buttons to know what one hides. The buttons should be covered structuredly, to this a small example:
One puts himself the first 4 sub-masters (e. g. ) headlights on the first 4 white buttons of the keyboard of the left. Perhaps one has effects run light (or the like) with these sub-masters (headlights) programmed, these effects are then put on the black buttons more than the first four white buttons. So one has the headlights manually in the handle and also can if necessary start a run light fast.
At all applications it is useful a button to cover himself with a proper blackout at least because sometimes this button is "gold worth" because one can thus immediately turn all headlights/scanners off. One should put the blackout on a button for example on the outermost right white button which one can remember well (or black button, because everything gets dark).

==Links and references==
<references/>
{{End-LaTeX}}
{{NavigationTop-Man2
| LinkBackwards = Joystick_control_DMXC2
| TextBackwards = Joystick control
| LinkForwards = DMXIn_remote_control_DMXC2
| TextForwards = DMXIn remote control
}}
[[de: MIDI-Fernsteuerung_DMXC2]]
[[Category: DMXControl 2]]

MIDI remote control DMXC2

2014-03-26T18:04:56Z

DominicjpgacgftlfToyama: /* The configuration window */

{{Chaptertitle_DMXC}} 
 
{{Hint|25.10.2013: UPrenner: create the article page 02.10.2013: UPrenner: work-in-progress 
02.02.2013: UPrenner article ready, just update of pictures 02.02.2013: UPrenner pictures updated 
'''If you are a native speaker, please Help us and review this
}} 
{{NavigationTop-Man2
| LinkBackwards = Joystick_control_DMXC2
| TextBackwards = Joystick control
| LinkForwards = DMXIn_remote_control_DMXC2
| TextForwards = DMXIn remote control
}}
{{Start-LaTeX}}
==Overview==
{{Picture_with_subtitle |DMXC2_Manual_MIDI_remote_control_activate.png|1|MIDI-Fernsteuerung|right}}
The MIDI remote control enables DMXControl to use MIDI protocol. Unlike the DMXIn remote control the MIDI remote control only uses a word size of 7 bits so that only values of 0 to 127 over the protocol are transferred.
Apart from little MIDI keyboards, there is the Behringer BCF2000 or BCR2000 as well as Korg nanoKONTROL 2 or Pioneer CDJ 350 also.
It is advisable to review the reference documentation here: Wikipedia <ref> MIDI on Wikipedia http://de.wikipedia.org/wiki/Musical_Instrument_Digital_Interface </ref>
 
 
 

==Description and configuration==

Some of the best known midi controllers are well:
* BCF2000/BCR2000 von Behringer <ref>BCF2000 http://www.behringer.com/de/Products/BCF2000.aspx </ref>
* Korg nanoKONTROL 2
* Pioneer CDJ-350

But also almost every keyboard (instrument) can be used with a MIDI input, or usb to midi interface.
MIDI devices which connect via USB also work.

The configuration files of the BCF2000 are shown in the pictures.

===The configuration window===
DMXControl needs to know about new MIDI interfaces. If your interface or device was not recognized on launch, you should enable it now.

Under the menu « Settings » choose configuration and choice of the corresponding MIDI device are carried out « MIDI remote control » here. If your device does not appear in the MIDI in/out port list then you should try reinstalling your device drivers.

At successful configuration and choice himself should in the lower part of the MIDI configuration window the advertisements at « Message: . . . Data 1: . . . Data 2: . . . » changing according to the operated MIDI control element at the MIDI device and MIDI code of the control element showing the corresponding ones.
If this works, you can devote themselves to the real configuration now.

{{BoxHint
|Text = It should be respected, however, on this that the subsequent configuration with « MIDI Learn » only work when the MIDI remote control is deactivated in between (see picture ''active voice'').
Furthermore a simultaneous use of the MIDI port of (a device) works together with another program (e. g. Winamp control about Xor MIDI Control) only the original (not Windows) drivers of the manufacturer (here: Fame).
}}

===Config of MIDI channel configuration===

{{Picture_with_subtitle |DMXC2_Manual_MIDI_remote_control_control_elements.png|2|MIDI remote control configuration, control element|center}}
Since the first configuration at the simplest one with this one « MIDI Learn ». It is, is come in to the configuration here preferably in this way to make function. Changes can be carried out by hand later any time.
To the better overview one should which one give the control elements the name of the assigned control element as long as one still knows « New control element » which button heard. (One most simply leaves renaming, « enter key », with this one).
E.g. sensible Nammen would be fader 1, fader 2 etc. or button C, button C sharp etc. or Poti 1, Poti 2 etc.
The names one are subject to alteration, should, however, be chosen correspondingly so that it is known also after quite a long time still around which control elements.

===Configuring the command assignment===

{{Picture_with_subtitle |DMXC2_Manual_MIDI_remote_control_command_assignment.png|3|MIDI remote control configuration, command assignment|center}}

After the controller was included in the upper list and named completely, you can do this one order corresponding to control elements in the register rider command assignment assign now.

For the individual control elements every functionality can be chosen, it already is used of the keyboard control or the command box like you.

E. g. with the name ''Show1'' then passes the possibility of assigning a corresponding order to the individual control elements by production of a new bank, under module then becomes at all control elements « deactivates » shown. 
The individual table columns have following meaning and functions.
{|style="padding:20px;"
|- style="vertical-align:top;"
| style="text-align:right" | '''                 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:''' no module selected.

'''Audio:''' Using command on the module audio.

'''Audiotrack:''' Using command on the module Audio track player.

'''BeatTool:''' Using command on the module Beat Tool.

'''Chasers:''' Using command on the module Chaser.

'''Command line:''' Using command on the module Command line.

'''Command box:''' Using command on the module Command box.

'''Cue libary:''' Using command on the module Cue libary.

'''Cue list:''' Using command on the module Cue list.

'''Devices:''' Using command on the module Devices in the graphical view.

'''DMX output:''' Using command on the module DMX output.

'''DMXIn remote:''' Using command on the module DMXIn remote.

'''Group selection:''' Using command on the module Group selection.

'''Joystick:''' Using command on the module Joystick control.

'''Master:''' Using command on the module Master.

'''Midi Remote:''' Using command on the module Midi remote.

'''OSC receiver:''' Using command on the module OSC receiver.

'''Sound Analyzer:''' Using command on the module Sound analyzer.

'''Submaster:''' Using command on the module Submaster.

'''Textbook:''' Using command on the module Textbook.
|}
{{BoxHint
|Text = Plugins which support a control by the command box also seem additional here. This shall exemplarily be called MadMaxOne plugin here.
}}
{|style="padding:20px;"
|- style="vertical-align:top;"
| style="width: 110px; text-align:right" |   ||     || '''MadMaxOne Plug-In:''' Using command on the plugin MadMaxOne. 
|- style="vertical-align:top;"
| style="text-align:right" |'''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.
|- style="vertical-align:top;"
| style="text-align:right" | '''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.
|- style="vertical-align:top;"
| style="text-align:right" | '''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):''' With the T flag a button can be configured as on/off switch button.

'''Use specified value (O):''' With the O flag lets himself in, written down on the field, apply per cent value to the module/device.

'''Ask for value (A):''' With the A flag a value written down more petition tightly on it can be applied to the module/device. At the click on the configured button an input window in which the value can be entered opens.

'''Ignore value 0 (I):''' The handing over of a value of zero at not depressed button is ignored.
|- style="vertical-align:top;"
| style="text-align:right" | '''Value:''' ||     || By a click in this field a corresponding value can be deposited quickly for a device or a function.
|}
{{BoxHint
|Text = 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.
}}

==Controls==
The configuration of the control elements is carried out this one elements almost analogously [[DMXIn-Fernsteuerung_DMXC2|DMXIn control]] to this one. Every control element corresponds to a midi channel whose value is used for the configured order.

{| style="width:100%"
|-
!colspan="2" style="text-align:center"| Start the chaser !!colspan="2" style="text-align:center"| Stop the chaser !!colspan="2" style="text-align:center"| Start/Stop the chaser
|-
| style="text-align:right" | '''Module:''' || Chasers ||style="text-align:right"| '''Module:''' || Chasers ||style="text-align:right"| '''Module:''' || Chasers
|-
| style="text-align:right" | '''Device/Function:''' || Selected ||style="text-align:right"| '''Device/Function:''' || Selected ||style="text-align:right"| '''Device/Function:''' || Selected
|-
| style="text-align:right" | '''Channel:''' || Start ||style="text-align:right"| '''Channel:''' || Stop ||style="text-align:right"| '''Channel:''' || Start/Stop
|-
| style="text-align:right" | '''Flags:''' || -,-,-,- ||style="text-align:right"| '''Flags:''' || -,-,-,- ||style="text-align:right"| '''Flags:''' || T,-,-,-
|-
| style="text-align:right" | '''Value:''' || - ||style="text-align:right"| '''Value:''' || - ||style="text-align:right"| '''Value:''' || -
|}

==Module commands==

* Modul: '''MIDI remote'''

* Meaning from ''device/function'' and ''channel''
{| class="wikitable centered"
|- style="vertical-align:top;"
!style="width: 100px"| Device/Function
!style="width: 200px"| Description
!style="width: 100px"| Channel
!style="width: 200px"| Description
|- style="vertical-align:top;"
|style="width: 100px" rowspan="3"| Bank
|style="width: 200px" rowspan="3"| At choice of this function, there is the possibility of accessing the different benches about the command in the MIDI remote control.
|style="width: 100px"| Next
|style="width: 200px"| The next bank selects.
|- style="vertical-align:top;"
|style="width: 100px"| Previous
|style="width: 200px"| The previous bank selects.
|- style="vertical-align:top;"
|style="width: 100px"| Bank name
|style="width: 200px"| Direct choice of the defined benches about bank namens.
|}

Meaning of the ''Flags'':
{| class="wikitable centered"
|- style="vertical-align:top;"
! style="width: 35px"| Flag
! style="width: 105px"| Meaning
! style="width: 460px"| Description
|- style="vertical-align:top;"
| style="width: 35px; text-align:center"| T
| style="width: 105px"| Toggle mode
| style="width: 460px"| The Flag »''Toggle mode''« result in the function's being set by the first call and being reset by the second call.
|- style="vertical-align:top;"
| style="width: 35px; text-align:center"| O
| style="width: 105px"| Used specified value
| style="width: 460px"| 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%
|- style="vertical-align:top;"
| style="width: 35px; text-align:center"| A
| style="width: 105px"| Ask for value
| style="width: 460px"| 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.
|- style="vertical-align:top;"
| style="width: 35px; text-align:center"| I
| style="width: 105px"| Ignore value 0
| style="width: 460px"| 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)==

'''Flags:''' You click in this column, you a context menu is shown if two option in which or one can turn off: 
– Receive: Switch on this option if the MIDI order shall be processed at reception. 
– Send: Switch on this option if the MIDI order shall be sent if the corresponding value changes in the program. 

The banks are, stored the control elements however global in the project folder. You therefore should at a bill of exchange on another computer with the pile And go function provide it best this also gets this file changed on the new computer.

Be recommended can, the software midi OX, since one can test hereby whether the device also is attached also correctly and signals arrive in the PC. One can find the program here: of course one can http://www.midiox.com/zip/midioxse.exe test the function ability of the interface also with MIDI Sequencer programs.

One uses one a normal midi keyboard ("piano buttons") should so the buttons mark themselves with stickers best behind the buttons to know what one hides. The buttons should be covered structuredly, to this a small example:
One puts himself the first 4 sub-masters (e. g. ) headlights on the first 4 white buttons of the keyboard of the left. Perhaps one has effects run light (or the like) with these sub-masters (headlights) programmed, these effects are then put on the black buttons more than the first four white buttons. So one has the headlights manually in the handle and also can if necessary start a run light fast.
At all applications it is useful a button to cover himself with a proper blackout at least because sometimes this button is "gold worth" because one can thus immediately turn all headlights/scanners off. One should put the blackout on a button for example on the outermost right white button which one can remember well (or black button, because everything gets dark).

==Links and references==
<references/>
{{End-LaTeX}}
{{NavigationTop-Man2
| LinkBackwards = Joystick_control_DMXC2
| TextBackwards = Joystick control
| LinkForwards = DMXIn_remote_control_DMXC2
| TextForwards = DMXIn remote control
}}
[[de: MIDI-Fernsteuerung_DMXC2]]
[[Category: DMXControl 2]]

MIDI remote control DMXC2

2014-03-25T16:35:29Z

DominicjpgacgftlfToyama: /* Description and configuration */

{{Chaptertitle_DMXC}} 
 
{{Hint|25.10.2013: UPrenner: create the article page 02.10.2013: UPrenner: work-in-progress 
02.02.2013: UPrenner article ready, just update of pictures 02.02.2013: UPrenner pictures updated 
'''If you are a native speaker, please Help us and review this
}} 
{{NavigationTop-Man2
| LinkBackwards = Joystick_control_DMXC2
| TextBackwards = Joystick control
| LinkForwards = DMXIn_remote_control_DMXC2
| TextForwards = DMXIn remote control
}}
{{Start-LaTeX}}
==Overview==
{{Picture_with_subtitle |DMXC2_Manual_MIDI_remote_control_activate.png|1|MIDI-Fernsteuerung|right}}
The MIDI remote control enables DMXControl to use MIDI protocol. Unlike the DMXIn remote control the MIDI remote control only uses a word size of 7 bits so that only values of 0 to 127 over the protocol are transferred.
Apart from little MIDI keyboards, there is the Behringer BCF2000 or BCR2000 as well as Korg nanoKONTROL 2 or Pioneer CDJ 350 also.
It is advisable to review the reference documentation here: Wikipedia <ref> MIDI on Wikipedia http://de.wikipedia.org/wiki/Musical_Instrument_Digital_Interface </ref>
 
 
 

==Description and configuration==

Some of the best known midi controllers are well:
* BCF2000/BCR2000 von Behringer <ref>BCF2000 http://www.behringer.com/de/Products/BCF2000.aspx </ref>
* Korg nanoKONTROL 2
* Pioneer CDJ-350

But also almost every keyboard (instrument) can be used with a MIDI input, or usb to midi interface.
MIDI devices which connect via USB also work.

The configuration files of the BCF2000 are shown in the pictures.

===The configuration window===
DMXControl needs to know about new MIDI interfaces. If your interface or device was not recognized on launch, you should enable it now.

Under the menu « Settings » choose configuration and choice of the corresponding MIDI device are carried out « MIDI remote control » here. Should under MIDI be no device had a choice by into port and MIDI out port, the drivers then weren't apparently installed correctly.

At successful configuration and choice himself should in the lower part of the MIDI configuration window the advertisements at « Message: . . . Data 1: . . . Data 2: . . . » changing according to the operated MIDI control element at the MIDI device and MIDI code of the control element showing the corresponding ones.
If this works, you can devote themselves to the real configuration now.

{{BoxHint
|Text = It should be respected, however, on this that the subsequent configuration with « MIDI Learn » only work when the MIDI remote control is deactivated in between (see picture ''active voice'').
Furthermore a simultaneous use of the MIDI port of (a device) works together with another program (e. g. Winamp control about Xor MIDI Control) only the original (not Windows) drivers of the manufacturer (here: Fame).
}}

===Config of MIDI channel configuration===

{{Picture_with_subtitle |DMXC2_Manual_MIDI_remote_control_control_elements.png|2|MIDI remote control configuration, control element|center}}
Since the first configuration at the simplest one with this one « MIDI Learn ». It is, is come in to the configuration here preferably in this way to make function. Changes can be carried out by hand later any time.
To the better overview one should which one give the control elements the name of the assigned control element as long as one still knows « New control element » which button heard. (One most simply leaves renaming, « enter key », with this one).
E.g. sensible Nammen would be fader 1, fader 2 etc. or button C, button C sharp etc. or Poti 1, Poti 2 etc.
The names one are subject to alteration, should, however, be chosen correspondingly so that it is known also after quite a long time still around which control elements.

===Configuring the command assignment===

{{Picture_with_subtitle |DMXC2_Manual_MIDI_remote_control_command_assignment.png|3|MIDI remote control configuration, command assignment|center}}

After the controller was included in the upper list and named completely, you can do this one order corresponding to control elements in the register rider command assignment assign now.

For the individual control elements every functionality can be chosen, it already is used of the keyboard control or the command box like you.

E. g. with the name ''Show1'' then passes the possibility of assigning a corresponding order to the individual control elements by production of a new bank, under module then becomes at all control elements « deactivates » shown. 
The individual table columns have following meaning and functions.
{|style="padding:20px;"
|- style="vertical-align:top;"
| style="text-align:right" | '''                 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:''' no module selected.

'''Audio:''' Using command on the module audio.

'''Audiotrack:''' Using command on the module Audio track player.

'''BeatTool:''' Using command on the module Beat Tool.

'''Chasers:''' Using command on the module Chaser.

'''Command line:''' Using command on the module Command line.

'''Command box:''' Using command on the module Command box.

'''Cue libary:''' Using command on the module Cue libary.

'''Cue list:''' Using command on the module Cue list.

'''Devices:''' Using command on the module Devices in the graphical view.

'''DMX output:''' Using command on the module DMX output.

'''DMXIn remote:''' Using command on the module DMXIn remote.

'''Group selection:''' Using command on the module Group selection.

'''Joystick:''' Using command on the module Joystick control.

'''Master:''' Using command on the module Master.

'''Midi Remote:''' Using command on the module Midi remote.

'''OSC receiver:''' Using command on the module OSC receiver.

'''Sound Analyzer:''' Using command on the module Sound analyzer.

'''Submaster:''' Using command on the module Submaster.

'''Textbook:''' Using command on the module Textbook.
|}
{{BoxHint
|Text = Plugins which support a control by the command box also seem additional here. This shall exemplarily be called MadMaxOne plugin here.
}}
{|style="padding:20px;"
|- style="vertical-align:top;"
| style="width: 110px; text-align:right" |   ||     || '''MadMaxOne Plug-In:''' Using command on the plugin MadMaxOne. 
|- style="vertical-align:top;"
| style="text-align:right" |'''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.
|- style="vertical-align:top;"
| style="text-align:right" | '''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.
|- style="vertical-align:top;"
| style="text-align:right" | '''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):''' With the T flag a button can be configured as on/off switch button.

'''Use specified value (O):''' With the O flag lets himself in, written down on the field, apply per cent value to the module/device.

'''Ask for value (A):''' With the A flag a value written down more petition tightly on it can be applied to the module/device. At the click on the configured button an input window in which the value can be entered opens.

'''Ignore value 0 (I):''' The handing over of a value of zero at not depressed button is ignored.
|- style="vertical-align:top;"
| style="text-align:right" | '''Value:''' ||     || By a click in this field a corresponding value can be deposited quickly for a device or a function.
|}
{{BoxHint
|Text = 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.
}}

==Controls==
The configuration of the control elements is carried out this one elements almost analogously [[DMXIn-Fernsteuerung_DMXC2|DMXIn control]] to this one. Every control element corresponds to a midi channel whose value is used for the configured order.

{| style="width:100%"
|-
!colspan="2" style="text-align:center"| Start the chaser !!colspan="2" style="text-align:center"| Stop the chaser !!colspan="2" style="text-align:center"| Start/Stop the chaser
|-
| style="text-align:right" | '''Module:''' || Chasers ||style="text-align:right"| '''Module:''' || Chasers ||style="text-align:right"| '''Module:''' || Chasers
|-
| style="text-align:right" | '''Device/Function:''' || Selected ||style="text-align:right"| '''Device/Function:''' || Selected ||style="text-align:right"| '''Device/Function:''' || Selected
|-
| style="text-align:right" | '''Channel:''' || Start ||style="text-align:right"| '''Channel:''' || Stop ||style="text-align:right"| '''Channel:''' || Start/Stop
|-
| style="text-align:right" | '''Flags:''' || -,-,-,- ||style="text-align:right"| '''Flags:''' || -,-,-,- ||style="text-align:right"| '''Flags:''' || T,-,-,-
|-
| style="text-align:right" | '''Value:''' || - ||style="text-align:right"| '''Value:''' || - ||style="text-align:right"| '''Value:''' || -
|}

==Module commands==

* Modul: '''MIDI remote'''

* Meaning from ''device/function'' and ''channel''
{| class="wikitable centered"
|- style="vertical-align:top;"
!style="width: 100px"| Device/Function
!style="width: 200px"| Description
!style="width: 100px"| Channel
!style="width: 200px"| Description
|- style="vertical-align:top;"
|style="width: 100px" rowspan="3"| Bank
|style="width: 200px" rowspan="3"| At choice of this function, there is the possibility of accessing the different benches about the command in the MIDI remote control.
|style="width: 100px"| Next
|style="width: 200px"| The next bank selects.
|- style="vertical-align:top;"
|style="width: 100px"| Previous
|style="width: 200px"| The previous bank selects.
|- style="vertical-align:top;"
|style="width: 100px"| Bank name
|style="width: 200px"| Direct choice of the defined benches about bank namens.
|}

Meaning of the ''Flags'':
{| class="wikitable centered"
|- style="vertical-align:top;"
! style="width: 35px"| Flag
! style="width: 105px"| Meaning
! style="width: 460px"| Description
|- style="vertical-align:top;"
| style="width: 35px; text-align:center"| T
| style="width: 105px"| Toggle mode
| style="width: 460px"| The Flag »''Toggle mode''« result in the function's being set by the first call and being reset by the second call.
|- style="vertical-align:top;"
| style="width: 35px; text-align:center"| O
| style="width: 105px"| Used specified value
| style="width: 460px"| 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%
|- style="vertical-align:top;"
| style="width: 35px; text-align:center"| A
| style="width: 105px"| Ask for value
| style="width: 460px"| 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.
|- style="vertical-align:top;"
| style="width: 35px; text-align:center"| I
| style="width: 105px"| Ignore value 0
| style="width: 460px"| 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)==

'''Flags:''' You click in this column, you a context menu is shown if two option in which or one can turn off: 
– Receive: Switch on this option if the MIDI order shall be processed at reception. 
– Send: Switch on this option if the MIDI order shall be sent if the corresponding value changes in the program. 

The banks are, stored the control elements however global in the project folder. You therefore should at a bill of exchange on another computer with the pile And go function provide it best this also gets this file changed on the new computer.

Be recommended can, the software midi OX, since one can test hereby whether the device also is attached also correctly and signals arrive in the PC. One can find the program here: of course one can http://www.midiox.com/zip/midioxse.exe test the function ability of the interface also with MIDI Sequencer programs.

One uses one a normal midi keyboard ("piano buttons") should so the buttons mark themselves with stickers best behind the buttons to know what one hides. The buttons should be covered structuredly, to this a small example:
One puts himself the first 4 sub-masters (e. g. ) headlights on the first 4 white buttons of the keyboard of the left. Perhaps one has effects run light (or the like) with these sub-masters (headlights) programmed, these effects are then put on the black buttons more than the first four white buttons. So one has the headlights manually in the handle and also can if necessary start a run light fast.
At all applications it is useful a button to cover himself with a proper blackout at least because sometimes this button is "gold worth" because one can thus immediately turn all headlights/scanners off. One should put the blackout on a button for example on the outermost right white button which one can remember well (or black button, because everything gets dark).

==Links and references==
<references/>
{{End-LaTeX}}
{{NavigationTop-Man2
| LinkBackwards = Joystick_control_DMXC2
| TextBackwards = Joystick control
| LinkForwards = DMXIn_remote_control_DMXC2
| TextForwards = DMXIn remote control
}}
[[de: MIDI-Fernsteuerung_DMXC2]]
[[Category: DMXControl 2]]

MIDI remote control DMXC2

2014-03-25T16:29:54Z

DominicjpgacgftlfToyama: /* Overview */

{{Chaptertitle_DMXC}} 
 
{{Hint|25.10.2013: UPrenner: create the article page 02.10.2013: UPrenner: work-in-progress 
02.02.2013: UPrenner article ready, just update of pictures 02.02.2013: UPrenner pictures updated 
'''If you are a native speaker, please Help us and review this
}} 
{{NavigationTop-Man2
| LinkBackwards = Joystick_control_DMXC2
| TextBackwards = Joystick control
| LinkForwards = DMXIn_remote_control_DMXC2
| TextForwards = DMXIn remote control
}}
{{Start-LaTeX}}
==Overview==
{{Picture_with_subtitle |DMXC2_Manual_MIDI_remote_control_activate.png|1|MIDI-Fernsteuerung|right}}
The MIDI remote control enables DMXControl to use MIDI protocol. Unlike the DMXIn remote control the MIDI remote control only uses a word size of 7 bits so that only values of 0 to 127 over the protocol are transferred.
Apart from little MIDI keyboards, there is the Behringer BCF2000 or BCR2000 as well as Korg nanoKONTROL 2 or Pioneer CDJ 350 also.
It is advisable to review the reference documentation here: Wikipedia <ref> MIDI on Wikipedia http://de.wikipedia.org/wiki/Musical_Instrument_Digital_Interface </ref>
 
 
 

==Description and configuration==

Some of the best known midi controllers are well:
* BCF2000/BCR2000 von Behringer <ref>BCF2000 http://www.behringer.com/de/Products/BCF2000.aspx </ref>
* Korg nanoKONTROL 2
* Pioneer CDJ-350

But also almost every keyboard (instrument) can be used with a sound card with MIDI entrance at the computer for steering DMXControl of software like here.
There alternatively are MIDI keyboards as of 40 euros nowadays which can be attached directly by USB to the computer.

The configuration files of the BCF2000 exemplarily are shown in the pictures.

Generally, every higher-order sound card already shows a MIDI interface so that this can get connected to e. g. a musical instrument (keyboard) and can get misused as a MIDI controller at the card behind.

===The configuration window===
DMXControl needs to recognize new MIDI interfaces, shouldn't these been at the start of the program not switched on yet be started newly be.

Under the menu « Settings » the menu item finds you the configuration and choice of the corresponding MIDI device are carried out « MIDI remote control » here. Should under MIDI be no device had a choice by into port and MIDI out port, the drivers then weren't apparently installed correctly.

At successful configuration and choice himself should in the lower part of the MIDI configuration window the advertisements at « Message: . . . Data 1: . . . Data 2: . . . » changing according to the operated MIDI control element at the MIDI device and MIDI code of the control element showing the corresponding ones.
If this works, you can devote themselves to the real configuration now.

{{BoxHint
|Text = It should be respected, however, on this that the subsequent configuration with « MIDI Learn » only work when the MIDI remote control is deactivated in between (see picture ''active voice'').
Furthermore a simultaneous use of the MIDI port of (a device) works together with another program (e. g. Winamp control about Xor MIDI Control) only the original (not Windows) drivers of the manufacturer (here: Fame).
}}

===Config of MIDI channel configuration===

{{Picture_with_subtitle |DMXC2_Manual_MIDI_remote_control_control_elements.png|2|MIDI remote control configuration, control element|center}}
Since the first configuration at the simplest one with this one « MIDI Learn ». It is, is come in to the configuration here preferably in this way to make function. Changes can be carried out by hand later any time.
To the better overview one should which one give the control elements the name of the assigned control element as long as one still knows « New control element » which button heard. (One most simply leaves renaming, « enter key », with this one).
E.g. sensible Nammen would be fader 1, fader 2 etc. or button C, button C sharp etc. or Poti 1, Poti 2 etc.
The names one are subject to alteration, should, however, be chosen correspondingly so that it is known also after quite a long time still around which control elements.

===Configuring the command assignment===

{{Picture_with_subtitle |DMXC2_Manual_MIDI_remote_control_command_assignment.png|3|MIDI remote control configuration, command assignment|center}}

After the controller was included in the upper list and named completely, you can do this one order corresponding to control elements in the register rider command assignment assign now.

For the individual control elements every functionality can be chosen, it already is used of the keyboard control or the command box like you.

E. g. with the name ''Show1'' then passes the possibility of assigning a corresponding order to the individual control elements by production of a new bank, under module then becomes at all control elements « deactivates » shown. 
The individual table columns have following meaning and functions.
{|style="padding:20px;"
|- style="vertical-align:top;"
| style="text-align:right" | '''                 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:''' no module selected.

'''Audio:''' Using command on the module audio.

'''Audiotrack:''' Using command on the module Audio track player.

'''BeatTool:''' Using command on the module Beat Tool.

'''Chasers:''' Using command on the module Chaser.

'''Command line:''' Using command on the module Command line.

'''Command box:''' Using command on the module Command box.

'''Cue libary:''' Using command on the module Cue libary.

'''Cue list:''' Using command on the module Cue list.

'''Devices:''' Using command on the module Devices in the graphical view.

'''DMX output:''' Using command on the module DMX output.

'''DMXIn remote:''' Using command on the module DMXIn remote.

'''Group selection:''' Using command on the module Group selection.

'''Joystick:''' Using command on the module Joystick control.

'''Master:''' Using command on the module Master.

'''Midi Remote:''' Using command on the module Midi remote.

'''OSC receiver:''' Using command on the module OSC receiver.

'''Sound Analyzer:''' Using command on the module Sound analyzer.

'''Submaster:''' Using command on the module Submaster.

'''Textbook:''' Using command on the module Textbook.
|}
{{BoxHint
|Text = Plugins which support a control by the command box also seem additional here. This shall exemplarily be called MadMaxOne plugin here.
}}
{|style="padding:20px;"
|- style="vertical-align:top;"
| style="width: 110px; text-align:right" |   ||     || '''MadMaxOne Plug-In:''' Using command on the plugin MadMaxOne. 
|- style="vertical-align:top;"
| style="text-align:right" |'''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.
|- style="vertical-align:top;"
| style="text-align:right" | '''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.
|- style="vertical-align:top;"
| style="text-align:right" | '''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):''' With the T flag a button can be configured as on/off switch button.

'''Use specified value (O):''' With the O flag lets himself in, written down on the field, apply per cent value to the module/device.

'''Ask for value (A):''' With the A flag a value written down more petition tightly on it can be applied to the module/device. At the click on the configured button an input window in which the value can be entered opens.

'''Ignore value 0 (I):''' The handing over of a value of zero at not depressed button is ignored.
|- style="vertical-align:top;"
| style="text-align:right" | '''Value:''' ||     || By a click in this field a corresponding value can be deposited quickly for a device or a function.
|}
{{BoxHint
|Text = 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.
}}

==Controls==
The configuration of the control elements is carried out this one elements almost analogously [[DMXIn-Fernsteuerung_DMXC2|DMXIn control]] to this one. Every control element corresponds to a midi channel whose value is used for the configured order.

{| style="width:100%"
|-
!colspan="2" style="text-align:center"| Start the chaser !!colspan="2" style="text-align:center"| Stop the chaser !!colspan="2" style="text-align:center"| Start/Stop the chaser
|-
| style="text-align:right" | '''Module:''' || Chasers ||style="text-align:right"| '''Module:''' || Chasers ||style="text-align:right"| '''Module:''' || Chasers
|-
| style="text-align:right" | '''Device/Function:''' || Selected ||style="text-align:right"| '''Device/Function:''' || Selected ||style="text-align:right"| '''Device/Function:''' || Selected
|-
| style="text-align:right" | '''Channel:''' || Start ||style="text-align:right"| '''Channel:''' || Stop ||style="text-align:right"| '''Channel:''' || Start/Stop
|-
| style="text-align:right" | '''Flags:''' || -,-,-,- ||style="text-align:right"| '''Flags:''' || -,-,-,- ||style="text-align:right"| '''Flags:''' || T,-,-,-
|-
| style="text-align:right" | '''Value:''' || - ||style="text-align:right"| '''Value:''' || - ||style="text-align:right"| '''Value:''' || -
|}

==Module commands==

* Modul: '''MIDI remote'''

* Meaning from ''device/function'' and ''channel''
{| class="wikitable centered"
|- style="vertical-align:top;"
!style="width: 100px"| Device/Function
!style="width: 200px"| Description
!style="width: 100px"| Channel
!style="width: 200px"| Description
|- style="vertical-align:top;"
|style="width: 100px" rowspan="3"| Bank
|style="width: 200px" rowspan="3"| At choice of this function, there is the possibility of accessing the different benches about the command in the MIDI remote control.
|style="width: 100px"| Next
|style="width: 200px"| The next bank selects.
|- style="vertical-align:top;"
|style="width: 100px"| Previous
|style="width: 200px"| The previous bank selects.
|- style="vertical-align:top;"
|style="width: 100px"| Bank name
|style="width: 200px"| Direct choice of the defined benches about bank namens.
|}

Meaning of the ''Flags'':
{| class="wikitable centered"
|- style="vertical-align:top;"
! style="width: 35px"| Flag
! style="width: 105px"| Meaning
! style="width: 460px"| Description
|- style="vertical-align:top;"
| style="width: 35px; text-align:center"| T
| style="width: 105px"| Toggle mode
| style="width: 460px"| The Flag »''Toggle mode''« result in the function's being set by the first call and being reset by the second call.
|- style="vertical-align:top;"
| style="width: 35px; text-align:center"| O
| style="width: 105px"| Used specified value
| style="width: 460px"| 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%
|- style="vertical-align:top;"
| style="width: 35px; text-align:center"| A
| style="width: 105px"| Ask for value
| style="width: 460px"| 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.
|- style="vertical-align:top;"
| style="width: 35px; text-align:center"| I
| style="width: 105px"| Ignore value 0
| style="width: 460px"| 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)==

'''Flags:''' You click in this column, you a context menu is shown if two option in which or one can turn off: 
– Receive: Switch on this option if the MIDI order shall be processed at reception. 
– Send: Switch on this option if the MIDI order shall be sent if the corresponding value changes in the program. 

The banks are, stored the control elements however global in the project folder. You therefore should at a bill of exchange on another computer with the pile And go function provide it best this also gets this file changed on the new computer.

Be recommended can, the software midi OX, since one can test hereby whether the device also is attached also correctly and signals arrive in the PC. One can find the program here: of course one can http://www.midiox.com/zip/midioxse.exe test the function ability of the interface also with MIDI Sequencer programs.

One uses one a normal midi keyboard ("piano buttons") should so the buttons mark themselves with stickers best behind the buttons to know what one hides. The buttons should be covered structuredly, to this a small example:
One puts himself the first 4 sub-masters (e. g. ) headlights on the first 4 white buttons of the keyboard of the left. Perhaps one has effects run light (or the like) with these sub-masters (headlights) programmed, these effects are then put on the black buttons more than the first four white buttons. So one has the headlights manually in the handle and also can if necessary start a run light fast.
At all applications it is useful a button to cover himself with a proper blackout at least because sometimes this button is "gold worth" because one can thus immediately turn all headlights/scanners off. One should put the blackout on a button for example on the outermost right white button which one can remember well (or black button, because everything gets dark).

==Links and references==
<references/>
{{End-LaTeX}}
{{NavigationTop-Man2
| LinkBackwards = Joystick_control_DMXC2
| TextBackwards = Joystick control
| LinkForwards = DMXIn_remote_control_DMXC2
| TextForwards = DMXIn remote control
}}
[[de: MIDI-Fernsteuerung_DMXC2]]
[[Category: DMXControl 2]]

Devices DMXC2

2014-03-25T15:49:36Z

DominicjpgacgftlfToyama: /* Description */

{{Chaptertitle_DMXC}} 

{{Hint|20.5.2013: JKuehn: create the article page 24.10.2013: work-in-progress by UPrenner 
24.10.2013: UPrenner article ready, just update of pictures 
06.01.2013: UPrenner: update of pictures done '''If you are a native speaker, please Help us and review this article
}} 
{{NavigationTop-Man2
| LinkBackwards = Graphical_view_DMXC2
| TextBackwards = Graphical view
| LinkForwards = Output_plugins_DMXC2
| TextForwards = Output plugins
}}
{{Start-LaTeX}}
==Overview==
The device list contains all devices ([[Glossar_DMXC2#DDF|DDF's]]) used in the project, and lists them with several associated parameters.
{{Picture_with_subtitle |DMXC2_Manual_device_list_window.png|1|Device list|center}}
 

==Description==

The most important aspect of a dmx show is the available equipment as well as their position in the DMX universe [[graphical_ view_DMXC2|graphical view]] The list is column based and sortable. The device list can also be copied to clipboard.

The device names can be renamed, and the DMX address can be set (either in the decimal or binary system).
In addition, the x and y positions are shown, in case these are unclear in the graphic stage view.

Further configuration of each device can be set by pressing « Configure » after highlighting a device in the window. A detailed description can be found in the ''chapter 4 graphic one stage view''.

Adding equipment is done by pressing the button « Add ».

==Color and Gobo lists==

DMXControl also provides the possibility of working with Color and Gobo lists. One can lay out different lists for a different devices or also at scanners and movingheads which these have exchanged colors or gobos for themselves which then are assigned to the device. The advantage is that one doesn't have to change the device definition file every time but can assign the new colors or Gobos via the Color and Gobo lists.

The construction of a Color or Gobo list new to one is carried out in the menu « Configuration » with the two menu items « Color lists » and « Gobo lists » The assignment of the prepared lists is, in which, at the corresponding points which Color or Gobo list select by drop down carried out one in the device configuration.

Also have to the function be input for Color and Gobo lists in the corresponding device definition file so that the whole also really works.

{{End-LaTeX}}
{{NavigationTop-Man2
| LinkBackwards = Graphical_view_DMXC2
| TextBackwards = Graphical view
| LinkForwards = Output_plugins_DMXC2
| TextForwards = Output plugins
}}
[[de: Geräte_DMXC2]]
[[Category: DMXControl 2]]

Devices DMXC2

2014-03-25T15:42:25Z

DominicjpgacgftlfToyama: /* Overview */

{{Chaptertitle_DMXC}} 

{{Hint|20.5.2013: JKuehn: create the article page 24.10.2013: work-in-progress by UPrenner 
24.10.2013: UPrenner article ready, just update of pictures 
06.01.2013: UPrenner: update of pictures done '''If you are a native speaker, please Help us and review this article
}} 
{{NavigationTop-Man2
| LinkBackwards = Graphical_view_DMXC2
| TextBackwards = Graphical view
| LinkForwards = Output_plugins_DMXC2
| TextForwards = Output plugins
}}
{{Start-LaTeX}}
==Overview==
The device list contains all devices ([[Glossar_DMXC2#DDF|DDF's]]) used in the project, and lists them with several associated parameters.
{{Picture_with_subtitle |DMXC2_Manual_device_list_window.png|1|Device list|center}}
 

==Description==

The most important data of everyone already become available equipment as well as their graphic position on the [[graphical_ view_DMXC2|graphical view]] shown in the device list (figure 1) in the project. The data are column-wise arbitrarily sortable. The device list lets himself exclusively over the menu « Window » Menu item « Device » calls and can over the button « Copy to clipboard » be copied as tab-separate text into the intermediate file to be used further so in other programs.

The device names can be renamed to the better re-reconnaissance and the DMX address can comfortably in the decimal and be binary system entered (DIP switch).
In addition, have the x and y positions of the icons read in the graphic stage view to themselves. Should these are untraceable on the graphic stage view.

Further attitudes of the device selected can over the button « Configure » at highlighted equipment over the window « Configure device » being carried out. A detailed description is in the ''chapter 4 graphic one stage view''.

Adding equipment is carried out via the button « Add », in which himself as in the case of the graphical view the window « Add device » opens.

==Color and Gobo lists==

DMXControl also provides the possibility of working with Color and Gobo lists. One can lay out different lists for a different devices or also at scanners and movingheads which these have exchanged colors or gobos for themselves which then are assigned to the device. The advantage is that one doesn't have to change the device definition file every time but can assign the new colors or Gobos via the Color and Gobo lists.

The construction of a Color or Gobo list new to one is carried out in the menu « Configuration » with the two menu items « Color lists » and « Gobo lists » The assignment of the prepared lists is, in which, at the corresponding points which Color or Gobo list select by drop down carried out one in the device configuration.

Also have to the function be input for Color and Gobo lists in the corresponding device definition file so that the whole also really works.

{{End-LaTeX}}
{{NavigationTop-Man2
| LinkBackwards = Graphical_view_DMXC2
| TextBackwards = Graphical view
| LinkForwards = Output_plugins_DMXC2
| TextForwards = Output plugins
}}
[[de: Geräte_DMXC2]]
[[Category: DMXControl 2]]