On 4/5/19 6:15 PM, Robin Gareus wrote:
If you meant that App1 is latent, and App2's
input-port is connected to
the sum of App1's output and the HW's capture port. Then the latency is
ambiguous (jack reports a range).
If App1 doesn't introduce a latency. App2 will see a single value for
the capture-latency on its input port.
jack does not include a "delay in the wire" to align paths. JACK is a
patchbay. It provides mechanism for efficient inter-application
connections, jackd itself does not enforce a policy on the user.
Yeah that's my issue, the latency problem can't be solved.
Maybe jack would be clearer without the port's latency and a simple way
to query the audio driver latency.