Why using OSC instead of MIDI messages ? OSC messages are MUCH more precise and it’s important when modulating specific parameters like filter cutoff. Also, the physic behaviors of Lemur objects make this software controller iApp quite unique ! That’s what some of these devices try to explore.
Use the ableton Live help box (at the bottom left) while flying over the MaxForLive devices with your mouse.
The ZIP file below contains the 4 MaxForLive devices (frozen devices), the 3 Lemur templates and 2 Lemur library objects ready to use in your own templates.hps-OSC-tools-v1_0.zip (1133 downloads)
ableton Live v9.0.4
Max or MaxForLive v6.1.3
Liine Lemur v4.0.3
tested on Mac OS X v10.6.8 but should work on both Mac and Windows platforms.
The small audio clicks and glitches are the result of the fullscreen capture that was running as a background task.
A simple device to let you connect up to 6 OSC controllers to 6 ableton Live parameter : select first the OSC controller number (ctrl1 to ctrl128), set the smooth time (from 0 ms to 10 sec), then “auto-map” the ableton Live parameter with a minimum and maximum. DONE !
Same underlying concept and usage as hps-OSC vector matrix but with a specific focus on audio vector mixing of 4 sound sources (a linear mode is also provided for other uses). The 4 audio sources can be 4 tracks or 4 macro controlling instruments’ volume in a rack instrument or … I think you’ve got the point.
I like to summarize this MaxForLive device as “how to dynamically mix 8 audio sources with just ONE finger !”. This device goes one step further than the vector mixing concept by using the Max nodes object in a clever way. Each audio sources (up to 8 tracks or instruments in instruments racks or …) is represented by a node with its X-Y location (it’s a conceptual 2D location, not a “real world” one) and its radius or intensity. Then, there is the listener node – if the listener is inside the radius of one or more nodes you will hear the sound sources with a intensity relative to how far/close the listener is from the nodes.
What is very interesting in this concept is that both the audio sources’ nodes and the listener one can be manipulated with your fingers, but also by the use of the physic behaviors of Lemur multiball object. That’s what the same video at the beginning of this page is about.
Configuration and OSC nomenclature
In your Lemur and in each device, you have to inform the communication port (that’s where the OSC messages are received). I’m always using PORT 8050 and it’s quite reliable.
These ports are already used by the Lemur iApp and the Lemur editor.
In hps-OSC control, hps-OSC vector matrix and hps-OSC vector mix devices, the OSC message nomenclature is:
ctrl1 => /hpsounds/ctrl1 ... ctrl128 => /hpsounds/ctrl128
In hps-OSC nodal mix device, the OSC messages are “hard coded”. I will documented it later here.