MXXX Limiter look-ahead and latency reporting

[valankar]

Hello,

When I use MLimiterX with 100% look-ahead it correctly reports latency in the Settings.

When I use MXXX with a Limiter with 100% look-ahead, it reports no latency in the Settings. In fact, changing the look-ahead to 400% also reports no latency. This seems a bug, does MXXX not report latency properly?

[DarkStar]

Confirmed. MXXX (v12.09rc1) is not reporting the latency to the host (even after clicking the Panic button).

[MeldaProduction]

Hmmm, I just checked with 12.09 and it seems working just fine. Please send me some settings.

[operator]

Hmmm, I just checked with 12.09 and it seems working just fine. Please send me some settings.

Tested in Bitwig and Reaper. I also got some Latency Report Issues but with the Crossovers in LinearPhase...

here is a simple scenario with MXXX1... a Crossover (LP) in combination with a Volume Modulation (Mod1 triggerd with Midi).

How to recreate:
Draw a 4 to the floor Midi-Triggered Click (very short impulse with a Synth,...) into the sequencer and if latency is correctly reported you should hear something. If you hear nothing go into the Mod1 and adjust the Custom shape of the LFO to see/hear when the Click is coming through. You will see there is some offset happening. But i´m not sure if this is a Latency Report issue or something different. But this makes the modulation-sources unusable for precise modulation... EVEN when Midi-Triggered.

When the Crossover is switched to the 6dB LP or any Analog Crossover everything works like expected..

Code: Select all

$eNrNVk1z4jgQvedXqJSqPU2wJH-X2p4KCcxSBQOFsxnmqLUVcEWWWFlOYH79lmxMDPmY3TktB2O3Xre6n15Lij7vSg6emKoKKWKIBwgCJjKZF2Idw1o-XAXwc3IRzVarVcW0LsS6ApcxxBDcSM7ptmL5slhv9IIKxmOIjF1oJTlnqhoJ+hdneWuulWJCLxSrmJ7cxrDcg0zJqpJPTEHw5c9JWvxgJIbYc51Pvk+OthGt9iSGAbZb83SZbnmhNVNmFMcQE4IHAQpsgkPvfJzE0EbuAIfY8wNkuxDM6G46ng+5zB4NIIY2gSBlnGWa5QterwsRQ-TJgSAtRNbUet8R5AeBb3swiea13tYagV6JVnIRte5VcngB45rzr7RkMbzpagXEpFA9zmsdQxuCs2EIVg1f32PowC5Oekr95REdw2tBuVyD6QKCy5TLLTN85ENLZvrtUpPIuOx-MAXSUkq9EayqYogGyIUglbXKWDPJt0Lk8vlubyL+QYUwySj2UHDNVCHWSbSQhdBgzOm6GsYQOxiCnZGQjTAiYRi6nget92DOOcw6C65kxqpKqh7FGIJxwXnzkm7k843kUt1TXrOqsd1tiuyxXYkXfwwaGIkhug4ICcZjCOZPTKkiZ83I+67k6BqQAKPr-+Bq-7qr00uYjALyc1erW1DD4olejoY3BHkveV0y8Bstt7+DBRVS0ZIC3IpzImLY1ynpdHov+YIKCFr9T0TOdqhJaNU8v8cweFe17YyNut8SptXL1uoa6SKajudVYp5nSlDs75qJbN98zWTOYvhVqpJyMz9VtGSaqabeJRVrZtoJHO0fUgCuQDsCQaOuJuPmbUizx3p7oH02uZ0szW7Wz8tKopF4YqYRrSRKi7WgHHSWW7bVm1a+d6PFYjlKR3cm2ItP1y6ZacjQh72+sSFom9HUCshLazVYl-Sx6AzbNCa7wgiCfQyv8Ft9ic5Q74HaTWOFzaw2tn3iOiFqNt6dMWHkeC7GHvFD-GGcFk38EHmh7-mO89Pc0CAIvC588C-g4fH3Adhu627k97IM8y1TVBdSVGCxoRVrNkiEXY+4DbJd2SRK9yI70eWUibVZZAKPjo2DEXD7Z0Q9q7kujmqskjMDAl+UNEKbzsEKzJujcJQXWqoToTcnJC3ZUj63XXUymG7Z4ew9U3ELG+7BQ6EqDbbdrB80zozuuiADOyTIRg4OvcB91VK9Yw5cgSEVOeBFWWizsRzCmQiBjVwUOL7j9bIzNJ3xcE4M7ojZTP4fxPxK+d6hdtf37JccTnl9zQV+ZTFCus508cTaWxUwTBgRJtEN1Wwt1X6iWTkRD9JKosMF7LCPt+dGz9nEUluwpJoZ8ZrLzOygzW9FrjezJGovB6B-UHfL1kGsg89FZPWujFVy8Q8wai9w

[MeldaProduction]

I'm a bit lost, I thought this is about Limiter? Are what am I missing? If you mean that Mod won't be in sync with something after the latency, then sure it won't, Mods are processing input signal and set the parameters. Then various items in the chain may be delayed variously, so there's no way around it. You can use ModularEx though and use its own mods .

[operator]

Ohh, sorry... my bad. i thought it should work in that way. but yes, fortunatly there is a workaround ... i will try it later with the ModularEx... thanks for the hint.

[operator]

Does that mean, if i´m using the crossover after the volume modulation, the "mod offset" isn´t happening? Because then i could solve my issues by first adressing the modulation on the Volume and then splitting it afterwards into two bands via the LP-Crossover.

SORRY FOR WASTING YOUR TIME!

Is there a way to assign the Mod1 Knob to an MP, that i can open the Mod1 via the "Easy-Screen" so I don´t need to go into the Edit-View to just open it?

[MeldaProduction]

I don't follow very well, but, basically, when a module (or the plugin) has modulators, then the modulation is following the input to that module (if it is following the input somehow), so if you then introduce some delay, the modulation will certainly be ahead of time for the modules after the delay. Which is where you may introduce the ModularEx if you want to avoid the delay.

I'm afraid modulators cannot be opened from the easy screen.

[valankar]

Please see the attached screenshots showing the latency problem with MXXX1 in 12.09.

The bottom of the window shows the latency in Ableton.

MLimiterX:

MXXX1:

Here is the MXXX1 copied settings:

Code: Select all

$eNptUl2P2jAQfOdXWHuvXEPC8XFSnBNNoUJKehFRW-roxgtYODayN6ejv75KIIir+mKtZjw7O6uNX95rzd7QeWUNh-DTCBiaykpl9hwa2j3O4SUZxPl2u-VIpMzeswcOIbDUGnJWa3R+acRvjZLDCNjX7+tS-cGIQxhF4XAyntywpfDniMP0eT6cTUNg2aY8aUWErmVDDtE0fPoXjjhMnoHl4j1bvX7Wtjq2KIdxBKxEjRWhLHSzV4bDaDgC9qMPM5vPZ+MpJPGF9n3BVo3W30SNHDJVK0LHQmAfAGDbLsyv9u115cf8D5m1x8UBhdwIUpbDE7AFkaiOuZXIYSU8tVvSWpw8yrzRpArhRJ2tXgthUHN4bJegzDE9CGNQ+87z1vYLanHuoP+G36BG4fHerFQS04NQpuiVN6TEyhop3Pnq1bJBEgeXaLfCJ4N4UZF6w8KhR2JLqaiNm8SpINxbd14T1muzs0ESp41zaOi6u67fvbjt5U5sIwg5RBC0d4SEzifxTyXpkCdxaRtXISsc7pQmdN3ZXSbrvwRXzSAO7q7QJ4O-m+XhVg==

[valankar]

I also just tried with 12.10, same problem.

[MeldaProduction]

I don't follow, there's no latency in these settings! (I tried anyways...)

[jmalge]

To clarify, make the settings in both limiters identical.

In particular, set Peak Hold to 0.50ms in MXXX1/Limiter and it'll also report 88 samples.

[valankar]

Ah thanks, I didn't know about the Peak Hold setting.