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.

BYOD Public Beta

1235»

Comments

  • Flapjack and byod spring reverb through a clean TONEX preset

  • @NeuM said:
    Please test using as AU's in Logic Pro on both iPadOS and macOS. Thank you.

    I don’t have a MacBook but I can test it in logic on iOS if you need me to

  • Ooh, opto beta update

  • Really enjoying all the amazing effects of this amazing app! The Poly Octave is it man! Used it live for all my Lead and really sounded amazing! <3

  • Question, does it really make a difference whether I set the oversampling to anything higher than 1?

  • @Tones4Christ said:
    Question, does it really make a difference whether I set the oversampling to anything higher than 1?

    It depends. Let your ears judge. It also depends what sample rate you are running at.

  • @espiegel123 said:

    @Tones4Christ said:
    Question, does it really make a difference whether I set the oversampling to anything higher than 1?

    It depends. Let your ears judge. It also depends what sample rate you are running at.

    Thanks!
    I'm running at 96 khz with a 256 buffer size in AUM. Some weird thing has happening live on stage yesterday! Almost freaked out. My CPU was hovering near 100% when I activated my Poly Octave effect in BYOD. I never had this happen even in the previous Beta. I noticed that I had oversampling at 4X. Lowered it to 1X and didn't notice totally wise anything wrong. But it really helped my cpu go down. I have 5 instances of BYOD in my AWM template so I really was afraid the app my crash my setup but thank God it didn't.

    2 instances for Poly Octave
    2 Instances for Delay (1 for Dotted 8th) other one for 8ths note)
    1 instance for the RONN Drive. (Massive)

    Weird thing is I'm trying right now to replicate the CPU stuff and it's not happening. With everything enabled at once CPU is at 56% no joke!!!

  • @Tones4Christ : don’t use oversampling when running at 96k

  • Yeah, you’d be running a sample rate of 384k with the OS at 4x if you’re already in 96k

  • @espiegel123 said:
    @Tones4Christ : don’t use oversampling when running at 96k

    Oh wow! Thanks guys!

    @Fingolfinzz said:
    Yeah, you’d be running a sample rate of 384k with the OS at 4x if you’re already in 96k

    OMG :#

    So even with Delays or any instances of BYOD?

  • Yeah if you’re running the project in 96k then everything will be running that high. BYOD does run a little high as well. I know when I have the GuitarML ones going on every track I’m hitting pretty high dsp. I usually run in 48k and a 512 buffer. But I do drop the buffer down as low as it can take if I’m doing my guitar or keys to get rid of any latency. If it’s struggling too much, I just have to end up freezing or bouncing some tracks. I’m used to bouncing a lot after using the Acustica stuff on desktop, that stuff is a cpu nightmare

  • @Tones4Christ said:

    @espiegel123 said:
    @Tones4Christ : don’t use oversampling when running at 96k

    Oh wow! Thanks guys!

    @Fingolfinzz said:
    Yeah, you’d be running a sample rate of 384k with the OS at 4x if you’re already in 96k

    OMG :#

    So even with Delays or any instances of BYOD?

    Yes. The purpose of oversampling is dealing with aliasing issues that result from some dsp processes running at 48k and below (more or less). Running at 96k is essentially 2x oversampling of 48 k

Sign In or Register to comment.