User Details

Username: xanadu
Website: None provided
Facebook: None provided
Twitter: None provided
Soundcloud: None provided
Account Status: enabled
Member since: Dec 14 2009
About xanadu:
(report this profile)

Devices by xanadu

SynClone FM Synth Version 1.0.156
Volca Sample Editor Version 035
Launchpad interface Version 1.0
Launchpad DrumSeq Version 1.1.23
MFL Document Utility Version 1.0
Mentat Slice Drummer Version 0.300
Live Touchscreen Remote Version 0.70
wjl.spectrum.utility Version 1.0
Launchpad 185 Sequencer Version 1.5.9
Lemur Kaoss Keyboard Version 159
Live Session Script Version 156
Pentatonic Keyboard Version 011
Synplant Genes Version 1.0
SparkLE Drumrack Version 170
Electribe2 Pattern Editor Version 026
MicroTonic Drumpad Version 1.0.1
High precision Circuit Rack Version 17
Microtonic with XO Version 1.3

Total Downloads: 40,276

Comments by xanadu


Bugfixes. Microtonic with XO is now updated to version 1.2.

There was an error in javascript which prevented analysis of Microsonic presets in some cases.

The file creator tried to write files to the folders 'Closed Hihat' and 'Open Hihat'. These folders were named 'Open Hat' and 'Open Hat'. Instead of throwing an error the files were actually written to 'C:/Program Files/Cycling '74/Max 8'. Please remove all .WAV files in your Max installation folder and rename the 'Closed Hat' and 'Open Hihat' folders. Then run the Microtonic Sample Creator again from the updated download version 1.2.

In version 1.1 I've reworked the manual, correcting typo's and making it more comprehensible (i hope). Being a Dutchman, writing in English is somewhat error prone.

Hi dystopiandisco,

Thanks for your remark. I don't have a Mac, so I can't test my devices on it.

I've added a menu with the Microtonic plugins that MaxForLive can find in the default places. There's also an option to select your plug-in manually. I hope this will work for everyone now.


Unfortenately there were some bugs. These were fixed in version 17.


Please replace the DX10 with anything that makes a sound when it's receiving a MIDi note ;-) A simpler is a good candidate.

Please replace the DX10 with anything that makes a sound when it's receiving a MIDi note ;-) A simpler is a good candidate.

I left it on purpose. I needed to put some instrument there. The dx10 from Image Line is a nice ancient VST instrument that doesn't distract (I thought) from my new love baby.

If you see all LEDs on the SparkLE controller lighting up then the outward connection is okay. If you then push a button or tuns an encoder a LED on the device should blink. If that's the case all your connections are up and running.

The SparkLE.IO.003.amxd connects to the main device using the OSX/UPD network. That should be okay as well when the IO to the hardware works.

The main device can't and shouldn't connect to SparkLE MIDI because these MIDI ports are already being used by the IO device.

There was another reason for using jmidi: Live does nt decode the endless encoders right. I have not solved that one yet. I suppose I have to create a Live Control Surface to do the MIDI IO.

I wonder if Ableton will ever solve these midi IO issues, giving us SysEx, channels and endless encoders.

I don't know what's the problem. I'm on Windows 8, 32 bits. Jmidi works fine for me, except that I had to find out that java is not available in MaxForLive when the SparkLE VST is loaded.

I've added a new version of the device. This version has a SparkLE.through.Live device that must be placed on a MIDI track of it's own. SparkLE MIDI must be enabled in Live and both input and output must be connected to the track of the new device. Monitor In must be lit.

This new device will communicate with the SparkLE.DRUM.rack using UDP channel 9980 and 9981.

Note that SparkLE MIDI must be off when connecting the controller again to the SparkLE software.

Arturia SparkLE VST and jmidi both use the Java Virtual Machine (JVM). But they can't use it both in the same Max instance. Does the problem still exist when SparkLE VST is not loaded?




The devices are frozen now and the abstractions / subpatchers themselves are present as well.

A preset system is part of new functionality that is ready now. I've been working on some other improvements too. I try to publish the next version this week. I still have to tidy some things up and update the manual.

Hi Olson,

This device certainly is a hack. I made it as a proof of concept. I don't think it has much practical use.

I'm programming a 'SynClone FM' device now in MSP. I'm learning a lot on DSP programming from this.

I'll write an email for "randomize seed" and "clone the selected branch".



Oh and yes, Live Session Script now supprts MaxForLive 5 as wel as MaxForLive 6.

This is for advertising my device!

Version 137 is the result of a struggle with unstability. Live Session Script would die at irregular points. Max 5 and Max 6 both had their own patterns. I hope I have overcome the worst of this, but I haven't found the real problem yet. Inserting 'deferlow' at crucial points seems to help.

Besides parameters in racks in the track of Live Session Script, parameters in racks in the group track can be automated now. Automation has a lot more power, allowing for real LFO activity, automated by up to 6 arguments.



In version 099 MIDI CC functionality is disabled because it crashed Ableton Live when more then one scripter was active.

I'm astounded - I thought this was just simple, innocent code.



Hi Synnack,

Start, Compile, Break, CC Through and Variables are available now for MIDI mapping.


Thanks Myoko. There are lemur files for iPad and iPhone included now.


Both Novation products Launchpad and Nocturn work in the way you are suggesting. On the Nocturn I find this couter-intuitive: I want to see where I am, not where I can go. But on the Nocturn you can have more than 2 pages, leaving not much choice.

On my Korg nanoKey and Akai LPK25 keyboard a led lights up left for lower keys and right for higher keys. I like that.

So both methods are used on modern Midi devices. I think I can make this choice into a setup option in the next update.

I have my iPad for nearly two month. I bought the full featured Lemur app by Liine. It's incredible. I'm creating this 185 type of sequencer now for the Lemur. I think the touchscreen is a better fit for this sequencer.


Your observation is correct. One push is for setting a drum. Two pushes will delete then. One press always sets a drum, two pushes is a shortcut for putting them of with first going to 'no drum' mode.

User 1 mode is a special mode for using the pads of the Launchpad as drumpads. It has a different MIDI layout. So the answer must be that only User 2 Mode is available for a free user asignment of the pads. The standard Launchpad Control Surface is using User 1 Mode for it's own wicked purposes.

Well I'm quite pleased with the current version. In december i crossgraded to Max 6 with Gen and an iPad. Then I found that the Lemur has come to the iPad. This really gives me a lot to discover!

But this Launchpad 185 Sequencer and my Launchpad Drum Sequencer really are my love babies.

If someone comes up with good ideas for effects I certainly try to implement them. Perhaps it would be nice to have more patterns that could be swithced by pushing a button.



It's found in the help file you can open with the 'Help...' button in the Live window of the sequencer.

These are the effects:
0- Nothing happens
1- One note is played using it's own duration
A- On each step a note is played using it's own duration
D- A note is played during the whole stage
L- Legato mode. Previous stages with a D or L effect will wait to send their note-off MIDI signals until a stage with another effect than L is played. In the L stage a new note is played during the whole stage. This should be used in combination with a mono-synth.
S- A note is played on each step according to the 'Duty cycle' setting.
3- There are 3 notes played, dividing the stage in 3 equal parts
-- Nothinh happens.Anyone with a suggestion?


Hello Rosko,

Thanks for your explanation. I think I've got the bug now. Changing the pitch with the mouse *only* worked when the Launchpad was displaying the pitch. Since you are not using a Launchpad, your internal pitch setting was not opdated. In version 134 this is fixed.

By the way, this sequencer was made for use with a Launchpad, so it would be more fun if you could get one.


Hello Rosko,

Thanks for your explanation. I think I've got the bug now. Changing the pitch with the mouse *only* worked when the Launchpad was displaying the pitch. Since you are not using a Launchpad, your internal pitch setting was not opdated. In version 134 this is fixed.

By the way, this sequencer was made for use with a Launchpad, so it would be more fun if you could get one.


Hi Rosko,

I think you really want to use my little sequencer, but helas without much luck. I'm still trying to figure out what is exactly your problem and what is causing it.

1. Are you using only 1 copy of Launchpad 185 sequencer in your Live song? At this time more than one copy is not tested and probably won't work.

2. When you mention 'tracks' do you mean the Ableton Live tracks or the 16 'stages' in the sequencer?

3. I think order of the initiatlization on your system be hust a little different than on my computer, resulting in uninitialized stages. I have uploaded a new version 132. This one has a better initialization worked out. Does this help for you?

4. Please upload your Ableton Line .ALS song file to . Then I can try te recreate the problem at my own system.



Hello Rosko,

Sorry to hear the Launchpad 185 seq is not working well on your system. I suppose it's is a timing problem, but I can't reproduce your issues on my Windows XP system. What system are you on?



This device reaches completion.

I promise will take care of saving / restoring the device with the Live set and an instructing manual.

Your user ratings are welcome now.

The sequencer uses Live's transport so Live must be running. If Live and the sequencer are both running there should be a running light in the sequencer window.

Else please describe your system.

Thanks for the report. Start time and sequencing has been worked over in the new version. It will start quantized correctly. It will keep track of the steps using Live's transport as a master timer.

The sequencer will not take care of changing the meter while playing. It doesn't respond to jumping on the timeline while playing it just goes on counting the beats and looping when it has played all it's steps.

Velocity works, but the synth or the sampler must respond to it. Some presets dont't use velocity or aplly it to open or close a filter.

Hello guys,

Thanks for your ideas, downloads and the wonderful rating of the drumseq. This really keeps me goning.

But now the sad news.

First I bought a new touchscreen. Then my computer got broke (unrelated, probably) and went to the repair service. The verdict is: motherboard broken. It will take some time to get it up and running again, so please be patient on updates.

Happy new year,


Thanks for the positive remarks.

I like the idea of memorized patterns.

My first priority is now on having presets for different drummachines. User presets are welcome at LaunchpadDrumSeq@site4fun .

The Mentat Slice Drummer is approaching beta now. The next update will have 2 * 7 pads and work together wich the drumseq.


Hi dewdisco and Zengel,

The running light is fixed now in version 1.1.15.

Are you asking for an undo function for the pattern? Or are the curent 64 steps max not enough?

At the moment I'm working on the Mentat Slice Drummer (it's at ). It's inspired by Fxpansions Guru and Ghost. This device should become a natural partner for the drum sequencer.


Hello Dewdisco,

I'm gladto hear your Launchpad is working now.

Your problem with .LPDRUMPAD is most likely an issue for all Apple users. I can't test it on a Windows machine, so in the next release I will change the extension to .MAXPRESET like you did.




I can't reproduce your first issue. I'm on a Windows XP 32 bit, Live 8.2.1. I've tested this on and MFL 5.1.6 and 5.1.7. I'm able to program drumhits on 4 rows of the Launchpad which show up on the Launchpad, on the screen and are output to my speakers.

Your second issue is caused by the filetypes MFL wishes to recognize. A drumpattern is saved with a .LPDRUMPAD extension. To load it back first choose filetypes *.* in the openfile dialog.

Sorry I can't give you a clue for the first issue.

Kind regards,



Please explain this a bit. What do you mean by 'erase the edit of previous 4 row when switching to another slot' and 'the superposition on the launchpad made it impossible to use the 7 slots'?


That must be

Please send the movie to LaunchpadDrumSeq@site4fun



Currently I'm working on automation. There are some stability issues which need to solved.


The idea of live input from Live is interesting. However, an instrument has no audio input and an audio effect has no midi input so I have to create a workaround.


The MaxForLive dropfile objects needs dropping of a filename (as the name suggests), A live clip is something else and it can't be dropped on a dropfile. Drag and drop from a Live Looper effect doesn't work either. So I'm afraid we can't drag and drop audio from Live into a MFL device.


Hi synnack,

If I where you, I would only test devices from on virtual computers (VMware) after making a snapshot. But life is short and this severely limits what you can achieve within your lifetime...

If someone wants to distribute malware using a MFL device he already has access to the file system and other resources using Javascript. If someone publishes a device with a link to auxiliary resources he probably do even more harm.

If you don't trust the software, don't download it. But this is true for any device on

The count of Ableton Live users who also bought MFL is not interesting for people/companies that distribute virusses.

People who are using Live with MFL on stage are keen to never ever connect their notebooks to the internet and thoroughly test any new software before installing it on this computer.

Don't hesitate to report your testing results and wishlist for enahancements.

The first full version of the Launchpad drum sequencer is released now.

New features:

- The help file is updated
- Clip-automation is working now

The first full version of the Launchpad drum sequencer is released now.

New features:

- The help file is updated
- Clip-automation is working now

The first full version of the Launchpad drum sequencer is released now.

New features:

- The help file is updated
- Clip-automation is working now

The new version 1.0.86 is a bugfix release.
- The running light is working again
- The Param control has been completely rewritten
- A half-speed mode is added
- The help file is not updated yet
- Some now controls have to be added to the Launchpad
- Automation is not working

King Regards,


Yep. The running light is a bug which is fixed. I'm working on automation of the 12 parameters and patterns (parts of the 4 bar squence). I think an update will be available saturday or sunday.

Jkspost, where you using a groove when you got strange triggers?

Hi AuralBee,

Cycling '74 already fixed it. There are 'Incremental Object Updates' at . You need the update for 'pattr'. Pattr is widely used, so I suggest to go and get it. On Windows the .mxe files go to C:\Program Files\Cycling '74\Max 5.0\Cycling '74\max-externals .

After updating the device works correctly in MFL 5.1.4.

Hello AuralBee,

Thanks for pointing out I did not have the latest version of MFL. I must have overlooked the update. Now we're on par with MFL 5.1.4.

In 5.1.3 my Launchpad was by default recognized by the DrumSeq, no more in rthe new version. And I do loose the target settings now on parameter_controls now.

So MFL 5.1.3 and 5.1.4 are not full upward compatible because some functionallity is broken after upgrading to MFL 5.1.4. I will post to C'74 to get support on this.

But here's the good news.

When I apply MPC 57% it sounds really groovy now, where this was less convincing in MFL 5.1.3. Or am I dreaming? I can have all versions of Live at the same time on my computer, but I can only have one version of MFL. I hope MFL really improved on latency and concurrency.

Hi AuralBee,

Sorry to hear that saving parameters doesn't work for you, I can't reproduce your error on my Quad core PC, Ableton Live 8.1.4 and MFL 5.1.3 (41767). Do you have a different setup?

There is grooving now. I have adopted Ableton Live's groove system. If you place a groove clip on the track with the DrumSeq and let it play or loop, the sequencer will play in time with the groove. If no groove is played the drumpseq will play again in straight mode. This means that all of Live's groove library is at your disposal and that you can play your own groove clips as well. In stead of groove templates you can also use MIDI clips with 16 well placed notes (pitch doesn't matter).

By playing grooves with 8 or 32 notes on a bar the DrumSeq can play in double and half speed. Five, Seven or eleven notes let the sequencer play odd signatures, but this needs some experimentation.

The second beta is ready.

>Parameter controls: layout is fantastic. I noticed when automating that the live undo buffer is filling up. Could this be fixed ?
- As far as I know that would need a live.remote (for every controlled parameter). These little gems eat so much CPU that my quad core intel 2.4 Ghz can't handle it. Even 2 or 3 parameter controls freezes the whole setup. Sorry.

>Parameter allocations do not get saved. Could pattr solve this ?
- Fixed. Keeping state between sessions gave me headaches, and I don't think I'm really done with it now. Keep asking questions please.

>There is no room :-) but: bottom row: running light (maybe red?)
- yes. Yellow/Amber, not red. Better for the eyes, I think.

>Swing function would be nice ?
- The Launchpad Drumseq follows the timing of Ableton Live. This means that loops and tempo changes work for the device. I think DrumSeq will follow Live's grooves as well, but this needs checking. But perhaps the drum should not always follow the general groove. It's possible to delay drumhits, but they can't be played before Live's timer says it's time.

If I add groove-control it must make sence, so I take my time for it.

(Now I need to find out how to get the updated device in this site)

I have a meailaddress for thsi device now:

Thanks AuralBee. You ask the right questions. I'm going to figure this out. These are the things that are not-so-obvious in Max, I think.


Thanks for your reaction and kind words.

I downloaded the Samchillian. I'got it working. The letters of the keyboard are transformed into MIDI notes. It also reacts to a MIDI-in channel. It does some transposing and you you repeat the same note it will output a different note every time. But I don't really understand what the program is doing.

I suppose this program can be rewritten for the Launchpad in MFL. As I don't understand the proper workings I will not do this myself right now.

At the momnet I'm thinking of implementing a realtime drumpattern editor and other sequencer like devices.

To prevent getting more spam I don't leave my email address at forums. Sorry for this.