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 Update: AUv3 Support with Mixer Add-On!

1235

Comments

  • @Gavinski said:

    Yes, I just can't help but feel that this is a browsing system designed by someone with a very small number of AUv3s on their system. A search bar is essential really.

    Could very well be and personally I see no sensible reason to have >200 AUv3's installed because honestly how many of those would get used on a daily basis?!

  • @Samu said:

    @Gavinski said:

    Yes, I just can't help but feel that this is a browsing system designed by someone with a very small number of AUv3s on their system. A search bar is essential really.

    Could very well be and personally I see no sensible reason to have >200 AUv3's installed because honestly how many of those would get used on a daily basis?!

    Well, tbh even having to scroll through 200 is a pain. There should ideally be a search bar, end of story!

  • @oscillotus said:
    Is it normal for Skulptur to appear in the instruments but not the FX?

    Bump! Could someone validate this?

  • @Gavinski said:

    @Samu said:

    @Gavinski said:

    Yes, I just can't help but feel that this is a browsing system designed by someone with a very small number of AUv3s on their system. A search bar is essential really.

    Could very well be and personally I see no sensible reason to have >200 AUv3's installed because honestly how many of those would get used on a daily basis?!

    Well, tbh even having to scroll through 200 is a pain. There should ideally be a search bar, end of story!

    I agree with having a search bar in the AUv3 window. Would make life easier.

  • Search for Samples could be handy too (ie. search thru all locations), I mean when search is added to AUv3's search samples are the next logical step...

  • @Gavinski said:

    @Robin2 said:
    @elf_audio, in line with some others it seems, I feel the AUv3 browsing/selection is a bit more long winded and awkward than it could be.

    How about simply having the plugin icons and names simply placed next to developer’s names as I’ve mocked up here for the Audio Damage instruments. This would make things a bit more immediate and longer lists of plugins from a developer than would immediately fit could be accessed by scrolling left/right on the list?

    Part of the problem with initially having to go via the name the developer’s have chosen is that this name doesn’t always look familiar (for example, NIRA makes sense as Alexander Zolotov’s handle once you know he uses the NightRadio name for the music he makes but if you don’t know that, NIRA could be a bit confusing). By adopting an approach like I’m suggesting, you’d immediately see some of the plugin icons and names so you’d know what plugins belonged to that developer even if the name didn’t look familiar.

    Just a thought, cheers.

    Yes, I just can't help but feel that this is a browsing system designed by someone with a very small number of AUv3s on their system. A search bar is essential really.

    I don’t have the luxury of having lots and lots of Audio Units installed at any one time because I’m always short of storage space so that’s true, I don’t have many installed compared to some.

    Having said that, just because people here on this forum have hundreds and hundreds of Audio Units, I don’t think you can jump to the conclusion that everyone making music on iOS must also have. People here - myself included - have a particular interest in these apps, just as the viewers of your channel and Patreon members do, but we don’t represent all iOS music makers so we surely can’t draw reliable conclusions based on that?

    In my post though, I was suggesting it as a way of making things a bit quicker (admittedly for those without lots and lots and lots of plugins - I do take your point) and more importantly as a way of negating the problem that not all developer titles simply state their name and can therefore be confusing.

    Plus, I never said this was a suggestion instead of a search bar!

  • @Robin2 said:

    @Gavinski said:

    @Robin2 said:
    @elf_audio, in line with some others it seems, I feel the AUv3 browsing/selection is a bit more long winded and awkward than it could be.

    How about simply having the plugin icons and names simply placed next to developer’s names as I’ve mocked up here for the Audio Damage instruments. This would make things a bit more immediate and longer lists of plugins from a developer than would immediately fit could be accessed by scrolling left/right on the list?

    Part of the problem with initially having to go via the name the developer’s have chosen is that this name doesn’t always look familiar (for example, NIRA makes sense as Alexander Zolotov’s handle once you know he uses the NightRadio name for the music he makes but if you don’t know that, NIRA could be a bit confusing). By adopting an approach like I’m suggesting, you’d immediately see some of the plugin icons and names so you’d know what plugins belonged to that developer even if the name didn’t look familiar.

    Just a thought, cheers.

    Yes, I just can't help but feel that this is a browsing system designed by someone with a very small number of AUv3s on their system. A search bar is essential really.

    I don’t have the luxury of having lots and lots of Audio Units installed at any one time because I’m always short of storage space so that’s true, I don’t have many installed compared to some.

    Having said that, just because people here on this forum have hundreds and hundreds of Audio Units, I don’t think you can jump to the conclusion that everyone making music on iOS must also have. People here - myself included - have a particular interest in these apps, just as the viewers of your channel and Patreon members do, but we don’t represent all iOS music makers so we surely can’t draw reliable conclusions based on that?

    In my post though, I was suggesting it as a way of making things a bit quicker (admittedly for those without lots and lots and lots of plugins - I do take your point) and more importantly as a way of negating the problem that not all developer titles simply state their name and can therefore be confusing.

    Plus, I never said this was a suggestion instead of a search bar!

    Oh yeah, I never took it that way. Your suggestion is great. And having a search bar would also be great.

  • Personally for me, my memory is not so good for names, so although a search is useful I like Robins idea of listing the icons horizontally. I don’t think it even needs the company identifier as a lot of them are a bit obscure and it just uses space.

  • Pretty sure there are plans to improve the plugin list, it was probably just path of least resistance for now :)

  • After playing around for a couple hours. I still wish for a global play/stop option in all the menu’s. There has to be a way to slip it into the sample screen somewhere. And of course an option for chords.

  • @FunksMaName said:
    Pretty sure there are plans to improve the plugin list, it was probably just path of least resistance for now :)

    I'm going to assume the same. I think point was to implement the AUv3 functionality in the first place. I'm sure Marek will make the plugin list more robust in the future now that it's implemented in this form.

  • @stormywaterz said:
    After playing around for a couple hours. I still wish for a global play/stop option in all the menu’s. There has to be a way to slip it into the sample screen somewhere. And of course an option for chords.

    +1 for global play/stop !

  • I don't want to sound like an unsatisfied customer, it's the contrary really, I'm diving back in and love it.

    A feature I'd like to see is MIDI feedback for things like sample volume/pitch, sample start, etc. When I use Koala with the MIDI Fighter Twister to experiment around, I always get parameter jump from one sample to another.

  • Does the sequencer page record, and play back, pitch bends and vibrato from instruments like the SWAM ones?

  • @FriedTapeworm said:
    Does the sequencer page record, and play back, pitch bends and vibrato from instruments like the SWAM ones?

    There is no parameter recording as of now. The workflow in this case would be to resample to a new pad.

  • @oscillotus said:

    @stormywaterz said:
    After playing around for a couple hours. I still wish for a global play/stop option in all the menu’s. There has to be a way to slip it into the sample screen somewhere. And of course an option for chords.

    +1 for global play/stop !

    On the sample page if you move the fx/headphone and mic down you can fit the play stop just like the rest of the pages. That’s the view from the iPhone so it is doable.

  • @oscillotus said:

    @stormywaterz said:
    After playing around for a couple hours. I still wish for a global play/stop option in all the menu’s. There has to be a way to slip it into the sample screen somewhere. And of course an option for chords.

    +1 for global play/stop !

    +2
    I wish for play/stop on all pages every time I use Koala. It gets frustrating without it.

  • @stormywaterz said:

    @oscillotus said:

    @stormywaterz said:
    After playing around for a couple hours. I still wish for a global play/stop option in all the menu’s. There has to be a way to slip it into the sample screen somewhere. And of course an option for chords.

    +1 for global play/stop !

    On the sample page if you move the fx/headphone and mic down you can fit the play stop just like the rest of the pages. That’s the view from the iPhone so it is doable.

    Lol… @stormywaterz, I thought you were saying that this was already possible and a little-known Easter-Egg-type feature, so I spent fifteen minutes pressing the mic/fx buttons and sliding down, long-pressing and sliding, etc, to no avail. Only then did it finally occur to me that your message was a suggestion to the developer, not the imparting of hidden wisdom to us users. That’s what chronic insomnia does to you.

  • It is sort of mystifying why in all these years, having been so open to other suggestions, Transport on every page has been consistently turned down. I don't get it.

    That's not a complaint, just one of those niggly little things that I wish I could make sense of.

  • Yes with update I’m going to give Koala another go. I watched quite a few youtube videos to reacquaint myself and everyone is:

    • Working on the sample page
    • Switching to the sequencer page just to start the transport
    • Switching back to the sample page to do something
    • Switching back to the sequence page to stop the transport
  • @wim said:
    It is sort of mystifying why in all these years, having been so open to other suggestions, Transport on every page has been consistently turned down. I don't get it.

    That's not a complaint, just one of those niggly little things that I wish I could make sense of.

    It is very strange.

    Having said that, I was under the impression that the official position on AU hosting support was a hard no to keep things simple and keep more parity between platforms and then this update happens. So maybe there’s hope?

    Anyway, I’ll certainly add my voice to those calling for transport controls on every page. @elf_audio, it really does genuinely get in the way of workflow.

  • @oscillotus said:
    @janm31415 @elf_audio Percussive seems to get out of sync after exactly 12 bars. This seems to only happen in Percussive yet. Just to let you know ;)

    Hi, thanks for letting me know. I will investigate and see whether I can find a fix.

  • @FunksMaName said:
    Quantized recording IS here.

    I saw mention of gaps in recording - it's been officially stated there's currently no latency compensation inside Koala, so anything you add that adds latency (anything with lookahead or latent instruments or effects added to buses) will result in slightly off recordings (latency gap at the start)... record a smidge longer, and tidy up the start (or use auto crop start if that works for what you're doing)

    Enjoy :)

    This only work on standalone? Would be cool to be able to capture bars like this with koala loaded in fx slot on AUM channel(s) ..

  • @mikejohn said:

    This only work on standalone? Would be cool to be able to capture bars like this with koala loaded in fx slot on AUM channel(s) ..

    Go to Settings and turn on "Hold to record"

  • @mikejohn said:
    This only work on standalone? Would be cool to be able to capture bars like this with koala loaded in fx slot on AUM channel(s) ..

    Definitely works inside AUM :) make sure transport is running, and 'hold to record' is ON

  • @FunksMaName said:

    @mikejohn said:
    This only work on standalone? Would be cool to be able to capture bars like this with koala loaded in fx slot on AUM channel(s) ..

    Definitely works inside AUM :) make sure transport is running, and 'hold to record' is ON

    Ah .. perfect. Thanks!

  • The problem with the quantised recording is that it is not sample accurate, even without adding any effects. It results in cutting off a small part of the start and adding it at the end. I measured it in an audio editor and it is 4ms out.

  • @cytone said:
    The problem with the quantised recording is that it is not sample accurate, even without adding any effects. It results in cutting off a small part of the start and adding it at the end. I measured it in an audio editor and it is 4ms out.

    what's 4ms amongst friends? :tongue:
    is this just using internal samples and nothing else? (no auv3s?)

  • @FunksMaName said:

    @cytone said:
    The problem with the quantised recording is that it is not sample accurate, even without adding any effects. It results in cutting off a small part of the start and adding it at the end. I measured it in an audio editor and it is 4ms out.

    what's 4ms amongst friends? :tongue:
    is this just using internal samples and nothing else? (no auv3s?)

    Tested it just playing a kick drum sample.

  • edited May 28

    Looking fwd to trying out my new controller with this.

Sign In or Register to comment.