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 1.4.0 update is here!

1235710

Comments

  • @Shiloh said:

    @Edward_Alexander said:
    Can confirm problem loading Koala AU, but IAA loads fine.

    Same here. iPad Air 3 iOS 15.4.1

    Koala dev is on it

  • @yokotate said:
    So happy to be able to cut, copy and paste from one node to another now - this is huge, among all the other nice updates. Good to see the tip jar too, AUM is truly amazing and needs to be supported.

    Yep, the ‘tip jar’ should be be brought to others apps..

  • Yes a breakdown video would be cool.

  • "Indicate knob drag direction visually."
    When I actually used the new version of AUM, I was personally surprised by this feature. For the first time I was able to be aware of the ability to create vertical and horizontal knobs at the same time when using multiple nodes at the same time. I think this developer (j_liljedahl) thought very much about the UI and UX of a tablet that can use multi-touch and dived deep into it.

  • @Jumpercollins said:
    Yes a breakdown video would be cool.

    I suppose, Doug will do…

  • @ExAsperis99 said:

    @wim said:
    On a more serious note, what I'm really missing in AUM is a left handed smoke shifter. But that's true for nearly all iOS DAWs. I guess I still need to stick to the desktop until iOS finally catches up.

    There's a very simple workaround with some insane midi app that looks like code from the 1980s that I will reference as a subtle way of proving my never-to-be-challenged authority in all matters regarding (but not limited to) electronic music production. The name escapes me at the moment, but it with an hour's simple coding it's easy enough to duplicate and reverse a right handed smoke shifter.

    Left-handed linguist here, you guys are both spelling schmuck sifter wrong.

  • @shazbot said:
    AUv3: don't process bypassed nodes.

    Yup, felt the same when I saw it.
    It seems though, that now bypassing is not as immediate as it was. I have a project where I used Rozeta LFO, set to a square wave, to bypass an insert FX in sync, but now it’s not perfectly timed as it was.

    @j_liljedahl is that a trade off of not processing bypassed nodes?

  • It seems that not only Koala is affected. Some of my projects no longer work correctly. For example: Autony no longer plays the Waverly apps and Grand Piano, I can't connect them either. Don't have the time now, but hopefully all the other apps are working. Or did I miss something? Or do we need to update to iOS 15.5?
    iPad Pro 2021 12.9" iOS 15.4.1

  • @onerez said:

    @ErrkaPetti said:

    @j_liljedahl said:

    @tja said:
    @j_liljedahl The tips are sorted wrongly.

    I noticed! They changed order in the release compared to the beta. Will sort it out in the next update.

    Also, there can only ever be some "medium" or "middle" when there is an uneven number.

    With 4 choices, there cannot be a Medium Tip!

    Medium is between small and large, and then there’s Huge.

    Jonathan, where in the app can I find the TIP JAR?
    I must be blind…

    Send a huge tip if I only find it…

    Thanks!

    Huge tip on the way to the great mr Liljedahl on the west coast of Sweden!

  • 👍

    ⭐️ ⭐️ ⭐️ ⭐️ ⭐️

  • edited May 2022

    @ZankFrappa said:
    It seems that not only Koala is affected. Some of my projects no longer work correctly. For example: Autony no longer plays the Waverly apps and Grand Piano, I can't connect them either. Don't have the time now, but hopefully all the other apps are working. Or did I miss something? Or do we need to update to iOS 15.5?
    iPad Pro 2021 12.9" iOS 15.4.1

    Seems Koala is not loading here.. Air4 15.5

  • @uncledave said:

    @RaquNox said:

    @j_liljedahl said:

    @RaquNox said:
    Still no MIDI receive clock. Until recently I still used AUM for my main iPad as an instrument set up, as any other app just lacked the polish, ease of use, but I could only use it in a limited capacity, since no external MIDI clock. The latest Drambo 2.0 update finally provided a stable and useful alternative to connect to my Elektron and TE gear. Was hoping really deeply that we might finally see a MIDI clock in (which I know can be very hard to get right), or, at least transport control in - this would probably be easy. Having AUM as the MIDI host is terrible ergonomically compared to using external gear, especially pressing that small play button to start/stop the whole thing.

    There is MIDI Machine Control already that lets you control the transport (start, stop, rewind, record, etc), and you can also map such actions to any MIDI note/cc/etc message.

    Thanks for your response! I understand it can be mapped, but transport on any of my hardware are not regular MIDI cc messages (Elektron DIGI boxes, OP-Z, OP-1), hence they can not be mapped. For example in FL studio (which also does not accept clock), all of these maschine start and stop/restart transport automatically (if they are set to send transport - which is separate from clock on the elektrons). I am unsure what the format is for that though.

    As suggested, they are likely sending MIDI Machine Control mesages, which are special MIDI SysEx format messages. You could use a MIDI monitor to check what the hardware is sending. If it's MMC, you just need to enable Receive MMC in the Transport parameters section of AUM. Try it; it might just work!

    Thanks, I have gone and tried again.. nothing coming through, so no way to map transport control. No worries.. I do love AUM, but mostly just use it for doodling on iPad standalone now.

  • @RaquNox said:

    @uncledave said:

    @RaquNox said:

    @j_liljedahl said:

    @RaquNox said:
    Still no MIDI receive clock. Until recently I still used AUM for my main iPad as an instrument set up, as any other app just lacked the polish, ease of use, but I could only use it in a limited capacity, since no external MIDI clock. The latest Drambo 2.0 update finally provided a stable and useful alternative to connect to my Elektron and TE gear. Was hoping really deeply that we might finally see a MIDI clock in (which I know can be very hard to get right), or, at least transport control in - this would probably be easy. Having AUM as the MIDI host is terrible ergonomically compared to using external gear, especially pressing that small play button to start/stop the whole thing.

    There is MIDI Machine Control already that lets you control the transport (start, stop, rewind, record, etc), and you can also map such actions to any MIDI note/cc/etc message.

    Thanks for your response! I understand it can be mapped, but transport on any of my hardware are not regular MIDI cc messages (Elektron DIGI boxes, OP-Z, OP-1), hence they can not be mapped. For example in FL studio (which also does not accept clock), all of these maschine start and stop/restart transport automatically (if they are set to send transport - which is separate from clock on the elektrons). I am unsure what the format is for that though.

    As suggested, they are likely sending MIDI Machine Control mesages, which are special MIDI SysEx format messages. You could use a MIDI monitor to check what the hardware is sending. If it's MMC, you just need to enable Receive MMC in the Transport parameters section of AUM. Try it; it might just work!

    Thanks, I have gone and tried again.. nothing coming through, so no way to map transport control. No worries.. I do love AUM, but mostly just use it for doodling on iPad standalone now.

    How and where are you monitoring the MIDI. If you have devices connected to each other by MIDI and starting one starts the others, there is a midi message involved as that is the only method being used for communication . It may take sleuthing to determine what it is.

  • @espiegel123 said:

    @RaquNox said:

    @uncledave said:

    @RaquNox said:

    @j_liljedahl said:

    @RaquNox said:
    Still no MIDI receive clock. Until recently I still used AUM for my main iPad as an instrument set up, as any other app just lacked the polish, ease of use, but I could only use it in a limited capacity, since no external MIDI clock. The latest Drambo 2.0 update finally provided a stable and useful alternative to connect to my Elektron and TE gear. Was hoping really deeply that we might finally see a MIDI clock in (which I know can be very hard to get right), or, at least transport control in - this would probably be easy. Having AUM as the MIDI host is terrible ergonomically compared to using external gear, especially pressing that small play button to start/stop the whole thing.

    There is MIDI Machine Control already that lets you control the transport (start, stop, rewind, record, etc), and you can also map such actions to any MIDI note/cc/etc message.

    Thanks for your response! I understand it can be mapped, but transport on any of my hardware are not regular MIDI cc messages (Elektron DIGI boxes, OP-Z, OP-1), hence they can not be mapped. For example in FL studio (which also does not accept clock), all of these maschine start and stop/restart transport automatically (if they are set to send transport - which is separate from clock on the elektrons). I am unsure what the format is for that though.

    As suggested, they are likely sending MIDI Machine Control mesages, which are special MIDI SysEx format messages. You could use a MIDI monitor to check what the hardware is sending. If it's MMC, you just need to enable Receive MMC in the Transport parameters section of AUM. Try it; it might just work!

    Thanks, I have gone and tried again.. nothing coming through, so no way to map transport control. No worries.. I do love AUM, but mostly just use it for doodling on iPad standalone now.

    How and where are you monitoring the MIDI. If you have devices connected to each other by MIDI and starting one starts the others, there is a midi message involved as that is the only method being used for communication . It may take sleuthing to determine what it is.

    Hi espiegel123; I'm not an expert, but I believe this is not MIDI CC, PC or NOTE, but something called a system real time message, which falls in the same category of MIDI messages as the clock sync (but is not clock sync).. If I'm reading this correctly: https://www.midi.org/specifications-old/item/table-1-summary-of-midi-message

  • @RaquNox said:

    @espiegel123 said:

    @RaquNox said:

    @uncledave said:

    @RaquNox said:

    @j_liljedahl said:

    @RaquNox said:
    Still no MIDI receive clock. Until recently I still used AUM for my main iPad as an instrument set up, as any other app just lacked the polish, ease of use, but I could only use it in a limited capacity, since no external MIDI clock. The latest Drambo 2.0 update finally provided a stable and useful alternative to connect to my Elektron and TE gear. Was hoping really deeply that we might finally see a MIDI clock in (which I know can be very hard to get right), or, at least transport control in - this would probably be easy. Having AUM as the MIDI host is terrible ergonomically compared to using external gear, especially pressing that small play button to start/stop the whole thing.

    There is MIDI Machine Control already that lets you control the transport (start, stop, rewind, record, etc), and you can also map such actions to any MIDI note/cc/etc message.

    Thanks for your response! I understand it can be mapped, but transport on any of my hardware are not regular MIDI cc messages (Elektron DIGI boxes, OP-Z, OP-1), hence they can not be mapped. For example in FL studio (which also does not accept clock), all of these maschine start and stop/restart transport automatically (if they are set to send transport - which is separate from clock on the elektrons). I am unsure what the format is for that though.

    As suggested, they are likely sending MIDI Machine Control mesages, which are special MIDI SysEx format messages. You could use a MIDI monitor to check what the hardware is sending. If it's MMC, you just need to enable Receive MMC in the Transport parameters section of AUM. Try it; it might just work!

    Thanks, I have gone and tried again.. nothing coming through, so no way to map transport control. No worries.. I do love AUM, but mostly just use it for doodling on iPad standalone now.

    How and where are you monitoring the MIDI. If you have devices connected to each other by MIDI and starting one starts the others, there is a midi message involved as that is the only method being used for communication . It may take sleuthing to determine what it is.

    Hi espiegel123; I'm not an expert, but I believe this is not MIDI CC, PC or NOTE, but something called a system real time message, which falls in the same category of MIDI messages as the clock sync (but is not clock sync).. If I'm reading this correctly: https://www.midi.org/specifications-old/item/table-1-summary-of-midi-message

    Understood. You can still intercept it with some tools and pass along an appropriate message. So, you need to look at the stream with an appropriate midi monitor to see what messages are being sent.

  • @branis said:

    @shazbot said:
    AUv3: don't process bypassed nodes.

    Yup, felt the same when I saw it.
    It seems though, that now bypassing is not as immediate as it was. I have a project where I used Rozeta LFO, set to a square wave, to bypass an insert FX in sync, but now it’s not perfectly timed as it was.

    @j_liljedahl is that a trade off of not processing bypassed nodes?

    Timing should be the same, but some FX might sound different when unbypassed because the fx is essentially ”paused” while bypassed. So for example a delay might have have left over echoes from the signal before being bypassed. AUM does send a ”reset” as well as telling the node it’s bypassed, so plugins can clear buffers etc if they want. However I guess if you’re using a wet fx you’d rather automate a send instead of bypassing the fx. I would not recommend using bypass in this sequenced musical way anyhow, because it happens on buffer boundaries so will have jitter in timing depending on your buffer size. Better to use a plugin parameter.

  • @j_liljedahl I'm getting hanging notes on the in-app midi keyboard in new AUM (iPad iOS 15.5)
    If you start on C4 then slide finger to C5 then release, then C5 will not receive Note Off.
    This is with 'hold' set to off and the only way to stop the note is to start / stop transport.

    Would also be good to make the keyboard a bit taller or draggable, I think its got smaller vertically.

  • Thanks for another huge update, @j_liljedahl! The ability to copy, move and bypass fx is huge workflow improvement. Especially after previous modulation section update. Best DAW which isn't actually a DAW became better and better.

  • @RaquNox said:

    @espiegel123 said:

    @RaquNox said:

    @uncledave said:

    @RaquNox said:

    @j_liljedahl said:

    @RaquNox said:
    Still no MIDI receive clock. Until recently I still used AUM for my main iPad as an instrument set up, as any other app just lacked the polish, ease of use, but I could only use it in a limited capacity, since no external MIDI clock. The latest Drambo 2.0 update finally provided a stable and useful alternative to connect to my Elektron and TE gear. Was hoping really deeply that we might finally see a MIDI clock in (which I know can be very hard to get right), or, at least transport control in - this would probably be easy. Having AUM as the MIDI host is terrible ergonomically compared to using external gear, especially pressing that small play button to start/stop the whole thing.

    There is MIDI Machine Control already that lets you control the transport (start, stop, rewind, record, etc), and you can also map such actions to any MIDI note/cc/etc message.

    Thanks for your response! I understand it can be mapped, but transport on any of my hardware are not regular MIDI cc messages (Elektron DIGI boxes, OP-Z, OP-1), hence they can not be mapped. For example in FL studio (which also does not accept clock), all of these maschine start and stop/restart transport automatically (if they are set to send transport - which is separate from clock on the elektrons). I am unsure what the format is for that though.

    As suggested, they are likely sending MIDI Machine Control mesages, which are special MIDI SysEx format messages. You could use a MIDI monitor to check what the hardware is sending. If it's MMC, you just need to enable Receive MMC in the Transport parameters section of AUM. Try it; it might just work!

    Thanks, I have gone and tried again.. nothing coming through, so no way to map transport control. No worries.. I do love AUM, but mostly just use it for doodling on iPad standalone now.

    How and where are you monitoring the MIDI. If you have devices connected to each other by MIDI and starting one starts the others, there is a midi message involved as that is the only method being used for communication . It may take sleuthing to determine what it is.

    Hi espiegel123; I'm not an expert, but I believe this is not MIDI CC, PC or NOTE, but something called a system real time message, which falls in the same category of MIDI messages as the clock sync (but is not clock sync).. If I'm reading this correctly: https://www.midi.org/specifications-old/item/table-1-summary-of-midi-message

    Or it could be MIDI Machine Control, as I suggested earlier. Should be visible on a monitor either way.

  • @uncledave said:

    @RaquNox said:

    @espiegel123 said:

    @RaquNox said:

    @uncledave said:

    @RaquNox said:

    @j_liljedahl said:

    @RaquNox said:
    Still no MIDI receive clock. Until recently I still used AUM for my main iPad as an instrument set up, as any other app just lacked the polish, ease of use, but I could only use it in a limited capacity, since no external MIDI clock. The latest Drambo 2.0 update finally provided a stable and useful alternative to connect to my Elektron and TE gear. Was hoping really deeply that we might finally see a MIDI clock in (which I know can be very hard to get right), or, at least transport control in - this would probably be easy. Having AUM as the MIDI host is terrible ergonomically compared to using external gear, especially pressing that small play button to start/stop the whole thing.

    There is MIDI Machine Control already that lets you control the transport (start, stop, rewind, record, etc), and you can also map such actions to any MIDI note/cc/etc message.

    Thanks for your response! I understand it can be mapped, but transport on any of my hardware are not regular MIDI cc messages (Elektron DIGI boxes, OP-Z, OP-1), hence they can not be mapped. For example in FL studio (which also does not accept clock), all of these maschine start and stop/restart transport automatically (if they are set to send transport - which is separate from clock on the elektrons). I am unsure what the format is for that though.

    As suggested, they are likely sending MIDI Machine Control mesages, which are special MIDI SysEx format messages. You could use a MIDI monitor to check what the hardware is sending. If it's MMC, you just need to enable Receive MMC in the Transport parameters section of AUM. Try it; it might just work!

    Thanks, I have gone and tried again.. nothing coming through, so no way to map transport control. No worries.. I do love AUM, but mostly just use it for doodling on iPad standalone now.

    How and where are you monitoring the MIDI. If you have devices connected to each other by MIDI and starting one starts the others, there is a midi message involved as that is the only method being used for communication . It may take sleuthing to determine what it is.

    Hi espiegel123; I'm not an expert, but I believe this is not MIDI CC, PC or NOTE, but something called a system real time message, which falls in the same category of MIDI messages as the clock sync (but is not clock sync).. If I'm reading this correctly: https://www.midi.org/specifications-old/item/table-1-summary-of-midi-message

    Or it could be MIDI Machine Control, as I suggested earlier. Should be visible on a monitor either way.

    I'll try this one out asap, thanks

  • Love the new long press “node” pop-ups. Very useful.

    Will echo what a few others have said: Would like to see MIDI Clock sync (I don’t find Ableton Link to be any better than good ol’ MIDI Clock, especially when dealing with hardware). I understand though that it’s hard to do right.

    IMO, AUM has the best user interface in all of iOS land. Brilliant job.

  • Great update, thank you!

  • @espiegel123
    As Au in AUM slot does not work. Koala IAA in AUM works

    @espiegel123 said:

    @joniqwest said:
    yup doesn't work for me either. can't load koala in Aum
    2018 iPad Pro 11"
    iOS 15.2.1

    As AU or standalone?

  • Apparently the Koala bug is fixed in Koala beta version but the developer is currently away.

  • new Koala updated here! and is fixed for new AUM!:)

  • edited May 2022

    Btw, any chances to see keyboard scaling option in future updates? Definitely it will make things easier for non keyboard players like me.

  • Yep new update fixes Koala :)

  • THANKS @j_liljedahl 😊👍🏼

  • Slowly making my way thru the new features…..

    Noticed that the ‘scroll left/right’ arrow keys are no longer working on my Bluetooth keyboard. Was working in the previous version a day ago. But oddly enough the ‘page left/right’ (command + arrow keys) still works? 🤔

    Anyone else have this problem?

    Cheers

Sign In or Register to comment.