Device Details

Device Overview

Name/Version: Knob Twiddler .999
Author: opticon93  
Description: Hi Folks,

Long ago, I decided that I wanted an artificial knob twiddler that would simulate what a human "could" do with a knob, using their Thumb and Index finger.

Most humans can't twiddle a knob like an LFO. Even when humans are doing things quickly, it's still smooth sweeping for a droid.

Back then, my favorite version was a certain setting of Robert Henke's "LFO Zero". It had a bunch of Smooth, some Jitter and a lot of MSP stuff. Unfortunately, I couldn't use too many of them because of the big CPU hit.

Later, I found Synnacks LineFO and figured some things out... Use MAX instead of MSP.

Most importantly, this device uses a MAX object from Karlheinz Essl's Real Time Composition Library. I can definitely use more of them.


Usage:

Map to your Live parameter.

[Nodes] determine the number of breakpoints between minimum and Maximum.

The Value row gives the Min/Max values of the mapping.

On the Speed row, decreasing the [Slowness] is equivalent to increasing the Fastness. I generally prefer to have the [Slowness] above 500 ms. If its smaller than that, it starts to get inhuman.

[Smoothier] rounds out the corners.


Enjoy

DownDate: Hi Folks, this is a much earlier version that I like more. The knobs take on the values of the target.
 

Device Details

Downloads: 714
Tags lfo, utility, other
Live Version Used: 10.1.14
Max Version Used: 8
Date Added: Mar 08 2018 10:17:18
Date Last Updated: May 17 2020 01:19:25
Average Rating -n/a-
Rate this device: (must be logged in to rate devices login)
Device Type: midi_device
URL (optional):
License (more info): None

Device Files

Device File: A KnobTwiddler 02.amxd
 


Comments

Hey, I was debating how to create something like this. Thank you. The output scaling was confusing at first (I assumed the Min/Max values were for the individual nodes), but it makes sense to me now. Much appreciated.

Thank you, I'm glad you like it. It is a bit tricky to describe. I think of the Nodes as "Complexity". I like medium complexity, with the nodes around 9-14.

This is quite handy; thank you for sharing it.

I've run across a problem with persisting settings: the "Min" and "Range" dials in the Values section both reset themselves to `0.24` when the Live project containing the device is loaded (and when closing the M4L editor window after viewing the device). I'm sure it has something to do with the `* 0.24` object feeding into both dials, but that's as far as I got.

Thank you! I'm glad you like it.

Its been a long time since I've dived into this one. I'm pretty sure the "0.24"'s are because I had difficulty getting the Current Value of the mapped parameter, so I set the knobs to 24% of their max value to be safe. Otherwise, they would randomly go to the max or min value when mapped.

I've had many problems when changing the attributes (max, min and current value) of a knob. For example, when any attribute is changed, the knob can no longer be automated correctly in Ableton. Ableton only remembers the original value of the knob. Nevertheless, I like this version better than the previous one.


Login to comment on this device.

[ browse device library ]