But the only way to find out for sure is to do some loopback tests.
There is some real time processing, which will create latency of its own.but this latency is probably very very small compared to the IO Buffer.īut anyway, even though you don't see it in that number doesn't mean its not happening. I suspect that the Process Buffer has to do with the way midi is processed in real time as it comes into LogicPro, before it actually goes into the channel strip. That 10.7ms number is the amount of latency required to process your audio, in addition to midi. That variable amount of latency is not reported at all in that 10.7ms number you see. Fortunately midi latency is less than 1ms.the main problem with midi latency is that its not consistent, so you will hear people talk about jitter. There is some inherent latency in the midi connection over USB already, that latency is also not reported in the audio preferences value you see. The latency would be most likely in the midi.and it would be hard to test because it would be a factor of how much latency is there between when you press a key on your keyboard and hear a sound. It doesn't necessarily mean there isn't some latency happening, its just not represented on that dialog box in the number you see. Apple does say in their own docs that it can increase latency somehow, but no more information then that is provided.
We get no such indicator for the Process Buffer Range. That's why the audio preferences actually displays that value to you so that you know. A larger buffer has exactly that much latency added, calculated precisely based on the size (in samples) and the sample rate. The other buffer, the I/O buffer, has to do with the size of audio buffer that is passed to the sound card. SMALL is probably the one to use, but if you start having weird problems, then bump it to medium or large to see if the problems go away. So I just leave it on LARGE all the time now.īottom line, I wouldn't worry about it.
I have noticed that with certain extreme tasks with lots of midi traffic and lots of stuff in the environment, a SMALL setting resulted in dropped notes sometimes and when I changed it to large, then all the notes went through. The environment processes midi outside of the normal plugin process block.so this setting MIGHT be related to that environment processing and perhaps you will not notice any difference whatsoever unless you are doing tricky things in the environment? Speculation. The truth is there is hardly any real information about this setting. Basically I am speculating too now, hehe. Its quite possible that the environment itself could have a bit more latency when using the large setting.but that playback from tracks to instruments would not have that problem at all. No idea if those discussions had merit or were speculative also. There are some old discussions from a decade ago where people talk about some subtle midi timing problems unless they use a small setting. My own experience is that I don't notice any additional latency when I use the large setting and pretty much leave it on large all the time. That doesn't mean its not there, you would need to do some loopback tests to find out, but its not indicated as any kind of value anywhere in LogicPro. Change that value in preferences and the reported latency does not change at all. Supposedly it could be adding more latency, but there is no indicator anywhere in LogicPro that would show you how much more latency it is allegedly creating if you use say, the large setting. You can find numerous discussions about it in this forum and mentions about it various articles on the web are all kind of vague and in my opinion, speculative. There is very little clear information about exactly what the Process Buffer Range is to be honest.
0 kommentar(er)
