depthofallthings wrote:Just gave that a try, still sends it all the way to the bottom
I upgraded to 10.7 recently, and today I noticed a huge bug with automation. Apple was able to replicate the issue and after a few hours determined that everyone on their team has the same bug (even users with Monterey). Now my case is with the engineering team.
Here's the issue. If you have any gradual automation change set over 50 seconds, it will drop out down to the lowest or highest value if it's a gradual increase or decrease. You can test this out by creating any new track and setting a volume automation of -inf at the beginning of your project, then 0 dB about 4 minutes in. Scrub your playhead from start to finish but watch the automation value readout on the left panel. You'll see it dropping out incrementally. Some is more noticeable than others, depending on how drastic the change in value is. Please note that this affects ANY type of automation. Bear this in mind if your projects have been sounding a little strange lately or if you're hearing things change quickly where it shouldn't.
Here is a gif video:
If you are also experiencing this problem, I recommend reporting to Apple so they are able to gauge the impact. I can see this being a big issue for a lot of us being how common and simple this type of editing is. Please let me know if you find any good workarounds other than rolling back the Time Machine. Thank you!
EDIT: I have found a slight workaround, still not great. The issue seems to happen between two single points of automation set over 50 seconds. You will have to place automation waypoints along the slope within 50 seconds and it will not drop out. Unfortunately, it will drop your automation to the lowest point, so you'll have to eyeball where it needs to go back up to. There seems to be yet another bug. If you click on the middle between two points, it doesn't just simply add a point.
tiedieshred wrote:I have 10.7.1 and I am still experiencing this automation problem....
David Nahmani wrote:tiedieshred wrote:I have 10.7.1 and I am still experiencing this automation problem....
Ugh... Sorry to hear! Can you attach an example of a simple project that does that? How to attach files to your post
tiedieshred wrote:I opened a new project and I was able to use automation no problem. It is in an older logic project (November 3 2021) that I am experiencing the automation issue. It is not a simple project but I can maybe take a video of it not functioning or something. Using touch to control the volume automation doesn't work either. I am not tech savvy FYI but I do own your Logic 10.5 manual!
David Nahmani wrote:tiedieshred wrote:I opened a new project and I was able to use automation no problem. It is in an older logic project (November 3 2021) that I am experiencing the automation issue. It is not a simple project but I can maybe take a video of it not functioning or something. Using touch to control the volume automation doesn't work either. I am not tech savvy FYI but I do own your Logic 10.5 manual!
Great! Always good to hear.
Maybe it's because the automation was created in a buggy version of Logic. I wonder, what happens if you just redraw the automation now? Like remove one point and recreate it.
If you want to attach a project, you can save it as a copy, and in the copy, delete all tracks and regions but the one necessary to showcase the issue.
David Nahmani wrote:You're welcome!
polanoid wrote:If I may chime in here: There's conflicting Track and Region automation in the example project. A track automation node at the project start wants to set the volume to -1.3 dB, whilst a region automation node at the same position wants to set it to 0.0 dB. This is asking for trouble, even if "Region Automation takes priority over track automation" is switched on (as the automation nodes are at the same position). You definitely should delete one of those nodes, otherwise chasing won't work correctly (starting playback at 1 1 1 1 will set Volume to -1.3 dB, starting from a later position will set it to 0 dB).
Apart from that the example project's automation plays back just fine here (10.7.2 on Monterey)