giada
giada copied to clipboard
High delay between microphone and the metronome
Some users on YouTube (in the comment section of this video tutorial) report a latency problem during audio recording:
There is an annoying delay between my microphone and the metronome after I record a sample. Any way to fix this?
And:
I think the program has a serious latency problem. I have experienced the same problem at every buffer size with a high performance PC and excellent interface/mixer setup.
I played around with Giada on a Windows machine during coffee break at work, and indeed it has a crazy delay when recording from the mic. No such issues on Linux and Jack though.
Can confirm latency using pulseaudio on opensuse. Other programs, such as reaper or audacity, don't have any latency problems when using pulse
I too have experienced this problem. @tomek-szczesny and @BRFNGRNBWS, try the following: when the latency is crazy, open the Configuration window, change the buffer size (any value is good), close and restart Giada. The latency should go back to normal. I'm still not sure where the issue comes from, I suspect somewhere in RtAudio on Linux and the PulseAudio API.
I too have had this problem on a Ubuntu 20.04 system with hardware CPU="Intel(R) Core(TM) i9-8950HK CPU @ 2.90GHz" (reporting 6 cores & 12 threads), mem=64MiB and using Pulseaudio for the input/output/system in config. I tried it with setting buffer size from 1024 (default) to 2048 and 4096. Also tried setting "resampling" to "Zero Order Hold (Fast)" without being able to solve the latency issue. Not sure what else to try.
dpkg reports
$ dpkg --list giada
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description
+++-==============-==================-============-=================================
ii giada 0.15.4+ds1-1build1 amd64 Hardcore Loop Machine
@AJRepo thanks for reporting. Are you able to reproduce this or is it just random?
I am able to reproduce this.
RtAudio has been updated to version 5.2.0/6.0.0beta today (a71467fbf21ed99ab711761d982e4b019c2fd4bf), things might have improved now, at least in the development version.
Can't reproduce this one with new RtAudio 6.x, closing.