eMagnus wrote:
So the only thing the I/O buffer size effects is LATENCY correct?
Once I was bouncing midi to audio on a track that had a 3rd party plug-in. I kept getting clicks in the audio file. Everyone thought the issue was with the buffer size. Did they have any reason to suggest this?
Yes.
You can only empty and fill a water bucket so fast, the smaller the bucket the more times you have to fill/empty it. (the plus being it takes less time to do so, the downside is, it's more work.)
Think of the empty/fill cycle as your latency.
Something to consider... needing a low buffer is worthwhile for (mainly) two things.
Reasonable reaction time when playing a softsynth, -and- realtime monitoring of an audio signal through Logic's audio engine.
If you monitor out side of Logic you can raise the I/O buffer to 256, 512 or 1024 and give your computer a rest. I usually monitor via the interface's direct monitoring function and run that through a mixer with a hardware reverb unit. Generally leave my I/O buffer high so I don't have to worry about the many pitfalls of low latency monitoring.
pancenter-
p.s. Softsynth monitoring takes less time than monitoring an external audio signal. While monitoring a vocal with effects may need a buffer of 64 to be close to realtime, a softsynth can achieve close to the same latency using a buffer of 128.
p.s.#2 It's OK, or even a good idea to raise the I/O buffer when bouncing effect heavy tracks, or an effect heavy mix.