(exe) Remote MIDI Mapper

[Durisian]

Here's a first look at Remote MIDI Mapper.

At the moment there are 2 sections, Continuous Control and Script Trigger.
Continuous Control takes a MIDI Controller and maps it to a channel on the console. Commuication can be in either or both directions. Although tramitting MIDI based on a console channel will be lagging and most likely error prone (you can alter the channel refresh rate in the options).
Definately not accurate - MIDI has 128 possible values (comapred to DMX's 256). for simplicity - the steps are are converted to channel percentage when recieving midi - and same vice versa , the percentage is converted to 0-127. (is there a way to get the dmx value for a bunch of channels at the same time?)

Script Trigger sends a Lua command to the console when a given MIDI event is recieved.

to do - field testing , continuous look control and translation of MIDI Show Control (if anyone has the 1.1 spec, please pm me )

Install -
Will not work on a console. Needs to run remotely for MIDI Interface access.
unzip to a suitable location and run RMM.exe
I used the C# MIDI Toolkit by Leslie Sanford to provide easy access to windows midi. And a few other UI libs. All the dll's should be kept in the same folder as the exe.

Updated - See here for latest version

[BrianEvans]

Here is the intensity value of multiple fixtures. (In %)
print(HC.AttributeGetValue('1/6'))

You can also get multiple outputs at the same time. (In DMX 0 to 255)
print(HC.GetProperty('output','#1/6','value'))

[Durisian]

Thanks Brian.
I guess what I'm after is similar to AttributeGetValue but returning dmx values rather than %
Although given the laggy nature of sending MIDI on changes - it's not a big deal to utilize the percentage value anyway

[RobertBell]

8-Bit DMX is protocol level. Internally all attributes are 32-bit. We need to give you a way to get real numbers vs. integers.

FYI this also works (integer only) print(HC.AttributeGetValue('1/6','intensity+DS'))

+V = add value
+L = add label
+S = add state
+D = add display value (i.e. what's displayed in the ML grid)

+R to return a real number Value

Any combo of +VLSD is valid.

Returned state values are:
If not from a Cue, the state is uppercase:
GET_ATTRIBUTE_STATE_CAPTURED 'C'
GET_ATTRIBUTE_STATE_DEFAULT 'D'
GET_ATTRIBUTE_STATE_FROM_LOOK 'L'
If the state is from a cue, the state is lower case:
GET_ATTRIBUTE_STATE_UP 'u'
GET_ATTRIBUTE_STATE_DOWN 'd'
GET_ATTRIBUTE_STATE_CHANGED 'c'
GET_ATTRIBUTE_STATE_BLOCKED 'b'
GET_ATTRIBUTE_STATE_TRACKED 't'

[Durisian]

oooo I'd forgotten about +VLSD - Thanks Robert

8-Bit DMX is protocol level. Internally all attributes are 32-bit. We need to give you a way to get real numbers vs. integers.

I'm not sure I understand - can you clarify the difference between real number and integer?

[RobertBell]

Right now it gives you an integer between 0-100. At least you could expect a number between 0-255. But internally we use 32 bit double precision real values. Eg 45.34628765

[Durisian]

Here's the latest installment

- Massive stability and performance improvemnets
- Added continuous control for looks
- Better fixture selection
- Script trigger can accept greater or less than for the midi value, doesn't have to equal
- Experimenation with MIDI hold pedal (very buggy, but's its fun playing a tune and watching all the lights play along)