I tested it by routing the output and input with a physical cable. I was surprised.
I have to edit the offset to 0 in the clip for alignment.
That is, with the integrated sound card in my computer and Pipewire, the offset that Qtractor performs isn't necessary (in fact, it's counterproductive). I suppose this is because Pipewire has already performed it.
As I said, all of this is beyond me due to its complexity.
Another surprise: there are still misalignments when the loop is activated, despite having a standard kernel and no audio configuration.
However, with the standard kernel, the misalignments between tracks in playbacks without loops disappeared.
PS
My test indicates that you were right; the place where the user should be able to specify the compensation is in the recorder, in this case Qtractor, thus bringing order to all the different latencies and compensations that can arise from different combinations of sound cards, kernels, audio engines, etc.
PS 2
Another curious thing.
jack_iodelay gave you 4250, and that was correct. I got 0 (the latency tool in Cable is just an interface for jack_iodelay), and that was correct too.
I tested it by routing the output and input with a physical cable. I was surprised.
I have to edit the offset to 0 in the clip for alignment.
That is, with the integrated sound card in my computer and Pipewire, the offset that Qtractor performs isn't necessary (in fact, it's counterproductive). I suppose this is because Pipewire has already performed it.
As I said, all of this is beyond me due to its complexity.
Another surprise: there are still misalignments when the loop is activated, despite having a standard kernel and no audio configuration.
However, with the standard kernel, the misalignments between tracks in playbacks without loops disappeared.
PS
My test indicates that you were right; the place where the user should be able to specify the compensation is in the recorder, in this case Qtractor, thus bringing order to all the different latencies and compensations that can arise from different combinations of sound cards, kernels, audio engines, etc.
PS 2
Another curious thing.
jack_iodelay gave you 4250, and that was correct. I got 0 (the latency tool in Cable is just an interface for jack_iodelay), and that was correct too.