Smoother Automation curves when recording?

[COSM]

I might be overlooking something simple here, but I can't seem to figure out how to stop Ableton "smoothing" out the recorded automation from a knob tweak. It's averaging a lot of the subtleness of this certain tweak and drawing straight ramps, when there is a small amount of variation.

When recording, it adds in lots of anchor points, but as soon as it stops, it cleans it up again.

I would like this to not happen, ideas?

-Tom

[mode:masters]

hmm, i've not observed this in my clips but perhaps Record Quantization settings?

[d-track]

ive heard it is something to do with the options file. you may change some default setting

[mode:masters]

I went home and tried to replicate this, no go. Was working fine for me.

Did you get it sorted Tom?

[Mr-Bit]

Is it: preferences/Options


-ThinningAggressiveness=0

I also have

-_EnsureKeyMessagesForPlugins

Bit

[d-track]

i told you

[concept_control]

Good question Tom, I noticed this started happening when I installed .0.8 or .0.9 and was really hacked off, Maybe the reinstall deleted my prefs file come to think of it... hrmm. Either way info is surprisingly sparse as to how to remedy this and it should be an actual preference menu pulldown or something less rubbish. Maybe like quantizing notes, you could group some points and right click, smooth when required, rather than humping the subtlety from things as standard.

[Nokatus]

Live has done this for years, and it has always ticked me off. I think it's essential to make this setting visible in the preferences.

See my previous thread on this topic (with pics) here:

http://forum.ableton.com/viewtopic.php?t=98535

[cturner]

I ran into this problem recently while I was automating track envelopes in an audio track. I was drawing a sine curve with points at every vector of audio data (or however fast Live draws automation) and got a triangle wave as the result of its smoothing.

It appears that the algorithm considers a change delta from one point to the next and doesn't look globally at the waveform you've drawn.

I wrote this crude Javascript for M4L that will only pass through floats and ints at a specified interval, say every 50 or 100 numbers. Reducing the quantity of data increased the change delta between points, and so much more of the sine curve was drawn.

HTH, Charles

Code: Select all

autowatch = 1;
inlets = 2;

var drop = 0; // Start at every 100 numbers
var interval = 100;

function msg_float(n)
{
  if( inlet === 0 )
  {
    if( drop === interval )
    {
      outlet( 0, n );
      drop = 0;
    }
    drop++;
  }
  else
  {
    interval = parseInt('10', n);
    drop = 0;
    post("interval:", interval, "\n");
  }
}

function msg_int(n)
{
  if( inlet === 0 )
  {
    if( drop === interval )
    {
      outlet( 0, n );
      drop = 0;
    }
    drop++;
  }
  else
  {
    interval = n;
    drop = 0;
    post("interval:", interval, "\n");
  }
}

post("drop.js compiled...\n");