User Details

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

Devices by kenan

Launchpad Mashinator Version 0.4
Midimashinator Version 1.0
Jumpinator Version 0.5
Knobinator Version 0.1
Modulatorinator Version 0.4
Paraminator Version 0.2
Spin Cycle Version 0.1

Total Downloads: 4,709

Comments by kenan


Are you trying to map the crossfader? For some reason it is immune to mapping. Even the native M4L devices don't map it. You might try combining Midimashinator with the Spin Cycle device--Spin Cycle has a special button explicitly for controlling the Crossfader.

Just uploaded Spin Cycle, a device that lets you move the crossfader, or any other dial or fader, at the press of a button.

What version of Live are you running. The mappings save for me on Live 8.3.4.

Okay. There's something odd about the Live crossfader because the mapping routine that I'm using doesn't seem to work with the crossfader. The factory MFL devices also don't map to it. Can you map Modulatorinator to the crossfader? If so, what version of Live are you using?

@jeffromusic What is it you're trying to accomplish? What would you want to happen when you restart a modulation that you stopped halfway through?

Just downloaded the beta 9. I'm assuming @OS is referring to the MultiMap device--but I've only just begun my exploration of Live 9 so maybe there's another device I haven't found yet.

MultMap and Knobinator are similar in appearance but have completely different functionality. In terms of functionality, Modulatorinator in manual mode accomplishes the same thing as MultiMap. Of course MultiMap doesn't have a curve setting or a global.

With the Knobinator, the mapped parameters don't move in tandem with the Knobinator Knob, but instead each parameter fires when the knob passes a user specified threshold. I often use Knobinator to control the Grid amount on the Beat Repeat. I might only want 1/32, 1/16, 1/8, and 1/4 grid values--I don't want to use the 1/24, 1/12, and 1/6 values wich are nested between the values I do want.

To accomplish this I map Knobinator to the Grid control, turn off Multiple (since I only want to control the Grid dial), and then using the default threshold distribution (the Dist. button), I set the following in the On Value boxes starting at the bottom: 47, 47, 60, 60, 77, 77, 97, 97. Now as I turn the Knobinator Knob, the Grid control only moves between the desired values. It skips 1/24, 1/12, and 1/6.

Hope this helps explain part of what the Knobinator can do.

It's not a copy, but it might have the same functionality as a 9 factory device. I haven't installed 9 yet so I can't say for sure. It would be nice to have a factory device that does this so that I don't have to maintain this one.

Just uploaded version 0.4. Some cosmetic changes as well as a few plumbing tweaks. The key new feature is the Momentary/Toggle button. By default, buttons are momentary, but you can switch to toggle mode where the button stays on until you press it again to turn it off.

I wanted this feature so that the Mashinator could support both roles in a row on a Launchpad. In particular, I wanted to mix both types of buttons and didn't want some buttons managed my Mashinator and others midi-mapped. That also wasn't very portable when building and saving custom racks.

Also, I needed toggle support for the Modulatorinator. I wanted to press a Mashinator button and have the modulation run for a bar or so and automatically turn off when complete. The toggle mode is perfect for that.



I've uploaded a new version which fixes that bug. Check it out and let me know if you have any other issues.


Glad you're enjoying Midimashinator.

Just record your button pushes into a regular MIDI clip in Live. When you play the clip back, it will reproduce your performance. Midimashinator just needs note on/off data in order to operate.

I will look into the device not working when automating. I didn't spend much time testing how the device handles automation since I automate it with MIDI clips.

Let me know if I misunderstood your question.