wilx Posted February 16, 2007 Share Posted February 16, 2007 Specifically, setting 'bypass effect' automation on any track is behaving oddly. Whatever automation I set happens about a bar and a half before it's supposed to. So say I've automated a distortion plug-in to start on bar4, beat3 for two beats. What happens is the distortion comes on - for the correct duration, but starts and ends earlier than it should. What's going wrong!? EDIT; tried the same stuff in a new Logic song, and the problem did not occur. I'd still like to find out what's happening though, as I want to carry on using the project in question. Quote Link to comment Share on other sites More sharing options...
Fred B Posted February 16, 2007 Share Posted February 16, 2007 Have you tried 'Sample Accurate Automation' in Preferences > Audio > General ? Quote Link to comment Share on other sites More sharing options...
wilx Posted February 16, 2007 Author Share Posted February 16, 2007 didn't work - it must be something reasonably simple if just one Logic project exhibits this behaviour... Quote Link to comment Share on other sites More sharing options...
wilx Posted February 17, 2007 Author Share Posted February 17, 2007 And if it helps - it seems to just happen with 'bypass' automation. Quote Link to comment Share on other sites More sharing options...
wilx Posted April 24, 2007 Author Share Posted April 24, 2007 This problem has just resurfaced, this time with Volume automation on the master output track. I've set an automation dip from normal volume to silence, then back up to normal again, but when playing the track Logic dips and raises the volume about half a second earlier than it should. The volume fader falls before the SPL reaches the automation dip, and rises before the SPL reaches the automation raise. I'm totally stumped, and it's a cripplingly annoying problem, so anyone with any suggestions, please chip in! Thanks. Quote Link to comment Share on other sites More sharing options...
David Nahmani Posted April 24, 2007 Share Posted April 24, 2007 I haven't had that problem. One thing I've noticed is that automation starts behaving oddly when your song start marker is placed before 1 1 1 1. I always leave mine on 1 1 1 1 since, and start the song on Bar 2 or 3 if necessary. I have never run into automation problems since. Could it be your problem? Quote Link to comment Share on other sites More sharing options...
wilx Posted April 25, 2007 Author Share Posted April 25, 2007 The song starts at 1:1:1:1, and there's nothing particularly significant or different about this project and the couple of others that have started to exhibit this fault. Is it worth ringing 'official' support? It's as ridiculous as it is frustrating, but I can't think of any possible cause... The problem doesn't happen on other tracks though - just on the output track. Aside from this, I have Solo buttons enabled in all tracks, but whenever I load one up they aren't there, despite saving the track with them in. Logic can be so bloody frustrating at times! Quote Link to comment Share on other sites More sharing options...
Fred B Posted April 25, 2007 Share Posted April 25, 2007 (edited) You're not alone. I've also experienced that bypass automation occurs too early. See this thread http://www.logicprohelp.com/viewtopic.php?t=3698&highlight=automation So I think it's just a (sporadic) bug. Edited April 25, 2007 by Fred B Quote Link to comment Share on other sites More sharing options...
Logic lost Posted April 25, 2007 Share Posted April 25, 2007 (edited) gay Edited April 25, 2007 by Logic lost Quote Link to comment Share on other sites More sharing options...
wilx Posted April 25, 2007 Author Share Posted April 25, 2007 motherfucvk u all read my post about au or il be pissed off cunts. how rude. wilx from crc? No idea what 'crc' is, so I'm guessing no... Quote Link to comment Share on other sites More sharing options...
Logic lost Posted April 25, 2007 Share Posted April 25, 2007 ah well ul get over it no time for formalities Quote Link to comment Share on other sites More sharing options...
Fred B Posted April 26, 2007 Share Posted April 26, 2007 Just wanted to add that with some testing I've found that bypass automation in general is too early by 1/16th to 1/24th note at 120bpm, which corresponds to about 100msecs. It may be called a bug or just an inaccuracy. Quote Link to comment Share on other sites More sharing options...
monkeystrike Posted June 24, 2007 Share Posted June 24, 2007 even the sample accurate automation in logic is everything else but accurate. it's a known problem we'll just have to live with it - see it as a funny surprise "will it be tight this time, oh please god...." Quote Link to comment Share on other sites More sharing options...
ski Posted June 24, 2007 Share Posted June 24, 2007 motherfucvk... I wonder if that's the Latin spelling. Anyone? Quote Link to comment Share on other sites More sharing options...
David Nahmani Posted June 24, 2007 Share Posted June 24, 2007 He must have thought I would censor bad words... which I don't. I find most audio professionals are usually reasonable and if they want to use one of those words, it's usually for a good reason. Quote Link to comment Share on other sites More sharing options...
meyermal Posted November 4, 2011 Share Posted November 4, 2011 Hi everyone, in some of my sessions the automation of my output start ahead of itself: volume fades out before the automation does. Why is that. Thank you for your help. .christian Quote Link to comment Share on other sites More sharing options...
Eriksimon Posted November 4, 2011 Share Posted November 4, 2011 HOW ABOUT the remote possibilly-bob-ety that there are some LATENCY inducing plugins inserted on Aux channels? Weren't there some issues with latency compensation on buses, in conjunction with automation? Quote Link to comment Share on other sites More sharing options...
remix6 Posted November 4, 2011 Share Posted November 4, 2011 Hey mate, Try clearing your system PRAM (it's cured a few random unexplained Logic bugs for me at times) - might work for you.. http://support.apple.com/kb/ht1379 Quote Link to comment Share on other sites More sharing options...
BenjaminOe Posted June 18, 2021 Share Posted June 18, 2021 HOW ABOUT the remote possibilly-bob-ety that there are some LATENCY inducing plugins inserted on Aux channels? Weren't there some issues with latency compensation on buses, in conjunction with automation? This right here! I also experienced that the automation for bypass parameter responded ahead of time instead of on time. Turned out I had only set Accurate Automation to. "Volume, Pan, Sends" and needed to turn on "Volume, Pan, Sends, Plug-In Parameters" Solution: Set Sample Accurate Automation to: "Volume, Pan, Sends, Plug-In Parameters". [found under Preferences>General] You may also need to have your Plug-in latency set to Compensation: "All". I am not sure about this, so don't hang me up on it, but it works for me. [Also found under Preferences>General] Quote Link to comment Share on other sites More sharing options...
ralphonz Posted October 27, 2021 Share Posted October 27, 2021 Damn, I'm getting this problem still in 10.7. It doesn't seem to matter what I set Sample Accurate Automation to, my automation plays about ¾ bar too early! I'm trying to finalise a mix so there's like a billion plugins and busses. It's most obvious with mutes but it's happening with delay throws etc too. The wierd thing is I could have sworn it wasn't doing this a coupe of weeks ago, but now it's stuck like this no matter if I restart... Quote Link to comment Share on other sites More sharing options...
koryjgregory Posted June 8, 2023 Share Posted June 8, 2023 damn im still having this problem with bypassing plugins thru automation now. what a bummer 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.