Forums
At the moment Qtractor does it for plugins and insert sends in a track. Putting a limiter with latency in a bus is not compensated.
How about including the audio bus that a track is connected to? I think of 2 lines in a track's "plugin"-tab instead of the one that's there now:
[ ] track trackname latency compensation (current value)
[ ] bus busname latency compensation (current value)
In this case it would make sense again to add the latency input for insert sends in buses.
What do you think?
re. Advanced latency compensation...
yes, we can try that but the "Latency compensation" option should be at each bus plugin-list tab (and not on each track).
however, the latency value for each track should reflect the total latency then: 1) the latency value to the track's own plugin-chain as is currently displayed, plus 2) the latency of the nominal audio output bus (if enabled).
is that it, grosso modo ?
Re. Advanced latency compensation...
Yes, that makes sense.
We won't catch all cases this way, think of aux sends in a track. But I'd say it's a step forward and covers some real world cases.
Re. Advanced latency compensation...
something's brewed
check qtractor >= v1.6.2.13git.efe3e4 [develop]
completely untested--leaving the exercise to you ;)
seeya
Re. Advanced latency compensation...
Thanks Rui.
Re. Advanced latency compensation...
It's magic: switching latency compensation in the bus has an immediate effect while playback is running. Switching latency compensation in a track needs stopping/starting playback.
re. Advanced latency compensation...
there's more in v1.6.2.14git.baa7d4 [develop]
please test && tell, as much as thoroughly you possibly can ;)
thanks
re. Advanced latency compensation...
That works well. I could test output bus latency compensation only.
Not sure how to test input bus latency compensation.
But I am confident that it works:)
Good job!
re. Advanced latency compensation... PING
Thx Rui, it's working perfectly with Insert Send/Returns, too.
I hardly dare to ask but the next step to be state of the art would be an manual but aided latency detection for insert sends with a PING button that does the same as LSP Latency Meter.
And in stage 2 maybe a button on the main pane's top "ping all Inserts" as help function when jack bufsize or pipewire quantum has changed.
Probably a lot of work for a convenience feature, so maybe for Christmas? :)
re. Advanced latency compensation... PING...
yes, probably on both accounts ;)
byee
re. Advanced latency compensation... PING...
Thanks for this positive outlook, Rui.
Now using external hardware is even more fun. And Inserts can be (ab)used to report a fake latency, so Qtractor can compensate the latency of plugins that don't report it to the host. Complicated setups with additional aux sends to other buses can be handled/aligned manually, e.g. by inserting LSP Compensation Delay if the destination bus of an aux send has a lower latency than the track's audio bus. Of course this can be pushed to extremes and might lead to a delay function within aux sends some day or a whole rewrite of the latency compensation. Until that I am confident that all real world problems are already solvable with Qtractor as it is now.
Add new comment