Home » The PARIS Forums » PARIS: Main » WIKI: LATENCY DATABASE OPEN FOR REFERENCE and CONTRIBUTIONS
| WIKI: LATENCY DATABASE OPEN FOR REFERENCE and CONTRIBUTIONS [message #98191] |
Thu, 24 April 2008 15:27  |
|
|
http://www.kerrygalloway.com/WikiPARIS/wikka.php?wakka=Nativ eLatencyDatabase
There's a decent start there, composed of efforts of Dimitrios' I've found,
plus the official WAVES latency specs.
The term "database" is actually technically incorrect at the moment; it's
currently just a text list. The name reflects my intention to build it into
an actual user-contributable, searchable database - just as soon as I
decide/figure out how to do that.
For now, if you want to add a plugin that's not on the list - assuming you
are logged in to the Wiki, just doubleclick on the page to open the editor
and add the plugin to the bottom of the page as text, using something along
the lines of the following format - PLUGIN NAME / [TAB] / LATENCY IN
SAMPLES; just bring info and I'll take care of tidying it if needed.
Please contribute more as you find them!
- Kerry
"... being bitter is like swallowing poison and waiting for the other guy to die..." - anon
|
|
|
|
| Re: WIKI: LATENCY DATABASE OPEN FOR REFERENCE and CONTRIBUTIONS [message #98203 is a reply to message #98191] |
Thu, 24 April 2008 18:46  |
Deej
Messages: 130
Registered: September 2006
|
Senior Member |
|
|
Kerry Galloway <kg@kerrygalloway.com> wrote:
> http://www.kerrygalloway.com/WikiPARIS/wikka.php?wakka=Nativ eLatencyDatabase
>
>There's a decent start there, composed of efforts of Dimitrios' I've found,
>plus the official WAVES latency specs.
>
>The term "database" is actually technically incorrect at the moment; it's
>currently just a text list. The name reflects my intention to build it into
>an actual user-contributable, searchable database - just as soon as I
>decide/figure out how to do that.
>
>For now, if you want to add a plugin that's not on the list - assuming you
>are logged in to the Wiki, just doubleclick on the page to open the editor
>and add the plugin to the bottom of the page as text, using something along
>the lines of the following format - PLUGIN NAME / [TAB] / LATENCY IN
>SAMPLES; just bring info and I'll take care of tidying it if needed.
>
>Please contribute more as you find them!
>
>
>- Kerry
Here's some info I dragged out of my archives regarding Paris nudge values.
I don't know if it will help, bu6t it might if the programmer needs info
on how Paris "sees" things......
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 but is actually 80. A 10ms
nudge isn't 10 X 80 or 800 samples though, it's actually 480.
Here they are if anyone is interested:
1ms= 80 samples
5ms= 240 samples
10ms= 480 samples
25ms= 1120 samples
50ms= 2240 samples
75ms= 3360 samples
100ms= 4480 samples
also, using sampleslide to assist the nudge function....for UAD-1 plugins,
the Sampleslide presets were as follows:
1 Plugin 1536 (slide 4 x 100ms in Editor)
1 Pultec 1523 (slide 4 x 100ms in Editor)
2 Plugins 3072 (slide 8 x 100ms in Editor)
2 Pultecs 3046 (slide 8 x 100ms in Editor)
1 Plugin 1 Pultec 3059 (slide 8 x 100ms in Editor)
2 Plugins 1 Pultec 4595 (slide 12 x 100ms in Editor)
2 Pultecs 1 Plugin 4582 (slide 12 x 100ms in Editor)
3 Plugins 4608 (slide 12 x 100ms in Editor)
3 Pultecs 4569 (slide 12 x 100ms in Editor)
I think I put this together back when UAD-1 latency was twice what it is
now.
Well anyway....FWIW
;o)
|
|
|
|
| Re: WIKI: LATENCY DATABASE OPEN FOR REFERENCE and CONTRIBUTIONS [message #98211 is a reply to message #98203] |
Fri, 25 April 2008 01:17 |
|
|
You rock! That's perfect, posted it before my gig tonight.
http://www.kerrygalloway.com/WikiPARIS/wikka.php?wakka=Nativ eLatencyDatabase
Hooly dooly, those are some big-ass latency numbers.
Over a second latency? What did the UAD have to do - contact UA's head
office to get permission to pass each individual sample?
- Kerry
On 4/24/08 6:46 PM, in article 481137fa$1@linux, "Deej" <noway@jose.us>
wrote:
>
> Kerry Galloway <kg@kerrygalloway.com> wrote:
>> http://www.kerrygalloway.com/WikiPARIS/wikka.php?wakka=Nativ eLatencyDatabase
>>
>> There's a decent start there, composed of efforts of Dimitrios' I've found,
>> plus the official WAVES latency specs.
>>
>> The term "database" is actually technically incorrect at the moment; it's
>> currently just a text list. The name reflects my intention to build it into
>> an actual user-contributable, searchable database - just as soon as I
>> decide/figure out how to do that.
>>
>> For now, if you want to add a plugin that's not on the list - assuming you
>> are logged in to the Wiki, just doubleclick on the page to open the editor
>> and add the plugin to the bottom of the page as text, using something along
>> the lines of the following format - PLUGIN NAME / [TAB] / LATENCY IN
>> SAMPLES; just bring info and I'll take care of tidying it if needed.
>>
>> Please contribute more as you find them!
>>
>>
>> - Kerry
>
>
> Here's some info I dragged out of my archives regarding Paris nudge values.
> I don't know if it will help, bu6t it might if the programmer needs info
> on how Paris "sees" things......
>
> 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 but is actually 80. A 10ms
> nudge isn't 10 X 80 or 800 samples though, it's actually 480.
>
> Here they are if anyone is interested:
>
> 1ms= 80 samples
> 5ms= 240 samples
> 10ms= 480 samples
> 25ms= 1120 samples
> 50ms= 2240 samples
> 75ms= 3360 samples
> 100ms= 4480 samples
>
>
> also, using sampleslide to assist the nudge function....for UAD-1 plugins,
> the Sampleslide presets were as follows:
>
> 1 Plugin 1536 (slide 4 x 100ms in Editor)
> 1 Pultec 1523 (slide 4 x 100ms in Editor)
> 2 Plugins 3072 (slide 8 x 100ms in Editor)
> 2 Pultecs 3046 (slide 8 x 100ms in Editor)
> 1 Plugin 1 Pultec 3059 (slide 8 x 100ms in Editor)
> 2 Plugins 1 Pultec 4595 (slide 12 x 100ms in Editor)
> 2 Pultecs 1 Plugin 4582 (slide 12 x 100ms in Editor)
> 3 Plugins 4608 (slide 12 x 100ms in Editor)
> 3 Pultecs 4569 (slide 12 x 100ms in Editor)
>
> I think I put this together back when UAD-1 latency was twice what it is
> now.
>
> Well anyway....FWIW
>
> ;o)
>
"... being bitter is like swallowing poison and waiting for the other guy to die..." - anon
|
|
|
|
| Re: WIKI: LATENCY DATABASE OPEN FOR REFERENCE and CONTRIBUTIONS [message #98219 is a reply to message #98211] |
Fri, 25 April 2008 09:57 |
no
Messages: 40
Registered: January 2008
|
Member |
|
|
Kerry Galloway <kg@kerrygalloway.com> wrote:
>
>Hooly dooly, those are some big-ass latency numbers.
No Sh*t!
I always wondered why so many were having issues with latency
and the automation editor.
Now I know!
I thought some of you guys were trying to automate the
attack portion of every hit of a snare track or something..
>
>Over a second latency? What did the UAD have to do - contact UA's head
>office to get permission to pass each individual sample?
>
>- Kerry
>
>
>On 4/24/08 6:46 PM, in article 481137fa$1@linux, "Deej" <noway@jose.us>
>wrote:
>
>>
>> Kerry Galloway <kg@kerrygalloway.com> wrote:
>>> http://www.kerrygalloway.com/WikiPARIS/wikka.php?wakka=Nativ eLatencyDatabase
>>>
>>> There's a decent start there, composed of efforts of Dimitrios' I've
found,
>>> plus the official WAVES latency specs.
>>>
>>> The term "database" is actually technically incorrect at the moment;
it's
>>> currently just a text list. The name reflects my intention to build it
into
>>> an actual user-contributable, searchable database - just as soon as I
>>> decide/figure out how to do that.
>>>
>>> For now, if you want to add a plugin that's not on the list - assuming
you
>>> are logged in to the Wiki, just doubleclick on the page to open the editor
>>> and add the plugin to the bottom of the page as text, using something
along
>>> the lines of the following format - PLUGIN NAME / [TAB] / LATENCY IN
>>> SAMPLES; just bring info and I'll take care of tidying it if needed.
>>>
>>> Please contribute more as you find them!
>>>
>>>
>>> - Kerry
>>
>>
>> Here's some info I dragged out of my archives regarding Paris nudge values.
>> I don't know if it will help, bu6t it might if the programmer needs info
>> on how Paris "sees" things......
>>
>> 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 but is actually 80. A 10ms
>> nudge isn't 10 X 80 or 800 samples though, it's actually 480.
>>
>> Here they are if anyone is interested:
>>
>> 1ms= 80 samples
>> 5ms= 240 samples
>> 10ms= 480 samples
>> 25ms= 1120 samples
>> 50ms= 2240 samples
>> 75ms= 3360 samples
>> 100ms= 4480 samples
>>
>>
>> also, using sampleslide to assist the nudge function....for UAD-1 plugins,
>> the Sampleslide presets were as follows:
>>
>> 1 Plugin 1536 (slide 4 x 100ms in Editor)
>> 1 Pultec 1523 (slide 4 x 100ms in Editor)
>> 2 Plugins 3072 (slide 8 x 100ms in Editor)
>> 2 Pultecs 3046 (slide 8 x 100ms in Editor)
>> 1 Plugin 1 Pultec 3059 (slide 8 x 100ms in Editor)
>> 2 Plugins 1 Pultec 4595 (slide 12 x 100ms in Editor)
>> 2 Pultecs 1 Plugin 4582 (slide 12 x 100ms in Editor)
>> 3 Plugins 4608 (slide 12 x 100ms in Editor)
>> 3 Pultecs 4569 (slide 12 x 100ms in Editor)
>>
>> I think I put this together back when UAD-1 latency was twice what it
is
>> now.
>>
>> Well anyway....FWIW
>>
>> ;o)
>>
>
|
|
|
|
| Re: WIKI: LATENCY DATABASE OPEN FOR REFERENCE and CONTRIBUTIONS [message #98240 is a reply to message #98219] |
Fri, 25 April 2008 16:49 |
Aaron Allen
Messages: 1988
Registered: May 2008
|
Senior Member |
|
|
This is why I pulled my UAD card out and put it back in the static bag/box.
The latency was just an automation killer, even though I loved the sound of
it. If we can truly see PDC for Paris, it's probably time to pull it back
out for duty again.
AA
"Kim W." <no@no.no> wrote in message news:48120d81$1@linux...
>
> Kerry Galloway <kg@kerrygalloway.com> wrote:
>>
>>Hooly dooly, those are some big-ass latency numbers.
>
> No Sh*t!
> I always wondered why so many were having issues with latency
> and the automation editor.
> Now I know!
> I thought some of you guys were trying to automate the
> attack portion of every hit of a snare track or something..
>
>
>>
>>Over a second latency? What did the UAD have to do - contact UA's head
>>office to get permission to pass each individual sample?
>>
>>- Kerry
>>
>>
>>On 4/24/08 6:46 PM, in article 481137fa$1@linux, "Deej" <noway@jose.us>
>>wrote:
>>
>>>
>>> Kerry Galloway <kg@kerrygalloway.com> wrote:
>>>> http://www.kerrygalloway.com/WikiPARIS/wikka.php?wakka=Nativ eLatencyDatabase
>>>>
>>>> There's a decent start there, composed of efforts of Dimitrios' I've
> found,
>>>> plus the official WAVES latency specs.
>>>>
>>>> The term "database" is actually technically incorrect at the moment;
> it's
>>>> currently just a text list. The name reflects my intention to build it
> into
>>>> an actual user-contributable, searchable database - just as soon as I
>>>> decide/figure out how to do that.
>>>>
>>>> For now, if you want to add a plugin that's not on the list - assuming
> you
>>>> are logged in to the Wiki, just doubleclick on the page to open the
>>>> editor
>>>> and add the plugin to the bottom of the page as text, using something
> along
>>>> the lines of the following format - PLUGIN NAME / [TAB] / LATENCY IN
>>>> SAMPLES; just bring info and I'll take care of tidying it if needed.
>>>>
>>>> Please contribute more as you find them!
>>>>
>>>>
>>>> - Kerry
>>>
>>>
>>> Here's some info I dragged out of my archives regarding Paris nudge
>>> values.
>>> I don't know if it will help, bu6t it might if the programmer needs info
>>> on how Paris "sees" things......
>>>
>>> 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 but is actually 80. A
>>> 10ms
>>> nudge isn't 10 X 80 or 800 samples though, it's actually 480.
>>>
>>> Here they are if anyone is interested:
>>>
>>> 1ms= 80 samples
>>> 5ms= 240 samples
>>> 10ms= 480 samples
>>> 25ms= 1120 samples
>>> 50ms= 2240 samples
>>> 75ms= 3360 samples
>>> 100ms= 4480 samples
>>>
>>>
>>> also, using sampleslide to assist the nudge function....for UAD-1
>>> plugins,
>>> the Sampleslide presets were as follows:
>>>
>>> 1 Plugin 1536 (slide 4 x 100ms in Editor)
>>> 1 Pultec 1523 (slide 4 x 100ms in Editor)
>>> 2 Plugins 3072 (slide 8 x 100ms in Editor)
>>> 2 Pultecs 3046 (slide 8 x 100ms in Editor)
>>> 1 Plugin 1 Pultec 3059 (slide 8 x 100ms in Editor)
>>> 2 Plugins 1 Pultec 4595 (slide 12 x 100ms in Editor)
>>> 2 Pultecs 1 Plugin 4582 (slide 12 x 100ms in Editor)
>>> 3 Plugins 4608 (slide 12 x 100ms in Editor)
>>> 3 Pultecs 4569 (slide 12 x 100ms in Editor)
>>>
>>> I think I put this together back when UAD-1 latency was twice what it
> is
>>> now.
>>>
>>> Well anyway....FWIW
>>>
>>> ;o)
>>>
>>
>
|
|
|
|
| Re: WIKI: LATENCY DATABASE OPEN FOR REFERENCE and CONTRIBUTIONS [message #98243 is a reply to message #98240] |
Fri, 25 April 2008 17:16 |
|
|
Hmmmm... That would be insanely cool.
Problem is - I don't think it's going to give *true* PDC, for this reason:
VST plugs can only play a sample as the Now Line crawls over it; they have
no idea what the next sample's going to be.
So if I understand it correctly FaderWorks is more like a sophisticated
series of automatically calculated delays - everything's still going to
audibly shift to the right in relation to waveforms and previously-laid-in
automation every time you put a plugin on it.
You'll watch the waveform go by and then hear the kick it crawled over a
second later - it's just going to automate the process of calculating that
and keeping sample-accurate relationship to the other tracks. This in itself
is a Very Good Thing - but all it's going to do is move everything later in
time against the automation grid *together* in an *automated* and
*organized* way.
I would be *so* delighted to hear I'm wrong on this. But my mind would be
boggled to hear that Vertex figured out a way to give the VST slots a peek
at audio far enough in advance of its arrival so that they could pass on,
say, a one-second-delayed compressed kick at the time the Now Line hit it.
- k
On 4/25/08 4:49 PM, in article 481270c8@linux, "Aaron Allen"
<know-spam@not_here.dude> wrote:
> This is why I pulled my UAD card out and put it back in the static bag/box.
> The latency was just an automation killer, even though I loved the sound of
> it. If we can truly see PDC for Paris, it's probably time to pull it back
> out for duty again.
>
> AA
>
> "Kim W." <no@no.no> wrote in message news:48120d81$1@linux...
>>
>> Kerry Galloway <kg@kerrygalloway.com> wrote:
>>>
>>> Hooly dooly, those are some big-ass latency numbers.
>>
>> No Sh*t!
>> I always wondered why so many were having issues with latency
>> and the automation editor.
>> Now I know!
>> I thought some of you guys were trying to automate the
>> attack portion of every hit of a snare track or something..
>>
>>
>>>
>>> Over a second latency? What did the UAD have to do - contact UA's head
>>> office to get permission to pass each individual sample?
>>>
>>> - Kerry
>>>
>>>
>>> On 4/24/08 6:46 PM, in article 481137fa$1@linux, "Deej" <noway@jose.us>
>>> wrote:
>>>
>>>>
>>>> Kerry Galloway <kg@kerrygalloway.com> wrote:
>>>>> http://www.kerrygalloway.com/WikiPARIS/wikka.php?wakka=Nativ eLatencyDataba
>>>>> se
>>>>>
>>>>> There's a decent start there, composed of efforts of Dimitrios' I've
>> found,
>>>>> plus the official WAVES latency specs.
>>>>>
>>>>> The term "database" is actually technically incorrect at the moment;
>> it's
>>>>> currently just a text list. The name reflects my intention to build it
>> into
>>>>> an actual user-contributable, searchable database - just as soon as I
>>>>> decide/figure out how to do that.
>>>>>
>>>>> For now, if you want to add a plugin that's not on the list - assuming
>> you
>>>>> are logged in to the Wiki, just doubleclick on the page to open the
>>>>> editor
>>>>> and add the plugin to the bottom of the page as text, using something
>> along
>>>>> the lines of the following format - PLUGIN NAME / [TAB] / LATENCY IN
>>>>> SAMPLES; just bring info and I'll take care of tidying it if needed.
>>>>>
>>>>> Please contribute more as you find them!
>>>>>
>>>>>
>>>>> - Kerry
>>>>
>>>>
>>>> Here's some info I dragged out of my archives regarding Paris nudge
>>>> values.
>>>> I don't know if it will help, bu6t it might if the programmer needs info
>>>> on how Paris "sees" things......
>>>>
>>>> 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 but is actually 80. A
>>>> 10ms
>>>> nudge isn't 10 X 80 or 800 samples though, it's actually 480.
>>>>
>>>> Here they are if anyone is interested:
>>>>
>>>> 1ms= 80 samples
>>>> 5ms= 240 samples
>>>> 10ms= 480 samples
>>>> 25ms= 1120 samples
>>>> 50ms= 2240 samples
>>>> 75ms= 3360 samples
>>>> 100ms= 4480 samples
>>>>
>>>>
>>>> also, using sampleslide to assist the nudge function....for UAD-1
>>>> plugins,
>>>> the Sampleslide presets were as follows:
>>>>
>>>> 1 Plugin 1536 (slide 4 x 100ms in Editor)
>>>> 1 Pultec 1523 (slide 4 x 100ms in Editor)
>>>> 2 Plugins 3072 (slide 8 x 100ms in Editor)
>>>> 2 Pultecs 3046 (slide 8 x 100ms in Editor)
>>>> 1 Plugin 1 Pultec 3059 (slide 8 x 100ms in Editor)
>>>> 2 Plugins 1 Pultec 4595 (slide 12 x 100ms in Editor)
>>>> 2 Pultecs 1 Plugin 4582 (slide 12 x 100ms in Editor)
>>>> 3 Plugins 4608 (slide 12 x 100ms in Editor)
>>>> 3 Pultecs 4569 (slide 12 x 100ms in Editor)
>>>>
>>>> I think I put this together back when UAD-1 latency was twice what it
>> is
>>>> now.
>>>>
>>>> Well anyway....FWIW
>>>>
>>>> ;o)
>>>>
>>>
>>
>
>
"... being bitter is like swallowing poison and waiting for the other guy to die..." - anon
|
|
|
|
| Re: WIKI: LATENCY DATABASE OPEN FOR REFERENCE and CONTRIBUTIONS [message #98249 is a reply to message #98243] |
Fri, 25 April 2008 20:42 |
Aaron Allen
Messages: 1988
Registered: May 2008
|
Senior Member |
|
|
Yeah, I shoulda been clearer on this. I think your take is right, that it's
not *real* PDC.. however, if I stuff the UAD in another machine and ADAT
pipe it, this psuedo delay comp would be pretty good at keeping it all
automated and pretty close to the now line, as long as I input the right
info.
My whole thing was having to be a mathmatician just to keep up with the damn
thing, totally blowing out my listening vibe and turning into the black hole
of fun - which ain't productive. Now, it just might be :)
AA
"Kerry Galloway" <kg@kerrygalloway.com> wrote in message
news:C437C27F.AC98%kg@kerrygalloway.com...
> Hmmmm... That would be insanely cool.
>
> Problem is - I don't think it's going to give *true* PDC, for this reason:
> VST plugs can only play a sample as the Now Line crawls over it; they have
> no idea what the next sample's going to be.
>
> So if I understand it correctly FaderWorks is more like a sophisticated
> series of automatically calculated delays - everything's still going to
> audibly shift to the right in relation to waveforms and previously-laid-in
> automation every time you put a plugin on it.
>
> You'll watch the waveform go by and then hear the kick it crawled over a
> second later - it's just going to automate the process of calculating that
> and keeping sample-accurate relationship to the other tracks. This in
> itself
> is a Very Good Thing - but all it's going to do is move everything later
> in
> time against the automation grid *together* in an *automated* and
> *organized* way.
>
> I would be *so* delighted to hear I'm wrong on this. But my mind would be
> boggled to hear that Vertex figured out a way to give the VST slots a peek
> at audio far enough in advance of its arrival so that they could pass on,
> say, a one-second-delayed compressed kick at the time the Now Line hit it.
>
> - k
>
> On 4/25/08 4:49 PM, in article 481270c8@linux, "Aaron Allen"
> <know-spam@not_here.dude> wrote:
>
>> This is why I pulled my UAD card out and put it back in the static
>> bag/box.
>> The latency was just an automation killer, even though I loved the sound
>> of
>> it. If we can truly see PDC for Paris, it's probably time to pull it back
>> out for duty again.
>>
>> AA
>>
>> "Kim W." <no@no.no> wrote in message news:48120d81$1@linux...
>>>
>>> Kerry Galloway <kg@kerrygalloway.com> wrote:
>>>>
>>>> Hooly dooly, those are some big-ass latency numbers.
>>>
>>> No Sh*t!
>>> I always wondered why so many were having issues with latency
>>> and the automation editor.
>>> Now I know!
>>> I thought some of you guys were trying to automate the
>>> attack portion of every hit of a snare track or something..
>>>
>>>
>>>>
>>>> Over a second latency? What did the UAD have to do - contact UA's head
>>>> office to get permission to pass each individual sample?
>>>>
>>>> - Kerry
>>>>
>>>>
>>>> On 4/24/08 6:46 PM, in article 481137fa$1@linux, "Deej" <noway@jose.us>
>>>> wrote:
>>>>
>>>>>
>>>>> Kerry Galloway <kg@kerrygalloway.com> wrote:
>>>>>> http://www.kerrygalloway.com/WikiPARIS/wikka.php?wakka=Nativ eLatencyDataba
>>>>>> se
>>>>>>
>>>>>> There's a decent start there, composed of efforts of Dimitrios' I've
>>> found,
>>>>>> plus the official WAVES latency specs.
>>>>>>
>>>>>> The term "database" is actually technically incorrect at the moment;
>>> it's
>>>>>> currently just a text list. The name reflects my intention to build
>>>>>> it
>>> into
>>>>>> an actual user-contributable, searchable database - just as soon as I
>>>>>> decide/figure out how to do that.
>>>>>>
>>>>>> For now, if you want to add a plugin that's not on the list -
>>>>>> assuming
>>> you
>>>>>> are logged in to the Wiki, just doubleclick on the page to open the
>>>>>> editor
>>>>>> and add the plugin to the bottom of the page as text, using something
>>> along
>>>>>> the lines of the following format - PLUGIN NAME / [TAB] / LATENCY IN
>>>>>> SAMPLES; just bring info and I'll take care of tidying it if needed.
>>>>>>
>>>>>> Please contribute more as you find them!
>>>>>>
>>>>>>
>>>>>> - Kerry
>>>>>
>>>>>
>>>>> Here's some info I dragged out of my archives regarding Paris nudge
>>>>> values.
>>>>> I don't know if it will help, bu6t it might if the programmer needs
>>>>> info
>>>>> on how Paris "sees" things......
>>>>>
>>>>> 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 but is actually 80. A
>>>>> 10ms
>>>>> nudge isn't 10 X 80 or 800 samples though, it's actually 480.
>>>>>
>>>>> Here they are if anyone is interested:
>>>>>
>>>>> 1ms= 80 samples
>>>>> 5ms= 240 samples
>>>>> 10ms= 480 samples
>>>>> 25ms= 1120 samples
>>>>> 50ms= 2240 samples
>>>>> 75ms= 3360 samples
>>>>> 100ms= 4480 samples
>>>>>
>>>>>
>>>>> also, using sampleslide to assist the nudge function....for UAD-1
>>>>> plugins,
>>>>> the Sampleslide presets were as follows:
>>>>>
>>>>> 1 Plugin 1536 (slide 4 x 100ms in Editor)
>>>>> 1 Pultec 1523 (slide 4 x 100ms in Editor)
>>>>> 2 Plugins 3072 (slide 8 x 100ms in Editor)
>>>>> 2 Pultecs 3046 (slide 8 x 100ms in Editor)
>>>>> 1 Plugin 1 Pultec 3059 (slide 8 x 100ms in Editor)
>>>>> 2 Plugins 1 Pultec 4595 (slide 12 x 100ms in Editor)
>>>>> 2 Pultecs 1 Plugin 4582 (slide 12 x 100ms in Editor)
>>>>> 3 Plugins 4608 (slide 12 x 100ms in Editor)
>>>>> 3 Pultecs 4569 (slide 12 x 100ms in Editor)
>>>>>
>>>>> I think I put this together back when UAD-1 latency was twice what it
>>> is
>>>>> now.
>>>>>
>>>>> Well anyway....FWIW
>>>>>
>>>>> ;o)
>>>>>
>>>>
>>>
>>
>>
>
|
|
|
|
|
|
| Re: LATENCY DATABASE OPEN FOR REFERENCE and CONTRIBUTIONS [message #98561 is a reply to message #98525] |
Mon, 05 May 2008 13:27 |
|
|
A pleasure, sir - thanks for your kind words!
The Wiki is a start, but what I've done so far largely amounts to
reshuffling previously-existing data into easier-to-search formats. Same
sh*t, different font kinda deal. But while it isn't entirely without value
in itself, I see it simply as essential groundwork that needs to be laid to
support more ambitious and important advances.
- Kerry
On 5/5/08 6:42 AM, in article 481f1170@linux, "Miguel Vigil"
<nospam@nospam.com> wrote:
> Nice layout Kerry and very considerate of you.
>
> muchisimas gracias,
>
> El Miguel
>
>
>
>
> "Kerry Galloway" <kg@kerrygalloway.com> wrote in message
> news:C4365751.AC45%kg@kerrygalloway.com...
>> http://www.kerrygalloway.com/WikiPARIS/wikka.php?wakka=Nativ eLatencyDatabase
>>
>> There's a decent start there, composed of efforts of Dimitrios' I've
>> found,
>> plus the official WAVES latency specs.
>>
>> The term "database" is actually technically incorrect at the moment; it's
>> currently just a text list. The name reflects my intention to build it
>> into
>> an actual user-contributable, searchable database - just as soon as I
>> decide/figure out how to do that.
>>
>> For now, if you want to add a plugin that's not on the list - assuming you
>> are logged in to the Wiki, just doubleclick on the page to open the editor
>> and add the plugin to the bottom of the page as text, using something
>> along
>> the lines of the following format - PLUGIN NAME / [TAB] / LATENCY IN
>> SAMPLES; just bring info and I'll take care of tidying it if needed.
>>
>> Please contribute more as you find them!
>>
>>
>> - Kerry
>>
>
>
"... being bitter is like swallowing poison and waiting for the other guy to die..." - anon
|
|
|
|
| Re: LATENCY DATABASE OPEN FOR REFERENCE and CONTRIBUTIONS [message #98851 is a reply to message #98561] |
Tue, 20 May 2008 11:47 |
damien.gelee
Messages: 36
Registered: July 2006
|
Member |
|
|
Dont know if it can help, but this free stuff analyse every VST plug on your
PC. Latency is also displayed. Sometime it crashes, but it's usable anyway,
and information are correct for those i could verify.
Vincent Burel is not a known as a beginner by any means.
http://pagesperso-orange.fr/vb-audio/us/resources/vst_scanne r/vst_scanner.htm
Damien.
"Kerry Galloway" <kg@kerrygalloway.com> a écrit dans le message de news:
C444BBB1.AE56%kg@kerrygalloway.com...
>A pleasure, sir - thanks for your kind words!
>
> The Wiki is a start, but what I've done so far largely amounts to
> reshuffling previously-existing data into easier-to-search formats. Same
> sh*t, different font kinda deal. But while it isn't entirely without value
> in itself, I see it simply as essential groundwork that needs to be laid
> to
> support more ambitious and important advances.
>
> - Kerry
>
> On 5/5/08 6:42 AM, in article 481f1170@linux, "Miguel Vigil"
> <nospam@nospam.com> wrote:
>
>> Nice layout Kerry and very considerate of you.
>>
>> muchisimas gracias,
>>
>> El Miguel
>>
>>
>>
>>
>> "Kerry Galloway" <kg@kerrygalloway.com> wrote in message
>> news:C4365751.AC45%kg@kerrygalloway.com...
>>> http://www.kerrygalloway.com/WikiPARIS/wikka.php?wakka=Nativ eLatencyDatabase
>>>
>>> There's a decent start there, composed of efforts of Dimitrios' I've
>>> found,
>>> plus the official WAVES latency specs.
>>>
>>> The term "database" is actually technically incorrect at the moment;
>>> it's
>>> currently just a text list. The name reflects my intention to build it
>>> into
>>> an actual user-contributable, searchable database - just as soon as I
>>> decide/figure out how to do that.
>>>
>>> For now, if you want to add a plugin that's not on the list - assuming
>>> you
>>> are logged in to the Wiki, just doubleclick on the page to open the
>>> editor
>>> and add the plugin to the bottom of the page as text, using something
>>> along
>>> the lines of the following format - PLUGIN NAME / [TAB] / LATENCY IN
>>> SAMPLES; just bring info and I'll take care of tidying it if needed.
>>>
>>> Please contribute more as you find them!
>>>
>>>
>>> - Kerry
>>>
>>
>>
>
>
|
|
|
|
| Re: LATENCY DATABASE OPEN FOR REFERENCE and CONTRIBUTIONS [message #98853 is a reply to message #98851] |
Tue, 20 May 2008 15:11 |
|
|
Heya Damien - thanks for the tip. I'm not on PC myself yet, but once I am
this will be a useful resource. Thanks!
- Kerry
On 5/20/08 11:47 AM, in article 48331f15@linux, "Damien Gelee"
<damien.gelee@club-internet.fr> wrote:
> Dont know if it can help, but this free stuff analyse every VST plug on your
> PC. Latency is also displayed. Sometime it crashes, but it's usable anyway,
> and information are correct for those i could verify.
> Vincent Burel is not a known as a beginner by any means.
> http://pagesperso-orange.fr/vb-audio/us/resources/vst_scanne r/vst_scanner.htm
>
> Damien.
>
>
>
>
> "Kerry Galloway" <kg@kerrygalloway.com> a écrit dans le message de news:
> C444BBB1.AE56%kg@kerrygalloway.com...
>> A pleasure, sir - thanks for your kind words!
>>
>> The Wiki is a start, but what I've done so far largely amounts to
>> reshuffling previously-existing data into easier-to-search formats. Same
>> sh*t, different font kinda deal. But while it isn't entirely without value
>> in itself, I see it simply as essential groundwork that needs to be laid
>> to
>> support more ambitious and important advances.
>>
>> - Kerry
>>
>> On 5/5/08 6:42 AM, in article 481f1170@linux, "Miguel Vigil"
>> <nospam@nospam.com> wrote:
>>
>>> Nice layout Kerry and very considerate of you.
>>>
>>> muchisimas gracias,
>>>
>>> El Miguel
>>>
>>>
>>>
>>>
>>> "Kerry Galloway" <kg@kerrygalloway.com> wrote in message
>>> news:C4365751.AC45%kg@kerrygalloway.com...
>>>>
http://www.kerrygalloway.com/WikiPARIS/wikka.php?wakka=Nativ eLatencyDatabas>>>>
e
>>>>
>>>> There's a decent start there, composed of efforts of Dimitrios' I've
>>>> found,
>>>> plus the official WAVES latency specs.
>>>>
>>>> The term "database" is actually technically incorrect at the moment;
>>>> it's
>>>> currently just a text list. The name reflects my intention to build it
>>>> into
>>>> an actual user-contributable, searchable database - just as soon as I
>>>> decide/figure out how to do that.
>>>>
>>>> For now, if you want to add a plugin that's not on the list - assuming
>>>> you
>>>> are logged in to the Wiki, just doubleclick on the page to open the
>>>> editor
>>>> and add the plugin to the bottom of the page as text, using something
>>>> along
>>>> the lines of the following format - PLUGIN NAME / [TAB] / LATENCY IN
>>>> SAMPLES; just bring info and I'll take care of tidying it if needed.
>>>>
>>>> Please contribute more as you find them!
>>>>
>>>>
>>>> - Kerry
>>>>
>>>
>>>
>>
>>
>
>
"... being bitter is like swallowing poison and waiting for the other guy to die..." - anon
|
|
|
|
Goto Forum:
Current Time: Wed Nov 27 23:28:44 PST 2024
Total time taken to generate the page: 0.02742 seconds
|
The PARIS Forums
Search
Help
Members
Register
Login
Home
