I am looking at possibly purchasing Max For Live, for the purpose of MIDI triggering DMXIS lighting events. I'm not exactly sure what this patch here is, but I gather this means M4L can indeed be used to control the DMXIS plugin?
I'm very curious to know if M4L will allow me to do the following...
- With Ableton Live in Stop mode. (no pre-programmed automation)
- I strike a midi drum pad.
- the velocity of my strike is read and translated and set as a DMXIS lighting intensity value.
- The lighting intensity value is always being decremented by an adjustable timer acting to fade the value to zero.
The effect I'm going for is to have individual lighting effects activate per midi drum trigger pad. With the lighting effect tweaked to slowly fade out at about the same rate that the audio drum samples decay.
Hi Banister, thanks for your interest in my patch.
This is not a M4L patch, but it's simple to implement as a Live plug with some changes.
It's also a not complete patch, because you need the external DMXIS Vst plugin, authorized using his hardware interface.
In substance, my patch is a little VST host where you can remote basically all controls inside the VST, and in this way, with other controls, midi or what else (like OSC), it's possible to remote control the dmx parameters of the VST itself, and that's is easier to do as to control directly all the dmx values in output (the VST just do it for you).
I think I'm starting to understand now. This has nothing to do with Ableton Live or Max4Live...it is used to control the DMXIS VST inside of Max. Ableton Live has the ability to easily control each parameter simply by clicking on "Configure" and touching each control in the VST window. I have attached a screenshot from Live of the DMXIS plugin after using Configure Mode to add each parameter for control.
The one area where something like this could be useful to Ableton/M4L users is in the smoothing of the fader values. This is noted at the DMXIS FAQ page on setting up MIDI (Controlling DMXIS using MIDI
MIDI CC and Note messages have a resolution of 7 bits, (0-127). The resolution of a single DMX channel is 8 bits (0-255). Therefore, if you control DMXIS using MIDI CCs or Notes, you will not get the full resolution available. This could manifest itself as jerky movements of scanners & moving heads, for example. The solution (if available on your MIDI controller) is to use high resolution 14-bit MIDI NRPN messages to control DMXIS.