Home » The PARIS Forums » PARIS: Main » Author of Vertex needs some input from us to improve !!
|
|
| Re: Author of Vertex needs some input from us to improve !! [message #78777 is a reply to message #78774] |
Mon, 22 January 2007 00:44   |
Dimitrios
Messages: 1056
Registered: August 2005
|
Senior Member |
|
|
Sorry,
I wrongly pressed the wrong button here...
Ok this was after my suggestion of high latency buffer for UAD1 and other
dsp card users.
I know that most of us have plenty of ram but if there is some other suggestion
regarding this latency buffer and its upper limit please reply as soon as
possible...
Note that one instance of uad1 needs 16384 samples.
So a normal uad1 user how many instances of uad1 plyugins does he use on
a normal (or abnormal ) situation ?
His 132000 samples upper limit suggestion as you read on my previous post
is an EIGHT instances of UAD1 plugs as maximum.
Is that enouph ?
Ok DJ please do not answer this :)
If memory is not a problem , I for myself have 1.5 GB and use XP then I would
suggest double of that 234000.
What do ya think ?/
Regards,
Dimitrios
"Dimitrios" <musurgio@otenet.gr> wrote:
>
>Hi,
>Well this guy is willing to help us out with whatever benefits will arrise
>for him by buying his plugin...
>Note that his plugin has a discount until 31 of January , around 46-47 $
>final price.
>WE HAVE TO SHOW our appreciation on developers like him as we can ask for
>further Paris support, like maybe wdm drivers ???
>NOW he asks for some input from us.
>Here is what he wrote on his last email...
>To be flexible enough it is certainly possible to choose a much larger latency
>buffer, but consider this: A buffer consumes memory, e.g. 65536 samples
need
>262144 bytes per channel (each sample is 32 bit floating point for VST).
>If you run e.g. 48 (stereo?)-tracks with 48 instances of FaderWorks you
need
>48 * 2 * 262144 bytes = 25 MB of memory. Should be no problem for today's
>computers, but some users have Win98, so I'm not sure if RAM memory could
>be an issue. If not, I would suggest about 132000 samples as upper limit
>(needs about 1 MB per FaderWorks instance). What do you (or others) think
>about it?
>
>
>
>
|
|
|
|
| Re: Author of Vertex needs some input from us to improve !! [message #78786 is a reply to message #78777] |
Mon, 22 January 2007 04:44 |
Dimitrios
Messages: 1056
Registered: August 2005
|
Senior Member |
|
|
Here is what the author wrote about his latency addon for vertex..!!
Track 1 has a latency of 16384 samples. The same is true for track 2. As
track 1 and track 2 have the same latency they are already in sync, but all
other tracks (the remaining 46 tracks) have to be delayed by 16384 samples,
not 32768.
Take another example: Track 1 has a plug-in with 16384 samples of latency.
Track 2 has a plug-in with a latency of 8192 samples. What FaderWorks will
do is: Tracks 1 will pass through as it is, track 2 will be delayed by 8192
samples and all other tracks will be delayed by 16384 samples.
What counts for the overall latency is the largest latency of any track.
You calculate the sum of latencies only for individual tracks when you e.g.
put several uad1 behind on the same track.
ISN'T that WHAT WE WANT ? !!!
If we don't buy this vertex we have to jump off Paris !! :)
Regards,
Dimitrios
"Dimitrios" <musurgio@otenet.gr> wrote:
>
>Sorry,
>I wrongly pressed the wrong button here...
>Ok this was after my suggestion of high latency buffer for UAD1 and other
>dsp card users.
>I know that most of us have plenty of ram but if there is some other suggestion
>regarding this latency buffer and its upper limit please reply as soon as
>possible...
>Note that one instance of uad1 needs 16384 samples.
>So a normal uad1 user how many instances of uad1 plyugins does he use on
>a normal (or abnormal ) situation ?
>His 132000 samples upper limit suggestion as you read on my previous post
>is an EIGHT instances of UAD1 plugs as maximum.
>Is that enouph ?
>Ok DJ please do not answer this :)
>If memory is not a problem , I for myself have 1.5 GB and use XP then I
would
>suggest double of that 234000.
>What do ya think ?/
>Regards,
>Dimitrios
>
>"Dimitrios" <musurgio@otenet.gr> wrote:
>>
>>Hi,
>>Well this guy is willing to help us out with whatever benefits will arrise
>>for him by buying his plugin...
>>Note that his plugin has a discount until 31 of January , around 46-47
$
>>final price.
>>WE HAVE TO SHOW our appreciation on developers like him as we can ask for
>>further Paris support, like maybe wdm drivers ???
>>NOW he asks for some input from us.
>>Here is what he wrote on his last email...
>>To be flexible enough it is certainly possible to choose a much larger
latency
>>buffer, but consider this: A buffer consumes memory, e.g. 65536 samples
>need
>>262144 bytes per channel (each sample is 32 bit floating point for VST).
>>If you run e.g. 48 (stereo?)-tracks with 48 instances of FaderWorks you
>need
>>48 * 2 * 262144 bytes = 25 MB of memory. Should be no problem for today's
>>computers, but some users have Win98, so I'm not sure if RAM memory could
>>be an issue. If not, I would suggest about 132000 samples as upper limit
>>(needs about 1 MB per FaderWorks instance). What do you (or others) think
>>about it?
>>
>>
>>
>>
>
|
|
|
|
|
|
| Re: Author of Vertex needs some input from us to improve !! [message #78800 is a reply to message #78799] |
Mon, 22 January 2007 09:02 |
Dimitrios
Messages: 1056
Registered: August 2005
|
Senior Member |
|
|
Dear Gene,
The latency is determined on the plugins we put...
It does not matter if the highest possible will be 120000 samples when we
use maximum of two uad1 plugins per track, meaning you can use 2 uad1 plugins
across all your audiotracks if you have many uad cards for a total of 32768
samples if you use FXpansion wrapper or 8192 if you use Chainer wrapper !!
Even with chainer if you go up to 4 uad1 plugins in a row on a single track
,which is mostly unusual the toatl latency of the system with chainer will
be 16384 !!!
Well with fxpansion is 4 times 16384.
I am excited ...
Note that for NON UAD1 card users like me (I sold them :)) we can use all
these eds compressors with lookahead and nolimit with lookahead and compensate
across all submixes for latency !
Also note that waves ren series introduces 64 samples.
T-racks great plugins the same 64.
Also we can compensate for the difference beetween eds cards ,14 samples
and 2 for each thereafter in case you have more than 16 phase related audio
tracks when recording...
I really love that.
I opened 64 instances of vertex with no cpyu load !
Very very light !
Regards,
Dimitrios
"Gene Lennon" <glennon@NOSPmyrealbox.com> wrote:
>
>"Dimitrios" <musurgio@otenet.gr> wrote:
>>
>>Here is what the author wrote about his latency addon for vertex..!!
>>Track 1 has a latency of 16384 samples. The same is true for track 2. As
>>track 1 and track 2 have the same latency they are already in sync, but
>all
>>other tracks (the remaining 46 tracks) have to be delayed by 16384 samples,
>>not 32768.
>>
>>Take another example: Track 1 has a plug-in with 16384 samples of latency.
>>Track 2 has a plug-in with a latency of 8192 samples. What FaderWorks will
>>do is: Tracks 1 will pass through as it is, track 2 will be delayed by
8192
>>samples and all other tracks will be delayed by 16384 samples.
>>
>>What counts for the overall latency is the largest latency of any track.
>>You calculate the sum of latencies only for individual tracks when you
e.g.
>>put several uad1 behind on the same track.
>>
>>ISN'T that WHAT WE WANT ? !!!
>>If we don't buy this vertex we have to jump off Paris !! :)
>>Regards,
>>Dimitrios
>>
>>"Dimitrios" <musurgio@otenet.gr> wrote:
>>>
>
>
>That is what we want, but extremely high playback latencies will probably
>cause a delay between fader and mute actions and audible execution (and
also
>delay meters). I need to make automation decisions with effects in place,
>so extremely long delays could be problematic.
>Any chance we could pick from a list or assign a total delay?
>Gene
>This is exciting.
>
|
|
|
|
| Re: Author of Vertex needs some input from us to improve !! [message #78804 is a reply to message #78799] |
Mon, 22 January 2007 08:33 |
duncan
Messages: 123
Registered: November 2006
|
Senior Member |
|
|
Gene/Dimitrios:
Would it even be necessary to "pick from a list" or "assign" total
delay? Seems like the total delay would simply be as low (or as high)
as needed to compensate for the plugins used. (Unless I'm missing
something, which is always a possibility...)
As for me -- I'm still on 98, 512 ram -- could I run this thing right
now, just to compensate for EDS fx offsets, submix offsets, etc.?
-- interested in how this turns out -- thanks -- chas.
On 23 Jan 2007 02:54:04 +1000, "Gene Lennon"
<glennon@NOSPmyrealbox.com> wrote:
>
>"Dimitrios" <musurgio@otenet.gr> wrote:
>>
>>Here is what the author wrote about his latency addon for vertex..!!
>>Track 1 has a latency of 16384 samples. The same is true for track 2. As
>>track 1 and track 2 have the same latency they are already in sync, but
>all
>>other tracks (the remaining 46 tracks) have to be delayed by 16384 samples,
>>not 32768.
>>
>>Take another example: Track 1 has a plug-in with 16384 samples of latency.
>>Track 2 has a plug-in with a latency of 8192 samples. What FaderWorks will
>>do is: Tracks 1 will pass through as it is, track 2 will be delayed by 8192
>>samples and all other tracks will be delayed by 16384 samples.
>>
>>What counts for the overall latency is the largest latency of any track.
>>You calculate the sum of latencies only for individual tracks when you e.g.
>>put several uad1 behind on the same track.
>>
>>ISN'T that WHAT WE WANT ? !!!
>>If we don't buy this vertex we have to jump off Paris !! :)
>>Regards,
>>Dimitrios
>>
>>"Dimitrios" <musurgio@otenet.gr> wrote:
>>>
>
>
>That is what we want, but extremely high playback latencies will probably
>cause a delay between fader and mute actions and audible execution (and also
>delay meters). I need to make automation decisions with effects in place,
>so extremely long delays could be problematic.
>Any chance we could pick from a list or assign a total delay?
>Gene
>This is exciting.
|
|
|
|
| Re: Author of Vertex needs some input from us to improve !! [message #78806 is a reply to message #78800] |
Mon, 22 January 2007 08:45 |
Deej [4]
Messages: 1292
Registered: January 2007
|
Senior Member |
|
|
I will buy this later this afternoon. No kidding.
"Dimitrios" <musurgio@otenet.gr> wrote in message news:45b4e025$1@linux...
>
> Dear Gene,
> The latency is determined on the plugins we put...
> It does not matter if the highest possible will be 120000 samples when we
> use maximum of two uad1 plugins per track, meaning you can use 2 uad1
> plugins
> across all your audiotracks if you have many uad cards for a total of
> 32768
> samples if you use FXpansion wrapper or 8192 if you use Chainer wrapper !!
> Even with chainer if you go up to 4 uad1 plugins in a row on a single
> track
> ,which is mostly unusual the toatl latency of the system with chainer will
> be 16384 !!!
> Well with fxpansion is 4 times 16384.
> I am excited ...
> Note that for NON UAD1 card users like me (I sold them :)) we can use all
> these eds compressors with lookahead and nolimit with lookahead and
> compensate
> across all submixes for latency !
> Also note that waves ren series introduces 64 samples.
> T-racks great plugins the same 64.
> Also we can compensate for the difference beetween eds cards ,14 samples
> and 2 for each thereafter in case you have more than 16 phase related
> audio
> tracks when recording...
> I really love that.
> I opened 64 instances of vertex with no cpyu load !
> Very very light !
> Regards,
> Dimitrios
>
> "Gene Lennon" <glennon@NOSPmyrealbox.com> wrote:
>>
>>"Dimitrios" <musurgio@otenet.gr> wrote:
>>>
>>>Here is what the author wrote about his latency addon for vertex..!!
>>>Track 1 has a latency of 16384 samples. The same is true for track 2. As
>>>track 1 and track 2 have the same latency they are already in sync, but
>>all
>>>other tracks (the remaining 46 tracks) have to be delayed by 16384
>>>samples,
>>>not 32768.
>>>
>>>Take another example: Track 1 has a plug-in with 16384 samples of
>>>latency.
>>>Track 2 has a plug-in with a latency of 8192 samples. What FaderWorks
>>>will
>>>do is: Tracks 1 will pass through as it is, track 2 will be delayed by
> 8192
>>>samples and all other tracks will be delayed by 16384 samples.
>>>
>>>What counts for the overall latency is the largest latency of any track.
>>>You calculate the sum of latencies only for individual tracks when you
> e.g.
>>>put several uad1 behind on the same track.
>>>
>>>ISN'T that WHAT WE WANT ? !!!
>>>If we don't buy this vertex we have to jump off Paris !! :)
>>>Regards,
>>>Dimitrios
>>>
>>>"Dimitrios" <musurgio@otenet.gr> wrote:
>>>>
>>
>>
>>That is what we want, but extremely high playback latencies will probably
>>cause a delay between fader and mute actions and audible execution (and
> also
>>delay meters). I need to make automation decisions with effects in place,
>>so extremely long delays could be problematic.
>>Any chance we could pick from a list or assign a total delay?
>>Gene
>>This is exciting.
>>
>
|
|
|
|
| Re: Author of Vertex needs some input from us to improve !! [message #78807 is a reply to message #78804] |
Mon, 22 January 2007 10:25 |
Dimitrios
Messages: 1056
Registered: August 2005
|
Senior Member |
|
|
Well there is no pick from the list thing.
If you read all the posts you will understand that the latency is due to
the amount you manually type on a ceratin vertex instance vst plugin.
so if you put a 64 samples latent vst plugin you just type 64 and all other
audio tracks get delayed that amount !
The author just asks how much would be the maximum possible latency needed
because the 132000 maximum (only maximum if you will ever reach that ) the
author suggests uses 1 mb memory per vertex instance , so for 32 audio tracks
with vertex 32mb will be needed, for 64 paris audio tracks with vertex 64
mb will be needed.
I aggree with the author's 132000 samples as maximum ,if you will ever reach
that I say again.
Normally you would never pass 1000 without uad1 plugins...
Regards,
Dimitrios
Chas. Duncan <duncan5199ATsbcglobalDOTnet@> wrote:
>
>Gene/Dimitrios:
>
>Would it even be necessary to "pick from a list" or "assign" total
>delay? Seems like the total delay would simply be as low (or as high)
>as needed to compensate for the plugins used. (Unless I'm missing
>something, which is always a possibility...)
>
>As for me -- I'm still on 98, 512 ram -- could I run this thing right
>now, just to compensate for EDS fx offsets, submix offsets, etc.?
>
>-- interested in how this turns out -- thanks -- chas.
>
>
>On 23 Jan 2007 02:54:04 +1000, "Gene Lennon"
><glennon@NOSPmyrealbox.com> wrote:
>
>>
>>"Dimitrios" <musurgio@otenet.gr> wrote:
>>>
>>>Here is what the author wrote about his latency addon for vertex..!!
>>>Track 1 has a latency of 16384 samples. The same is true for track 2.
As
>>>track 1 and track 2 have the same latency they are already in sync, but
>>all
>>>other tracks (the remaining 46 tracks) have to be delayed by 16384 samples,
>>>not 32768.
>>>
>>>Take another example: Track 1 has a plug-in with 16384 samples of latency.
>>>Track 2 has a plug-in with a latency of 8192 samples. What FaderWorks
will
>>>do is: Tracks 1 will pass through as it is, track 2 will be delayed by
8192
>>>samples and all other tracks will be delayed by 16384 samples.
>>>
>>>What counts for the overall latency is the largest latency of any track.
>>>You calculate the sum of latencies only for individual tracks when you
e.g.
>>>put several uad1 behind on the same track.
>>>
>>>ISN'T that WHAT WE WANT ? !!!
>>>If we don't buy this vertex we have to jump off Paris !! :)
>>>Regards,
>>>Dimitrios
>>>
>>>"Dimitrios" <musurgio@otenet.gr> wrote:
>>>>
>>
>>
>>That is what we want, but extremely high playback latencies will probably
>>cause a delay between fader and mute actions and audible execution (and
also
>>delay meters). I need to make automation decisions with effects in place,
>>so extremely long delays could be problematic.
>>Any chance we could pick from a list or assign a total delay?
>>Gene
>>This is exciting.
>
|
|
|
|
| Re: Author of Vertex needs some input from us to improve !! [message #78809 is a reply to message #78806] |
Mon, 22 January 2007 10:32 |
Dimitrios musurgioote
Messages: 2
Registered: January 2007
|
Junior Member |
|
|
Great DJ,
This is the best answer to his kind efforts to even hear our cries for support
!
He is laready planning the vertex update without even knowing if Paris people
will support him and his plugin.
I am very excited that a clever "manual" latency compensator will be usable
for parisians.
We just have to make a big latency table accessible to everyone where every
know plugin must be listed .
I will contribute for sure in this list.
DJ 132000 samples as maximum is enouph for you ?
It needs to be configured from the beginning of the writting of vertex update.
Regards,
Dimitrios
"DJ" <www.aarrrrggghhh!!!.com> wrote:
>I will buy this later this afternoon. No kidding.
>
>"Dimitrios" <musurgio@otenet.gr> wrote in message news:45b4e025$1@linux...
>>
>> Dear Gene,
>> The latency is determined on the plugins we put...
>> It does not matter if the highest possible will be 120000 samples when
we
>> use maximum of two uad1 plugins per track, meaning you can use 2 uad1
>> plugins
>> across all your audiotracks if you have many uad cards for a total of
>> 32768
>> samples if you use FXpansion wrapper or 8192 if you use Chainer wrapper
!!
>> Even with chainer if you go up to 4 uad1 plugins in a row on a single
>> track
>> ,which is mostly unusual the toatl latency of the system with chainer
will
>> be 16384 !!!
>> Well with fxpansion is 4 times 16384.
>> I am excited ...
>> Note that for NON UAD1 card users like me (I sold them :)) we can use
all
>> these eds compressors with lookahead and nolimit with lookahead and
>> compensate
>> across all submixes for latency !
>> Also note that waves ren series introduces 64 samples.
>> T-racks great plugins the same 64.
>> Also we can compensate for the difference beetween eds cards ,14 samples
>> and 2 for each thereafter in case you have more than 16 phase related
>> audio
>> tracks when recording...
>> I really love that.
>> I opened 64 instances of vertex with no cpyu load !
>> Very very light !
>> Regards,
>> Dimitrios
>>
>> "Gene Lennon" <glennon@NOSPmyrealbox.com> wrote:
>>>
>>>"Dimitrios" <musurgio@otenet.gr> wrote:
>>>>
>>>>Here is what the author wrote about his latency addon for vertex..!!
>>>>Track 1 has a latency of 16384 samples. The same is true for track 2.
As
>>>>track 1 and track 2 have the same latency they are already in sync, but
>>>all
>>>>other tracks (the remaining 46 tracks) have to be delayed by 16384
>>>>samples,
>>>>not 32768.
>>>>
>>>>Take another example: Track 1 has a plug-in with 16384 samples of
>>>>latency.
>>>>Track 2 has a plug-in with a latency of 8192 samples. What FaderWorks
>>>>will
>>>>do is: Tracks 1 will pass through as it is, track 2 will be delayed by
>> 8192
>>>>samples and all other tracks will be delayed by 16384 samples.
>>>>
>>>>What counts for the overall latency is the largest latency of any track.
>>>>You calculate the sum of latencies only for individual tracks when you
>> e.g.
>>>>put several uad1 behind on the same track.
>>>>
>>>>ISN'T that WHAT WE WANT ? !!!
>>>>If we don't buy this vertex we have to jump off Paris !! :)
>>>>Regards,
>>>>Dimitrios
>>>>
>>>>"Dimitrios" <musurgio@otenet.gr> wrote:
>>>>>
>>>
>>>
>>>That is what we want, but extremely high playback latencies will probably
>>>cause a delay between fader and mute actions and audible execution (and
>> also
>>>delay meters). I need to make automation decisions with effects in place,
>>>so extremely long delays could be problematic.
>>>Any chance we could pick from a list or assign a total delay?
>>>Gene
>>>This is exciting.
>>>
>>
>
>
|
|
|
|
| Re: Author of Vertex needs some input from us to improve !! [message #78833 is a reply to message #78809] |
Mon, 22 January 2007 13:37 |
Deej [4]
Messages: 1292
Registered: January 2007
|
Senior Member |
|
|
Dimitrios,
If I need more than 4 x UAD-1 plugins on any track, then I need to retrack
the audio source anyway. As far as outside projects are concerned, if I need
to polish a turd, it's going to require something other than UAD-1
plugs..........something like Melodyne, Autotune, etc. and these aren't as
processor intensive as the UAD-1 plugins anyway.
Regards,
DJ
<Dimitrios musurgio#otenet.gr> wrote in message news:45b4f522@linux...
>
> Great DJ,
> This is the best answer to his kind efforts to even hear our cries for
> support
> !
> He is laready planning the vertex update without even knowing if Paris
> people
> will support him and his plugin.
> I am very excited that a clever "manual" latency compensator will be
> usable
> for parisians.
> We just have to make a big latency table accessible to everyone where
> every
> know plugin must be listed .
> I will contribute for sure in this list.
> DJ 132000 samples as maximum is enouph for you ?
> It needs to be configured from the beginning of the writting of vertex
> update.
> Regards,
> Dimitrios
>
> "DJ" <www.aarrrrggghhh!!!.com> wrote:
>>I will buy this later this afternoon. No kidding.
>>
>>"Dimitrios" <musurgio@otenet.gr> wrote in message news:45b4e025$1@linux...
>>>
>>> Dear Gene,
>>> The latency is determined on the plugins we put...
>>> It does not matter if the highest possible will be 120000 samples when
> we
>>> use maximum of two uad1 plugins per track, meaning you can use 2 uad1
>
>>> plugins
>>> across all your audiotracks if you have many uad cards for a total of
>
>>> 32768
>>> samples if you use FXpansion wrapper or 8192 if you use Chainer wrapper
> !!
>>> Even with chainer if you go up to 4 uad1 plugins in a row on a single
>
>>> track
>>> ,which is mostly unusual the toatl latency of the system with chainer
> will
>>> be 16384 !!!
>>> Well with fxpansion is 4 times 16384.
>>> I am excited ...
>>> Note that for NON UAD1 card users like me (I sold them :)) we can use
> all
>>> these eds compressors with lookahead and nolimit with lookahead and
>>> compensate
>>> across all submixes for latency !
>>> Also note that waves ren series introduces 64 samples.
>>> T-racks great plugins the same 64.
>>> Also we can compensate for the difference beetween eds cards ,14 samples
>>> and 2 for each thereafter in case you have more than 16 phase related
>
>>> audio
>>> tracks when recording...
>>> I really love that.
>>> I opened 64 instances of vertex with no cpyu load !
>>> Very very light !
>>> Regards,
>>> Dimitrios
>>>
>>> "Gene Lennon" <glennon@NOSPmyrealbox.com> wrote:
>>>>
>>>>"Dimitrios" <musurgio@otenet.gr> wrote:
>>>>>
>>>>>Here is what the author wrote about his latency addon for vertex..!!
>>>>>Track 1 has a latency of 16384 samples. The same is true for track 2.
> As
>>>>>track 1 and track 2 have the same latency they are already in sync, but
>>>>all
>>>>>other tracks (the remaining 46 tracks) have to be delayed by 16384
>>>>>samples,
>>>>>not 32768.
>>>>>
>>>>>Take another example: Track 1 has a plug-in with 16384 samples of
>>>>>latency.
>>>>>Track 2 has a plug-in with a latency of 8192 samples. What FaderWorks
>
>>>>>will
>>>>>do is: Tracks 1 will pass through as it is, track 2 will be delayed by
>>> 8192
>>>>>samples and all other tracks will be delayed by 16384 samples.
>>>>>
>>>>>What counts for the overall latency is the largest latency of any
>>>>>track.
>>>>>You calculate the sum of latencies only for individual tracks when you
>>> e.g.
>>>>>put several uad1 behind on the same track.
>>>>>
>>>>>ISN'T that WHAT WE WANT ? !!!
>>>>>If we don't buy this vertex we have to jump off Paris !! :)
>>>>>Regards,
>>>>>Dimitrios
>>>>>
>>>>>"Dimitrios" <musurgio@otenet.gr> wrote:
>>>>>>
>>>>
>>>>
>>>>That is what we want, but extremely high playback latencies will
>>>>probably
>>>>cause a delay between fader and mute actions and audible execution (and
>>> also
>>>>delay meters). I need to make automation decisions with effects in
>>>>place,
>>>>so extremely long delays could be problematic.
>>>>Any chance we could pick from a list or assign a total delay?
>>>>Gene
>>>>This is exciting.
>>>>
>>>
>>
>>
>
|
|
|
|
| Re: Author of Vertex needs some input from us to improve !! [message #78836 is a reply to message #78809] |
Mon, 22 January 2007 14:08 |
Deej [4]
Messages: 1292
Registered: January 2007
|
Senior Member |
|
|
DJ 132000 samples as maximum is enouph for you ?
Yes. That is more than enough for me personally. Money is now in same
vicinity as mouth. The software has been purchased.
Thanks,
;o)
<Dimitrios musurgio#otenet.gr> wrote in message news:45b4f522@linux...
>
> Great DJ,
> This is the best answer to his kind efforts to even hear our cries for
> support
> !
> He is laready planning the vertex update without even knowing if Paris
> people
> will support him and his plugin.
> I am very excited that a clever "manual" latency compensator will be
> usable
> for parisians.
> We just have to make a big latency table accessible to everyone where
> every
> know plugin must be listed .
> I will contribute for sure in this list.
> DJ 132000 samples as maximum is enouph for you ?
> It needs to be configured from the beginning of the writting of vertex
> update.
> Regards,
> Dimitrios
>
> "DJ" <www.aarrrrggghhh!!!.com> wrote:
>>I will buy this later this afternoon. No kidding.
>>
>>"Dimitrios" <musurgio@otenet.gr> wrote in message news:45b4e025$1@linux...
>>>
>>> Dear Gene,
>>> The latency is determined on the plugins we put...
>>> It does not matter if the highest possible will be 120000 samples when
> we
>>> use maximum of two uad1 plugins per track, meaning you can use 2 uad1
>
>>> plugins
>>> across all your audiotracks if you have many uad cards for a total of
>
>>> 32768
>>> samples if you use FXpansion wrapper or 8192 if you use Chainer wrapper
> !!
>>> Even with chainer if you go up to 4 uad1 plugins in a row on a single
>
>>> track
>>> ,which is mostly unusual the toatl latency of the system with chainer
> will
>>> be 16384 !!!
>>> Well with fxpansion is 4 times 16384.
>>> I am excited ...
>>> Note that for NON UAD1 card users like me (I sold them :)) we can use
> all
>>> these eds compressors with lookahead and nolimit with lookahead and
>>> compensate
>>> across all submixes for latency !
>>> Also note that waves ren series introduces 64 samples.
>>> T-racks great plugins the same 64.
>>> Also we can compensate for the difference beetween eds cards ,14 samples
>>> and 2 for each thereafter in case you have more than 16 phase related
>
>>> audio
>>> tracks when recording...
>>> I really love that.
>>> I opened 64 instances of vertex with no cpyu load !
>>> Very very light !
>>> Regards,
>>> Dimitrios
>>>
>>> "Gene Lennon" <glennon@NOSPmyrealbox.com> wrote:
>>>>
>>>>"Dimitrios" <musurgio@otenet.gr> wrote:
>>>>>
>>>>>Here is what the author wrote about his latency addon for vertex..!!
>>>>>Track 1 has a latency of 16384 samples. The same is true for track 2.
> As
>>>>>track 1 and track 2 have the same latency they are already in sync, but
>>>>all
>>>>>other tracks (the remaining 46 tracks) have to be delayed by 16384
>>>>>samples,
>>>>>not 32768.
>>>>>
>>>>>Take another example: Track 1 has a plug-in with 16384 samples of
>>>>>latency.
>>>>>Track 2 has a plug-in with a latency of 8192 samples. What FaderWorks
>
>>>>>will
>>>>>do is: Tracks 1 will pass through as it is, track 2 will be delayed by
>>> 8192
>>>>>samples and all other tracks will be delayed by 16384 samples.
>>>>>
>>>>>What counts for the overall latency is the largest latency of any
>>>>>track.
>>>>>You calculate the sum of latencies only for individual tracks when you
>>> e.g.
>>>>>put several uad1 behind on the same track.
>>>>>
>>>>>ISN'T that WHAT WE WANT ? !!!
>>>>>If we don't buy this vertex we have to jump off Paris !! :)
>>>>>Regards,
>>>>>Dimitrios
>>>>>
>>>>>"Dimitrios" <musurgio@otenet.gr> wrote:
>>>>>>
>>>>
>>>>
>>>>That is what we want, but extremely high playback latencies will
>>>>probably
>>>>cause a delay between fader and mute actions and audible execution (and
>>> also
>>>>delay meters). I need to make automation decisions with effects in
>>>>place,
>>>>so extremely long delays could be problematic.
>>>>Any chance we could pick from a list or assign a total delay?
>>>>Gene
>>>>This is exciting.
>>>>
>>>
>>
>>
>
|
|
|
|
| Re: Author of Vertex needs some input from us to improve !! [message #78852 is a reply to message #78807] |
Mon, 22 January 2007 19:33 |
duncan
Messages: 123
Registered: November 2006
|
Senior Member |
|
|
OK, that's understood then -- max latency not an issue. Cool. And I
had an email exchange with the developer today regarding 98 -- he says
it shouldn't be a problem and encouraged me to try the demo. Which
I'll do, as soon as I'm done with this batch of mixes I'm busy with
right now (don't want to throw *anything* new into this system until
this job is done). But, if he gets this "manual latency" compensator
gizmo working, I'll buy just for that and for the extra solo and mute
capability.
-- thanks for keeping on top of these developments -- much appreciated
-- chas.
On 23 Jan 2007 04:25:42 +1000, "Dimitrios" <musurgio@otenet.gr> wrote:
>
>Well there is no pick from the list thing.
>If you read all the posts you will understand that the latency is due to
>the amount you manually type on a ceratin vertex instance vst plugin.
>so if you put a 64 samples latent vst plugin you just type 64 and all other
>audio tracks get delayed that amount !
>The author just asks how much would be the maximum possible latency needed
>because the 132000 maximum (only maximum if you will ever reach that ) the
>author suggests uses 1 mb memory per vertex instance , so for 32 audio tracks
>with vertex 32mb will be needed, for 64 paris audio tracks with vertex 64
>mb will be needed.
>I aggree with the author's 132000 samples as maximum ,if you will ever reach
>that I say again.
>Normally you would never pass 1000 without uad1 plugins...
>Regards,
>Dimitrios
>Chas. Duncan <duncan5199ATsbcglobalDOTnet@> wrote:
>>
>>Gene/Dimitrios:
>>
>>Would it even be necessary to "pick from a list" or "assign" total
>>delay? Seems like the total delay would simply be as low (or as high)
>>as needed to compensate for the plugins used. (Unless I'm missing
>>something, which is always a possibility...)
>>
>>As for me -- I'm still on 98, 512 ram -- could I run this thing right
>>now, just to compensate for EDS fx offsets, submix offsets, etc.?
>>
>>-- interested in how this turns out -- thanks -- chas.
>>
>>
>>On 23 Jan 2007 02:54:04 +1000, "Gene Lennon"
>><glennon@NOSPmyrealbox.com> wrote:
>>
>>>
>>>"Dimitrios" <musurgio@otenet.gr> wrote:
>>>>
>>>>Here is what the author wrote about his latency addon for vertex..!!
>>>>Track 1 has a latency of 16384 samples. The same is true for track 2.
>As
>>>>track 1 and track 2 have the same latency they are already in sync, but
>>>all
>>>>other tracks (the remaining 46 tracks) have to be delayed by 16384 samples,
>>>>not 32768.
>>>>
>>>>Take another example: Track 1 has a plug-in with 16384 samples of latency.
>>>>Track 2 has a plug-in with a latency of 8192 samples. What FaderWorks
>will
>>>>do is: Tracks 1 will pass through as it is, track 2 will be delayed by
>8192
>>>>samples and all other tracks will be delayed by 16384 samples.
>>>>
>>>>What counts for the overall latency is the largest latency of any track.
>>>>You calculate the sum of latencies only for individual tracks when you
>e.g.
>>>>put several uad1 behind on the same track.
>>>>
>>>>ISN'T that WHAT WE WANT ? !!!
>>>>If we don't buy this vertex we have to jump off Paris !! :)
>>>>Regards,
>>>>Dimitrios
>>>>
>>>>"Dimitrios" <musurgio@otenet.gr> wrote:
>>>>>
>>>
>>>
>>>That is what we want, but extremely high playback latencies will probably
>>>cause a delay between fader and mute actions and audible execution (and
>also
>>>delay meters). I need to make automation decisions with effects in place,
>>>so extremely long delays could be problematic.
>>>Any chance we could pick from a list or assign a total delay?
>>>Gene
>>>This is exciting.
>>
|
|
|
|
| Re: Author of Vertex needs some input from us to improve !! [message #78863 is a reply to message #78852] |
Tue, 23 January 2007 07:03 |
Phil Aiken
Messages: 62
Registered: February 2008
|
Member |
|
|
I am a little unclear still....
For arguments sake, let's say I have a 32 track project on 2 cards, with
plugins of various latencies...track 1 has 16384 ms. track 10 has 16376 ms,
and track 20 (track 4 of submix 2) has 256 ms latency. What would be the
procedure with Vertex to even all tracks out across the project?
Chas. Duncan <duncan5199ATsbcglobalDOTnet@> wrote:
>OK, that's understood then -- max latency not an issue. Cool. And I
>had an email exchange with the developer today regarding 98 -- he says
>it shouldn't be a problem and encouraged me to try the demo. Which
>I'll do, as soon as I'm done with this batch of mixes I'm busy with
>right now (don't want to throw *anything* new into this system until
>this job is done). But, if he gets this "manual latency" compensator
>gizmo working, I'll buy just for that and for the extra solo and mute
>capability.
>
>-- thanks for keeping on top of these developments -- much appreciated
>-- chas.
>
>On 23 Jan 2007 04:25:42 +1000, "Dimitrios" <musurgio@otenet.gr> wrote:
>
>>
>>Well there is no pick from the list thing.
>>If you read all the posts you will understand that the latency is due to
>>the amount you manually type on a ceratin vertex instance vst plugin.
>>so if you put a 64 samples latent vst plugin you just type 64 and all other
>>audio tracks get delayed that amount !
>>The author just asks how much would be the maximum possible latency needed
>>because the 132000 maximum (only maximum if you will ever reach that )
the
>>author suggests uses 1 mb memory per vertex instance , so for 32 audio
tracks
>>with vertex 32mb will be needed, for 64 paris audio tracks with vertex
64
>>mb will be needed.
>>I aggree with the author's 132000 samples as maximum ,if you will ever
reach
>>that I say again.
>>Normally you would never pass 1000 without uad1 plugins...
>>Regards,
>>Dimitrios
>>Chas. Duncan <duncan5199ATsbcglobalDOTnet@> wrote:
>>>
>>>Gene/Dimitrios:
>>>
>>>Would it even be necessary to "pick from a list" or "assign" total
>>>delay? Seems like the total delay would simply be as low (or as high)
>>>as needed to compensate for the plugins used. (Unless I'm missing
>>>something, which is always a possibility...)
>>>
>>>As for me -- I'm still on 98, 512 ram -- could I run this thing right
>>>now, just to compensate for EDS fx offsets, submix offsets, etc.?
>>>
>>>-- interested in how this turns out -- thanks -- chas.
>>>
>>>
>>>On 23 Jan 2007 02:54:04 +1000, "Gene Lennon"
>>><glennon@NOSPmyrealbox.com> wrote:
>>>
>>>>
>>>>"Dimitrios" <musurgio@otenet.gr> wrote:
>>>>>
>>>>>Here is what the author wrote about his latency addon for vertex..!!
>>>>>Track 1 has a latency of 16384 samples. The same is true for track 2.
>>As
>>>>>track 1 and track 2 have the same latency they are already in sync,
but
>>>>all
>>>>>other tracks (the remaining 46 tracks) have to be delayed by 16384 samples,
>>>>>not 32768.
>>>>>
>>>>>Take another example: Track 1 has a plug-in with 16384 samples of latency.
>>>>>Track 2 has a plug-in with a latency of 8192 samples. What FaderWorks
>>will
>>>>>do is: Tracks 1 will pass through as it is, track 2 will be delayed
by
>>8192
>>>>>samples and all other tracks will be delayed by 16384 samples.
>>>>>
>>>>>What counts for the overall latency is the largest latency of any track.
>>>>>You calculate the sum of latencies only for individual tracks when you
>>e.g.
>>>>>put several uad1 behind on the same track.
>>>>>
>>>>>ISN'T that WHAT WE WANT ? !!!
>>>>>If we don't buy this vertex we have to jump off Paris !! :)
>>>>>Regards,
>>>>>Dimitrios
>>>>>
>>>>>"Dimitrios" <musurgio@otenet.gr> wrote:
>>>>>>
>>>>
>>>>
>>>>That is what we want, but extremely high playback latencies will probably
>>>>cause a delay between fader and mute actions and audible execution (and
>>also
>>>>delay meters). I need to make automation decisions with effects in place,
>>>>so extremely long delays could be problematic.
>>>>Any chance we could pick from a list or assign a total delay?
>>>>Gene
>>>>This is exciting.
>>>
>
|
|
|
|
| Re: Author of Vertex needs some input from us to improve !! [message #78866 is a reply to message #78863] |
Tue, 23 January 2007 08:02 |
Dimitrios
Messages: 1056
Registered: August 2005
|
Senior Member |
|
|
Hi Phil,
According to the author you just have to type the latency on the vertex instance
you are putting a plugin and then vertex takes care of the rest !!
Here is how it will work...
You open vertex dsp on every audio track on your 2 card system.
You can save that as a template for further projects.
Now lets say you open on track 1 a plugin that has 16384 samples latency
, you just type 16384 on that vertex's instance of audio track 1 and vertex
takes care of the rest 31 audio tracks to get alligned.
Now you put a plugin on track 10 which has a latency of 16376 ,you just type
that number on track's 10 vertex instance and so vertex takes care of the
rest 31 audio tracks again meaning that it delays all other tracks in a way
that all have this 16376 latency, menaing again that it just adds 12 samples
to track 10 and lives all other 31 audio tracks with same 16384 latency !!
Isn't that clever ??
Now you say you put a plugin on track 4 of submix 2 that has a latency of
256 ms (you have here to translate it to samples as to have it on your latency
list) this is 1290 samples ,plus the 12 samples submix 2 introduces (Paris
feature) you will have a total of 1302.
Just type 1302 on track's 4 vertex instance and vertex will take this very
same track to the 16384 latency situation !
This very clever delay compensator DOES not add the latencies but uses the
biggest amoung all instances and alligns the rest !
I hope this helps.
Regards,
Dimitrios
"Phil Aiken" <asdf@asdf.sdf> wrote:
>
>
>I am a little unclear still....
> For arguments sake, let's say I have a 32 track project on 2 cards, with
>plugins of various latencies...track 1 has 16384 ms. track 10 has 16376
ms,
>and track 20 (track 4 of submix 2) has 256 ms latency. What would be the
>procedure with Vertex to even all tracks out across the project?
>
>
>
>
>Chas. Duncan <duncan5199ATsbcglobalDOTnet@> wrote:
>>OK, that's understood then -- max latency not an issue. Cool. And I
>>had an email exchange with the developer today regarding 98 -- he says
>>it shouldn't be a problem and encouraged me to try the demo. Which
>>I'll do, as soon as I'm done with this batch of mixes I'm busy with
>>right now (don't want to throw *anything* new into this system until
>>this job is done). But, if he gets this "manual latency" compensator
>>gizmo working, I'll buy just for that and for the extra solo and mute
>>capability.
>>
>>-- thanks for keeping on top of these developments -- much appreciated
>>-- chas.
>>
>>On 23 Jan 2007 04:25:42 +1000, "Dimitrios" <musurgio@otenet.gr> wrote:
>>
>>>
>>>Well there is no pick from the list thing.
>>>If you read all the posts you will understand that the latency is due
to
>>>the amount you manually type on a ceratin vertex instance vst plugin.
>>>so if you put a 64 samples latent vst plugin you just type 64
and all other
>>>audio tracks get delayed that amount !
>>>The author just asks how much would be the maximum possible latency needed
>>>because the 132000 maximum (only maximum if you will ever reach that )
>the
>>>author suggests uses 1 mb memory per vertex instance , so for 32 audio
>tracks
>>>with vertex 32mb will be needed, for 64 paris audio tracks with vertex
>64
>>>mb will be needed.
>>>I aggree with the author's 132000 samples as maximum ,if you will ever
>reach
>>>that I say again.
>>>Normally you would never pass 1000 without uad1 plugins...
>>>Regards,
>>>Dimitrios
>>>Chas. Duncan <duncan5199ATsbcglobalDOTnet@> wrote:
>>>>
>>>>Gene/Dimitrios:
>>>>
>>>>Would it even be necessary to "pick from a list" or "assign" total
>>>>delay? Seems like the total delay would simply be as low (or as high)
>>>>as needed to compensate for the plugins used. (Unless I'm missing
>>>>something, which is always a possibility...)
>>>>
>>>>As for me -- I'm still on 98, 512 ram -- could I run this thing right
>>>>now, just to compensate for EDS fx offsets, submix offsets, etc.?
>>>>
>>>>-- interested in how this turns out -- thanks -- chas.
>>>>
>>>>
>>>>On 23 Jan 2007 02:54:04 +1000, "Gene Lennon"
>>>><glennon@NOSPmyrealbox.com> wrote:
>>>>
>>>>>
>>>>>"Dimitrios" <musurgio@otenet.gr> wrote:
>>>>>>
>>>>>>Here is what the author wrote about his latency addon for vertex..!!
>>>>>>Track 1 has a latency of 16384 samples. The same is true for track
2.
>>>As
>>>>>>track 1 and track 2 have the same latency they are already in sync,
>but
>>>>>all
>>>>>>other tracks (the remaining 46 tracks) have to be delayed by 16384
samples,
>>>>>>not 32768.
>>>>>>
>>>>>>Take another example: Track 1 has a plug-in with 16384 samples of latency.
>>>>>>Track 2 has a plug-in with a latency of 8192 samples. What FaderWorks
>>>will
>>>>>>do is: Tracks 1 will pass through as it is, track 2 will be delayed
>by
>>>8192
>>>>>>samples and all other tracks will be delayed by 16384 samples.
>>>>>>
>>>>>>What counts for the overall latency is the largest latency of any track.
>>>>>>You calculate the sum of latencies only for individual tracks when
you
>>>e.g.
>>>>>>put several uad1 behind on the same track.
>>>>>>
>>>>>>ISN'T that WHAT WE WANT ? !!!
>>>>>>If we don't buy this vertex we have to jump off Paris !! :)
>>>>>>Regards,
>>>>>>Dimitrios
>>>>>>
>>>>>>"Dimitrios" <musurgio@otenet.gr> wrote:
>>>>>>>
>>>>>
>>>>>
>>>>>That is what we want, but extremely high playback latencies will probably
>>>>>cause a delay between fader and mute actions and audible execution (and
>>>also
>>>>>delay meters). I need to make automation decisions with effects in place,
>>>>>so extremely long delays could be problematic.
>>>>>Any chance we could pick from a list or assign a total delay?
>>>>>Gene
>>>>>This is exciting.
>>>>
>>
>
|
|
|
|
| Re: Author of Vertex needs some input from us to improve !! [message #78867 is a reply to message #78866] |
Tue, 23 January 2007 08:04 |
Dimitrios
Messages: 1056
Registered: August 2005
|
Senior Member |
|
|
Dear Phil,
You probably have read that I said allign all 31 audio tracks to 16376 I
meant to 16384 which already was so, so it just adds 12 samples to track
10.
Regards,
Dimitrios
"Dimitrios" <musurgio@otenet.gr> wrote:
>
>Hi Phil,
>According to the author you just have to type the latency on the vertex
instance
>you are putting a plugin and then vertex takes care of the rest !!
>Here is how it will work...
>You open vertex dsp on every audio track on your 2 card system.
>You can save that as a template for further projects.
>Now lets say you open on track 1 a plugin that has 16384 samples latency
>, you just type 16384 on that vertex's instance of audio track 1 and vertex
>takes care of the rest 31 audio tracks to get alligned.
>Now you put a plugin on track 10 which has a latency of 16376 ,you just
type
>that number on track's 10 vertex instance and so vertex takes care of the
>rest 31 audio tracks again meaning that it delays all other tracks in a
way
>that all have this 16376 latency, menaing again that it just adds 12 samples
>to track 10 and lives all other 31 audio tracks with same 16384 latency
!!
>Isn't that clever ??
>Now you say you put a plugin on track 4 of submix 2 that has a latency of
>256 ms (you have here to translate it to samples as to have it on your latency
>list) this is 1290 samples ,plus the 12 samples submix 2 introduces (Paris
>feature) you will have a total of 1302.
>Just type 1302 on track's 4 vertex instance and vertex will take this very
>same track to the 16384 latency situation !
>This very clever delay compensator DOES not add the latencies but uses the
>biggest amoung all instances and alligns the rest !
>I hope this helps.
>Regards,
>Dimitrios
>
>"Phil Aiken" <asdf@asdf.sdf> wrote:
>>
>>
>>I am a little unclear still....
>> For arguments sake, let's say I have a 32 track project on 2 cards, with
>>plugins of various latencies...track 1 has 16384 ms. track 10 has 16376
>ms,
>>and track 20 (track 4 of submix 2) has 256 ms latency. What would be the
>>procedure with Vertex to even all tracks out across the project?
>>
>>
>>
>>
>>Chas. Duncan <duncan5199ATsbcglobalDOTnet@> wrote:
>>>OK, that's understood then -- max latency not an issue. Cool. And I
>>>had an email exchange with the developer today regarding 98 -- he says
>>>it shouldn't be a problem and encouraged me to try the demo. Which
>>>I'll do, as soon as I'm done with this batch of mixes I'm busy with
>>>right now (don't want to throw *anything* new into this system until
>>>this job is done). But, if he gets this "manual latency" compensator
>>>gizmo working, I'll buy just for that and for the extra solo and mute
>>>capability.
>>>
>>>-- thanks for keeping on top of these developments -- much appreciated
>>>-- chas.
>>>
>>>On 23 Jan 2007 04:25:42 +1000, "Dimitrios" <musurgio@otenet.gr> wrote:
>>>
>>>>
>>>>Well there is no pick from the list thing.
>>>>If you read all the posts you will understand that the latency is due
>to
>>>>the amount you manually type on a ceratin vertex instance vst plugin.
>>>>so if you put a 64 samples latent vst plugin you just type 64
>and all other
>>>>audio tracks get delayed that amount !
>>>>The author just asks how much would be the maximum possible latency needed
>>>>because the 132000 maximum (only maximum if you will ever reach that
)
>>the
>>>>author suggests uses 1 mb memory per vertex instance , so for 32 audio
>>tracks
>>>>with vertex 32mb will be needed, for 64 paris audio tracks with vertex
>>64
>>>>mb will be needed.
>>>>I aggree with the author's 132000 samples as maximum ,if you will ever
>>reach
>>>>that I say again.
>>>>Normally you would never pass 1000 without uad1 plugins...
>>>>Regards,
>>>>Dimitrios
>>>>Chas. Duncan <duncan5199ATsbcglobalDOTnet@> wrote:
>>>>>
>>>>>Gene/Dimitrios:
>>>>>
>>>>>Would it even be necessary to "pick from a list" or "assign" total
>>>>>delay? Seems like the total delay would simply be as low (or as high)
>>>>>as needed to compensate for the plugins used. (Unless I'm missing
>>>>>something, which is always a possibility...)
>>>>>
>>>>>As for me -- I'm still on 98, 512 ram -- could I run this thing right
>>>>>now, just to compensate for EDS fx offsets, submix offsets, etc.?
>>>>>
>>>>>-- interested in how this turns out -- thanks -- chas.
>>>>>
>>>>>
>>>>>On 23 Jan 2007 02:54:04 +1000, "Gene Lennon"
>>>>><glennon@NOSPmyrealbox.com> wrote:
>>>>>
>>>>>>
>>>>>>"Dimitrios" <musurgio@otenet.gr> wrote:
>>>>>>>
>>>>>>>Here is what the author wrote about his latency addon for vertex..!!
>>>>>>>Track 1 has a latency of 16384 samples. The same is true for track
>2.
>>>>As
>>>>>>>track 1 and track 2 have the same latency they are already in sync,
>>but
>>>>>>all
>>>>>>>other tracks (the remaining 46 tracks) have to be delayed by 16384
>samples,
>>>>>>>not 32768.
>>>>>>>
>>>>>>>Take another example: Track 1 has a plug-in with 16384 samples of
latency.
>>>>>>>Track 2 has a plug-in with a latency of 8192 samples. What FaderWorks
>>>>will
>>>>>>>do is: Tracks 1 will pass through as it is, track 2 will be delayed
>>by
>>>>8192
>>>>>>>samples and all other tracks will be delayed by 16384 samples.
>>>>>>>
>>>>>>>What counts for the overall latency is the largest latency of any
track.
>>>>>>>You calculate the sum of latencies only for individual tracks when
>you
>>>>e.g.
>>>>>>>put several uad1 behind on the same track.
>>>>>>>
>>>>>>>ISN'T that WHAT WE WANT ? !!!
>>>>>>>If we don't buy this vertex we have to jump off Paris !! :)
>>>>>>>Regards,
>>>>>>>Dimitrios
>>>>>>>
>>>>>>>"Dimitrios" <musurgio@otenet.gr> wrote:
>>>>>>>>
>>>>>>
>>>>>>
>>>>>>That is what we want, but extremely high playback latencies will probably
>>>>>>cause a delay between fader and mute actions and audible execution
(and
>>>>also
>>>>>>delay meters). I need to make automation decisions with effects in
place,
>>>>>>so extremely long delays could be problematic.
>>>>>>Any chance we could pick from a list or assign a total delay?
>>>>>>Gene
>>>>>>This is exciting.
>>>>>
>>>
>>
>
|
|
|
|
| Re: Author of Vertex needs some input from us to improve !! [message #78870 is a reply to message #78867] |
Tue, 23 January 2007 09:34 |
Chris Lang
Messages: 91
Registered: March 2007
|
Member |
|
|
That is awesome. Buying it now...
Chris
"Dimitrios" <musurgio@otenet.gr> wrote:
>
>Dear Phil,
>You probably have read that I said allign all 31 audio tracks to 16376 I
>meant to 16384 which already was so, so it just adds 12 samples to track
>10.
>Regards,
>Dimitrios
>
>"Dimitrios" <musurgio@otenet.gr> wrote:
>>
>>Hi Phil,
>>According to the author you just have to type the latency on the vertex
>instance
>>you are putting a plugin and then vertex takes care of the rest !!
>>Here is how it will work...
>>You open vertex dsp on every audio track on your 2 card system.
>>You can save that as a template for further projects.
>>Now lets say you open on track 1 a plugin that has 16384 samples latency
>>, you just type 16384 on that vertex's instance of audio track 1 and vertex
>>takes care of the rest 31 audio tracks to get alligned.
>>Now you put a plugin on track 10 which has a latency of 16376 ,you just
>type
>>that number on track's 10 vertex instance and so vertex takes care of the
>>rest 31 audio tracks again meaning that it delays all other tracks in a
>way
>>that all have this 16376 latency, menaing again that it just adds 12 samples
>>to track 10 and lives all other 31 audio tracks with same 16384 latency
>!!
>>Isn't that clever ??
>>Now you say you put a plugin on track 4 of submix 2 that has a latency
of
>>256 ms (you have here to translate it to samples as to have it on your
latency
>>list) this is 1290 samples ,plus the 12 samples submix 2 introduces (Paris
>>feature) you will have a total of 1302.
>>Just type 1302 on track's 4 vertex instance and vertex will take this very
>>same track to the 16384 latency situation !
>>This very clever delay compensator DOES not add the latencies but uses
the
>>biggest amoung all instances and alligns the rest !
>>I hope this helps.
>>Regards,
>>Dimitrios
>>
>>"Phil Aiken" <asdf@asdf.sdf> wrote:
>>>
>>>
>>>I am a little unclear still....
>>> For arguments sake, let's say I have a 32 track project on 2 cards, with
>>>plugins of various latencies...track 1 has 16384 ms. track 10 has 16376
>>ms,
>>>and track 20 (track 4 of submix 2) has 256 ms latency. What would be the
>>>procedure with Vertex to even all tracks out across the project?
>>>
>>>
>>>
>>>
>>>Chas. Duncan <duncan5199ATsbcglobalDOTnet@> wrote:
>>>>OK, that's understood then -- max latency not an issue. Cool. And I
>>>>had an email exchange with the developer today regarding 98 -- he says
>>>>it shouldn't be a problem and encouraged me to try the demo. Which
>>>>I'll do, as soon as I'm done with this batch of mixes I'm busy with
>>>>right now (don't want to throw *anything* new into this system until
>>>>this job is done). But, if he gets this "manual latency" compensator
>>>>gizmo working, I'll buy just for that and for the extra solo and mute
>>>>capability.
>>>>
>>>>-- thanks for keeping on top of these developments -- much appreciated
>>>>-- chas.
>>>>
>>>>On 23 Jan 2007 04:25:42 +1000, "Dimitrios" <musurgio@otenet.gr> wrote:
>>>>
>>>>>
>>>>>Well there is no pick from the list thing.
>>>>>If you read all the posts you will understand that the latency is due
>>to
>>>>>the amount you manually type on a ceratin vertex instance vst plugin.
>>>>>so if you put a 64 samples latent vst plugin you just type 64
>>and all other
>>>>>audio tracks get delayed that amount !
>>>>>The author just asks how much would be the maximum possible latency
needed
>>>>>because the 132000 maximum (only maximum if you will ever reach that
>)
>>>the
>>>>>author suggests uses 1 mb memory per vertex instance , so for 32 audio
>>>tracks
>>>>>with vertex 32mb will be needed, for 64 paris audio tracks with vertex
>>>64
>>>>>mb will be needed.
>>>>>I aggree with the author's 132000 samples as maximum ,if you will ever
>>>reach
>>>>>that I say again.
>>>>>Normally you would never pass 1000 without uad1 plugins...
>>>>>Regards,
>>>>>Dimitrios
>>>>>Chas. Duncan <duncan5199ATsbcglobalDOTnet@> wrote:
>>>>>>
>>>>>>Gene/Dimitrios:
>>>>>>
>>>>>>Would it even be necessary to "pick from a list" or "assign" total
>>>>>>delay? Seems like the total delay would simply be as low (or as high)
>>>>>>as needed to compensate for the plugins used. (Unless I'm missing
>>>>>>something, which is always a possibility...)
>>>>>>
>>>>>>As for me -- I'm still on 98, 512 ram -- could I run this thing right
>>>>>>now, just to compensate for EDS fx offsets, submix offsets, etc.?
>>>>>>
>>>>>>-- interested in how this turns out -- thanks -- chas.
>>>>>>
>>>>>>
>>>>>>On 23 Jan 2007 02:54:04 +1000, "Gene Lennon"
>>>>>><glennon@NOSPmyrealbox.com> wrote:
>>>>>>
>>>>>>>
>>>>>>>"Dimitrios" <musurgio@otenet.gr> wrote:
>>>>>>>>
>>>>>>>>Here is what the author wrote about his latency addon for vertex..!!
>>>>>>>>Track 1 has a latency of 16384 samples. The same is true for track
>>2.
>>>>>As
>>>>>>>>track 1 and track 2 have the same latency they are already in sync,
>>>but
>>>>>>>all
>>>>>>>>other tracks (the remaining 46 tracks) have to be delayed by 16384
>>samples,
>>>>>>>>not 32768.
>>>>>>>>
>>>>>>>>Take another example: Track 1 has a plug-in with 16384 samples of
>latency.
>>>>>>>>Track 2 has a plug-in with a latency of 8192 samples. What FaderWorks
>>>>>will
>>>>>>>>do is: Tracks 1 will pass through as it is, track 2 will be delayed
>>>by
>>>>>8192
>>>>>>>>samples and all other tracks will be delayed by 16384 samples.
>>>>>>>>
>>>>>>>>What counts for the overall latency is the largest latency of any
>track.
>>>>>>>>You calculate the sum of latencies only for individual tracks when
>>you
>>>>>e.g.
>>>>>>>>put several uad1 behind on the same track.
>>>>>>>>
>>>>>>>>ISN'T that WHAT WE WANT ? !!!
>>>>>>>>If we don't buy this vertex we have to jump off Paris !! :)
>>>>>>>>Regards,
>>>>>>>>Dimitrios
>>>>>>>>
>>>>>>>>"Dimitrios" <musurgio@otenet.gr> wrote:
>>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>That is what we want, but extremely high playback latencies will probably
>>>>>>>cause a delay between fader and mute actions and audible execution
>(and
>>>>>also
>>>>>>>delay meters). I need to make automation decisions with effects in
>place,
>>>>>>>so extremely long delays could be problematic.
>>>>>>>Any chance we could pick from a list or assign a total delay?
>>>>>>>Gene
>>>>>>>This is exciting.
>>>>>>
>>>>
>>>
>>
>
|
|
|
|
| Re: Author of Vertex needs some input from us to improve !! [message #78871 is a reply to message #78870] |
Tue, 23 January 2007 09:42 |
Dimitrios
Messages: 1056
Registered: August 2005
|
Senior Member |
|
|
Great Chris !
Please email him too saying that you are a Paris users that has been informed
about the latency compensator !
Regards,
Dimitrios
"Chris Lang" <yo@yo.yo> wrote:
>
>That is awesome. Buying it now...
>
>Chris
>
>
>"Dimitrios" <musurgio@otenet.gr> wrote:
>>
>>Dear Phil,
>>You probably have read that I said allign all 31 audio tracks to 16376
I
>>meant to 16384 which already was so, so it just adds 12 samples to track
>>10.
>>Regards,
>>Dimitrios
>>
>>"Dimitrios" <musurgio@otenet.gr> wrote:
>>>
>>>Hi Phil,
>>>According to the author you just have to type the latency on the vertex
>>instance
>>>you are putting a plugin and then vertex takes care of the rest !!
>>>Here is how it will work...
>>>You open vertex dsp on every audio track on your 2 card system.
>>>You can save that as a template for further projects.
>>>Now lets say you open on track 1 a plugin that has 16384 samples latency
>>>, you just type 16384 on that vertex's instance of audio track 1 and vertex
>>>takes care of the rest 31 audio tracks to get alligned.
>>>Now you put a plugin on track 10 which has a latency of 16376 ,you just
>>type
>>>that number on track's 10 vertex instance and so vertex takes care of
the
>>>rest 31 audio tracks again meaning that it delays all other tracks in
a
>>way
>>>that all have this 16376 latency, menaing again that it just adds 12 samples
>>>to track 10 and lives all other 31 audio tracks with same 16384 latency
>>!!
>>>Isn't that clever ??
>>>Now you say you put a plugin on track 4 of submix 2 that has a latency
>of
>>>256 ms (you have here to translate it to samples as to have it on your
>latency
>>>list) this is 1290 samples ,plus the 12 samples submix 2 introduces (Paris
>>>feature) you will have a total of 1302.
>>>Just type 1302 on track's 4 vertex instance and vertex will take this
very
>>>same track to the 16384 latency situation !
>>>This very clever delay compensator DOES not add the latencies but uses
>the
>>>biggest amoung all instances and alligns the rest !
>>>I hope this helps.
>>>Regards,
>>>Dimitrios
>>>
>>>"Phil Aiken" <asdf@asdf.sdf> wrote:
>>>>
>>>>
>>>>I am a little unclear still....
>>>> For arguments sake, let's say I have a 32 track project on 2 cards,
with
>>>>plugins of various latencies...track 1 has 16384 ms. track 10 has 16376
>>>ms,
>>>>and track 20 (track 4 of submix 2) has 256 ms latency. What would be
the
>>>>procedure with Vertex to even all tracks out across the project?
>>>>
>>>>
>>>>
>>>>
>>>>Chas. Duncan <duncan5199ATsbcglobalDOTnet@> wrote:
>>>>>OK, that's understood then -- max latency not an issue. Cool. And
I
>>>>>had an email exchange with the developer today regarding 98 -- he says
>>>>>it shouldn't be a problem and encouraged me to try the demo. Which
>>>>>I'll do, as soon as I'm done with this batch of mixes I'm busy with
>>>>>right now (don't want to throw *anything* new into this system until
>>>>>this job is done). But, if he gets this "manual latency" compensator
>>>>>gizmo working, I'll buy just for that and for the extra solo and mute
>>>>>capability.
>>>>>
>>>>>-- thanks for keeping on top of these developments -- much appreciated
>>>>>-- chas.
>>>>>
>>>>>On 23 Jan 2007 04:25:42 +1000, "Dimitrios" <musurgio@otenet.gr> wrote:
>>>>>
>>>>>>
>>>>>>Well there is no pick from the list thing.
>>>>>>If you read all the posts you will understand that the latency is due
>>>to
>>>>>>the amount you manually type on a ceratin vertex instance vst plugin.
>>>>>>so if you put a 64 samples latent vst plugin you just type 64
>>>and all other
>>>>>>audio tracks get delayed that amount !
>>>>>>The author just asks how much would be the maximum possible latency
>needed
>>>>>>because the 132000 maximum (only maximum if you will ever reach that
>>)
>>>>the
>>>>>>author suggests uses 1 mb memory per vertex instance , so for 32 audio
>>>>tracks
>>>>>>with vertex 32mb will be needed, for 64 paris audio tracks with vertex
>>>>64
>>>>>>mb will be needed.
>>>>>>I aggree with the author's 132000 samples as maximum ,if you will ever
>>>>reach
>>>>>>that I say again.
>>>>>>Normally you would never pass 1000 without uad1 plugins...
>>>>>>Regards,
>>>>>>Dimitrios
>>>>>>Chas. Duncan <duncan5199ATsbcglobalDOTnet@> wrote:
>>>>>>>
>>>>>>>Gene/Dimitrios:
>>>>>>>
>>>>>>>Would it even be necessary to "pick from a list" or "assign" total
>>>>>>>delay? Seems like the total delay would simply be as low (or as high)
>>>>>>>as needed to compensate for the plugins used. (Unless I'm missing
>>>>>>>something, which is always a possibility...)
>>>>>>>
>>>>>>>As for me -- I'm still on 98, 512 ram -- could I run this thing right
>>>>>>>now, just to compensate for EDS fx offsets, submix offsets, etc.?
>>>>>>>
>>>>>>>-- interested in how this turns out -- thanks -- chas.
>>>>>>>
>>>>>>>
>>>>>>>On 23 Jan 2007 02:54:04 +1000, "Gene Lennon"
>>>>>>><glennon@NOSPmyrealbox.com> wrote:
>>>>>>>
>>>>>>>>
>>>>>>>>"Dimitrios" <musurgio@otenet.gr> wrote:
>>>>>>>>>
>>>>>>>>>Here is what the author wrote about his latency addon for vertex..!!
>>>>>>>>>Track 1 has a latency of 16384 samples. The same is true for track
>>>2.
>>>>>>As
>>>>>>>>>track 1 and track 2 have the same latency they are already in sync,
>>>>but
>>>>>>>>all
>>>>>>>>>other tracks (the remaining 46 tracks) have to be delayed by 16384
>>>samples,
>>>>>>>>>not 32768.
>>>>>>>>>
>>>>>>>>>Take another example: Track 1 has a plug-in with 16384 samples of
>>latency.
>>>>>>>>>Track 2 has a plug-in with a latency of 8192 samples. What FaderWorks
>>>>>>will
>>>>>>>>>do is: Tracks 1 will pass through as it is, track 2 will be delayed
>>>>by
>>>>>>8192
>>>>>>>>>samples and all other tracks will be delayed by 16384 samples.
>>>>>>>>>
>>>>>>>>>What counts for the overall latency is the largest latency of any
>>track.
>>>>>>>>>You calculate the sum of latencies only for individual tracks when
>>>you
>>>>>>e.g.
>>>>>>>>>put several uad1 behind on the same track.
>>>>>>>>>
>>>>>>>>>ISN'T that WHAT WE WANT ? !!!
>>>>>>>>>If we don't buy this vertex we have to jump off Paris !! :)
>>>>>>>>>Regards,
>>>>>>>>>Dimitrios
>>>>>>>>>
>>>>>>>>>"Dimitrios" <musurgio@otenet.gr> wrote:
>>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>That is what we want, but extremely high playback latencies will
probably
>>>>>>>>cause a delay between fader and mute actions and audible execution
>>(and
>>>>>>also
>>>>>>>>delay meters). I need to make automation decisions with effects in
>>place,
>>>>>>>>so extremely long delays could be problematic.
>>>>>>>>Any chance we could pick from a list or assign a total delay?
>>>>>>>>Gene
>>>>>>>>This is exciting.
>>>>>>>
>>>>>
>>>>
>>>
>>
>
|
|
|
|
| Re: Author of Vertex needs some input from us to improve !! [message #78872 is a reply to message #78871] |
Tue, 23 January 2007 09:25 |
Jeff hoover
Messages: 22
Registered: January 2007
|
Junior Member |
|
|
So is the compensator already in the product, or do we have a timeline
for it?
Hoov
Dimitrios wrote:
> Great Chris !
> Please email him too saying that you are a Paris users that has been informed
> about the latency compensator !
> Regards,
> Dimitrios
>
> "Chris Lang" <yo@yo.yo> wrote:
>
>>That is awesome. Buying it now...
>>
>>Chris
>>
>>
>>"Dimitrios" <musurgio@otenet.gr> wrote:
>>
>>>Dear Phil,
>>>You probably have read that I said allign all 31 audio tracks to 16376
>
> I
>
>>>meant to 16384 which already was so, so it just adds 12 samples to track
>>>10.
>>>Regards,
>>>Dimitrios
>>>
>>>"Dimitrios" <musurgio@otenet.gr> wrote:
>>>
>>>>Hi Phil,
>>>>According to the author you just have to type the latency on the vertex
>>>
>>>instance
>>>
>>>>you are putting a plugin and then vertex takes care of the rest !!
>>>>Here is how it will work...
>>>>You open vertex dsp on every audio track on your 2 card system.
>>>>You can save that as a template for further projects.
>>>>Now lets say you open on track 1 a plugin that has 16384 samples latency
>>>>, you just type 16384 on that vertex's instance of audio track 1 and vertex
>>>>takes care of the rest 31 audio tracks to get alligned.
>>>>Now you put a plugin on track 10 which has a latency of 16376 ,you just
>>>
>>>type
>>>
>>>>that number on track's 10 vertex instance and so vertex takes care of
>
> the
>
>>>>rest 31 audio tracks again meaning that it delays all other tracks in
>
> a
>
>>>way
>>>
>>>>that all have this 16376 latency, menaing again that it just adds 12 samples
>>>>to track 10 and lives all other 31 audio tracks with same 16384 latency
>>>
>>>!!
>>>
>>>>Isn't that clever ??
>>>>Now you say you put a plugin on track 4 of submix 2 that has a latency
>>
>>of
>>
>>>>256 ms (you have here to translate it to samples as to have it on your
>>
>>latency
>>
>>>>list) this is 1290 samples ,plus the 12 samples submix 2 introduces (Paris
>>>>feature) you will have a total of 1302.
>>>>Just type 1302 on track's 4 vertex instance and vertex will take this
>
> very
>
>>>>same track to the 16384 latency situation !
>>>>This very clever delay compensator DOES not add the latencies but uses
>>
>>the
>>
>>>>biggest amoung all instances and alligns the rest !
>>>>I hope this helps.
>>>>Regards,
>>>>Dimitrios
>>>>
>>>>"Phil Aiken" <asdf@asdf.sdf> wrote:
>>>>
>>>>>
>>>>>I am a little unclear still....
>>>>>For arguments sake, let's say I have a 32 track project on 2 cards,
>
> with
>
>>>>>plugins of various latencies...track 1 has 16384 ms. track 10 has 16376
>>>>
>>>>ms,
>>>>
>>>>>and track 20 (track 4 of submix 2) has 256 ms latency. What would be
>
> the
>
>>>>>procedure with Vertex to even all tracks out across the project?
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>Chas. Duncan <duncan5199ATsbcglobalDOTnet@> wrote:
>>>>>
>>>>>>OK, that's understood then -- max latency not an issue. Cool. And
>
> I
>
>>>>>>had an email exchange with the developer today regarding 98 -- he says
>>>>>>it shouldn't be a problem and encouraged me to try the demo. Which
>>>>>>I'll do, as soon as I'm done with this batch of mixes I'm busy with
>>>>>>right now (don't want to throw *anything* new into this system until
>>>>>>this job is done). But, if he gets this "manual latency" compensator
>>>>>>gizmo working, I'll buy just for that and for the extra solo and mute
>>>>>>capability.
>>>>>>
>>>>>>-- thanks for keeping on top of these developments -- much appreciated
>>>>>>-- chas.
>>>>>>
>>>>>>On 23 Jan 2007 04:25:42 +1000, "Dimitrios" <musurgio@otenet.gr> wrote:
>>>>>>
>>>>>>
>>>>>>>Well there is no pick from the list thing.
>>>>>>>If you read all the posts you will understand that the latency is due
>>>>
>>>>to
>>>>
>>>>>>>the amount you manually type on a ceratin vertex instance vst plugin.
>>>>>>>so if you put a 64 samples latent vst plugin you just type 64
>>>>
>>>>and all other
>>>>
>>>>>>>audio tracks get delayed that amount !
>>>>>>>The author just asks how much would be the maximum possible latency
>>
>>needed
>>
>>>>>>>because the 132000 maximum (only maximum if you will ever reach that
>>>
>>>)
>>>
>>>>>the
>>>>>
>>>>>>>author suggests uses 1 mb memory per vertex instance , so for 32 audio
>>>>>
>>>>>tracks
>>>>>
>>>>>>>with vertex 32mb will be needed, for 64 paris audio tracks with vertex
>>>>>
>>>>>64
>>>>>
>>>>>>>mb will be needed.
>>>>>>>I aggree with the author's 132000 samples as maximum ,if you will ever
>>>>>
>>>>>reach
>>>>>
>>>>>>>that I say again.
>>>>>>>Normally you would never pass 1000 without uad1 plugins...
>>>>>>>Regards,
>>>>>>>Dimitrios
>>>>>>>Chas. Duncan <duncan5199ATsbcglobalDOTnet@> wrote:
>>>>>>>
>>>>>>>>Gene/Dimitrios:
>>>>>>>>
>>>>>>>>Would it even be necessary to "pick from a list" or "assign" total
>>>>>>>>delay? Seems like the total delay would simply be as low (or as high)
>>>>>>>>as needed to compensate for the plugins used. (Unless I'm missing
>>>>>>>>something, which is always a possibility...)
>>>>>>>>
>>>>>>>>As for me -- I'm still on 98, 512 ram -- could I run this thing right
>>>>>>>>now, just to compensate for EDS fx offsets, submix offsets, etc.?
>>>>>>>>
>>>>>>>>-- interested in how this turns out -- thanks -- chas.
>>>>>>>>
>>>>>>>>
>>>>>>>>On 23 Jan 2007 02:54:04 +1000, "Gene Lennon"
>>>>>>>><glennon@NOSPmyrealbox.com> wrote:
>>>>>>>>
>>>>>>>>
>>>>>>>>>"Dimitrios" <musurgio@otenet.gr> wrote:
>>>>>>>>>
>>>>>>>>>>Here is what the author wrote about his latency addon for vertex..!!
>>>>>>>>>>Track 1 has a latency of 16384 samples. The same is true for track
>>>>
>>>>2.
>>>>
>>>>>>>As
>>>>>>>
>>>>>>>>>>track 1 and track 2 have the same latency they are already in sync,
>>>>>
>>>>>but
>>>>>
>>>>>>>>>all
>>>>>>>>>
>>>>>>>>>>other tracks (the remaining 46 tracks) have to be delayed by 16384
>>>>
>>>>samples,
>>>>
>>>>>>>>>>not 32768.
>>>>>>>>>>
>>>>>>>>>>Take another example: Track 1 has a plug-in with 16384 samples of
>>>
>>>latency.
>>>
>>>>>>>>>>Track 2 has a plug-in with a latency of 8192 samples. What FaderWorks
>>>>>>>
>>>>>>>will
>>>>>>>
>>>>>>>>>>do is: Tracks 1 will pass through as it is, track 2 will be delayed
>>>>>
>>>>>by
>>>>>
>>>>>>>8192
>>>>>>>
>>>>>>>>>>samples and all other tracks will be delayed by 16384 samples.
>>>>>>>>>>
>>>>>>>>>>What counts for the overall latency is the largest latency of any
>>>
>>>track.
>>>
>>>>>>>>>>You calculate the sum of latencies only for individual tracks when
>>>>
>>>>you
>>>>
>>>>>>>e.g.
>>>>>>>
>>>>>>>>>>put several uad1 behind on the same track.
>>>>>>>>>>
>>>>>>>>>>ISN'T that WHAT WE WANT ? !!!
>>>>>>>>>>If we don't buy this vertex we have to jump off Paris !! :)
>>>>>>>>>>Regards,
>>>>>>>>>>Dimitrios
>>>>>>>>>>
>>>>>>>>>>"Dimitrios" <musurgio@otenet.gr> wrote:
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>That is what we want, but extremely high playback latencies will
>
> probably
>
>>>>>>>>>cause a delay between fader and mute actions and audible execution
>>>
>>>(and
>>>
>>>>>>>also
>>>>>>>
>>>>>>>>>delay meters). I need to make automation decisions with effects in
>>>
>>>place,
>>>
>>>>>>>>>so extremely long delays could be problematic.
>>>>>>>>>Any chance we could pick from a list or assign a total delay?
>>>>>>>>>Gene
>>>>>>>>>This is exciting.
>>>>>>>>
>
|
|
|
|
| Re: Author of Vertex needs some input from us to improve !! [message #78873 is a reply to message #78872] |
Tue, 23 January 2007 10:49 |
Dimitrios
Messages: 1056
Registered: August 2005
|
Senior Member |
|
|
Dear Jeff,
This is what makes this author a nice guy ...
I proposed it to him to be added on his vertex and he reacted in a very positive
way improving my idea and promissing a couple of weeks for this update to
his vertex that will include the latency compensator.
Hope this helps.
Regards,
Dimitrios
Jeff hoover <jkhoover@excite-DOT-com> wrote:
>So is the compensator already in the product, or do we have a timeline
>for it?
>
>Hoov
>
>Dimitrios wrote:
>> Great Chris !
>> Please email him too saying that you are a Paris users that has been informed
>> about the latency compensator !
>> Regards,
>> Dimitrios
>>
>> "Chris Lang" <yo@yo.yo> wrote:
>>
>>>That is awesome. Buying it now...
>>>
>>>Chris
>>>
>>>
>>>"Dimitrios" <musurgio@otenet.gr> wrote:
>>>
>>>>Dear Phil,
>>>>You probably have read that I said allign all 31 audio tracks to 16376
>>
>> I
>>
>>>>meant to 16384 which already was so, so it just adds 12 samples to track
>>>>10.
>>>>Regards,
>>>>Dimitrios
>>>>
>>>>"Dimitrios" <musurgio@otenet.gr> wrote:
>>>>
>>>>>Hi Phil,
>>>>>According to the author you just have to type the latency on the vertex
>>>>
>>>>instance
>>>>
>>>>>you are putting a plugin and then vertex takes care of the rest !!
>>>>>Here is how it will work...
>>>>>You open vertex dsp on every audio track on your 2 card system.
>>>>>You can save that as a template for further projects.
>>>>>Now lets say you open on track 1 a plugin that has 16384 samples latency
>>>>>, you just type 16384 on that vertex's instance of audio track 1 and
vertex
>>>>>takes care of the rest 31 audio tracks to get alligned.
>>>>>Now you put a plugin on track 10 which has a latency of 16376 ,you just
>>>>
>>>>type
>>>>
>>>>>that number on track's 10 vertex instance and so vertex takes care of
>>
>> the
>>
>>>>>rest 31 audio tracks again meaning that it delays all other tracks in
>>
>> a
>>
>>>>way
>>>>
>>>>>that all have this 16376 latency, menaing again that it just adds 12
samples
>>>>>to track 10 and lives all other 31 audio tracks with same 16384 latency
>>>>
>>>>!!
>>>>
>>>>>Isn't that clever ??
>>>>>Now you say you put a plugin on track 4 of submix 2 that has a latency
>>>
>>>of
>>>
>>>>>256 ms (you have here to translate it to samples as to have it on your
>>>
>>>latency
>>>
>>>>>list) this is 1290 samples ,plus the 12 samples submix 2 introduces
(Paris
>>>>>feature) you will have a total of 1302.
>>>>>Just type 1302 on track's 4 vertex instance and vertex will take this
>>
>> very
>>
>>>>>same track to the 16384 latency situation !
>>>>>This very clever delay compensator DOES not add the latencies but uses
>>>
>>>the
>>>
>>>>>biggest amoung all instances and alligns the rest !
>>>>>I hope this helps.
>>>>>Regards,
>>>>>Dimitrios
>>>>>
>>>>>"Phil Aiken" <asdf@asdf.sdf> wrote:
>>>>>
>>>>>>
>>>>>>I am a little unclear still....
>>>>>>For arguments sake, let's say I have a 32 track project on 2 cards,
>>
>> with
>>
>>>>>>plugins of various latencies...track 1 has 16384 ms. track 10 has 16376
>>>>>
>>>>>ms,
>>>>>
>>>>>>and track 20 (track 4 of submix 2) has 256 ms latency. What would be
>>
>> the
>>
>>>>>>procedure with Vertex to even all tracks out across the project?
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>Chas. Duncan <duncan5199ATsbcglobalDOTnet@> wrote:
>>>>>>
>>>>>>>OK, that's understood then -- max latency not an issue. Cool. And
>>
>> I
>>
>>>>>>>had an email exchange with the developer today regarding 98 -- he
says
>>>>>>>it shouldn't be a problem and encouraged me to try the demo. Which
>>>>>>>I'll do, as soon as I'm done with this batch of mixes I'm busy with
>>>>>>>right now (don't want to throw *anything* new into this system until
>>>>>>>this job is done). But, if he gets this "manual latency" compensator
>>>>>>>gizmo working, I'll buy just for that and for the extra solo and mute
>>>>>>>capability.
>>>>>>>
>>>>>>>-- thanks for keeping on top of these developments -- much appreciated
>>>>>>>-- chas.
>>>>>>>
>>>>>>>On 23 Jan 2007 04:25:42 +1000, "Dimitrios" <musurgio@otenet.gr> wrote:
>>>>>>>
>>>>>>>
>>>>>>>>Well there is no pick from the list thing.
>>>>>>>>If you read all the posts you will understand that the latency is
due
>>>>>
>>>>>to
>>>>>
>>>>>>>>the amount you manually type on a ceratin vertex instance vst plugin.
>>>>>>>>so if you put a 64 samples latent vst plugin you just type 64
>>>>>
>>>>>and all other
>>>>>
>>>>>>>>audio tracks get delayed that amount !
>>>>>>>>The author just asks how much would be the maximum possible latency
>>>
>>>needed
>>>
>>>>>>>>because the 132000 maximum (only maximum if you will ever reach that
>>>>
>>>>)
>>>>
>>>>>>the
>>>>>>
>>>>>>>>author suggests uses 1 mb memory per vertex instance , so for 32
audio
>>>>>>
>>>>>>tracks
>>>>>>
>>>>>>>>with vertex 32mb will be needed, for 64 paris audio tracks with vertex
>>>>>>
>>>>>>64
>>>>>>
>>>>>>>>mb will be needed.
>>>>>>>>I aggree with the author's 132000 samples as maximum ,if you will
ever
>>>>>>
>>>>>>reach
>>>>>>
>>>>>>>>that I say again.
>>>>>>>>Normally you would never pass 1000 without uad1 plugins...
>>>>>>>>Regards,
>>>>>>>>Dimitrios
>>>>>>>>Chas. Duncan <duncan5199ATsbcglobalDOTnet@> wrote:
>>>>>>>>
>>>>>>>>>Gene/Dimitrios:
>>>>>>>>>
>>>>>>>>>Would it even be necessary to "pick from a list" or "assign" total
>>>>>>>>>delay? Seems like the total delay would simply be as low (or as
high)
>>>>>>>>>as needed to compensate for the plugins used. (Unless I'm missing
>>>>>>>>>something, which is always a possibility...)
>>>>>>>>>
>>>>>>>>>As for me -- I'm still on 98, 512 ram -- could I run this thing
right
>>>>>>>>>now, just to compensate for EDS fx offsets, submix offsets, etc.?
>>>>>>>>>
>>>>>>>>>-- interested in how this turns out -- thanks -- chas.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>On 23 Jan 2007 02:54:04 +1000, "Gene Lennon"
>>>>>>>>><glennon@NOSPmyrealbox.com> wrote:
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>>"Dimitrios" <musurgio@otenet.gr> wrote:
>>>>>>>>>>
>>>>>>>>>>>Here is what the author wrote about his latency addon for vertex..!!
>>>>>>>>>>>Track 1 has a latency of 16384 samples. The same is true for track
>>>>>
>>>>>2.
>>>>>
>>>>>>>>As
>>>>>>>>
>>>>>>>>>>>track 1 and track 2 have the same latency they are already in
sync,
>>>>>>
>>>>>>but
>>>>>>
>>>>>>>>>>all
>>>>>>>>>>
>>>>>>>>>>>other tracks (the remaining 46 tracks) have to be delayed by 16384
>>>>>
>>>>>samples,
>>>>>
>>>>>>>>>>>not 32768.
>>>>>>>>>>>
>>>>>>>>>>>Take another example: Track 1 has a plug-in with 16384 samples
of
>>>>
>>>>latency.
>>>>
>>>>>>>>>>>Track 2 has a plug-in with a latency of 8192 samples. What FaderWorks
>>>>>>>>
>>>>>>>>will
>>>>>>>>
>>>>>>>>>>>do is: Tracks 1 will pass through as it is, track 2 will be delayed
>>>>>>
>>>>>>by
>>>>>>
>>>>>>>>8192
>>>>>>>>
>>>>>>>>>>>samples and all other tracks will be delayed by 16384 samples.
>>>>>>>>>>>
>>>>>>>>>>>What counts for the overall latency is the largest latency of
any
>>>>
>>>>track.
>>>>
>>>>>>>>>>>You calculate the sum of latencies only for individual tracks
when
>>>>>
>>>>>you
>>>>>
>>>>>>>>e.g.
>>>>>>>>
>>>>>>>>>>>put several uad1 behind on the same track.
>>>>>>>>>>>
>>>>>>>>>>>ISN'T that WHAT WE WANT ? !!!
>>>>>>>>>>>If we don't buy this vertex we have to jump off Paris !! :)
>>>>>>>>>>>Regards,
>>>>>>>>>>>Dimitrios
>>>>>>>>>>>
>>>>>>>>>>>"Dimitrios" <musurgio@otenet.gr> wrote:
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>That is what we want, but extremely high playback latencies will
>>
>> probably
>>
>>>>>>>>>>cause a delay between fader and mute actions and audible execution
>>>>
>>>>(and
>>>>
>>>>>>>>also
>>>>>>>>
>>>>>>>>>>delay meters). I need to make automation decisions with effects
in
>>>>
>>>>place,
>>>>
>>>>>>>>>>so extremely long delays could be problematic.
>>>>>>>>>>Any chance we could pick from a list or assign a total delay?
>>>>>>>>>>Gene
>>>>>>>>>>This is exciting.
>>>>>>>>>
>>
|
|
|
|
| Re: Author of Vertex needs some input from us to improve !! [message #78876 is a reply to message #78873] |
Tue, 23 January 2007 10:35 |
Tom Bruhl
Messages: 1368
Registered: June 2007
|
Senior Member |
|
|
This is a multi-part message in MIME format.
------=_NextPart_000_0054_01C73EF3.6183A160
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
A couple of weeks?!?! That's alot of latency.
Tom
"Dimitrios" <musurgio@otenet.gr> wrote in message =
news:45b64aaa$1@linux...
Dear Jeff,
This is what makes this author a nice guy ...
I proposed it to him to be added on his vertex and he reacted in a =
very positive
way improving my idea and promissing a couple of weeks for this update =
to
his vertex that will include the latency compensator.
Hope this helps.
Regards,
Dimitrios
Jeff hoover <jkhoover@excite-DOT-com> wrote:
>So is the compensator already in the product, or do we have a =
timeline=20
>for it?
>
>Hoov
>
>Dimitrios wrote:
>> Great Chris !
>> Please email him too saying that you are a Paris users that has =
been informed
>> about the latency compensator !
>> Regards,
>> Dimitrios
>>=20
>> "Chris Lang" <yo@yo.yo> wrote:
>>=20
>>>That is awesome. Buying it now...
>>>
>>>Chris
>>>
>>>
>>>"Dimitrios" <musurgio@otenet.gr> wrote:
>>>
>>>>Dear Phil,
>>>>You probably have read that I said allign all 31 audio tracks to =
16376
>>=20
>> I
>>=20
>>>>meant to 16384 which already was so, so it just adds 12 samples to =
track
>>>>10.
>>>>Regards,
>>>>Dimitrios
>>>>
>>>>"Dimitrios" <musurgio@otenet.gr> wrote:
>>>>
>>>>>Hi Phil,
>>>>>According to the author you just have to type the latency on the =
vertex
>>>>
>>>>instance
>>>>
>>>>>you are putting a plugin and then vertex takes care of the rest =
!!
>>>>>Here is how it will work...
>>>>>You open vertex dsp on every audio track on your 2 card system.
>>>>>You can save that as a template for further projects.
>>>>>Now lets say you open on track 1 a plugin that has 16384 samples =
latency
>>>>>, you just type 16384 on that vertex's instance of audio track 1 =
and
vertex
>>>>>takes care of the rest 31 audio tracks to get alligned.
>>>>>Now you put a plugin on track 10 which has a latency of 16376 =
,you just
>>>>
>>>>type
>>>>
>>>>>that number on track's 10 vertex instance and so vertex takes =
care of
>>=20
>> the
>>=20
>>>>>rest 31 audio tracks again meaning that it delays all other =
tracks in
>>=20
>> a
>>=20
>>>>way
>>>>
>>>>>that all have this 16376 latency, menaing again that it just adds =
12
samples
>>>>>to track 10 and lives all other 31 audio tracks with same 16384 =
latency
>>>>
>>>>!!
>>>>
>>>>>Isn't that clever ??
>>>>>Now you say you put a plugin on track 4 of submix 2 that has a =
latency
>>>
>>>of
>>>
>>>>>256 ms (you have here to translate it to samples as to have it on =
your
>>>
>>>latency
>>>
>>>>>list) this is 1290 samples ,plus the 12 samples submix 2 =
introduces
(Paris
>>>>>feature) you will have a total of 1302.
>>>>>Just type 1302 on track's 4 vertex instance and vertex will take =
this
>>=20
>> very
>>=20
>>>>>same track to the 16384 latency situation !
>>>>>This very clever delay compensator DOES not add the latencies but =
uses
>>>
>>>the
>>>
>>>>>biggest amoung all instances and alligns the rest !
>>>>>I hope this helps.
>>>>>Regards,
>>>>>Dimitrios
>>>>>
>>>>>"Phil Aiken" <asdf@asdf.sdf> wrote:
>>>>>
>>>>>>
>>>>>>I am a little unclear still....
>>>>>>For arguments sake, let's say I have a 32 track project on 2 =
cards,
>>=20
>> with
>>=20
>>>>>>plugins of various latencies...track 1 has 16384 ms. track 10 =
has 16376
>>>>>
>>>>>ms,
>>>>>
>>>>>>and track 20 (track 4 of submix 2) has 256 ms latency. What =
would be
>>=20
>> the
>>=20
>>>>>>procedure with Vertex to even all tracks out across the project?
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>Chas. Duncan <duncan5199ATsbcglobalDOTnet@> wrote:
>>>>>>
>>>>>>>OK, that's understood then -- max latency not an issue. Cool. =
And
>>=20
>> I
>>=20
>>>>>>>had an email exchange with the developer today regarding 98 -- =
he
says
>>>>>>>it shouldn't be a problem and encouraged me to try the demo. =
Which
>>>>>>>I'll do, as soon as I'm done with this batch of mixes I'm busy =
with
>>>>>>>right now (don't want to throw *anything* new into this system =
until
>>>>>>>this job is done). But, if he gets this "manual latency" =
compensator
>>>>>>>gizmo working, I'll buy just for that and for the extra solo =
and mute
>>>>>>>capability.
>>>>>>>
>>>>>>>-- thanks for keeping on top of these developments -- much =
appreciated
>>>>>>>-- chas.
>>>>>>>
>>>>>>>On 23 Jan 2007 04:25:42 +1000, "Dimitrios" <musurgio@otenet.gr> =
wrote:
>>>>>>>
>>>>>>>
>>>>>>>>Well there is no pick from the list thing.
>>>>>>>>If you read all the posts you will understand that the latency =
is
due
>>>>>
>>>>>to
>>>>>
>>>>>>>>the amount you manually type on a ceratin vertex instance vst =
plugin.
>>>>>>>>so if you put a 64 samples latent vst plugin you just type 64=20
>>>>>
>>>>>and all other
>>>>>
>>>>>>>>audio tracks get delayed that amount !
>>>>>>>>The author just asks how much would be the maximum possible =
latency
>>>
>>>needed
>>>
>>>>>>>>because the 132000 maximum (only maximum if you will ever =
reach that
>>>>
>>>>)
>>>>
>>>>>>the
>>>>>>
>>>>>>>>author suggests uses 1 mb memory per vertex instance , so for =
32
audio
>>>>>>
>>>>>>tracks
>>>>>>
>>>>>>>>with vertex 32mb will be needed, for 64 paris audio tracks =
with vertex
>>>>>>
>>>>>>64
>>>>>>
>>>>>>>>mb will be needed.
>>>>>>>>I aggree with the author's 132000 samples as maximum ,if you =
will
ever
>>>>>>
>>>>>>reach
>>>>>>
>>>>>>>>that I say again.
>>>>>>>>Normally you would never pass 1000 without uad1 plugins...
>>>>>>>>Regards,
>>>>>>>>Dimitrios
>>>>>>>>Chas. Duncan <duncan5199ATsbcglobalDOTnet@> wrote:
>>>>>>>>
>>>>>>>>>Gene/Dimitrios:
>>>>>>>>>
>>>>>>>>>Would it even be necessary to "pick from a list" or "assign" =
total
>>>>>>>>>delay? Seems like the total delay would simply be as low (or =
as
high)
>>>>>>>>>as needed to compensate for the plugins used. (Unless I'm =
missing
>>>>>>>>>something, which is always a possibility...)
>>>>>>>>>
>>>>>>>>>As for me -- I'm still on 98, 512 ram -- could I run this =
thing
right
>>>>>>>>>now, just to compensate for EDS fx offsets, submix offsets, =
etc.?
>>>>>>>>>
>>>>>>>>>-- interested in how this turns out -- thanks -- chas.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>On 23 Jan 2007 02:54:04 +1000, "Gene Lennon"
>>>>>>>>><glennon@NOSPmyrealbox.com> wrote:
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>>"Dimitrios" <musurgio@otenet.gr> wrote:
>>>>>>>>>>
>>>>>>>>>>>Here is what the author wrote about his latency addon for =
vertex..!!
>>>>>>>>>>>Track 1 has a latency of 16384 samples. The same is true =
for track
>>>>>
>>>>>2.
>>>>>
>>>>>>>>As
>>>>>>>>
>>>>>>>>>>>track 1 and track 2 have the same latency they are already =
in
sync,
>>>>>>
>>>>>>but
>>>>>>
>>>>>>>>>>all
>>>>>>>>>>
>>>>>>>>>>>other tracks (the remaining 46 tracks) have to be delayed =
by 16384
>>>>>
>>>>>samples,
>>>>>
>>>>>>>>>>>not 32768.
>>>>>>>>>>>
>>>>>>>>>>>Take another example: Track 1 has a plug-in with 16384 =
samples
of
>>>>
>>>>latency.
>>>>
>>>>>>>>>>>Track 2 has a plug-in with a latency of 8192 samples. What =
FaderWorks
>>>>>>>>
>>>>>>>>will
>>>>>>>>
>>>>>>>>>>>do is: Tracks 1 will pass through as it is, track 2 will be =
delayed
>>>>>>
>>>>>>by
>>>>>>
>>>>>>>>8192
>>>>>>>>
>>>>>>>>>>>samples and all other tracks will be delayed by 16384 =
samples.
>>>>>>>>>>>
>>>>>>>>>>>What counts for the overall latency is the largest latency =
of
any
>>>>
>>>>track.
>>>>
>>>>>>>>>>>You calculate the sum of latencies only for individual =
tracks
when
>>>>>
>>>>>you
>>>>>
>>>>>>>>e.g.
>>>>>>>>
>>>>>>>>>>>put several uad1 behind on the same track.
>>>>>>>>>>>
>>>>>>>>>>>ISN'T that WHAT WE WANT ? !!!
>>>>>>>>>>>If we don't buy this vertex we have to jump off Paris !! :)
>>>>>>>>>>>Regards,
>>>>>>>>>>>Dimitrios=20
>>>>>>>>>>>
>>>>>>>>>>>"Dimitrios" <musurgio@otenet.gr> wrote:
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>That is what we want, but extremely high playback latencies =
will
>>=20
>> probably
>>=20
>>>>>>>>>>cause a delay between fader and mute actions and audible =
execution
>>>>
>>>>(and
>>>>
>>>>>>>>also
>>>>>>>>
>>>>>>>>>>delay meters). I need to make automation decisions with =
effects
in
>>>>
>>>>place,
>>>>
>>>>>>>>>>so extremely long delays could be problematic.=20
>>>>>>>>>>Any chance we could pick from a list or assign a total =
delay?
>>>>>>>>>>Gene
>>>>>>>>>>This is exciting.
>>>>>>>>>
>>=20
I choose Polesoft Lockspam to fight spam, and you?
http://www.polesoft.com/refer.html
------=_NextPart_000_0054_01C73EF3.6183A160
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>A couple of weeks?!?! That's alot =
of=20
latency.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Tom</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV> </DIV>
<BLOCKQUOTE=20
style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; =
BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
<DIV>"Dimitrios" <<A=20
href=3D"mailto:musurgio@otenet.gr">musurgio@otenet.gr</A>> wrote in =
message=20
<A =
href=3D"news:45b64aaa$1@linux">news:45b64aaa$1@linux</A>...</DIV><BR>Dear=
=20
Jeff,<BR>This is what makes this author a nice guy ...<BR>I proposed =
it to him=20
to be added on his vertex and he reacted in a very positive<BR>way =
improving=20
my idea and promissing a couple of weeks for this update to<BR>his =
vertex that=20
will include the latency compensator.<BR>Hope this=20
helps.<BR>Regards,<BR>Dimitrios<BR>Jeff hoover <<A=20
=
href=3D"mailto:jkhoover@excite-DOT-com">jkhoover@excite-DOT-com</A>>=20
wrote:<BR>>So is the compensator already in the product, or do we =
have a=20
timeline <BR>>for it?<BR>><BR>>Hoov<BR>><BR>>Dimitrios=20
wrote:<BR>>> Great Chris !<BR>>> Please email him too =
saying that=20
you are a Paris users that has been informed<BR>>> about the =
latency=20
compensator !<BR>>> Regards,<BR>>> Dimitrios<BR>>>=20
<BR>>> "Chris Lang" <<A =
href=3D"mailto:yo@yo.yo">yo@yo.yo</A>>=20
wrote:<BR>>> <BR>>>>That is awesome. Buying it=20
=
now...<BR>>>><BR>>>>Chris <BR>>>><BR>>>&g=
t;<BR>>>>"Dimitrios"=20
<<A href=3D"mailto:musurgio@otenet.gr">musurgio@otenet.gr</A>>=20
wrote:<BR>>>><BR>>>>>Dear =
Phil,<BR>>>>>You=20
probably have read that I said allign all 31 audio tracks to =
16376<BR>>>=20
<BR>>> I<BR>>> <BR>>>>>meant to 16384 which =
already=20
was so, so it just adds 12 samples to=20
=
track<BR>>>>>10.<BR>>>>>Regards, <BR>>>>&=
gt;Dimitrios<BR>>>>><BR>>>>> "Dimitrios"=20
<<A href=3D"mailto:musurgio@otenet.gr">musurgio@otenet.gr</A>>=20
wrote:<BR>>>>><BR>>>>>>Hi=20
Phil,<BR>>>>>>According to the author you just have to =
type the=20
latency on the=20
=
vertex<BR>>>>><BR>>>>>instance <BR>>>>>=
;<BR>>>>>>you=20
are putting a plugin and then vertex takes care of the rest=20
!!<BR>>>>>>Here is how it will=20
work...<BR>>>>>>You open vertex dsp on every audio =
track on=20
your 2 card system.<BR>>>>>>You can save that as a =
template for=20
further projects.<BR>>>>>>Now lets say you open on =
track 1 a=20
plugin that has 16384 samples latency<BR>>>>>>, you =
just type=20
16384 on that vertex's instance of audio track 1=20
and<BR>vertex<BR>>>>>>takes care of the rest 31 audio =
tracks to=20
get alligned.<BR>>>>>>Now you put a plugin on track 10 =
which=20
has a latency of 16376 ,you=20
=
just<BR>>>>><BR>>>>>type <BR>>>>><BR>&=
gt;>>>>that=20
number on track's 10 vertex instance and so vertex takes care =
of<BR>>>=20
<BR>>> the<BR>>> <BR>>>>>>rest 31 audio =
tracks=20
again meaning that it delays all other tracks in<BR>>> =
<BR>>>=20
a<BR>>>=20
=
<BR>>>>>way<BR>>>>> <BR>>>>>>that =
all=20
have this 16376 latency, menaing again that it just adds=20
12<BR>samples<BR>>>>>>to track 10 and lives all other =
31 audio=20
tracks with same 16384=20
=
latency<BR>>>>><BR>>>>>!! <BR>>>>><BR>=
>>>>>Isn't=20
that clever ??<BR>>>>>>Now you say you put a plugin on =
track 4=20
of submix 2 that has a=20
=
latency<BR>>>><BR>>>>of <BR>>>><BR>>>>=
>>256=20
ms (you have here to translate it to samples as to have it on=20
=
your<BR>>>><BR>>>>latency <BR>>>><BR>>>&g=
t;>>list)=20
this is 1290 samples ,plus the 12 samples submix 2=20
introduces<BR>(Paris<BR>>>>>>feature) you will have a =
total of=20
1302.<BR>>>>>>Just type 1302 on track's 4 vertex =
instance and=20
vertex will take this<BR>>> <BR>>> very<BR>>>=20
<BR>>>>>>same track to the 16384 latency situation=20
!<BR>>>>>>This very clever delay compensator DOES not =
add the=20
latencies but=20
=
uses<BR>>>><BR>>>>the <BR>>>><BR>>>>&g=
t;>biggest=20
amoung all instances and alligns the rest !<BR>>>>>>I =
hope this=20
=
helps.<BR>>>>>>Regards, <BR>>>>>>Dimitrios<B=
R>>>>>><BR>>>>>> "Phil=20
Aiken" <<A href=3D"mailto:asdf@asdf.sdf">asdf@asdf.sdf</A>>=20
=
wrote:<BR>>>>>><BR>>>>>>> <BR>>>>=
;>>>I=20
am a little unclear still....<BR>>>>>>>For arguments =
sake,=20
let's say I have a 32 track project on 2 cards,<BR>>> =
<BR>>>=20
with<BR>>> <BR>>>>>>>plugins of various=20
latencies...track 1 has 16384 ms. track 10 has=20
=
16376<BR>>>>>><BR>>>>>>ms, <BR>>>>&=
gt;><BR>>>>>>>and=20
track 20 (track 4 of submix 2) has 256 ms latency. What would =
be<BR>>>=20
<BR>>> the<BR>>> <BR>>>>>>>procedure =
with Vertex=20
to even all tracks out across the=20
=
project?<BR>>>>>>> <BR>>>>>>><BR>>&=
gt;>>>><BR>>>>>>> <BR>>>>>>&g=
t;Chas.=20
Duncan <duncan5199ATsbcglobalDOTnet@>=20
wrote:<BR>>>>>>> <BR>>>>>>>>OK, =
that's=20
understood then -- max latency not an issue. Cool. =
And<BR>>>=20
<BR>>> I<BR>>> <BR>>>>>>>>had an =
email=20
exchange with the developer today regarding 98 --=20
he<BR>says<BR>>>>>>>>it shouldn't be a problem =
and=20
encouraged me to try the demo. =
Which<BR> >>>>>>>I'll =20
do, as soon as I'm done with this batch of mixes I'm busy=20
with<BR> >>>>>>>righ t now (don't want to throw =
*anything*=20
new into this system until<BR> >>>>>>>this job is=20
done). But, if he gets this "manual latency"=20
compensator<BR> >>>>>>>gizm o working, I'll buy =
just for=20
that and for the extra solo and=20
=
mute<BR> >>>>>>>capa bility. <BR>>>>>>&g=
t;><BR> >>>>>>>--=2 0
thanks for keeping on top of these developments -- much=20
appreciated<BR> >>>>>>>--=2 0
=
chas.<BR>>>>>>>> <BR>>>>>>>>On =
23 Jan=20
2007 04:25:42 +1000, "Dimitrios" <<A=20
href=3D"mailto:musurgio@otenet.gr">musurgio@otenet.gr</A>>=20
=
wrote:<BR>>>>>>>> <BR>>>>>>>> <BR=
> >>>>>>>& ;gt;Well=20
there is no pick from the list =
thing.<BR> >>>>>>>& ;gt;If=20
you read all the posts you will understand that the latency=20
=
is<BR>due<BR>>>>>><BR >>>>>>to<BR>>>&g=
t;>><BR> >>>>>>>& ;gt;the=20
amount you manually type on a ceratin vertex instance vst=20
plugin.<BR> >>>>>>>& ;gt;so if you put a 64 samples =
latent=20
vst plugin you just type 64=20
<BR>>>>>><BR>>>>>>and all=20
other<BR>>>>>><BR> >>>>>>>& ;gt;audio =
tracks=20
get delayed that amount !<BR> >>>>>>>& ;gt;The =
author just=20
asks how much would be the maximum possible=20
=
latency<BR>>>><BR>>>>needed <BR>>>><BR>>>=
>>>>>>because=20
the 132000 maximum (only maximum if you will ever reach=20
=
that<BR>>>>><BR>>>>>) <BR>>>>><BR>>=
>>>>>the<BR>>>>>>> <BR>>>>>&g=
t;>>>author=20
suggests uses 1 mb memory per vertex instance , so for=20
=
32<BR>audio<BR>>>>>>> <BR>>>>>>>tracks=
<BR>>>>>>><BR> >>>>>>>& ;gt;with=20
vertex 32mb will be needed, for 64 paris audio tracks with=20
=
vertex<BR>>>>>>> <BR>>>>>>>64<BR>>&=
gt;>>>><BR> >>>>>>>& ;gt;mb=20
will be needed.<BR> >>>>>>>& ;gt;I aggree with the =
author's=20
132000 samples as maximum ,if you=20
=
will<BR>ever<BR>>>>>>> <BR>>>>>>>reach=
<BR>>>>>>><BR> >>>>>>>& ;gt;that=20
I say again.<BR> >>>>>>>& ;gt;Normally you would =
never pass=20
1000 without uad1=20
=
plugins...<BR> >>>>>>>& ;gt;Regards, <BR>>>>>=
;>>>>Dimitrios<BR> >>>>>>>& ;gt;Chas.=20
Duncan <duncan5199ATsbcglobalDOTnet@>=20
=
wrote:<BR> >>>>>>>& ;gt; <BR>>>>>>>>=
;>>Gene/Dimitrios:<BR> >>>>>>>& ;gt;> <BR>>&=
gt;>>>>>>>W ould=20
it even be necessary to "pick from a list" or "assign"=20
total<BR> >>>>>>>& ;gt;>delay? Seems like =
the total=20
delay would simply be as low (or=20
as<BR>high)<BR> >>>>>>>& ;gt;>as needed to =
compensate for=20
the plugins used. (Unless I'm=20
missing<BR> >>>>>>>& ;gt;>something, which is =
always a=20
=
possibility...)<BR> >>>>>>>& ;gt;> <BR>>>>&g=
t;>>>>>As=20
for me -- I'm still on 98, 512 ram -- could I run this=20
thing<BR>right<BR> >>>>>>>& ;gt;>now, just to =
compensate=20
for EDS fx offsets, submix offsets,=20
=
etc.?<BR> >>>>>>>& ;gt;> <BR>>>>>>>=
>>>--=20
interested in how this turns out -- thanks --=20
=
chas.<BR> >>>>>>>& ;gt;> <BR>>>>>>>=
>>><BR> >>>>>>>& ;gt;>On=20
23 Jan 2007 02:54:04 +1000, "Gene=20
Lennon"<BR> >>>>>>>& ;gt;>< <A=20
=
href=3D"mailto:glennon@NOSPmyrealbox.com">glennon@NOSPmyrealbox.com</A>&g=
t;=20
=
wrote:<BR> >>>>>>>& ;gt;> <BR>>>>>>>=
;>>><BR> >>>>>>>& ;gt;>> "Dimitrios"=20
<<A href=3D"mailto:musurgio@otenet.gr">musurgio@otenet.gr</A>>=20
=
wrote:<BR> >>>>>>>& ;gt;>> <BR>>>>>>=
;>>>>>>Here=20
is what the author wrote about his latency addon for=20
vertex..!!<BR> >>>>>>>& ;gt;>>>Track 1 has =
a=20
latency of 16384 samples. The same is true for=20
=
track<BR>>>>>><BR>>>>>>2. <BR>>>>&g=
t;><BR> >>>>>>>& ;gt;As <BR>>>>>>>&=
gt;><BR> >>>>>>>& ;gt;>>>track=20
1 and track 2 have the same latency they are already=20
=
in<BR>sync,<BR>>>>>>> <BR>>>>>>>but<BR=
>>>>>>><BR> >>>>>>>& ;gt;>>all <=
BR> >>>>>>>& ;gt;>> <BR>>>>>>>&g=
t;>>>>other=20
tracks (the remaining 46 tracks) have to be delayed by=20
=
16384<BR>>>>>><BR>>>>>>samples, <BR>>>=
>>><BR> >>>>>>>& ;gt;>>>not=20
=
32768.<BR> >>>>>>>& ;gt;>>> <BR>>>>>=
;>>>>>>>Tak e=20
another example: Track 1 has a plug-in with 16384=20
=
samples<BR>of<BR>>>>><BR>>>>>latency. <BR>>>=
>><BR> >>>>>>>& ;gt;>>>Track=20
2 has a plug-in with a latency of 8192 samples. What=20
=
FaderWorks<BR> >>>>>>>& ;gt; <BR>>>>>>>=
;>>will<BR> >>>>>>>& ;gt; <BR>>>>>>=
>>>>>>do=20
is: Tracks 1 will pass through as it is, track 2 will be=20
=
delayed<BR>>>>>>> <BR>>>>>>>by<BR>>=
>>>>><BR> >>>>>>>& ;gt;8192 <BR>>>&=
gt;>>>>><BR> >>>>>>>& ;gt;>>>sa=
mples=20
and all other tracks will be delayed by 16384=20
=
samples.<BR> >>>>>>>& ;gt;>>> <BR>>>>&=
gt;>>>>>>>W hat=20
counts for the overall latency is the largest latency=20
=
of<BR>any<BR>>>>><BR>>>>>track. <BR>>>>&g=
t;<BR> >>>>>>>& ;gt;>>>You=20
calculate the sum of latencies only for individual=20
=
tracks<BR>when<BR>>>>>> <BR>>>>>>you<BR>>=
>>>><BR> >>>>>>>& ;gt;e.g. <BR>>>>&=
gt;>>>><BR> >>>>>>>& ;gt;>>>put=20
several uad1 behind on the same=20
=
track.<BR> >>>>>>>& ;gt;>>> <BR>>>>>=
;>>>>>>>ISN 'T=20
that WHAT WE WANT ? =
!!!<BR> >>>>>>>& ;gt;>>>If we=20
don't buy this vertex we have to jump off Paris !!=20
=
:)<BR> >>>>>>>& ;gt;>>>Regards, <BR>>>>=
;>>>>>>>&am p;gt;Dimitrios=20
=
<BR> >>>>>>>& ;gt;>>> <BR>>>>>>&=
gt;>>>>>"Dimitrios"=20
<<A href=3D"mailto:musurgio@otenet.gr">musurgio@otenet.gr</A>>=20
=
wrote:<BR> >>>>>>>& ;gt;>>> <BR>>>>>=
;>>>>>><BR> >>>>>>>& ;gt;>>That=
=20
is what we want, but extremely high playback latencies =
will<BR>>>=20
<BR>>> probably<BR>>>=20
<BR> >>>>>>>& ;gt;>>cause a delay between =
fader and=20
mute actions and audible=20
=
execution<BR>>>>><BR>>>>>(and <BR>>>>>=
<BR> >>>>>>>& ;gt;also <BR> >>>>>>>& ;=
gt;<BR> >>>>>>>& ;gt;>>delay=20
meters). I need to make automation decisions with=20
=
effects<BR>in<BR>>>>><BR>>>>>place, <BR>>>&g=
t;><BR> >>>>>>>& ;gt;>>so=20
extremely long delays could be problematic.=20
<BR> >>>>>>>& ;gt;>>Any chance we could pick =
from a=20
list or assign a total=20
=
delay?<BR> >>>>>>>& ;gt;>>Gene <BR>>>>>=
;>>>>>>This=20
is exciting.<BR> >>>>>>>& ;gt;> <BR>>>=20
<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_0054_01C73EF3.6183A160--
|
|
|
|
| Re: Author of Vertex needs some input from us to improve !! [message #78877 is a reply to message #78876] |
Tue, 23 January 2007 11:07 |
Deej [4]
Messages: 1292
Registered: January 2007
|
Senior Member |
|
|
This is a multi-part message in MIME format.
------=_NextPart_000_0374_01C73EE7.170A7FC0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
ROTFL!!!!!
(patience gwasshoppa')
;o)
"Tom Bruhl" <arpegio@comcast.net> wrote in message =
news:45b655ee@linux...
A couple of weeks?!?! That's alot of latency.
Tom
"Dimitrios" <musurgio@otenet.gr> wrote in message =
news:45b64aaa$1@linux...
Dear Jeff,
This is what makes this author a nice guy ...
I proposed it to him to be added on his vertex and he reacted in a =
very positive
way improving my idea and promissing a couple of weeks for this =
update to
his vertex that will include the latency compensator.
Hope this helps.
Regards,
Dimitrios
Jeff hoover <jkhoover@excite-DOT-com> wrote:
>So is the compensator already in the product, or do we have a =
timeline=20
>for it?
>
>Hoov
>
>Dimitrios wrote:
>> Great Chris !
>> Please email him too saying that you are a Paris users that has =
been informed
>> about the latency compensator !
>> Regards,
>> Dimitrios
>>=20
>> "Chris Lang" <yo@yo.yo> wrote:
>>=20
>>>That is awesome. Buying it now...
>>>
>>>Chris
>>>
>>>
>>>"Dimitrios" <musurgio@otenet.gr> wrote:
>>>
>>>>Dear Phil,
>>>>You probably have read that I said allign all 31 audio tracks to =
16376
>>=20
>> I
>>=20
>>>>meant to 16384 which already was so, so it just adds 12 samples =
to track
>>>>10.
>>>>Regards,
>>>>Dimitrios
>>>>
>>>>"Dimitrios" <musurgio@otenet.gr> wrote:
>>>>
>>>>>Hi Phil,
>>>>>According to the author you just have to type the latency on =
the vertex
>>>>
>>>>instance
>>>>
>>>>>you are putting a plugin and then vertex takes care of the rest =
!!
>>>>>Here is how it will work...
>>>>>You open vertex dsp on every audio track on your 2 card system.
>>>>>You can save that as a template for further projects.
>>>>>Now lets say you open on track 1 a plugin that has 16384 =
samples latency
>>>>>, you just type 16384 on that vertex's instance of audio track =
1 and
vertex
>>>>>takes care of the rest 31 audio tracks to get alligned.
>>>>>Now you put a plugin on track 10 which has a latency of 16376 =
,you just
>>>>
>>>>type
>>>>
>>>>>that number on track's 10 vertex instance and so vertex takes =
care of
>>=20
>> the
>>=20
>>>>>rest 31 audio tracks again meaning that it delays all other =
tracks in
>>=20
>> a
>>=20
>>>>way
>>>>
>>>>>that all have this 16376 latency, menaing again that it just =
adds 12
samples
>>>>>to track 10 and lives all other 31 audio tracks with same 16384 =
latency
>>>>
>>>>!!
>>>>
>>>>>Isn't that clever ??
>>>>>Now you say you put a plugin on track 4 of submix 2 that has a =
latency
>>>
>>>of
>>>
>>>>>256 ms (you have here to translate it to samples as to have it =
on your
>>>
>>>latency
>>>
>>>>>list) this is 1290 samples ,plus the 12 samples submix 2 =
introduces
(Paris
>>>>>feature) you will have a total of 1302.
>>>>>Just type 1302 on track's 4 vertex instance and vertex will =
take this
>>=20
>> very
>>=20
>>>>>same track to the 16384 latency situation !
>>>>>This very clever delay compensator DOES not add the latencies =
but uses
>>>
>>>the
>>>
>>>>>biggest amoung all instances and alligns the rest !
>>>>>I hope this helps.
>>>>>Regards,
>>>>>Dimitrios
>>>>>
>>>>>"Phil Aiken" <asdf@asdf.sdf> wrote:
>>>>>
>>>>>>
>>>>>>I am a little unclear still....
>>>>>>For arguments sake, let's say I have a 32 track project on 2 =
cards,
>>=20
>> with
>>=20
>>>>>>plugins of various latencies...track 1 has 16384 ms. track 10 =
has 16376
>>>>>
>>>>>ms,
>>>>>
>>>>>>and track 20 (track 4 of submix 2) has 256 ms latency. What =
would be
>>=20
>> the
>>=20
>>>>>>procedure with Vertex to even all tracks out across the =
project?
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>Chas. Duncan <duncan5199ATsbcglobalDOTnet@> wrote:
>>>>>>
>>>>>>>OK, that's understood then -- max latency not an issue. =
Cool. And
>>=20
>> I
>>=20
>>>>>>>had an email exchange with the developer today regarding 98 =
-- he
says
>>>>>>>it shouldn't be a problem and encouraged me to try the demo. =
Which
>>>>>>>I'll do, as soon as I'm done with this batch of mixes I'm =
busy with
>>>>>>>right now (don't want to throw *anything* new into this =
system until
>>>>>>>this job is done). But, if he gets this "manual latency" =
compensator
>>>>>>>gizmo working, I'll buy just for that and for the extra solo =
and mute
>>>>>>>capability.
>>>>>>>
>>>>>>>-- thanks for keeping on top of these developments -- much =
appreciated
>>>>>>>-- chas.
>>>>>>>
>>>>>>>On 23 Jan 2007 04:25:42 +1000, "Dimitrios" =
<musurgio@otenet.gr> wrote:
>>>>>>>
>>>>>>>
>>>>>>>>Well there is no pick from the list thing.
>>>>>>>>If you read all the posts you will understand that the =
latency is
due
>>>>>
>>>>>to
>>>>>
>>>>>>>>the amount you manually type on a ceratin vertex instance =
vst plugin.
>>>>>>>>so if you put a 64 samples latent vst plugin you just type =
64=20
>>>>>
>>>>>and all other
>>>>>
>>>>>>>>audio tracks get delayed that amount !
>>>>>>>>The author just asks how much would be the maximum possible =
latency
>>>
>>>needed
>>>
>>>>>>>>because the 132000 maximum (only maximum if you will ever =
reach that
>>>>
>>>>)
>>>>
>>>>>>the
>>>>>>
>>>>>>>>author suggests uses 1 mb memory per vertex instance , so =
for 32
audio
>>>>>>
>>>>>>tracks
>>>>>>
>>>>>>>>with vertex 32mb will be needed, for 64 paris audio tracks =
with vertex
>>>>>>
>>>>>>64
>>>>>>
>>>>>>>>mb will be needed.
>>>>>>>>I aggree with the author's 132000 samples as maximum ,if you =
will
ever
>>>>>>
>>>>>>reach
>>>>>>
>>>>>>>>that I say again.
>>>>>>>>Normally you would never pass 1000 without uad1 plugins...
>>>>>>>>Regards,
>>>>>>>>Dimitrios
>>>>>>>>Chas. Duncan <duncan5199ATsbcglobalDOTnet@> wrote:
>>>>>>>>
>>>>>>>>>Gene/Dimitrios:
>>>>>>>>>
>>>>>>>>>Would it even be necessary to "pick from a list" or =
"assign" total
>>>>>>>>>delay? Seems like the total delay would simply be as low =
(or as
high)
>>>>>>>>>as needed to compensate for the plugins used. (Unless I'm =
missing
>>>>>>>>>something, which is always a possibility...)
>>>>>>>>>
>>>>>>>>>As for me -- I'm still on 98, 512 ram -- could I run this =
thing
right
>>>>>>>>>now, just to compensate for EDS fx offsets, submix offsets, =
etc.?
>>>>>>>>>
>>>>>>>>>-- interested in how this turns out -- thanks -- chas.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>On 23 Jan 2007 02:54:04 +1000, "Gene Lennon"
>>>>>>>>><glennon@NOSPmyrealbox.com> wrote:
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>>"Dimitrios" <musurgio@otenet.gr> wrote:
>>>>>>>>>>
>>>>>>>>>>>Here is what the author wrote about his latency addon for =
vertex..!!
>>>>>>>>>>>Track 1 has a latency of 16384 samples. The same is true =
for track
>>>>>
>>>>>2.
>>>>>
>>>>>>>>As
>>>>>>>>
>>>>>>>>>>>track 1 and track 2 have the same latency they are =
already in
sync,
>>>>>>
>>>>>>but
>>>>>>
>>>>>>>>>>all
>>>>>>>>>>
>>>>>>>>>>>other tracks (the remaining 46 tracks) have to be delayed =
by 16384
>>>>>
>>>>>samples,
>>>>>
>>>>>>>>>>>not 32768.
>>>>>>>>>>>
>>>>>>>>>>>Take another example: Track 1 has a plug-in with 16384 =
samples
of
>>>>
>>>>latency.
>>>>
>>>>>>>>>>>Track 2 has a plug-in with a latency of 8192 samples. =
What FaderWorks
>>>>>>>>
>>>>>>>>will
>>>>>>>>
>>>>>>>>>>>do is: Tracks 1 will pass through as it is, track 2 will =
be delayed
>>>>>>
>>>>>>by
>>>>>>
>>>>>>>>8192
>>>>>>>>
>>>>>>>>>>>samples and all other tracks will be delayed by 16384 =
samples.
>>>>>>>>>>>
>>>>>>>>>>>What counts for the overall latency is the largest =
latency of
any
>>>>
>>>>track.
>>>>
>>>>>>>>>>>You calculate the sum of latencies only for individual =
tracks
when
>>>>>
>>>>>you
>>>>>
>>>>>>>>e.g.
>>>>>>>>
>>>>>>>>>>>put several uad1 behind on the same track.
>>>>>>>>>>>
>>>>>>>>>>>ISN'T that WHAT WE WANT ? !!!
>>>>>>>>>>>If we don't buy this vertex we have to jump off Paris !! =
:)
>>>>>>>>>>>Regards,
>>>>>>>>>>>Dimitrios=20
>>>>>>>>>>>
>>>>>>>>>>>"Dimitrios" <musurgio@otenet.gr> wrote:
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>That is what we want, but extremely high playback =
latencies will
>>=20
>> probably
>>=20
>>>>>>>>>>cause a delay between fader and mute actions and audible =
execution
>>>>
>>>>(and
>>>>
>>>>>>>>also
>>>>>>>>
>>>>>>>>>>delay meters). I need to make automation decisions with =
effects
in
>>>>
>>>>place,
>>>>
>>>>>>>>>>so extremely long delays could be problematic.=20
>>>>>>>>>>Any chance we could pick from a list or assign a total =
delay?
>>>>>>>>>>Gene
>>>>>>>>>>This is exciting.
>>>>>>>>>
>>=20
I choose Polesoft Lockspam to fight spam, and you?
http://www.polesoft.com/refer.html
------=_NextPart_000_0374_01C73EE7.170A7FC0
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>ROTFL!!!!!</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>(patience gwasshoppa')</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>;o)</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:45b655ee@linux">news:45b655ee@linux</A>...</DIV>
<DIV><FONT face=3DArial size=3D2>A couple of weeks?!?! That's =
alot of=20
latency.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Tom</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV> </DIV>
<BLOCKQUOTE=20
style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; =
BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
<DIV>"Dimitrios" <<A=20
href=3D"mailto:musurgio@otenet.gr">musurgio@otenet.gr</A>> wrote =
in message=20
<A =
href=3D"news:45b64aaa$1@linux">news:45b64aaa$1@linux</A>...</DIV><BR>Dear=
=20
Jeff,<BR>This is what makes this author a nice guy ...<BR>I proposed =
it to=20
him to be added on his vertex and he reacted in a very =
positive<BR>way=20
improving my idea and promissing a couple of weeks for this update =
to<BR>his=20
vertex that will include the latency compensator.<BR>Hope this=20
helps.<BR>Regards,<BR>Dimitrios<BR>Jeff hoover <<A=20
=
href=3D"mailto:jkhoover@excite-DOT-com">jkhoover@excite-DOT-com</A>>=20
wrote:<BR>>So is the compensator already in the product, or do we =
have a=20
timeline <BR>>for =
it?<BR>><BR>>Hoov<BR>><BR>>Dimitrios=20
wrote:<BR>>> Great Chris !<BR>>> Please email him too =
saying=20
that you are a Paris users that has been informed<BR>>> about =
the=20
latency compensator !<BR>>> Regards,<BR>>> =
Dimitrios<BR>>>=20
<BR>>> "Chris Lang" <<A =
href=3D"mailto:yo@yo.yo">yo@yo.yo</A>>=20
wrote:<BR>>> <BR>>>>That is awesome. Buying it=20
=
now...<BR>>>><BR>>>>Chris <BR>>>><BR>>>&g=
t;<BR>>>>"Dimitrios"=20
<<A href=3D"mailto:musurgio@otenet.gr">musurgio@otenet.gr</A>> =
wrote:<BR>>>><BR>>>>>Dear =
Phil,<BR>>>>>You=20
probably have read that I said allign all 31 audio tracks to=20
16376<BR>>> <BR>>> I<BR>>> =
<BR>>>>>meant to=20
16384 which already was so, so it just adds 12 samples to=20
=
track<BR>>>>>10.<BR>>>>>Regards, <BR>>>>&=
gt;Dimitrios<BR>>>>><BR>>>>> "Dimitrios"=20
<<A href=3D"mailto:musurgio@otenet.gr">musurgio@otenet.gr</A>> =
wrote:<BR>>>>><BR>>>>>>Hi=20
Phil,<BR>>>>>>According to the author you just have =
to type=20
the latency on the=20
=
vertex<BR>>>>><BR>>>>>instance <BR>>>>>=
;<BR>>>>>>you=20
are putting a plugin and then vertex takes care of the rest=20
!!<BR>>>>>>Here is how it will=20
work...<BR>>>>>>You open vertex dsp on every audio =
track on=20
your 2 card system.<BR>>>>>>You can save that as a =
template=20
for further projects.<BR>>>>>>Now lets say you open =
on track=20
1 a plugin that has 16384 samples latency<BR>>>>>>, =
you just=20
type 16384 on that vertex's instance of audio track 1=20
and<BR>vertex<BR>>>>>>takes care of the rest 31 audio =
tracks=20
to get alligned.<BR>>>>>>Now you put a plugin on =
track 10=20
which has a latency of 16376 ,you=20
=
just<BR>>>>><BR>>>>>type <BR>>>>><BR>&=
gt;>>>>that=20
number on track's 10 vertex instance and so vertex takes care =
of<BR>>>=20
<BR>>> the<BR>>> <BR>>>>>>rest 31 audio =
tracks=20
again meaning that it delays all other tracks in<BR>>> =
<BR>>>=20
a<BR>>>=20
=
<BR>>>>>way<BR>>>>> <BR>>>>>>that =
all=20
have this 16376 latency, menaing again that it just adds=20
12<BR>samples<BR>>>>>>to track 10 and lives all other =
31=20
audio tracks with same 16384=20
=
latency<BR>>>>><BR>>>>>!! <BR>>>>><BR>=
>>>>>Isn't=20
that clever ??<BR>>>>>>Now you say you put a plugin =
on track=20
4 of submix 2 that has a=20
=
latency<BR>>>><BR>>>>of <BR>>>><BR>>>>=
>>256=20
ms (you have here to translate it to samples as to have it on=20
=
your<BR>>>><BR>>>>latency <BR>>>><BR>>>&g=
t;>>list)=20
this is 1290 samples ,plus the 12 samples submix 2=20
introduces<BR>(Paris<BR>>>>>>feature) you will have a =
total=20
of 1302.<BR>>>>>>Just type 1302 on track's 4 vertex =
instance=20
and vertex will take this<BR>>> <BR>>> very<BR>>>=20
<BR>>>>>>same track to the 16384 latency situation=20
!<BR>>>>>>This very clever delay compensator DOES not =
add the=20
latencies but=20
=
uses<BR>>>><BR>>>>the <BR>>>><BR>>>>&g=
t;>biggest=20
amoung all instances and alligns the rest !<BR>>>>>>I =
hope=20
this=20
=
helps.<BR>>>>>>Regards, <BR>>>>>>Dimitrios<B=
R>>>>>><BR>>>>>> "Phil=20
Aiken" <<A href=3D"mailto:asdf@asdf.sdf">asdf@asdf.sdf</A>>=20
=
wrote:<BR>>>>>><BR>>>>>>> <BR>>>>=
;>>>I=20
am a little unclear still....<BR>>>>>>>For =
arguments sake,=20
let's say I have a 32 track project on 2 cards,<BR>>> =
<BR>>>=20
with<BR>>> <BR>>>>>>>plugins of various=20
latencies...track 1 has 16384 ms. track 10 has=20
=
16376<BR>>>>>><BR>>>>>>ms, <BR>>>>&=
gt;><BR>>>>>>>and=20
track 20 (track 4 of submix 2) has 256 ms latency. What would =
be<BR>>>=20
<BR>>> the<BR>>> <BR>>>>>>>procedure =
with=20
Vertex to even all tracks out across the=20
=
project?<BR>>>>>>> <BR>>>>>>><BR>>&=
gt;>>>><BR>>>>>>> <BR>>>>>>&g=
t;Chas.=20
Duncan <duncan5199ATsbcglobalDOTnet@>=20
=
wrote:<BR>>>>>>> <BR>>>>>>>>OK, =
that's=20
understood then -- max latency not an issue. Cool. =20
And<BR>>> <BR>>> I<BR>>>=20
<BR>>>>>>>>had an email exchange with the =
developer=20
today regarding 98 -- he<BR>says<BR>>>>>>>>it =
shouldn't=20
be a problem and encouraged me to try the demo. =20
Which<BR> >>>>>>>I'll do, as soon as I'm done =
with this=20
batch of mixes I'm busy with<BR> >>>>>>>righ t =
now (don't=20
want to throw *anything* new into this system=20
until<BR> >>>>>>>this job is done). But, =
if he=20
gets this "manual latency" =
compensator<BR> >>>>>>>gizm o=20
working, I'll buy just for that and for the extra solo and=20
=
mute<BR> >>>>>>>capa bility. <BR>>>>>>&g=
t;><BR> >>>>>>>--=2 0
thanks for keeping on top of these developments -- much=20
appreciated<BR> >>>>>>>--=2 0
=
chas.<BR>>>>>>>> <BR>>>>>>>>On =
23=20
Jan 2007 04:25:42 +1000, "Dimitrios" <<A=20
href=3D"mailto:musurgio@otenet.gr">musurgio@otenet.gr</A>>=20
=
wrote:<BR>>>>>>>> <BR>>>>>>>> <BR=
> >>>>>>>& ;gt;Well=20
there is no pick from the list =
thing.<BR> >>>>>>>& ;gt;If=20
you read all the posts you will understand that the latency=20
=
is<BR>due<BR>>>>>><BR >>>>>>to<BR>>>&g=
t;>><BR> >>>>>>>& ;gt;the=20
amount you manually type on a ceratin vertex instance vst=20
plugin.<BR> >>>>>>>& ;gt;so if you put a 64 =
samples latent=20
vst plugin you just type 64=20
<BR>>>>>><BR>>>>>>and all=20
=
other<BR>>>>>><BR> >>>>>>>& ;gt;audio=20
tracks get delayed that amount =
!<BR> >>>>>>>& ;gt;The=20
author just asks how much would be the maximum possible=20
=
latency<BR>>>><BR>>>>needed <BR>>>><BR>>>=
>>>>>>because=20
the 132000 maximum (only maximum if you will ever reach=20
=
that<BR>>>>><BR>>>>>) <BR>>>>><BR>>=
>>>>>the<BR>>>>>>> <BR>>>>>&g=
t;>>>author=20
suggests uses 1 mb memory per vertex instance , so for=20
=
32<BR>audio<BR>>>>>>> <BR>>>>>>>tracks=
<BR>>>>>>><BR> >>>>>>>& ;gt;with=20
vertex 32mb will be needed, for 64 paris audio tracks with=20
=
vertex<BR>>>>>>> <BR>>>>>>>64<BR>>&=
gt;>>>><BR> >>>>>>>& ;gt;mb=20
will be needed.<BR> >>>>>>>& ;gt;I aggree with the =
author's 132000 samples as maximum ,if you=20
=
will<BR>ever<BR>>>>>>> <BR>>>>>>>reach=
<BR>>>>>>><BR> >>>>>>>& ;gt;that=20
I say again.<BR> >>>>>>>& ;gt;Normally you would =
never=20
pass 1000 without uad1=20
=
plugins...<BR> >>>>>>>& ;gt;Regards, <BR>>>>>=
;>>>>Dimitrios<BR> >>>>>>>& ;gt;Chas.=20
Duncan <duncan5199ATsbcglobalDOTnet@>=20
=
wrote:<BR> >>>>>>>& ;gt; <BR>>>>>>>>=
;>>Gene/Dimitrios:<BR> >>>>>>>& ;gt;> <BR>>&=
gt;>>>>>>>W ould=20
it even be necessary to "pick from a list" or "assign"=20
total<BR> >>>>>>>& ;gt;>delay? Seems like =
the=20
total delay would simply be as low (or=20
as<BR>high)<BR> >>>>>>>& ;gt;>as needed to =
compensate=20
for the plugins used. (Unless I'm=20
missing<BR> >>>>>>>& ;gt;>something, which is =
always a=20
=
possibility...)<BR> >>>>>>>& ;gt;> <BR>>>>&g=
t;>>>>>As=20
for me -- I'm still on 98, 512 ram -- could I run this=20
thing<BR>right<BR> >>>>>>>& ;gt;>now, just to=20
compensate for EDS fx offsets, submix offsets,=20
=
etc.?<BR> >>>>>>>& ;gt;> <BR>>>>>>>=
>>>--=20
interested in how this turns out -- thanks --=20
=
chas.<BR> >>>>>>>& ;gt;> <BR>>>>>>>=
>>><BR> >>>>>>>& ;gt;>On=20
23 Jan 2007 02:54:04 +1000, "Gene=20
Lennon"<BR> >>>>>>>& ;gt;>< <A=20
=
href=3D"mailto:glennon@NOSPmyrealbox.com">glennon@NOSPmyrealbox.com</A>&g=
t;=20
=
wrote:<BR> >>>>>>>& ;gt;> <BR>>>>>>>=
;>>><BR> >>>>>>>& ;gt;>> "Dimitrios"=20
<<A href=3D"mailto:musurgio@otenet.gr">musurgio@otenet.gr</A>> =
=
wrote:<BR> >>>>>>>& ;gt;>> <BR>>>>>>=
;>>>>>>Here=20
is what the author wrote about his latency addon for=20
vertex..!!<BR> >>>>>>>& ;gt;>>>Track 1 =
has a=20
latency of 16384 samples. The same is true for=20
=
track<BR>>>>>><BR>>>>>>2. <BR>>>>&g=
t;><BR> >>>>>>>& ;gt;As <BR>>>>>>>&=
gt;><BR> >>>>>>>& ;gt;>>>track=20
1 and track 2 have the same latency they are already=20
=
in<BR>sync,<BR>>>>>>> <BR>>>>>>>but<BR=
>>>>>>><BR> >>>>>>>& ;gt;>>all <=
BR> >>>>>>>& ;gt;>> <BR>>>>>>>&g=
t;>>>>other=20
tracks (the remaining 46 tracks) have to be delayed by=20
=
16384<BR>>>>>><BR>>>>>>samples, <BR>>>=
>>><BR> >>>>>>>& ;gt;>>>not=20
=
32768.<BR> >>>>>>>& ;gt;>>> <BR>>>>>=
;>>>>>>>Tak e=20
another example: Track 1 has a plug-in with 16384=20
=
samples<BR>of<BR>>>>><BR>>>>>latency. <BR>>>=
>><BR> >>>>>>>& ;gt;>>>Track=20
2 has a plug-in with a latency of 8192 samples. What=20
=
FaderWorks<BR> >>>>>>>& ;gt; <BR>>>>>>>=
;>>will<BR> >>>>>>>& ;gt; <BR>>>>>>=
>>>>>>do=20
is: Tracks 1 will pass through as it is, track 2 will be=20
=
delayed<BR>>>>>>> <BR>>>>>>>by<BR>>=
>>>>><BR> >>>>>>>& ;gt;8192 <BR>>>&=
gt;>>>>><BR> >>>>>>>& ;gt;>>>sa=
mples=20
and all other tracks will be delayed by 16384=20
=
samples.<BR> >>>>>>>& ;gt;>>> <BR>>>>&=
gt;>>>>>>>W hat=20
counts for the overall latency is the largest latency=20
=
of<BR>any<BR>>>>><BR>>>>>track. <BR>>>>&g=
t;<BR> >>>>>>>& ;gt;>>>You=20
calculate the sum of latencies only for individual=20
=
tracks<BR>when<BR>>>>>> <BR>>>>>>you<BR>>=
>>>><BR> >>>>>>>& ;gt;e.g. <BR>>>>&=
gt;>>>><BR> >>>>>>>& ;gt;>>>put=20
several uad1 behind on the same=20
=
track.<BR> >>>>>>>& ;gt;>>> <BR>>>>>=
;>>>>>>>ISN 'T=20
that WHAT WE WANT ? =
!!!<BR> >>>>>>>& ;gt;>>>If we=20
don't buy this vertex we have to jump off Paris !!=20
=
:)<BR> >>>>>>>& ;gt;>>>Regards, <BR>>>>=
;>>>>>>>&am p;gt;Dimitrios=20
=
<BR> >>>>>>>& ;gt;>>> <BR>>>>>>&=
gt;>>>>>"Dimitrios"=20
<<A href=3D"mailto:musurgio@otenet.gr">musurgio@otenet.gr</A>> =
=
wrote:<BR> >>>>>>>& ;gt;>>> <BR>>>>>=
;>>>>>><BR> >>>>>>>& ;gt;>>That=
=20
is what we want, but extremely high playback latencies =
will<BR>>>=20
<BR>>> probably<BR>>>=20
<BR> >>>>>>>& ;gt;>>cause a delay between =
fader and=20
mute actions and audible=20
=
execution<BR>>>>><BR>>>>>(and <BR>>>>>=
<BR> >>>>>>>& ;gt;also <BR> >>>>>>>& ;=
gt;<BR> >>>>>>>& ;gt;>>delay=20
meters). I need to make automation decisions with=20
=
effects<BR>in<BR>>>>><BR>>>>>place, <BR>>>&g=
t;><BR> >>>>>>>& ;gt;>>so=20
extremely long delays could be problematic.=20
<BR> >>>>>>>& ;gt;>>Any chance we could pick =
from a=20
list or assign a total=20
=
delay?<BR> >>>>>>>& ;gt;>>Gene <BR>>>>>=
;>>>>>>This=20
is exciting.<BR> >>>>>>>& ;gt;> <BR>>>=20
<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_0374_01C73EE7.170A7FC0--
|
|
|
|
| Re: Author of Vertex needs some input from us to improve !! [message #78880 is a reply to message #78877] |
Tue, 23 January 2007 11:35 |
Tom Bruhl
Messages: 1368
Registered: June 2007
|
Senior Member |
|
|
This is a multi-part message in MIME format.
------=_NextPart_000_007E_01C73EFB.C562FA20
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
If this latency compensator shows up in two weeks I'll be floored.
I'll be surprised whenever it shows up. $45? Duh.
Tom
"DJ" <www.aarrrrggghhh!!!.com> wrote in message news:45b65d47@linux...
ROTFL!!!!!
(patience gwasshoppa')
;o)
"Tom Bruhl" <arpegio@comcast.net> wrote in message =
news:45b655ee@linux...
A couple of weeks?!?! That's alot of latency.
Tom
"Dimitrios" <musurgio@otenet.gr> wrote in message =
news:45b64aaa$1@linux...
Dear Jeff,
This is what makes this author a nice guy ...
I proposed it to him to be added on his vertex and he reacted in a =
very positive
way improving my idea and promissing a couple of weeks for this =
update to
his vertex that will include the latency compensator.
Hope this helps.
Regards,
Dimitrios
Jeff hoover <jkhoover@excite-DOT-com> wrote:
>So is the compensator already in the product, or do we have a =
timeline=20
>for it?
>
>Hoov
>
>Dimitrios wrote:
>> Great Chris !
>> Please email him too saying that you are a Paris users that has =
been informed
>> about the latency compensator !
>> Regards,
>> Dimitrios
>>=20
>> "Chris Lang" <yo@yo.yo> wrote:
>>=20
>>>That is awesome. Buying it now...
>>>
>>>Chris
>>>
>>>
>>>"Dimitrios" <musurgio@otenet.gr> wrote:
>>>
>>>>Dear Phil,
>>>>You probably have read that I said allign all 31 audio tracks =
to 16376
>>=20
>> I
>>=20
>>>>meant to 16384 which already was so, so it just adds 12 =
samples to track
>>>>10.
>>>>Regards,
>>>>Dimitrios
>>>>
>>>>"Dimitrios" <musurgio@otenet.gr> wrote:
>>>>
>>>>>Hi Phil,
>>>>>According to the author you just have to type the latency on =
the vertex
>>>>
>>>>instance
>>>>
>>>>>you are putting a plugin and then vertex takes care of the =
rest !!
>>>>>Here is how it will work...
>>>>>You open vertex dsp on every audio track on your 2 card =
system.
>>>>>You can save that as a template for further projects.
>>>>>Now lets say you open on track 1 a plugin that has 16384 =
samples latency
>>>>>, you just type 16384 on that vertex's instance of audio =
track 1 and
vertex
>>>>>takes care of the rest 31 audio tracks to get alligned.
>>>>>Now you put a plugin on track 10 which has a latency of 16376 =
,you just
>>>>
>>>>type
>>>>
>>>>>that number on track's 10 vertex instance and so vertex takes =
care of
>>=20
>> the
>>=20
>>>>>rest 31 audio tracks again meaning that it delays all other =
tracks in
>>=20
>> a
>>=20
>>>>way
>>>>
>>>>>that all have this 16376 latency, menaing again that it just =
adds 12
samples
>>>>>to track 10 and lives all other 31 audio tracks with same =
16384 latency
>>>>
>>>>!!
>>>>
>>>>>Isn't that clever ??
>>>>>Now you say you put a plugin on track 4 of submix 2 that has =
a latency
>>>
>>>of
>>>
>>>>>256 ms (you have here to translate it to samples as to have =
it on your
>>>
>>>latency
>>>
>>>>>list) this is 1290 samples ,plus the 12 samples submix 2 =
introduces
(Paris
>>>>>feature) you will have a total of 1302.
>>>>>Just type 1302 on track's 4 vertex instance and vertex will =
take this
>>=20
>> very
>>=20
>>>>>same track to the 16384 latency situation !
>>>>>This very clever delay compensator DOES not add the latencies =
but uses
>>>
>>>the
>>>
>>>>>biggest amoung all instances and alligns the rest !
>>>>>I hope this helps.
>>>>>Regards,
>>>>>Dimitrios
>>>>>
>>>>>"Phil Aiken" <asdf@asdf.sdf> wrote:
>>>>>
>>>>>>
>>>>>>I am a little unclear still....
>>>>>>For arguments sake, let's say I have a 32 track project on 2 =
cards,
>>=20
>> with
>>=20
>>>>>>plugins of various latencies...track 1 has 16384 ms. track =
10 has 16376
>>>>>
>>>>>ms,
>>>>>
>>>>>>and track 20 (track 4 of submix 2) has 256 ms latency. What =
would be
>>=20
>> the
>>=20
>>>>>>procedure with Vertex to even all tracks out across the =
project?
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>Chas. Duncan <duncan5199ATsbcglobalDOTnet@> wrote:
>>>>>>
>>>>>>>OK, that's understood then -- max latency not an issue. =
Cool. And
>>=20
>> I
>>=20
>>>>>>>had an email exchange with the developer today regarding 98 =
-- he
says
>>>>>>>it shouldn't be a problem and encouraged me to try the =
demo. Which
>>>>>>>I'll do, as soon as I'm done with this batch of mixes I'm =
busy with
>>>>>>>right now (don't want to throw *anything* new into this =
system until
>>>>>>>this job is done). But, if he gets this "manual latency" =
compensator
>>>>>>>gizmo working, I'll buy just for that and for the extra =
solo and mute
>>>>>>>capability.
>>>>>>>
>>>>>>>-- thanks for keeping on top of these developments -- much =
appreciated
>>>>>>>-- chas.
>>>>>>>
>>>>>>>On 23 Jan 2007 04:25:42 +1000, "Dimitrios" =
<musurgio@otenet.gr> wrote:
>>>>>>>
>>>>>>>
>>>>>>>>Well there is no pick from the list thing.
>>>>>>>>If you read all the posts you will understand that the =
latency is
due
>>>>>
>>>>>to
>>>>>
>>>>>>>>the amount you manually type on a ceratin vertex instance =
vst plugin.
>>>>>>>>so if you put a 64 samples latent vst plugin you just type =
64=20
>>>>>
>>>>>and all other
>>>>>
>>>>>>>>audio tracks get delayed that amount !
>>>>>>>>The author just asks how much would be the maximum =
possible latency
>>>
>>>needed
>>>
>>>>>>>>because the 132000 maximum (only maximum if you will ever =
reach that
>>>>
>>>>)
>>>>
>>>>>>the
>>>>>>
>>>>>>>>author suggests uses 1 mb memory per vertex instance , so =
for 32
audio
>>>>>>
>>>>>>tracks
>>>>>>
>>>>>>>>with vertex 32mb will be needed, for 64 paris audio tracks =
with vertex
>>>>>>
>>>>>>64
>>>>>>
>>>>>>>>mb will be needed.
>>>>>>>>I aggree with the author's 132000 samples as maximum ,if =
you will
ever
>>>>>>
>>>>>>reach
>>>>>>
>>>>>>>>that I say again.
>>>>>>>>Normally you would never pass 1000 without uad1 plugins...
>>>>>>>>Regards,
>>>>>>>>Dimitrios
>>>>>>>>Chas. Duncan <duncan5199ATsbcglobalDOTnet@> wrote:
>>>>>>>>
>>>>>>>>>Gene/Dimitrios:
>>>>>>>>>
>>>>>>>>>Would it even be necessary to "pick from a list" or =
"assign" total
>>>>>>>>>delay? Seems like the total delay would simply be as low =
(or as
high)
>>>>>>>>>as needed to compensate for the plugins used. (Unless =
I'm missing
>>>>>>>>>something, which is always a possibility...)
>>>>>>>>>
>>>>>>>>>As for me -- I'm still on 98, 512 ram -- could I run this =
thing
right
>>>>>>>>>now, just to compensate for EDS fx offsets, submix =
offsets, etc.?
>>>>>>>>>
>>>>>>>>>-- interested in how this turns out -- thanks -- chas.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>On 23 Jan 2007 02:54:04 +1000, "Gene Lennon"
>>>>>>>>><glennon@NOSPmyrealbox.com> wrote:
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>>"Dimitrios" <musurgio@otenet.gr> wrote:
>>>>>>>>>>
>>>>>>>>>>>Here is what the author wrote about his latency addon =
for vertex..!!
>>>>>>>>>>>Track 1 has a latency of 16384 samples. The same is =
true for track
>>>>>
>>>>>2.
>>>>>
>>>>>>>>As
>>>>>>>>
>>>>>>>>>>>track 1 and track 2 have the same latency they are =
already in
sync,
>>>>>>
>>>>>>but
>>>>>>
>>>>>>>>>>all
>>>>>>>>>>
>>>>>>>>>>>other tracks (the remaining 46 tracks) have to be =
delayed by 16384
>>>>>
>>>>>samples,
>>>>>
>>>>>>>>>>>not 32768.
>>>>>>>>>>>
>>>>>>>>>>>Take another example: Track 1 has a plug-in with 16384 =
samples
of
>>>>
>>>>latency.
>>>>
>>>>>>>>>>>Track 2 has a plug-in with a latency of 8192 samples. =
What FaderWorks
>>>>>>>>
>>>>>>>>will
>>>>>>>>
>>>>>>>>>>>do is: Tracks 1 will pass through as it is, track 2 =
will be delayed
>>>>>>
>>>>>>by
>>>>>>
>>>>>>>>8192
>>>>>>>>
>>>>>>>>>>>samples and all other tracks will be delayed by 16384 =
samples.
>>>>>>>>>>>
>>>>>>>>>>>What counts for the overall latency is the largest =
latency of
any
>>>>
>>>>track.
>>>>
>>>>>>>>>>>You calculate the sum of latencies only for individual =
tracks
when
>>>>>
>>>>>you
>>>>>
>>>>>>>>e.g.
>>>>>>>>
>>>>>>>>>>>put several uad1 behind on the same track.
>>>>>>>>>>>
>>>>>>>>>>>ISN'T that WHAT WE WANT ? !!!
>>>>>>>>>>>If we don't buy this vertex we have to jump off Paris =
!! :)
>>>>>>>>>>>Regards,
>>>>>>>>>>>Dimitrios=20
>>>>>>>>>>>
>>>>>>>>>>>"Dimitrios" <musurgio@otenet.gr> wrote:
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>That is what we want, but extremely high playback =
latencies will
>>=20
>> probably
>>=20
>>>>>>>>>>cause a delay between fader and mute actions and audible =
execution
>>>>
>>>>(and
>>>>
>>>>>>>>also
>>>>>>>>
>>>>>>>>>>delay meters). I need to make automation decisions with =
effects
in
>>>>
>>>>place,
>>>>
>>>>>>>>>>so extremely long delays could be problematic.=20
>>>>>>>>>>Any chance we could pick from a list or assign a total =
delay?
>>>>>>>>>>Gene
>>>>>>>>>>This is exciting.
>>>>>>>>>
>>=20
I choose Polesoft Lockspam to fight spam, and you?
http://www.polesoft.com/refer.html
------=_NextPart_000_007E_01C73EFB.C562FA20
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>If this latency compensator shows up in =
two weeks=20
I'll be floored.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>I'll be surprised whenever it shows =
up. =20
$45? Duh.</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>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; =
BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
<DIV>"DJ" <<A=20
=
href=3D"http://www.aarrrrggghhh!!!.com">www.aarrrrggghhh!!!.com</A>> =
wrote in=20
message <A =
href=3D"news:45b65d47@linux">news:45b65d47@linux</A>...</DIV>
<DIV><FONT face=3DArial size=3D2>ROTFL!!!!!</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>(patience gwasshoppa')</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>;o)</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:45b655ee@linux">news:45b655ee@linux</A>...</DIV>
<DIV><FONT face=3DArial size=3D2>A couple of weeks?!?! That's =
alot of=20
latency.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Tom</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV> </DIV>
<BLOCKQUOTE=20
style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; =
BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
<DIV>"Dimitrios" <<A=20
href=3D"mailto:musurgio@otenet.gr">musurgio@otenet.gr</A>> =
wrote in=20
message <A=20
=
href=3D"news:45b64aaa$1@linux">news:45b64aaa$1@linux</A>...</DIV><BR>Dear=
=20
Jeff,<BR>This is what makes this author a nice guy ...<BR>I =
proposed it to=20
him to be added on his vertex and he reacted in a very =
positive<BR>way=20
improving my idea and promissing a couple of weeks for this update =
to<BR>his vertex that will include the latency =
compensator.<BR>Hope this=20
helps.<BR>Regards,<BR>Dimitrios<BR>Jeff hoover <<A=20
=
href=3D"mailto:jkhoover@excite-DOT-com">jkhoover@excite-DOT-com</A>>=20
wrote:<BR>>So is the compensator already in the product, or do =
we have=20
a timeline <BR>>for =
it?<BR>><BR>>Hoov<BR>><BR>>Dimitrios=20
wrote:<BR>>> Great Chris !<BR>>> Please email him too =
saying=20
that you are a Paris users that has been informed<BR>>> =
about the=20
latency compensator !<BR>>> Regards,<BR>>>=20
Dimitrios<BR>>> <BR>>> "Chris Lang" <<A=20
href=3D"mailto:yo@yo.yo">yo@yo.yo</A>> wrote:<BR>>>=20
<BR>>>>That is awesome. Buying it=20
=
now...<BR>>>><BR>>>>Chris <BR>>>><BR>>>&g=
t;<BR>>>>"Dimitrios"=20
<<A =
href=3D"mailto:musurgio@otenet.gr">musurgio@otenet.gr</A>>=20
wrote:<BR>>>><BR>>>>>Dear=20
Phil,<BR>>>>>You probably have read that I said allign =
all 31=20
audio tracks to 16376<BR>>> <BR>>> I<BR>>>=20
<BR>>>>>meant to 16384 which already was so, so it =
just adds=20
12 samples to=20
=
track<BR>>>>>10.<BR>>>>>Regards, <BR>>>>&=
gt;Dimitrios<BR>>>>><BR>>>>> "Dimitrios"=20
<<A =
href=3D"mailto:musurgio@otenet.gr">musurgio@otenet.gr</A>>=20
wrote:<BR>>>>><BR>>>>>>Hi=20
Phil,<BR>>>>>>According to the author you just have =
to type=20
the latency on the=20
=
vertex<BR>>>>><BR>>>>>instance <BR>>>>>=
;<BR>>>>>>you=20
are putting a plugin and then vertex takes care of the rest=20
!!<BR>>>>>>Here is how it will=20
work...<BR>>>>>>You open vertex dsp on every audio =
track on=20
your 2 card system.<BR>>>>>>You can save that as a =
template=20
for further projects.<BR>>>>>>Now lets say you open =
on=20
track 1 a plugin that has 16384 samples =
latency<BR>>>>>>,=20
you just type 16384 on that vertex's instance of audio track 1=20
and<BR>vertex<BR>>>>>>takes care of the rest 31 =
audio=20
tracks to get alligned.<BR>>>>>>Now you put a =
plugin on=20
track 10 which has a latency of 16376 ,you=20
=
just<BR>>>>><BR>>>>>type <BR>>>>><BR>&=
gt;>>>>that=20
number on track's 10 vertex instance and so vertex takes care=20
of<BR>>> <BR>>> the<BR>>> =
<BR>>>>>>rest=20
31 audio tracks again meaning that it delays all other tracks=20
in<BR>>> <BR>>> a<BR>>>=20
=
<BR>>>>>way<BR>>>>> <BR>>>>>>that=20
all have this 16376 latency, menaing again that it just adds=20
12<BR>samples<BR>>>>>>to track 10 and lives all =
other 31=20
audio tracks with same 16384=20
=
latency<BR>>>>><BR>>>>>!! <BR>>>>><BR>=
>>>>>Isn't=20
that clever ??<BR>>>>>>Now you say you put a plugin =
on=20
track 4 of submix 2 that has a=20
=
latency<BR>>>><BR>>>>of <BR>>>><BR>>>>=
>>256=20
ms (you have here to translate it to samples as to have it on=20
=
your<BR>>>><BR>>>>latency <BR>>>><BR>>>&g=
t;>>list)=20
this is 1290 samples ,plus the 12 samples submix 2=20
introduces<BR>(Paris<BR>>>>>>feature) you will have =
a total=20
of 1302.<BR>>>>>>Just type 1302 on track's 4 vertex =
instance and vertex will take this<BR>>> <BR>>>=20
very<BR>>> <BR>>>>>>same track to the 16384 =
latency=20
situation !<BR>>>>>>This very clever delay =
compensator DOES=20
not add the latencies but=20
=
uses<BR>>>><BR>>>>the <BR>>>><BR>>>>&g=
t;>biggest=20
amoung all instances and alligns the rest =
!<BR>>>>>>I hope=20
this=20
=
helps.<BR>>>>>>Regards, <BR>>>>>>Dimitrios<B=
R>>>>>><BR>>>>>> "Phil=20
Aiken" <<A href=3D"mailto:asdf@asdf.sdf">asdf@asdf.sdf</A>>=20
=
wrote:<BR>>>>>><BR>>>>>>> <BR>>>>=
;>>>I=20
am a little unclear still....<BR>>>>>>>For =
arguments=20
sake, let's say I have a 32 track project on 2 cards,<BR>>>=20
<BR>>> with<BR>>> <BR>>>>>>>plugins =
of=20
various latencies...track 1 has 16384 ms. track 10 has=20
=
16376<BR>>>>>><BR>>>>>>ms, <BR>>>>&=
gt;><BR>>>>>>>and=20
track 20 (track 4 of submix 2) has 256 ms latency. What would=20
be<BR>>> <BR>>> the<BR>>>=20
<BR>>>>>>>procedure with Vertex to even all =
tracks out=20
across the=20
=
project?<BR>>>>>>> <BR>>>>>>><BR>>&=
gt;>>>><BR>>>>>>> <BR>>>>>>&g=
t;Chas.=20
Duncan <duncan5199ATsbcglobalDOTnet@>=20
=
wrote:<BR>>>>>>> <BR> >>>>>>>OK,= 20
that's understood then -- max latency not an issue. =
Cool. =20
And<BR>>> <BR>>> I<BR>>>=20
<BR>>>>>>>>had an email exchange with the =
developer=20
today regarding 98 -- he<BR>says<BR>>>>>>>>it =
shouldn't be a problem and encouraged me to try the demo. =20
Which<BR> >>>>>>>I'll do, as soon as I'm done =
with=20
this batch of mixes I'm busy =
with<BR> >>>>>>>righ t now=20
(don't want to throw *anything* new into this system=20
until<BR> >>>>>>>this job is done). But, =
if he=20
gets this "manual latency"=20
compensator<BR> >>>>>>>gizm o working, I'll buy =
just=20
for that and for the extra solo and=20
=
mute<BR> >>>>>>>capa bility. <BR>>>>>>&g=
t;><BR> >>>>>>>--=2 0
thanks for keeping on top of these developments -- much=20
appreciated<BR> >>>>>>>--=2 0
=
chas.<BR>>>>>>>> <BR>>>>>>>>On =
23=20
Jan 2007 04:25:42 +1000, "Dimitrios" <<A=20
href=3D"mailto:musurgio@otenet.gr">musurgio@otenet.gr</A>>=20
=
wrote:<BR>>>>>>>> <BR>>>>>>>> <BR=
> >>>>>>>& ;gt;Well=20
there is no pick from the list=20
thing.<BR> >>>>>>>& ;gt;If you read all the =
posts you=20
will understand that the latency=20
=
is<BR>due<BR>>>>>><BR >>>>>>to<BR>>>&g=
t;>><BR> >>>>>>>& ;gt;the=20
amount you manually type on a ceratin vertex instance vst=20
plugin.<BR> >>>>>>>& ;gt;so if you put a 64 =
samples=20
latent vst plugin you just type 64=20
<BR>>>>>><BR>>>>>>and all=20
=
other<BR>>>>>><BR> >>>>>>>& ;gt;audio=20
tracks get delayed that amount =
!<BR> >>>>>>>& ;gt;The=20
author just asks how much would be the maximum possible=20
=
latency<BR>>>><BR>>>>needed <BR>>>><BR>>>=
>>>>>>because=20
the 132000 maximum (only maximum if you will ever reach=20
=
that<BR>>>>><BR>>>>>) <BR>>>>><BR>>=
>>>>>the<BR>>>>>>> <BR>>>>>&g=
t;>>>author=20
suggests uses 1 mb memory per vertex instance , so for=20
=
32<BR>audio<BR>>>>>>> <BR>>>>>>>tracks=
<BR>>>>>>><BR> >>>>>>>& ;gt;with=20
vertex 32mb will be needed, for 64 paris audio tracks with=20
=
vertex<BR>>>>>>> <BR>>>>>>>64<BR>>&=
gt;>>>><BR> >>>>>>>& ;gt;mb=20
will be needed.<BR> >>>>>>>& ;gt;I aggree with =
the=20
author's 132000 samples as maximum ,if you=20
=
will<BR>ever<BR>>>>>>> <BR>>>>>>>reach=
<BR>>>>>>><BR> >>>>>>>& ;gt;that=20
I say again.<BR> >>>>>>>& ;gt;Normally you would =
never=20
pass 1000 without uad1=20
=
plugins...<BR> >>>>>>>& ;gt;Regards, <BR>>>>>=
;>>>>Dimitrios<BR> >>>>>>>& ;gt;Chas.=20
Duncan <duncan5199ATsbcglobalDOTnet@>=20
=
wrote:<BR> >>>>>>>& ;gt; <BR>>>>>>>>=
;>>Gene/Dimitrios:<BR> >>>>>>>& ;gt;> <BR>>&=
gt;>>>>>>>W ould=20
it even be necessary to "pick from a list" or "assign"=20
total<BR> >>>>>>>& ;gt;>delay? Seems =
like the=20
total delay would simply be as low (or=20
as<BR>high)<BR> >>>>>>>& ;gt;>as needed to =
compensate=20
for the plugins used. (Unless I'm=20
missing<BR> >>>>>>>& ;gt;>something, which is =
always=20
a=20
=
possibility...)<BR> >>>>>>>& ;gt;> <BR>>>>&g=
t;>>>>>As=20
for me -- I'm still on 98, 512 ram -- could I run this=20
thing<BR>right<BR> >>>>>>>& ;gt;>now, just to =
compensate for EDS fx offsets, submix offsets,=20
=
etc.?<BR> >>>>>>>& ;gt;> <BR>>>>>>>=
>>>--=20
interested in how this turns out -- thanks --=20
=
chas.<BR> >>>>>>>& ;gt;> <BR>>>>>>>=
>>><BR> >>>>>>>& ;gt;>On=20
23 Jan 2007 02:54:04 +1000, "Gene=20
Lennon"<BR> >>>>>>>& ;gt;>< <A=20
=
href=3D"mailto:glennon@NOSPmyrealbox.com">glennon@NOSPmyrealbox.com</A>&g=
t;=20
=
wrote:<BR> >>>>>>>& ;gt;> <BR>>>>>>>=
;>>><BR> >>>>>>>& ;gt;>> "Dimitrios"=20
<<A =
href=3D"mailto:musurgio@otenet.gr">musurgio@otenet.gr</A>>=20
=
wrote:<BR> >>>>>>>& ;gt;>> <BR>>>>>>=
;>>>>>>Here=20
is what the author wrote about his latency addon for=20
vertex..!!<BR> >>>>>>>& ;gt;>>>Track 1 =
has a=20
latency of 16384 samples. The same is true for=20
=
track<BR>>>>>><BR>>>>>>2. <BR>>>>&g=
t;><BR> >>>>>>>& ;gt;As <BR>>>>>>>&=
gt;><BR> >>>>>>>& ;gt;>>>track=20
1 and track 2 have the same latency they are already=20
=
in<BR>sync,<BR>>>>>>> <BR>>>>>>>but<BR=
>>>>>>><BR> >>>>>>>& ;gt;>>all <=
BR> >>>>>>>& ;gt;>> <BR>>>>>>>&g=
t;>>>>other=20
tracks (the remaining 46 tracks) have to be delayed by=20
=
16384<BR>>>>>><BR>>>>>>samples, <BR>>>=
>>><BR> >>>>>>>& ;gt;>>>not=20
=
32768.<BR> >>>>>>>& ;gt;>>> <BR>>>>>=
;>>>>>>>Tak e=20
another example: Track 1 has a plug-in with 16384=20
=
samples<BR>of<BR>>>>><BR>>>>>latency. <BR>>>=
>><BR> >>>>>>>& ;gt;>>>Track=20
2 has a plug-in with a latency of 8192 samples. What=20
=
FaderWorks<BR> >>>>>>>& ;gt; <BR>>>>>>>=
;>>will<BR> >>>>>>>& ;gt; <BR>>>>>>=
>>>>>>do=20
is: Tracks 1 will pass through as it is, track 2 will be=20
=
delayed<BR>>>>>>> <BR>>>>>>>by<BR>>=
>>>>><BR> >>>>>>>& ;gt;8192 <BR>>>&=
gt;>>>>><BR> >>>>>>>& ;gt;>>>sa=
mples=20
and all other tracks will be delayed by 16384=20
=
samples.<BR> >>>>>>>& ;gt;>>> <BR>>>>&=
gt;>>>>>>>W hat=20
counts for the overall latency is the largest latency=20
=
of<BR>any<BR>>>>><BR>>>>>track. <BR>>>>&g=
t;<BR> >>>>>>>& ;gt;>>>You=20
calculate the sum of latencies only for individual=20
=
tracks<BR>when<BR>>>>>> <BR>>>>>>you<BR>>=
>>>><BR> >>>>>>>& ;gt;e.g. <BR>>>>&=
gt;>>>><BR> >>>>>>>& ;gt;>>>put=20
several uad1 behind on the same=20
=
track.<BR> >>>>>>>& ;gt;>>> <BR>>>>>=
;>>>>>>>ISN 'T=20
that WHAT WE WANT ? =
!!!<BR> >>>>>>>& ;gt;>>>If=20
we don't buy this vertex we have to jump off Paris !!=20
=
:)<BR> >>>>>>>& ;gt;>>>Regards, <BR>>>>=
;>>>>>>>&am p;gt;Dimitrios=20
=
<BR> >>>>>>>& ;gt;>>> <BR>>>>>>&=
gt;>>>>>"Dimitrios"=20
<<A =
href=3D"mailto:musurgio@otenet.gr">musurgio@otenet.gr</A>>=20
=
wrote:<BR> >>>>>>>& ;gt;>>> <BR>>>>>=
;>>>>>><BR> >>>>>>>& ;gt;>>That=
=20
is what we want, but extremely high playback latencies =
will<BR>>>=20
<BR>>> probably<BR>>>=20
<BR> >>>>>>>& ;gt;>>cause a delay between =
fader=20
and mute actions and audible=20
=
execution<BR>>>>><BR>>>>>(and <BR>>>>>=
<BR> >>>>>>>& ;gt;also <BR> >>>>>>>& ;=
gt;<BR> >>>>>>>& ;gt;>>delay=20
meters). I need to make automation decisions with=20
=
effects<BR>in<BR>>>>><BR>>>>>place, <BR>>>&g=
t;><BR> >>>>>>>& ;gt;>>so=20
extremely long delays could be problematic.=20
<BR> >>>>>>>& ;gt;>>Any chance we could =
pick from=20
a list or assign a total=20
=
delay?<BR> >>>>>>>& ;gt;>>Gene <BR>>>>>=
;>>>>>>This=20
is exciting.<BR> >>>>>>>& ;gt;> <BR>>>=20
<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_007E_01C73EFB.C562FA20--
|
|
|
|
Goto Forum:
Current Time: Sat Apr 27 02:24:51 PDT 2024
Total time taken to generate the page: 0.04857 seconds
|
The PARIS Forums
Search
Help
Members
Register
Login
Home
