EZ3 latency reported by DAWs

[MintberryCrunch]

Can you please explain the latency values I get (reported by DAWs):

( BR = Bright Room  ;   MR = Main Room  ;  TR = Tight Room )

 

sample rate 44.1 kHz :

BR:  9 samples  ( 0.2 ms )

MR:  6 samples  ( 0.14 ms )

TR:  3 samples  ( 0.068 ms )

 

sample rate 48 kHz :

BR:  27 samples  ( 0.56 ms )

MR:  24 samples  ( 0.5 ms )

TR:  21 samples  ( 0.44 ms )

 

Does the EZ3 audio (FX) engine introduce latency? Even old EZXes  [i.e. EZ2 stock lib – 17 samples  ( 0.35 ms )]  show some samples of latency when loaded into EZ3 at 48 kHz sample rate.

Why is there quite a big difference ( i.e.  6 samples vs. 24 samples ) regarding 44.1 kHz vs. 48 kHz?

Why are these by-DAW-shown values not reported in EZ3 stand alone (no matter what kit I choose: the reported latency stays the same) ; (if I switch to 48kHz in stand alone I cannot see the additional latency that is reported by DAWs -which is 3-4 times higher than at 44.1 kHz-)

Why is the amount of latency TR < MR < BR ?

 

The Software Drumming Forum - tips & tricks + discussing drum samplers

Topic

[Anton Nordmark]

This depends on the preset. Different presets use different mixing effects that each can introduce latency to produce a song-ready sound.

You’ll find that the Original Mix for all 3 core libraries introduces 0 ms latency (according to my own FL Studio).

Your reading of 0.14 ms for Main Room is specific to the default preset (Michael Ilbert > Studio Full Mic > Basic).

Hope this helps!

Anton Nordmark – Toontrack
UX Designer

[MintberryCrunch]

Anton Nordmark wrote:

You’ll find that the Original Mix for all 3 core libraries introduces 0 ms latency

I get the following latency report when loading “Original Mix” (in different DAWs) :

at 48 khz :  17 samples ( 0.35 ms )  ;  at 88.2 khz :  32 samples  ;  at 96 khz :  35 samples

 

Why is only 44.1 kHz project sample rate a 0 from EZ3 latency report (and 48+ kHz significantly higher in this comparativeness with those marginal latencies)?

 

Why has EZDrummer2 always kept quiet about those (preset) latencies  -> reported latency always: 0 samples  no matter what preset has been loaded or what project sample rate has been set.

 

…and again the question: Why are these by-DAW-shown values not reported in EZ3 stand alone (and also not in SD3 standalnoe)?

(When a preset adds around 1.5 ms -which I found with some EZXes- then the audio stream output latency is of course not equivalent to the reported audio driver latency.)

The Software Drumming Forum - tips & tricks + discussing drum samplers

[Bear-Faced Cow]

Those latencies are not because of EZD3 itself. Those are from your DAW needing processing time to cross-sample from 44.1 (which the core library was recorded) to the other audio rates. They don’t just magically play back in other rates and going from multiples of 44.1 to multiples of 48 takes more work.

jord

---

Jordan L. Chilcott

Web Site: https://jordanchilcottmusic.com/

• This post was modified 3 years ago by Bear-Faced Cow.

[MintberryCrunch]

Bear-Faced Cow wrote:

Those latencies are not because of EZD3 itself

Never have seen this with other drum samplers: when loading SSD5.5 or Kontakt drum samplers always 0 samples are reported (no matter what the sample rate is). AddictiveDrums2 always reports 64 samples (no matter what the sample rate is).

 

So I doubt it has nothing to do with EZD3 (SD3) itself…

Also, internal EZ3 (/SD3) audio FX affect the reported latency values.

 

And what about EZ2 (SD2) latency report? Has it always been wrong (/not reporting latency)?

The Software Drumming Forum - tips & tricks + discussing drum samplers

[Bear-Faced Cow]

First I would find it difficult to believe that any software playing back a 44.1KHz waveform at a different multiple would be zero latency. Any software claiming zero when cross sampling is probably not reporting latency properly. There will always be some processing required to either upsample or downsample.

EZD3 is being rather honest in its usage, which is not really that huge. At that point I’d worry more about the type of audio interface or other latency inducing plug-ins within a DAW.

At least AD is honest enough to adding worst case overhead of .66ms at 96KHz, which also means at 44.1KHz that same 64 samples equals >1.5ms which is still imperceptible. My guess is they are probably reserving some for lookahead.

jord

---

Jordan L. Chilcott

Web Site: https://jordanchilcottmusic.com/

[MintberryCrunch]

Thanks for your answer, Jord

I don’t say that this latency is an issue (even not when it comes to real time e-drumming) – but it’s good to know even quite marginal latencies for real time tasks as we have to deal with a latency chain.

To me the question is why is there a kind of chaos with those reports: EZ3 reports it as a plugin but not in standalone, EZ2 has never reported anything (even not as plugin)…

The Software Drumming Forum - tips & tricks + discussing drum samplers

[Olof Hermansson]

MintberryCrunch wrote:

And what about EZ2 (SD2) latency report? Has it always been wrong (/not reporting latency)?

Yes, they have never reported their latency to the host.

Olof Hermansson - Toontrack
Coder

• This post was modified 3 years ago by Daniel Dermes.

[Bear-Faced Cow]

gotta love that Quote feature… Lol!

jord

---

Jordan L. Chilcott

Web Site: https://jordanchilcottmusic.com/

[Author]

Replies