FabFilter User Forum
Project-wide latency caused by Pro Q 4?
To be clear, because I've gotten some confusion about this on other forums I've asked: the MIDI channel has latency even if its audio is not passing through any instance of Pro Q4. That latency then goes away when I delete the instances of Pro Q4 on the *other* channel (the audio channel).
Ropedragon — Dec 17, 2024
SOLVED: I wasn't aware that Ableton's delay compensation matches the latency across all tracks. So because one track had an EQ band with spectral dynamics enabled, all other tracks were being delayed. Can be solved either by using reduced latency when monitoring, or by removing the spectral effect until mixing/mastering.
Ropedragon — Dec 17, 2024
Hi,
As the subject says, I seem to be experiencing latency across my whole live set on Ableton (12.1.5) for having multiple instances of fabfilter pro Q 4 open. I have an audio track running two instances (plus another instance on a pre-master bus). This seems to cause noticeable latency on a separate MIDI track running Wavetable. The latency disappears when I delete the two instances of Pro Q on the audio track.
This latency occurs whether or not there is audio being processed, so this seems to just be the result of the instances being there, not because they are currently processing something. The CPU load is also under 10%.
Any advice for how I might get rid of this?