Loopy Pro: Create music, your way.

What is Loopy Pro? — Loopy Pro is a powerful, flexible, and intuitive live looper, sampler, clip launcher and DAW for iPhone and iPad. At its core, it allows you to record and layer sounds in real-time to create complex musical arrangements. But it doesn’t stop there—Loopy Pro offers advanced tools to customize your workflow, build dynamic performance setups, and create a seamless connection between instruments, effects, and external gear.

Use it for live looping, sequencing, arranging, mixing, and much more. Whether you're a live performer, a producer, or just experimenting with sound, Loopy Pro helps you take control of your creative process.

Download on the App Store

Loopy Pro is your all-in-one musical toolkit. Try it for free today.

sidechain in AUM with/without delay compensation?

[Deleted User][Deleted User]
in General App Discussion

I have no idea what would be preferable/what one should expect. Noticed that when sending a sidechain (the blocswave drumloop) to the ToneBoosters compressor on the synth track and auditioning the drums there, there seems to be a doubling of the kick.
Anyone know what’s to be expected here regarding plugin delay compensation? @j_liljedahl

Comments

  • j_liljedahlj_liljedahl

    First of all, the kick should only come out of channel strip 5, it just passes through the side-chain receiver node. Maybe you have side-chain monitoring enabled in ToneBoosters so it's doubled and comes out of channel strip 2 as well?

    All this is quite complex, but I think I have done it correctly in AUM. A plugin can only report a global latency, so we'll have to assume that all outputs of a plugin have the same latency. But this doesn't matter in your case, because you only have one output (but two inputs).

    Regarding plugin inputs, AUM does set contextPresentationLatency for each input so the plugin can know if the signal coming into that input is delayed. I don't know if any nodes above your ToneBoosters introduce latency, or if that has anything to do with it.

    You can try to just bypass the output node of strip 5, if you still hear the kick then it means the side-chain signal is mixed with the output in the ToneBoosters plugin, and there's nothing any latency compensation can do about it since it's a single mixed signal, so you'll have to check the settings in ToneBoosters or report it to their devs if you can't turn off the side-chain->output routing.

  • [Deleted User][Deleted User]

    @j_liljedahl said:
    First of all, the kick should only come out of channel strip 5, it just passes through the side-chain receiver node. Maybe you have side-chain monitoring enabled in ToneBoosters so it's doubled and comes out of channel strip 2 as well?

    All this is quite complex, but I think I have done it correctly in AUM. A plugin can only report a global latency, so we'll have to assume that all outputs of a plugin have the same latency. But this doesn't matter in your case, because you only have one output (but two inputs).

    Regarding plugin inputs, AUM does set contextPresentationLatency for each input so the plugin can know if the signal coming into that input is delayed. I don't know if any nodes above your ToneBoosters introduce latency, or if that has anything to do with it.

    You can try to just bypass the output node of strip 5, if you still hear the kick then it means the side-chain signal is mixed with the output in the ToneBoosters plugin, and there's nothing any latency compensation can do about it since it's a single mixed signal, so you'll have to check the settings in ToneBoosters or report it to their devs if you can't turn off the side-chain->output routing.

    Thank you for explaining! Side-chain monitoring is indeed active in TB compressor..

Sign In or Register to comment.

© Vanilla Keystone Theme 2024