Revision [1459]

This is an old revision of NativeLatencyDatabase made by admin on 2010-01-01 16:49:09.

 

PARIS and Native Plug-in Latency


"Latency" is the time delay a plugin or other process introduces into an audio stream. Some plugins process in "real time" whereas others introduce either imperceptible or audible delay into the audio stream. This can create problems from disrupting internal phase relationships in multi-mic audio all the way to perceptibly "dragging" a track's timing.

The PARIS app, last updated in 2001, lacks internal latency compensation for either native or internal plugins, so PARIS users have evolved a variety of workarounds. They can avoid the issue by avoiding plugins that introduce latency; manually compensate for latency by nudging or sliding audio on the edit screen; or compensate for latency within a given submix via a system such as Vertex DSP's FaderWorks. Those who want to avoid the issue altogether can avoid the plugins marked in red below. Those seeking to manually compensate for latency can look up the exact latency of any particular plugin and nudge their audio earlier by that amount (or all other audio later by that amount). See important notes in sidebar to right for considerations affecting this approach.

Thanks to the efforts of user Dimitrios, PARIS users gained a new more convenient option for relative latency compensation for native plugins in 2009. Vertex DSP's FaderWorks uses a clever approach to compensate for global latency. A FaderWorks plugin is inserted on each channel of the PARIS mixer; FaderWorks keeps track of the latencies of each new plugin and delays all other channels in the submix accordingly if necessary. FaderWorks is not full global latency compensation - that particular submix will be delayed in relation to other submixes (latency is a "delay" of audio, so the ideal solution to correct for it would be to "advance" that audio in time, but FaderWorks can only affect audio that has already passed through the native inserts - it can't play audio any earlier than it receives it). But it's a great solution to correct *relative* latencies between channels within submixes. Delays are cumulative per channel; however, the maximum overall delay FaderWorks will introduce in a submix will be that of the most "latent" channel. Unless you're using highly "latent" plugins (or many native plugins with smaller latencies in series on a single channel), you may not notice any perceptible delay.

Note that when you are "nudging" on the editor screen in PARIS, the "nudge" values are not precise. PARIS power-user DJ explains in depth: "The nudge values are not consistent with what one would expect the samples to be per ms, and they are also not consistent with themselves. Meaning that a 1ms nudge would be expected to be 44 samples [assuming a sample rate of 44.1k] but is actually 80. A 10ms nudge isn't 10 X 80 or 800 samples though, it's actually 480."

PARIS Editor: Displayed vs. Actual Values
Displayed ValueActual movement in editor
"1ms"80 samples
"5ms"240 samples
"10ms"480 samples
"25ms"1120 samples
"50ms"2240 samples
"75ms"3360 samples
"100ms"4480 samples

DJ: "Using sampleslide to assist the nudge function... for UAD-1 plugins, Sampleslide presets were as follows:"

Compensating for UAD plugin latency with "Sampleslide" plus "nudge"
#TypeSampleslide valueAdd this much "nudge" in Editor
1Plugin1536slide 4 x 100ms in Editor
1Pultec1523slide 4 x 100ms in Editor
2Plugins3072slide 8 x 100ms in Editor
2Pultecs3046slide 8 x 100ms in Editor
1Plugin 1 Pultec3059slide 8 x 100ms in Editor
2Plugins 1 Pultec4595slide 12 x 100ms in Editor
2Pultecs 1 Plugin4582slide 12 x 100ms in Editor
3Plugins4608slide 12 x 100ms in Editor)
3Pultecs4569slide 12 x 100ms in Editor)

Native Plugin Latencies
ManufacturerPlug-in NameLatency in samples
DLimiter0
Dbcompressor0
TLSaturated Driver0
xxxSimple Limiter0
xxxSoft Overdrive0
xxxGene comp mono0
MDAdynamics0
MDAloudness0
MJcompressor0
MJmultiband0
xxxClassic_compressor0
CamelCamelphat_free0
E_phonicXpressor0
MnCompV1.r0
LuxonixLFX13100
ChunkwareVanilla44
KjaerhusGCO-10
DSPFXStudioverb0
DSPFXAcousticverb0
DSPFXChorus0
DSPFXautopan0
DSPFXAural Exciter0
DSPFXDelay0
DSPFXOptimizer33
DSPFXFlanger1024
WavesAPI 550A0
WavesAPI 550B0
WavesAPI 5600
WavesAPI 25000
WavesAudioTrack0
WavesC1 Compressor0
WavesC1 Gate0
WavesC1 Comp-Gate340
WavesC1 Comp-sc340
WavesC4 Multiband64
WavesDeBreath32,384
WavesDeEsser0
WavesDoppler0
WavesDoubler0
WavesEnigma0
WavesGTR3 Amps34
WavesGTR3 Stomps0
WavesGTR2 Amps34
WavesGTR2 Stomps0
WavesIR-1 Convolution Reverb0
WavesIR-L Convolution Reverb0
WavesIR-360 Convolution Reverb0
WavesL1 Ultramaximizer64
WavesL2 Ultramaximizer64
WavesL3 Multimaximizer3528
WavesL3 Ultramaximizer3528
WavesL3-16 Multimaximizer6207
WavesL3-LL Multimaximizer64
WavesL3-LL Ultramaximizer64
WavesLinear Phase Equalizer Broadband2679
WavesLinear Phase Equalizer Lowband2047
WavesLinear Phase Multiband3528
WavesMaxxBass0
WavesMaxxVolume64
WavesMetaFlanger0
WavesMondoMod0
WavesMorphoder639
WavesPAZ Analyzer0
WavesPS22 Split / X-SplitN/A
WavesPS22 SpreadN/A
WavesQ100
WavesQ-Clone344
WavesRenaissance Axx64
WavesRenaissance Bass0
WavesRenaissance Channel65
WavesRenaissance Compressor64
WavesRenaissance DeEsser64
WavesRenaissance Equalizer0
WavesRenaissance Reverb0
WavesRenaissance Vox64
WavesS1 Stereo Imager0
WavesSoundShifter6946
WavesSSL E Channel0
WavesSSL G Equalizer0
WavesSSL G Master Buss Compressor1
WavesSuperTap0
WavesTransX Multi64
WavesTransX Wide64
WavesTrueVerb0
WavesUltraPitch8239
WavesV-Comp0
WavesV-EQ30
WavesV-EQ40
WavesWaves Tune3072
WavesWaves Tune LT3072
WavesX-Click2625
WavesX-Crackle|{background-color:red; color:white}2625
WavesX-Hum0
WavesX-Noise5120
WavesZ-Noise34,702
WavesC360 Surround Compressor64
WavesIDR360 Surround Bit Re-Quantizer0
WavesL360 Surround Limiter64
WavesLFE360 Low Pass Filter0
WavesM360 Surround Manager0
WavesM360 Surround Mixdown0
WavesS360 Surround Imager0
WavesS360 Surround Panner0
WavesR360 Surround Reverb0
There are no comments on this page.
Valid XHTML :: Valid CSS: :: Powered by WikkaWiki