User Details

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

Devices by Crampe

AuDi -audio to midi synth- Version 1.1
Rec Midi CC Version 1.0
ClipAutomation Version 1.0
ClipAutomation with encoders LED feedback Version 1.0
ClipAutomation with LED feedback update Version 1.0.1
ClipAutomation update Version 1.0.1
Futility II Version 2.0
SessionLooper Version 1.0
SL4P - Session Looper For Push Version 1.1
Push-Global Quant Version 1.2
Push-Master Volume Version 1.0
Push-ArrangeMode Version 2.0
LF8 Version 1.0
Push Snap n Scale Version 1.0
Panarchy lite - Define your own pan laws Version 1.2
eCo Version 1.4
Panarchy - Define your own pan laws Version 1.3
articulaCtion Version 1.3
outist - insist Version 1.4
Push-Scaleton Version 1.2
BiP - bounce in place Version 1.3
BiP free - bounce in place Version 1.0
NeutronPreset Version 1.1
BadHaas Version 1.0
Futility Version 3.2
SAVE Version 1.0
ElectRhythm Version 1.0

Total Downloads: 11,669

Comments by Crampe


The bugs have noticed are the ones mentionned by Wetterberg.
About undo: what about modulating not the dials themselves (I imagine you're talking about the LPG one?), a solution is to modulate the value rather than the dial itself.
It's missing a nice live.banks for Push mapping, I might take a moment and do it if you don't have Push.

Mira support would be awesome.

That's a fun one! Thanks

Ok, I'll send you an email so you can send me a fixed version for which I'll manage the banks mapping.

I love phase distortion synths and this one is an awesome "simple" one.

Built-in modulations (i.e LFO) to any destination would be nice, but dragging LFO around is easy anyway.
It seems like this device doesn't like changing the number of voices: it's better to type in the number rather than using the knob; and it can Some parameters ranges could benefit a bit of exponential value scaling, to have better control ranges.
The parameters aren't Push ready but it just needs a quick edit. I could do it if you don't have Push Miunau.

Anyway, a nice one ;-)

Here's a nice trick that'd make a future version way more handy:

It's an midi in/out external (cross-platform) that bypasses the M4L midi limitations... Use it into your audio device to get midi input straight into it, this way you don't need the midi sender device anymore.

Hey Soundprayer, it works with L10.

Hey Orpheus,

Sorry to hear that. The poping Max console isn't due to Futility (the error message is, but it's not an issue in itself).
It pops-up because of another Max device in your set. Granulator use to do it. If you're using it please update to the latest version which fixes this.
If it's not Granuator then you need to find which device is involved.
Let me know...

"To anybody still having issues (on Mac):

The fix Kasper recommended above for Windows (downloading the vecmath class files) ( worked for me.

If you download the same file (vecmath-1.5.1.jar) and place it in the following / similar path directory it should then work automatically.

> /Applications/Ableton Live 10"

The link is dead. Can someone share the file?

Dynamic EQing is one of the very few things that Live doesn't do natively and for which I need to use a 3rd party device (from ToneBooster).
It appears that your device (from the screenshot, so I might be mistaking) is 1 band but kudos anyway and I'll give it a try with a generous amount of pleasure :-)
Dynamic EQ are just THE shit.

I'm not getting any panning applied to my signal, only the Doppler shift.
Am I missing something?

Yeah Brodiem, I could add a solo. That's not really how I envision the device or what I'd use, but I admit this is something that would probably be handy for many people.

Hey fellas,

Well, nice to hear about your simple tweak. I'm now wondering why did I really need to put this "0" message here. I have ideas about why, but it doesn't seem necessary at all except for visual reasons (which don't really matter)... So what REALLY was in my mind??
Anyway, thanks for you help, I'm going to push an update of the device.

Hey Solomonki, thanks for your feedback.
It seems like a very few people (not even 1%!) are experiencing this problem. That's really bugging me out.
I have to think of an other way of using buttons for key mapping.
Stay tuned, and sorry for the hassle.

Hey Mike,
sorry to hear that.
You should try using Futility within an empty set containing just one track, no other plugins, remote script etc... And see how it works. There's probably something conflicting with Futility in your setup.

Hi Mike,

there was an issue with the Mute feature that used to block the undo history.
Honestly, I never understood what's the reason for this bug, and why it only affects muting and not soloing/arming... the patching is similar for all of them.
So I came up with a workaround fix... apparently this created a new bug, at least for you.
I'll have a look asap.
sorry for the inconvenience.

Hi Stepart,

Sorry I didn't notice your message earlier.
Are you still having this issue?
In case, contact me via gumroad.

Hey Stomkraft,

- Yeah BiP is not supposed to be used in Session view... this is however already on the top of my to-do list ;-)

- the reason why I didn't made it so the recording stops automatically, following the "source" clip's length is that, it's fairly common to bounce in place a source that has e.g reverb or delay on it.
But I could think about adding a setting that would let you set a default "time to wait after the clip's end".

Hey mike8040,
Yeah it's fixed in v3 :-)

This is brilliant!

Ok, the mute/undo issue is fixed. Thanks for your patience.

Hey Brodiem,
I never got any complains about these devices crashing.
In which situation does it happen?

Hey there,
Sorry about my lack of feedback about the mute/undo issue.
I tried to solve this, and it should have been easy... BUT, at the moment my conclusion is that we're facing a silly Live/M4L bug actually.
The issue doesn't make sense at all, and the reason why I think it's a bug is that, if muting is a problem then soloing and arming should too as all these 3 functions are patched the exact same way.
I need to get in touch with ableton about this.
sorry for the inconvenience.

"Maybe a hint in the description that only the outlined parameters are able to control Neutron would be helpful."
that's in the README included in the download...

the new update fixed this issue.

Updated to 1.3:
10 more articulation slots available (20 total).
Changed the choosers background color.

unfortunately M4L is still very limited in this regard, and I'm afraid this is not something possible atm.

I need to post an update with a selectable midi out source. I was expecting for everyone to get the Neutron midi port automatically selected in Live, but I noticed that it sometimes can be assigned a different name (e.g "Neutron(1))
But yes, the device gives sysex control over the Neutron

Hey Johnbootyful
I had a quick look yeah, but the problem is not lying where I thought... which is totally weird. Might be a Max bug that happened during patching.
Anyway, I just need to have a deeper look at my patch... but I didn't really had time to do it, sorry. Will do asap.
(btw, this bug also personally annoys me...)

There's still a numbox filling up the undo

Hey Andreas,

Sorry I havent noticed your message earlier.
I'll patch an update with more articulations asap (and no I didn't promised anything previously).

@rockguycris: and I'll fix this color thing at the same time


Thanks for the heads up Funkatronics.
It's easy to patch a floating window. I'll let you know if take a moment to do it before you do.


hey johnbootyful
I'll have a look at this issue and post an update. I think I know what's happening.

Awesome. I haven't compared with commercial 3rd party plugins yet, but empirically the measurements look correct.
What about making it as a floating window?

Hey bgerkes,
I noticed something unexpected a few days ago. My Neutron midi port was suddenly changed from "Neutron" to "Neutron(1)" in osx audio&midi setup and thus in Live too. The result is that this device didn't work anymore of course as it connects to the midi port called "Neutron" by default.
Can you check what your Neutron midi port names is?
I'm gonna update the device to let the user chose the midi port from the device. It'll be less convenient as you'd need to do it overtime you load the device (unless you get some max knowledge and know how to edit it), but at least it'll work no matter what the midi port name is.

Hey Rozze,

Yeah for sure. PM me from the ableton forum maybe? My username is Valiumdupeuple. or by email by adding after Valiumdupeuple and @, of course.

Wow, awesome job!
You should definitely send it to Christian Kleine (maxforcats).

I didn't look at your device, but isn't the [poly] (and not [poly~]) object supposed to manage voices?

v2 is here !!!!!!!

I just did a test and I don't get any latency here.
You probably have a plugin that introduce latency on your source track.
And I also did a phase cancelling test, just for the fun, and obviously it cancels out perfectly. So 100% exact same quality.

Hey JeremySiegel,

Honestly I can't tell you anything specifics about the latency, as it's something totally dependant on Live's API, and M4L isn't absolutely perfect with timing. That's just the way it is implemented and I can't do anything about this.

About quality, it's just the same as routing from a track to another one, it's just a bus. It uses the Live API and not some Max objects to send the signal.
So even though I haven't done a phase canceling test, I'm 100% sure there's absolutely no difference between your orignal source and the resulting routed signal.
So no quality loss whatsoever.

Hey BG23,
good catch! I'm fixing this, thanks for letting me know!

Hey Orangeslice

This device is not meant to record e.g Mute automations but to add missing shortcuts to get a better mousiness workflow.
So what's happening here is that you're recording automation for the e.g Mute button of Futility, which creates a conflict when playing back afterward.
The buttons on the device have to be automatable to be key/midi mapped, that's just how M4L works, but that's not the point of this device.
I'm gonna edit the device's description to make this clear and warn about automations.

It's also not meant to be used on a single track, but globally. It just works on the currently selected track.


Hey Kuzma
Sorry for the laaaate reply.
I know with this happens. It only affects eCo-m (midi version).
I'm going to fix this, but the downside is that when the target instrument is switched off and then eco-m turns it On, the first note might get lost. This isn't a big deal when creating, but you might need to take this into account when performing.
In theory I'd need to very slightly delay only the 1st note, but atm I haven't found any reliable solution. Maybe I'll find a trick.

Device update.
You know why it didn't worked as intented?
Because I'm stupid, so I didn't freeze the device correctly.

Hey Audioguy,
Sorry I didn't notice your message.
No worries, that's the beauty of M4L !

@Brianboston, why not simply rack 2 instances of Outist in 2 different chains, and crossfade between them?

While installed on your system, I'm pretty sure Live isn't pointed to your Max 8.0.2 application. Please check your Live preferences.
If you're on Windows, use the device on its single midi channel, with the channel output set to your neutron port.

Hey broah,
The Scale mode display on Push can't be accessed for tracks that uses Scaleton. That's the only solution Iv'e found to avoid a loop when automating a scale change within a clip (normally the Scale button should be unlit, and pressing it should select Scaleton if not's already selected).
Just go to Device mode on Push and choose your scale from the device. Doesn't work?
Which Live/Max versions are you using?
Are you using the correct Scaleton version (there's one for each Push model)?

thanks OCH, will check your update.
I'm probably update Futility with new feature at some point.

Hehe ;-)
What about this one CaligulaCuddies:


Yeah I like puns.

v1.4 fixes the "doesn't work inside rack" issue.

I'm aware of this issue, this is due to the fact that I'm populating the articulations in a hack-y way in order to have them displayed on Push while still being able to change them dynamically.
Simply selecting an other track and going back to your original one is another way to solve this "bug", no need to save.

Yeah, this is an issue with computer keyboard mapping and the way the live.button behaves. I have to patch something to hack this behaviour.

Sorry, I haven't notice your message earlier. Is it solved for you?
Do you have exclusive solo activated in your preferences?

Good idea about the punch in/out.
Yeah I probably could make the [rsmpl] optional.
Let's wait for the next update.

Hey Broah,
I suppose having you Cthulu track monitoring set to On isn't an option?
Unfortunately I can't guarantee that this kind of interaction with other M4L devices won't happen.
I'll have a look though, but not in the upcoming days as I'm on a tight deadline.
For the time being I suppose you'll have to live with this annoying Live start up issue.
Coming back to you asap.

Hey Broah,
I could look at the device initialisation and timing things, but I've never experienced this and you're the first and only reporting this.
Do you have any other M4L device that could interact with in your template?

@ mcnaggers
Do you mean a dry/wet ?

Hey bdumaguina
That's very straightforward:
- Put the device before your e.g Kontakt.
- Enter your articulations' names and their corresponding note number in the settings window. Click save and you're done.
- Now you simply change your articulations/keyswitches by drawing automations (the articulations names appear), from the device menu chooser, or from Push (were the articulations names are also displayed).

Track chooser issue is solved.

To those who don't have the right track names appearing in the drop-down menu: are you using L9 by any chance?
This device needs Live 10.

Hi dudes,
Sorry, it looks like there's an issue with the last update.
I'm just coming back home; fixing this asap.
Sorry for the hassle.

Glad to hear that Foule.

"don't work correctly on a bus track with reverb
Minor midi glitches on midi track when using kontakt (don t know it s maybe the time it listens before stop or some..)"

Hi Foule.
I can't reproduce here with return track. I'm surprised as that's how I mainly use it for a few years now, and I've never seen any issue in this area. Let me know if you can find a clue.

about Konktakt. What kind of glitch?
Due to its nature, the first note of a midi instrument has to be delayed by a very very very little amount of time by eCo, because eCo obviously has to turn the instrument On before sending the incoming notes. This delay should be unnoticeable though.
If you could be more detailed about your issue, that'd be of a great help.


"The only thing is that eco turns the plugins back on when you press play and then does not turn them back off if it receives no incoming signal?"

Hi Perken, good catch!
Reproduced here, only with the eCo-m.
Actually, with no incoming signal, eCo turns on, not when starting playback, but stopping it. Can you confirm?
Then it doesn't turned off.

Fixing this asap, thanks a lot for pointing it out!

Hey Broah.
I'm thinking about making some kind of a short teaser, but not sure I'll have time to make a deeper video demo. The wild amount of spatialisation you can get out of this shit is pretty impressive, and I'm not sure yet if I could manage to make a short enough (i.e not boring) video that can be representative of its capabilities.

That's partly why I've decided to patch a free lite version, which hopefully gives a good idea of what the full version can do.


I'm glad this sweet words are coming from you!
I've sent you a mail.

Such a great idea!!!!

Really really interesting device, can't wait to try it out!!

The device is working. There was an issue due to a stupid mistake of mine in the latest update of the device, but it's all fixed now.
People never come back to say "yeah it's fixed", because we usually talk through emails.

Can't wait to try this out !

Hi Stamp,
I'll have a look into that, but not sure when...

Nice device. One little problem though:
Passed 125 ms, the delay parameter stops working, the sequencer stops running actually.

BTW, modulating the Size parameter from the matrix fills up Live undo history. I didn't look inside the device yet so I can't help more for the moment.

Wow ! I haven't came across such an incredible synth since... Oki Computer ! I always had somewhere in my head the wish to replicate it in M4L some day... But thanks to you it's now done, and how great it is !
Mind blowing, you've just stopped me from going to sleep.
Amazing piece of software, I'm astonished.
IMHO there's no good synth done in M4L except for Granulator, Phase Distortion Synth, and your BlitterSynth.
I love it.
Thanks a lot for sharing this.

The undo problem doesn't looked solved actually.
But great device.

Hi Christian,
I don't know if you noticed it, but this devices crashes Max 7 (and Live/M4L using Max 7 editor).

Hi Hemau,
Nice update.
What I was actually suggesting with the highlighted_clip_slot and the floating window ideas was a way to make this device "universal". Like, you put it on any midi track and it can step record on any selected clip on any track, no need to use several devices.
And as you use .js it would maybe be even easier to monitor what midi is arriving into Live.
The midi is always monitored by the device and simply fills the selected clip when desired with steprecorder.
This way it would really work as a fully integrated Live feature. No need to put and map one device per midi track.
Cheers, and sorry for the late reply.

Dickheads, well...
Patch created in Max 7 are backward compatible, but there's new objects and some of them are not backward compatible, because they make use of new technology.
So if your Max7 patch uses one of this new objects, ti won't work in previous version, and that makes complete sense ihmo.
These incompatible objects deals with stretching and pitch manipulation mostly, and this RevStretchR is based on this.

Yep, fixed. Excellent device !
I've noticed another thing though. If you use more than 1 device in the same set, it looks like the buffers are shared or something between devices.
So we can't really use more than a single device per set.

(using Max 7 of course)

Hi Ithkaa
For some reason the device doesn't work in Live. It records the audio, but the playback never starts.
It starts working when it's in edit mode, but not completely though. Only the first buffer plays.
It doesn't look like soothing is missing from the patch, but I didn't invest a lot.

Hi Hemau,
I didn't test the updated version yet. I don't know if it's what you fixed, but there was a bug with the "chord" function.
And, in this regard, I think the method you're using is not perfect... It would be really cool if we didn't have to select the number of notes we need in our chords. Simply add the last played note(s) as a step. I think it's just a matter of defining a "time gate" for the chords as we never really play all the notes of a chord in perfect synchronization; if the patch watches for the last 50ms and group the notes that'd be all good.

Hi Hemau,
I can't why you had problem with the "live_set view highlighted_clip_slot clip", there sure is a solution. That would make the device so much more useful.
Yeah, easy to make a floating window.
Maybe we should discuss this by email or PM.
I'm "valiumdupeuple" on ableton's forum. PM me there.

Those kind of patches can be really useful.
Unfortunately it's not possible to change Live's GUI elements color without feeding the undo history.

Taking the velocity from the incoming note would be cool also!

Hi Hemau,
This is a great device. However, I instantly though : "why not simply use the detail_clip or the highlighted_clip_slot to select the clip you want to record in?". It would be much more simple; just select the clip with your mouse and it's ready.
So I opened your patch to modify that, and discover that you're doing all the magic in a .js object... and unfortunately I don't know anything about js coding.
If you use "live.path live_set view detail_clip" each time a clip is selected it will send its id (and automatically be the one where the step recorder points at); but I think (from what I can understand in your js) that you're not directly using the clip's id to feed your function. Would it be possible to modify that ?

I think that the way the duration and length values are labeled is not very clear. Musical values would benefit imho.

Having the device as a floating window would also makes much more sense.

I'd love to help improving this device; if you need so I can, except for the js part...


Hi Oddeo,
No, but I could add that quite easily. The thing is: you won't be able to edit in arrangement without your screen even if you had this timing information display. That would be a huge step backward in music creation/production ! That doesn't make a lot of sense IMHO. Push is way better that using any other controller or you mouse+keyboard to play with the session view, which is a kind of an "instrument" view. The arrangement is here to edit,arrange... and things that hugely benefit from a screen.
The idea of my device is to be able to leave the mouse + keyboard as more as possible in arrangement and use Push instead. But the screen is unbeatable for arrangement !

I'm still amazed by this wonderful synth.

Yep 3phase. BTW you can download a fully functional demo version of the device on my website (link above). The device will just disappear after 10 minutes and you'll have to reload it to test it more.

Funky device !

Well done, nice cleaning of the Lil'midienvolepe device/concept.

Acually the device doesn't always work correctly. Most of the time the left/right gain reduction is applied but not the panning.
I didn't really examine the device, but it simple and it might be a simple bug.
I'll have a look and let you know.

Hi ssrmpc.
This is a great device, however, you should just made the 2 pan knobs "stored only" because as it is now, it conflicts with the automations and thus the BTS/ BTA buttons as soon as something is recorded.

Well done Sir !

Exporting the wavetable did already work. But of course I didn't thought about just dropping the file to load it :-)
BTW, so now I guess that it's the only way toward it. No way to save a (pencil-drawn) user wavetable in the device itself as part of a preset ? If you use a custom waveform, save a preset of the synth, you have to drag the saved (exported) waveform each time you load this preset (I mean ableton device preset here, inside the browser). That is not the most convenient thing, but...

Don't know if I'll test the 1.1 version tonight, I might need to go to sleep at some point.
I'm totally blown away by your synth ! Noise machine from hell !!!

And the sound of course. Unique synth.

Well, sure there are things to clarify, but with this kind of audio toys I like to scratch my head around what's not obvious.
But, here's one question I didn't explored and like the answer without head scratching:
I find that I can save my wavetables if I "draw" them with "instructions", great. But, is there a way to save a pencil-drawn wavetable ?
Congratulation, those envelopes! the modulation tab! the layout, the feedback routines... huge !!!!

Hi Pechmann.
I'm discovering your synth, and I'm quite excited, awesome work !
I guess in a few hours I'll take some time to understand some of its concept but for the moment I'm just having great fun.
Well done!