When will PROTOOLS get a PING FUNCTION?

[killah_trakz]

I’ve been going CRAZY trying to use my hardware inserts in protools without comb filtering and phasing.

I’m using Apollo X series. I’ve turned the latency too OFF. I’ve measured all the timing. Unfortunately I cannot put a negative in the I/O Delay comp setting.

It’s sad that this company is hindering itself by creating BOTTLENECKS for NO apparent reason. I just want to WORK. That’s it!


Sent from my iPhone using Tapatalk

[Darryl Ramm]

Why would you want to put in a negative value? That is not how this works.

What exact outboard hardware are you using? (Some has variable latency values) What latency have you measured? What exactly have you entered for that latency? And you are certain that if you bypass all the hardware inserts you do not have this problem happening due to other causes?

Explain exactly what you are doing like we are idiots…

[killah_trakz]

Originally Posted by Darryl Ramm

Why would you want to put in a negative value? That is not how this works.

What exact outboard hardware are you using? (Some has variable latency values) What latency have you measured? What exactly have you entered for that latency? And you are certain that if you bypass all the hardware inserts you do not have this problem happening due to other causes?

I’ve spent days and hours testing ALL the latencies and sample rates. The Apollo X is coming in AHEAD of what protools is able to provide.

I’m not the only person going through this. I done loopback tests and more.

And the aux busses ……. I just want to throw the computer out the window.


Sent from my iPhone using Tapatalk

[audiogamble]

I know. It's a pain that PT doesn't have this. Do you have logic pro also? I have a workflow that uses logic's ping to extract the numbers for pro tools.

[audiogamble]

Also as weird as it seems, if your hw insert delays are currently set to zero then for sure your inserts will come in ahead of regular audio.

[killah_trakz]

Originally Posted by audiogamble

I know. It's a pain that PT doesn't have this. Do you have logic pro also? I have a workflow that uses logic's ping to extract the numbers for pro tools.

I’ve tried that with reaper because it reports the samples and more. Stuck those numbers into protools and nope. Doesn’t work.


Sent from my iPhone using Tapatalk

[killah_trakz]

Originally Posted by audiogamble

I know. It's a pain that PT doesn't have this. Do you have logic pro also? I have a workflow that uses logic's ping to extract the numbers for pro tools.

Are you using an Apollo ?


Sent from my iPhone using Tapatalk

[audiogamble]

Originally Posted by killah_trakz

I’ve tried that with reaper because it reports the samples and more. Stuck those numbers into protools and nope. Doesn’t work.


Sent from my iPhone using Tapatalk

I'm not familiar with reaper's feature for this. What sort of values is it giving you?

[Darryl Ramm]

Yet it clearly works for many users. And others complaining about negative time offsets recently had the issue fixed/explained (by me) when they provided details (that was caused by using aggregate IO). Just complaining like this here with no useful info is unlikely to get you help for any of 1. You are doing something wrong (or “wrong” according to Pro Tools); or 2 something is broken in Pro Tools, or 3 something is broken in UAD hardware or software.

And if it’s a bug somewhere you are going to have to work out where and be able to point the finger with enough detail to get anybody to fix stuff.

Maybe let’s start with what you are running and what the playback engine is set to (not using aggregate IO right?… that can cause negative timing correction issues) you measure as a loop back latency. And what outboard gear you are trying use and what latency you measure for that. If you have a box with outrageous latency, it’s not going to be intended for use as an insert within a DAW, more it would be intended to use on the main output (where everything just gets delayed and there is no latency comp. And you have the UAD console totally disabled/out of the picture here? Esp. No high-latency UAD plugins running in the console (or Pro Tools?).

If you already have it down to a reproducible demo/test and you can describe it and you are confident it’s a bug then go ahead and file a support case, you can post the case# here and that may help Avid folks follow up.

How much “ahead” are you seeing this stuff shifted? Pro tools sure will get stuff wrong by say 10 or more samples. Is that what you are seeing?

[albee1952]

What hardware are you jumping thru hoops to make work? Dollars to donuts, staying in the box with plugins will give equal results without all the hassle