Ableton Forum

its def not fixed

one way is use signal pre-fx to feed sidchain, or a dummy signal

They could at least allow a 'manual' possible fix, a bit like track delays
users could be able to control a vst clock ppq offset on the device, that doesnt implies complex audio delay lines like audio pdc, that's just a simple add/sub float operation on timing datas

The question is why is Ableton unable to fix this issue. Surely they must know about it by now after all those years....


Ive posted this thread when it was Ableton live V5 ..in 2011....
12 years ago, yes 12.. should be renamed to "L12: years we don't care about tightness' of music
https ...

Have a look at the log text file, maybe some info about what plugin / io operation did the crash

made video explaining problem better, and why it's a pain for all plugin developpers that use transport

and some still imo 'weird' workarounds, that could be still a bit less painfull workflow wise (here on my scope, but for any synced vst)

https://www.youtube.com/watch?v=YORdCYgEk7A

yeah that kinda is the problem, it def can , slowly , but surely.., sneakily create that, ahemm, unwanted 'groove" over time^^

and yes i came really often with this.
a pretty simple exemple: im building a synced scope vst called psyscope
(but all other vst scopes, ie osczillos megascope ...

Ok thanks jur, i got my answer.

to clarify some part of PDC is working :
audio side of PDC is working, what is not working, is that while PDC has been delaying audio to keep stuff in sync audio wise,
it didn't compensate the clock devices receive , when it should have

so a relative drift occur ...

Few users including me repported problems with pdc since v5, more than 10 years ago now..

problem beeing main clock devices/vst receive is just not latency compensated.

this makes any synced device, being native/vst unusable with pdc.

could anyone with L12 test this simple setup/ex and repport if ...

**correction its integer nb of samples fitting tempis rather than ms.

in a way mathematically speaking,most tempis will make loops not fitting an integer nb of samples, and so kinda 'normal' to be rounded/truncated/different durations loops each turn, however all should be affected in the same way ...

this is especially more visible in resampling with short audio clip looping, ie here one bar:
first is 151 bpm, it clearly doesn't cancel and the drift is random each clip looping turn,
second is 150, perfect cancel, no drift, -inf on master. this reproduce to all ms fitting bpm

https://youtu.be ...

@angstom, try do the same test at say 121 Bpm, and try to loop the audio clip/arrangement, here 120 is fine, but 121, 22,23 ect are not

my pers findings is that tempis that fit integer number of ms per beat will fully cancel (ie 60,120,150..) but ANY other will drift and won't have
sample accuracy ...

ableton & usine
http://soundcloud.com/fx23/fx23-sarakon ... chitech164

my first live made with ableton & usine
Hitech psy to psychedelic trance 164-155 Bpm
feel free to comment, cheers'

https://soundcloud.com/fx23/fx23-live-t ... o-psyke155

..or there could just be an option in PDC préférences menu:

_Old behaviour ( per track delay comp)
_New behaviour (per device delay comp)