Synthesizer Jam [SYNC]

0 Comments | This entry was posted on Feb 24 2019

Jeden ersten Mittwoch im Monat treffen wir uns in der Raststätte in der Lothringer Straße in Aachen zur Synthesizer jam SYNC. Weitere Details zum Programm der Raststätte mit Konzerten Lesungen Ausstellungen und mehr findet ihr hier. Im Video ein kurzer Mitschnitt aus dem vergangenen Jahr.

Still alive 2019

0 Comments | This entry was posted on Feb 24 2019

Hey folks,
years passes by, and I focused more on my day job as research group manager at the university. I am still making music and use the Lemur, but I am no more into programming new interfaces for a while now. I guess thats how it goes very often with such special application developers. As I had my toolcase for the Lemur I was fine. Actually I even stopped reading the forum on liines website regulary and than, after I while, I forgot to look at the forum at all. Suddenly I registered that Liine put their forum down [sic!]. It must had happend nearly a year ago. And no proof of live from them at all. I tried to contact them, but no answer. So, sadly, it seems Lemur is dieng a second time, after that Jazzmutant death in 2012. If anyone has more information, please drop me a mail. Meanwhile one user had thankfully opened a new forum for lemur users:
I will see that I update this page soon and make a collestion of my interfaces available. At the moment you can also still download them from the Liine user area: but who knows for how long…
Hope you are all well and kind regards

studio setup 2013

0 Comments | This entry was posted on Nov 20 2013

a short overview on my setup for making electronic music

In my actual setup, everything that makes sounds comes out of ableton. so the video is more about controlling, than sounds or audio…

I use 2 Lemur parallel (iPad and Jazzmutant hardware), and get midifeedback on both. That means, changing values in any interface, will be reflected on all devices.

Isn´t so special? true, in days of networks it should have been standard…and I know there are some nice plug and play devices that are ultra coupled with software and for sure give feedback,… but between devices it is sometimes tricky.

I use at least 10 midiports to achive this on PC*:
*(it differs on mac, based on IAC and Lemurports)

active INs in ableton [track/remote]:

  • maple midi 1 = Jazzmutant Lemur, Midi target 0 out
  • loop midi 1 = Liine iPad Lemur, Miditarget 0 out
  • loop midi 3 = Liine iPad Lemur, Miditarget 1 out
  • loopbee = max/msp, Sequencomat [+sync in case of master]
  • Akai MPK 61
  • Arturia Analog factory
  • Tascam = as external gear: Doepfer Pocket Control DIRECT
  • active OUTs in ableton [remote]:

  • maple midi 2 = Jazzmutant Lemur, Midi target 0 in
  • loop midi 2 = Liine iPad Lemur, Miditarget 0 in
  • loop midi 4 = Liine iPad Lemur, Miditarget 1 in
  • This way, I got feedback on my Lemur. (While feedback on hardware controllers is not possible, misses motor encoders) ;)

    tonvibration studio setup 2013


    Demo video Scalomat 2013

    0 Comments | This entry was posted on Nov 01 2013

    Ambient music :)

    0 Comments | This entry was posted on Oct 27 2013

    Ambient tracks, recorded 2013 in Ableton 8 using Synth1 and Arturia Analog Laboratory.
    Controlling on Lemur including Sequencomat and Scalomat.
    This playlist contains 7 sounds, total time: 34.59

    Scalomat 2013

    0 Comments | This entry was posted on Sep 22 2013

    I have updated the Scalomat (for previous version see:

    Scalomat is a scale dependent keyboard for note entry.

  • In its actual version Scalomat fits the number of the pads per column automatically to the number of notes per scale and the vertical number of pads to the number of octaves.
  • Keynote and lowest octave can be set separately.
  • Beneath 15 standard scales selectable via drop down menu Scalomat also contains a custom scale that can be set on a little keyboard.
  • Keyvelocity can be set on the big fader on the right or it can be a random value between two ends of a Rangeobject.
  • Midichannelselection on drop down menu and additional Kill Midi switch (for accidently hung notes).
  • 3 Playstyles for Pads: “normal” – direct note on/off by touch; “switch” – switch notes on and off; “sustain” – sends delayed note off message indicated by release time on pad and controlled with a slider (0-15 seconds). Playtypes combineable during play.
  • And finally a little Programm change module for selected Midichannel.
  • Download Scalomat 2013 in the Liine user area:
    Visit the thread in Liine forum:

    ———-update 131020——-

    added more resolutions:


    Modumat [update 2013]

    0 Comments | This entry was posted on Sep 16 2013

    Its been a while since I posted some new tools or add ons…. but now I have found some time to update the “Modumat”, one of my first Lemur modules.

    “Modumat” does step modulation of Midi Control Change data on up to 16 steps. This can be linked to any function like filters, velocity, pan or whatever. The modulation can be send stepwise (default) or as a continious line (interpolate). There is a range for the output (e.g. if you only want filter to vary between 34 and 56 instead of 0-127) and a range for the used steps (16 is maximum). The new version6 got also a row of random-switches beneath the sliders – if a switch is activated the corresponding slider will get a new random value shortly after it is triggered. This brings in some variation. As you can control the position of random and the amount of output that is still interpreted by a range, I like to call it “controlled random”.

    All values can be saved in 15 presets. Saved slots are highlighted. To erase the highlighting press preset 0 and 14 parallel in play mode. This only erases the highlighting, to erase a preset just override it with a new preset.

    The output can be routed to any Midichannel and controller number by a drop down menu (sending to Miditarget 0 on Lemur).  There is a syncronised version (listening to clock input on Miditarget 0) and a unsynced version. Both using only half the screen, so there is enough space to combine it with a small key or a 2nd modumat on one interfacepage.

    You can download Modumat from the Liine user section:

    Here is a video from early 2009 which shows one of the first versions of Modumat. It does not contain all features (random switches, presets, Midirouting are missing) but it gives an idea how to use the Modumat.

    Enjoy :)

    Sequencomat v3.4 – program change

    0 Comments | This entry was posted on Jan 14 2013

    I am currently working on an update for my Sequencomat,
    this short video gives insight into some of the new functions:

    The video shows in the following order:
    - setup CCs for program change
    - using right slider to set all values
    - set stepvalues, use random
    - program pattern chain
    - play chain and see blinking
    - see feedback on synth1 template (normal midimapping)
    - and overwrite it manually

    v3.4 update will be available february 2013
    links and info will follow soon…

    See topic at Liine:
    manual of v3.3:

    New features on Sequencomat v3.4:

    - Program change is now transmitted via ControlChange on Controller
    number 129. This means you can jump the sound stepwise if you like or
    patternwise, which leads to some new musical opportunities. Controlling
    the 128 programnumbers via the MultiSlider is not the best ergonomic
    solution, but shrinking the range helps a bit and gives more

    - Pattern chains (follow actions) can now be programmed total free,
    including iterations of the same pattern and jumps across patternbanks.
    Chains can be programmed on the fly during playback.

    - Saved patternslots are now highlighted. This feature is an ergonomic
    must have and was already integrated in v1 and v2 of Sequencomat (where
    pattern saving was done in Lemur, not in max), but I missed it in v3
    (cause now pattern handling was done in max and I have to fiddle out a
    appropriate method to do so). Actually this feature was the reason I
    started the update.

    - Patternjumping can now be done with next beat. Although I am quite
    proud that Sequencomat jumps pattern directly so you can play them
    like an instrument some users asked me for a function where
    patternjumps are done at the end of the beat. So I integrated a
    dropdown-menu where you can choose between direct pattern triggering or
    with next 1/2bar, bar, 2bars, 4bars.

    - Next pattern to come will blink. This gives a good visual feedback for
    above mentioned patternchains and triggering on beat. Blinking rate
    responds to 8th of actual bpm.

    - Shortcuts for 15 scales. Although you still can define your scales
    totally free by entering the halftonesteps, I added shortcuts for 15
    well known scales. Scales can be defined independent for track 1-4 and
    5-8. They are parts of the set (not of a pattern) and can not be changed
    during playback.

    - 20 colortemplates. I expanded the available colors for the surface a
    lot. That 20 color themes include 4 mainly grey templates and 4 user
    templates, that can be built individually.

    - Sets of Sequencomat v3.3 are compatible with new v3.4, but will miss
    the patlight-vector for highlighting saved slots, which can be built
    by saving the patterns in same slots with v3.4

    The update will be available in February and all users of full license
    will get a free update.

    Route n Range: external Midigear with Lemur

    1 Comment | This entry was posted on Apr 28 2012

    Dear Lemurians,

    here is a new patch I´ve made in max/msp with a control surface for the Lemur.

    It is called “Route n Range” and what it does is: It takes an incoming MidiControlChange message from external gear, display it on the Lemur, where you can range it, and send it out to another Midi destination.

    Incoming Midi CC can be linked to 8 Controllers. Pressing the top bvutton will link the aligned Fader to the actual incoming Midi (Midilearn). Channel and Controllernumber can be also set manually by pressing switches in the 2nd row and turning the endless knobs for Channel and Controller. By activating the switches at the bottom line, values for Channel and Controller for Midiout can be changed with the 2 knobs too.

    Each Fader got a attached range, which controls the value output, displayed in a monitor below. This allows to transform the full movement of a hardware rotary encoder (0-127) to only send between concrete values (e.g. 35-76). However – the fader will follow the Midi input (0-127). Midiinput can also be overwritten by moving the Fader directly.

    Settings of all In and Out routings and ranges can be saved in 12 sets. If the numberpad is green, it is in load mode. For saving change to record mode by pressing the red switch above. Notice that these sets will only load the routings, they are not snapshots of the CCvalues! After a jump triggering is initiated by hardware input, where here all 8 Controls act independent from each other (no list processing).

    The Midiports for in and out can be chosen on the maxpatch. They are split for Controller 1-4 and 5-8, so you can use different Midiports or just the same. Choice of Midiports can be done only direct on the maxptach, not on the Lemur. But Midiports are also saved within presets, which can be loaded from the lemur.

    Between the maxpatch and the lemur surface is a bidirectional OSC connection. So the lemur controls the patch, while all Midi is handled in max/msp. (In fact the patch also works completely without a lemur.)

    You might ask: What the hell is that good for???

    As you can route your external Midigear directly within your DAW, why this circuitous way with a maxpatch and a lemur in between? The answer lays deep in my personal setup: I have a very well defined Midirouting in my DAW where I controll over 200 CCs. As I have learned many functions to concrete controllers, I do want to change the sending side of Midi, not receiving in my DAW. While most USBcontrollers can do that easily, my beloved “Doepfer Pocket Control” – best feeling encoders ever – has only a small DIPswitch, which makes midirouting unconfortable. Therefore, I needed the patch to switch the Encoders to different Controllernumbers. Furthermore I wanted to have a range, so I got more detailed control and I wanted to switch during playback. …thats where the patch comes from.

    I admit that this is a very specific use. But it might be, that there are some other users, who also have (old) Midigear and want to link it up dynamically, so here is the patch :) btw: the maxpatch is open for editing. I think it can be easily expanded to 16 Controllers if necessary.


    Sequencomat V1 – re-release for iPad 2012

    1 Comment | This entry was posted on Mar 20 2012

    I re-released my SequencomatV1 for iPad:

    Threat in Liines forum:

    V1 was first released september 2009. I had only some minor changes on maxptach, but I resized the interface, try to make it a bit “clearer” and also added physics on the Velocity and Length MultiSlider for trackvalues. I also put some effort in writing a manual/documentation. It is attached in the zip as pdf and available online: The manual also contains some scripting tutorials, because most variables are calculated on the lemur in V1 and only triggering of those is done in max.

    Naturally V2 and V3 of Sequencomat give more detailed control, but V1 with its direct controls has its own charme. A comparison of all Sequencomat sequencers is given in the FAQ of the manual. In common: Global values in V1 (Midichannel, grid, playdirection, steprange, startpoint) become trackvalues in V3; and track values in V1 (pitch, velocity, length) become stepvalues in V3. There is a video where I compare V1 (old legacy surface) and full V3.1:

    There is also a playlist (3 videos) that show functions of V1: (videos are also with old legacy surface, but demonstrate functions quite well)

    V1 is combinable with V3 and/or V3 lite. This can be done as different interfaces within one lemur project, but also on different lemurs (legacy/iPad). You just have to run both patches in max and set right IP and OSC for communication. For sync V1 and V3lite use rewire clock on both, cause it is the only clock V1 has. For sync V1 and fullV3, deactivate rewire and V1 will automatically follow V3 settings (it uses the same clock variable names).