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 update now live.

2»

Comments

  • KühlKühl

    Yeah, just USB for the audio, then like I say Bluetooth or WiFi for the clock send. It's pretty straightforward too, no need to jump through any hoops.

    Is there anything to install on the Mac, like a host program? Where do you find the inputs on the Mac?
    Perhaps in the audio control panel?

  • 1P181P18

    @Kühl said:

    Yeah, just USB for the audio, then like I say Bluetooth or WiFi for the clock send. It's pretty straightforward too, no need to jump through any hoops.

    Is there anything to install on the Mac, like a host program? Where do you find the inputs on the Mac?
    Perhaps in the audio control panel?

    There is an app already on MacOS called Audio MIDI Setup, it's icon looks like a mini keyboard. Connect your iPad via USB, open the app, and in the audio section of the app you'll see your iPad listed. Enable it and your iPad should be available as an audio input in you DAW.

    For MIDI turn on WiFi, then in the MIDI section of the app you should see your iPad listed, connect and MIDI can be sent over the Network.

  • j_liljedahlj_liljedahl

    @wim said:
    WiF i latency isn't constant. It can go up and down depending on interference and how much activity there is on your network.

    CoreMIDI packets over WiFi are timestamped, so in theory the sync should stay fixed once you've compensated for the latency mismatch, assuming the network delay never gets too big (or it will miss some MIDI clock ticks and go out of sync). I've never experienced WiFi MIDI to be reliable enough..

    I think MIDI over usb/lightning is coming in iOS11 though, or did I dream that?

  • j_liljedahlj_liljedahl

    @rezidue said:

    @rrc2soft said:

    @Crabman said:
    whats the"AU plugin memory allocation bug"?

    See this thread: trouble starting several au instances (page 4). There is a bug with the way iOS loads Audio Units. Without that fix, a host can only load a certain instances of the same AU. There is a workaround: show (even in a hidden, "sent-to-the-back" view) the view of the AU after loading it (that is, open the AU GUI after loading it). I also implemented that workaround, and it works.

    I just gave this a try but it looks like I run into a similar issue. I can load four instances of Kaspar but on the fifth all instances crash. iPad Pro 10.5". I'm not seeing the crazy CPU spikes or distorted audio that I would get in bm3 so maybe it crashes cleaner? Odd issue and seems worse on these new iPads.

    Check the device logs using "iConsole" or similar app on your desktop computer. If there's a lot of "Memory Warning" in the logs just before the crash - then it's a memory issue. Maybe that iPad model simply has not enough RAM to run 5 Kaspar instances + AUM + iOS itself!

  • OscarSouthOscarSouth

    @j_liljedahl said:

    @1P18 said:

    @1P18 said:
    MIDI Clock Send! Nice. Just connected AUM to Bitwig. This opens up a lot of possibilities.

    And for Mac users who are wondering, you can send audio over USB, and then send MIDI clock over Bluetooth or WiFi. Just use the Audio MIDI Setup app built into Mac OS. No interface needed to connect AUM to your DAW.

    Even though this is theoretically possible, I really don't recommend running MIDI clock over bluetooth or wireless. Maybe it will sync good enough, but probably not. The MIDI Clock Send was built to synchronize external hardware (sequencers, eurorack, synths, etc). But let us know how it goes! :)

    I even notice that MIDI clock accuracy drops considerably when sending MIDI clock between devices via iCA hardware.

  • j_liljedahlj_liljedahl

    @OscarSouth said:

    @j_liljedahl said:

    @1P18 said:

    @1P18 said:
    MIDI Clock Send! Nice. Just connected AUM to Bitwig. This opens up a lot of possibilities.

    And for Mac users who are wondering, you can send audio over USB, and then send MIDI clock over Bluetooth or WiFi. Just use the Audio MIDI Setup app built into Mac OS. No interface needed to connect AUM to your DAW.

    Even though this is theoretically possible, I really don't recommend running MIDI clock over bluetooth or wireless. Maybe it will sync good enough, but probably not. The MIDI Clock Send was built to synchronize external hardware (sequencers, eurorack, synths, etc). But let us know how it goes! :)

    I even notice that MIDI clock accuracy drops considerably when sending MIDI clock between devices via iCA hardware.

    That's interesting. I wonder if iCA does not preserve the timestamps? Precision/jitter should never be a problem if timestamp is preserved, even if all data has to be delayed due to the actual method of transferring the data.

  • OscarSouthOscarSouth

    @j_liljedahl I'm not technical enough to comment seriously on that, but it it sounds like it could be possible.

    I noticed it when sending a MIDI Link Sync clock to Samplr on two different devices. It's only like a fluctuating 0.1bpm less stable than on the same device and not noticeable musically, but left me wondering why and whether it could cause any other problems.

  • nicknick

    @rezidue said:

    @rrc2soft said:

    @Crabman said:
    whats the"AU plugin memory allocation bug"?

    See this thread: trouble starting several au instances (page 4). There is a bug with the way iOS loads Audio Units. Without that fix, a host can only load a certain instances of the same AU. There is a workaround: show (even in a hidden, "sent-to-the-back" view) the view of the AU after loading it (that is, open the AU GUI after loading it). I also implemented that workaround, and it works.

    I just gave this a try but it looks like I run into a similar issue. I can load four instances of Kaspar but on the fifth all instances crash. iPad Pro 10.5". I'm not seeing the crazy CPU spikes or distorted audio that I would get in bm3 so maybe it crashes cleaner? Odd issue and seems worse on these new iPads.

    this is probably a different issue, possibly Kaspar (which after all is 8 synths at once) needs too much memory to run five instances.
    I just tested and can run 10 instances of phosphor + eos now without problems, and could probably add more. So that looks like a well working fix to me.

  • j_liljedahlj_liljedahl

    @OscarSouth said:
    @j_liljedahl I'm not technical enough to comment seriously on that, but it it sounds like it could be possible.

    I noticed it when sending a MIDI Link Sync clock to Samplr on two different devices. It's only like a fluctuating 0.1bpm less stable than on the same device and not noticeable musically, but left me wondering why and whether it could cause any other problems.

    Well, I wouldn't worry too much if it's not noticeable musically :) But it's always interesting to know the flaws and amount of precision in different configurations and setups. Maybe I should make a MIDI clock measuring tool app!

  • guidinglightguidinglight

    This update offers so much more stability with RoughRider.

  • cuscolimacuscolima

    @j_liljedahl

    Thanks a lot, the upgrade is great, the workaround works well for me! You're the best!

  • KühlKühl

    @1P18 said:

    @Kühl said:

    Yeah, just USB for the audio, then like I say Bluetooth or WiFi for the clock send. It's pretty straightforward too, no need to jump through any hoops.

    Is there anything to install on the Mac, like a host program? Where do you find the inputs on the Mac?
    Perhaps in the audio control panel?

    There is an app already on MacOS called Audio MIDI Setup, it's icon looks like a mini keyboard. Connect your iPad via USB, open the app, and in the audio section of the app you'll see your iPad listed. Enable it and your iPad should be available as an audio input in you DAW.

    For MIDI turn on WiFi, then in the MIDI section of the app you should see your iPad listed, connect and MIDI can be sent over the Network.

    Yep. I know exactly what you mean. It's where my Yamaha Tyros 4 and ProTools Digi 003 shows up.
    How convenient. This means my Mac becomes a midi hub, since everything shows up in Audio/MIDI setup.
    Thanks for the help :smile:

  • SpookyZooSpookyZoo

    Anybody know if there is a setting or 'workaround' to have the AUM midi routing stay active while the app is backgrounded?

    Cheers in advance.

  • j_liljedahlj_liljedahl

    @SpookyZoo said:
    Anybody know if there is a setting or 'workaround' to have the AUM midi routing stay active while the app is backgrounded?

    AUM only keeps running in the background if its transport is playing or if there are any channels with input nodes. So a simple way is to create a channel and add a Mix Bus as channel source.

  • SpookyZooSpookyZoo

    @j_liljedahl said:

    @SpookyZoo said:
    Anybody know if there is a setting or 'workaround' to have the AUM midi routing stay active while the app is backgrounded?

    AUM only keeps running in the background if its transport is playing or if there are any channels with input nodes. So a simple way is to create a channel and add a Mix Bus as channel source.

    Thank you sir.

    We miss new stuff from you! :)

  • CrabmanCrabman

    Thanks for the update!Nice to have Midi Clock now and when you hit start it's very tight but it starts to drift away after half a minute or so.

  • rumorazzirumorazzi

    Thanks for midi clock, It's very useful for me!
    AUM it's my favorite app ever.

  • LeonLeroyLeonLeroy

    @j_liljedahl said:

    @SpookyZoo said:
    Anybody know if there is a setting or 'workaround' to have the AUM midi routing stay active while the app is backgrounded?

    AUM only keeps running in the background if its transport is playing or if there are any channels with input nodes. So a simple way is to create a channel and add a Mix Bus as channel source.

    thank you for this tip.

  • j_liljedahlj_liljedahl

    @Crabman said:
    Thanks for the update!Nice to have Midi Clock now and when you hit start it's very tight but it starts to drift away after half a minute or so.

    Please send me an email with the details so we can try to sort that out!

  • reziduerezidue

    @j_liljedahl said:

    @rezidue said:

    @rrc2soft said:

    @Crabman said:
    whats the"AU plugin memory allocation bug"?

    See this thread: trouble starting several au instances (page 4). There is a bug with the way iOS loads Audio Units. Without that fix, a host can only load a certain instances of the same AU. There is a workaround: show (even in a hidden, "sent-to-the-back" view) the view of the AU after loading it (that is, open the AU GUI after loading it). I also implemented that workaround, and it works.

    I just gave this a try but it looks like I run into a similar issue. I can load four instances of Kaspar but on the fifth all instances crash. iPad Pro 10.5". I'm not seeing the crazy CPU spikes or distorted audio that I would get in bm3 so maybe it crashes cleaner? Odd issue and seems worse on these new iPads.

    Check the device logs using "iConsole" or similar app on your desktop computer. If there's a lot of "Memory Warning" in the logs just before the crash - then it's a memory issue. Maybe that iPad model simply has not enough RAM to run 5 Kaspar instances + AUM + iOS itself!

    I've been testing with a memory monitoring app. When I first launch the app I have about 43% memory free (around 1.7GB). After adding four instances of Kaspar I have 34% free (around 1.3GB). Adding the fifth instance causes all previous instances to crash and memory is freed. I'm leaning on this being more related to it being a new iPad Pro. When it crashes all audio gets distorted (any other app that might be playing audio) and it doesn't return to normal until I kill the app hosting AU3. There were similar issues being reported before but the patches you did with AUM and intua did for BM3 seemed to have resolved it for most plugins but it seems to exist for Kaspar. I also made sure to preview the GUI for each instance before adding another. I'm going to start a new thread and see if anyone with Kaspar can test and report back.

  • reziduerezidue

    @rezidue said:

    @j_liljedahl said:

    @rezidue said:

    @rrc2soft said:

    @Crabman said:
    whats the"AU plugin memory allocation bug"?

    See this thread: trouble starting several au instances (page 4). There is a bug with the way iOS loads Audio Units. Without that fix, a host can only load a certain instances of the same AU. There is a workaround: show (even in a hidden, "sent-to-the-back" view) the view of the AU after loading it (that is, open the AU GUI after loading it). I also implemented that workaround, and it works.

    I just gave this a try but it looks like I run into a similar issue. I can load four instances of Kaspar but on the fifth all instances crash. iPad Pro 10.5". I'm not seeing the crazy CPU spikes or distorted audio that I would get in bm3 so maybe it crashes cleaner? Odd issue and seems worse on these new iPads.

    Check the device logs using "iConsole" or similar app on your desktop computer. If there's a lot of "Memory Warning" in the logs just before the crash - then it's a memory issue. Maybe that iPad model simply has not enough RAM to run 5 Kaspar instances + AUM + iOS itself!

    I've been testing with a memory monitoring app. When I first launch the app I have about 43% memory free (around 1.7GB). After adding four instances of Kaspar I have 34% free (around 1.3GB). Adding the fifth instance causes all previous instances to crash and memory is freed. I'm leaning on this being more related to it being a new iPad Pro. When it crashes all audio gets distorted (any other app that might be playing audio) and it doesn't return to normal until I kill the app hosting AU3. There were similar issues being reported before but the patches you did with AUM and intua did for BM3 seemed to have resolved it for most plugins but it seems to exist for Kaspar. I also made sure to preview the GUI for each instance before adding another. I'm going to start a new thread and see if anyone with Kaspar can test and report back.

    I was able to to grab logs like you suggested and indeed saw memory warnings before the instances were killed. Thanks for the suggestion. I'm still confused why it happens if I have over a gig free. Take a look when you can:

    https://forum.audiob.us/discussion/comment/395402/#Comment_395402

  • OscarSouthOscarSouth

    @j_liljedahl AUM update is awesome but any possibility of sending MIDI clock to more than one source?

  • DeVlaeminckDeVlaeminck

    @OscarSouth said:
    @j_liljedahl AUM update is awesome but any possibility of sending MIDI clock to more than one source?

    Sry, but you do mean more than one destination?

  • [Deleted User][Deleted User]

    Don't know if this is AUM or Ruismaker but Ruismaker no longer sync starts with AUM. In IAA mode with sequencer I remember it would sync start when AUM's play transport was tapped.
    @brambos has this been reported?

  • brambosbrambos

    @MusicMan4Christ said:
    Don't know if this is AUM or Ruismaker but Ruismaker no longer sync starts with AUM. In IAA mode with sequencer I remember it would sync start when AUM's play transport was tapped.
    @brambos has this been reported?

    I don't think it ever did. Ruismaker does Midi Start/Stop and Audiobus Start/Stop but not IAA Transport.

  • [Deleted User][Deleted User]

    I think you're right. I guess, i need to stick to a single workflow, cause i might have done that when i was using it inside AB3. Right now, i had it only in AUM with Minisynth 2. Will try it in AB3. Thanks man! Awesome apps!

    @brambos said:

    @MusicMan4Christ said:
    Don't know if this is AUM or Ruismaker but Ruismaker no longer sync starts with AUM. In IAA mode with sequencer I remember it would sync start when AUM's play transport was tapped.
    @brambos has this been reported?

    I don't think it ever did. Ruismaker does Midi Start/Stop and Audiobus Start/Stop but not IAA Transport.

  • OscarSouthOscarSouth

    @DeVlaeminck said:

    @OscarSouth said:
    @j_liljedahl AUM update is awesome but any possibility of sending MIDI clock to more than one source?

    Sry, but you do mean more than one destination?

    Yeah

  • j_liljedahlj_liljedahl

    @OscarSouth said:
    @j_liljedahl AUM update is awesome but any possibility of sending MIDI clock to more than one source?

    Currently no, but later on when I rewrite the MIDI router it will be possible.

Sign In or Register to comment.

© Vanilla Keystone Theme 2025