I would like to know if this will ever be adressed
Posted: Mon Mar 16, 2020 9:31 pm
from the Cableguys website FAQ :
" Q: effects are sometimes slightly out of sync in Ableton Live, as if latency is not being compensated for by PDC. What can I do about this?
A: effects work perfectly in Ableton Live when they're the only plugin on a track, but they can suffer from latency in other cases — such as when there are several other plugins also on the track, or when used on a group or audio track with other tracks routed to it. This problem is not caused by Cableguys plugins, but is the result of a PDC (Plugin Delay Compensation) issue within Ableton Live. Our plugins are synced to the timing information provided by Live, and unfortunately Live does not correctly factor in PDC, so the timing information provided can be wrong. We discussed this with Ableton in 2011, and we encourage anyone affected by the issue to bug them about it. These timing issues became less problematic with the release of Live 9.5, but they have not been completely solved."
9 years later this issue is still present, still very relevant and more complicated than ever to deal with since a lot of modern plugins add significant latency to processing chains.
Does anybody know why is this only an Ableton issue? and can anyone in the know tell if this will be adressed at all in the near future?
" Q: effects are sometimes slightly out of sync in Ableton Live, as if latency is not being compensated for by PDC. What can I do about this?
A: effects work perfectly in Ableton Live when they're the only plugin on a track, but they can suffer from latency in other cases — such as when there are several other plugins also on the track, or when used on a group or audio track with other tracks routed to it. This problem is not caused by Cableguys plugins, but is the result of a PDC (Plugin Delay Compensation) issue within Ableton Live. Our plugins are synced to the timing information provided by Live, and unfortunately Live does not correctly factor in PDC, so the timing information provided can be wrong. We discussed this with Ableton in 2011, and we encourage anyone affected by the issue to bug them about it. These timing issues became less problematic with the release of Live 9.5, but they have not been completely solved."
9 years later this issue is still present, still very relevant and more complicated than ever to deal with since a lot of modern plugins add significant latency to processing chains.
Does anybody know why is this only an Ableton issue? and can anyone in the know tell if this will be adressed at all in the near future?