You are here

Add new comment

rncbc's picture

i also agree this could be systemic to the jack/firewire (ffado) interface, specially re. that some or all capture ports have distinct latency added relative to each other.

ardour does have some magic to compensate for this disparate port latency when recording, provided the firewire jack backend fills in each port latency properties in its own right.

qtractor doesn't give a damn to latency compensation, yet. you'll have to bump recorded audio clip offsets to replicate ardours compensation, i guess :) well, that is to say that latency compensation is a completely manual operation on qtractor.

did your friend said that it is using two (2) firewire devices, probably in a daisy-chain setup ? i'll suspect the trouble is in that circumstance--half of the total input ports may get somewhat delayed (ie. fixed latency) when compared to the other half.

ask your friend to try with only one device at a time, probably recording only 8 tracks at once, and see what gives?

also, please, show here the complete output of `jack_lsp -plL` ...

cheers