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.

Big Koala update 2023 out now

1…89111314…16

Comments

  • skiphuntskiphunt

    Can you place Koala in the effects slot of AUM and then route the input to one of the new mixer buses without recording it as a sample first?

    Basically, just using Koala’s new effects on live input?

  • SamuSamu

    @skiphunt said:
    Can you place Koala in the effects slot of AUM and then route the input to one of the new mixer buses without recording it as a sample first?

    Basically, just using Koala’s new effects on live input?

    Yes by putting the ‘mic’ effect in an effects slot on the bus you wish to use for processing.

  • HotStrangeHotStrange

    @bezz_jeens said:

    @HotStrange said:

    @bleep said:

    @HotStrange said:

    @jwmmakerofmusic said:

    @wim said:
    Koala can work either way - though it only sends midi out from tapping pads. It doesn't send midi out from sequenced patterns. That feature has been requested though I believe.

    Hopefully this will be one of the features of the big update. We shall see. I love Koala as it currently functions. :)

    If we can send midi out from the sequences we made in the app I would lose my mind lol. Koalas sequencer is capable of some wild stuff so sending that elsewhere would be super cool.

    I've been sleeping on Koala sequencing, now wondering what "wild stuff" it is capable of? :)

    I use Koala for noise, ambient, drones, etc. It can definitely get wild when you start messing with the pitch and tempos + effects.

    Can you sequence pitch and and tempo and stuff? I'm so curious what you mean because I've been using the Koala sequencer like a simple piano roll with velocity and chance.

    No, I just meant adjusting the pitch manually and recording that. Or just simply pitching samples waaaay down. I would love to see automation added in an update some day though.

  • Antos3345Antos3345

    It's definitely a great sampler, but one thing I don't understand is why it doesn't have any envelopes for a filter like ADSR or does it? I mean if I have a pad and want a slow attack with a filter, how is this done? Any ADSRs?

  • skiphuntskiphunt
    edited September 2023

    @Samu said:

    @skiphunt said:
    Can you place Koala in the effects slot of AUM and then route the input to one of the new mixer buses without recording it as a sample first?

    Basically, just using Koala’s new effects on live input?

    Yes by putting the ‘mic’ effect in an effects slot on the bus you wish to use for processing.

    Thanks, but I was asking about the brand new effects that are included in the new Mixer IAP. I’d like to do the same thing, but use the new effects on live input that are in the Mixer. It doesn’t look like it’s possible, but I thought I’d see if there was a way to do it without recording a sample first to send to the buses in the new IAP mixer feature.

  • HotStrangeHotStrange

    @Antos3345 said:
    It's definitely a great sampler, but one thing I don't understand is why it doesn't have any envelopes for a filter like ADSR or does it? I mean if I have a pad and want a slow attack with a filter, how is this done? Any ADSRs?

    When you click edit to edit the sample it was an AR envelope. It’s mostly to shape the transients it seems but it can soften the attack a bit. If you’re wanting to make pad sounds from samples you’re probably better off with Samplewiz, Elsa, Chameleon, etc.

  • cokomairenacokomairena

    @Antos3345 said:
    It's definitely a great sampler, but one thing I don't understand is why it doesn't have any envelopes for a filter like ADSR or does it? I mean if I have a pad and want a slow attack with a filter, how is this done? Any ADSRs?

    Put koala in resample mode, start recording on a pad, do your envelope by hand with the filter fx 😅

  • wimwim

    @skiphunt said:

    @Samu said:

    @skiphunt said:
    Can you place Koala in the effects slot of AUM and then route the input to one of the new mixer buses without recording it as a sample first?

    Basically, just using Koala’s new effects on live input?

    Yes by putting the ‘mic’ effect in an effects slot on the bus you wish to use for processing.

    Thanks, but I was asking about the brand new effects that are included in the new Mixer IAP. I’d like to do the same thing, but use the new effects on live input that are in the Mixer. It doesn’t look like it’s possible, but I thought I’d see if there was a way to do it without recording a sample first to send to the buses in the new IAP mixer feature.

    You can. Like this:

  • echooperaechoopera

    Links to the samples in the Project in the YouTube Description.

    Enjoy :)

  • gusgranitegusgranite

    @elf_audio would love to be able to make the mixer faders full screen for long-throw. Have added to the Discord feature request channel.

  • skiphuntskiphunt

    Awesome! Thank you! :)

    @wim said:

    @skiphunt said:

    @Samu said:

    @skiphunt said:
    Can you place Koala in the effects slot of AUM and then route the input to one of the new mixer buses without recording it as a sample first?

    Basically, just using Koala’s new effects on live input?

    Yes by putting the ‘mic’ effect in an effects slot on the bus you wish to use for processing.

    Thanks, but I was asking about the brand new effects that are included in the new Mixer IAP. I’d like to do the same thing, but use the new effects on live input that are in the Mixer. It doesn’t look like it’s possible, but I thought I’d see if there was a way to do it without recording a sample first to send to the buses in the new IAP mixer feature.

    You can. Like this:

  • musikeermusikeer

    Anyone?

    Does it play the correct samples when used as an AUv3 in Cubasis, without having to open the interface, as the bug was before the update?

    I've replaced Koala with Sitala as an AUv3 sample player until knowing if Koala plays the correct samples dependably.

  • GrandbearGrandbear

    @musikeer said:
    Anyone?

    Does it play the correct samples when used as an AUv3 in Cubasis, without having to open the interface, as the bug was before the update?

    I've replaced Koala with Sitala as an AUv3 sample player until knowing if Koala plays the correct samples dependably.

    Nope, the bug remains

  • GrandbearGrandbear
    edited September 2023

    @Grandbear said:

    @musikeer said:
    Anyone?

    Does it play the correct samples when used as an AUv3 in Cubasis, without having to open the interface, as the bug was before the update?

    I've replaced Koala with Sitala as an AUv3 sample player until knowing if Koala plays the correct samples dependably.

    Nope, the bug remains

    Also, it looks like the note-to-pad mapping changes with the AU plugin size. Has anyone experienced this?

    Edit: alright, using Koala’s custom MIDI map fixed both issues for me. I guess it’s not an audio engine initialization problem, but a dynamic MIDI mapping one.

  • espiegel123espiegel123

    @Grandbear said:

    @Grandbear said:

    @musikeer said:
    Anyone?

    Does it play the correct samples when used as an AUv3 in Cubasis, without having to open the interface, as the bug was before the update?

    I've replaced Koala with Sitala as an AUv3 sample player until knowing if Koala plays the correct samples dependably.

    Nope, the bug remains

    Also, it looks like the note-to-pad mapping changes with the AU plugin size. Has anyone experienced this?

    Edit: alright, using Koala’s custom MIDI map fixed both issues for me. I guess it’s not an audio engine initialization problem, but a dynamic MIDI mapping one.

    The same pad is always mapped to the same midi trigger but the pads get moved around when you resize in a way that might not be obvious. The app was originally designed as 4*4 portrait aspect interface and the pads move around to accommodate other aspects ratios.

    But I think you will find that the mapping doesn’t really change. I.e. if the pad with sound A is triggered by midi note 32, the pad with sound A continues to be triggered by note 32 after the pads shift around whe the window resizes.

  • espiegel123espiegel123

    @musikeer said:
    Anyone?

    Does it play the correct samples when used as an AUv3 in Cubasis, without having to open the interface, as the bug was before the update?

    I've replaced Koala with Sitala as an AUv3 sample player until knowing if Koala plays the correct samples dependably.

    I don’t think this is particular to Cubasis. I think it is true in all hosts.

  • GrandbearGrandbear
    edited September 2023

    @espiegel123 said:

    @Grandbear said:

    @Grandbear said:

    @musikeer said:
    Anyone?

    Does it play the correct samples when used as an AUv3 in Cubasis, without having to open the interface, as the bug was before the update?

    I've replaced Koala with Sitala as an AUv3 sample player until knowing if Koala plays the correct samples dependably.

    Nope, the bug remains

    Also, it looks like the note-to-pad mapping changes with the AU plugin size. Has anyone experienced this?

    Edit: alright, using Koala’s custom MIDI map fixed both issues for me. I guess it’s not an audio engine initialization problem, but a dynamic MIDI mapping one.

    The same pad is always mapped to the same midi trigger but the pads get moved around when you resize in a way that might not be obvious. The app was originally designed as 4*4 portrait aspect interface and the pads move around to accommodate other aspects ratios.

    But I think you will find that the mapping doesn’t really change. I.e. if the pad with sound A is triggered by midi note 32, the pad with sound A continues to be triggered by note 32 after the pads shift around whe the window resizes.

    That’s not what I’m seeing, though. I’m playing a sequence of a single note and when I resize the plugin window it stops playing. Changing it back to the original size makes it play again. Regardless, using a custom MIDI map solves both problems for me.

    Here’s a quick video in AUM demonstrating the issue:
    https://share.icloud.com/photos/009LDMhh5h2s7gOIU6tVOhmLQ

  • musikeermusikeer
    edited September 2023

    @Grandbear said:

    @Grandbear said:

    @musikeer said:
    Anyone?

    Does it play the correct samples when used as an AUv3 in Cubasis, without having to open the interface, as the bug was before the update?

    I've replaced Koala with Sitala as an AUv3 sample player until knowing if Koala plays the correct samples dependably.

    Nope, the bug remains

    Also, it looks like the note-to-pad mapping changes with the AU plugin size. Has anyone experienced this?

    Edit: alright, using Koala’s custom MIDI map fixed both issues for me. I guess it’s not an audio engine initialization problem, but a dynamic MIDI mapping one.

    Thanks, Sir. Sitala seems the way to go for simple rock solid sample playback as a AUv3 plugin. Koala is great as a sampler and whatever new features etc. there are now. Both very exceptional apps!

  • pbrianpbrian

    @gregsmith said:
    But I’m trying to think what else would get me excited. Elastique as the timestretch algorithm? Better sampling like in bm3? (I don’t use bm3 but everyone says it’s best sampler on iOS)

    Anyone knows if this has been improved in the update? (Elastique as the realtime timestrech algo)

  • sigma79sigma79

    Why only 8 outputs.

    Fac drum ( although not a sampler needed )

    Has 16.

  • gosnotegosnote

    @RaquNox said:

    @gosnote said:
    Great to see Koala developing further! As my music making has moved towards desktop in the last year or two, but Koala is still heavily used on iOS in my workflow, my personal wish would be features that improve this iOS to desktop workflow. The ultimate of course being a stripped down Koala VST plugin for transferring all the sampling and sketching I enjoy using the iPad for, to my desktop DAW. However, smaller steps towards a smoother iOS to desktop transition would be: transferring the names of the pads and midi mapping to the exported pad file names and midi export.

    Koala is a universal app and works on the Apple Silicone Macs standalone or as an AuV3 plugin (Logic and Ableton support those for example).

    @RaquNox - yes that's true - I am using Cubase which supports VST3.

  • shinyisshinyshinyisshiny

    @echoopera vibey track!

  • sigma79sigma79

    Makes sense to be 8 out ( with 64 pads )

    However. When you clear a pad. It clears the multiout channel selected.

    Is there no way to save a template of multiout routing.

    Having to select the output routing.

    Everytime you sample ( 64 times per app )

    and everytime you redo a sample ?

    Is this in the update as havent bought ( maybe not needed )

  • sigma79sigma79

    Can you save routing in the update ?

  • hghonhghon

    @sigma79 said:
    Can you save routing in the update ?

    No you can’t. Routing is reset when a sample is removed.

  • jwmmakerofmusicjwmmakerofmusic

    @hghon said:

    @sigma79 said:
    Can you save routing in the update ?

    No you can’t. Routing is reset when a sample is removed.

    I will say while it could be a bit more cumbersome for some to have to reroute a sample when an old one is trashed, it does make logical sense (at least in my mind lol).

  • cokomairenacokomairena

    @jwmmakerofmusic said:

    @hghon said:

    @sigma79 said:
    Can you save routing in the update ?

    No you can’t. Routing is reset when a sample is removed.

    I will say while it could be a bit more cumbersome for some to have to reroute a sample when an old one is trashed, it does make logical sense (at least in my mind lol).

    Makes no sense over here, i think is just that marek hasn’t programmed it yet. Is any work around?

  • cokomairenacokomairena

    Work around: append the new sample instead of replacing it and it will preserve its properties, then crop

    A lot of work, but i guess that’s why they are called work around

  • AudioGusAudioGus
    edited September 2023

    @cokomairena said:
    Work around: append the new sample instead of replacing it and it will preserve its properties, then crop

    A lot of work, but i guess that’s why they are called work around

    Thanks for the workaround but yah, that is not great, hope it gets adressed.

  • tyslothrop1tyslothrop1

    I would like templates for routing, too. One could be, that samples on the first page go to the first mixbus, second page to the second bus and so on.

Sign In or Register to comment.

© Vanilla Keystone Theme 2024