MIDI, OSC or Eucon-Protocol

    Seaboard RISE

    My control board for the Modular Synth. With Keywaves!
    Of course I have an extra page:

    the Seaboard RISE

    Euphonix Artist Mix

    Eucon Protocol, 10 bit Resolution

    The Euphonix MC Mix (now Avid Artist Mix) is an excellent and affordable controller with Motorfaders and the fast Eucon-Protocol. When the controller is used with different software, the controllers jump to the positions of the active software. Anyone who has ever worked with high-quality machines can no longer be satisfied with a MIDI control (7bit). The Eucon protocol provides 1024 levels and the Ethernet connection is 250x faster than MIDI. The improvement in the transmission of slider movements is comparable to the sound improvement in the step from 44.1 to 96 kHz.

    For applications that can not work with the Eucon protocol, it is possible to use the MackieControl protocol, which is MIDI, but it still feels better than most other MIDI controllers , The silent iPad, however, is the simpler and also elegant, perhaps more modern solution for the control - the faderbank then remains just for other tactiles.

    Avid Artist Mix

    Tablets and Smartphones

    ... already better than on the Enterprise!

    Unnoticeable, a big change has taken place - similar to the central heating, the central CPU (the computer) moves into the spatial background and with it also far more than just the sub-noise. What a blessing! Smartphones and tablets are perfect controllers and can be upgraded with the appropriate apps. Not only do they replace the MIDI controllers, they pass them on thanks to the free "formability" of the interface, the resolution (approx. 10bit) and the speed (Pico instead of milliseconds), and they are absolutely silent.

    For me, tablets are mainly control devices. I prefer the sound processing with more powerful CPUs or with the synthesizer. The software is controlled via various tabs, including preferences and FX peripherals. Instead of a mixer or a motor-faderbank now an iPad already is enough, in order to mix a live sound at the highest level. In some cases I switch the A/B/Mono/Main/Direct Studiomonitoring with the iPhone and it does not even need any cables. Is this already paradise ?!

    For haptics and tactiles still remains the Motorfaderbank - also in 10bit (see above).


The app of the apps: Max on the Mac controlled via iPad
  • MIRA is an iPad app that gives Max programmers a huge piece of work in interface design, in which it simply mirrors some Max objects. Even if too few Max-Objects are supported - it can be done much more with it. Max would not be Max otherwise. In the photo is e.g. an audio waveform, even though MIRA can not (yet) map the Waveform object. However, multisliders can be misused with some mathematics to visualize waveforms that have enough information to display the sample. After only a few days with MIRA, I had the impression that OSC would only be used for selected things, and I'd rather turn to the blessings of object mirroring by MIRA - it is much less work on every patch! The concept of MIRA is so perfect, that it is easier for me to describe it by the (still?) negative points. It is only for Max/MSP on MACs, still the iPad is quite warm (which perhaps points to still not optimized data streams) - at the USB port of the computer discharges, despite the 5V supply, the iPad slowly (very slow). In short: MIRA is simply awesome and operational!

    On the left, the supported objects are displayed. There are already some M4L objects and I am pretty sure that M4L (Max for Live) will be treated with a special interest, because (in the combination of Cycling74 and Ableton) a very large customer group should be represented specifically with this control-surface. There is nothing else to be said about the objects, except that the number boxes can also be adjusted with a finger, thus they are not only serving for display. The problem of adjusting the dial and slider values when releasing (certainly one of the trickiest points in app programming) has already been significantly improved. Overall, the deal with MIRA is very, very pleasant. It should also be emphasized that Max patches with MIRA-Frame are automatically transferred to the iPad. So only the app has to be started on the iPad. MIRA is a giant step in the individualization of interfaces on the most popular instrument, the computer!

    MIRA not only brings Max to the iPad, but also iPad capabilities to Max. Multitouch, gesture control (wiping and tapping) as well as the gyro data, generated by the iPad through tilting, can be sent. Here it becomes very interesting. How fine these control parameters can be used, can be found impressively in some games for the iPad. Also the great ThumbJam app uses these possibilities in an inspiring way. Lastly, to the hopeful future, MIRA is not the first attempt to connect Max and the iPad. MIRA is offered by Cycling74 directly (of course via iTunes). It is something special and suggests that it is not a short Liason. For me, MIRA is out of competition and I take thank the developers and Cycling74! So - now I have to go back to work to change all my active patches to MIRA ... MIRA means a generation change for Max-Interfaces.

TouchOSC, OSCulator and Lemur

Controller apps that work with the OSC protocol


    Is a collection of 14 control elements. Both software as well as OSC (the "protocol") are to be learned within one day and offer especially for Max programmers a congratulatory expansion of their own software! Why? OSC is faster than MIDI and also offers a higher resolution. Even if MIDI (especially by standardization) is still useful for some things - moving a slider or controller with OSC can be much more comfortable...

    TouchOSC comes with a small computer software editor for the pad/pod/phone interface, which is transferred to the mobile device after completion. The ingenious touchOSC is its reduced form, which affects up to the price ($ 5). The only thing really missing is a range slider (with two values for min/max). Especially in conjunction with Max/MSP, however, excellent controls can be made - even including text transmissions ala teleprompter or karaoke help - also gyro values can be sent. Absolutely recommended and a must for anyone who already has a smartphone, iPod or tablet! TouchOSC also sends MIDI.


  • OSCulator

    is an excellent tool for addressing OSC messages. I use it to send keyboard shortcuts to software programs. These key combinations are offered by most software - iTunes has, for example, Start/Stop, Forward, Back, etc. With the help of Max and TouchOSC you can get more from OSCulator. Buttons can change the color and thus display the status - volume change does not have to be done step by step, by repeating the command - it can be automated by a Max-Metro-Object.

    For this, OSCulator is integrated as a third "host". The iPhone sends to Max, Max realizes all automatisms and sends to OSCulator, which supplies the desired software with commands. The colors of the buttons on the iPhone are also changed from Max so that the current status can be read - in this example "color blue" and "color gray" alternate. Osculator is an excellent tool for setting up an optimized work-bench!

  • Lemur

    The most comprehensive package, but it gets only a brief mention by me. The reason is that the programming of lemur is quite complex and extensive training is essential. Lemur offers besides various tabs also "suitcases", which can be opened and closed within the tab. Also Lemur has its own "generators" - that is, things can be animated or a kind of gravitation can be set. So a really great and complete thing!

    Even after several years, I've never taken the time to get deeper involved, which is a bit annoying, because Lemur was the pioneer of the TouchPanel movement and offers really fantastic possibilities to program good interfaces!


The Open-Sound-Protokoll "OSC"

What exactly is that?
  • OSC, in brief...

    OSC is a development of the "Center for New Music and Audio Technologies" (CNMAT) at the University of Berkeley, California". It is an open protocol, a kind of addressing kit.

    The most important character is the slash (/), which divides addresses into different areas. First, there is usually a number for the indexed or outgoing tab, e.g. "/ 1" for the first tab. The name of the object follows, for example "Slider1", ie "/1/Slider1". Names can be chosen freely, so it could also be called "/A/Hermann" or "/Purg/Nudel". The value of the slider appears after the address and a space, that is, e.g. "/1/Slider1 0.76". The slashes are to compile the address without spaces - the value follows after a space. If the slider is now moved on the pad/phone, the message (for example "/ 1 / Slider1 0.76") is sent to the computer. When the message "/ 1 / Slider1 0.76" is sent from the computer, the corresponding slider is moved to the position 0.76 regardless of whether the tab on which the slider is located is currently visible or not.

    In Max, messages can be exploited economically thanks to special routing objects. Thus, the first division would be e.g. "/ 1/2/3/4". Now all the data in the first tab would be at /1, the second at /2, etc. (of course only the "remainder" addresses, ie "/1/Slider1 0.76". Another normal route object from Max, with the attribute "Slider1" could now supply a number box with the corresponding values.


    Actually no relevant question - it is a UDP protocol and rather about whether you want to use WiFi as a controller data highway, or not. Almost all OSC apps also send MIDI.

    Very simple, very effective, very fast! Especially for Max-ists a great protocol. 14 bit resolution and the fast protocoll ensure perfect use. If OSC is used as an exclusive protocol, a large batch of addresses is created, which occasionally also carries orgian traits - if, for example, in addition to the slider values, color and text changes, peak meters and more is sent.

    Of course one has to deal with a little bit of network technology to set the addressing of the different OSC stations securely - but this is relatively simple and becomes more "normal".


    Clock-sync accuracy, theoretical limit:

    OSC: Pikosecond (via NTP/IEEE 1588 Sync) - MIDI: 20833 Microsekonds

    Transmission speed:

    OSC: >800M bits/sec - MIDI: 31,250 bits/sec

  • OSC - Examples in Max

    Clock-sync accuracy, theoretical limit.