Low resolution automation quantizing

[tequila slammer]

I was recording some filter automation into the arrange page yesterday, and I hit on something quite strange. The resulting envelope only kept the uppermost and lowermost points of each curve.

I had previously recorded quite a few tracks of automation that session, and they'd all kept the detail. In the case of the problem track I could see the whole curve being recorded, it just hugely simplified as soon as I stopped recording.

I'm guessing there's some setting I've accidentally flicked, but I can't for the life of me think what it is. I couldn't research into it too much as it was about 1:30am

Any ideas?

I'm using an Athlon 64 PC and a Behringer BCR2000.

Thanks!

Ben

[tequila slammer]

Has no-one else ever seen this happen???

[Hedroom]

Something to do with overdub and looping whilst recording?

[DJ Tequila]

I've just got this problem on a plug-in.

There doesn't seem to be a setting which relates to it. Any ideas?

[luddy]

Maybe it's the tequila?
-Luddy

[DJ Tequila]

There does seem to be a lot of tequila around doesn't there?

In all seriousness, I'm losing all the subtlety of my automations. I can see Ableton drawing in all the lovely automation data as I twist the knobs and record, it just strips it out when I stop recording. It's really frustrating.

Why would this be considered a good default behaviour?

Why has extra code been put in to delete controller data?

Why isn't there a setting to turn it off?

How do I fix it?

Anyone?

[DJ Tequila]

OK, I've been given a fix by Ableton support - it's a text file called 'options.txt' containing only the following:

-_ThinningAggressiveness=0

It needs to be put in the preferences folder. Support say:

"You can open the folder like this:

In the help menu, choose "get support".
In help view, click the link: show preferences folder.
Restart Live thereafter for the option to take an effect."

I'll be testing it tonight.



I also got an answer to one of the 'why's. Apparently complex automation data is RAM intensive.

They seemed to like my idea of making the simplification (thinning) step an 'undoable' event. What do you think?

I can't believe I'm the only person who sees this as an issue...?

However, assuming it works, a big thanks to support for sorting it. Hopefully this post will field a few potential calls for them.