Originally Posted by punani ➡️

Yes i hear u. But im not willing to spend 20.000 for a non professional musician. I record sometime for some guys and thats it. Everytime i thing ho yeah this is the **** something dissapointing comes up... This tascam uh 7000 must be a joy to play with but has no hiZ for e-guitars/bass... So i must use a DI thing... Steinberg ur44 sounds muff and dull compare to a RME babyface.. Oh my god... The more i dig the more i get stuck... I hate this researching

Originally Posted by eightyeightkeys ➡️

Having been a l-o-n-g time RME user in a pro studio, I recently sold the studio, scaled down and decided to go for an id14 mostly because any RME product is too much for what I need now.
Having said that, I didn't what to compromise on sound quality...at all... nor did I want ANY issues with drivers/latency etc under Windows 10. So far, so great ! Awesome sound quality and no issues at all on the driver/latency front. I record my own vox routinely and there is no perceptible latency...even when I'm max'ing out the VSTi's and having to use 2048 buffer setting.

Originally Posted by jkung ➡️

What kind of computer are you using? To get no latency while cutting vocals while maxing out VSTi is very impressive. You can't feel latency at 2048 samples? Am I confused?

Originally Posted by stella645 ➡️

No-one can not feel latency at 2048, it's around 50ms from the interface plus whatever plugins may be adding....he is using direct monitoring.

Originally Posted by jkung ➡️

didnt see he was using direct monitoring. if that is the case then any amount of vstis or how fast your computer doesnt matter.

Originally Posted by jkung ➡️

What kind of computer are you using? To get no latency while cutting vocals while maxing out VSTi is very impressive. You can't feel latency at 2048 samples? Am I confused?

Originally Posted by Amroth ➡️

Well, I got it all set up, really excited. Updated firmware and drivers, loaded up a session at 256 samples on PT10 and got crackles galore. Changed to 512 and still crackled. Only stopped it crackling at 1024 samples. Looks like I just don't have luck with interfaces :(

Originally Posted by Mantik ➡️

Hi Amroth, any news on your issue? I own the id14 too and came along similar problems.

Originally Posted by DistortingJack ➡️

What happens when you use the exact same buffer settings on the internal sound card? If you still get the same crackling, it's just your computer crapping out...

Originally Posted by Basspartout ➡️

Very interesting how different latency experiences are regarding the ID 14 and Focusrite.
Apart from my AMD Phenom six core PC with Win7 I tried the ID 14 with my Intel i7 Laptop Win10 from last year (both with 8 GB ram) and there the ID 14 worked significantly better.
So what was my choice? Getting a new (Intel) PC for my ID14?

Before I did that I decided last week to give the SPL Creon a try and behold: The Creon works exactly as good as the Focusrite 6i6 on my 'old' AMD.
So I'd say it is NOT necessarily my PC who's to blame here, right? It worked fine for three years now with the 6i6, why wouldnt it with another Interface.
It shows however, how it is always a matter of finding the right gear for your particular system and test your compatibilities.

The main crackling and latency problems with the ID14 on my system were caused
by Kontakt 5, especially when K5 reverbs were used, Addictive Drums 2, Arturia Analog Lab, Sample Tank 3. Interestingly enough not by UHE Diva for example.

And another interesting fact: all these VST mentioned produce some CPU peaks from time to time, visible in my DAW CPU meter (Studio One 3.2) BUT: they are not producing any crackles, meaning these CPU peaks are not audible with the Sacrlett or the SPL Creon.

The ID 14 is a really fine piece of gear, I'd say for the price you can't get a better sounding interface, it really sounds amazing, but the Windows drivers might not be as compatible as they could be so far.

Many thanks at this point to the very friendly and patient Audient support btw

Originally Posted by thx538 ➡️

Just for the record a new version of the ID App is out, with improved latency
(5.33 ms roud trip here @ 32 samples buffer size as reported by Ableton Live 10 under Windows 10 on a z170 chipset & i5-6600k proc.)

Originally Posted by thx538 ➡️

Just for the record a new version (4.0.0 dated 25/5/2018) of the ID App is out, with improved latency
(5.33 ms round trip here @ 32 samples buffer size as reported by Ableton Live 10 under Windows 10 on a z170 chipset & i5-6600k proc.)

Originally Posted by stella645 ➡️

OK...the v4 driver is a tiny bit lower latency than the previous but doesn't seem to work noticeably better under load.
So a fairly heavy project that was crackling at 256, but played ok at 512 was exactly the same with the new driver.

Nothing to get too excited about for most use tbh.

V3 followed by V4 measured results:





I did manage to run Addictive Keys piano at 16 samples as well as S-Gear amp sim just to see if it would run anything...but as 16 samples is only 1.1ms lower than 64 samples I can't get too excited by it.

Originally Posted by doom64 ➡️

I wonder how good 96 kHz is at 16 samples? Assuming that setting is possible. For that matter, how stable is it?

Originally Posted by ooowow ➡️

So the issue at hand for me is that my audient id14 interface has a delay when I try to record through my condenser microphone which is a Aston Origin.
My daw is FL Studio I have previously ran a gen 2 Scarlett solo with zero latency with no issues. But for some reason I can’t figure it out for my audient. The recordings themselves sound extremely clean but I can hear myself being offbeat compared to the instrumental. I’ve tried googling things many times also I have tried to use different modes such as (flstudioasio, asio4all, audientid14) etc.
If I can’t fix the latency issue I would at least like to turn off direct monitoring.