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.

AUM: Stuck at 44.1 kHz?!?

2»

Comments

  • [Deleted User][Deleted User]
    The user and all related content has been deleted.
  • vrtx_voidvrtx_void
    edited June 2023

    This seems to be an old thread, but I happen to have the very same issue, which drives me nuts and makes me really think about getting rid of iPad based setups in general.

    Whenever I connect my MOTU 16A or 828ES, AUM either totally freezes for a few seconds and I get the error message that my hardware is limited to 44.1 KHz, or it switches to 44.1 KHz and messes up my whole chain, since all devices are connected by AVB and clocked.

    My iPad is the very last 11 inch Pro version before the M1 generation.

    So is my iPad only capable of 44.1 KHz and I have to rerender all my samples and files accordingly to work with it, or did I miss any setting here?

    I am also interested to see if the issue is only in AUM. Does the same happen to the folks using Drambo, Loopy Pro or Logic iOS?

    /update:

    It is only occuring in AUM. Drambo e.g. is totally fine with 48 KHz and 128 samples:

  • vrtx_voidvrtx_void


  • bygjohnbygjohn

    I’m not an expert on this stuff, but intuitively I would always connect the interface before loading AUM and then loading the session, rather than doing it mid-session. Might be worth a try.

  • vrtx_voidvrtx_void

    @bygjohn said:
    I’m not an expert on this stuff, but intuitively I would always connect the interface before loading AUM and then loading the session, rather than doing it mid-session. Might be worth a try.

    Thanks for the advice, I did actually any possible combination: Connect the device before starting AUM, connecting after and so on, and yet it still does not work straight away.

    It's funny that today it worked after gazillions of different combinations of unplugging and replugging the USB cable. But then again this is unfortunately not really straightforward or in any way good for professional work..

  • espiegel123espiegel123

    AUM isn’t restricted to only one sample rate. I recommend disconnecting everything, rebooting, connecting your interface and then launching AUM.

    Before opening a project, try changing the sample rate and buffer size. If you do that , does it work?

  • vrtx_voidvrtx_void
    edited June 2023

    @espiegel123 said:
    AUM isn’t restricted to only one sample rate. I recommend disconnecting everything, rebooting, connecting your interface and then launching AUM.

    Before opening a project, try changing the sample rate and buffer size. If you do that , does it work?

    Also this does not really work for me..it is really crazy, since it is only AUM that behaves like this, both Loopy Pro and Drambo have no issues like that. My "problem" is that I neither feel confortable with Drambo's groovebox approach, nor (yet) with Loopy Pro's way too convoluted UI. Maybe I have to switch to Loopy Pro one day or give Logic iOS a chance, but AUM was so straightforward to use in combination with e.g. my M8 tracker, but as soon as I connect it to any audio interface with more than 2 channels, it breaks apart.

    Just also to clarify: I know about the max. 24 channel count limitation for iOS and have already programmed my routing in a very minimalistic way. It is also surprising to me that AUM can "force" my audio interface to switch to another sample rate..

  • bygjohnbygjohn

    @vrtx_void said:

    @espiegel123 said:
    AUM isn’t restricted to only one sample rate. I recommend disconnecting everything, rebooting, connecting your interface and then launching AUM.

    Before opening a project, try changing the sample rate and buffer size. If you do that , does it work?

    Also this does not really work for me..it is really crazy, since it is only AUM that behaves like this, bot Loopy Pro and Drambo have no issues like that. My "problem" is that I neither feel confortable with Drambo's groovebox approach, nor (yet) with Loopy Pro's way too convoluted UI. Maybe I have to switch to Loopy Pro one day or give Logic iOS a chance, but AUM was so straightforward to use in combination with e.b. my M8 tracker, but as soon as I connect it to any audio interface with more than 2 channels, it breaks apart.

    Just also to clarify: I know of the max. 24 channel count limitation for iOS and have already programmed my routing in a very minimalistic way. It is also surprising to me that AUM can "force" my audio interface to switch to another sample rate..

    It’s going to be another app, possibly a system app, that’s forcing this somehow. I know (from reading here, not experience) that some newer devices seem to be stuck on 48 unless you turn Siri off, for example. If something else hasn’t fixed the setting already, AUM usually works fine in this regard. I have a MOTU M4 (4 channels in, 4 channels out) and it’s fine with AUM (2018 ipad 6, iOS 16.4.1(a)).

    Try @espiegel123 ’s tips to see if it clears the issue, and if so watch for it reoccurring so you can narrow down the list of suspect apps.

  • espiegel123espiegel123

    @vrtx_void said:

    @espiegel123 said:
    AUM isn’t restricted to only one sample rate. I recommend disconnecting everything, rebooting, connecting your interface and then launching AUM.

    Before opening a project, try changing the sample rate and buffer size. If you do that , does it work?

    Also this does not really work for me..it is really crazy, since it is only AUM that behaves like this, bot Loopy Pro and Drambo have no issues like that. My "problem" is that I neither feel confortable with Drambo's groovebox approach, nor (yet) with Loopy Pro's way too convoluted UI. Maybe I have to switch to Loopy Pro one day or give Logic iOS a chance, but AUM was so straightforward to use in combination with e.b. my M8 tracker, but as soon as I connect it to any audio interface with more than 2 channels, it breaks apart.

    Just also to clarify: I know of the max. 24 channel count limitation for iOS and have already programmed my routing in a very minimalistic way. It is also surprising to me that AUM can "force" my audio interface to switch to another sample rate..

    I think you might have misunderstood the purpose of doing this. I am suggesting that you do this as a test to see if it is really that AUM can't set the sample rate of your device or if it is context dependent.

    Why not try it and see what happens? If you do this and it still doesn't work then that is important information -- especially if you want jonatan to look into it.

  • vrtx_voidvrtx_void

    @espiegel123 said:
    AUM isn’t restricted to only one sample rate. I recommend disconnecting everything, rebooting, connecting your interface and then launching AUM.

    Before opening a project, try changing the sample rate and buffer size. If you do that , does it work?

    I will try this tomorrow again and report :)

  • vrtx_voidvrtx_void

    Okay, this seems to be the working route, thanks to @espiegel123 !!

    It is not intuitive, but it worked by exactly the way you described it :)

Sign In or Register to comment.

© Vanilla Keystone Theme 2024