Andrea Bondavalli
Andrea Bondavalli
you can try to increase the latency, for example to 256 frames: `./run_latency_test.sh S16_LE 48000 2 60 256` If this is not working, you can try to double the latency...
I don't have this board so I cannot test directly. Can you report the output of: `cat /proc/cpuinfo` and `uname -a`
I don't see anything evident unfortunately. Everything seems ok.
I used a NanoPI NEO2. uname -a ``` Linux nanopineo2 5.8.8-sunxi64 #trunk SMP Sun Sep 13 01:50:54 PDT 2020 aarch64 aarch64 aarch64 GNU/Linux ``` In enclosed the kernel config I...
> Any ideia why? If I specify e.g. 64, the test is still done for 128. Is it an Alsa thing? The driver works with a tick frame size set...
If you change "tic_frame_size_at_1fs" to 48 in _test/daemon.conf_ you can run a test with 96 frames and this is the minimum latency I could successfully achieve on a NanoPI NEO2...
The reason I decided to set the "tic_frame_size_at_1fs" to 64 in the default configuration was to keep the driver ALSA interface usable via JACK (number of frames between JACK calls...
Thanks for sharing. This is interesting information.
> I've made a test on my Server with 2 x Xeon L5640 (24 Cores). It's running Ubuntu 20.04 LTS with Kernel 5.4.0-109-generic. Compiled and runned Latency test. Everything was...
it worked for me with last kernel of 5.9.x. So my guess is that the problem started at some point of 5.10.x. When we find where the problem started it...