(Link to petition for Apple to fix this bug: http://chng.it/bfczxYTh9g
)1. Automation in Logic (Pro X 10.4.8) is not plug-in delay compensated on audio/instruments tracks
(but on aux tracks/summing stacks).
In other words, once you're working with latency-intensive plug-ins, even instruments (e.g. VPS Avenger) or just being an UAD user, your automation is basically out of order. This is also true for Logic's own Linear Phase EQ for example, no additional 3rd party plug-ins needed. Just automate a low or hi-cut, the automation will be nearly around 100 ms out of time in this case.2. Plug-ins that depend on beat-time information (MIDI synced to the host) are simply not compensated on aux tracks/summing stacks
(but on audio/instrument tracks)
In other words, if you are using something like Output's Movement, LFO Tool, Pumper, Effectrix, Cableguys plug-ins... , you name it, on an aux track/summing stack - timing of the beat-time based plug-ins will be out of order. I know several producers using a ducking or gate-effect bus for such effects - timing won't be correct then. This is also true for Logic's own Phat and Step FX for example.3. Side chain signals aren't compensated correctly
The external side chain signal isn't compensated when introducing latency generating plug-ins after the side chain receiving plug-in on audio/instrument tracks (e.g. limiter after compressor with external side chain).
The external side chain signal isn't compensated when introducing latency generating plug-ins before the side chain receiving plug-in on aux tracks/summing stacks (e.g. tape simulation plug-in before compressor with external side chain).
If you are using the FabFilter Pro-L 2 with external side chain triggering for stem mastering for example, the side chaining will be completely out of time moreso when using one of the oversampling options. This is also true when working with Logic's own Linear Phase EQ and Compressor on one track using external side chaining.4. Bounce in Place is not compensated correctly at all
Bounce in Place does not take automation and plug-in delay compensation correctly into account especially when bouncing aux tracks/summing stacks (see above). Pure chaos, depending on what is going on on your tracks and busses. External side chaining is ignored when using Bounce in Place as well. So you have to use the export track or bounce to disk function and drag your files back again into Logic, cubersome.
The typical pop/EDM producer who uses ducking plug-ins or classic side chain compression in combination with latency intensive plug-ins basically gets a fuzzy timing. Also every UAD user pretty much is in trouble when using automation in Logic because the workarounds to avoid these issues are almost impossible - or you just don't use automation / side chaining at all. If you add multiple bussing and sends to the equation, it's clear that big mixes in Logic go completely off the rails.
This reminds me a lot of Ableton Live from 10 years ago. That was an absolute pain in the ass to work with for complex professional mixdowns at that time. Anyway, all of the above works perfectly in Cubase or Bitwig, for example. Even in Ableton Live (except for the MIDI synced plug-ins), everything is now in time, even if you are working with several hundreds of ms introduced latency in complex routed projects.I think that Logic (Pro X 10.4.8) is by far the worst DAW on the market today in terms of automation timing and plug-in delay compensation.
Any thoughts, insider knowledge or solutions on these?
iMac 4,2 GHz 64 GB RAM | macOS (latest official version) | Logic Pro (latest official version) | UAD Apollo | Endless list of plug-ins and samples