hi, in fact it's all quite the opposite:)
- each plugin must report their latency alone;
- qtractor compensates for for the total reported latency of all plugins inserted on that track and only (not others); the compensating track is played-back ahead or in advance (ie. the opposite of delaying other tracks;
- compensation is applied on a per-track basis, so tracks with different total plugin chain latencies get played pack in advance independently to other tracks.
hi, in fact it's all quite the opposite:)
- each plugin must report their latency alone;
- qtractor compensates for for the total reported latency of all plugins inserted on that track and only (not others); the compensating track is played-back ahead or in advance (ie. the opposite of delaying other tracks;
- compensation is applied on a per-track basis, so tracks with different total plugin chain latencies get played pack in advance independently to other tracks.
hth.
cheers