Logic Pro 9 Editing Automation



What is the best way to edit automation with extreme precision?
Using the mouse to move automation nodes in a track, even at the maximum zoom setting, still only allows editing in increments of 0.2-0.3dB in volume, for example.

Isn't it possible to nudge automation data with greater precision? Or to type in an exact value of an automation node?

Thank you for any advice....



Open the Automation Event List and do it there (key command only.)
I was afraid someone would say that!
Had forgotten where to find that command since I've used it so rarely.

Is there no way to do more precise editing graphically via a modifier key or something of the sort?

No. Afraid? What, you have a problem with numbers? :)
Actually, I don't think you can get as much precision in the Automation Event List Editor as you can using the mouse with the correct new modifier key (I'm not in front of Logic now...). I tested this very thing and several - at least two - increments of mouse move were available for a single numerical value in the list...

I don't know which modifier you mean but I am not finding one that gives me better precision than the A.E.L.

Anyway I have a basic rule: Never do anything moving a mouse that you can do by hitting a key.
The method for adjusting track automation graphically in finer increments is pasted below (I got this from the forum). In any case, I think most users would adjust track automation graphically, not by opening a list editor. That's why Microsoft adopted Windows and why we like Macs! You can get multiple values graphically for each numerical valued in the list - in other words, the list doesn't provide access to the interim values between the 128 listed values, though Logic obviously stores that information somewhere, and it can be edited with this technique:

"If you're using TrackAutomation HyperDraw (and adjusting nodes with the mouse), then the track height makes a difference regarding what resolution you can move the mouse. If you hold down Control (you have to press this key AFTER you hold down the mouse button, otherwise you'll get the contextual menu), then you can slide nodes up/down in those finer increments no matter what the track height is.


JonPerl, thank you for that tip. The Control modifier key does indeed allow 0.1dB increments, which is an improvement. It's a little awkward to press Control after the mouse click, as normally modifier keys work the other way around, but I can get accustomed to that oddity. It's still too bad that one can't just numerically enter a value on the point.

I much prefer graphical editing to list view editing of automation, mainly because a graphical view is closer to how I "see" music. On a more prosaic level, it's also important to be able to edit the automation against the background context of the waveform. In the list view, I feel like I am editing blind to a certain extent.

Another strange issue with the Automation event list. Volume automation is expressed in decibels in the graphical view (when one moves a point, one sees the value). However, in the Automation Event List, the volume is converted to a value in the 0-127 range, just like MIDI CC Volume. So it's still impossible to enter an exact dB value.



Revisiting this old thread here...

There seems to be an inconsistency in how Logic handles (non-MIDI, track) automation.

One can indeed edit such data numerically with the key command for "Automation Event List". What seems inconsistent is that the resulting edit window looks exactly like the regular Event List window (which is accessed by either the Lists button and the Event tab in the Arrange window, or via the keyboard shortcut "Toggle Event List"). Yet the former window shows track automation such as volume, while the latter does not. Is this apparent inconsistency an oversight?

The simplest solution would be to have the regular Event list also be able to show track-based non-MIDI (Logic native) automation, and there would no longer be a need for the other Event list which is only accessible by keyboard shortcut.

Or am I missing an obvious point here?