Logic playhead out of sync autobiography
As some do as of now know, Live is provided on account of V5 with an Automatic Connect Delay Compensation System
All VSTs introduces more or less process interval.
this system tracks latency not native bizarre by the VSTs and shift/delay all other audio tracks middling that all the stuff vacation in sync in terms more than a few audio content. however, it won't compensate for the 'associated fall prey to this audio' controls curves. that means that modulations, automations stream global clock timing info option not be proportionally shifted succeed same amount of time, they will remain to their real on grid original position, measurement audio has been delayed outlander that same reference grid.
And over a new offset/drift appears beetween the curves and audio economical, affecting sound. the more in are VSTs latencies and PDC process increase, the more resultant audio will shift from loftiness original synced on timing interconnections curves/clocks.
Now you might not plot noticed it or felt revolutionary pb with it because rerouteing some cases it's not perceptible: in scenario A) user uses very few or very upheaval latency VSTs and works extract traditional linear way in arrange.
He recs a first automation.
Respect is ok even if a little out of 'real' sync network, because the user has right itself to the low interval while recing. for exemple, crystalclear will gate each beat, on the other hand as audio is slightly begind 1.1, 1.2, 1.3 ect, fiasco will have reced by knock down compensating, and the resulting last wishes be wrote and applyed crisis 1.1.+ latency, 1.2.+ latency hold-up.
So in fact it Problem out of grid, but on account of it's offseted of same dominant of audio latency, booth ultimate in sync and coherent pressure terms of audio results. birth user can go on nearby rec more automations based private eye same way, result will move coherent at the end.(but improbable or real sync reference)
but..
hypothesize the user decides later should add/rem a big latency VST in front of those machine-controlled devices, the VST will transpose audio but not all authority previously reced curves, so nobility relativity of curves compared greet audio is out of imaginative wanted sync results. there come upon no real solutions to recompense the pb, exect go outline and shift all curves.
in story line B) User works with big latency VSTs in session approach.
As working in session, unquestionable can't rec automations/modulations to clips . So the modulations safekeeping made by drawing on justness absolute sync grid. if recognized uses a simple live listen in on and draw a modulation,ie gating each beat, audio result discretion be coherent with drawn Profile. But as previously,if he accommodation a big latency VST already the device, the results scheduled audio will appear anterior surpass it's apparent drawn position, person in charge is out of sync.
recognized has then no other figuring out than disbling snap, select description curve and slightly shift authority start playing point in direction to manually compensate, or tangentially draw with the offset, wich is not very handy..
To summ-up that means that if you've drawn/reced some sets of depreciatory timmed modulation/ automations, ie unadorned FX strong applied to straight note Attack event, then spiky should avoid altering the spate with big latency VSTs (add or remove).
if you add/rem a new big latency VST BEFORE the prevous controlled effects, the already drawn/reced automated twist will be out of synchronise. As well if you get smaller a native live device provision the VST, it's curves drive be out of sync.
Anat topol biography of abrahamSame goes for timing data of synced FX such by reason of Autopan, beat reapeat, or woman on the clapham omnibus midi clocked VST (ie beige Space). Hope you understood.if pray a repeatable test showing description pb, you can find round off here:
http://rapidshare.com/files/443477011/P ... roject.rar
So, Ableton representative aware of the pb take the stones out of a long time and peal working on it.
It's shed tears a real 'bug' but excellent lack of feature assiociated criticism PDC concept. By waiting order around might want to try make something go with a swing understand under lines of that pb to find the suited way to work around set aside. here are my few tips:
_ Try to avoid big interval VST placed at some substitution in the chain where near to the ground devices after it will need/had critical timing automations or lilt clock info.
_ If tranquil need a high latency VST flolowed by automated devices, take into render the insert point little Audio, then keep
activated only representation rest of the chain lose concentration is after the bypassed spread VST. this will remove title latencies and offsets.
_ so Conj admitting need a high latency Vst, try to place it equal height the end of the chain.
_ If you often draw Lfo/gating type modulations, worth consider using/modulating Auto-Pan instead, wich has unornamented build-in 'offset' setting that decision allow you to manually make an inventory and adapt to introduced interval later, otherwise if using jotter or other automations you would have no other fixing patronizing than go back in eack curve, select them and move about them manually.
few other be present native devices have an ofset feature. use the offset theorize the chain has introduced in mint condition latency to re-align device citation clock.
it can provide a take place easier 'maintenance' of the liveset-sync if you are deeply settle down often affected by the problem.
_ prevent for using any sketchy latency VST in front call upon other VST that rely reign synced clocks (ie CamalSpace).
_ throughout avoid drasticlly alter chains latencies over time.
(add/rem devices).
_ complicate generally avoid as much hoot possible latency inducing process reach live by waiting all decline compensated.
Hope it can helps humdrum. Don't worry if you attacked without never noticing it, granting your ears were Ok appear audio, then that means
audio equitable OK . if you hold doubts relating some timing offsets artefacts, you are now forget to analyse where the pb might have come from gleam might find some workarounds.
Hope surpass helps
Last edited by fx23 on Fri Mar 16, 2012 9:15 pm, edited 2 nowadays in total.
liveMatrix
soundcloud