11oLsen Homepage


I'm glad I had the opportunity to develop the hb1Control software with Hornberg Research. hb1 is a nice midi breath controller with some cool features.

The hb1Control software provides you with full control over parameters, presets and preset combinations of the hb1. It also adds features that are not available if the hb1 is used without a computer. The software can be remote controlled with a web browser on (nearly) any device.

Parameter Randomizer Device

My parameter randomizer with probability distribution per parameter. I thought it might be useful for others, too.

Finally I did some updates to the Nocturn m4l device. It makes more sense when mappings are recalled with the Liveset.

A design update for Reminder m4l device to make it compatible with Max 7 UI.

I had some fun with the Digginsack Facebook Group where a given sample has to be used for a 2 minute beat which ends up in a voting.



On a search for things related to audio metadata extraction i came across MEAPsoft quite a long time ago. I didn't like the GUI and the way it was meant to be used but noticed there has to be some interessting code behind it. The intention was to reuse the open source code in Max someday but my knowledge of any text based programming languages was very limited at that time.

It was this summer that i took part in a 7-week C# course which finally gave me the needed insight into object oriented languages that i was missing to understand the code and to start this project. 

It's hard to tell when a private software project is finished, in fact it's never. I decided to share this now because it reached a state where it has all main features of MEAPsoft and some more. In addition many bugs in the MEAPsoft source code have been fixed. And i really need a break from JAVA.

MEAP4Max is nothing to use, it's something to build upon. A tool for the Max community. Have fun.


Random Simpler

I'm back with this instrument. Like in a previous device, I use Ableton Live's file database as a sample source but this time it's a sample player at the same time. My goal was to have a pretty complete set of controls of a simple sampler engine like playback direction, loop modes, pitch, filter, envelopes, panning, volume and a seemless communication with the database in the background.

The device makes it easy to take a trip through your soundfiles by just pressing Next or Prev (midimapable buttons btw) independent from your folder structure. What I like to do is combining multiple instances in a drumrack with something that generates midi notes and build little generative music maschines. Again not your average Max4Live device instead an innovative approach with well thought out Max patches. 

I've learned so much while creating this about MSP (signal processing objects in Max), databases in general, handling dictionarys and databases in a C-external, porting everything over from Windows to xcode on Mac, make multiple instances of the same device talking with each other etc. It was a great jorney and it's not finished. I hope for some feedback and already have my own to-do list for this.    

Random Sample Picker v2

This max4live device uses javascript to access Live's file database to allow advanced filtering of files. For the results we create symbolic links to make them drag-n-dropable from Live's browser. All in all it is more a proof of concept than a really useful device. Strange that Ableton isn't implementing more browser features in view of the fact that all file meta data is stored in a sqlite database.   



The Euclidean Algorithm

Another side-product of an upcoming device i want to share.

Meanwhile everybody knows this paper by Godfried Toussaint. I din't know there's an extended version. First time i heard about it was in this awesome maschinedrum talk by wesen, goto time 29:00.

It's easy to find good 3rd party externals to solve the task, but i felt challenged by doing it with basic max objects.

The first result was a highly inefficient patch. But now, after understanding the binary version of the algorithm a little bit better, i managed to create a much more efficient and simplified abstraction for Max.

Nocturn Live Api Device

This was the logical step after creating the nocturn object. A m4l device that translates the raw Nocturn in/output to a system of pages to access the different sections of Live's API. The part that was handled by "Automap" and control script before.

This is again a PC-only release because it depends on my 11nocturn object. 

It should be pretty self-explanatory. A user window always shows the mappings and settings of the current page. There's a dedicated button on the controller to show/hide the user window.


  • my old solution (Automap+script) didn't work in Live 9
  • the idea to circumvent installation and configuration of Automap, a control script and so on
  • i like the rotary encoders because they are easy to switch to another parameter and resolution. They're endless which is better for scrolling and navigating than standard 0-127 midi knobs
  • for peace on earth

Working with parameters in the Live Api leads you to a decision on using live.remote~ to make fast but not recordable tweaks or using live.objects for lower-priority but recordable parameter changes.
I used live.object in any case to be able to record automations for device parameters. Now, we finally can do that in session view with Live 9.

Please don't hesitate to send me bug reports or suggestions. I patched this for my own needs and that may have made me blind for certain things. Same is true for growing complexity of patches.

As far as what i have planned, one major update will follow. And maybe i'll add a video to show the basic function of the device. Everything beyond depends on your feedback.

Novation Nocturn Object

 novation nocturn pic

The idea came up when i tryed to install the Novation Nocturn again after a long time and itegrate it into Ableton Live. It's a pain. You really can't use this device without Automap, the software provided by Novation to create mappings for midi messages which are being sent into other software via virtual midi lines. And there's no native support for this controller in Live.

I needed an object to directly talk with the Nocturn from Max/Max4live. In the end, I will connect this object with the Live Api in a Max4live device and, by this, bypass the second pain of using/creating a custom phyton controller script in Live. I mean, a patch is far easier to customize and adapt to personal needs.

This guy obviously found a way to use the usb protocol of the nocturn with python under linux. With his Informations and some usb-sniffing in Windows i was aware of the protocol.

This is coded with the help of libusb-win32, a port of the USB library libusb 0.1 to the Microsoft Windows operating systems. I highly recommend to take a look if you think about custom drivers or custom interfaces for usb devices.

Interessting talks about this topic:

This release has NOT been tested extensively with many different maschines and conditions. Your feedback is really appreciated!

Keystrokes and Mouseclicks

These two Max externals for Windows can simulate keyboard and mouse input. Keystrokes and mousewheel input affect the active window.

Remote controlling (music-) software for me is one key for a smooth workflow. But sometimes important functions of a software cannot be assigned to a controller but to the keyboard or mouse.