Good catch. Thanks!!
Confirmed still not working in 9.5.1. Such a shame.
I might be kicking in open doors here but just as a tip you should always measure “ping” with a dry signal.
If you have any kind distortion or reverb or such there is a chance you might get a slightly off delay measurement because cubase is trying to measure a very short ping.
If ýou have a digital reverb unit for instance you should set it to 100% “dry” before you measure. That way you get both your D/A-A/D delay and the delay you get from the digital reverb unit itself (as an example).
It sucks because using 64 bit actually is more efficient on my system but I cannot use it due to the ping not working in 64 bit mode.
I’m still waiting for someone at Steinberg to let us know that they are at least aware of this.
First, I am waiting for a fix my self
Second, Switch to 32 bit mode, do your pinging and save your external plugins (and/or write down the delay settings). Then switch back to 64 bit mode…
^^^Cheers for the workaround Carvin Man.
The delay settings are saved so no need to write them down. Just switch back to 64bit engine and they’re there.
Still a fiddle about IMO.
I agree, and I actually mentioned the same workaround in a previous post.
This is only effective when and only using 1 external FX at a time. What if you need to eq and compress or even run your signal thru 2 fx 'pieces of gear before coming back into Cubase? This is where the delay ping is required. Who’s not to say that 64 bit processing doesn’t add some delay… how would one know since it’s not working in 64 bit
we have a couple of threads going discussing this, but this has been reported now that we have a full repro.
Glad to hear that. Thank You!!
To put it bluntly, I don’t think anyone in this thread understand how this feature works.
If you have a interface with a fixed-latency driver (which is the case with my Apollos), Cubase already knows about your interface round trip delay. This is the starting point ‘guess’ that Cubase takes to give the correct delay compensation in your DAW. So if you do a Ping test and get a ‘0’, that means the guess was correct and everything is working as it should.
So again if you directly route a cable from your interface output 1 to your interface input 1 and did a ping test, … it SHOULD report 0. Whether your buffer setting is at 32 samples or 1024 samples. Cubase already pre-emptivley knows about this delay… so the Ping test is for calculating any ‘extra’ stuff…
If you have mostly Analog Outboard gear, (which has no inherent latency or delay) this should mostly read 0. However, if you have something like a ADAT output converter, or other digital process or digital FX that has some latency to it…this is where Cubase tries to calculate that and compensate it for you. Its possible your interface itself might have some onboard-DSP processes that introduce extra latency beyond the advertised ‘guess’ too.
At leasts that is how I understand how it works.
If you have an interface driver that constantly changes latency…then Cubase cant really help you much. Otherwise, like someone said, just make sure before a final bounce to Ping everybody.
digi001, I completely disagree with your assessment and your understanding of the issue. Have you exited recorded audio to an analog external device and then returned it to the Cubase Project? The ping test exists and there’s a reason why it exists, and, trust me, not for the reasons you suggest.
I took a drum loop…duplicated it.
Ran it to my 1176 in all-buttons mode via External FX
Blended it back into the original. Did this at 64 samples and 1024 samples. Ping read ‘0’ both times.
Heard no phasing or anything weird going on.
Hmm I can check again…
Is anyone else on a Universal Audio Apollo?
I’m on the latest version of Cubase 9 by the way…not 9.5
To state the obvious - have you tried it in 32 bit mode? 64 bit mode could be the obvious cause of your problem.
I am not having a problem with this.
Just trying to explain to everyone on this thread how External FX works.
I believe I was in 64 bit mode.
0 MEANS IT IS WORKING!!!
ZERO IS GOOD!!!
(at least thats how I understand it. working for me. Macbook Pro, El Capitain, Cubase 9, 3 Apollos and a studio full of analog gear)
No. Try it in 32 bit mode.
I don’t think Cubase 9 has 64 bit option. So the above statement isn’t true. I was in 32 bit mode.
However…i just tried this with my demo version of Cubase 9.5 and it works in both 32 and 64 bit mixing modes.
It’s possible this topic doesn’t apply to you if you only use a computer interface and don’t have outboard converters…I dunno.
It still ‘can’ apply to me for certain situations.
For example, I just inserted a UAD Neve 1073 into my Interface insert on my Apollo.
This means the DSP inside my interface now is processing the incoming signal. Since it is a intensive computer algorithm with oversampling and other things going on (not an analog process) it has a latency associated with it. Cubase doesn’t know about this one because their isn’t shared some Latency Compensation scheme between my Interface Plugins and my DAW (its not that complex). So it now sounds out of phase and weird.
I hit the ‘Ping’ button and it calculates 1.15ms which sounds about right.
I listen back and now everything sounds in phase and correct.
OR another example, like you said…if I use an external converter attached to my Interface ADAT output/input. Then depending on the converter this may add some digital latency which Cubase doesn’t know about.
However…most of the reason I go out-of-the-box is to use Analog Gear…not digital. I have 32 channels of I/O on my 3 Apollos and they are all synced up to an external Clock source that Cubase also sees (not sure if the clock matters or not)
Everything working good here.
So yeh when I say ‘0’ is good and what the Ping should read…that is assuming you are 1: using Analog Hardware and 2: using your interface I/O which has a reliable and consistent latency which is correctly being reported to Cubase.
Anyone else saying other things on this thread are WRONG from everything that I can tell.
Glad to hear that it’s working for you, thanks for the info!
Please let the others who are experiencing this issue continue to contribute to this thread in hopes of a solution. Ping/delay is not working for me in 64 bit mode and plenty of people have also reported this. It’s sorta like the major GUI issue that was affecting users, some were affected and other weren’t.
From my observations, I have determined that 32 bit mode works and 64 bit mode doesn’t. The Ping/Delay compensation has always been a bit funky since CB 8 and apparently it was marked as an issue by Steinberg a while ago, here:
Still hoping that Steinberg addresses this bug/issue for us users who are experiencing it.