Home » The PARIS Forums » PARIS: Main » Author of Vertex VST will update with Latency compensator for Paris !!
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Re: Author of Vertex VST will update with Latency compensator for Paris !! [message #78726 is a reply to message #78724] |
Sat, 20 January 2007 23:21   |
![neil[1] is currently offline](/theme/PARIS_Forum_Template/images/offline.png "neil[1] is currently offline")
neil[1]
Messages: 164
Registered: October 2006
|
Senior Member |
|
|
It never ceases to amaze me how many people are willing to
develop for Paris, except for those that created Paris.
Yes, Edmund, I'm talking to you.
Neil
"Tom Bruhl" <arpegio@comcast.net> wrote:
>
>
>Dimitrios,
>You only have to type the latency once to compensate let's say 50 =
>tracks?
>I'll buy that plugin.=20
>Tom
>
> "Ted Gerber" <tedgerber@rogers.com> wrote in message =
>news:45b2e30e$1@linux...
>
> Very cool Dimitrios! You continue to energize us. I'm in.
>
> Ted
>
>
>
> "Dimitrios" <musurgio@otenet.gr> wrote:
> >
> >Yes.
> >I contacted the Vertex dsp vst plugin author who is a very nice guy =
>by the
> >way...
> >He will update vertex dsp fader vst plugin with a LIGHT manual delay
=
>compensator
> >suited for us Parisians !!
> >The concept is the following:
> >We put dsp fader vst one very paris audio track.
> >Benefits.
> >We can solo mute certain Paris audio track groups.
> >Now you can solo your drumtracks only or maybe mute all your acoustic
=
>guitars
> >!!
> >BEYOND these already implemented things this nice plugin has to offer
=
>tha
> >author will implement the following:
> >Note that you have opened vertex on all paris audio tracks.
> >Now lets say you put waves rencomp to audiotrack 1 that introduces a
=
>delay
> >of 64 samples.
> >What you do is type the number 64 on this track's vertex dsp vst =
>instance
> >the number 64 and ALL OTHER vertex instances GET DELAYED by 64 =
>samples !!
> >Isn't that a nice thought ?
> >Same with eds insertion of a plugin like eds compressor with a =
>lookahead,
> >just type the corresponding samples in delay and all other tracks get
=
>delayed
> >automatically !!
> >I hope that we will support this guy with this plugin if we want =
>ci\ontinuing
> >support...
> >What do you think >?>
> >Regards,
> >Dimitrios
>
>
>
>I choose Polesoft Lockspam to fight spam, and you?
>http://www.polesoft.com/refer.html
>
><!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.2800.1400" name=3DGENERATOR>
><STYLE></STYLE>
></HEAD>
><BODY bgColor=3D#ffffff>
><DIV><FONT face=3DArial size=3D2>Dimitrios,</FONT></DIV>
><DIV><FONT face=3DArial size=3D2>You only have to type the =
>latency once to=20
>compensate let's say 50 tracks?</FONT></DIV>
><DIV><FONT face=3DArial size=3D2>I'll buy that =
>plugin. </FONT></DIV>
><DIV><FONT face=3DArial size=3D2>Tom</FONT></DIV>
><DIV><FONT face=3DArial size=3D2></FONT> </DIV>
><BLOCKQUOTE=20
>style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; =
>BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
> <DIV>"Ted Gerber" <<A=20
> href=3D"mailto:tedgerber@rogers.com">tedgerber@rogers.com</A>> =
>wrote in=20
> message <A=20
> =
>href=3D"news:45b2e30e$1@linux">news:45b2e30e$1@linux</A>...</DIV><BR>Very=
> cool=20
> Dimitrios! You continue to energize us. I'm=20
> in.<BR><BR>Ted<BR><BR><BR><BR>"Dimitrios" <<A=20
> href=3D"mailto:musurgio@otenet.gr">musurgio@otenet.gr</A>>=20
> wrote:<BR>><BR>>Yes.<BR>>I contacted the Vertex dsp vst =
>plugin author=20
> who is a very nice guy by the<BR>>way...<BR>>He will update =
>vertex dsp=20
> fader vst plugin with a LIGHT manual delay compensator<BR>>suited =
>for us=20
> Parisians !!<BR>>The concept is the following:<BR>>We put dsp =
>fader vst=20
> one very paris audio track.<BR>>Benefits.<BR>>We can solo mute =
>certain=20
> Paris audio track groups.<BR>>Now you can solo your drumtracks only =
>or=20
> maybe mute all your acoustic guitars<BR>>!!<BR>>BEYOND these =
>already=20
> implemented things this nice plugin has to offer tha<BR>>author =
>will=20
> implement the following:<BR>>Note that you have opened vertex on =
>all paris=20
> audio tracks.<BR>>Now lets say you put waves rencomp to =
>audiotrack 1=20
> that introduces a delay<BR>>of 64 samples.<BR>>What you do is =
>type the=20
> number 64 on this track's vertex dsp vst instance<BR>>the number 64 =
>and ALL=20
> OTHER vertex instances GET DELAYED by 64 samples !!<BR>>Isn't that =
>a nice=20
> thought ?<BR>>Same with eds insertion of a plugin like eds =
>compressor with=20
> a lookahead,<BR>>just type the corresponding samples in delay and =
>all other=20
> tracks get delayed<BR>>automatically !!<BR>>I hope that we will =
>support=20
> this guy with this plugin if we want=20
> ci\ontinuing<BR>>support...<BR>>What do you think=20
> >?><BR>>Regards,<BR>>Dimitrios<BR></BLOCKQUOTE>
><DIV><FONT size=3D2><BR><BR>I choose Polesoft Lockspam to fight spam, =
>and=20
>you?<BR><A=20
>href=3D"http://www.polesoft.com/refer.html">http://www.polesoft.com/refer=
>.html</A> </FONT></DIV></BODY></HTML>
>
>
|
|
|
|
|
|
|
|
|
|
|
|
| Re: Author of Vertex VST will update with Latency compensator for Paris !! [message #78779 is a reply to message #78773] |
Sun, 21 January 2007 23:54 |
Tom Bruhl
Messages: 1368
Registered: June 2007
|
Senior Member |
|
|
This is a multi-part message in MIME format.
------=_NextPart_000_01C7_01C73DD0.9ACFCCB0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Dimitrios,
I'm still liking it as much as anything else I've heard.
The grouping feature is just another plus although
it must be a pain to use - opening plugins etc..
Have you checked out Brian's technique of soloing within
a Paris editor? I never figured it out but he makes it
look simple like everything else..
Tom
"Dimitrios" <musurgio@otenet.gr> wrote in message =
news:45b468da$1@linux...
Hi,
Automatic figuring out of actual latency is a "impossible" task.
Although a plug-in reports its latency to the host, a plug-in cannot =
request
this value from another plug-in !
Thats why we are somehow doomed for automatic latency detection.
But this hand typing of latency for a single plugin is a great feature =
!!
Regards,
Dimitrios
"Brandon" <a@a.com> wrote:
>
>Would be cool.
>I like what Chuck is working on as well.
>If it could automatically figure it out the latency would be awesome.
>If you can just type in a latency you knew was greater than the =
largest
it
>would be cool instead of trying to figure out what the actual latency =
is.
>B=20
>
>
>Chas. Duncan <duncan5199ATsbcglobalDOTnet@> wrote:
>>
>>Now this is a cool idea.
>>
>>-- thanks -- chas.
>>
>>On 21 Jan 2007 07:53:33 +1000, "Dimitrios" <musurgio@otenet.gr> =
wrote:
>>
>>>
>>>Yes.
>>>I contacted the Vertex dsp vst plugin author who is a very nice guy =
by
>the
>>>way...
>>>He will update vertex dsp fader vst plugin with a LIGHT manual =
delay compensator
>>>suited for us Parisians !!
>>>The concept is the following:
>>>We put dsp fader vst one very paris audio track.
>>>Benefits.
>>>We can solo mute certain Paris audio track groups.
>>>Now you can solo your drumtracks only or maybe mute all your =
acoustic
guitars
>>>!!
>>>BEYOND these already implemented things this nice plugin has to =
offer
tha
>>>author will implement the following:
>>>Note that you have opened vertex on all paris audio tracks.
>>>Now lets say you put waves rencomp to audiotrack 1 that introduces =
a
delay
>>>of 64 samples.
>>>What you do is type the number 64 on this track's vertex dsp vst =
instance
>>>the number 64 and ALL OTHER vertex instances GET DELAYED by 64 =
samples
>!!
>>>Isn't that a nice thought ?
>>>Same with eds insertion of a plugin like eds compressor with a =
lookahead,
>>>just type the corresponding samples in delay and all other tracks =
get
delayed
>>>automatically !!
>>>I hope that we will support this guy with this plugin if we want =
ci\ontinuing
>>>support...
>>>What do you think >?>
>>>Regards,
>>>Dimitrios
>>
>
I choose Polesoft Lockspam to fight spam, and you?
http://www.polesoft.com/refer.html
------=_NextPart_000_01C7_01C73DD0.9ACFCCB0
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.2800.1400" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>Dimitrios,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>I'm still liking it as much as anything =
else I've=20
heard.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>The grouping feature is just another =
plus=20
although</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>it must be a pain to use - opening =
plugins=20
etc..</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Have you checked out Brian's technique =
of soloing=20
within</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>a Paris editor? I never figured =
it out but he=20
makes it</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>look simple like everything =
else..</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Tom</FONT></DIV>
<BLOCKQUOTE=20
style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; =
BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
<DIV>"Dimitrios" <<A=20
href=3D"mailto:musurgio@otenet.gr">musurgio@otenet.gr</A>> wrote in =
message=20
<A=20
=
href=3D"news:45b468da$1@linux">news:45b468da$1@linux</A>...</DIV><BR>Hi,<=
BR>Automatic=20
figuring out of actual latency is a "impossible" task.<BR>Although a =
plug-in=20
reports its latency to the host, a plug-in cannot request<BR>this =
value from=20
another plug-in !<BR>Thats why we are somehow doomed for automatic =
latency=20
detection.<BR>But this hand typing of latency for a single plugin is a =
great=20
feature !!<BR>Regards,<BR>Dimitrios<BR><BR>"Brandon" <<A=20
href=3D"mailto:a@a.com">a@a.com</A>> wrote:<BR>><BR>>Would be =
cool.<BR>>I like what Chuck is working on as well.<BR>>If it =
could=20
automatically figure it out the latency would be awesome.<BR>>If =
you can=20
just type in a latency you knew was greater than the=20
largest<BR>it<BR>>would be cool instead of trying to figure out =
what the=20
actual latency is.<BR>>B <BR>><BR>><BR>>Chas. Duncan=20
<duncan5199ATsbcglobalDOTnet@> wrote:<BR>>><BR>>>Now =
this is=20
a cool idea.<BR>>><BR>>>-- thanks --=20
chas.<BR>>><BR>>>On 21 Jan 2007 07:53:33 +1000, =
"Dimitrios" <<A=20
href=3D"mailto:musurgio@otenet.gr">musurgio@otenet.gr</A>>=20
=
wrote:<BR>>><BR>>>><BR >>>>Yes.<BR>>>>I=20
contacted the Vertex dsp vst plugin author who is a very nice guy=20
by<BR>>the<BR>>>>way...<BR>>>>He will update =
vertex dsp=20
fader vst plugin with a LIGHT manual delay =
compensator<BR>>>>suited=20
for us Parisians !!<BR>>>>The concept is the=20
following:<BR>>>>We put dsp fader vst one very paris audio=20
track.<BR>>>>Benefits.<BR>>>>We can solo mute =
certain Paris=20
audio track groups.<BR>>>>Now you can solo your drumtracks =
only or=20
maybe mute all your=20
acoustic<BR>guitars<BR>>>>!!<BR>>>>BEYOND these =
already=20
implemented things this nice plugin has to =
offer<BR>tha<BR>>>>author=20
will implement the following:<BR>>>>Note that you have opened =
vertex=20
on all paris audio tracks.<BR>>>>Now lets say you put waves =
rencomp=20
to audiotrack 1 that introduces a<BR>delay<BR>>>>of 64=20
samples.<BR>>>>What you do is type the number 64 on this =
track's=20
vertex dsp vst instance<BR>>>>the number 64 and ALL OTHER =
vertex=20
instances GET DELAYED by 64 samples<BR>>!!<BR>>>>Isn't =
that a nice=20
thought ?<BR>>>>Same with eds insertion of a plugin like eds=20
compressor with a lookahead,<BR>>>>just type the =
corresponding=20
samples in delay and all other tracks=20
get<BR>delayed<BR>>>>automatically !!<BR>>>>I hope =
that we=20
will support this guy with this plugin if we want=20
ci\ontinuing<BR>>>>support...<BR>>>>What do you =
think=20
=
>?><BR>>>>Regards,<BR>>>>Dimitrios <BR>>><BR=
>><BR></BLOCKQUOTE>
<DIV><FONT size=3D2><BR><BR>I choose Polesoft Lockspam to fight spam, =
and=20
you?<BR><A=20
href=3D"http://www.polesoft.com/refer.html">http://www.polesoft.com/refer=
..html</A> </FONT></DIV></BODY ></HTML>
------=_NextPart_000_01C7_01C73DD0.9ACFCCB0--
|
|
|
|
| Re: Author of Vertex VST will update with Latency compensator for Paris !! [message #78781 is a reply to message #78779] |
Mon, 22 January 2007 01:05 |
Dimitrios
Messages: 1056
Registered: August 2005
|
Senior Member |
|
|
Dear Tom,
No it is not that difficult as you think the soloing thing.
See how it works.
You have ONCE configure what tracks are to be grouped to whatever group 1,2,3,4...up
to 32 !!
When you configure like drums group 1 guitars group 2 , keys group 3 , vocals
group 4 ,etc... then you just have to open on only instance of the corrsponding
group set i.e open kick to solo all drums group , open solo guitar to solo
all guitar group etc...
This solo in editor thing I guess is only for one submix right ?
This vertex though looks great too !!
So flexible can do more than solo and mute can do bypass and can fade volumes
beetween groups with volume offsets !!
Needs some experiment and manual reading I guess.
Regards,
Dimitrios
"Tom Bruhl" <arpegio@comcast.net> wrote:
>
>
>Dimitrios,
>I'm still liking it as much as anything else I've heard.
>The grouping feature is just another plus although
>it must be a pain to use - opening plugins etc..
>
>Have you checked out Brian's technique of soloing within
>a Paris editor? I never figured it out but he makes it
>look simple like everything else..
>Tom
> "Dimitrios" <musurgio@otenet.gr> wrote in message =
>news:45b468da$1@linux...
>
> Hi,
> Automatic figuring out of actual latency is a "impossible" task.
> Although a plug-in reports its latency to the host, a plug-in cannot =
>request
> this value from another plug-in !
> Thats why we are somehow doomed for automatic latency detection.
> But this hand typing of latency for a single plugin is a great feature
=
>!!
> Regards,
> Dimitrios
>
> "Brandon" <a@a.com> wrote:
> >
> >Would be cool.
> >I like what Chuck is working on as well.
> >If it could automatically figure it out the latency would be awesome.
> >If you can just type in a latency you knew was greater than the =
>largest
> it
> >would be cool instead of trying to figure out what the actual latency
=
>is.
> >B=20
> >
> >
> >Chas. Duncan <duncan5199ATsbcglobalDOTnet@> wrote:
> >>
> >>Now this is a cool idea.
> >>
> >>-- thanks -- chas.
> >>
> >>On 21 Jan 2007 07:53:33 +1000, "Dimitrios" <musurgio@otenet.gr> =
>wrote:
> >>
> >>>
> >>>Yes.
> >>>I contacted the Vertex dsp vst plugin author who is a very nice guy
=
>by
> >the
> >>>way...
> >>>He will update vertex dsp fader vst plugin with a LIGHT manual =
>delay compensator
> >>>suited for us Parisians !!
> >>>The concept is the following:
> >>>We put dsp fader vst one very paris audio track.
> >>>Benefits.
> >>>We can solo mute certain Paris audio track groups.
> >>>Now you can solo your drumtracks only or maybe mute all your =
>acoustic
> guitars
> >>>!!
> >>>BEYOND these already implemented things this nice plugin has to =
>offer
> tha
> >>>author will implement the following:
> >>>Note that you have opened vertex on all paris audio tracks.
> >>>Now lets say you put waves rencomp to audiotrack 1 that introduces
=
>a
> delay
> >>>of 64 samples.
> >>>What you do is type the number 64 on this track's vertex dsp vst =
>instance
> >>>the number 64 and ALL OTHER vertex instances GET DELAYED by 64 =
>samples
> >!!
> >>>Isn't that a nice thought ?
> >>>Same with eds insertion of a plugin like eds compressor with a =
>lookahead,
> >>>just type the corresponding samples in delay and all other tracks =
>get
> delayed
> >>>automatically !!
> >>>I hope that we will support this guy with this plugin if we want =
>ci\ontinuing
> >>>support...
> >>>What do you think >?>
> >>>Regards,
> >>>Dimitrios
> >>
> >
>
>
>
>I choose Polesoft Lockspam to fight spam, and you?
>http://www.polesoft.com/refer.html
>
><!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.2800.1400" name=3DGENERATOR>
><STYLE></STYLE>
></HEAD>
><BODY bgColor=3D#ffffff>
><DIV><FONT face=3DArial size=3D2>Dimitrios,</FONT></DIV>
><DIV><FONT face=3DArial size=3D2>I'm still liking it as much as anything
=
>else I've=20
>heard.</FONT></DIV>
><DIV><FONT face=3DArial size=3D2>The grouping feature is just another =
>plus=20
>although</FONT></DIV>
><DIV><FONT face=3DArial size=3D2>it must be a pain to use - opening =
>plugins=20
>etc..</FONT></DIV>
><DIV><FONT face=3DArial size=3D2></FONT> </DIV>
><DIV><FONT face=3DArial size=3D2>Have you checked out Brian's technique
=
>of soloing=20
>within</FONT></DIV>
><DIV><FONT face=3DArial size=3D2>a Paris editor? I never figured =
>it out but he=20
>makes it</FONT></DIV>
><DIV><FONT face=3DArial size=3D2>look simple like everything =
>else..</FONT></DIV>
><DIV><FONT face=3DArial size=3D2>Tom</FONT></DIV>
><BLOCKQUOTE=20
>style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; =
>BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
> <DIV>"Dimitrios" <<A=20
> href=3D"mailto:musurgio@otenet.gr">musurgio@otenet.gr</A>> wrote in =
>message=20
> <A=20
> =
>href=3D"news:45b468da$1@linux">news:45b468da$1@linux</A>...</DIV><BR>Hi,<=
>BR>Automatic=20
> figuring out of actual latency is a "impossible" task.<BR>Although a =
>plug-in=20
> reports its latency to the host, a plug-in cannot request<BR>this =
>value from=20
> another plug-in !<BR>Thats why we are somehow doomed for automatic =
>latency=20
> detection.<BR>But this hand typing of latency for a single plugin is a
=
>great=20
> feature !!<BR>Regards,<BR>Dimitrios<BR><BR>"Brandon" <<A=20
> href=3D"mailto:a@a.com">a@a.com</A>> wrote:<BR>><BR>>Would be =
>
> cool.<BR>>I like what Chuck is working on as well.<BR>>If it =
>could=20
> automatically figure it out the latency would be awesome.<BR>>If =
>you can=20
> just type in a latency you knew was greater than the=20
> largest<BR>it<BR>>would be cool instead of trying to figure out =
>what the=20
> actual latency is.<BR>>B <BR>><BR>><BR>>Chas. Duncan=20
> <duncan5199ATsbcglobalDOTnet@> wrote:<BR>>><BR>>>Now =
>this is=20
> a cool idea.<BR>>><BR>>>-- thanks --=20
> chas.<BR>>><BR>>>On 21 Jan 2007 07:53:33 +1000, =
>"Dimitrios" <<A=20
> href=3D"mailto:musurgio@otenet.gr">musurgio@otenet.gr</A>>=20
> =
>wrote:<BR>>><BR>>>><BR>>>>Yes.<BR>>>>I=20
> contacted the Vertex dsp vst plugin author who is a very nice guy=20
> by<BR>>the<BR>>>>way...<BR>>>>He will update =
>vertex dsp=20
> fader vst plugin with a LIGHT manual delay =
>compensator<BR>>>>suited=20
> for us Parisians !!<BR>>>>The concept is the=20
> following:<BR>>>>We put dsp fader vst one very paris audio=20
> track.<BR>>>>Benefits.<BR>>>>We can solo mute =
>certain Paris=20
> audio track groups.<BR>>>>Now you can solo your drumtracks =
>only or=20
> maybe mute all your=20
> acoustic<BR>guitars<BR>>>>!!<BR>>>>BEYOND these =
>already=20
> implemented things this nice plugin has to =
>offer<BR>tha<BR>>>>author=20
> will implement the following:<BR>>>>Note that you have opened =
>vertex=20
> on all paris audio tracks.<BR>>>>Now lets say you put waves =
>rencomp=20
> to audiotrack 1 that introduces a<BR>delay<BR>>>>of 64=20
> samples.<BR>>>>What you do is type the number 64 on this =
>track's=20
> vertex dsp vst instance<BR>>>>the number 64 and ALL OTHER =
>vertex=20
> instances GET DELAYED by 64 samples<BR>>!!<BR>>>>Isn't =
>that a nice=20
> thought ?<BR>>>>Same with eds insertion of a plugin like eds=20
> compressor with a lookahead,<BR>>>>just type the =
>corresponding=20
> samples in delay and all other tracks=20
> get<BR>delayed<BR>>>>automatically !!<BR>>>>I hope =
>that we=20
> will support this guy with this plugin if we want=20
> ci\ontinuing<BR>>>>support...<BR>>>>What do you =
>think=20
> =
>>?><BR>>>>Regards,<BR>>>>Dimitrios<BR>>><BR=
>>><BR></BLOCKQUOTE>
><DIV><FONT size=3D2><BR><BR>I choose Polesoft Lockspam to fight spam, =
>and=20
>you?<BR><A=20
>href=3D"http://www.polesoft.com/refer.html">http://www.polesoft.com/refer=
>.html</A> </FONT></DIV></BODY></HTML>
>
>
|
|
|
|
| Re: Author of Vertex VST will update with Latency compensator for Paris !! [message #78794 is a reply to message #78779] |
Mon, 22 January 2007 06:46 |
Aaron Allen
Messages: 1988
Registered: May 2008
|
Senior Member |
|
|
This is a multi-part message in MIME format.
------=_NextPart_000_0073_01C73E01.CD10FB00
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Tom, it is simple. Select in the editor what tracks you want to solo. =
You can use control+k to cut at the time line if you have a specific =
section you want. With those highlighted, go to the Control 16 and there =
is a specific button for play selected it. That's it. Just undo your =
cuts once you're done here with a control+z.=20
AA
"Tom Bruhl" <arpegio@comcast.net> wrote in message =
news:45b46e27@linux...
Dimitrios,
I'm still liking it as much as anything else I've heard.
The grouping feature is just another plus although
it must be a pain to use - opening plugins etc..
Have you checked out Brian's technique of soloing within
a Paris editor? I never figured it out but he makes it
look simple like everything else..
Tom
"Dimitrios" <musurgio@otenet.gr> wrote in message =
news:45b468da$1@linux...
Hi,
Automatic figuring out of actual latency is a "impossible" task.
Although a plug-in reports its latency to the host, a plug-in cannot =
request
this value from another plug-in !
Thats why we are somehow doomed for automatic latency detection.
But this hand typing of latency for a single plugin is a great =
feature !!
Regards,
Dimitrios
"Brandon" <a@a.com> wrote:
>
>Would be cool.
>I like what Chuck is working on as well.
>If it could automatically figure it out the latency would be =
awesome.
>If you can just type in a latency you knew was greater than the =
largest
it
>would be cool instead of trying to figure out what the actual =
latency is.
>B=20
>
>
>Chas. Duncan <duncan5199ATsbcglobalDOTnet@> wrote:
>>
>>Now this is a cool idea.
>>
>>-- thanks -- chas.
>>
>>On 21 Jan 2007 07:53:33 +1000, "Dimitrios" <musurgio@otenet.gr> =
wrote:
>>
>>>
>>>Yes.
>>>I contacted the Vertex dsp vst plugin author who is a very nice =
guy by
>the
>>>way...
>>>He will update vertex dsp fader vst plugin with a LIGHT manual =
delay compensator
>>>suited for us Parisians !!
>>>The concept is the following:
>>>We put dsp fader vst one very paris audio track.
>>>Benefits.
>>>We can solo mute certain Paris audio track groups.
>>>Now you can solo your drumtracks only or maybe mute all your =
acoustic
guitars
>>>!!
>>>BEYOND these already implemented things this nice plugin has to =
offer
tha
>>>author will implement the following:
>>>Note that you have opened vertex on all paris audio tracks.
>>>Now lets say you put waves rencomp to audiotrack 1 that =
introduces a
delay
>>>of 64 samples.
>>>What you do is type the number 64 on this track's vertex dsp vst =
instance
>>>the number 64 and ALL OTHER vertex instances GET DELAYED by 64 =
samples
>!!
>>>Isn't that a nice thought ?
>>>Same with eds insertion of a plugin like eds compressor with a =
lookahead,
>>>just type the corresponding samples in delay and all other tracks =
get
delayed
>>>automatically !!
>>>I hope that we will support this guy with this plugin if we want =
ci\ontinuing
>>>support...
>>>What do you think >?>
>>>Regards,
>>>Dimitrios
>>
>
I choose Polesoft Lockspam to fight spam, and you?
http://www.polesoft.com/refer.html
------=_NextPart_000_0073_01C73E01.CD10FB00
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.5730.11" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>Tom, it is simple. Select in the editor =
what tracks=20
you want to solo. You can use control+k to cut at the time line if you =
have a=20
specific section you want. With those highlighted, go to the Control 16 =
and=20
there is a specific button for play selected it. That's it. Just undo =
your cuts=20
once you're done here with a control+z. </FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>AA</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>"Tom Bruhl" <<A=20
href=3D"mailto:arpegio@comcast.net">arpegio@comcast.net</A>> wrote =
in message=20
<A href=3D"news:45b46e27@linux">news:45b46e27@linux</A>...</DIV>
<DIV><FONT face=3DArial size=3D2>Dimitrios,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>I'm still liking it as much as =
anything else I've=20
heard.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>The grouping feature is just another =
plus=20
although</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>it must be a pain to use - opening =
plugins=20
etc..</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Have you checked out Brian's =
technique of soloing=20
within</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>a Paris editor? I never figured =
it out but=20
he makes it</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>look simple like everything =
else..</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Tom</FONT></DIV>
<BLOCKQUOTE=20
style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; =
BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
<DIV>"Dimitrios" <<A=20
href=3D"mailto:musurgio@otenet.gr">musurgio@otenet.gr</A>> wrote =
in message=20
<A=20
=
href=3D"news:45b468da$1@linux">news:45b468da$1@linux</A>...</DIV><BR>Hi,<=
BR>Automatic=20
figuring out of actual latency is a "impossible" task.<BR>Although a =
plug-in=20
reports its latency to the host, a plug-in cannot request<BR>this =
value from=20
another plug-in !<BR>Thats why we are somehow doomed for automatic =
latency=20
detection.<BR>But this hand typing of latency for a single plugin is =
a great=20
feature !!<BR>Regards,<BR>Dimitrios<BR><BR>"Brandon" <<A=20
href=3D"mailto:a@a.com">a@a.com</A>> wrote:<BR>><BR>>Would =
be=20
cool.<BR>>I like what Chuck is working on as well.<BR>>If it =
could=20
automatically figure it out the latency would be awesome.<BR>>If =
you can=20
just type in a latency you knew was greater than the=20
largest<BR>it<BR>>would be cool instead of trying to figure out =
what the=20
actual latency is.<BR>>B <BR>><BR>><BR>>Chas. Duncan=20
<duncan5199ATsbcglobalDOTnet@> =
wrote:<BR>>><BR>>>Now this=20
is a cool idea.<BR>>><BR>>>-- thanks --=20
chas.<BR>>><BR>>>On 21 Jan 2007 07:53:33 +1000, =
"Dimitrios"=20
<<A href=3D"mailto:musurgio@otenet.gr">musurgio@otenet.gr</A>> =
=
wrote:<BR>>><BR>>>><BR >>>>Yes.<BR>>>>I=20
contacted the Vertex dsp vst plugin author who is a very nice guy=20
by<BR>>the<BR>>>>way...<BR>>>>He will update =
vertex dsp=20
fader vst plugin with a LIGHT manual delay =
compensator<BR>>>>suited=20
for us Parisians !!<BR>>>>The concept is the=20
following:<BR>>>>We put dsp fader vst one very paris audio=20
track.<BR>>>>Benefits.<BR>>>>We can solo mute =
certain=20
Paris audio track groups.<BR>>>>Now you can solo your =
drumtracks=20
only or maybe mute all your=20
acoustic<BR>guitars<BR>>>>!!<BR>>>>BEYOND these =
already=20
implemented things this nice plugin has to=20
offer<BR>tha<BR>>>>author will implement the=20
following:<BR>>>>Note that you have opened vertex on all =
paris=20
audio tracks.<BR>>>>Now lets say you put waves rencomp =
to =20
audiotrack 1 that introduces a<BR>delay<BR>>>>of 64=20
samples.<BR>>>>What you do is type the number 64 on this =
track's=20
vertex dsp vst instance<BR>>>>the number 64 and ALL OTHER =
vertex=20
instances GET DELAYED by 64 samples<BR>>!!<BR>>>>Isn't =
that a=20
nice thought ?<BR>>>>Same with eds insertion of a plugin =
like eds=20
compressor with a lookahead,<BR>>>>just type the =
corresponding=20
samples in delay and all other tracks=20
get<BR>delayed<BR>>>>automatically !!<BR>>>>I hope =
that we=20
will support this guy with this plugin if we want=20
ci\ontinuing<BR>>>>support...<BR>>>>What do you =
think=20
=
>?><BR>>>>Regards,<BR>>>>Dimitrios <BR>>><BR=
>><BR></BLOCKQUOTE>
<DIV><FONT size=3D2><BR><BR>I choose Polesoft Lockspam to fight spam, =
and=20
you?<BR><A=20
=
href=3D"http://www.polesoft.com/refer.html">http://www.polesoft.com/refer=
..html</A> </FONT></DIV></BLOCKQUOTE ></BODY></HTML>
------=_NextPart_000_0073_01C73E01.CD10FB00--
|
|
|
|
| Re: Author of Vertex VST will update with Latency compensator for Paris !! [message #78797 is a reply to message #78794] |
Mon, 22 January 2007 07:45 |
Tom Bruhl
Messages: 1368
Registered: June 2007
|
Senior Member |
|
|
This is a multi-part message in MIME format.
------=_NextPart_000_006B_01C73E12.7CE16C30
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Aaron,
I'll get right on it. I never cut them in the past.
That's why they never worked I guess.
Thanks,
Tom
"Aaron Allen" <know-spam@not_here.dude> wrote in message =
news:45b4cec2@linux...
Tom, it is simple. Select in the editor what tracks you want to solo. =
You can use control+k to cut at the time line if you have a specific =
section you want. With those highlighted, go to the Control 16 and there =
is a specific button for play selected it. That's it. Just undo your =
cuts once you're done here with a control+z.=20
AA
"Tom Bruhl" <arpegio@comcast.net> wrote in message =
news:45b46e27@linux...
Dimitrios,
I'm still liking it as much as anything else I've heard.
The grouping feature is just another plus although
it must be a pain to use - opening plugins etc..
Have you checked out Brian's technique of soloing within
a Paris editor? I never figured it out but he makes it
look simple like everything else..
Tom
"Dimitrios" <musurgio@otenet.gr> wrote in message =
news:45b468da$1@linux...
Hi,
Automatic figuring out of actual latency is a "impossible" task.
Although a plug-in reports its latency to the host, a plug-in =
cannot request
this value from another plug-in !
Thats why we are somehow doomed for automatic latency detection.
But this hand typing of latency for a single plugin is a great =
feature !!
Regards,
Dimitrios
"Brandon" <a@a.com> wrote:
>
>Would be cool.
>I like what Chuck is working on as well.
>If it could automatically figure it out the latency would be =
awesome.
>If you can just type in a latency you knew was greater than the =
largest
it
>would be cool instead of trying to figure out what the actual =
latency is.
>B=20
>
>
>Chas. Duncan <duncan5199ATsbcglobalDOTnet@> wrote:
>>
>>Now this is a cool idea.
>>
>>-- thanks -- chas.
>>
>>On 21 Jan 2007 07:53:33 +1000, "Dimitrios" <musurgio@otenet.gr> =
wrote:
>>
>>>
>>>Yes.
>>>I contacted the Vertex dsp vst plugin author who is a very nice =
guy by
>the
>>>way...
>>>He will update vertex dsp fader vst plugin with a LIGHT manual =
delay compensator
>>>suited for us Parisians !!
>>>The concept is the following:
>>>We put dsp fader vst one very paris audio track.
>>>Benefits.
>>>We can solo mute certain Paris audio track groups.
>>>Now you can solo your drumtracks only or maybe mute all your =
acoustic
guitars
>>>!!
>>>BEYOND these already implemented things this nice plugin has to =
offer
tha
>>>author will implement the following:
>>>Note that you have opened vertex on all paris audio tracks.
>>>Now lets say you put waves rencomp to audiotrack 1 that =
introduces a
delay
>>>of 64 samples.
>>>What you do is type the number 64 on this track's vertex dsp =
vst instance
>>>the number 64 and ALL OTHER vertex instances GET DELAYED by 64 =
samples
>!!
>>>Isn't that a nice thought ?
>>>Same with eds insertion of a plugin like eds compressor with a =
lookahead,
>>>just type the corresponding samples in delay and all other =
tracks get
delayed
>>>automatically !!
>>>I hope that we will support this guy with this plugin if we =
want ci\ontinuing
>>>support...
>>>What do you think >?>
>>>Regards,
>>>Dimitrios
>>
>
I choose Polesoft Lockspam to fight spam, and you?
http://www.polesoft.com/refer.html
------=_NextPart_000_006B_01C73E12.7CE16C30
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.2800.1400" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>Aaron,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>I'</FONT><FONT face=3DArial size=3D2>ll =
get right on=20
it. I never cut them in the past.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>That's why they never worked I =
guess.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Thanks,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Tom</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:45b4cec2@linux">news:45b4cec2@linux</A>...</DIV>
<DIV><FONT face=3DArial size=3D2>Tom, it is simple. Select in the =
editor what=20
tracks you want to solo. You can use control+k to cut at the time line =
if you=20
have a specific section you want. With those highlighted, go to the =
Control 16=20
and there is a specific button for play selected it. That's it. Just =
undo your=20
cuts once you're done here with a control+z. </FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>AA</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>"Tom Bruhl" <<A=20
href=3D"mailto:arpegio@comcast.net">arpegio@comcast.net</A>> =
wrote in=20
message <A =
href=3D"news:45b46e27@linux">news:45b46e27@linux</A>...</DIV>
<DIV><FONT face=3DArial size=3D2>Dimitrios,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>I'm still liking it as much as =
anything else=20
I've heard.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>The grouping feature is just =
another plus=20
although</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>it must be a pain to use - opening =
plugins=20
etc..</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Have you checked out Brian's =
technique of=20
soloing within</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>a Paris editor? I never =
figured it out=20
but he makes it</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>look simple like everything =
else..</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Tom</FONT></DIV>
<BLOCKQUOTE=20
style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; =
BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
<DIV>"Dimitrios" <<A=20
href=3D"mailto:musurgio@otenet.gr">musurgio@otenet.gr</A>> =
wrote in=20
message <A=20
=
href=3D"news:45b468da$1@linux">news:45b468da$1@linux</A>...</DIV><BR>Hi,<=
BR>Automatic=20
figuring out of actual latency is a "impossible" task.<BR>Although =
a=20
plug-in reports its latency to the host, a plug-in cannot =
request<BR>this=20
value from another plug-in !<BR>Thats why we are somehow doomed =
for=20
automatic latency detection.<BR>But this hand typing of latency =
for a=20
single plugin is a great feature=20
!!<BR>Regards,<BR>Dimitrios<BR><BR>"Brandon" <<A=20
href=3D"mailto:a@a.com">a@a.com</A>> =
wrote:<BR>><BR>>Would be=20
cool.<BR>>I like what Chuck is working on as well.<BR>>If it =
could=20
automatically figure it out the latency would be =
awesome.<BR>>If you=20
can just type in a latency you knew was greater than the=20
largest<BR>it<BR>>would be cool instead of trying to figure out =
what=20
the actual latency is.<BR>>B <BR>><BR>><BR>>Chas. =
Duncan=20
<duncan5199ATsbcglobalDOTnet@> =
wrote:<BR>>><BR>>>Now=20
this is a cool idea.<BR>>><BR>>>-- thanks --=20
chas.<BR>>><BR>>>On 21 Jan 2007 07:53:33 +1000, =
"Dimitrios"=20
<<A =
href=3D"mailto:musurgio@otenet.gr">musurgio@otenet.gr</A>>=20
=
wrote:<BR>>><BR>>>><BR >>>>Yes.<BR>>>>I=20
contacted the Vertex dsp vst plugin author who is a very nice guy=20
by<BR>>the<BR>>>>way...<BR>>>>He will update =
vertex=20
dsp fader vst plugin with a LIGHT manual delay=20
compensator<BR>>>>suited for us Parisians =
!!<BR>>>>The=20
concept is the following:<BR>>>>We put dsp fader vst one =
very=20
paris audio track.<BR>>>>Benefits.<BR>>>>We can =
solo=20
mute certain Paris audio track groups.<BR>>>>Now you can =
solo=20
your drumtracks only or maybe mute all your=20
acoustic<BR>guitars<BR>>>>!!<BR>>>>BEYOND these =
already=20
implemented things this nice plugin has to=20
offer<BR>tha<BR>>>>author will implement the=20
following:<BR>>>>Note that you have opened vertex on all =
paris=20
audio tracks.<BR>>>>Now lets say you put waves rencomp =
to =20
audiotrack 1 that introduces a<BR>delay<BR>>>>of 64=20
samples.<BR>>>>What you do is type the number 64 on this =
track's=20
vertex dsp vst instance<BR>>>>the number 64 and ALL OTHER =
vertex=20
instances GET DELAYED by 64 samples<BR>>!!<BR>>>>Isn't =
that a=20
nice thought ?<BR>>>>Same with eds insertion of a plugin =
like eds=20
compressor with a lookahead,<BR>>>>just type the =
corresponding=20
samples in delay and all other tracks=20
get<BR>delayed<BR>>>>automatically !!<BR>>>>I =
hope that=20
we will support this guy with this plugin if we want=20
ci\ontinuing<BR>>>>support...<BR>>>>What do you =
think=20
=
>?><BR>>>>Regards,<BR>>>>Dimitrios <BR>>><BR=
>><BR></BLOCKQUOTE>
<DIV><FONT size=3D2><BR><BR>I choose Polesoft Lockspam to fight =
spam, and=20
you?<BR><A=20
=
href=3D"http://www.polesoft.com/refer.html">http://www.polesoft.com/refer=
..html</A> </FONT></DIV></BLOCKQUOTE ></BLOCKQUOTE></BODY>=
</HTML>
------=_NextPart_000_006B_01C73E12.7CE16C30--
|
|
|
|
| Re: Author of Vertex VST will update with Latency compensator for Paris !! [message #78812 is a reply to message #78794] |
Mon, 22 January 2007 11:36 |
Rod Lincoln
Messages: 883
Registered: September 2005
|
Senior Member |
|
|
Yeah, I use it all the time. Also has the benifit of hearing and effects you
have on it in solo AND talent can hear the solo.
This makes for a very flexible solo function. If I'm tracking and I wan't
to solo and have the talent NOT here it that way, I use the normal solo button.
If the talent wants to hear what they've done solo'd up I use the "play selection"
method (al a Brian's technique)
Rod
"Aaron Allen" <know-spam@not_here.dude> wrote:
>
>
>Tom, it is simple. Select in the editor what tracks you want to solo. =
>You can use control+k to cut at the time line if you have a specific =
>section you want. With those highlighted, go to the Control 16 and there
=
>is a specific button for play selected it. That's it. Just undo your =
>cuts once you're done here with a control+z.=20
>
>AA
> "Tom Bruhl" <arpegio@comcast.net> wrote in message =
>news:45b46e27@linux...
> Dimitrios,
> I'm still liking it as much as anything else I've heard.
> The grouping feature is just another plus although
> it must be a pain to use - opening plugins etc..
>
> Have you checked out Brian's technique of soloing within
> a Paris editor? I never figured it out but he makes it
> look simple like everything else..
> Tom
> "Dimitrios" <musurgio@otenet.gr> wrote in message =
>news:45b468da$1@linux...
>
> Hi,
> Automatic figuring out of actual latency is a "impossible" task.
> Although a plug-in reports its latency to the host, a plug-in cannot
=
>request
> this value from another plug-in !
> Thats why we are somehow doomed for automatic latency detection.
> But this hand typing of latency for a single plugin is a great =
>feature !!
> Regards,
> Dimitrios
>
> "Brandon" <a@a.com> wrote:
> >
> >Would be cool.
> >I like what Chuck is working on as well.
> >If it could automatically figure it out the latency would be =
>awesome.
> >If you can just type in a latency you knew was greater than the =
>largest
> it
> >would be cool instead of trying to figure out what the actual =
>latency is.
> >B=20
> >
> >
> >Chas. Duncan <duncan5199ATsbcglobalDOTnet@> wrote:
> >>
> >>Now this is a cool idea.
> >>
> >>-- thanks -- chas.
> >>
> >>On 21 Jan 2007 07:53:33 +1000, "Dimitrios" <musurgio@otenet.gr> =
>wrote:
> >>
> >>>
> >>>Yes.
> >>>I contacted the Vertex dsp vst plugin author who is a very nice =
>guy by
> >the
> >>>way...
> >>>He will update vertex dsp fader vst plugin with a LIGHT manual =
>delay compensator
> >>>suited for us Parisians !!
> >>>The concept is the following:
> >>>We put dsp fader vst one very paris audio track.
> >>>Benefits.
> >>>We can solo mute certain Paris audio track groups.
> >>>Now you can solo your drumtracks only or maybe mute all your =
>acoustic
> guitars
> >>>!!
> >>>BEYOND these already implemented things this nice plugin has to =
>offer
> tha
> >>>author will implement the following:
> >>>Note that you have opened vertex on all paris audio tracks.
> >>>Now lets say you put waves rencomp to audiotrack 1 that =
>introduces a
> delay
> >>>of 64 samples.
> >>>What you do is type the number 64 on this track's vertex dsp vst
=
>instance
> >>>the number 64 and ALL OTHER vertex instances GET DELAYED by 64 =
>samples
> >!!
> >>>Isn't that a nice thought ?
> >>>Same with eds insertion of a plugin like eds compressor with a =
>lookahead,
> >>>just type the corresponding samples in delay and all other tracks
=
>get
> delayed
> >>>automatically !!
> >>>I hope that we will support this guy with this plugin if we want
=
>ci\ontinuing
> >>>support...
> >>>What do you think >?>
> >>>Regards,
> >>>Dimitrios
> >>
> >
>
>
>
> I choose Polesoft Lockspam to fight spam, and you?
> http://www.polesoft.com/refer.html
>
><!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.5730.11" name=3DGENERATOR>
><STYLE></STYLE>
></HEAD>
><BODY bgColor=3D#ffffff>
><DIV><FONT face=3DArial size=3D2>Tom, it is simple. Select in the editor
=
>what tracks=20
>you want to solo. You can use control+k to cut at the time line if you =
>have a=20
>specific section you want. With those highlighted, go to the Control 16
=
>and=20
>there is a specific button for play selected it. That's it. Just undo =
>your cuts=20
>once you're done here with a control+z. </FONT></DIV>
><DIV><FONT face=3DArial size=3D2></FONT> </DIV>
><DIV><FONT face=3DArial size=3D2>AA</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>"Tom Bruhl" <<A=20
> href=3D"mailto:arpegio@comcast.net">arpegio@comcast.net</A>> wrote =
>in message=20
> <A href=3D"news:45b46e27@linux">news:45b46e27@linux</A>...</DIV>
> <DIV><FONT face=3DArial size=3D2>Dimitrios,</FONT></DIV>
> <DIV><FONT face=3DArial size=3D2>I'm still liking it as much as =
>anything else I've=20
> heard.</FONT></DIV>
> <DIV><FONT face=3DArial size=3D2>The grouping feature is just another
=
>plus=20
> although</FONT></DIV>
> <DIV><FONT face=3DArial size=3D2>it must be a pain to use - opening =
>plugins=20
> etc..</FONT></DIV>
> <DIV><FONT face=3DArial size=3D2></FONT> </DIV>
> <DIV><FONT face=3DArial size=3D2>Have you checked out Brian's =
>technique of soloing=20
> within</FONT></DIV>
> <DIV><FONT face=3DArial size=3D2>a Paris editor? I never figured =
>it out but=20
> he makes it</FONT></DIV>
> <DIV><FONT face=3DArial size=3D2>look simple like everything =
>else..</FONT></DIV>
> <DIV><FONT face=3DArial size=3D2>Tom</FONT></DIV>
> <BLOCKQUOTE=20
> style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; =
>BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
> <DIV>"Dimitrios" <<A=20
> href=3D"mailto:musurgio@otenet.gr">musurgio@otenet.gr</A>> wrote =
>in message=20
> <A=20
> =
>href=3D"news:45b468da$1@linux">news:45b468da$1@linux</A>...</DIV><BR>Hi,<=
>BR>Automatic=20
> figuring out of actual latency is a "impossible" task.<BR>Although a
=
>plug-in=20
> reports its latency to the host, a plug-in cannot request<BR>this =
>value from=20
> another plug-in !<BR>Thats why we are somehow doomed for automatic =
>latency=20
> detection.<BR>But this hand typing of latency for a single plugin is
=
>a great=20
> feature !!<BR>Regards,<BR>Dimitrios<BR><BR>"Brandon" <<A=20
> href=3D"mailto:a@a.com">a@a.com</A>> wrote:<BR>><BR>>Would =
>be=20
> cool.<BR>>I like what Chuck is working on as well.<BR>>If it =
>could=20
> automatically figure it out the latency would be awesome.<BR>>If =
>you can=20
> just type in a latency you knew was greater than the=20
> largest<BR>it<BR>>would be cool instead of trying to figure out =
>what the=20
> actual latency is.<BR>>B <BR>><BR>><BR>>Chas. Duncan=20
> <duncan5199ATsbcglobalDOTnet@> =
>wrote:<BR>>><BR>>>Now this=20
> is a cool idea.<BR>>><BR>>>-- thanks --=20
> chas.<BR>>><BR>>>On 21 Jan 2007 07:53:33 +1000, =
>"Dimitrios"=20
> <<A href=3D"mailto:musurgio@otenet.gr">musurgio@otenet.gr</A>> =
>
> =
>wrote:<BR>>><BR>>>><BR>>>>Yes.<BR>>>>I=20
> contacted the Vertex dsp vst plugin author who is a very nice guy=20
> by<BR>>the<BR>>>>way...<BR>>>>He will update =
>vertex dsp=20
> fader vst plugin with a LIGHT manual delay =
>compensator<BR>>>>suited=20
> for us Parisians !!<BR>>>>The concept is the=20
> following:<BR>>>>We put dsp fader vst one very paris audio=20
> track.<BR>>>>Benefits.<BR>>>>We can solo mute =
>certain=20
> Paris audio track groups.<BR>>>>Now you can solo your =
>drumtracks=20
> only or maybe mute all your=20
> acoustic<BR>guitars<BR>>>>!!<BR>>>>BEYOND these =
>already=20
> implemented things this nice plugin has to=20
> offer<BR>tha<BR>>>>author will implement the=20
> following:<BR>>>>Note that you have opened vertex on all =
>paris=20
> audio tracks.<BR>>>>Now lets say you put waves rencomp =
>to =20
> audiotrack 1 that introduces a<BR>delay<BR>>>>of 64=20
> samples.<BR>>>>What you do is type the number 64 on this =
>track's=20
> vertex dsp vst instance<BR>>>>the number 64 and ALL OTHER =
>vertex=20
> instances GET DELAYED by 64 samples<BR>>!!<BR>>>>Isn't =
>that a=20
> nice thought ?<BR>>>>Same with eds insertion of a plugin =
>like eds=20
> compressor with a lookahead,<BR>>>>just type the =
>corresponding=20
> samples in delay and all other tracks=20
> get<BR>delayed<BR>>>>automatically !!<BR>>>>I hope =
>that we=20
> will support this guy with this plugin if we want=20
> ci\ontinuing<BR>>>>support...<BR>>>>What do you =
>think=20
> =
>>?><BR>>>>Regards,<BR>>>>Dimitrios<BR>>><BR=
>>><BR></BLOCKQUOTE>
> <DIV><FONT size=3D2><BR><BR>I choose Polesoft Lockspam to fight spam,
=
>and=20
> you?<BR><A=20
> =
>href=3D"http://www.polesoft.com/refer.html">http://www.polesoft.com/refer=
>.html</A> </FONT></DIV></BLOCKQUOTE></BODY></HTML>
>
>
|
|
|
|
| Re: Author of Vertex VST will update with Latency compensator for Paris !! [message #78830 is a reply to message #78812] |
Mon, 22 January 2007 12:34 |
Tom Bruhl
Messages: 1368
Registered: June 2007
|
Senior Member |
|
|
This is a multi-part message in MIME format.
------=_NextPart_000_0141_01C73E3A.BF902A30
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
R-i-g-h-t! Cool beans.
"Rod Lincoln" <rlincoln@nospam.kc.rr.com> wrote in message =
news:45b5044b$1@linux...
Yeah, I use it all the time. Also has the benifit of hearing and =
effects you
have on it in solo AND talent can hear the solo.
This makes for a very flexible solo function. If I'm tracking and I =
wan't
to solo and have the talent NOT here it that way, I use the normal =
solo button.
If the talent wants to hear what they've done solo'd up I use the =
"play selection"
method (al a Brian's technique)
Rod
"Aaron Allen" <know-spam@not_here.dude> wrote:
>
>
>Tom, it is simple. Select in the editor what tracks you want to solo. =
=3D
>You can use control+k to cut at the time line if you have a specific =
=3D
>section you want. With those highlighted, go to the Control 16 and =
there
=3D
>is a specific button for play selected it. That's it. Just undo your =
=3D
>cuts once you're done here with a control+z.=3D20
>
>AA
> "Tom Bruhl" <arpegio@comcast.net> wrote in message =3D
>news:45b46e27@linux...
> Dimitrios,
> I'm still liking it as much as anything else I've heard.
> The grouping feature is just another plus although
> it must be a pain to use - opening plugins etc..
>
> Have you checked out Brian's technique of soloing within
> a Paris editor? I never figured it out but he makes it
> look simple like everything else..
> Tom
> "Dimitrios" <musurgio@otenet.gr> wrote in message =3D
>news:45b468da$1@linux...
>
> Hi,
> Automatic figuring out of actual latency is a "impossible" task.
> Although a plug-in reports its latency to the host, a plug-in =
cannot
=3D
>request
> this value from another plug-in !
> Thats why we are somehow doomed for automatic latency detection.
> But this hand typing of latency for a single plugin is a great =
=3D
>feature !!
> Regards,
> Dimitrios
>
> "Brandon" <a@a.com> wrote:
> >
> >Would be cool.
> >I like what Chuck is working on as well.
> >If it could automatically figure it out the latency would be =3D
>awesome.
> >If you can just type in a latency you knew was greater than the =
=3D
>largest
> it
> >would be cool instead of trying to figure out what the actual =
=3D
>latency is.
> >B=3D20
> >
> >
> >Chas. Duncan <duncan5199ATsbcglobalDOTnet@> wrote:
> >>
> >>Now this is a cool idea.
> >>
> >>-- thanks -- chas.
> >>
> >>On 21 Jan 2007 07:53:33 +1000, "Dimitrios" <musurgio@otenet.gr> =
=3D
>wrote:
> >>
> >>>
> >>>Yes.
> >>>I contacted the Vertex dsp vst plugin author who is a very =
nice =3D
>guy by
> >the
> >>>way...
> >>>He will update vertex dsp fader vst plugin with a LIGHT manual =
=3D
>delay compensator
> >>>suited for us Parisians !!
> >>>The concept is the following:
> >>>We put dsp fader vst one very paris audio track.
> >>>Benefits.
> >>>We can solo mute certain Paris audio track groups.
> >>>Now you can solo your drumtracks only or maybe mute all your =
=3D
>acoustic
> guitars
> >>>!!
> >>>BEYOND these already implemented things this nice plugin has =
to =3D
>offer
> tha
> >>>author will implement the following:
> >>>Note that you have opened vertex on all paris audio tracks.
> >>>Now lets say you put waves rencomp to audiotrack 1 that =3D
>introduces a
> delay
> >>>of 64 samples.
> >>>What you do is type the number 64 on this track's vertex dsp =
vst
=3D
>instance
> >>>the number 64 and ALL OTHER vertex instances GET DELAYED by 64 =
=3D
>samples
> >!!
> >>>Isn't that a nice thought ?
> >>>Same with eds insertion of a plugin like eds compressor with a =
=3D
>lookahead,
> >>>just type the corresponding samples in delay and all other =
tracks
=3D
>get
> delayed
> >>>automatically !!
> >>>I hope that we will support this guy with this plugin if we =
want
=3D
>ci\ontinuing
> >>>support...
> >>>What do you think >?>
> >>>Regards,
> >>>Dimitrios
> >>
> >
>
>
>
> I choose Polesoft Lockspam to fight spam, and you?
> http://www.polesoft.com/refer.html =20
>
><!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
><HTML><HEAD>
><META http-equiv=3D3DContent-Type content=3D3D"text/html; =3D
>charset=3D3Diso-8859-1">
><META content=3D3D"MSHTML 6.00.5730.11" name=3D3DGENERATOR>
><STYLE></STYLE>
></HEAD>
><BODY bgColor=3D3D#ffffff>
><DIV><FONT face=3D3DArial size=3D3D2>Tom, it is simple. Select in the =
editor
=3D
>what tracks=3D20
>you want to solo. You can use control+k to cut at the time line if =
you =3D
>have a=3D20
>specific section you want. With those highlighted, go to the Control =
16
=3D
>and=3D20
>there is a specific button for play selected it. That's it. Just undo =
=3D
>your cuts=3D20
>once you're done here with a control+z. </FONT></DIV>
><DIV><FONT face=3D3DArial size=3D3D2></FONT> </DIV>
><DIV><FONT face=3D3DArial size=3D3D2>AA</FONT></DIV>
><BLOCKQUOTE dir=3D3Dltr=3D20
>style=3D3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; =
=3D
>BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
> <DIV>"Tom Bruhl" <<A=3D20
> href=3D3D"mailto:arpegio@comcast.net">arpegio@comcast.net</A>> =
wrote =3D
>in message=3D20
> <A href=3D3D"news:45b46e27@linux">news:45b46e27@linux</A>...</DIV>
> <DIV><FONT face=3D3DArial size=3D3D2>Dimitrios,</FONT></DIV>
> <DIV><FONT face=3D3DArial size=3D3D2>I'm still liking it as much as =
=3D
>anything else I've=3D20
> heard.</FONT></DIV>
> <DIV><FONT face=3D3DArial size=3D3D2>The grouping feature is just =
another
=3D
>plus=3D20
> although</FONT></DIV>
> <DIV><FONT face=3D3DArial size=3D3D2>it must be a pain to use - =
opening =3D
>plugins=3D20
> etc..</FONT></DIV>
> <DIV><FONT face=3D3DArial size=3D3D2></FONT> </DIV>
> <DIV><FONT face=3D3DArial size=3D3D2>Have you checked out Brian's =
=3D
>technique of soloing=3D20
> within</FONT></DIV>
> <DIV><FONT face=3D3DArial size=3D3D2>a Paris editor? I never =
figured =3D
>it out but=3D20
> he makes it</FONT></DIV>
> <DIV><FONT face=3D3DArial size=3D3D2>look simple like everything =
=3D
>else..</FONT></DIV>
> <DIV><FONT face=3D3DArial size=3D3D2>Tom</FONT></DIV>
> <BLOCKQUOTE=3D20
> style=3D3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; =
=3D
>BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
> <DIV>"Dimitrios" <<A=3D20
> href=3D3D"mailto:musurgio@otenet.gr">musurgio@otenet.gr</A>> =
wrote =3D
>in message=3D20
> <A=3D20
> =3D
=
>href=3D3D"news:45b468da$1@linux">news:45b468da$1@linux</A>...</DIV><BR>H=
i,<=3D
>BR>Automatic=3D20
> figuring out of actual latency is a "impossible" =
task.<BR>Although a
=3D
>plug-in=3D20
> reports its latency to the host, a plug-in cannot request<BR>this =
=3D
>value from=3D20
> another plug-in !<BR>Thats why we are somehow doomed for =
automatic =3D
>latency=3D20
> detection.<BR>But this hand typing of latency for a single plugin =
is
=3D
>a great=3D20
> feature !!<BR>Regards,<BR>Dimitrios<BR><BR>"Brandon" <<A=3D20
> href=3D3D"mailto:a@a.com">a@a.com</A>> wrote:<BR>><BR>>Would =3D
>be=3D20
> cool.<BR>>I like what Chuck is working on as well.<BR>>If it =3D
>could=3D20
> automatically figure it out the latency would be awesome.<BR>>If =
=3D
>you can=3D20
> just type in a latency you knew was greater than the=3D20
> largest<BR>it<BR>>would be cool instead of trying to figure out =
=3D
>what the=3D20
> actual latency is.<BR>>B <BR>><BR>><BR>>Chas. Duncan=3D20
> <duncan5199ATsbcglobalDOTnet@> =3D
>wrote:<BR>>><BR>>>Now this=3D20
> is a cool idea.<BR>>><BR>>>-- thanks --=3D20
> chas.<BR>>><BR>>>On 21 Jan 2007 07:53:33 +1000, =3D
>"Dimitrios"=3D20
> <<A href=3D3D"mailto:musurgio@otenet.gr">musurgio@otenet.gr</A>> =
=3D
>
> =3D
>wrote:<BR>>><BR>>>><BR>>>>Yes.<BR>>>>I=3D20
> contacted the Vertex dsp vst plugin author who is a very nice =
guy=3D20
> by<BR>>the<BR>>>>way...<BR>>>>He will update =3D
>vertex dsp=3D20
> fader vst plugin with a LIGHT manual delay =3D
>compensator<BR>>>>suited=3D20
> for us Parisians !!<BR>>>>The concept is the=3D20
> following:<BR>>>>We put dsp fader vst one very paris audio=3D20
> track.<BR>>>>Benefits.<BR>>>>We can solo mute =3D
>certain=3D20
> Paris audio track groups.<BR>>>>Now you can solo your =3D
>drumtracks=3D20
> only or maybe mute all your=3D20
> acoustic<BR>guitars<BR>>>>!!<BR>>>>BEYOND these =3D
>already=3D20
> implemented things this nice plugin has to=3D20
> offer<BR>tha<BR>>>>author will implement the=3D20
> following:<BR>>>>Note that you have opened vertex on all =3D
>paris=3D20
> audio tracks.<BR>>>>Now lets say you put waves rencomp =3D
>to =3D20
> audiotrack 1 that introduces a<BR>delay<BR>>>>of 64=3D20
> samples.<BR>>>>What you do is type the number 64 on this =3D
>track's=3D20
> vertex dsp vst instance<BR>>>>the number 64 and ALL OTHER =3D
>vertex=3D20
> instances GET DELAYED by 64 samples<BR>>!!<BR>>>>Isn't =3D
>that a=3D20
> nice thought ?<BR>>>>Same with eds insertion of a plugin =3D
>like eds=3D20
> compressor with a lookahead,<BR>>>>just type the =3D
>corresponding=3D20
> samples in delay and all other tracks=3D20
> get<BR>delayed<BR>>>>automatically !!<BR>>>>I hope =3D
>that we=3D20
> will support this guy with this plugin if we want=3D20
> ci\ontinuing<BR>>>>support...<BR>>>>What do you =3D
>think=3D20
> =3D
>>?><BR>>>>Regards,<BR>>>>Dimitrios<BR>>><BR=3D
>>><BR></BLOCKQUOTE>
> <DIV><FONT size=3D3D2><BR><BR>I choose Polesoft Lockspam to fight =
spam,
=3D
>and=3D20
> you?<BR><A=3D20
> =3D
=
>href=3D3D"http://www.polesoft.com/refer.html">http://www.polesoft.com/re=
fer=3D
>.html</A> </FONT></DIV></BLOCKQUOTE></BODY></HTML>
>
>
------=_NextPart_000_0141_01C73E3A.BF902A30
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.2800.1400" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>R-i-g-h-t! Cool =
beans.</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>"Rod Lincoln" <<A=20
=
href=3D"mailto:rlincoln@nospam.kc.rr.com">rlincoln@nospam.kc.rr.com</A>&g=
t;=20
wrote in message <A=20
=
href=3D"news:45b5044b$1@linux">news:45b5044b$1@linux</A>...</DIV><BR>Yeah=
, I use=20
it all the time. Also has the benifit of hearing and effects =
you<BR>have on it=20
in solo AND talent can hear the solo.<BR>This makes for a very =
flexible solo=20
function. If I'm tracking and I wan't<BR>to solo and have the talent =
NOT here=20
it that way, I use the normal solo button.<BR>If the talent wants to =
hear what=20
they've done solo'd up I use the "play selection"<BR>method (al a =
Brian's=20
technique)<BR>Rod<BR>"Aaron Allen" <<A=20
=
href=3D"mailto:know-spam@not_here.dude">know-spam@not_here.dude</A>>=20
wrote:<BR>><BR>><BR>>Tom, it is simple. Select in the editor =
what=20
tracks you want to solo. =3D<BR>>You can use control+k to cut at =
the time=20
line if you have a specific =3D<BR>>section you want. With those =
highlighted,=20
go to the Control 16 and there<BR>=3D<BR>>is a specific button for =
play=20
selected it. That's it. Just undo your =3D<BR>>cuts once you're =
done here=20
with a control+z.=3D20<BR>><BR>>AA<BR>> "Tom Bruhl" =
<<A=20
href=3D"mailto:arpegio@comcast.net">arpegio@comcast.net</A>> wrote =
in message=20
=3D<BR>>news:45b46e27@linux...<BR>> =
Dimitrios,<BR>> I'm=20
still liking it as much as anything else I've heard.<BR>> The =
grouping feature is just another plus although<BR>> it must =
be a pain=20
to use - opening plugins etc..<BR>><BR>> Have you checked =
out=20
Brian's technique of soloing within<BR>> a Paris =
editor? I=20
never figured it out but he makes it<BR>> look simple like =
everything=20
else..<BR>> Tom<BR>> "Dimitrios" <<A=20
href=3D"mailto:musurgio@otenet.gr">musurgio@otenet.gr</A>> wrote in =
message=20
=3D<BR>>news:45b468da$1@linux...<BR>><BR>> =20
Hi,<BR>> Automatic figuring out of actual latency =
is a=20
"impossible" task.<BR>> Although a plug-in =
reports its=20
latency to the host, a plug-in=20
cannot<BR>=3D<BR>>request<BR>> this value from =
another=20
plug-in !<BR>> Thats why we are somehow doomed =
for=20
automatic latency detection.<BR>> But this hand =
typing of=20
latency for a single plugin is a great =3D<BR>>feature=20
!!<BR>> Regards,<BR>> =20
Dimitrios<BR>><BR>> "Brandon" <<A=20
href=3D"mailto:a@a.com">a@a.com</A>> =
wrote:<BR>> =20
><BR>> >Would be =
cool.<BR>> =20
>I like what Chuck is working on as well.<BR>> =
>If=20
it could automatically figure it out the latency would be=20
=3D<BR>>awesome.<BR>> >If you can just type =
in a=20
latency you knew was greater than the=20
=3D<BR>>largest<BR>> =
it<BR>> =20
>would be cool instead of trying to figure out what the actual=20
=3D<BR>>latency is.<BR>> =20
>B=3D20<BR>> ><BR>> =20
><BR>> >Chas. Duncan=20
<duncan5199ATsbcglobalDOTnet@> wrote:<BR>> =20
>><BR>> >>Now this is a cool=20
idea.<BR>> >><BR>> =
>>--=20
thanks -- chas.<BR>> =
>><BR>> =20
>>On 21 Jan 2007 07:53:33 +1000, "Dimitrios" <<A=20
href=3D"mailto:musurgio@otenet.gr">musurgio@otenet.gr</A>>=20
=3D<BR>>wrote:<BR>> =
>><BR>> =20
>>><BR>> =20
>>>Yes.<BR>> >>>I contacted the =
Vertex=20
dsp vst plugin author who is a very nice =3D<BR>>guy=20
by<BR>> >the<BR>> =20
>>>way...<BR>> >>>He will =
update vertex=20
dsp fader vst plugin with a LIGHT manual =3D<BR>>delay=20
compensator<BR>> >>>suited for us =
Parisians=20
!!<BR>> >>>The concept is the=20
following:<BR>> >>>We put dsp fader vst =
one very=20
paris audio track.<BR>> =20
>>>Benefits.<BR>> >>>We can =
solo mute=20
certain Paris audio track groups.<BR>> =
>>>Now=20
you can solo your drumtracks only or maybe mute all your=20
=3D<BR>>acoustic<BR>> =
guitars<BR>> =20
>>>!!<BR>> >>>BEYOND these =
already=20
implemented things this nice plugin has to=20
=3D<BR>>offer<BR>> =
tha<BR>> =20
>>>author will implement the =
following:<BR>> =20
>>>Note that you have opened vertex on all paris audio=20
tracks.<BR>> >>>Now lets say you put =
waves=20
rencomp to audiotrack 1 that =3D<BR>>introduces=20
a<BR>> delay<BR>> =
>>>of 64=20
samples.<BR>> >>>What you do is type the =
number=20
64 on this track's vertex dsp=20
vst<BR>=3D<BR>>instance<BR>> >>>the =
number 64=20
and ALL OTHER vertex instances GET DELAYED by 64=20
=3D<BR>>samples<BR>> =
>!!<BR>> =20
>>>Isn't that a nice thought ?<BR>> =20
>>>Same with eds insertion of a plugin like eds compressor =
with a=20
=3D<BR>>lookahead,<BR>> >>>just type =
the=20
corresponding samples in delay and all other=20
tracks<BR>=3D<BR>>get<BR>> =20
delayed<BR>> >>>automatically=20
!!<BR>> >>>I hope that we will support =
this guy=20
with this plugin if we =
want<BR>=3D<BR>>ci\ontinuing<BR>> =20
>>>support...<BR>> >>>What do =
you think=20
>?><BR>> =20
>>>Regards,<BR>> =20
>>>Dimitrios<BR>> =20
>><BR>> =
><BR>><BR>><BR>><BR>> =20
I choose Polesoft Lockspam to fight spam, and you?<BR>> <A=20
=
href=3D"http://www.polesoft.com/refer.html">http://www.polesoft.com/refer=
..html</A> =20
<BR>><BR>><!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0=20
Transitional//EN"><BR>><HTML><HEAD> <BR>><META=20
http-equiv=3D3DContent-Type content=3D3D"text/html;=20
=3D<BR>>charset=3D3Diso-8859-1"><BR>><META =
content=3D3D"MSHTML=20
6.00.5730.11"=20
=
name=3D3DGENERATOR><BR>><STYLE></STYLE> <BR>></HEA=
D><BR>><BODY=20
bgColor=3D3D#ffffff><BR>><DIV><FONT face=3D3DArial =
size=3D3D2>Tom,=20
it is simple. Select in the editor<BR>=3D<BR>>what =
tracks=3D20<BR>>you want=20
to solo. You can use control+k to cut at the time line if you =
=3D<BR>>have=20
a=3D20<BR>>specific section you want. With those highlighted, go to =
the=20
Control 16<BR>=3D<BR>>and=3D20<BR>>there is a specific button =
for play=20
selected it. That's it. Just undo =3D<BR>>your =
cuts=3D20<BR>>once you're=20
done here with a control+z.=20
</FONT></DIV><BR>><DIV><FONT face=3D3DArial=20
size=3D3D2></FONT> </DIV><BR>><DIV><FONT =
face=3D3DArial=20
size=3D3D2>AA</FONT></DIV> ; <BR>><BLOCKQUOTE=20
dir=3D3Dltr=3D20<BR>>style=3D3D"PADDING-RIGHT: 0px; PADDING-LEFT: =
5px;=20
MARGIN-LEFT: 5px; =3D<BR>>BORDER-LEFT: #000000 2px solid; =
MARGIN-RIGHT:=20
0px"><BR>> <DIV>"Tom Bruhl" =
<<A=3D20<BR>> =20
href=3D3D"<A=20
=
href=3D'mailto:arpegio@comcast.net">arpegio@comcast.net</A'>mailto:arpegi=
o@comcast.net">arpegio@comcast.net</A</A>>>=20
wrote =3D<BR>>in message=3D20<BR>> <A href=3D3D"<A=20
=
href=3D'news:45b46e27@linux">news:45b46e27@linux</A>...</DIV'>news:45b46e=
27@linux">news:45b46e27@linux</A>...</DIV</A>><BR>>&nbs=
p;=20
<DIV><FONT face=3D3DArial=20
size=3D3D2>Dimitrios,</FONT></DI V> <BR>> =20
<DIV><FONT face=3D3DArial size=3D3D2>I'm still liking it =
as much as=20
=3D<BR>>anything else I've=3D20<BR>> =20
heard.</FONT></DIV><BR>> <DIV><FONT =
face=3D3DArial=20
size=3D3D2>The grouping feature is just=20
another<BR>=3D<BR>>plus=3D20<BR>> =20
although</FONT></DIV><BR>> <DIV><FONT=20
face=3D3DArial size=3D3D2>it must be a pain to use - opening=20
=3D<BR>>plugins=3D20<BR>> =
etc..</FONT></DIV><BR>> =20
<DIV><FONT face=3D3DArial size=3D3D2></FONT>=20
</DIV><BR>> <DIV><FONT face=3D3DArial =
size=3D3D2>Have=20
you checked out Brian's =3D<BR>>technique of =
soloing=3D20<BR>> =20
within</FONT></DIV><BR>> <DIV><FONT =
face=3D3DArial=20
size=3D3D2>a Paris editor? I never figured =3D<BR>>it out=20
but=3D20<BR>> he makes =
it</FONT></DIV><BR>> =20
<DIV><FONT face=3D3DArial size=3D3D2>look simple like =
everything=20
=3D<BR>>else..</FONT></DIV> <BR>> =
<DIV><FONT=20
face=3D3DArial =
size=3D3D2>Tom</FONT></DIV&g t; <BR>> =20
<BLOCKQUOTE=3D20<BR>> style=3D3D"PADDING-RIGHT: 0px; =
PADDING-LEFT:=20
5px; MARGIN-LEFT: 5px; =3D<BR>>BORDER-LEFT: #000000 2px solid; =
MARGIN-RIGHT:=20
0px"><BR>> <DIV>"Dimitrios"=20
<<A=3D20<BR>> href=3D3D"<A=20
=
href=3D'mailto:musurgio@otenet.gr">musurgio@otenet.gr</A'>mailto:musurgio=
@otenet.gr">musurgio@otenet.gr</A</A>>>=20
wrote =3D<BR>>in message=3D20<BR>> =20
<A=3D20<BR>> =3D<BR>>href=3D3D"<A=20
=
href=3D'news:45b468da$1@linux">news:45b468da$1@linux</A>...</DIV><BR>Hi'>=
news:45b468da$1@linux">news:45b468da$1@linux</A>...</DIV>&=
lt;BR>Hi</A>,<=3D<BR>>BR>Automatic=3D20 <BR>> &n=
bsp;=20
figuring out of actual latency is a "impossible" =
task.<BR>Although=20
a<BR>=3D<BR>>plug-in=3D20<BR>> reports its =
latency to the=20
host, a plug-in cannot request<BR>this =3D<BR>>value=20
from=3D20<BR>> another plug-in !<BR>Thats =
why we are=20
somehow doomed for automatic =
=3D<BR>>latency=3D20<BR>> =20
detection.<BR>But this hand typing of latency for a single =
plugin=20
is<BR>=3D<BR>>a great=3D20<BR>> feature=20
!!<BR>Regards,<BR>Dimitrios& lt;BR><BR> "Brandon"=20
<<A=3D20<BR>> href=3D3D"<A=20
=
href=3D'mailto:a@a.com">a@a.com</A'>mailto:a@a.com">a@a.com</A</A>&=
gt;>=20
wrote:<BR>><BR>>Wo uld=20
=3D<BR>>be=3D20<BR>> cool.<BR>>I like =
what Chuck=20
is working on as well.<BR>>If it=20
=3D<BR>>could=3D20<BR>> automatically figure =
it out the=20
latency would be awesome.<BR>>If =3D<BR>>you=20
can=3D20<BR>> just type in a latency you knew was =
greater=20
than the=3D20<BR>> =
largest<BR>it<BR>>would=2 0
be cool instead of trying to figure out =3D<BR>>what=20
the=3D20<BR>> actual latency is.<BR>>B=20
<BR>><BR>>< BR>>Chas.=20
Duncan=3D20<BR>> =
<duncan5199ATsbcglobalDOTnet@>=20
=3D<BR> >wrote:<BR>>><BR&a mp;gt;>>Now=20
this=3D20<BR>> is a cool=20
idea.<BR>>><BR>&am p;gt;>-- thanks=20
--=3D20<BR>> =
chas.<BR>>><BR>&am p;gt;>On 21=20
Jan 2007 07:53:33 +1000, =
=3D<BR>>"Dimitrios"=3D20<BR>> =20
<<A href=3D3D"<A=20
=
href=3D'mailto:musurgio@otenet.gr">musurgio@otenet.gr</A'>mailto:musurgio=
@otenet.gr">musurgio@otenet.gr</A</A>>>=20
=3D<BR>><BR>> =20
=
=3D<BR> >wrote:<BR>>><BR&a mp;gt;>>><BR>>& ;g=
t;>Yes.<BR>>>>I=3D 20 <BR>> =20
contacted the Vertex dsp vst plugin author who is a very nice=20
guy=3D20<BR>> =20
=
by<BR>>the<BR>>&am p;gt;>way...<BR>>>> ;He =
will=20
update =3D<BR>>vertex dsp=3D20<BR>> fader vst =
plugin with=20
a LIGHT manual delay=20
=
=3D<BR> >compensator<BR>>>> ;suited=3D20 <BR>> &nbs=
p; =20
for us Parisians !!<BR>>>>The concept is=20
the=3D20<BR>> following:<BR>>>>We =
put dsp=20
fader vst one very paris audio=3D20<BR>> =20
track.<BR>>>>Benefits.&am p;lt;BR>>>>We can solo =
mute=20
=3D<BR>>certain=3D20<BR>> Paris audio track=20
groups.<BR>>>>Now you can solo your=20
=3D<BR>>drumtracks=3D20<BR>> only or maybe =
mute all=20
your=3D20<BR>> =20
=
acoustic<BR>guitars<BR>>& amp;gt;>!!<BR>>>>B E=
YOND=20
these =3D<BR>>already=3D20<BR>> implemented =
things this=20
nice plugin has to=3D20<BR>> =20
offer<BR>tha<BR>>> >author will implement=20
the=3D20<BR>> =
following:<BR>>>>Note that you=20
have opened vertex on all =
=3D<BR>>paris=3D20<BR>> audio=20
tracks.<BR>>>>Now lets say you put waves rencomp =
=3D<BR>>to=20
=3D20<BR>> audiotrack 1 that introduces=20
a<BR>delay<BR>>>&a mp;gt;of =
64=3D20<BR>> =20
samples.<BR>>>>What you do is type the number 64 on =
this=20
=3D<BR>>track's=3D20<BR>> vertex dsp vst=20
instance<BR>>>>the number 64 and ALL OTHER=20
=3D<BR>>vertex=3D20<BR>> instances GET DELAYED =
by 64=20
samples<BR>>!!<BR>> ;>>Isn't =3D<BR>>that=20
a=3D20<BR>> nice thought =
?<BR>>>>Same with=20
eds insertion of a plugin =3D<BR>>like =
eds=3D20<BR>> =20
compressor with a lookahead,<BR>>>>just type the=20
=3D<BR>>corresponding=3D20<BR>> samples in =
delay and all=20
other tracks=3D20<BR>> =20
get<BR>delayed<BR>>&g t;>automatically=20
!!<BR>>>>I hope =3D<BR>>that =
we=3D20<BR>> =20
will support this guy with this plugin if we =
want=3D20<BR>> =20
ci\ontinuing<BR>>>>suppor t...<BR>>>>What =
do you=20
=3D<BR>>think=3D20<BR>> =20
=
=3D<BR> >>?><BR>>>& amp;gt;Regards,<BR>>>>D=
imitrios<BR>>><BR=3D<BR>>>><BR></BLOCKQU=
OTE><BR>> =20
<DIV><FONT size=3D3D2><BR><BR>I choose =
Polesoft Lockspam=20
to fight spam,<BR>=3D<BR>>and=3D20<BR>> =20
you?<BR><A=3D20<BR>> =3D<BR>>href=3D3D"<A=20
=
href=3D'http://www.polesoft.com/refer.html">http://www.polesoft.com/refer=
'>http://www.polesoft.com/refer.html">http://www.polesoft.com/refer</A=
>=3D<BR>>.html</A>=20
=
</FONT></DIV></BLOCKQUOTE ></BODY></HTML> <BR=
>><BR>><BR></BLOCKQUOTE></BODY></HTML>
------=_NextPart_000_0141_01C73E3A.BF902A30--
|
|
|
|
Goto Forum:
Current Time: Wed Dec 25 04:34:56 PST 2024
Total time taken to generate the page: 0.01324 seconds
|
The PARIS Forums
Search
Help
Members
Register
Login
Home
