Skip navigation

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

746 Views 10 Replies Latest reply: Jun 9, 2012 10:42 AM by Pancenter RSS
rbdavis Calculating status...
Currently Being Moderated
Jun 7, 2012 11:12 AM

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.

  • Pancenter Level 5 Level 5 (7,505 points)

    Are you using plugins on the tracks or are you bypassing the plugins.


    It could be some plugin causing latency or it could be Logic's antiquated (but processor efficient) buffering scheme.


    Do you notice a slight delay on the first note played (from MIDI controller) when switching software instrument tracks? That's because the buffers aren't active until play is pressed or a MIDI note triggers the software instrument.


    Try selecting a plain audio track (not record ready) before exporting.


    What is your (Preferences/Audio/General  Plug-in-Latency  Compensation:)   set to?

  • Pancenter Level 5 Level 5 (7,505 points)

    I'm not referring to your audio card nor the type of audio latency you mention, "plug-in latency compensation" is something entirely different.  Nevermind, I think you're happier just complaining.

  • chorleyman Level 4 Level 4 (1,415 points)

    Yeah, of course you're talking about the plug-in latency - this kind of thing is beginning to pee me off now because there are usually perfectly simple ways to rectify the result of whatever function of Logic you've used when it doesn't quite match up to expectations, so the fine details seem like a laboured point.

  • chorleyman Level 4 Level 4 (1,415 points)

    I'm not sure you understood my point, but I'm glad you've found the solution, thanks to Pancenter. Logic is a complicated beast and I don't expect any software of this nature is ever going to be all things to all men - there are improvements that I'd like to see, but on the whole I think its a pretty good piece of software.


    If I were an audio engineer (rather the the lone musician that I am), I'd want to work cross-platform, but I'm happy.

  • Pancenter Level 5 Level 5 (7,505 points)

    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.


More Like This

  • Retrieving data ...

Bookmarked By (0)


  • This solved my question - 10 points
  • This helped me - 5 points
This site contains user submitted content, comments and opinions and is for informational purposes only. Apple disclaims any and all liability for the acts, omissions and conduct of any third parties in connection with or related to your use of the site. All postings and use of the content on this site are subject to the Apple Support Communities Terms of Use.