12-15-2016, 03:29 PM
(12-15-2016, 12:34 PM)dwrae Wrote: Since the app/driver does not run in the kernel as real-time thread, lower than 512 is not possible indeed. It's still heaps better than the hundreds of milliseconds delay you get with Android though. One thing that may help is rooting the device and enabling the root tweak such that the USB audio thread can run as a real-time thread, but it's unfortunately still no guarantee.
I actually consider this as a good news!!! I thought that "normal" low latency, like 128 samples, is possible with USB-driver and thus there was something wrong with my gear/tab. But it's good to know that it's the actual implementation/method that's the limiting factor when it comes to latency.