Rui Nuno Capela

the expected offset should be the one reported by JACK API for the input port for which the audio clip was recorded from, that is: 2048 + 438 = 2486!...

> I agree with you about "-I 438 -O 438" it's the same as using "-I 876 -O 0" in my case. no, it is not, and I 'm sure...

ok. may you redo all your tests with qtractor >= 0.9.13.20git.https://github.com/rncbc/qtractor/commit/3b02b9 ? let me tell you that all your kind efforts on this topic are very much appreciated many thanks...

getting somewhere... please retry with qtractor >= 0.9.13.21git. https://github.com/rncbc/qtractor/commit/4f0a6d thanks

for recording, the number of periods is irrelevant for **input latency** compensation; the number of periods is only meaningful for **output latency** calculations, being this exactly one shown on the...

i understand all that, but to keep the whole story short I'd say it again: when recording and/or overdubbing, make sure to keep the frames/period setting (buffer-size) to an absolute...

try whether turning off Help > Configure... > Options > Use desktop environment native dialogs makes any difference.

what is exactly your system/desktop environment? kde/plasma, gnome, xfce, unity, etc.? what is the display server back-end? is it plain standard x11, or is it wayland or mir ?

then what about jack? what's the environment you have to run jack? - is it jack1 or jack2 is it jackd (classic) or is it jackdbus? - what do you...

have you tried it all without starting a2jmidid ? or not running jackdbus at all? eg. `killall jackdbus; chmod a-x /path/to/jackdbus;` and then run `jackd` from a terminal command line...