Seems a rather huge Input latency value to me. Home comes ? 
Maybe you should also show us how your audio buffers (and any inputs) are set in your Focusrite control software.
tbh I’ve never modified anything there, do you think that might be the problem?
as for the buffers on my focusrite, I said on the original post that I lowered them already, they’re at 32 now, but I think originally they were at 256. when I lowered them originallyI tried going down one level at a time (I recorded a take at 192, another take at 128, and so on)but none of them made a difference
Yeah… 32 buffer shouldn’t give a latency anywhere near as high as that.
If you up the buffer back to 64 or 128 is it the same?
And to be sure, is this the only selectable entry for Focusrite 2i2…it’s not like an additional core audio setup that’s aggregating some other device??
like I said on the other reply, yes, 64 or 128 give me the same results
and as far as I know this is the only entry for focusrite 2i2 but I could be missing stuff
you can correct me if im wrong (I might be) but I dont think this is a latency issue? things get their own fucked up version of “recorded” as I play them, without any delay
I’m not talking about results, I’m asking if that extremely high latency changes with a different buffer setting.
If your audio interface is reporting a latency that’s about 4 or 5 times higher than it should be then it certainly indicates something is wrong with your audio setup. So yeah, it’s a latency issue in that respect.
and as far as I know this is the only entry for focusrite 2i2 but I could be missing stuff
If you go to the pulldown menu it will be obvious if there is any other entry for Focusrite…it seems unlikely but I’m not exactly sure how Mac audio works.
Also always worth reinstalling the drivers for the interface if you’re seeing something odd like this.
I just did it and it did change but it just went higher. at 32 its at 30.454ms, at 64 it goes to 31.179 and at 128 it gets to 32.630.
as for the pulldown menu im guessing youre talking about the one for Asio drivers. there I only see options for the Scarlett and for built in audio, so yeah, nothing else.
again, correct me if im wrong, but I said before that everything gets recorded well on other DAWs so I dont fully understand what reinstalling the drivers would do?
sorry if im starting to sound dumb, but ive been fighting with this for so long that my brain is a bit fried
It’s a tricky one to diagnose but that input latency just isn’t right and that comes from the driver not from Cubase. Not my place to correct you if you feel it can’t be that because it works in other DAWs. Best of luck.
I just tried it for the sake of it, but input latency is still at 30ms
We could do with another Mac user with a focusrite to confirm this isn’t some oddity of the way latency is displayed in Macs.
On windows to get it to that kind of figure I need to up my buffers to the max 2048.
And input is usually lower than output at buffers under the highest settings.
Have you maybe tried Cubase safe mode? This is about the last thing I can think of atm.
no, I havent tried that, tbh never heard of it. what is it and what would I be doing with it?
Judt start Cubase with those keys held down, select disable program preferences, the see if the latency is the same.
I don’t really think it could be this as behaviour looks different than usual, but could you also check the Mac mic privacy settings allow Cubase to use the mic (which affects any input)
I did the safe mode thing but sadly nothing changed. I also checked the privacy settings and they already were enabled
Ok, so considering the input latency weirdness we now discovered, it seems like Cubase is picking something else as the Focusrite inputs, which is confirmed by the input capturing actual audio, and you hearing the “noise of your fingers plucking the strings”.
Can you try recording again but this time you speak or sing loudly. If your voice is on the recording then the inputs may be mixed up with your computer’s integrated microphone.
There is no other explanation.
Mac uses Core Audio (instead of ASIO) which aggregates all devices as one, and if for any reason it has decided to map the integrated microphone as a Focusrite input, then this would explain why the latency value is higher than expected (because it uses the buffer size of the integrated device and not the Focusrite one).
Since I am not a Mac user I will not be able to help much, but there is one thing that is required on Mac is to go into privacy settings and allow Cubase to access the microphone so that USB devices can work properly (I don’t remember exactly what the setting is called but it’s something like that)
hey, so I did try recording voice as one of the first things when got this problem. to be honest, its a shame that I cant describe the sound well due to a lack of vocabulary on my part.
when I recorded voice the day I did it with a mic and the results were similar to the ones I got from instruments, when it does get a sound, it is heavily distorted, saturated, and sort of crackling ? not to mention the weird way it cuts frequencies. again this is when I get sound into the track, which is usually like really short peaks, like getting slapped on the face? the rest of the track is silence.
about the privacy settings,
as you can see here that was the last thing I checked and it was already enabled
I do think you might be onto something, but since im not really techy person I cant think of any other ideas regarding the core audio thing you just mentioned. if you happen to know more about this stuff please let me know.
Hi,
Have you tried to increase the Buffer Size?
I figured what the problem was, and my gut feeling about this being a dumb mistake was right. the place where I usually check microphone connections didn’t show this.
turns out Mac has a “Standard” and “voice isolation” modes, the whole time I had this problem was because it was set on “voice isolation”
as you can see, switching to standard also lowered the input latency considerably
now, as to why it didnt affect my recording on GarageBand, I have no idea, but I have too much stuff to catch up on to take the time to think about that.
I will leave this post up in case anyone ever has the same problem as me since many of the answers were really helpful things that I would not have checked otherwise
thanks to all people who replied and im sorry for wasting your time with a problem that had such a silly solution
6 Likes