04-02-2020, 02:23 AM
(04-01-2020, 10:19 PM)I got the behringer 202 as suggested, and in setup it had borderline latency, and then something died and now the instructional videos all say "audio renderer error." So I went to the Behringer site to download the driver, and asio4all was all there was. Not impressed just yet.jamjam Wrote:(04-01-2020, 02:58 PM)Suedseele Wrote: Has anybody a positiv experience with ASIO4All device? I cant use it. I get only 'NoLatency' in the device check. Do I something wrong?ASIO for all is kludge to make WDM devices appear to campatible with ASIO driver interface. The problem is that it has lots of IO jitter and therefore does not work well for low-latency. Anyone serious about playing virtually real-time low-latency, should get audio interface that natively has ASIO driver (other than Focusrite - it usually works well), or WDM_KS (kernel Streaming) driver. For Macs, usually no special driver is needed, but some audio gear do have CoreAudio optimized driver.
Regards Stefan
One more thing, with ASIO for all, you do not know the real IO latency of the device. This is the same for WASAPI or DirectSound based audio interfaces (used with builtin mics and headphones). That is why we cannot report the actual latency from those devices.
