Home » The PARIS Forums » PARIS: Main » Faderworks new update !!! see how it looks !!!!!!!!!
|
|
|
|
|
|
|
|
|
|
|
Re: Faderworks new update !!! see how it looks !!!!!!!!! [message #97920 is a reply to message #97919] |
Fri, 11 April 2008 14:08 |
Tom Bruhl
Messages: 1368 Registered: June 2007
|
Senior Member |
|
|
This is a multi-part message in MIME format.
------=_NextPart_000_0037_01C89BF6.9FC977E0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
I am patiently waiting . . .=20
"Dimitrios" <musurgio@otenet.gr> wrote in message =
news:47ffd102$1@linux...
This is the Alpha version.
In a few days I will the full beta version to test...
I truly believe that faderworks is a godsend plugin for Paris.
Not to overcome the 32 groups it has where you can solo mute and =
change volume
for ecrtain audio tracks across all submixes !
Cheers,
Dimitrios
"Mike Audet" <mike@..> wrote:
>
>Hi Dimitrios,
>
>This is huge!!! I did buy faderworks to support the cause. I'll =
have to
>get this update.
>
>Great stuff!!!
>
>Mike
>
>"Dimitrios" <musurgio@otenet.gr> wrote:
>>
>>
>>
>>The author promised me a new upgrade for Faderworks tailored to us =
Paris
>users
>>!!!
>>This the page where you put all your plugins names and known =
latencies
so
>>every time you put a plugin on your audio track you just push the om =
button
>>and all other Paris audio tracks get alligned !!
>>What else could we ask from a third party plugin developer ??
>>He first made a PDC for us when I kindly asked him so and then he =
makes
>this
>>update to make it even better for all of us Paris users ( am I alone =
??)
>>For all thos that have not bought Faderworks please do so to show =
our gratitute
>>because he will make our work with Paris so much easier !
>>DeeJ come on back we are waiting for you, jump on Paris again !
>>Regards,
>>Dimitrios
>>
>
I choose Polesoft Lockspam to fight spam, and you?
http://www.polesoft.com/refer.html
------=_NextPart_000_0037_01C89BF6.9FC977E0
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.2900.2180" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>I am patiently waiting . . . =
</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 =
href=3D"news:47ffd102$1@linux">news:47ffd102$1@linux</A>...</DIV><BR>This=
is=20
the Alpha version.<BR>In a few days I will the full beta version to=20
test...<BR>I truly believe that faderworks is a godsend plugin for=20
Paris.<BR>Not to overcome the 32 groups it has where you can solo mute =
and=20
change volume<BR>for ecrtain audio tracks across all submixes=20
!<BR>Cheers,<BR>Dimitrios<BR><BR>"Mike Audet" <mike@..>=20
wrote:<BR>><BR>>Hi Dimitrios,<BR>><BR>>This is =
huge!!! I did=20
buy faderworks to support the cause. I'll have to<BR>>get =
this=20
update.<BR>><BR>>Great=20
stuff!!!<BR>><BR>>Mike<BR>><BR>> "Dimitrios" <<A=20
href=3D"mailto:musurgio@otenet.gr">musurgio@otenet.gr</A>>=20
wrote:<BR>>><BR>>><BR>>> <BR>>>The author =
promised me a=20
new upgrade for Faderworks tailored to us=20
Paris<BR>>users<BR>>>!!!<BR>>>This the page where you =
put all=20
your plugins names and known latencies<BR>so<BR>>>every time you =
put a=20
plugin on your audio track you just push the om button<BR>>>and =
all=20
other Paris audio tracks get alligned !!<BR>>>What else could we =
ask=20
from a third party plugin developer ??<BR>>>He first made a PDC =
for us=20
when I kindly asked him so and then he =
makes<BR>>this<BR>>>update to=20
make it even better for all of us Paris users ( am I alone =
??)<BR>>>For=20
all thos that have not bought Faderworks please do so to show our=20
gratitute<BR>>>because he will make our work with Paris so much =
easier=20
!<BR>>>DeeJ come on back we are waiting for you, jump on Paris =
again=20
=
!<BR>>>Regards,<BR>>>Dimitrios <BR>>><BR>><BR></BLOCK=
QUOTE>
<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_0037_01C89BF6.9FC977E0--
|
|
|
|
|
|
|
|
|
|
|
|
Re: Faderworks new update !!! see how it looks !!!!!!!!! [message #97936 is a reply to message #97907] |
Sat, 12 April 2008 09:34 |
|
Dimitrios, I'm wondering - I've never used FaderWorks, but seeing as plugin
latencies are absolute and repeatable across systems - are there any plans
to include a database of the commonly used plugins so Faderworks just
recognizes them and sets their latencies automatically?
Yes, I know it's lazy - and the current version doesn't seem to be much of a
hassle at all. But you gotta admit, it'd be elegant. All that seems
necessary is for the most commonly used plugins to be databased by
Faderworks in advance rather than being manually entered and for the
software to do what software does best (which is to go look stuff up and
write it somewhere else). Or maybe I'm misunderstanding how it works, and it
does this already?
- Kerry
On 4/11/08 11:26 AM, in article 47ffad71$1@linux, "Dimitrios"
<musurgio@otenet.gr> wrote:
>
> The author promised me a new upgrade for Faderworks tailored to us Paris users
> !!!
> This the page where you put all your plugins names and known latencies so
> every time you put a plugin on your audio track you just push the om button
> and all other Paris audio tracks get alligned !!
> What else could we ask from a third party plugin developer ??
> He first made a PDC for us when I kindly asked him so and then he makes this
> update to make it even better for all of us Paris users ( am I alone ??)
> For all thos that have not bought Faderworks please do so to show our
> gratitute
> because he will make our work with Paris so much easier !
> DeeJ come on back we are waiting for you, jump on Paris again !
> Regards,
> Dimitrios
"... being bitter is like swallowing poison and waiting for the other guy to die..." - anon
|
|
|
|
Re: Faderworks new update !!! see how it looks !!!!!!!!! [message #97939 is a reply to message #97907] |
Sat, 12 April 2008 15:29 |
|
Ok..Now, I'm on-board with fader works. I'll be back on Paris this summer..So,
this update is a good one..
P.S. Maybe we could get those folks ove at Solid State Logic
http://www.solid-state-logic.com/music/Pro-Convert/index.asp
(EDL Convert) to write a session conversion for Paris. That way tjose of
us who are on other DAWS, can open other formats and so on..?? It's worth
a try..
"Dimitrios" <musurgio@otenet.gr> wrote:
>
>
>
>The author promised me a new upgrade for Faderworks tailored to us Paris
users
>!!!
>This the page where you put all your plugins names and known latencies so
>every time you put a plugin on your audio track you just push the om button
>and all other Paris audio tracks get alligned !!
>What else could we ask from a third party plugin developer ??
>He first made a PDC for us when I kindly asked him so and then he makes
this
>update to make it even better for all of us Paris users ( am I alone ??)
>For all thos that have not bought Faderworks please do so to show our gratitute
>because he will make our work with Paris so much easier !
>DeeJ come on back we are waiting for you, jump on Paris again !
>Regards,
>Dimitrios
>
|
|
|
Re: Faderworks new update !!! see how it looks !!!!!!!!! [message #97941 is a reply to message #97936] |
Sat, 12 April 2008 18:32 |
Dimitrios
Messages: 1056 Registered: August 2005
|
Senior Member |
|
|
Kerry,
The uthor refused to make a ral pdc because of some restrictions that vst
plugins give.
Anyway maybe you did not understand how Faderworks new version will work.
Ok...
So you have a bunch of plugins.
You collect their latencies, someone , maybe me, will post the most used
plugins with their latencies...
Then you just make presets inside faderworks with name and latency.
For instance
Waves rvox 64
Waves rcomp 64
Drumagog 175
etc
Then whenever you put say rvox on a paris audio track you just will scroll
your column inside faderworks until you find the one named rvox nd just hit
the on button !
Thats all !!
All other faderworkds instances on all other paris audio tracks will get
delayed by that latency !
Its a damn clever sustem.
It even substracts latencies !!
So if you have a overall 256 samples latency and you put a plugin on a new
track that has 64 then the 256 overall does not change but the above track
gets delayed by 256-64= 198 !!!
He is damn clever guy !
Hope this helps,
Regards,
Dimitrios
Kerry Galloway <kg@kerrygalloway.com> wrote:
>Dimitrios, I'm wondering - I've never used FaderWorks, but seeing as plugin
>latencies are absolute and repeatable across systems - are there any plans
>to include a database of the commonly used plugins so Faderworks just
>recognizes them and sets their latencies automatically?
>
>Yes, I know it's lazy - and the current version doesn't seem to be much
of a
>hassle at all. But you gotta admit, it'd be elegant. All that seems
>necessary is for the most commonly used plugins to be databased by
>Faderworks in advance rather than being manually entered and for the
>software to do what software does best (which is to go look stuff up and
>write it somewhere else). Or maybe I'm misunderstanding how it works, and
it
>does this already?
>
>- Kerry
>
>
>On 4/11/08 11:26 AM, in article 47ffad71$1@linux, "Dimitrios"
><musurgio@otenet.gr> wrote:
>
>>
>> The author promised me a new upgrade for Faderworks tailored to us Paris
users
>> !!!
>> This the page where you put all your plugins names and known latencies
so
>> every time you put a plugin on your audio track you just push the om button
>> and all other Paris audio tracks get alligned !!
>> What else could we ask from a third party plugin developer ??
>> He first made a PDC for us when I kindly asked him so and then he makes
this
>> update to make it even better for all of us Paris users ( am I alone ??)
>> For all thos that have not bought Faderworks please do so to show our
>> gratitute
>> because he will make our work with Paris so much easier !
>> DeeJ come on back we are waiting for you, jump on Paris again !
>> Regards,
>> Dimitrios
>
|
|
|
Re: Faderworks new update !!! see how it looks !!!!!!!!! [message #97942 is a reply to message #97941] |
Sat, 12 April 2008 19:22 |
Tom Bruhl
Messages: 1368 Registered: June 2007
|
Senior Member |
|
|
This is a multi-part message in MIME format.
------=_NextPart_000_0011_01C89CEB.A6C86E20
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
>Dimitrios,
Does Paris automation and it's GUI remain lined up
after applying a plugin with latency and compensating with Faderworks?
What is the prospective time of availablitity for this blessing?
>Tom
"Dimitrios" <musurgio@otenet.gr> wrote in message =
news:480162c4$1@linux...
Kerry,
The uthor refused to make a ral pdc because of some restrictions that =
vst
plugins give.
Anyway maybe you did not understand how Faderworks new version will =
work.
Ok...
So you have a bunch of plugins.
You collect their latencies, someone , maybe me, will post the most =
used
plugins with their latencies...
Then you just make presets inside faderworks with name and latency.
For instance
Waves rvox 64
Waves rcomp 64
Drumagog 175
etc
Then whenever you put say rvox on a paris audio track you just will =
scroll
your column inside faderworks until you find the one named rvox nd =
just hit
the on button !
Thats all !!
All other faderworkds instances on all other paris audio tracks will =
get
delayed by that latency !
Its a damn clever sustem.
It even substracts latencies !!
So if you have a overall 256 samples latency and you put a plugin on a =
new
track that has 64 then the 256 overall does not change but the above =
track
gets delayed by 256-64=3D 198 !!!
He is damn clever guy !
Hope this helps,
Regards,
Dimitrios
Kerry Galloway <kg@kerrygalloway.com> wrote:
>Dimitrios, I'm wondering - I've never used FaderWorks, but seeing as =
plugin
>latencies are absolute and repeatable across systems - are there any =
plans
>to include a database of the commonly used plugins so Faderworks just
>recognizes them and sets their latencies automatically?
>
>Yes, I know it's lazy - and the current version doesn't seem to be =
much
of a
>hassle at all. But you gotta admit, it'd be elegant. All that seems
>necessary is for the most commonly used plugins to be databased by
>Faderworks in advance rather than being manually entered and for the
>software to do what software does best (which is to go look stuff up =
and
>write it somewhere else). Or maybe I'm misunderstanding how it works, =
and
it
>does this already?
>
>- Kerry
>
>
>On 4/11/08 11:26 AM, in article 47ffad71$1@linux, "Dimitrios"
><musurgio@otenet.gr> wrote:
>
>>=20
>> The author promised me a new upgrade for Faderworks tailored to us =
Paris
users
>> !!!
>> This the page where you put all your plugins names and known =
latencies
so
>> every time you put a plugin on your audio track you just push the =
om button
>> and all other Paris audio tracks get alligned !!
>> What else could we ask from a third party plugin developer ??
>> He first made a PDC for us when I kindly asked him so and then he =
makes
this
>> update to make it even better for all of us Paris users ( am I =
alone ??)
>> For all thos that have not bought Faderworks please do so to show =
our
>> gratitute
>> because he will make our work with Paris so much easier !
>> DeeJ come on back we are waiting for you, jump on Paris again !
>> Regards,
>> Dimitrios
>
I choose Polesoft Lockspam to fight spam, and you?
http://www.polesoft.com/refer.html
------=_NextPart_000_0011_01C89CEB.A6C86E20
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.2900.2180" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>>Dimitrios,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Does Paris automation and it's GUI =
remain=20
lined up</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>after applying a plugin with =
latency and=20
compensating with Faderworks?</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>What is the prospective time of =
availablitity for=20
this blessing?</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>>Tom</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV> </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>"Dimitrios" <<A=20
href=3D"mailto:musurgio@otenet.gr">musurgio@otenet.gr</A>> wrote in =
message=20
<A=20
=
href=3D"news:480162c4$1@linux">news:480162c4$1@linux</A>...</DIV><BR>Kerr=
y,<BR>The=20
uthor refused to make a ral pdc because of some restrictions that=20
vst<BR>plugins give.<BR>Anyway maybe you did not understand how =
Faderworks new=20
version will work.<BR>Ok...<BR>So you have a bunch of plugins.<BR>You =
collect=20
their latencies, someone , maybe me, will post the most =
used<BR>plugins with=20
their latencies...<BR>Then you just make presets inside faderworks =
with name=20
and latency.<BR>For instance<BR>Waves rvox 64<BR>Waves rcomp=20
64<BR>Drumagog 175<BR>etc<BR><BR>Then whenever you =
put say=20
rvox on a paris audio track you just will scroll<BR>your column inside =
faderworks until you find the one named rvox nd just hit<BR>the on =
button=20
!<BR>Thats all !!<BR>All other faderworkds instances on all other =
paris audio=20
tracks will get<BR>delayed by that latency !<BR>Its a damn clever=20
sustem.<BR>It even substracts latencies !!<BR>So if you have a overall =
256=20
samples latency and you put a plugin on a new<BR>track that has 64 =
then the=20
256 overall does not change but the above track<BR>gets delayed by =
256-64=3D 198=20
!!!<BR>He is damn clever guy !<BR>Hope this=20
helps,<BR>Regards,<BR>Dimitrios<BR><BR>Kerry Galloway <<A=20
href=3D"mailto:kg@kerrygalloway.com">kg@kerrygalloway.com</A>>=20
wrote:<BR>>Dimitrios, I'm wondering - I've never used FaderWorks, =
but=20
seeing as plugin<BR>>latencies are absolute and repeatable across =
systems -=20
are there any plans<BR>>to include a database of the commonly used =
plugins=20
so Faderworks just<BR>>recognizes them and sets their latencies=20
automatically?<BR>><BR>>Yes, I know it's lazy - and the current =
version=20
doesn't seem to be much<BR>of a<BR>>hassle at all. But you gotta =
admit,=20
it'd be elegant. All that seems<BR>>necessary is for the most =
commonly used=20
plugins to be databased by<BR>>Faderworks in advance rather than =
being=20
manually entered and for the<BR>>software to do what software does =
best=20
(which is to go look stuff up and<BR>>write it somewhere else). Or =
maybe=20
I'm misunderstanding how it works, and<BR>it<BR>>does this=20
already?<BR>><BR>>- Kerry<BR>><BR>><BR>>On 4/11/08 =
11:26 AM, in=20
article <A href=3D"mailto:47ffad71$1@linux">47ffad71$1@linux</A>,=20
"Dimitrios"<BR>><<A=20
href=3D"mailto:musurgio@otenet.gr">musurgio@otenet.gr</A>>=20
wrote:<BR>><BR>>> <BR>>> The author promised me a new =
upgrade=20
for Faderworks tailored to us Paris<BR>users<BR>>> =
!!!<BR>>> This=20
the page where you put all your plugins names and known=20
latencies<BR>so<BR>>> every time you put a plugin on your audio =
track=20
you just push the om button<BR>>> and all other Paris audio =
tracks get=20
alligned !!<BR>>> What else could we ask from a third party =
plugin=20
developer ??<BR>>> He first made a PDC for us when I kindly =
asked him so=20
and then he makes<BR>this<BR>>> update to make it even better =
for all of=20
us Paris users ( am I alone ??)<BR>>> For all thos that have not =
bought=20
Faderworks please do so to show our<BR>>> gratitute<BR>>> =
because=20
he will make our work with Paris so much easier !<BR>>> DeeJ =
come on=20
back we are waiting for you, jump on Paris again !<BR>>>=20
Regards,<BR>>> Dimitrios<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_0011_01C89CEB.A6C86E20--
|
|
|
Re: Faderworks new update !!! see how it looks !!!!!!!!! [message #97943 is a reply to message #97942] |
Sat, 12 April 2008 22:25 |
|
> 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_3290883939_20656351
Content-type: text/plain;
charset="ISO-8859-1"
Content-transfer-encoding: 8bit
I may be talking out my hindquarters here, but it seems to me that the
principle that it works on is delaying audio streams according to a
mini-database of latencies; I don�t see how the editor screen could know
anything about what the plugins are doing to the audio, so I�m guessing no.
Of course I�d love to have that hunch proven wrong.
- K
On 4/12/08 7:22 PM, in article 480170b3@linux, "Tom Bruhl"
<arpegio@comcast.net> wrote:
>> >Dimitrios,
> Does Paris automation and it's GUI remain lined up
> after applying a plugin with latency and compensating with Faderworks?
>
> What is the prospective time of availablitity for this blessing?
>> >Tom
>
>
>
>
>>
>> "Dimitrios" <musurgio@otenet.gr> wrote in message news:480162c4$1@linux...
>>
>> Kerry,
>> The uthor refused to make a ral pdc because of some restrictions that vst
>> plugins give.
>> Anyway maybe you did not understand how Faderworks new version will work.
>> Ok...
>> So you have a bunch of plugins.
>> You collect their latencies, someone , maybe me, will post the most used
>> plugins with their latencies...
>> Then you just make presets inside faderworks with name and latency.
>> For instance
>> Waves rvox 64
>> Waves rcomp 64
>> Drumagog 175
>> etc
>>
>> Then whenever you put say rvox on a paris audio track you just will scroll
>> your column inside faderworks until you find the one named rvox nd just hit
>> the on button !
>> Thats all !!
>> All other faderworkds instances on all other paris audio tracks will get
>> delayed by that latency !
>> Its a damn clever sustem.
>> It even substracts latencies !!
>> So if you have a overall 256 samples latency and you put a plugin on a new
>> track that has 64 then the 256 overall does not change but the above track
>> gets delayed by 256-64= 198 !!!
>> He is damn clever guy !
>> Hope this helps,
>> Regards,
>> Dimitrios
>>
>> Kerry Galloway <kg@kerrygalloway.com> wrote:
>>> >Dimitrios, I'm wondering - I've never used FaderWorks, but seeing as
>>> plugin
>>> >latencies are absolute and repeatable across systems - are there any plans
>>> >to include a database of the commonly used plugins so Faderworks just
>>> >recognizes them and sets their latencies automatically?
>>> >
>>> >Yes, I know it's lazy - and the current version doesn't seem to be much
>> of a
>>> >hassle at all. But you gotta admit, it'd be elegant. All that seems
>>> >necessary is for the most commonly used plugins to be databased by
>>> >Faderworks in advance rather than being manually entered and for the
>>> >software to do what software does best (which is to go look stuff up and
>>> >write it somewhere else). Or maybe I'm misunderstanding how it works, and
>> it
>>> >does this already?
>>> >
>>> >- Kerry
>>> >
>>> >
>>> >On 4/11/08 11:26 AM, in article 47ffad71$1@linux, "Dimitrios"
>>> ><musurgio@otenet.gr> wrote:
>>> >
>>>> >>
>>>> >> The author promised me a new upgrade for Faderworks tailored to us
>>>> Paris
>> users
>>>> >> !!!
>>>> >> This the page where you put all your plugins names and known latencies
>> so
>>>> >> every time you put a plugin on your audio track you just push the om
>>>> button
>>>> >> and all other Paris audio tracks get alligned !!
>>>> >> What else could we ask from a third party plugin developer ??
>>>> >> He first made a PDC for us when I kindly asked him so and then he makes
>> this
>>>> >> update to make it even better for all of us Paris users ( am I alone
>>>> ??)
>>>> >> For all thos that have not bought Faderworks please do so to show our
>>>> >> gratitute
>>>> >> because he will make our work with Paris so much easier !
>>>> >> DeeJ come on back we are waiting for you, jump on Paris again !
>>>> >> Regards,
>>>> >> Dimitrios
>>> >
>
>
> I choose Polesoft Lockspam to fight spam, and you?
> http://www.polesoft.com/refer.html
>
--B_3290883939_20656351
Content-type: text/html;
charset="ISO-8859-1"
Content-transfer-encoding: quoted-printable
<HTML>
<HEAD>
<TITLE>Re: Faderworks new update !!! see how it looks !!!!!!!!!</TITLE>
</HEAD>
<BODY>
<FONT FACE=3D"Verdana, Helvetica, Arial"><SPAN STYLE=3D'font-size:12.0px'>I may=
be talking out my hindquarters here, but it seems to me that the principle =
that it works on is delaying audio streams according to a mini-database of l=
atencies; I don’t see how the editor screen could know anything about =
what the plugins are doing to the audio, so I’m guessing no. Of course=
I’d love to have that hunch proven wrong.<BR>
<BR>
- K<BR>
<BR>
<BR>
On 4/12/08 7:22 PM, in article 480170b3@linux, "Tom Bruhl" <ar=
pegio@comcast.net> wrote:<BR>
<BR>
</SPAN></FONT><BLOCKQUOTE><SPAN STYLE=3D'font-size:12.0px'><FONT FACE=3D"Arial"=
>>Dimitrios,<BR>
Does Paris automation and it's GUI remain lined up<BR>
after applying a plugin with latency and compensating with Faderworks?<BR>
</FONT><FONT FACE=3D"Verdana, Helvetica, Arial"> <BR>
</FONT><FONT FACE=3D"Arial">What is the prospective time of availablitity for=
this blessing?<BR>
>Tom<BR>
</FONT><FONT FACE=3D"Verdana, Helvetica, Arial"> <BR>
<BR>
<BR>
<BR>
</FONT></SPAN><BLOCKQUOTE><SPAN STYLE=3D'font-size:12.0px'><FONT FACE=3D"Verdan=
a, Helvetica, Arial"> <BR>
"Dimitrios" <musurgio@otenet.gr> wrote in message new=
s:480162c4$1@linux...<BR>
<BR>
Kerry,<BR>
The uthor refused to make a ral pdc because of some restrictions that=
vst<BR>
plugins give.<BR>
Anyway maybe you did not understand how Faderworks new version will w=
ork.<BR>
Ok...<BR>
So you have a bunch of plugins.<BR>
You collect their latencies, someone , maybe me, will post the most u=
sed<BR>
plugins with their latencies...<BR>
Then you just make presets inside faderworks with name and latency.<B=
R>
For instance<BR>
Waves rvox 64<BR>
Waves rcomp 64<BR>
Drumagog 175<BR>
etc<BR>
<BR>
Then whenever you put say rvox on a paris audio track you just will s=
croll<BR>
your column inside faderworks until you find the one named rvox nd ju=
st hit<BR>
the on button !<BR>
Thats all !!<BR>
All other faderworkds instances on all other paris audio tracks will =
get<BR>
delayed by that latency !<BR>
Its a damn clever sustem.<BR>
It even substracts latencies !!<BR>
So if you have a overall 256 samples latency and you put a plugin on =
a new<BR>
track that has 64 then the 256 overall does not change but the above =
track<BR>
gets delayed by 256-64=3D 198 !!!<BR>
He is damn clever guy !<BR>
Hope this helps,<BR>
Regards,<BR>
Dimitrios<BR>
<BR>
Kerry Galloway <kg@kerrygalloway.com> wrote:<BR>
>Dimitrios, I'm wondering - I've never used FaderWorks, but seeing=
as plugin<BR>
>latencies are absolute and repeatable across systems - are there =
any plans<BR>
>to include a database of the commonly used plugins so Faderworks =
just<BR>
>recognizes them and sets their latencies automatically?<BR>
><BR>
>Yes, I know it's lazy - and the current version doesn't seem to b=
e much<BR>
of a<BR>
>hassle at all. But you gotta admit, it'd be elegant. All that see=
ms<BR>
>necessary is for the most commonly used plugins to be databased b=
y<BR>
>Faderworks in advance rather than being manually entered and for =
the<BR>
>software to do what software does best (which is to go look stuff=
up and<BR>
>write it somewhere else). Or maybe I'm misunderstanding how it wo=
rks, and<BR>
it<BR>
>does this already?<BR>
><BR>
>- Kerry<BR>
><BR>
><BR>
>On 4/11/08 11:26 AM, in article 47ffad71$1@linux, "Dim=
itrios"<BR>
><musurgio@otenet.gr> wrote:<BR>
><BR>
>> <BR>
>> The author promised me a new upgrade for Faderworks tailored=
to us Paris<BR>
users<BR>
>> !!!<BR>
>> This the page where you put all your plugins names and known=
latencies<BR>
so<BR>
>> every time you put a plugin on your audio track you just pus=
h the om button<BR>
>> and all other Paris audio tracks get alligned !!<BR>
>> What else could we ask from a third party plugin developer ?=
?<BR>
>> He first made a PDC for us when I kindly asked him so and th=
en he makes<BR>
this<BR>
>> update to make it even better for all of us Paris users ( am=
I alone ??)<BR>
>> For all thos that have not bought Faderworks please do so to=
show our<BR>
>> gratitute<BR>
>> because he will make our work with Paris so much easier !<BR=
>
>> DeeJ come on back we are waiting for you, jump on Paris agai=
n !<BR>
>> Regards,<BR>
>> Dimitrios<BR>
><BR>
</FONT></SPAN></BLOCKQUOTE><SPAN STYLE=3D'font-size:12.0px'><FONT FACE=3D"Verda=
na, Helvetica, Arial"><BR>
<BR>
I choose Polesoft Lockspam to fight spam, and you?<BR>
<a href=3D"http://www.polesoft.com/refer.html">http://www.polesoft.com/refer.=
html</a> <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_3290883939_20656351--
"... being bitter is like swallowing poison and waiting for the other guy to die..." - anon
|
|
|
Re: Faderworks new update !!! see how it looks !!!!!!!!! [message #97945 is a reply to message #97943] |
Sat, 12 April 2008 23:30 |
Tom Bruhl
Messages: 1368 Registered: June 2007
|
Senior Member |
|
|
This is a multi-part message in MIME format.
------=_NextPart_000_000C_01C89D0E.59880AD0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Re: Faderworks new update !!! see how it looks !!!!!!!!!Hi Kerry,
I'm thinking the GUI won't be aware of what's going on behind the =
scenes.
Is that what you're saying also? I'm also thinking that even though it =
looks
lined up it won't sound lined up and still the lines will have to be =
redrawn
visually incorrectly on all the tracks. I hope I'm wrong.
The next step would be to have Faderworks tell us what the total latency =
in use
is then we can offset all automation by that much across the board. =
This would
also necessitate all automation being written before plugs are applied. =
That's
not usually how I work except for tom gating once in a while.
Tom
"Kerry Galloway" <kg@kerrygalloway.com> wrote in message =
news:C426E762.2C6C%kg@kerrygalloway.com...
I may be talking out my hindquarters here, but it seems to me that the =
principle that it works on is delaying audio streams according to a =
mini-database of latencies; I don't see how the editor screen could know =
anything about what the plugins are doing to the audio, so I'm guessing =
no. Of course I'd love to have that hunch proven wrong.
- K
On 4/12/08 7:22 PM, in article 480170b3@linux, "Tom Bruhl" =
<arpegio@comcast.net> wrote:
>Dimitrios,
Does Paris automation and it's GUI remain lined up
after applying a plugin with latency and compensating with =
Faderworks?
What is the prospective time of availablitity for this blessing?
>Tom
=20
=20
=20
"Dimitrios" <musurgio@otenet.gr> wrote in message =
news:480162c4$1@linux...
Kerry,
The uthor refused to make a ral pdc because of some restrictions =
that vst
plugins give.
Anyway maybe you did not understand how Faderworks new version =
will work.
Ok...
So you have a bunch of plugins.
You collect their latencies, someone , maybe me, will post the =
most used
plugins with their latencies...
Then you just make presets inside faderworks with name and =
latency.
For instance
Waves rvox 64
Waves rcomp 64
Drumagog 175
etc
Then whenever you put say rvox on a paris audio track you just =
will scroll
your column inside faderworks until you find the one named rvox =
nd just hit
the on button !
Thats all !!
All other faderworkds instances on all other paris audio tracks =
will get
delayed by that latency !
Its a damn clever sustem.
It even substracts latencies !!
So if you have a overall 256 samples latency and you put a plugin =
on a new
track that has 64 then the 256 overall does not change but the =
above track
gets delayed by 256-64=3D 198 !!!
He is damn clever guy !
Hope this helps,
Regards,
Dimitrios
Kerry Galloway <kg@kerrygalloway.com> wrote:
>Dimitrios, I'm wondering - I've never used FaderWorks, but =
seeing as plugin
>latencies are absolute and repeatable across systems - are there =
any plans
>to include a database of the commonly used plugins so Faderworks =
just
>recognizes them and sets their latencies automatically?
>
>Yes, I know it's lazy - and the current version doesn't seem to =
be much
of a
>hassle at all. But you gotta admit, it'd be elegant. All that =
seems
>necessary is for the most commonly used plugins to be databased =
by
>Faderworks in advance rather than being manually entered and for =
the
>software to do what software does best (which is to go look =
stuff up and
>write it somewhere else). Or maybe I'm misunderstanding how it =
works, and
it
>does this already?
>
>- Kerry
>
>
>On 4/11/08 11:26 AM, in article 47ffad71$1@linux, "Dimitrios"
><musurgio@otenet.gr> wrote:
>
>>=20
>> The author promised me a new upgrade for Faderworks tailored =
to us Paris
users
>> !!!
>> This the page where you put all your plugins names and known =
latencies
so
>> every time you put a plugin on your audio track you just push =
the om button
>> and all other Paris audio tracks get alligned !!
>> What else could we ask from a third party plugin developer ??
>> He first made a PDC for us when I kindly asked him so and then =
he makes
this
>> update to make it even better for all of us Paris users ( am I =
alone ??)
>> For all thos that have not bought Faderworks please do so to =
show our
>> gratitute
>> because he will make our work with Paris so much easier !
>> DeeJ come on back we are waiting for you, jump on Paris again =
!
>> Regards,
>> Dimitrios
>
I choose Polesoft Lockspam to fight spam, and you?
http://www.polesoft.com/refer.html =20
------=_NextPart_000_000C_01C89D0E.59880AD0
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><TITLE>Re: Faderworks new update !!! see how it looks =
!!!!!!!!!</TITLE>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2900.2180" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>Hi Kerry,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>I'm thinking the GUI won't be aware of =
what's going=20
on behind the scenes.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Is that what you're saying also? =
I'm also=20
thinking that even though it looks</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>lined up it won't sound lined up and =
still the=20
lines will have to be redrawn</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>visually incorrectly on all the =
tracks. I=20
hope I'm wrong.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>The next step would be to have =
Faderworks tell us=20
what the total latency in use</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>is then we can offset all automation by =
that much=20
across the board. This would</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>also necessitate all automation being =
written=20
before plugs are applied. That's</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>not usually how I work except for tom =
gating once=20
in a while.</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>"Kerry Galloway" <<A=20
href=3D"mailto:kg@kerrygalloway.com">kg@kerrygalloway.com</A>> =
wrote in=20
message <A=20
=
href=3D"news:C426E762.2C6C%kg@kerrygalloway.com">news:C426E762.2C6C%kg@ke=
rrygalloway.com</A>...</DIV><FONT=20
face=3D"Verdana, Helvetica, Arial"><SPAN style=3D"FONT-SIZE: 12px">I =
may be=20
talking out my hindquarters here, but it seems to me that the =
principle that=20
it works on is delaying audio streams according to a mini-database of=20
latencies; I don=92t see how the editor screen could know anything =
about what=20
the plugins are doing to the audio, so I=92m guessing no. Of course =
I=92d love to=20
have that hunch proven wrong.<BR><BR>- K<BR><BR><BR>On 4/12/08 7:22 =
PM, in=20
article 480170b3@linux, "Tom Bruhl" <arpegio@comcast.net>=20
wrote:<BR><BR></SPAN></FONT>
<BLOCKQUOTE><SPAN style=3D"FONT-SIZE: 12px"><FONT=20
face=3DArial>>Dimitrios,<BR>Does Paris automation and it's GUI =
remain lined=20
up<BR>after applying a plugin with latency and compensating with=20
Faderworks?<BR></FONT><FONT=20
face=3D"Verdana, Helvetica, Arial"><BR></FONT><FONT =
face=3DArial>What is the=20
prospective time of availablitity for this=20
blessing?<BR>>Tom<BR></FONT><FONT=20
face=3D"Verdana, Helvetica, =
Arial"><BR> <BR> <BR> <BR> </FONT></SPAN>
<BLOCKQUOTE><SPAN style=3D"FONT-SIZE: 12px"><FONT=20
face=3D"Verdana, Helvetica, Arial"><BR>"Dimitrios"=20
<musurgio@otenet.gr> wrote in message=20
news:480162c4$1@linux...<BR><BR>Kerry,<BR>The uthor =
refused to=20
make a ral pdc because of some restrictions that =
vst<BR>plugins=20
give.<BR>Anyway maybe you did not understand how Faderworks new=20
version will work.<BR>Ok...<BR>So you have a bunch of=20
plugins.<BR>You collect their latencies, someone , maybe me, =
will=20
post the most used<BR>plugins with their =
latencies...<BR>Then you=20
just make presets inside faderworks with name and =
latency.<BR>For=20
instance<BR>Waves rvox 64<BR>Waves rcomp =
64<BR>Drumagog=20
175<BR>etc<BR><BR>Then whenever you put say =
rvox=20
on a paris audio track you just will scroll<BR>your column inside=20
faderworks until you find the one named rvox nd just =
hit<BR>the on=20
button !<BR>Thats all !!<BR>All other faderworkds instances =
on all=20
other paris audio tracks will get<BR>delayed by that latency =
!<BR>Its a damn clever sustem.<BR>It even substracts =
latencies=20
!!<BR>So if you have a overall 256 samples latency and you =
put a=20
plugin on a new<BR>track that has 64 then the 256 overall =
does not=20
change but the above track<BR>gets delayed by 256-64=3D 198 =
!!!<BR>He=20
is damn clever guy !<BR>Hope this=20
helps,<BR>Regards,<BR>Dimitrios<BR><BR>Kerry Galloway=20
<kg@kerrygalloway.com> wrote:<BR>>Dimitrios, I'm =
wondering=20
- I've never used FaderWorks, but seeing as =
plugin<BR>>latencies=20
are absolute and repeatable across systems - are there any=20
plans<BR>>to include a database of the commonly used plugins =
so=20
Faderworks just<BR>>recognizes them and sets their latencies=20
automatically?<BR>><BR>>Yes, I know it's lazy - and =
the=20
current version doesn't seem to be much<BR>of =
a<BR>>hassle at=20
all. But you gotta admit, it'd be elegant. All that=20
seems<BR>>necessary is for the most commonly used plugins =
to be=20
databased by<BR>>Faderworks in advance rather than being =
manually=20
entered and for the<BR>>software to do what software does best=20
(which is to go look stuff up and<BR>>write it somewhere =
else).=20
Or maybe I'm misunderstanding how it works, =
and<BR>it<BR>>does=20
this already?<BR>><BR>>- =
Kerry<BR>><BR>><BR>>On=20
4/11/08 11:26 AM, in article 47ffad71$1@linux,=20
"Dimitrios"<BR>><musurgio@otenet.gr>=20
wrote:<BR>><BR>>> <BR>>> The author promised =
me a new=20
upgrade for Faderworks tailored to us =
Paris<BR>users<BR>>>=20
!!!<BR>>> This the page where you put all your plugins =
names=20
and known latencies<BR>so<BR>>> every time you put a =
plugin on=20
your audio track you just push the om button<BR>>> and =
all=20
other Paris audio tracks get alligned !!<BR>>> What =
else could=20
we ask from a third party plugin developer ??<BR>>> He =
first=20
made a PDC for us when I kindly asked him so and then he=20
makes<BR>this<BR>>> update to make it even better for all of =
us Paris users ( am I alone ??)<BR>>> For all thos =
that have=20
not bought Faderworks please do so to show our<BR>>>=20
gratitute<BR>>> because he will make our work with =
Paris so=20
much easier !<BR>>> DeeJ come on back we are waiting =
for you,=20
jump on Paris again !<BR>>> Regards,<BR>>>=20
Dimitrios<BR>><BR></FONT></SPAN></BLOCKQUOTE><SPAN=20
style=3D"FONT-SIZE: 12px"><FONT face=3D"Verdana, Helvetica, =
Arial"><BR><BR>I=20
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></FONT></SPAN></BLOCKQUOTE> <SPAN=20
style=3D"FONT-SIZE: 12px"><FONT=20
face=3D"Verdana, Helvetica, =
Arial"><BR></BLOCKQUOTE></FONT></SPAN></BODY></HTML>
------=_NextPart_000_000C_01C89D0E.59880AD0--
|
|
|
Goto Forum:
Current Time: Fri Dec 27 10:52:01 PST 2024
Total time taken to generate the page: 0.04100 seconds
|