The PARIS Forums: PARIS: Main » Do_You_want_a_Quick_PDC

Home » The PARIS Forums » PARIS: Main » Do_You_want_a_Quick_PDC_Solution ??

Show: Today's Messages :: Polls :: Message Navigator

Do_You_want_a_Quick_PDC_Solution ?? [message #67071]

Wed, 19 April 2006 07:23

Dimitrios

Messages: 1056
Registered: August 2005

Senior Member

I don't know if most of you are aware of Latency delay vst plugin from Voxengo.
IT IS NOT Sample delay from Voxengo again.
The beauty of Latency delay is that it uses a fixed 10.000 samples around
200ms for every instance put on a vst slot.
So the concept is this.
Put one instance of it ON EVEY audio track you have on one vst slot.
Thus every instance will show 0000 and all your audio tracks will be latent
for 10.000 samples.
Now lets say on track 5 you wanna use a rencomp from Waves .
You just go there on your Latency delay and just put the 64 number.
This is the actual rencomp latency.
Thus all your tracks will be alligned.
Now say you put a LA2 UAD1 plug on track 7 (please use Chainer wrapped from
Spinaudio to have the 4096 latency) then you just put on latency delay the
4096 number.
Now lets say you put a EDS compressor on track 8 that has a 2 sample latency
with 0 lookahead and 47 samples with 0.001 lookahead
So you just put that number there...
Easy right ?
No nudging to the left and delaying to the right.
Voxengo latency delay does not makes your cpu any heavier at all !!

Regards,
Dimitrios

Report message to a moderator

Re: Do_You_want_a_Quick_PDC_Solution ?? [message #67076 is a reply to message #67071]

Wed, 19 April 2006 08:23

John [1]
Messages: 2229
Registered: September 2005

Senior Member

Dimitrios, How do you determine the latency of each plugin? How about writing
a VST to determine the latencies. hehe

Thanks,
John

"Dimitrios" <musurgio@otenet.gr> wrote:
>
>I don't know if most of you are aware of Latency delay vst plugin from Voxengo.
>IT IS NOT Sample delay from Voxengo again.
>The beauty of Latency delay is that it uses a fixed 10.000 samples around
>200ms for every instance put on a vst slot.
>So the concept is this.
>Put one instance of it ON EVEY audio track you have on one vst slot.
>Thus every instance will show 0000 and all your audio tracks will be latent
>for 10.000 samples.
>Now lets say on track 5 you wanna use a rencomp from Waves .
>You just go there on your Latency delay and just put the 64 number.
>This is the actual rencomp latency.
>Thus all your tracks will be alligned.
>Now say you put a LA2 UAD1 plug on track 7 (please use Chainer wrapped from
>Spinaudio to have the 4096 latency) then you just put on latency delay the
>4096 number.
>Now lets say you put a EDS compressor on track 8 that has a 2 sample latency
>with 0 lookahead and 47 samples with 0.001 lookahead
>So you just put that number there...
>Easy right ?
>No nudging to the left and delaying to the right.
>Voxengo latency delay does not makes your cpu any heavier at all !!
>
>Regards,
>Dimitrios

Report message to a moderator

Re: Do_You_want_a_Quick_PDC_Solution ?? [message #67077 is a reply to message #67071]

Wed, 19 April 2006 08:19

Deej [1]

Messages: 2149
Registered: January 2006

Senior Member

But the tracks are going to play back 10000 samples behind the waveform in
the editor.......right? this is the problem with the UAD latency
compensator. It's really hard to use real time fader automation when the
audio plays so far behind the waveform, though maybe 200ms would work. I'd
have to try it..

"Dimitrios" <musurgio@otenet.gr> wrote in message news:444647d4$1@linux...
>
> I don't know if most of you are aware of Latency delay vst plugin from
Voxengo.
> IT IS NOT Sample delay from Voxengo again.
> The beauty of Latency delay is that it uses a fixed 10.000 samples around
> 200ms for every instance put on a vst slot.
> So the concept is this.
> Put one instance of it ON EVEY audio track you have on one vst slot.
> Thus every instance will show 0000 and all your audio tracks will be
latent
> for 10.000 samples.
> Now lets say on track 5 you wanna use a rencomp from Waves .
> You just go there on your Latency delay and just put the 64 number.
> This is the actual rencomp latency.
> Thus all your tracks will be alligned.
> Now say you put a LA2 UAD1 plug on track 7 (please use Chainer wrapped
from
> Spinaudio to have the 4096 latency) then you just put on latency delay the
> 4096 number.
> Now lets say you put a EDS compressor on track 8 that has a 2 sample
latency
> with 0 lookahead and 47 samples with 0.001 lookahead
> So you just put that number there...
> Easy right ?
> No nudging to the left and delaying to the right.
> Voxengo latency delay does not makes your cpu any heavier at all !!
>
> Regards,
> Dimitrios

Report message to a moderator

Re: Do_You_want_a_Quick_PDC_Solution ?? [message #67080 is a reply to message #67076]

Wed, 19 April 2006 08:30

Dimitrios

Messages: 1056
Registered: August 2005

Senior Member

Dear John,
There is a free app called vstspy that reads all your vst'd and shows amoung
other info the delay too...
http://tobybear.phreque.com/files/vstspy.zip
Enjoy
Regards,
Dimitrios

"John" <no@no.com> wrote:
>
>Dimitrios, How do you determine the latency of each plugin? How about
writing
>a VST to determine the latencies. hehe
>
>Thanks,
>John
>
>"Dimitrios" <musurgio@otenet.gr> wrote:
>>
>>I don't know if most of you are aware of Latency delay vst plugin from
Voxengo.
>>IT IS NOT Sample delay from Voxengo again.
>>The beauty of Latency delay is that it uses a fixed 10.000 samples around
>>200ms for every instance put on a vst slot.
>>So the concept is this.
>>Put one instance of it ON EVEY audio track you have on one vst slot.
>>Thus every instance will show 0000 and all your audio tracks will be latent
>>for 10.000 samples.
>>Now lets say on track 5 you wanna use a rencomp from Waves .
>>You just go there on your Latency delay and just put the 64 number.
>>This is the actual rencomp latency.
>>Thus all your tracks will be alligned.
>>Now say you put a LA2 UAD1 plug on track 7 (please use Chainer wrapped
from
>>Spinaudio to have the 4096 latency) then you just put on latency delay
the
>>4096 number.
>>Now lets say you put a EDS compressor on track 8 that has a 2 sample latency
>>with 0 lookahead and 47 samples with 0.001 lookahead
>>So you just put that number there...
>>Easy right ?
>>No nudging to the left and delaying to the right.
>>Voxengo latency delay does not makes your cpu any heavier at all !!
>>
>>Regards,
>>Dimitrios
>

Report message to a moderator

Re: Do_You_want_a_Quick_PDC_Solution ?? [message #67092 is a reply to message #67080]

Wed, 19 April 2006 14:43

John [1]

Messages: 2229
Registered: September 2005

Senior Member

Is it the initial delay column that tells you the delay of the plugin in
vstspy?
John

Dimitrios wrote:
> Dear John,
> There is a free app called vstspy that reads all your vst'd and shows amoung
> other info the delay too...
> http://tobybear.phreque.com/files/vstspy.zip
> Enjoy
> Regards,
> Dimitrios
>
> "John" <no@no.com> wrote:
>> Dimitrios, How do you determine the latency of each plugin? How about
> writing
>> a VST to determine the latencies. hehe
>>
>> Thanks,
>> John
>>
>> "Dimitrios" <musurgio@otenet.gr> wrote:
>>> I don't know if most of you are aware of Latency delay vst plugin from
> Voxengo.
>>> IT IS NOT Sample delay from Voxengo again.
>>> The beauty of Latency delay is that it uses a fixed 10.000 samples around
>>> 200ms for every instance put on a vst slot.
>>> So the concept is this.
>>> Put one instance of it ON EVEY audio track you have on one vst slot.
>>> Thus every instance will show 0000 and all your audio tracks will be latent
>>> for 10.000 samples.
>>> Now lets say on track 5 you wanna use a rencomp from Waves .
>>> You just go there on your Latency delay and just put the 64 number.
>>> This is the actual rencomp latency.
>>> Thus all your tracks will be alligned.
>>> Now say you put a LA2 UAD1 plug on track 7 (please use Chainer wrapped
> from
>>> Spinaudio to have the 4096 latency) then you just put on latency delay
> the
>>> 4096 number.
>>> Now lets say you put a EDS compressor on track 8 that has a 2 sample latency
>>> with 0 lookahead and 47 samples with 0.001 lookahead
>>> So you just put that number there...
>>> Easy right ?
>>> No nudging to the left and delaying to the right.
>>> Voxengo latency delay does not makes your cpu any heavier at all !!
>>>
>>> Regards,
>>> Dimitrios
>

Report message to a moderator

Re: Do_You_want_a_Quick_PDC_Solution ?? [message #67111 is a reply to message #67092]

Thu, 20 April 2006 01:56

Dimitrios

Messages: 1056
Registered: August 2005

Senior Member

Hi,
There is a column saying init delay, thats it.
Note that not all vst plugins show up the right way.
For instance, T-racks introduces a 64 samples latency but vstspy show 0 !
I will post later a list with latencies of what I have checked myself.
Regards,
Dimitrios

John <no@no.com> wrote:
>Is it the initial delay column that tells you the delay of the plugin in

>vstspy?
>John
>
>Dimitrios wrote:
>> Dear John,
>> There is a free app called vstspy that reads all your vst'd and shows
amoung
>> other info the delay too...
>> http://tobybear.phreque.com/files/vstspy.zip
>> Enjoy
>> Regards,
>> Dimitrios
>>
>> "John" <no@no.com> wrote:
>>> Dimitrios, How do you determine the latency of each plugin? How about
>> writing
>>> a VST to determine the latencies. hehe
>>>
>>> Thanks,
>>> John
>>>
>>> "Dimitrios" <musurgio@otenet.gr> wrote:
>>>> I don't know if most of you are aware of Latency delay vst plugin from
>> Voxengo.
>>>> IT IS NOT Sample delay from Voxengo again.
>>>> The beauty of Latency delay is that it uses a fixed 10.000 samples around
>>>> 200ms for every instance put on a vst slot.
>>>> So the concept is this.
>>>> Put one instance of it ON EVEY audio track you have on one vst slot.
>>>> Thus every instance will show 0000 and all your audio tracks will be
latent
>>>> for 10.000 samples.
>>>> Now lets say on track 5 you wanna use a rencomp from Waves .
>>>> You just go there on your Latency delay and just put the 64 number.
>>>> This is the actual rencomp latency.
>>>> Thus all your tracks will be alligned.
>>>> Now say you put a LA2 UAD1 plug on track 7 (please use Chainer wrapped
>> from
>>>> Spinaudio to have the 4096 latency) then you just put on latency delay
>> the
>>>> 4096 number.
>>>> Now lets say you put a EDS compressor on track 8 that has a 2 sample
latency
>>>> with 0 lookahead and 47 samples with 0.001 lookahead
>>>> So you just put that number there...
>>>> Easy right ?
>>>> No nudging to the left and delaying to the right.
>>>> Voxengo latency delay does not makes your cpu any heavier at all !!
>>>>
>>>> Regards,
>>>> Dimitrios
>>

Report message to a moderator

Re: Do_You_want_a_Quick_PDC_Solution ?? [message #67117 is a reply to message #67111]

Thu, 20 April 2006 04:28

John [1]
Messages: 2229
Registered: September 2005

Senior Member

And please tell us how you tested them. Thanks!
John

"Dimitrios" <musurgio@otenet.gr> wrote:
>
>Hi,
>There is a column saying init delay, thats it.
>Note that not all vst plugins show up the right way.
>For instance, T-racks introduces a 64 samples latency but vstspy show 0
!
>I will post later a list with latencies of what I have checked myself.
>Regards,
>Dimitrios
>
>John <no@no.com> wrote:
>>Is it the initial delay column that tells you the delay of the plugin in
>
>>vstspy?
>>John
>>
>>Dimitrios wrote:
>>> Dear John,
>>> There is a free app called vstspy that reads all your vst'd and shows
>amoung
>>> other info the delay too...
>>> http://tobybear.phreque.com/files/vstspy.zip
>>> Enjoy
>>> Regards,
>>> Dimitrios
>>>
>>> "John" <no@no.com> wrote:
>>>> Dimitrios, How do you determine the latency of each plugin? How about
>>> writing
>>>> a VST to determine the latencies. hehe
>>>>
>>>> Thanks,
>>>> John
>>>>
>>>> "Dimitrios" <musurgio@otenet.gr> wrote:
>>>>> I don't know if most of you are aware of Latency delay vst plugin from
>>> Voxengo.
>>>>> IT IS NOT Sample delay from Voxengo again.
>>>>> The beauty of Latency delay is that it uses a fixed 10.000 samples
around
>>>>> 200ms for every instance put on a vst slot.
>>>>> So the concept is this.
>>>>> Put one instance of it ON EVEY audio track you have on one vst slot.
>>>>> Thus every instance will show 0000 and all your audio tracks will be
>latent
>>>>> for 10.000 samples.
>>>>> Now lets say on track 5 you wanna use a rencomp from Waves .
>>>>> You just go there on your Latency delay and just put the 64 number.
>>>>> This is the actual rencomp latency.
>>>>> Thus all your tracks will be alligned.
>>>>> Now say you put a LA2 UAD1 plug on track 7 (please use Chainer wrapped
>>> from
>>>>> Spinaudio to have the 4096 latency) then you just put on latency delay
>>> the
>>>>> 4096 number.
>>>>> Now lets say you put a EDS compressor on track 8 that has a 2 sample
>latency
>>>>> with 0 lookahead and 47 samples with 0.001 lookahead
>>>>> So you just put that number there...
>>>>> Easy right ?
>>>>> No nudging to the left and delaying to the right.
>>>>> Voxengo latency delay does not makes your cpu any heavier at all !!
>>>>>
>>>>> Regards,
>>>>> Dimitrios
>>>
>

Report message to a moderator

Re: Do_You_want_a_Quick_PDC_Solution ?? [message #67122 is a reply to message #67117]

Thu, 20 April 2006 06:16

Dimitrios

Messages: 1056
Registered: August 2005

Senior Member

The test is quite simple:
Just copy same audio file on to two audio tracks.
Put the vst on one track and a dleay plugin like voxengo sample delay on
the other.
Now rverse the phase of one track and see when they cancel themselves or
almost deiisapear.
You will understand when this will happen by changing sample by sample the
latency.
Regards,
Dimitrios

"john" <no@no.com> wrote:
>
>And please tell us how you tested them. Thanks!
>John
>
>"Dimitrios" <musurgio@otenet.gr> wrote:
>>
>>Hi,
>>There is a column saying init delay, thats it.
>>Note that not all vst plugins show up the right way.
>>For instance, T-racks introduces a 64 samples latency but vstspy show 0
>!
>>I will post later a list with latencies of what I have checked myself.
>>Regards,
>>Dimitrios
>>
>>John <no@no.com> wrote:
>>>Is it the initial delay column that tells you the delay of the plugin
in
>>
>>>vstspy?
>>>John
>>>
>>>Dimitrios wrote:
>>>> Dear John,
>>>> There is a free app called vstspy that reads all your vst'd and shows
>>amoung
>>>> other info the delay too...
>>>> http://tobybear.phreque.com/files/vstspy.zip
>>>> Enjoy
>>>> Regards,
>>>> Dimitrios
>>>>
>>>> "John" <no@no.com> wrote:
>>>>> Dimitrios, How do you determine the latency of each plugin? How about
>>>> writing
>>>>> a VST to determine the latencies. hehe
>>>>>
>>>>> Thanks,
>>>>> John
>>>>>
>>>>> "Dimitrios" <musurgio@otenet.gr> wrote:
>>>>>> I don't know if most of you are aware of Latency delay vst plugin
from
>>>> Voxengo.
>>>>>> IT IS NOT Sample delay from Voxengo again.
>>>>>> The beauty of Latency delay is that it uses a fixed 10.000 samples
>around
>>>>>> 200ms for every instance put on a vst slot.
>>>>>> So the concept is this.
>>>>>> Put one instance of it ON EVEY audio track you have on one vst slot.
>>>>>> Thus every instance will show 0000 and all your audio tracks will
be
>>latent
>>>>>> for 10.000 samples.
>>>>>> Now lets say on track 5 you wanna use a rencomp from Waves .
>>>>>> You just go there on your Latency delay and just put the 64 number.
>>>>>> This is the actual rencomp latency.
>>>>>> Thus all your tracks will be alligned.
>>>>>> Now say you put a LA2 UAD1 plug on track 7 (please use Chainer wrapped
>>>> from
>>>>>> Spinaudio to have the 4096 latency) then you just put on latency delay
>>>> the
>>>>>> 4096 number.
>>>>>> Now lets say you put a EDS compressor on track 8 that has a 2 sample
>>latency
>>>>>> with 0 lookahead and 47 samples with 0.001 lookahead
>>>>>> So you just put that number there...
>>>>>> Easy right ?
>>>>>> No nudging to the left and delaying to the right.
>>>>>> Voxengo latency delay does not makes your cpu any heavier at all !!
>>>>>>
>>>>>> Regards,
>>>>>> Dimitrios
>>>>
>>
>

Report message to a moderator

Previous Topic:	Paris/Cubase sync. DJ?
Next Topic:	UAD1-dropouts ?

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

] [

]

Current Time: Thu Apr 03 17:18:50 PDT 2025

Total time taken to generate the page: 0.01485 seconds