Volume automation not working

Hi. Last week I opened mixes of an EP that was done about a year ago, the release had been delayed and some small tweaks were requested before the tracks get sent to mastering.

These mixes have a large amount of volume automation going on, but on opening them suddenly none of it is working. The Yellow lines in the automation lanes now have values that look like MIDI numbers rather than a DB measurement, and the faders simply do not follow the written automation.

It's equally strange that when I move the mouse to the automation select dropdown menu within the track, it suddenly switches to a grey line with no data written into it. My original volume automation is now stuck on a yellow line which does not appear to be connected to the channels volume functions.

Has anyone else experienced this? Do you know the cause, or more importantly the solution?

I currently have a very impatient label waiting for me to deliver these tracks and it's getting very tight here.


Kind regards


Tim

Logic Pro X, OS X El Capitan (10.11.6)

Posted on Oct 13, 2016 7:11 AM

Reply
6 replies

Oct 13, 2016 11:24 AM in response to Myownbadself

My guess is that it might have something to do with the implementation of the checkbox in the Project Settings I just showed you, which I think didn't exist a year ago. That functionality is a little tricky about what it does in the background. Maybe the new Logic version interprets the data differently and messes things up.


To further troubleshoot that issue, you have to do some open heart surgery on Logic and for that you have to understand the implementation of Track Automation, which lives in a "parallel universe" inside a Project. It is basically an additional Arrange Window "layer" with Automation Regions that contain the Track Automation Data (which are Fader Events) the data you see on the Automation Lane.

You cannot view the content of those Automation Regions in the standard Event List, it has its own list called the "Automation Event List" that you open with the Key Command ctr+cmd+E. It looks like the Event List, but pay attention to the name in the Window Title Bar. When you have the Project Settings Window open and toggle that special checkbox, you will see the status of the Automation data change between Fader and Control. This is only a playback function, where Logic decides where to route the data to. My guess is that in your Project, it actually changes the Fader Events on the Automation Lane visually to Control Events.

User uploaded file


And in case you haven't seen that before in Logic:

While the Automation Event List is open, open a new Main Window (cmd+1). What you see now is your Project, viewing only the Automation Layer, all the Channel Strip Objects with their Automation Regions. You can even open the standard Event List pane on the right and edit the Fader Events like MIDI Events.

I explain that in more details in my Logic book "Logic Pro X - The Details". This is definitely something that is not mentioned in the official User Guide or find in any other Logic book.


Here is a screenshot of the Main Window showing those Automation Regions. It is the same Project from the screenshot above. Again, pay attention to the Window Title Bar, it tells you the hierarchy, what you looking at, in this case the Automation level. Now if you click the "Leave Folder Button", the button with the arrow above the Tracks List, you will move back to your standard Tracks View.

User uploaded file


Hope that helps


Edgar Rothermich - LogicProGEM.com

(Author of the "Graphically Enhanced Manuals")

http://DingDingMusic.com/Manuals/

'I may receive some form of compensation, financial or otherwise, from my recommendation or link.'

Oct 13, 2016 10:38 AM in response to Myownbadself

It sounds like you are looking at MIDI Volume data (CC#7). However, the Automation Lane can only display Track Automation data and not MIDI Volume (which would be Region Automation. That type of data has to be contained in a MIDI Region. Technically there is a way around it, but not meant to be.


Make a copy of your Project an try the following

See if the following checkbox is enabled: Project Settings ➤ MIDI ➤ "Control Change 7/10 controls Volume/Pan of channel strip objects" This will direct CC#7 data to the Volume Fader

User uploaded file


You can convert Region Automation (CC#7) to Track Automation (Track Volume). However, you have to select the Regions first, or use the second commands to convert All.


User uploaded file


Hope that helps


Edgar Rothermich - LogicProGEM.com

(Author of the "Graphically Enhanced Manuals")

http://DingDingMusic.com/Manuals/

'I may receive some form of compensation, financial or otherwise, from my recommendation or link.'

Oct 13, 2016 2:13 PM in response to Myownbadself

Sorry, but I have to ask: is automation turned on? It's only visible when you hover over Volume (in this case)

User uploaded file

If it was too obvious I apologise 🙂


Maybe try to convert the automation to another type and back again: To do this, hold ALT key and select Pan from the Volume menu. Choose Convert in the dialogue, and then convert back to volume. Might re-assign the curves to that parameter ...

Oct 13, 2016 10:38 AM in response to EdgarRothermich

Hi Edgar, it very much looks like it may be CC07 data, but the thing is when the tracks were first mixed that data was written in as track automation, not as midi data. That's what's so weird. It's just upon reopening the project after a year that it's now in what seems to be a midi format that the faders won't respond to. Do you have any idea what has caused this and how I can get Logic to recognise the data in the original track automation format?

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

Volume automation not working

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.