Diegel Posted November 22, 2023 Share Posted November 22, 2023 (edited) Running Logic 10.8 on 2020 imac with ventura using external ssd for the project. I have 1 track where the fader is lagging like 2 to 3 seconds behind the automation. I tried disabling all plugins and sends on the track but didnt help. I have sample accurate information enabled for everything in settings and latency compensation set to all. Any help would be much appreciated. Edited November 22, 2023 by Diegel Typo Quote Link to comment Share on other sites More sharing options...
polanoid Posted November 22, 2023 Share Posted November 22, 2023 Could you post the project, or at least a screenshot video showing the issue? Quote Link to comment Share on other sites More sharing options...
Diegel Posted November 22, 2023 Author Share Posted November 22, 2023 1 hour ago, polanoid said: Could you post the project, or at least a screenshot video showing the issue? Yep here you go. Exact same automation on both tracks and you can see how out of sync the fader is on the track labelled "BAD" in the mixer window. I removed all effects and sends and later in the video I tried disabling the automation on all other tracks to no avail. Quote Link to comment Share on other sites More sharing options...
Diegel Posted November 22, 2023 Author Share Posted November 22, 2023 I even tried making a new audio track with nothing on it but the automation and it is also out of sync with the good track (but perfectly in sync with the bad track that has like 2 seconds of latency). Quote Link to comment Share on other sites More sharing options...
Solution polanoid Posted November 22, 2023 Solution Share Posted November 22, 2023 (edited) This post was recognized by David Nahmani! "Nice catch!" polanoid was awarded the badge 'Great Support' and 25 points. Weird. Could you open the Automation Folder (use the key command, then do Cmd-1), locate the automation region on the track that is assigned to your "BAD" channel strip, and check if - for whatever reason - the region's delay parameter is set to anything else than zero? Edited November 22, 2023 by polanoid 1 Quote Link to comment Share on other sites More sharing options...
polanoid Posted November 22, 2023 Share Posted November 22, 2023 (edited) Oh and also check your MIDI defaults - I just noticed that if the Delay parameter is set to something else than zero, it seems to be taken over to the automation region of newly created tracks (which doesn't seem right to me 😉 ). I wonder if this is a new behaviour in 10.8? I will check with older versions. Stay tuned. Edited November 22, 2023 by polanoid 1 Quote Link to comment Share on other sites More sharing options...
polanoid Posted November 22, 2023 Share Posted November 22, 2023 (edited) 5 minutes ago, polanoid said: I wonder if this is a new behaviour in 10.8? No this happens already in 10.5. @David Nahmani, is this a known issue? Or is it even a - gasp! - feature? Edited November 22, 2023 by polanoid Quote Link to comment Share on other sites More sharing options...
polanoid Posted November 22, 2023 Share Posted November 22, 2023 1 hour ago, Diegel said: the bad track that has like 2 seconds of latency At your project tempo of 120 bpm that would correspond to a region delay of 1 bar. Quote Link to comment Share on other sites More sharing options...
Diegel Posted November 23, 2023 Author Share Posted November 23, 2023 14 hours ago, polanoid said: Weird. Could you open the Automation Folder (use the key command, then do Cmd-1), locate the automation region on the track that is assigned to your "BAD" channel strip, and check if - for whatever reason - the region's delay parameter is set to anything else than zero? Yep this is the solution. After opening automation folder (Ctl + Cmd + E) and then hitting Cmd+1, I noticed 3 tracks had the region's delay parameter set to +1/1. Now I just wonder how that happened in the first place. Quote Link to comment Share on other sites More sharing options...
polanoid Posted November 23, 2023 Share Posted November 23, 2023 17 minutes ago, Diegel said: Yep this is the solution. After opening automation folder (Ctl + Cmd + E) and then hitting Cmd+1, I noticed 3 tracks had the region's delay parameter set to +1/1. Now I just wonder how that happened in the first place. As I wrote, you probably have (or had) your MIDI Defaults set up this way. 1 Quote Link to comment Share on other sites More sharing options...
Diegel Posted November 23, 2023 Author Share Posted November 23, 2023 10 minutes ago, polanoid said: As I wrote, you probably have (or had) your MIDI Defaults set up this way. Those 3 tracks I recorded with logic on someone else's computer at their studio so I probably have to tell them to check it out on their computer. Thanks again! Quote Link to comment Share on other sites More sharing options...
David Nahmani Posted November 23, 2023 Share Posted November 23, 2023 14 hours ago, polanoid said: No this happens already in 10.5. @David Nahmani, is this a known issue? Or is it even a - gasp! - feature? Wow, definitely a bug. I was able to reproduce it. I'm reporting it. Thank you @polanoid! 2 Quote Link to comment Share on other sites More sharing options...
polanoid Posted November 23, 2023 Share Posted November 23, 2023 Fascinating that no-one on this forum seems to have noticed this bug yet, given that it is very old (maybe even always has been this way since the introduction of Track Automation? Can someone with access to very old Logic versions check this?) Quote Link to comment Share on other sites More sharing options...
David Nahmani Posted November 23, 2023 Share Posted November 23, 2023 Just now, polanoid said: Fascinating that no-one on this forum seems to have noticed this bug yet, given that it is very old (maybe even always has been this way since the introduction of Track Automation? Can someone with access to very old Logic versions check this?) I'm guessing most people wouldn't naturally have a Delay value set in their MIDI Defaults settings? But I agree that it's odd that this surfacing only now. I've reported it. Very nice catch. 🙂 1 Quote Link to comment Share on other sites More sharing options...
okok Posted November 23, 2023 Share Posted November 23, 2023 hi automation-timing issues have been a problem for very long. this is a huge problem now when exporting for dolby-atmos, since the automation-timing for 3D-objects becomes completely inaccurate. 👎 Quote Link to comment Share on other sites More sharing options...
polanoid Posted November 23, 2023 Share Posted November 23, 2023 1 minute ago, okok said: automation-timing issues have been a problem for very long. this is a huge problem now when exporting for dolby-atmos, since the automation-timing for 3D-objects becomes completely inaccurate. 👎 Different subject really Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.