Protone

I don´t. I can´t believe that after all these years Logic has been around you still can´t trust automation to move correctly (or at least with same logic every time) when you drag regions around. That must be one of the most fundamental and basic tasks almost everybody does daily, and they just can´t make it right. Here is just one example from today that made me start this thread (sorry for crappy image quality...): https://www.dropbox.com/s/6w7rhx7nk6ssh5h/IMG_0484.MOV?dl=0 In that example I move 3 blocks with automation. Where does the automation disappear from the 2nd block??? Not to mention what happens to automation curves at the original location... Makes me mad! This crappy behaviour is manageable when you operate on one track and you can just watch the automation and repair the damage manually. But when you have a project with 100+ tracks and massive amount of automation on each track, copying a whole section of a song to another location is a fu**ing nightmare. Have you found reliable ways to move automation? I would like to know if there are any known workarounds or if maybe a completely different workflow (instead of dragging regions) could lead to more reliable results. Thanks.

I recently started a thread about my problems to cycle through midi parameters in main window using key commands. It appeared that those parameters are now all under region automation, and I did finally get my shortcuts to work the way I want. (Thanks to David and Eric!) BUT cycling through these parameters is super laggy and buggy now. When ever I choose to show the region automation, I get the beachball for couple of seconds. And while the region automation is visible, each time I change parameter to view, same thing. Does this happen to anyone else? Or can you smoothly view region automation parameters, without pauses and beachballs? -Pete

Must be a bug of some kind... I changed from track to region many times using key commands, and it didn´t help. But after clicking the automation button it started to work again. Thanks Eric.

OP here... For some reason I can no longer "cycle through used parameters". This is weird, I am 95% sure it used to work for a while after updating to 10.4. The actual key command is "Automation: cycle through used parameters". It does nothing. I tried changing the shortcut to different key, but it didn´t help. To be clear, the problem occurs when I am in the main window, select a region, and then make sure the automation is showing region automation. When I try to cycle through used parameters, nothing happens.

Got it. Thanks.

The shortcut key that I have always had for showing different midi parameters of a midi region (sustain pedal, mod wheel, etc etc), now only toggles track automation view on and off after updating to 10.4. I can´t find a way to show midi data of a region at all in main window. I now have to double click the region and open piano roll to be able to see and edit mod wheel automation for example. This is way slower than before, and allows me to only see one region at the time. I think it´s crucial to be able to see and edit midi data in main window when you have large orchestral arrangements, and you have to write and edit lots of (midi)automation. Can anyone confirm this behaviour? Hopefully I am just missing something...

I am having hard time with logic (10.3.2) surround panner and levels. Let´s say I have a mono source, lead vocal for example. I insert gainer (mono to stereo) as a last insert just to make the track 2channel for easier panning between LCR. I don´t know if anyone else does this, but I find it easier to do this way if I want to spread a mono signal from C to L+R. Now, if keep both channels 100% centered (spread 0), OR if I make it 100% LR (spread 60), I get identical output level. But if the spread is anything else between 0 and 60 degrees, the output is louder. Is this how the panner is supposed to work? If someone knows a reason why it definitely should behave this way, please explain me! Does anyone know a way to automate a mono signal to move from center speaker to L+R in a way that does not have any effect on overall loudness? So that when a the master is downmixed to stereo, there would be no change in the sound at all while this one track moves from C to LR? Do I make any sense? Because if I do the automation described above, the loudness rises when the audio starts to spread, and then finally lowers back to original level when spread reaches 60 degrees. I have tried different panning laws, btw. -Pete

I have a scoring project that is over 40 minutes long, and consists of more than 100 tracks, most of them with volume automation. I need to make some tempo changes, so I need to lock regions and automation to SMPTE. Regions are easy, but only way to lock automation seems to be track by track in "automation event list". It would take forever that way. Is there any way to lock all automation at once?

Thanks for your reply danyg, but no, I am not confusing anything. What I mean is that new region based automation should control clip gain and not the channel fader to be useful. That's how it works in Protools, and its brilliant. The clip gain we have in logic does not allow you to draw automation. But that relative automation sounds interesting, I have to check that out!

I was sooooooooo happy to hear that logic finally has protools style clip gain. Except that it doesn't, the region automation controls the fader just like regular volume automation. What the...??? Can someone give ONE example of a situation where this beats clip gain automation? At least in my workflow (in ProTools), the whole point of clip gain automation is to control the levels before channel plugins. Another great thing about it is that I can automate the clips as much as I want and still have my channel free of volume automation (to be able to move the fader where I want) until the time I actually want to automate it. Maybe there is a reason to do it Logic-10.1-way, but until someone points that out to me, I think they blew it!

I have been trying to find an answer, but I haven't. Is it possible to prevent Logic from zooming the track when you hit A to show automation? I mean it's fine if the track is very thin, then it's ok that it zooms in to be able to actually see the automation. But when the track is already zoomed in, hitting "A" makes it huge, sometimes wider than my display. I like to keep my tracks quite large all the time, and I like to toggle automation mode a lot, so this "force-zoom-to-way-too-wide" makes me nuts. It wasn't like this in LP9. -pete

Thanks istation! Finally someone to confirm this behavior! So I´m not crazy after all! Funny, I think I have tried all key combinations, but not in that order. I work in PT too, and there you always have to press + hold keys before mouse buttons… Anyway, good to know how to make it not snap. Still don´t get why it snaps with all the other key combinations, since there is no point snapping to original position, EVER!

What the …? Here it always snaps to the original position, no matter what settings I have, no matter if the original position is on a grid or not. Really, all you guys can drag a note just few ticks without problems?? Here is a blurry video that hopefully shows what I am talking about: https://www.dropbox.com/s/qbc7e427htul7sl/snap.MOV

No, thats not what I mean. Even when the snapping is off or you hold ctrl, midi events snap to their orig. position if you try to drag them very close. It's like magnet... I can't explain it better than this with my non native english...

Snapping midi events to their original position in piano roll is still unfixed! No way to turn it off! It is impossible to drag midi events small amounts because they always snap to where they were before. As a workaround you have to first drag them too far, let go, and then drag again back where you want them. I don´t know if some of you think it´s a good feature, but I can´t think of a situation where I would need it. I mean if I decide to move the event in the first place, isn´t it obvious that I want it anywhere but to the place where it was?? If I want it to be where it is, I don´t try to move it!! This feature should be called "automatic undo when fine tuning timing". Other than that, nice update!