Home » The PARIS Forums » PARIS: Main » So does this automatically compensate for Paris latency?
|
|
|
|
|
|
|
|
| Re: So does this automatically compensate for Paris latency? [message #95983 is a reply to message #95980] |
Thu, 14 February 2008 22:19   |
![Deej [5] is currently offline](/theme/PARIS_Forum_Template/images/offline.png "Deej [5] is currently offline")
Deej [5]
Messages: 373
Registered: March 2008
|
Senior Member |
|
|
This is a multi-part message in MIME format.
------=_NextPart_000_00E8_01C86F5F.FD2EFB30
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Well, I've been thinking about some aspects of Paris that I really =
liked. However, there's still the situation with bussing across =
submixes, but it's not something I couldn't overcome.
I really miss the Paris EQ and FX actually. They are much better, IMO, =
than any VST plugins I've heard that aren't DSP driven.
the more I delve into Cubase, the more things about it that I like, but =
also, the more sonic weaknesses I see vis-a-vis Paris. It's possible to =
do the "big" thing in Cubase, it's easy to do it in Paris. I miss the =
easy part.=20
I think I'd be a bit more satisfied with Cubase if I was using a DM2000 =
with digital I/O options that would accommodate my outboard gear. =
Anybody got a spare $20k laying around?
"Aaron Allen" <know-spam@not_here.dude> wrote in message =
news:47b5217d@linux...
>I thought you were trying to simplify :)
>=20
> AA
>=20
>=20
> "Deej" <noway@jose.net> wrote in message news:47b51030$1@linux...
>> So basically, if you put this on each channel any plugin you add to =
that=20
>> channel will report it's latency and then all channels can be =
adjusted to=20
>> compensate for this amount of latency? If this is cumulative, that is =
>> basically the same as having PDC. The only difference is a mouse =
click=20
>> each time you add a plugin so that the remaining channels adjust to =
the=20
>> additional latency.
>>
>> Does this work with the high cumulative latency numbers that are =
incurred=20
>> when UAD-1 plugins are stacked on tracks?
>>
>> I guess, what I'm getting at here is if I were to put together =
another=20
>> Paris DAW, say 4 x Cards (which I know I can channel to a single IRQ =
on a=20
>> 13 slot Magma) and then have my other Magma in use running the two =
POCO's=20
>> and 4 x UAD-1 cards, I could have a Paris DAW that that would =
integrate=20
>> UAD-1 and POCO plugins and I wouldn't have to jack around with =
nudge/slide=20
>> or Sampleslide?.....I could just click a mouse every time I added =
another=20
>> plug and everything would be compensated?
>>
>>
>> "Don Nafe" <dnafe@magma.ca> wrote in message news:47b4cb97@linux...
>>> I'm still not sure whether it automatically detects a plugin's =
latency=20
>>> (where applicable)
>>>
>>> but yes, put it on each channel, throw in aplugin and input it's =
latency=20
>>> and Bob's your Uncle...latencey adjustment across all channels.
>>>
>>> Nice thing is if you add a different plugin to a different channel =
you=20
>>> just have to input that letency on that channelss faderwork plug and =
all=20
>>> channels get adjusted accordingly (and so on and so on....
>>>
>>>
>>> "Deej" <noway@jose.net> wrote in message news:47b4b204@linux...
>>>> http://www.vertexdsp.com/products/ReleaseNotes_FaderWorks.rt f
>>>>
>>>> Before I sold my Paris system, I bought this plugin. I have never =
even=20
>>>> used it. Does it now provide PDC if instantiated on every Paris =
channel=20
>>>> used during a mix? that would be huge if it did.
>>>>
>>>>
>>>>
>>>
>>>
>>
>>=20
>=20
>
------=_NextPart_000_00E8_01C86F5F.FD2EFB30
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.6000.16608" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY>
<DIV><FONT face=3DArial size=3D2>Well, I've been thinking about some =
aspects of=20
Paris that I really liked. However, there's still the situation with =
bussing=20
across submixes, but it's not something I couldn't =
overcome.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>I really miss the Paris EQ and FX =
actually. They=20
are much better, IMO, than any VST plugins I've heard that aren't DSP=20
driven.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>the more I delve into Cubase, the more =
things about=20
it that I like, but also, the more sonic weaknesses I see vis-a-vis =
Paris. It's=20
<EM>possible</EM> to do the "big" thing in Cubase, it's <EM>easy</EM> to =
do it=20
in Paris. I miss the <EM>easy</EM> part. </FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>I think I'd be a bit more satisfied =
with Cubase if=20
I was using a DM2000 with digital I/O options that would =
accommodate=20
my outboard gear. Anybody got a spare $20k laying around?</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>"Aaron Allen" <</FONT><A=20
href=3D"mailto:know-spam@not_here.dude"><FONT face=3DArial=20
size=3D2>know-spam@not_here.dude</FONT></A><FONT face=3DArial =
size=3D2>> wrote in=20
message </FONT><A href=3D"news:47b5217d@linux"><FONT face=3DArial=20
size=3D2>news:47b5217d@linux</FONT></A><FONT face=3DArial=20
size=3D2>...</FONT></DIV><FONT face=3DArial size=3D2>>I thought you =
were trying to=20
simplify :)<BR>> <BR>> AA<BR>> <BR>> <BR>> "Deej" =
<</FONT><A=20
href=3D"mailto:noway@jose.net"><FONT face=3DArial=20
size=3D2>noway@jose.net</FONT></A><FONT face=3DArial size=3D2>> wrote =
in message=20
</FONT><A href=3D"news:47b51030$1@linux"><FONT face=3DArial=20
size=3D2>news:47b51030$1@linux</FONT></A><FONT face=3DArial =
size=3D2>...<BR>>>=20
So basically, if you put this on each channel any plugin you add to that =
<BR>>> channel will report it's latency and then all channels can =
be=20
adjusted to <BR>>> compensate for this amount of latency? If this =
is=20
cumulative, that is <BR>>> basically the same as having PDC. The =
only=20
difference is a mouse click <BR>>> each time you add a plugin so =
that the=20
remaining channels adjust to the <BR>>> additional=20
latency.<BR>>><BR>>> Does this work with the high cumulative =
latency=20
numbers that are incurred <BR>>> when UAD-1 plugins are stacked on =
tracks?<BR>>><BR>>> I guess, what I'm getting at here is if =
I were=20
to put together another <BR>>> Paris DAW, say 4 x Cards (which I =
know I=20
can channel to a single IRQ on a <BR>>> 13 slot Magma) and =
then have=20
my other Magma in use running the two POCO's <BR>>> and 4 x UAD-1 =
cards, I=20
could have a Paris DAW that that would integrate <BR>>> UAD-1 and =
POCO=20
plugins and I wouldn't have to jack around with nudge/slide <BR>>> =
or=20
Sampleslide?.....I could just click a mouse every time I added another=20
<BR>>> plug and everything would be=20
compensated?<BR>>><BR>>><BR >>> "Don Nafe" =
<</FONT><A=20
href=3D"mailto:dnafe@magma.ca"><FONT face=3DArial=20
size=3D2>dnafe@magma.ca</FONT></A><FONT face=3DArial size=3D2>> wrote =
in message=20
</FONT><A href=3D"news:47b4cb97@linux"><FONT face=3DArial=20
size=3D2>news:47b4cb97@linux</FONT></A><FONT face=3DArial =
size=3D2>...<BR>>>>=20
I'm still not sure whether it automatically detects a plugin's latency=20
<BR>>>> (where applicable)<BR>>>><BR>>>> but =
yes, put=20
it on each channel, throw in aplugin and input it's latency =
<BR>>>> and=20
Bob's your Uncle...latencey adjustment across all=20
channels.<BR>>>><BR>>>> Nice thing is if you add a =
different=20
plugin to a different channel you <BR>>>> just have to input =
that=20
letency on that channelss faderwork plug and all <BR>>>> =
channels get=20
adjusted accordingly (and so on and so=20
on....<BR>>>><BR>>>> <BR>>>> "Deej" =
<</FONT><A=20
href=3D"mailto:noway@jose.net"><FONT face=3DArial=20
size=3D2>noway@jose.net</FONT></A><FONT face=3DArial size=3D2>> wrote =
in message=20
</FONT><A href=3D"news:47b4b204@linux"><FONT face=3DArial=20
size=3D2>news:47b4b204@linux</FONT></A><FONT face=3DArial=20
size=3D2>...<BR>>>>> </FONT><A=20
href=3D" http://www.vertexdsp.com/products/ReleaseNotes_FaderWorks.rt f"><F=
ONT=20
face=3DArial=20
size=3D2> http://www.vertexdsp.com/products/ReleaseNotes_FaderWorks.rt f</F=
ONT></A><BR><FONT=20
face=3DArial size=3D2>>>>><BR>>>>> Before I sold =
my Paris=20
system, I bought this plugin. I have never even <BR>>>>> =
used it.=20
Does it now provide PDC if instantiated on every Paris channel=20
<BR>>>>> used during a mix? that would be huge if it=20
did.<BR>>>>><BR>>>>> <BR>>>>><BR>>&=
gt;><BR>>>><BR>>> <BR>>>=20
<BR>> <BR>></FONT></BODY></HTML>
------=_NextPart_000_00E8_01C86F5F.FD2EFB30--
|
|
|
|
| Re: So does this automatically compensate for Paris latency? [message #95985 is a reply to message #95983] |
Thu, 14 February 2008 22:29 |
Aaron Allen
Messages: 1988
Registered: May 2008
|
Senior Member |
|
|
This is a multi-part message in MIME format.
------=_NextPart_000_001A_01C86F69.D7AE4230
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
That's about it man, and why Paris lives on at my place. I can't get =
away from knowing it sonically so well, the magic glue the bus provides, =
along with the punch I/O love. To be honest though, the UAD latency =
pissed me off so much I just yanked the card and static bagged it. It's =
probably bound for my non DSP native rig soon as I get the time.=20
BTW, don't forget that the Paris EQ is available as a VST.=20
"Deej" <noway@jose.net> wrote in message news:47b5321a@linux...
Well, I've been thinking about some aspects of Paris that I really =
liked. However, there's still the situation with bussing across =
submixes, but it's not something I couldn't overcome.
I really miss the Paris EQ and FX actually. They are much better, IMO, =
than any VST plugins I've heard that aren't DSP driven.
the more I delve into Cubase, the more things about it that I like, =
but also, the more sonic weaknesses I see vis-a-vis Paris. It's possible =
to do the "big" thing in Cubase, it's easy to do it in Paris. I miss the =
easy part.=20
I think I'd be a bit more satisfied with Cubase if I was using a =
DM2000 with digital I/O options that would accommodate my outboard gear. =
Anybody got a spare $20k laying around?
"Aaron Allen" <know-spam@not_here.dude> wrote in message =
news:47b5217d@linux...
>I thought you were trying to simplify :)
>=20
> AA
>=20
>=20
> "Deej" <noway@jose.net> wrote in message news:47b51030$1@linux...
>> So basically, if you put this on each channel any plugin you add to =
that=20
>> channel will report it's latency and then all channels can be =
adjusted to=20
>> compensate for this amount of latency? If this is cumulative, that =
is=20
>> basically the same as having PDC. The only difference is a mouse =
click=20
>> each time you add a plugin so that the remaining channels adjust to =
the=20
>> additional latency.
>>
>> Does this work with the high cumulative latency numbers that are =
incurred=20
>> when UAD-1 plugins are stacked on tracks?
>>
>> I guess, what I'm getting at here is if I were to put together =
another=20
>> Paris DAW, say 4 x Cards (which I know I can channel to a single =
IRQ on a=20
>> 13 slot Magma) and then have my other Magma in use running the two =
POCO's=20
>> and 4 x UAD-1 cards, I could have a Paris DAW that that would =
integrate=20
>> UAD-1 and POCO plugins and I wouldn't have to jack around with =
nudge/slide=20
>> or Sampleslide?.....I could just click a mouse every time I added =
another=20
>> plug and everything would be compensated?
>>
>>
>> "Don Nafe" <dnafe@magma.ca> wrote in message news:47b4cb97@linux...
>>> I'm still not sure whether it automatically detects a plugin's =
latency=20
>>> (where applicable)
>>>
>>> but yes, put it on each channel, throw in aplugin and input it's =
latency=20
>>> and Bob's your Uncle...latencey adjustment across all channels.
>>>
>>> Nice thing is if you add a different plugin to a different channel =
you=20
>>> just have to input that letency on that channelss faderwork plug =
and all=20
>>> channels get adjusted accordingly (and so on and so on....
>>>
>>>
>>> "Deej" <noway@jose.net> wrote in message news:47b4b204@linux...
>>>> http://www.vertexdsp.com/products/ReleaseNotes_FaderWorks.rt f
>>>>
>>>> Before I sold my Paris system, I bought this plugin. I have never =
even=20
>>>> used it. Does it now provide PDC if instantiated on every Paris =
channel=20
>>>> used during a mix? that would be huge if it did.
>>>>
>>>>
>>>>
>>>
>>>
>>
>>=20
>=20
>
------=_NextPart_000_001A_01C86F69.D7AE4230
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.6000.16608" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>That's about it man, and why Paris =
lives on at my=20
place. I can't get away from knowing it sonically so well, the magic =
glue the=20
bus provides, along with the punch I/O love. To be honest though, the =
UAD=20
latency pissed me off so much I just yanked the card and static bagged =
it. It's=20
probably bound for my non DSP native rig soon as I get the time. =
</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>BTW, don't forget that the Paris EQ is =
available as=20
a VST. </FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV> </DIV>
<BLOCKQUOTE=20
style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; =
BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
<DIV>"Deej" <<A =
href=3D"mailto:noway@jose.net">noway@jose.net</A>> wrote=20
in message <A =
href=3D"news:47b5321a@linux">news:47b5321a@linux</A>...</DIV>
<DIV><FONT face=3DArial size=3D2>Well, I've been thinking about some =
aspects of=20
Paris that I really liked. However, there's still the situation with =
bussing=20
across submixes, but it's not something I couldn't =
overcome.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>I really miss the Paris EQ and FX =
actually. They=20
are much better, IMO, than any VST plugins I've heard that aren't DSP=20
driven.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>the more I delve into Cubase, the =
more things=20
about it that I like, but also, the more sonic weaknesses I see =
vis-a-vis=20
Paris. It's <EM>possible</EM> to do the "big" thing in Cubase, it's=20
<EM>easy</EM> to do it in Paris. I miss the <EM>easy</EM> part. =
</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>I think I'd be a bit more satisfied =
with Cubase=20
if I was using a DM2000 with digital I/O options that would=20
accommodate my outboard gear. Anybody got a spare $20k laying=20
around?</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>"Aaron Allen" <</FONT><A=20
href=3D"mailto:know-spam@not_here.dude"><FONT face=3DArial=20
size=3D2>know-spam@not_here.dude</FONT></A><FONT face=3DArial =
size=3D2>> wrote in=20
message </FONT><A href=3D"news:47b5217d@linux"><FONT face=3DArial=20
size=3D2>news:47b5217d@linux</FONT></A><FONT face=3DArial=20
size=3D2>...</FONT></DIV><FONT face=3DArial size=3D2>>I thought you =
were trying=20
to simplify :)<BR>> <BR>> AA<BR>> <BR>> <BR>> "Deej"=20
<</FONT><A href=3D"mailto:noway@jose.net"><FONT face=3DArial=20
size=3D2>noway@jose.net</FONT></A><FONT face=3DArial size=3D2>> =
wrote in message=20
</FONT><A href=3D"news:47b51030$1@linux"><FONT face=3DArial=20
size=3D2>news:47b51030$1@linux</FONT></A><FONT face=3DArial =
size=3D2>...<BR>>>=20
So basically, if you put this on each channel any plugin you add to =
that=20
<BR>>> channel will report it's latency and then all channels =
can be=20
adjusted to <BR>>> compensate for this amount of latency? If =
this is=20
cumulative, that is <BR>>> basically the same as having PDC. The =
only=20
difference is a mouse click <BR>>> each time you add a plugin so =
that=20
the remaining channels adjust to the <BR>>> additional=20
latency.<BR>>><BR>>> Does this work with the high =
cumulative=20
latency numbers that are incurred <BR>>> when UAD-1 plugins are =
stacked=20
on tracks?<BR>>><BR>>> I guess, what I'm getting at here =
is if I=20
were to put together another <BR>>> Paris DAW, say 4 x Cards =
(which I=20
know I can channel to a single IRQ on a <BR>>> 13 slot =
Magma) and=20
then have my other Magma in use running the two POCO's <BR>>> =
and 4 x=20
UAD-1 cards, I could have a Paris DAW that that would integrate =
<BR>>>=20
UAD-1 and POCO plugins and I wouldn't have to jack around with =
nudge/slide=20
<BR>>> or Sampleslide?.....I could just click a mouse every time =
I added=20
another <BR>>> plug and everything would be=20
compensated?<BR>>><BR>>><BR >>> "Don Nafe" =
<</FONT><A=20
href=3D"mailto:dnafe@magma.ca"><FONT face=3DArial=20
size=3D2>dnafe@magma.ca</FONT></A><FONT face=3DArial size=3D2>> =
wrote in message=20
</FONT><A href=3D"news:47b4cb97@linux"><FONT face=3DArial=20
size=3D2>news:47b4cb97@linux</FONT></A><FONT face=3DArial=20
size=3D2>...<BR>>>> I'm still not sure whether it =
automatically detects=20
a plugin's latency <BR>>>> (where=20
applicable)<BR>>>><BR>>>> but yes, put it on each =
channel,=20
throw in aplugin and input it's latency <BR>>>> and Bob's =
your=20
Uncle...latencey adjustment across all=20
channels.<BR>>>><BR>>>> Nice thing is if you add a =
different=20
plugin to a different channel you <BR>>>> just have to input =
that=20
letency on that channelss faderwork plug and all <BR>>>> =
channels get=20
adjusted accordingly (and so on and so=20
on....<BR>>>><BR>>>> <BR>>>> "Deej" =
<</FONT><A=20
href=3D"mailto:noway@jose.net"><FONT face=3DArial=20
size=3D2>noway@jose.net</FONT></A><FONT face=3DArial size=3D2>> =
wrote in message=20
</FONT><A href=3D"news:47b4b204@linux"><FONT face=3DArial=20
size=3D2>news:47b4b204@linux</FONT></A><FONT face=3DArial=20
size=3D2>...<BR>>>>> </FONT><A=20
=
href=3D" http://www.vertexdsp.com/products/ReleaseNotes_FaderWorks.rt f"><F=
ONT=20
face=3DArial=20
=
size=3D2> http://www.vertexdsp.com/products/ReleaseNotes_FaderWorks.rt f</F=
ONT></A><BR><FONT=20
face=3DArial size=3D2>>>>><BR>>>>> Before I =
sold my Paris=20
system, I bought this plugin. I have never even <BR>>>>> =
used it.=20
Does it now provide PDC if instantiated on every Paris channel=20
<BR>>>>> used during a mix? that would be huge if it=20
=
did.<BR>>>>><BR>>>>> <BR>>>>><BR>>&=
gt;><BR>>>><BR>>> <BR>>>=20
<BR>> <BR>></FONT> </BLOCKQUOTE></BODY></HTML>
------=_NextPart_000_001A_01C86F69.D7AE4230--
|
|
|
|
| Re: So does this automatically compensate for Paris latency? [message #95987 is a reply to message #95985] |
Thu, 14 February 2008 22:35 |
Deej [5]
Messages: 373
Registered: March 2008
|
Senior Member |
|
|
This is a multi-part message in MIME format.
------=_NextPart_000_0111_01C86F62.45B0EC40
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
I had forgotten about the Paris VST EQ. You got a link? Actually, now =
that I think about it, I think I bought it years ago. Not sure WTF I put =
it though.
"Aaron Allen" <know-spam@not_here.dude> wrote in message =
news:47b5348f@linux...
That's about it man, and why Paris lives on at my place. I can't get =
away from knowing it sonically so well, the magic glue the bus provides, =
along with the punch I/O love. To be honest though, the UAD latency =
pissed me off so much I just yanked the card and static bagged it. It's =
probably bound for my non DSP native rig soon as I get the time.=20
BTW, don't forget that the Paris EQ is available as a VST.=20
"Deej" <noway@jose.net> wrote in message news:47b5321a@linux...
Well, I've been thinking about some aspects of Paris that I really =
liked. However, there's still the situation with bussing across =
submixes, but it's not something I couldn't overcome.
I really miss the Paris EQ and FX actually. They are much better, =
IMO, than any VST plugins I've heard that aren't DSP driven.
the more I delve into Cubase, the more things about it that I like, =
but also, the more sonic weaknesses I see vis-a-vis Paris. It's possible =
to do the "big" thing in Cubase, it's easy to do it in Paris. I miss the =
easy part.=20
I think I'd be a bit more satisfied with Cubase if I was using a =
DM2000 with digital I/O options that would accommodate my outboard gear. =
Anybody got a spare $20k laying around?
"Aaron Allen" <know-spam@not_here.dude> wrote in message =
news:47b5217d@linux...
>I thought you were trying to simplify :)
>=20
> AA
>=20
>=20
> "Deej" <noway@jose.net> wrote in message news:47b51030$1@linux...
>> So basically, if you put this on each channel any plugin you add =
to that=20
>> channel will report it's latency and then all channels can be =
adjusted to=20
>> compensate for this amount of latency? If this is cumulative, =
that is=20
>> basically the same as having PDC. The only difference is a mouse =
click=20
>> each time you add a plugin so that the remaining channels adjust =
to the=20
>> additional latency.
>>
>> Does this work with the high cumulative latency numbers that are =
incurred=20
>> when UAD-1 plugins are stacked on tracks?
>>
>> I guess, what I'm getting at here is if I were to put together =
another=20
>> Paris DAW, say 4 x Cards (which I know I can channel to a single =
IRQ on a=20
>> 13 slot Magma) and then have my other Magma in use running the =
two POCO's=20
>> and 4 x UAD-1 cards, I could have a Paris DAW that that would =
integrate=20
>> UAD-1 and POCO plugins and I wouldn't have to jack around with =
nudge/slide=20
>> or Sampleslide?.....I could just click a mouse every time I added =
another=20
>> plug and everything would be compensated?
>>
>>
>> "Don Nafe" <dnafe@magma.ca> wrote in message =
news:47b4cb97@linux...
>>> I'm still not sure whether it automatically detects a plugin's =
latency=20
>>> (where applicable)
>>>
>>> but yes, put it on each channel, throw in aplugin and input it's =
latency=20
>>> and Bob's your Uncle...latencey adjustment across all channels.
>>>
>>> Nice thing is if you add a different plugin to a different =
channel you=20
>>> just have to input that letency on that channelss faderwork plug =
and all=20
>>> channels get adjusted accordingly (and so on and so on....
>>>
>>>
>>> "Deej" <noway@jose.net> wrote in message news:47b4b204@linux...
>>>> http://www.vertexdsp.com/products/ReleaseNotes_FaderWorks.rt f
>>>>
>>>> Before I sold my Paris system, I bought this plugin. I have =
never even=20
>>>> used it. Does it now provide PDC if instantiated on every Paris =
channel=20
>>>> used during a mix? that would be huge if it did.
>>>>
>>>>
>>>>
>>>
>>>
>>
>>=20
>=20
>
------=_NextPart_000_0111_01C86F62.45B0EC40
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.6000.16608" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>I had forgotten about the Paris VST EQ. =
You got a=20
link? Actually, now that I think about it, I think I bought it years =
ago. Not=20
sure WTF I put it though.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; =
BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
<DIV>"Aaron Allen" <<A=20
=
href=3D"mailto:know-spam@not_here.dude">know-spam@not_here.dude</A>> =
wrote in=20
message <A =
href=3D"news:47b5348f@linux">news:47b5348f@linux</A>...</DIV>
<DIV><FONT face=3DArial size=3D2>That's about it man, and why Paris =
lives on at my=20
place. I can't get away from knowing it sonically so well, the magic =
glue the=20
bus provides, along with the punch I/O love. To be honest though, the =
UAD=20
latency pissed me off so much I just yanked the card and static bagged =
it.=20
It's probably bound for my non DSP native rig soon as I get the time.=20
</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>BTW, don't forget that the Paris EQ =
is available=20
as a VST. </FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV> </DIV>
<BLOCKQUOTE=20
style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; =
BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
<DIV>"Deej" <<A =
href=3D"mailto:noway@jose.net">noway@jose.net</A>> wrote=20
in message <A =
href=3D"news:47b5321a@linux">news:47b5321a@linux</A>...</DIV>
<DIV><FONT face=3DArial size=3D2>Well, I've been thinking about some =
aspects of=20
Paris that I really liked. However, there's still the situation with =
bussing=20
across submixes, but it's not something I couldn't =
overcome.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>I really miss the Paris EQ and FX =
actually.=20
They are much better, IMO, than any VST plugins I've heard that =
aren't DSP=20
driven.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>the more I delve into Cubase, the =
more things=20
about it that I like, but also, the more sonic weaknesses I see =
vis-a-vis=20
Paris. It's <EM>possible</EM> to do the "big" thing in Cubase, it's=20
<EM>easy</EM> to do it in Paris. I miss the <EM>easy</EM> part.=20
</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>I think I'd be a bit more satisfied =
with Cubase=20
if I was using a DM2000 with digital I/O options that =
would=20
accommodate my outboard gear. Anybody got a spare $20k laying=20
around?</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>"Aaron Allen" <</FONT><A=20
href=3D"mailto:know-spam@not_here.dude"><FONT face=3DArial=20
size=3D2>know-spam@not_here.dude</FONT></A><FONT face=3DArial =
size=3D2>> wrote=20
in message </FONT><A href=3D"news:47b5217d@linux"><FONT face=3DArial =
size=3D2>news:47b5217d@linux</FONT></A><FONT face=3DArial=20
size=3D2>...</FONT></DIV><FONT face=3DArial size=3D2>>I thought =
you were trying=20
to simplify :)<BR>> <BR>> AA<BR>> <BR>> <BR>> "Deej"=20
<</FONT><A href=3D"mailto:noway@jose.net"><FONT face=3DArial=20
size=3D2>noway@jose.net</FONT></A><FONT face=3DArial size=3D2>> =
wrote in=20
message </FONT><A href=3D"news:47b51030$1@linux"><FONT face=3DArial=20
size=3D2>news:47b51030$1@linux</FONT></A><FONT face=3DArial=20
size=3D2>...<BR>>> So basically, if you put this on each =
channel any=20
plugin you add to that <BR>>> channel will report it's latency =
and=20
then all channels can be adjusted to <BR>>> compensate for =
this amount=20
of latency? If this is cumulative, that is <BR>>> basically =
the same=20
as having PDC. The only difference is a mouse click <BR>>> =
each time=20
you add a plugin so that the remaining channels adjust to the =
<BR>>>=20
additional latency.<BR>>><BR>>> Does this work with the =
high=20
cumulative latency numbers that are incurred <BR>>> when UAD-1 =
plugins=20
are stacked on tracks?<BR>>><BR>>> I guess, what I'm =
getting at=20
here is if I were to put together another <BR>>> Paris DAW, =
say 4 x=20
Cards (which I know I can channel to a single IRQ on a =
<BR>>> 13=20
slot Magma) and then have my other Magma in use running the two =
POCO's=20
<BR>>> and 4 x UAD-1 cards, I could have a Paris DAW that that =
would=20
integrate <BR>>> UAD-1 and POCO plugins and I wouldn't have to =
jack=20
around with nudge/slide <BR>>> or Sampleslide?.....I could =
just click=20
a mouse every time I added another <BR>>> plug and everything =
would be=20
compensated?<BR>>><BR>>><BR >>> "Don Nafe" =
<</FONT><A=20
href=3D"mailto:dnafe@magma.ca"><FONT face=3DArial=20
size=3D2>dnafe@magma.ca</FONT></A><FONT face=3DArial size=3D2>> =
wrote in=20
message </FONT><A href=3D"news:47b4cb97@linux"><FONT face=3DArial=20
size=3D2>news:47b4cb97@linux</FONT></A><FONT face=3DArial=20
size=3D2>...<BR>>>> I'm still not sure whether it =
automatically=20
detects a plugin's latency <BR>>>> (where=20
applicable)<BR>>>><BR>>>> but yes, put it on each =
channel,=20
throw in aplugin and input it's latency <BR>>>> and Bob's =
your=20
Uncle...latencey adjustment across all=20
channels.<BR>>>><BR>>>> Nice thing is if you add a =
different plugin to a different channel you <BR>>>> just =
have to=20
input that letency on that channelss faderwork plug and all =
<BR>>>>=20
channels get adjusted accordingly (and so on and so=20
on....<BR>>>><BR>>>> <BR>>>> "Deej" =
<</FONT><A=20
href=3D"mailto:noway@jose.net"><FONT face=3DArial=20
size=3D2>noway@jose.net</FONT></A><FONT face=3DArial size=3D2>> =
wrote in=20
message </FONT><A href=3D"news:47b4b204@linux"><FONT face=3DArial=20
size=3D2>news:47b4b204@linux</FONT></A><FONT face=3DArial=20
size=3D2>...<BR>>>>> </FONT><A=20
=
href=3D" http://www.vertexdsp.com/products/ReleaseNotes_FaderWorks.rt f"><F=
ONT=20
face=3DArial=20
=
size=3D2> http://www.vertexdsp.com/products/ReleaseNotes_FaderWorks.rt f</F=
ONT></A><BR><FONT=20
face=3DArial size=3D2>>>>><BR>>>>> Before I =
sold my=20
Paris system, I bought this plugin. I have never even =
<BR>>>>>=20
used it. Does it now provide PDC if instantiated on every Paris =
channel=20
<BR>>>>> used during a mix? that would be huge if it=20
=
did.<BR>>>>><BR>>>>> <BR>>>>><BR>>&=
gt;><BR>>>><BR>>> <BR>>>=20
<BR>> <BR>></FONT> </BLOCKQUOTE></BLOCKQUOTE></BODY></HTML>
------=_NextPart_000_0111_01C86F62.45B0EC40--
|
|
|
|
|
|
| Re: So does this automatically compensate for Paris latency? [message #96013 is a reply to message #95983] |
Fri, 15 February 2008 15:20 |
Martin Harrington
Messages: 560
Registered: September 2005
|
Senior Member |
|
|
> This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.
--B_3286002021_5305604
Content-type: text/plain;
charset="ISO-8859-1"
Content-transfer-encoding: 8bit
Deej.
Surely if you equate all the gear that you¹ve bought to find Native utopia,
and add the man hours spent, (at whatever rate you choose), you would easily
have spent over $20,000 dollars on your investment.
Makes the DM 2000 an attractive proposition.
Martin Harrington
On 15/2/08 5:19 PM, in article 47b5321a@linux, "Deej" <noway@jose.net>
wrote:
> Well, I've been thinking about some aspects of Paris that I really liked.
> However, there's still the situation with bussing across submixes, but it's
> not something I couldn't overcome.
>
> I really miss the Paris EQ and FX actually. They are much better, IMO, than
> any VST plugins I've heard that aren't DSP driven.
>
> the more I delve into Cubase, the more things about it that I like, but also,
> the more sonic weaknesses I see vis-a-vis Paris. It's possible to do the "big"
> thing in Cubase, it's easy to do it in Paris. I miss the easy part.
>
> I think I'd be a bit more satisfied with Cubase if I was using a DM2000 with
> digital I/O options that would accommodate my outboard gear. Anybody got a
> spare $20k laying around?
>
>
>
>
> "Aaron Allen" <know-spam@not_here.dude <mailto:know-spam@not_here.dude> >
> wrote in message news:47b5217d@linux <news:47b5217d@linux> ...
>> >I thought you were trying to simplify :)
>> >
>> > AA
>> >
>> >
>> > "Deej" <noway@jose.net <mailto:noway@jose.net> > wrote in message
>> news:47b51030$1@linux <news:47b51030$1@linux> ...
>>> >> So basically, if you put this on each channel any plugin you add to that
>>> >> channel will report it's latency and then all channels can be adjusted to
>>> >> compensate for this amount of latency? If this is cumulative, that is
>>> >> basically the same as having PDC. The only difference is a mouse click
>>> >> each time you add a plugin so that the remaining channels adjust to the
>>> >> additional latency.
>>> >>
>>> >> Does this work with the high cumulative latency numbers that are incurred
>>> >> when UAD-1 plugins are stacked on tracks?
>>> >>
>>> >> I guess, what I'm getting at here is if I were to put together another
>>> >> Paris DAW, say 4 x Cards (which I know I can channel to a single IRQ on
a
>>> >> 13 slot Magma) and then have my other Magma in use running the two POCO's
>>> >> and 4 x UAD-1 cards, I could have a Paris DAW that that would integrate
>>> >> UAD-1 and POCO plugins and I wouldn't have to jack around with
>>> nudge/slide
>>> >> or Sampleslide?.....I could just click a mouse every time I added another
>>> >> plug and everything would be compensated?
>>> >>
>>> >>
>>> >> "Don Nafe" <dnafe@magma.ca <mailto:dnafe@magma.ca> > wrote in message
>>> news:47b4cb97@linux <news:47b4cb97@linux> ...
>>>> >>> I'm still not sure whether it automatically detects a plugin's latency
>>>> >>> (where applicable)
>>>> >>>
>>>> >>> but yes, put it on each channel, throw in aplugin and input it's
>>>> latency
>>>> >>> and Bob's your Uncle...latencey adjustment across all channels.
>>>> >>>
>>>> >>> Nice thing is if you add a different plugin to a different channel you
>>>> >>> just have to input that letency on that channelss faderwork plug and
>>>> all
>>>> >>> channels get adjusted accordingly (and so on and so on....
>>>> >>>
>>>> >>>
>>>> >>> "Deej" <noway@jose.net <mailto:noway@jose.net> > wrote in message
>>>> news:47b4b204@linux <news:47b4b204@linux> ...
>>>>> >>>> http://www.vertexdsp.com/products/ReleaseNotes_FaderWorks.rt f
>>>>> < http://www.vertexdsp.com/products/ReleaseNotes_FaderWorks.rt f>
>>>>> >>>>
>>>>> >>>> Before I sold my Paris system, I bought this plugin. I have never
>>>>> even
>>>>> >>>> used it. Does it now provide PDC if instantiated on every Paris
>>>>> channel
>>>>> >>>> used during a mix? that would be huge if it did.
>>>>> >>>>
>>>>> >>>>
>>>>> >>>>
>>>> >>>
>>>> >>>
>>> >>
>>> >>
>> >
>> >
--B_3286002021_5305604
Content-type: text/html;
charset="ISO-8859-1"
Content-transfer-encoding: quoted-printable
<HTML>
<HEAD>
<TITLE>Re: So does this automatically compensate for Paris latency?</TITLE>
</HEAD>
<BODY>
<FONT FACE=3D"Verdana, Helvetica, Arial"><SPAN STYLE=3D'font-size:12.0px'>Deej.=
<BR>
<BR>
Surely if you equate all the gear that you’ve bought to find Native u=
topia, and add the man hours spent, (at whatever rate you choose), you would=
easily have spent over $20,000 dollars on your investment.<BR>
Makes the DM 2000 an attractive proposition.<BR>
<BR>
Martin Harrington <BR>
<BR>
<BR>
<BR>
<BR>
On 15/2/08 5:19 PM, in article 47b5321a@linux, "Deej" <noway@j=
ose.net> wrote:<BR>
<BR>
</SPAN></FONT><BLOCKQUOTE><SPAN STYLE=3D'font-size:12.0px'><FONT FACE=3D"Arial"=
>Well, I've been thinking about some aspects of Paris that I really liked. H=
owever, there's still the situation with bussing across submixes, but it's n=
ot something I couldn't overcome.<BR>
</FONT><FONT FACE=3D"Verdana, Helvetica, Arial"> <BR>
</FONT><FONT FACE=3D"Arial">I really miss the Paris EQ and FX actually. They =
are much better, IMO, than any VST plugins I've heard that aren't DSP driven=
..<BR>
</FONT><FONT FACE=3D"Verdana, Helvetica, Arial"> <BR>
</FONT><FONT FACE=3D"Arial">the more I delve into Cubase, the more things abo=
ut it that I like, but also, the more sonic weaknesses I see vis-a-vis Paris=
.. It's <I>possible</I> to do the "big" thing in Cubase, it's <I>ea=
sy</I> to do it in Paris. I miss the <I>easy</I> part. <BR>
</FONT><FONT FACE=3D"Verdana, Helvetica, Arial"> <BR>
</FONT><FONT FACE=3D"Arial">I think I'd be a bit more satisfied with Cubase i=
f I was using a DM2000 with digital I/O options that would accommodate my ou=
tboard gear. Anybody got a spare $20k laying around?<BR>
</FONT><FONT FACE=3D"Verdana, Helvetica, Arial"> <BR>
<BR>
<BR>
<BR>
</FONT><FONT FACE=3D"Arial">"Aaron Allen" <know-spam@not_here.du=
de</FONT><FONT FACE=3D"Verdana, Helvetica, Arial"> <a href=3D"mailto:know-spam@n=
ot_here.dude"><mailto:know-spam@not_here.dude></a> </FONT><FONT FACE=3D"=
Arial">> wrote in message news:47b5217d@linux</FONT><FONT FACE=3D"Verdana, =
Helvetica, Arial"> <news:47b5217d@linux> </FONT><FONT FACE=3D"Arial">...=
<BR>
>I thought you were trying to simplify :)<BR>
> <BR>
> AA<BR>
> <BR>
> <BR>
> "Deej" <noway@jose.net</FONT><FONT FACE=3D"Verdana, Helveti=
ca, Arial"> <a href=3D"mailto:noway@jose.net"><mailto:noway@jose.net></a=
> </FONT><FONT FACE=3D"Arial">> wrote in message news:47b51030$1@linux</FON=
T><FONT FACE=3D"Verdana, Helvetica, Arial"> <news:47b51030$1@linux> </FO=
NT><FONT FACE=3D"Arial">...<BR>
>> So basically, if you put this on each channel any plugin you add t=
o that <BR>
>> channel will report it's latency and then all channels can be adju=
sted to <BR>
>> compensate for this amount of latency? If this is cumulative, that=
is <BR>
>> basically the same as having PDC. The only difference is a mouse c=
lick <BR>
>> each time you add a plugin so that the remaining channels adjust t=
o the <BR>
>> additional latency.<BR>
>><BR>
>> Does this work with the high cumulative latency numbers that are i=
ncurred <BR>
>> when UAD-1 plugins are stacked on tracks?<BR>
>><BR>
>> I guess, what I'm getting at here is if I were to put together ano=
ther <BR>
>> Paris DAW, say 4 x Cards (which I know I can channel to a single &=
nbsp;IRQ on a <BR>
>> 13 slot Magma) and then have my other Magma in use running the two=
POCO's <BR>
>> and 4 x UAD-1 cards, I could have a Paris DAW that that would inte=
grate <BR>
>> UAD-1 and POCO plugins and I wouldn't have to jack around with nud=
ge/slide <BR>
>> or Sampleslide?.....I could just click a mouse every time I added =
another <BR>
>> plug and everything would be compensated?<BR>
>><BR>
>><BR>
>> "Don Nafe" <dnafe@magma.ca</FONT><FONT FACE=3D"Verdana,=
Helvetica, Arial"> <a href=3D"mailto:dnafe@magma.ca"><mailto:dnafe@magma.c=
a></a> </FONT><FONT FACE=3D"Arial">> wrote in message news:47b4cb97@linu=
x</FONT><FONT FACE=3D"Verdana, Helvetica, Arial"> <news:47b4cb97@linux> =
</FONT><FONT FACE=3D"Arial">...<BR>
>>> I'm still not sure whether it automatically detects a plugin's=
latency <BR>
>>> (where applicable)<BR>
>>><BR>
>>> but yes, put it on each channel, throw in aplugin and input it=
's latency <BR>
>>> and Bob's your Uncle...latencey adjustment across all channels=
..<BR>
>>><BR>
>>> Nice thing is if you add a different plugin to a different cha=
nnel you <BR>
>>> just have to input that letency on that channelss faderwork pl=
ug and all <BR>
>>> channels get adjusted accordingly (and so on and so on....<BR>
>>><BR>
>>><BR>
>>> "Deej" <noway@jose.net</FONT><FONT FACE=3D"Verdana,=
Helvetica, Arial"> <a href=3D"mailto:noway@jose.net"><mailto:noway@jose.ne=
t></a> </FONT><FONT FACE=3D"Arial">> wrote in message news:47b4b204@linu=
x</FONT><FONT FACE=3D"Verdana, Helvetica, Arial"> <news:47b4b204@linux> =
</FONT><FONT FACE=3D"Arial">...<BR>
>>>> <a href=3D"http://www.vertexdsp.com/products/ReleaseNotes_Fa=
derWorks.rtf"> http://www.vertexdsp.com/products/ReleaseNotes_FaderWorks.rt f<=
/a></FONT><FONT FACE=3D"Verdana, Helvetica, Arial"> <a href=3D"http://www.vertex=
dsp.com/products/ReleaseNotes_FaderWorks.rtf"><http://www.vertexdsp.com/p=
roducts/ReleaseNotes_FaderWorks.rtf></a> <BR>
</FONT><FONT FACE=3D"Arial">>>>><BR>
>>>> Before I sold my Paris system, I bought this plugin. I hav=
e never even <BR>
>>>> used it. Does it now provide PDC if instantiated on every =
Paris channel <BR>
>>>> used during a mix? that would be huge if it did.<BR>
>>>><BR>
>>>><BR>
>>>><BR>
>>><BR>
>>><BR>
>><BR>
>> <BR>
> <BR>
><BR>
</FONT></SPAN></BLOCKQUOTE><SPAN STYLE=3D'font-size:12.0px'><FONT FACE=3D"Verda=
na, Helvetica, Arial"><BR>
</FONT></SPAN>
</BODY>
</HTML>
--B_3286002021_5305604--
|
|
|
|
| Re: So does this automatically compensate for Paris latency? [message #96016 is a reply to message #95985] |
Fri, 15 February 2008 23:19 |
Rod Lincoln
Messages: 883
Registered: September 2005
|
Senior Member |
|
|
Curiously, what about the UAD latency stuff pisses you off? I know your a
way smart dude. It's really just nudging back 400 or 800 ms and applying
sampleslide at the appropriate values.
I'll admit, it's not as simple as ADC, but to me it doesn't seem that hard.
I'll admit that I am jonesing for a drum buss
comp that could operate with ADC when using Paris.
Rod
"Aaron Allen" <know-spam@not_here.dude> wrote:
>
>
>That's about it man, and why Paris lives on at my place. I can't get =
>away from knowing it sonically so well, the magic glue the bus provides,
=
>along with the punch I/O love. To be honest though, the UAD latency =
>pissed me off so much I just yanked the card and static bagged it. It's
=
>probably bound for my non DSP native rig soon as I get the time.=20
>
>BTW, don't forget that the Paris EQ is available as a VST.=20
>
>
> "Deej" <noway@jose.net> wrote in message news:47b5321a@linux...
> Well, I've been thinking about some aspects of Paris that I really =
>liked. However, there's still the situation with bussing across =
>submixes, but it's not something I couldn't overcome.
>
> I really miss the Paris EQ and FX actually. They are much better, IMO,
=
>than any VST plugins I've heard that aren't DSP driven.
>
> the more I delve into Cubase, the more things about it that I like, =
>but also, the more sonic weaknesses I see vis-a-vis Paris. It's possible
=
>to do the "big" thing in Cubase, it's easy to do it in Paris. I miss the
=
>easy part.=20
>
> I think I'd be a bit more satisfied with Cubase if I was using a =
>DM2000 with digital I/O options that would accommodate my outboard gear.
=
>Anybody got a spare $20k laying around?
>
>
>
>
> "Aaron Allen" <know-spam@not_here.dude> wrote in message =
>news:47b5217d@linux...
> >I thought you were trying to simplify :)
> >=20
> > AA
> >=20
> >=20
> > "Deej" <noway@jose.net> wrote in message news:47b51030$1@linux...
> >> So basically, if you put this on each channel any plugin you add to
=
>that=20
> >> channel will report it's latency and then all channels can be =
>adjusted to=20
> >> compensate for this amount of latency? If this is cumulative, that
=
>is=20
> >> basically the same as having PDC. The only difference is a mouse =
>click=20
> >> each time you add a plugin so that the remaining channels adjust to
=
>the=20
> >> additional latency.
> >>
> >> Does this work with the high cumulative latency numbers that are =
>incurred=20
> >> when UAD-1 plugins are stacked on tracks?
> >>
> >> I guess, what I'm getting at here is if I were to put together =
>another=20
> >> Paris DAW, say 4 x Cards (which I know I can channel to a single =
>IRQ on a=20
> >> 13 slot Magma) and then have my other Magma in use running the two
=
>POCO's=20
> >> and 4 x UAD-1 cards, I could have a Paris DAW that that would =
>integrate=20
> >> UAD-1 and POCO plugins and I wouldn't have to jack around with =
>nudge/slide=20
> >> or Sampleslide?.....I could just click a mouse every time I added =
>another=20
> >> plug and everything would be compensated?
> >>
> >>
> >> "Don Nafe" <dnafe@magma.ca> wrote in message news:47b4cb97@linux...
> >>> I'm still not sure whether it automatically detects a plugin's =
>latency=20
> >>> (where applicable)
> >>>
> >>> but yes, put it on each channel, throw in aplugin and input it's =
>latency=20
> >>> and Bob's your Uncle...latencey adjustment across all channels.
> >>>
> >>> Nice thing is if you add a different plugin to a different channel
=
>you=20
> >>> just have to input that letency on that channelss faderwork plug =
>and all=20
> >>> channels get adjusted accordingly (and so on and so on....
> >>>
> >>>
> >>> "Deej" <noway@jose.net> wrote in message news:47b4b204@linux...
> >>>> http://www.vertexdsp.com/products/ReleaseNotes_FaderWorks.rt f
> >>>>
> >>>> Before I sold my Paris system, I bought this plugin. I have never
=
>even=20
> >>>> used it. Does it now provide PDC if instantiated on every Paris =
>channel=20
> >>>> used during a mix? that would be huge if it did.
> >>>>
> >>>>
> >>>>
> >>>
> >>>
> >>
> >>=20
> >=20
> >
>
><!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
><HTML><HEAD>
><META http-equiv=3DContent-Type content=3D"text/html; =
>charset=3Diso-8859-1">
><META content=3D"MSHTML 6.00.6000.16608" name=3DGENERATOR>
><STYLE></STYLE>
></HEAD>
><BODY bgColor=3D#ffffff>
><DIV><FONT face=3DArial size=3D2>That's about it man, and why Paris =
>lives on at my=20
>place. I can't get away from knowing it sonically so well, the magic =
>glue the=20
>bus provides, along with the punch I/O love. To be honest though, the =
>UAD=20
>latency pissed me off so much I just yanked the card and static bagged =
>it. It's=20
>probably bound for my non DSP native rig soon as I get the time. =
></FONT></DIV>
><DIV><FONT face=3DArial size=3D2></FONT> </DIV>
><DIV><FONT face=3DArial size=3D2>BTW, don't forget that the Paris EQ is
=
>available as=20
>a VST. </FONT></DIV>
><DIV><FONT face=3DArial size=3D2></FONT> </DIV>
><DIV> </DIV>
><BLOCKQUOTE=20
>style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; =
>BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
> <DIV>"Deej" <<A =
>href=3D"mailto:noway@jose.net">noway@jose.net</A>> wrote=20
> in message <A =
>href=3D"news:47b5321a@linux">news:47b5321a@linux</A>...</DIV>
> <DIV><FONT face=3DArial size=3D2>Well, I've been thinking about some =
>aspects of=20
> Paris that I really liked. However, there's still the situation with =
>bussing=20
> across submixes, but it's not something I couldn't =
>overcome.</FONT></DIV>
> <DIV><FONT face=3DArial size=3D2></FONT> </DIV>
> <DIV><FONT face=3DArial size=3D2>I really miss the Paris EQ and FX =
>actually. They=20
> are much better, IMO, than any VST plugins I've heard that aren't DSP=20
> driven.</FONT></DIV>
> <DIV><FONT face=3DArial size=3D2></FONT> </DIV>
> <DIV><FONT face=3DArial size=3D2>the more I delve into Cubase, the =
>more things=20
> about it that I like, but also, the more sonic weaknesses I see =
>vis-a-vis=20
> Paris. It's <EM>possible</EM> to do the "big" thing in Cubase, it's=20
> <EM>easy</EM> to do it in Paris. I miss the <EM>easy</EM> part. =
></FONT></DIV>
> <DIV><FONT face=3DArial size=3D2></FONT> </DIV>
> <DIV><FONT face=3DArial size=3D2>I think I'd be a bit more satisfied =
>with Cubase=20
> if I was using a DM2000 with digital I/O options that would=20
> accommodate my outboard gear. Anybody got a spare $20k laying=20
> around?</FONT></DIV>
> <DIV><FONT face=3DArial size=3D2></FONT> </DIV>
> <DIV><FONT face=3DArial size=3D2></FONT> </DIV>
> <DIV><FONT face=3DArial size=3D2></FONT> </DIV>
> <DIV><FONT face=3DArial size=3D2></FONT> </DIV>
> <DIV><FONT face=3DArial size=3D2>"Aaron Allen" <</FONT><A=20
> href=3D"mailto:know-spam@not_here.dude"><FONT face=3DArial=20
> size=3D2>know-spam@not_here.dude</FONT></A><FONT face=3DArial =
>size=3D2>> wrote in=20
> message </FONT><A href=3D"news:47b5217d@linux"><FONT face=3DArial=20
> size=3D2>news:47b5217d@linux</FONT></A><FONT face=3DArial=20
> size=3D2>...</FONT></DIV><FONT face=3DArial size=3D2>>I thought you =
>were trying=20
> to simplify :)<BR>> <BR>> AA<BR>> <BR>> <BR>> "Deej"=20
> <</FONT><A href=3D"mailto:noway@jose.net"><FONT face=3DArial=20
> size=3D2>noway@jose.net</FONT></A><FONT face=3DArial size=3D2>> =
>wrote in message=20
> </FONT><A href=3D"news:47b51030$1@linux"><FONT face=3DArial=20
> size=3D2>news:47b51030$1@linux</FONT></A><FONT face=3DArial =
>size=3D2>...<BR>>>=20
> So basically, if you put this on each channel any plugin you add to =
>that=20
> <BR>>> channel will report it's latency and then all channels =
>can be=20
> adjusted to <BR>>> compensate for this amount of latency? If =
>this is=20
> cumulative, that is <BR>>> basically the same as having PDC. The =
>only=20
> difference is a mouse click <BR>>> each time you add a plugin so =
>that=20
> the remaining channels adjust to the <BR>>> additional=20
> latency.<BR>>><BR>>> Does this work with the high =
>cumulative=20
> latency numbers that are incurred <BR>>> when UAD-1 plugins are =
>stacked=20
> on tracks?<BR>>><BR>>> I guess, what I'm getting at here =
>is if I=20
> were to put together another <BR>>> Paris DAW, say 4 x Cards =
>(which I=20
> know I can channel to a single IRQ on a <BR>>> 13 slot =
>Magma) and=20
> then have my other Magma in use running the two POCO's <BR>>> =
>and 4 x=20
> UAD-1 cards, I could have a Paris DAW that that would integrate =
><BR>>>=20
> UAD-1 and POCO plugins and I wouldn't have to jack around with =
>nudge/slide=20
> <BR>>> or Sampleslide?.....I could just click a mouse every time =
>I added=20
> another <BR>>> plug and everything would be=20
> compensated?<BR>>><BR>>><BR>>> "Don Nafe" =
><</FONT><A=20
> href=3D"mailto:dnafe@magma.ca"><FONT face=3DArial=20
> size=3D2>dnafe@magma.ca</FONT></A><FONT face=3DArial size=3D2>> =
>wrote in message=20
> </FONT><A href=3D"news:47b4cb97@linux"><FONT face=3DArial=20
> size=3D2>news:47b4cb97@linux</FONT></A><FONT face=3DArial=20
> size=3D2>...<BR>>>> I'm still not sure whether it =
>automatically detects=20
> a plugin's latency <BR>>>> (where=20
> applicable)<BR>>>><BR>>>> but yes, put it on each =
>channel,=20
> throw in aplugin and input it's latency <BR>>>> and Bob's =
>your=20
> Uncle...latencey adjustment across all=20
> channels.<BR>>>><BR>>>> Nice thing is if you add a =
>different=20
> plugin to a different channel you <BR>>>> just have to input =
>that=20
> letency on that channelss faderwork plug and all <BR>>>> =
>channels get=20
> adjusted accordingly (and so on and so=20
> on....<BR>>>><BR>>>><BR>>>> "Deej" =
><</FONT><A=20
> href=3D"mailto:noway@jose.net"><FONT face=3DArial=20
> size=3D2>noway@jose.net</FONT></A><FONT face=3DArial size=3D2>> =
>wrote in message=20
> </FONT><A href=3D"news:47b4b204@linux"><FONT face=3DArial=20
> size=3D2>news:47b4b204@linux</FONT></A><FONT face=3DArial=20
> size=3D2>...<BR>>>>> </FONT><A=20
> =
>href=3D" http://www.vertexdsp.com/products/ReleaseNotes_FaderWorks.rt f"><F=
>ONT=20
> face=3DArial=20
> =
>size=3D2> http://www.vertexdsp.com/products/ReleaseNotes_FaderWorks.rt f</F=
>ONT></A><BR><FONT=20
> face=3DArial size=3D2>>>>><BR>>>>> Before I =
>sold my Paris=20
> system, I bought this plugin. I have never even <BR>>>>> =
>used it.=20
> Does it now provide PDC if instantiated on every Paris channel=20
> <BR>>>>> used during a mix? that would be huge if it=20
> =
>did.<BR>>>>><BR>>>>><BR>>>>><BR>>&=
>gt;><BR>>>><BR>>><BR>>>=20
> <BR>> <BR>></FONT> </BLOCKQUOTE></BODY></HTML>
>
>
|
|
|
|
| Re: So does this automatically compensate for Paris latency? [message #96017 is a reply to message #96016] |
Fri, 15 February 2008 23:23 |
Aaron Allen
Messages: 1988
Registered: May 2008
|
Senior Member |
|
|
Rod
Mostly, A/B comparisons and plug stacking - especially with mulit mic'd
source tracks. It becomes an exercise in math and presets just to make the
drum kit flow (in phase) with plugs and takes away the art form for the way
I like to work. I'm pretty freakish about the timing of the kit mics.
I could do the sample slide thing on the 'non' plug tracks and just remove
compensation delayed inserts as needed but that keeps the automation editor
kinda worthless (mostly on the drum kit) for manual/visual draws against the
wavform, and I'd much much rather automate and keep the natural thing
happenin than to compress/effect too much. I find that automate technique to
be absolute gold on a vocal track or for polishing those turds we all know
and love. To add to my frustration, I can do all those things and more in a
native app, render the move and dump it to paris so as not to have to fool
with it. But that's more time spent on things I should be able to do more
quickly in one app. And a personal flaw/peeve of mine is finding myself
focused on technical rather than musical details at mix time when I should
be making art, if that makes sense...
I even considered just using my creamware 3-card setup as a DSP farm via
adat pipes, but to be honest I found that interface taxing on my patience
and don't have a machine room anymore ..... so I have to be careful about
the amount of ambient noise in the room.
I know, I need to fix that (bad Aaron). Not enough positives there, and I
don't want to start a Deej inspired bank account war over here :)
Guess there's no magic bullet - yet. I think native apps are getting real
close though man, at least for me, to taking over as the main DAW of choice.
"Rod Lincoln" <rlincoln@nospam.kc.rr.com> wrote in message
news:47b6806f$1@linux...
>
> Curiously, what about the UAD latency stuff pisses you off? I know your a
> way smart dude. It's really just nudging back 400 or 800 ms and applying
> sampleslide at the appropriate values.
> I'll admit, it's not as simple as ADC, but to me it doesn't seem that
> hard.
> I'll admit that I am jonesing for a drum buss
> comp that could operate with ADC when using Paris.
> Rod
> "Aaron Allen" <know-spam@not_here.dude> wrote:
>>
>>
>>That's about it man, and why Paris lives on at my place. I can't get =
>>away from knowing it sonically so well, the magic glue the bus provides,
> =
>>along with the punch I/O love. To be honest though, the UAD latency =
>>pissed me off so much I just yanked the card and static bagged it. It's
> =
>>probably bound for my non DSP native rig soon as I get the time.=20
>>
>>BTW, don't forget that the Paris EQ is available as a VST.=20
>>
>>
>> "Deej" <noway@jose.net> wrote in message news:47b5321a@linux...
>> Well, I've been thinking about some aspects of Paris that I really =
>>liked. However, there's still the situation with bussing across =
>>submixes, but it's not something I couldn't overcome.
>>
>> I really miss the Paris EQ and FX actually. They are much better, IMO,
> =
>>than any VST plugins I've heard that aren't DSP driven.
>>
>> the more I delve into Cubase, the more things about it that I like, =
>>but also, the more sonic weaknesses I see vis-a-vis Paris. It's possible
> =
>>to do the "big" thing in Cubase, it's easy to do it in Paris. I miss the
> =
>>easy part.=20
>>
>> I think I'd be a bit more satisfied with Cubase if I was using a =
>>DM2000 with digital I/O options that would accommodate my outboard gear.
> =
>>Anybody got a spare $20k laying around?
>>
>>
>>
>>
>> "Aaron Allen" <know-spam@not_here.dude> wrote in message =
>>news:47b5217d@linux...
>> >I thought you were trying to simplify :)
>> >=20
>> > AA
>> >=20
>> >=20
>> > "Deej" <noway@jose.net> wrote in message news:47b51030$1@linux...
>> >> So basically, if you put this on each channel any plugin you add to
> =
>>that=20
>> >> channel will report it's latency and then all channels can be =
>>adjusted to=20
>> >> compensate for this amount of latency? If this is cumulative, that
> =
>>is=20
>> >> basically the same as having PDC. The only difference is a mouse =
>>click=20
>> >> each time you add a plugin so that the remaining channels adjust to
> =
>>the=20
>> >> additional latency.
>> >>
>> >> Does this work with the high cumulative latency numbers that are =
>>incurred=20
>> >> when UAD-1 plugins are stacked on tracks?
>> >>
>> >> I guess, what I'm getting at here is if I were to put together =
>>another=20
>> >> Paris DAW, say 4 x Cards (which I know I can channel to a single =
>>IRQ on a=20
>> >> 13 slot Magma) and then have my other Magma in use running the two
> =
>>POCO's=20
>> >> and 4 x UAD-1 cards, I could have a Paris DAW that that would =
>>integrate=20
>> >> UAD-1 and POCO plugins and I wouldn't have to jack around with =
>>nudge/slide=20
>> >> or Sampleslide?.....I could just click a mouse every time I added =
>>another=20
>> >> plug and everything would be compensated?
>> >>
>> >>
>> >> "Don Nafe" <dnafe@magma.ca> wrote in message news:47b4cb97@linux...
>> >>> I'm still not sure whether it automatically detects a plugin's =
>>latency=20
>> >>> (where applicable)
>> >>>
>> >>> but yes, put it on each channel, throw in aplugin and input it's =
>>latency=20
>> >>> and Bob's your Uncle...latencey adjustment across all channels.
>> >>>
>> >>> Nice thing is if you add a different plugin to a different channel
> =
>>you=20
>> >>> just have to input that letency on that channelss faderwork plug =
>>and all=20
>> >>> channels get adjusted accordingly (and so on and so on....
>> >>>
>> >>>
>> >>> "Deej" <noway@jose.net> wrote in message news:47b4b204@linux...
>> >>>> http://www.vertexdsp.com/products/ReleaseNotes_FaderWorks.rt f
>> >>>>
>> >>>> Before I sold my Paris system, I bought this plugin. I have never
> =
>>even=20
>> >>>> used it. Does it now provide PDC if instantiated on every Paris =
>>channel=20
>> >>>> used during a mix? that would be huge if it did.
>> >>>>
>> >>>>
>> >>>>
>> >>>
>> >>>
>> >>
>> >>=20
>> >=20
>> >
>>
>><!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
>><HTML><HEAD>
>><META http-equiv=3DContent-Type content=3D"text/html; =
>>charset=3Diso-8859-1">
>><META content=3D"MSHTML 6.00.6000.16608" name=3DGENERATOR>
>><STYLE></STYLE>
>></HEAD>
>><BODY bgColor=3D#ffffff>
>><DIV><FONT face=3DArial size=3D2>That's about it man, and why Paris =
>>lives on at my=20
>>place. I can't get away from knowing it sonically so well, the magic =
>>glue the=20
>>bus provides, along with the punch I/O love. To be honest though, the =
>>UAD=20
>>latency pissed me off so much I just yanked the card and static bagged =
>>it. It's=20
>>probably bound for my non DSP native rig soon as I get the time. =
>></FONT></DIV>
>><DIV><FONT face=3DArial size=3D2></FONT> </DIV>
>><DIV><FONT face=3DArial size=3D2>BTW, don't forget that the Paris EQ is
> =
>>available as=20
>>a VST. </FONT></DIV>
>><DIV><FONT face=3DArial size=3D2></FONT> </DIV>
>><DIV> </DIV>
>><BLOCKQUOTE=20
>>style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; =
>>BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
>> <DIV>"Deej" <<A =
>>href=3D"mailto:noway@jose.net">noway@jose.net</A>> wrote=20
>> in message <A =
>>href=3D"news:47b5321a@linux">news:47b5321a@linux</A>...</DIV>
>> <DIV><FONT face=3DArial size=3D2>Well, I've been thinking about some =
>>aspects of=20
>> Paris that I really liked. However, there's still the situation with =
>>bussing=20
>> across submixes, but it's not something I couldn't =
>>overcome.</FONT></DIV>
>> <DIV><FONT face=3DArial size=3D2></FONT> </DIV>
>> <DIV><FONT face=3DArial size=3D2>I really miss the Paris EQ and FX =
>>actually. They=20
>> are much better, IMO, than any VST plugins I've heard that aren't DSP=20
>> driven.</FONT></DIV>
>> <DIV><FONT face=3DArial size=3D2></FONT> </DIV>
>> <DIV><FONT face=3DArial size=3D2>the more I delve into Cubase, the =
>>more things=20
>> about it that I like, but also, the more sonic weaknesses I see =
>>vis-a-vis=20
>> Paris. It's <EM>possible</EM> to do the "big" thing in Cubase, it's=20
>> <EM>easy</EM> to do it in Paris. I miss the <EM>easy</EM> part. =
>></FONT></DIV>
>> <DIV><FONT face=3DArial size=3D2></FONT> </DIV>
>> <DIV><FONT face=3DArial size=3D2>I think I'd be a bit more satisfied =
>>with Cubase=20
>> if I was using a DM2000 with digital I/O options that would=20
>> accommodate my outboard gear. Anybody got a spare $20k laying=20
>> around?</FONT></DIV>
>> <DIV><FONT face=3DArial size=3D2></FONT> </DIV>
>> <DIV><FONT face=3DArial size=3D2></FONT> </DIV>
>> <DIV><FONT face=3DArial size=3D2></FONT> </DIV>
>> <DIV><FONT face=3DArial size=3D2></FONT> </DIV>
>> <DIV><FONT face=3DArial size=3D2>"Aaron Allen" <</FONT><A=20
>> href=3D"mailto:know-spam@not_here.dude"><FONT face=3DArial=20
>> size=3D2>know-spam@not_here.dude</FONT></A><FONT face=3DArial =
>>size=3D2>> wrote in=20
>> message </FONT><A href=3D"news:47b5217d@linux"><FONT face=3DArial=20
>> size=3D2>news:47b5217d@linux</FONT></A><FONT face=3DArial=20
>> size=3D2>...</FONT></DIV><FONT face=3DArial size=3D2>>I thought you =
>>were trying=20
>> to simplify :)<BR>> <BR>> AA<BR>> <BR>> <BR>> "Deej"=20
>> <</FONT><A href=3D"mailto:noway@jose.net"><FONT face=3DArial=20
>> size=3D2>noway@jose.net</FONT></A><FONT face=3DArial size=3D2>> =
>>wrote in message=20
>> </FONT><A href=3D"news:47b51030$1@linux"><FONT face=3DArial=20
>> size=3D2>news:47b51030$1@linux</FONT></A><FONT face=3DArial =
>>size=3D2>...<BR>>>=20
>> So basically, if you put this on each channel any plugin you add to =
>>that=20
>> <BR>>> channel will report it's latency and then all channels =
>>can be=20
>> adjusted to <BR>>> compensate for this amount of latency? If =
>>this is=20
>> cumulative, that is <BR>>> basically the same as having PDC. The =
>>only=20
>> difference is a mouse click <BR>>> each time you add a plugin so =
>>that=20
>> the remaining channels adjust to the <BR>>> additional=20
>> latency.<BR>>><BR>>> Does this work with the high =
>>cumulative=20
>> latency numbers that are incurred <BR>>> when UAD-1 plugins are =
>>stacked=20
>> on tracks?<BR>>><BR>>> I guess, what I'm getting at here =
>>is if I=20
>> were to put together another <BR>>> Paris DAW, say 4 x Cards =
>>(which I=20
>> know I can channel to a single IRQ on a <BR>>> 13 slot =
>>Magma) and=20
>> then have my other Magma in use running the two POCO's <BR>>> =
>>and 4 x=20
>> UAD-1 cards, I could have a Paris DAW that that would integrate =
>><BR>>>=20
>> UAD-1 and POCO plugins and I wouldn't have to jack around with =
>>nudge/slide=20
>> <BR>>> or Sampleslide?.....I could just click a mouse every time =
>>I added=20
>> another <BR>>> plug and everything would be=20
>> compensated?<BR>>><BR>>><BR>>> "Don Nafe" =
>><</FONT><A=20
>> href=3D"mailto:dnafe@magma.ca"><FONT face=3DArial=20
>> size=3D2>dnafe@magma.ca</FONT></A><FONT face=3DArial size=3D2>> =
>>wrote in message=20
>> </FONT><A href=3D"news:47b4cb97@linux"><FONT face=3DArial=20
>> size=3D2>news:47b4cb97@linux</FONT></A><FONT face=3DArial=20
>> size=3D2>...<BR>>>> I'm still not sure whether it =
>>automatically detects=20
>> a plugin's latency <BR>>>> (where=20
>> applicable)<BR>>>><BR>>>> but yes, put it on each =
>>channel,=20
>> throw in aplugin and input it's latency <BR>>>> and Bob's =
>>your=20
>> Uncle...latencey adjustment across all=20
>> channels.<BR>>>><BR>>>> Nice thing is if you add a =
>>different=20
>> plugin to a different channel you <BR>>>> just have to input =
>>that=20
>> letency on that channelss faderwork plug and all <BR>>>> =
>>channels get=20
>> adjusted accordingly (and so on and so=20
>> on....<BR>>>><BR>>>><BR>>>> "Deej" =
>><</FONT><A=20
>> href=3D"mailto:noway@jose.net"><FONT face=3DArial=20
>> size=3D2>noway@jose.net</FONT></A><FONT face=3DArial size=3D2>> =
>>wrote in message=20
>> </FONT><A href=3D"news:47b4b204@linux"><FONT face=3DArial=20
>> size=3D2>news:47b4b204@linux</FONT></A><FONT face=3DArial=20
>> size=3D2>...<BR>>>>> </FONT><A=20
>> =
>>href=3D" http://www.vertexdsp.com/products/ReleaseNotes_FaderWorks.rt f"><F=
>>ONT=20
>> face=3DArial=20
>> =
>>size=3D2> http://www.vertexdsp.com/products/ReleaseNotes_FaderWorks.rt f</F=
>>ONT></A><BR><FONT=20
>> face=3DArial size=3D2>>>>><BR>>>>> Before I =
>>sold my Paris=20
>> system, I bought this plugin. I have never even <BR>>>>> =
>>used it.=20
>> Does it now provide PDC if instantiated on every Paris channel=20
>> <BR>>>>> used during a mix? that would be huge if it=20
>> =
>>did.<BR>>>>><BR>>>>><BR>>>>><BR>>&=
>>gt;><BR>>>><BR>>><BR>>>=20
>> <BR>> <BR>></FONT> </BLOCKQUOTE></BODY></HTML>
>>
>>
>
|
|
|
|
Goto Forum:
Current Time: Mon May 20 04:30:08 PDT 2024
Total time taken to generate the page: 0.04087 seconds
|
The PARIS Forums
Search
Help
Members
Register
Login
Home
