PROTOOLS HD + SCOPE (insert delayed) by ADC perfect harmony.

[m.my91]

Hello i've just fix the latency problem i had with protools and scope.
i put scope in an insert track in protools and i calculate the latency .
scope make 0.27 ms at 96 khz with spdif in + vinco+ spdif out.(but the latency grow when you use different plugins).
01v96 + src2496 make 2.28 ms.
i have 2.55 ms of latency.
i put this value in ms in the hw insert i/o in protools.
then i can record any tdm or rtas plugins through scope insert delayed at 2.55 ms.
the result is perfect.
no latency sensation on monitoring.
mixing scope plugins with rtas or tdm give a better result than scope or digidesign plugins ising alone.
no need to use a big creamware card a pulsar 1 will make the job because you don't need to use scope mixer in the project.
only compressor ,eq ,virtaul amps,...

[garyb]

again, ProTools is working in the computer.
Scope is external to the computer.

the computer has latency for anything going into and out of it. when Scope signals go to the sequencer(ProTools), there is a known latency. there has to be because the CPU is not a realtime device. most modern sequencers compensate for this by delaying playback. this is NOT some special latency with Scope and ProTools, however.

[m.my91]

again, ProTools is working in the computer.
Scope is external to the computer.

the computer has latency for anything going into and out of it. when Scope signals go to the sequencer(ProTools), there is a known latency. there has to be because the CPU is not a realtime device. most modern sequencers compensate for this by delaying playback. this is NOT some special latency with Scope and ProTools, however.

but protools doesn't use the computer cpu.
only for rtas plugins.(and you can compensate rtas latency buffer with the "midi offest value in sample"
all other (midi tdm recording) use tdm dsp.
so protools is an external to the computer.
scope is also an external system.
but the problem is not what is doing latency or external or internal device.
the problem is how to use all this dsp in a "perfect aligned time"
use a vinco at 96 khz on spdif in out scope project in an protools insert need to put 0.27 ms to be aligned in the protools midi grid.
only thing i want is to have a "SONICCORE LATENCY CHART" for all the plugins ,like waves do:
http://aaron.headwai.com/ra/Recording%2 ... yChart.pdf

[hubird]

There once was a try on this forum to make a complete list.
It never grew big, I guess as the relevance of it is so minimal for life playing.
If you monitor directly from Scope that is.
Latency demanding plugs you'd normally only add during the mixing phase, be it in Scope or -worse- native.

[m.my91]

There once was a try on this forum to make a complete list.
It never grew big, I guess as the relevance of it is so minimal for life playing.
If you monitor directly from Scope that is.
Latency demanding plugs you'd normally only add during the mix phase.

do you know where i can find this list?

[hubird]

no, you need to search. But don't, there was no list, or hardly a start.
Maybe Atomic was involved, but I'm not sure.

Get the message, you don't win anything with your hunt, but I wish you luck in your queeste for 1/4 milliseconds delaying numbers while there a storm outside, called 'native'

[m.my91]

There once was a try on this forum to make a complete list.
It never grew big, I guess as the relevance of it is so minimal for life playing.
If you monitor directly from Scope that is.
Latency demanding plugs you'd normally only add during the mixing phase.

No i don't use scope for monitoring.
i use protools.
scope is only insered on protools track.
i don't had phase tools or sample delay plugins in the protools track for mixing after recording.
all the the delay compensation of protools scope and periphicals is mesured with a digidesign methode and then you have a value to in sample in the insert of the protools track.
the track is a monitor track i pass it in a buss and record it in another track...
on the second track there be no more latency....even in the recording result...

[m.my91]

no, you need to search. But don't, there was no list, or hardly a start.
Maybe Atomic was involved, but I'm not sure.

Get the message, you don't win anything with your hunt, but I wish you luck in your queeste for 1/4 milliseconds delaying numbers while there a storm outside, called 'native'

no because i see that when i use different plugins on insert i have to put a different value in protools hw insert.
with protools you can adjust to 0.100 ms precison.
at 2 ms really not good but at 2.55 it's perfect.
i will contact atomic perhaps wee can do this list?

[ronnie]

Could be a clock issue. Sounds like you are using SP/DIF which is known for bad sync when used for audio and clock. You have ProTools HD and Scope. How and what are you using for a clock. MIDI clock won't cut it for audio.

[hubird]

no, you need to search. But don't, there was no list, or hardly a start.
Maybe Atomic was involved, but I'm not sure.

Get the message, you don't win anything with your hunt, but I wish you luck in your queeste for 1/4 milliseconds delaying numbers while there a storm outside, called 'native'

no because i see that when i use different plugins on insert i have to put a different value in protools hw insert.
with protools you can adjust to 0.100 ms precison.
at 2 ms really not good but at 2.55 it's perfect.
i will contact atomic perhaps wee can do this list?

I see.
But if Protools offers that latency tool doesn't mean it's a law to use it...
Scope's latency (without special fx) is too low to worry about, I'd say.
I mix bands who seem to suffer from life playing latency (also backward) of 50 ms or even double and more.
I do correct the audiofiles for that, by cutting/stretching.

What do you mean with 'at 2 ms really not good but at 2.55 it's perfect'?
Technically?

[ronnie]

OMG. I'm having a Deja Vu. Maybe it's just PCI overload (as in Persistent Commenter Idiocy). I have a sudden urge to do some cutting and stretching.

[m.my91]

Could be a clock issue. Sounds like you are using SP/DIF which is known for bad sync when used for audio and clock. You have ProTools HD and Scope. How and what are you using for a clock. MIDI clock won't cut it for audio.

i use the 192 i/o wordclock by bnc...

[m.my91]

no, you need to search. But don't, there was no list, or hardly a start.
Maybe Atomic was involved, but I'm not sure.

Get the message, you don't win anything with your hunt, but I wish you luck in your queeste for 1/4 milliseconds delaying numbers while there a storm outside, called 'native'

no because i see that when i use different plugins on insert i have to put a different value in protools hw insert.
with protools you can adjust to 0.100 ms precison.
at 2 ms really not good but at 2.55 it's perfect.
i will contact atomic perhaps wee can do this list?

I see.
But if Protools offers that latency tool doesn't mean it's a law to use it...
Scope's latency (without special fx) is too low to worry about, I'd say.
I mix bands who seem to suffer from life playing latency (also backward) of 50 ms or even double and more.
I do correct the audiofiles for that, by cutting/stretching.

What do you mean with 'at 2 ms really not good but at 2.55 it's perfect'?
Technically?

you do as you want....
for me : no time stretch or cutting for being sync with the tempo grid.(recording is exaclty the same as playing tracking monitor)
for the latency value in the protools insert hw you heard a difference beetween 2 ms and 2.5 ms.
with 2 ms backward tempo gris 2.5 ms is in the tempo grid..

[m.my91]

OMG. I'm having a Deja Vu. Maybe it's just PCI overload (as in Persistent Commenter Idiocy). I have a sudden urge to do some cutting and stretching.

so spent your time cutting and streching .
but forget the groove of your music production....

[ronnie]

I wasn't referring to audio.

[garyb]

Scope is not intended to work at 192k...

[ronnie]

Scope is not intended to work at 192k...

Neither is ProTools (44 or 48)

[m.my91]

Scope is not intended to work at 192k...

so bad.
perhaps in scope 6?
if scope work at 192 khz it would be a great commercial upgrade for scope.
and why sonniccore didn't build a a16 with multi aes:ebu i/o 192 khz doublewire.
you can tell then if it's possible?

[m.my91]

Scope is not intended to work at 192k...

so bad.
perhaps in scope 6?
if scope work at 192 khz it would be a great commercial upgrade for scope.
and why sonniccore didn't build a a16 with multi aes:ebu i/o 192 khz doublewire.
because using scope plugin with other plugins (rtas tdm) work very well
you can tell then if it's possible?

[garyb]

anyone who can afford to multitrack at 192k has plenty of money to throw at the problem.
only mastering labs regularly use 192k.