4 ms·
And even when it doesn't require it, we always want it. :-)
by iainctduncan 5y ago
And even when it doesn't require it, we always want it. :-)
- jancsika 5y agoAnd even when we set it, we don't get it, because we blithely read a "latency" label in a GUI instead of measuring the round-trip latency on the specific device in question.
- PaulDavisThe1st 5y agoThat wouldn't be correct either, at least half the time. Problem is that "latency" is used with different meanings, at least two: 1. time from an acoustic pressure wave reaching a transducer (microphone), being converted to a digital representation, being processed by a computer, being converted back to an analog representation and finally causing a new acoustic pressure wave care of another transducer (speaker). 2. time between when someone uses some kind of physical control (mouse, MIDI keyboard, touch surface, many others) to indicate that they would like something to happen (a new note, a change in a parameter) and an acoustic pressure wave emerging somewhere that reflects that change. The first one is "roundtrip" latency; the second one is playback latency.
- jancsika 5y agoHow do you measure playback latency? Is there a way that an end user can do it as easily as measuring rountrip latency? Edit: clarification. Also, is there some measurement being done to come up with the latency given in the following dialog? https://qjackctl.sourceforge.io/qjackctl-screenshots.html https://qjackctl.sourceforge.io/qjackctl-screenshots.html Or is that just the result of arithmetic for the given configuration options above it?