I'm wondering if this happens to anyone else. Sometimes I will double click on an automation line and the value that the line is at will be changed. For example, if I am automating a lp on EQ eight that is set at 10kHz, when I double click on the red line it will turn to a value like 9.89kHz (then becomes tedious to get it back to the original value even using the ctrl key). This happens with native plugins/fx, external vsts and softsynths without rhyme or reason. This doesn't cause my program to crash or anything so I don't have crash files to send to support. Anyone have this problem? Is there a way Ableton can fix this?
I am on a pc running windows 7, i7, 4gb ram on Live 8.2.6.
Automation lines changing values
-
florian_bl
- Posts: 92
- Joined: Wed Oct 12, 2011 3:53 pm
- Location: Austria
Re: Automation lines changing values
It's not just your computer. This happens to all of us. It's the same in ProTools btw. I don't know about the other DAWs and I have no idea why this is happening, but it's "normal" 
-
Warrior Bob
- Posts: 841
- Joined: Mon Apr 06, 2009 5:10 pm
- Location: Central Coast, California
- Contact:
Re: Automation lines changing values
This is the case for me too, I believe it's just part of how Live's automation interface works. I personally find it fiddly and difficult to use - a few keyboard shortcuts for things like "don't change the value on this or that axis" (such as are common in graphics software) would go a long way.
Re: Automation lines changing values
Undo (Ctrl+z)
Re: Automation lines changing values
This doesn't help when it changes the value every time I double click the lineyur2die4 wrote:Undo (Ctrl+z)
It's weird because I didn't have this happen with Live 7 and it didn't do this for the first few updates of 8 either.
It's not a huge issue, but it does bother my workflow/ocd at times.
-
AaronShaver
- Posts: 82
- Joined: Sat Nov 01, 2008 7:08 pm
- Location: Portland, OR
Re: Automation lines changing values
Yep, happens to me all the time. I'll double a track volume line and it'll move to -0.2 db instead of staying at 0.0 db. Annoying.