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.

Koala - the ultimate pocket-sized sampler

17880828384

Comments

  • edited April 2022

    In my work flow, Koala is a playground, sketch pad, and place to experiment. It is very fast to get going, and get fun results quickly as well. I deleted all my phone games when I got Koala, because on top of making music, it scratches my gaming itch as well with the way it is layed out for easy quick work flow and real time experimentation with sound mangling.

    I have had many tracks start in Koala, then stems are brought over to mix with other instruments to flesh out the rest of the track.

  • @jrjulius and @FriedTapeworm
    Thanks for the quick response
    Just watched a few more videos
    I am gonna jump on this
    The thought of loopy pro and koala sounds like a good combination
    Was gonna buy let’s Unmix but for the same money I get a new app and the Easter egg, does anybody know if let’s Unmix and koala use the same algorithm to split the stems ?
    Ether way time to purchase
    Sorry in advance as am sure over the next few days will be asking basic questions
    Many thanks for your replies
    Elf on the shelf take my money!

  • The user and all related content has been deleted.
  • Ok
    Purchased
    And activated the Easter egg
    Also purchased the av3
    Samurai purchase later
    Thanks all

  • @elf_audio while I’m not really into the feature ( I mostly sample myself these days) I think it’s cool what you did and what you keep bringing to the table, thank you for continuing to think about and add functions to koala sampler, it’s really a killer app, and gives me no end of inspiration and stimulus! You have a lifelong user here and I can’t wait to see what else you have up your sleeve!

  • Has there been an update of when the strum feature will return? I never got to try it 😭

  • @HotStrange said:
    Has there been an update of when the strum feature will return? I never got to try it 😭

    Nothing specific -- just that it needs more work to be satisfactory.

  • @elf_audio said:
    Yeah this sort of backfired - I didn’t foresee people getting upset about it.

    The feature is super beta. I tested it but idk how it would work in the wild, how people will take the fact that you have to download 158MB to use it. Also if you have an old phone or an andr*id phone it can run very slowly.

    I don’t feel morally ok charging extra for it because it was made by someone else and is totally open source and I sort of wince when I see others (eg algoriddim) using the exact same algorithm and massively profiting from it.

    Also, the feature isn’t finished, I intend to put a UI on it to make the workflow a bit nicer. Once that’s done I won’t be hiding it behind an Easter egg, it will be a mainline feature. I just wanted to get it out there to see what people thought of it before sinking more time into it.

    Also, the quality isn’t great (it doesn’t always extract that great and must downsample to 32khz), so I kind of wanted to test the water with a few people. And it was Easter and I love Easter egg hunts.

    I didn’t realise it would irritate so many people, probably wouldn’t do it again, but then I get flak from users all day about this or that bug, or not adding a feature that they want etc etc, so I’ve got very used to apologising haha. it’s been a learning experience! Apologies to anyone who got wound up about it.

    Funnily enough there was another unpublicised Easter egg in the previous version that a few people found which I have since removed and got

    It's an amazing app, and I found the easter egg by checking this forum, so I'm perfectly happy with the outcome :)

  • @sevenape said:
    @elf_audio while I’m not really into the feature ( I mostly sample myself these days) I think it’s cool what you did

    I’m in the same boat re: self sampling, but I’ve been using the feature to tear apart my finished tracks and it gets WEIRD (especially with my old lo-fi psych rock songs). I’ve also used it to tear apart resampled passages because you get a lot of unexpected artifacts and weird cross-contamination.

    It’s one of those features I’m sure will get better as the neural networks improve, but I hope there’s some way to keep this “early days” processing as an option. Hearing snippets of my vocals bleed through a crash cymbal really caught me off guard, and I love it.

  • Yeah the artefacts really have an eerie quality! The algorithm is the same one that all the other apps are using but is far from state of the art (it’s about 4 years old), but dunno if the newer algorithms will run with limited RAM and cpu/gpu.

    I really wish the strum feature didn’t leak but that’s my own fault. It will come when I get a chance to finish designing it. Got so many other things to do first (mostly android based 🫠)

  • edited April 2022

    @elf_audio said:
    Yeah the artefacts really have an eerie quality! The algorithm is the same one that all the other apps are using but is far from state of the art (it’s about 4 years old), but dunno if the newer algorithms will run with limited RAM and cpu/gpu.

    I really wish the strum feature didn’t leak but that’s my own fault. It will come when I get a chance to finish designing it. Got so many other things to do first (mostly android based 🫠)

    @elf_audio this new Extract Feature is excellent. Please never ever remove :) working perfect and the audio processing works fast for me. Thanks as always Marek

  • @elf_audio are we aware that when recording with the note repeat, the sequence will delete itself if you hold it down over the loop point and also if you have two fingers switching back and forth between different note repeat values?

  • I sample from the radio into the Octatrack quite a lot, and I just realized that now I can sample radio into Koala and use this fancy new Extract feature, then do further chops from there.

  • edited April 2022

    Hi guys, hope all is well.
    I’m having a strange issue here with koala note repeat.
    Notes keep disappearing during recording.
    @elf_audio
    @Samu
    am I missing or doing something wrong?
    Please have a look at video for better understanding

  • @Paa89 said:
    Hi guys, hope all is well.
    I’m having a strange issue here with koala note repeat.
    Notes keep disappearing during recording.
    @elf_audio
    @Samu
    I’m I missing or doing something wrong?
    Please have a look at video for better understanding

    Looks like a bug to me...
    ...just to be clear are you latching/sliding your finger on the re-trigger pads?
    (Ie. you never lift your finger from the screen while recording).

    I'll see if I can repeat the 'thing' later on...

    Cheers!

  • edited April 2022

    @Samu said:

    @Paa89 said:
    Hi guys, hope all is well.
    I’m having a strange issue here with koala note repeat.
    Notes keep disappearing during recording.
    @elf_audio
    @Samu
    I’m I missing or doing something wrong?
    Please have a look at video for better understanding

    Looks like a bug to me...
    ...just to be clear are you latching/sliding your finger on the re-trigger pads?
    (Ie. you never lift your finger from the screen while recording).

    I'll see if I can repeat the 'thing' later on...

    Cheers!

    This definitely happens 100%. Every single time I use the note repeat. I don’t think you’re doing anything wrong, I think unfortunately it just doesn’t work too well currently.

    If you hold the note repeat past the loop point as it loops back around, it will delete itself. Also if you have one finger on, for example, 8th notes, then put another on for example, 16th notes, the notes will trigger but the recorded sequence will delete itself. The ideal behavior would be akin to how BM3 does it where you can hold everything down and switch repeat values back and forth as it loops around and around and what you hear is what’s recorded.

    So essentially it’s ok for quick bursts of note repeat, but if you are trying to hold down the note repeat for the duration of an entire loop and/or mix in different repeat values during the same recording, there’s going to be issues

  • @db909 said:

    @Samu said:

    @Paa89 said:
    Hi guys, hope all is well.
    I’m having a strange issue here with koala note repeat.
    Notes keep disappearing during recording.
    @elf_audio
    @Samu
    I’m I missing or doing something wrong?
    Please have a look at video for better understanding

    Looks like a bug to me...
    ...just to be clear are you latching/sliding your finger on the re-trigger pads?
    (Ie. you never lift your finger from the screen while recording).

    I'll see if I can repeat the 'thing' later on...

    Cheers!

    This definitely happens 100%. Every single time I use the note repeat. I don’t think you’re doing anything wrong, I think unfortunately it just doesn’t work too well currently.

    If you hold the note repeat past the loop point as it loops back around, it will delete itself. Also if you have one finger on, for example, 8th notes, then put another on for example, 16th notes, the notes will trigger but the recorded sequence will delete itself. The ideal behavior would be akin to how BM3 does it where you can hold everything down and switch repeat values back and forth as it loops around and around and what you hear is what’s recorded.

    So essentially it’s ok for quick bursts of note repeat, but if you are trying to hold down the note repeat for the duration of an entire loop and/or mix in different repeat values during the same recording, there’s going to be issues

    @Samu @db909 has described it better.

    @elf_audio there also seems to an issue with the iPhone version (iPhone 13 pro ) : when you trying to preview a sample to import, you hear nothing but when the sample is loaded onto a pad you can hear it. Tested in both GB and Cubasis.
    Have a look

  • edited April 2022

    @Paa89 said:
    @elf_audio there also seems to an issue with the iPhone version (iPhone 13 pro ) : when you trying to preview a sample to import, you hear nothing but when the sample is loaded onto a pad you can hear it. Tested in both GB and Cubasis.
    Have a look

    I had this on the iPhoneXR too - however it was due to me having “Silent Mode” switched On on my phone (i.e. the mode that’s activated using the hardware switch on the side of my phone)

    Can you confirm if you have Silent Mode switched off?

  • edited April 2022

    @attakk said:

    @Paa89 said:
    @elf_audio there also seems to an issue with the iPhone version (iPhone 13 pro ) : when you trying to preview a sample to import, you hear nothing but when the sample is loaded onto a pad you can hear it. Tested in both GB and Cubasis.
    Have a look

    I had this on the iPhoneXR too - however it was due to me having “Silent Mode” switched On on my phone (i.e. the mode that’s activated using the hardware switch on the side of my phone)

    Can you confirm if you have Silent Mode switched off?

    I can confirm it has to do with the silent switch. Does it still happen on the XR?

  • @Paa89 said:

    @attakk said:

    @Paa89 said:
    @elf_audio there also seems to an issue with the iPhone version (iPhone 13 pro ) : when you trying to preview a sample to import, you hear nothing but when the sample is loaded onto a pad you can hear it. Tested in both GB and Cubasis.
    Have a look

    I had this on the iPhoneXR too - however it was due to me having “Silent Mode” switched On on my phone (i.e. the mode that’s activated using the hardware switch on the side of my phone)

    Can you confirm if you have Silent Mode switched off?

    I can confirm it has to do with the silent switch. Does it still happen on the XR?

    Once @elf_audio told me about the switch (I always have it set to silent - EXCEPT when I’m using Koala’s file browser now ha ha!) then everything’s been fine for me on my XR ever since 👍

  • Having to apologise for doing something nice is just fricking nuts…and very 2022.

  • Questions about Koala.

    Ideally I need to map launchpad to koala pads when in Drambo. So I can trigger koala pads via controller. Bonus. Record via same trigger pads.

    When choosing the midi version in Koala. So you can choose midi channel per koala auv3. Can you still route controller midi to each koala pad?

    When not using the midi channel version of mapping koala. So you custom map pads via koala by pressing a pad on koala screen. Then controller . Is koala recieving the different midi channels you give controller. If not. Does koala map across its/a keyboard range. So c1 mapping to pad isnt triggered by a c2 mapping of another pad?

  • edited April 2022

    Progress?

  • I’m excited about the Stems Easter egg. I have extracted stems with command line on my computer so this is way easier.

    I haven’t yet activated though - found it by accident because there seems to be a bug where if you use the Edit - make mono feature the stems are created as well.

  • edited April 2022

    This app just isnt mappable. Even with the midi ch selection in koala. It only responds from a controller. When its Koala set to all. Making a controller ( I think would be ) across 2 ipads just be triggering koala pads when you dont want to trigger and when you map 64 pads in ascending octave. Notes just trigger everywhere. Not even similar to what the launchpad is sending. Keep trying to find the right octave and use the offset but notes are getting inverted sometimes in relation to mapping. Some left. Some right. Even though mapping is ascending.

  • @sigma79 said:
    This app just isnt mappable. Even with the midi ch selection in koala. It only responds from a controller. When its Koala set to all. Making a controller ( I think would be ) across 2 ipads just be triggering koala pads when you dont want to trigger and when you map 64 pads in ascending octave. Notes just trigger everywhere. Not even similar to what the launchpad is sending. Keep trying to find the right octave and use the offset but notes are getting inverted sometimes in relation to mapping. Some left. Some right. Even though mapping is ascending.

    Koala is midi mappable. It isn’t clear from your posts why you are having problems and to what degree it has to do with how you have it routed and set up.

  • @espiegel123 said:

    @sigma79 said:
    This app just isnt mappable. Even with the midi ch selection in koala. It only responds from a controller. When its Koala set to all. Making a controller ( I think would be ) across 2 ipads just be triggering koala pads when you dont want to trigger and when you map 64 pads in ascending octave. Notes just trigger everywhere. Not even similar to what the launchpad is sending. Keep trying to find the right octave and use the offset but notes are getting inverted sometimes in relation to mapping. Some left. Some right. Even though mapping is ascending.

    Koala is midi mappable. It isn’t clear from your posts why you are having problems and to what degree it has to do with how you have it routed and set up.

    I can explain but a test will be. If you can check with drambo keyboard. Koala midi version ( so that you dont use koala own mapping ) The Koala option that gives you a midi ch and offset. Koala only responds when midi ch is set to all and worse. The keys of Drambo. Just trigger koala pads not in ascending order. Across koala abcd pages.

  • @espiegel123 said:

    @sigma79 said:
    This app just isnt mappable. Even with the midi ch selection in koala. It only responds from a controller. When its Koala set to all. Making a controller ( I think would be ) across 2 ipads just be triggering koala pads when you dont want to trigger and when you map 64 pads in ascending octave. Notes just trigger everywhere. Not even similar to what the launchpad is sending. Keep trying to find the right octave and use the offset but notes are getting inverted sometimes in relation to mapping. Some left. Some right. Even though mapping is ascending.

    Koala is midi mappable. It isn’t clear from your posts why you are having problems and to what degree it has to do with how you have it routed and set up.

  • edited April 2022

    @sigma79 said:

    @espiegel123 said:

    @sigma79 said:
    This app just isnt mappable. Even with the midi ch selection in koala. It only responds from a controller. When its Koala set to all. Making a controller ( I think would be ) across 2 ipads just be triggering koala pads when you dont want to trigger and when you map 64 pads in ascending octave. Notes just trigger everywhere. Not even similar to what the launchpad is sending. Keep trying to find the right octave and use the offset but notes are getting inverted sometimes in relation to mapping. Some left. Some right. Even though mapping is ascending.

    Koala is midi mappable. It isn’t clear from your posts why you are having problems and to what degree it has to do with how you have it routed and set up.

    I can explain but a test will be. If you can check with drambo keyboard. Koala midi version ( so that you dont use koala own mapping ) The Koala option that gives you a midi ch and offset. Koala only responds when midi ch is set to all and worse. The keys of Drambo. Just trigger koala pads not in ascending order. Across koala abcd pages.

    This sounds like a Drambo routing question. You might want to start a thread asking for help using Koala's midi mapping in Drambo and post a video there showing what you have tried

    EDIT: this message was posted at the same time as the post above

  • @espiegel123 said:

    @sigma79 said:

    @espiegel123 said:

    @sigma79 said:
    This app just isnt mappable. Even with the midi ch selection in koala. It only responds from a controller. When its Koala set to all. Making a controller ( I think would be ) across 2 ipads just be triggering koala pads when you dont want to trigger and when you map 64 pads in ascending octave. Notes just trigger everywhere. Not even similar to what the launchpad is sending. Keep trying to find the right octave and use the offset but notes are getting inverted sometimes in relation to mapping. Some left. Some right. Even though mapping is ascending.

    Koala is midi mappable. It isn’t clear from your posts why you are having problems and to what degree it has to do with how you have it routed and set up.

    I can explain but a test will be. If you can check with drambo keyboard. Koala midi version ( so that you dont use koala own mapping ) The Koala option that gives you a midi ch and offset. Koala only responds when midi ch is set to all and worse. The keys of Drambo. Just trigger koala pads not in ascending order. Across koala abcd pages.

    This sounds like a Drambo routing question. You might want to start a thread asking for help using Koala's midi mapping in Drambo and post a video there showing what you have tried

    EDIT: this message was posted at the same time as the post above

    Same as aum. Keyboard just triggers random pads and Koala only works with midi set ch set to all.

Sign In or Register to comment.