Why does Logic Pro 9 add 0.3s silence at start of all my tracks when I "export all tracks as audio files"?

Question

OK - when I "export all tracks as audio files" it works fine - I get a load of exported tracks (annoyingly with the stupid "_bip" prefix at the end).
But I find that they all have about 0.3s silence inserted at the start. WHY??!!!
I checked, and on the timeline all the tracks start with their first note at the beginning of the track so there is no silence in the arrangement. But still this silence on export.
This Logic feature is so badly designed - why can't it do the simplest things as expected.

Answer 1

rbdavis wrote:
Thank you I will look into plug-in latency compensation. However, there is no latency or need for latency compensation when outputting offline files in this way. Latency compensation is for live playback where real-time processing matters. So this is flawed software design, hence my comments about it being illogical.
"there is no latency or need for latency compensation when outputting offline files.....etc"
You don't fully understand how Logic's audio engine and buffering scheme works... not that anyone fully does except the programmers. Basically your above statement is incorrect, as some plugins have built-in-latency and others don't, but that's not the complete picture. The problem is a combination of a plugin's built-in-latency and how Logic buffers data. Logic deactivates the audio engine when stopped, all plugins and software instruments become deactivated including the ability to load or purge data buffers with the exception of a software instrument or audio track that is selected for "live" input.
(Look up Plug-in-Latency Compensation in the manual for a full explation of the choices available)
I won't disagree with you about the software design, however, rather than flawed I tend to think of it as antiquated. The positive side of this is extremely low processor use and the ability to design templates with all plugins and software instruments loaded and ready to start a new project. The downside most Logic users are familiar with...  unexpected overloads in the middle of a project when a approaching a region that makes use of processor intensive plugins, Loops that don't match up perfectly when starting a project from bar 1 and/or missing notes at the beginning of MIDI loop if starting at bar 1.... plus a half dozen other anomalies related to Logic's "efficient" audio engine. The efficiency concept made sense back when computers didn't have enough power to handle active or semi-active plugins, seems it causes more problems than not these days.