Hitrate
commented
7 years ago How are you checking the latency like that? I Wanna try the same experiment when I get home in a few days.
Thx
Torben Scharling
On 15 Aug 2017, at 22.28, Elieser Ademir de Jesus notifications@github.com wrote:
Reported by Chuck Vaughn (by email):
Jamtaba during its own local trip from instrument to the sound card, has too much latency, my buffer is 64 buffers at 48,000 so it is very low already...it can't really go lower than that...
my local monitor is many times faster than jamtaba's local monitor performance...
this is why i do not want to hear the jamtaba local monitor signal... also, the Jamtaba local monitor, over time, increases in latency ...which is not good...
it starts out at around 30 to 35 milliseconds delay, BUT - then it keeps increasing with more delay....every few minutes.. here is a snapshot of the JAMTABA local monitor signal showing 80 ms delay(RED) more than my own local sound card monitor(GREEN) - only after 10 minutes
just another update....it is an hour later and the Jamtaba local audio monitor latency is now almost 700 milliseconds of delay
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread.
elieserdejesus
chaseology
Reported by Chuck Vaughn (by email):
Jamtaba during its own local trip from instrument to the sound card, has too much latency, my buffer is 64 buffers at 48,000 so it is very low already...it can't really go lower than that...
my local monitor is many times faster than jamtaba's local monitor performance...
also, the Jamtaba local monitor, over time, increases in latency ...which is not good...
here is a snapshot of the JAMTABA local monitor signal showing 80 ms delay(RED) more than my own local sound card monitor(GREEN) - only after 10 minutes
just another update....it is an hour later and the Jamtaba local audio monitor latency is now almost 700 milliseconds of delay