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

1…5758606263…84

Comments

  • manaftermidnightmanaftermidnight

    I think I solved the issue with fx being stuck using a simple mozaic script which resets the midi cc on stop and start (just to be sure).

  • SamuSamu

    I think the most fun I've had with the latest Koala update is to take a very short sample and stretch it to 8bars for some insane granular mayhem :)

  • xraydashxraydash

    @dasgoods said:

    @manaftermidnight said:

    If anyone is interested I can upload the Audiobus/Xequence 2 template I am using. I have midi mapped the sequences in Koala to a drum template in Xequence 2 as well.

    Yes please do share :smile:

    +1 Thanks!

  • manaftermidnightmanaftermidnight

    Will upload tomorrow B)

  • GeorgeL909GeorgeL909
    edited February 2021

    @manaftermidnight said:
    Really enjoying the samurai update!

    My workflow is that I make, say 8 patterns, in Koala and then I make a song structure with Xequence 2. Koala and Xequence 2 are hosted in Audiobus.

    I have midi mapped all the performance effects to instruments in Xequence 2 so that I can record automation. Works really well. But if I stop the playback in the middle of a track with automation the effect is not reset in Koala even though hold is not enabled. Xequence 2 is supposed to send a reset message on stop for all controllers when playback is stopped. Could be a lot of different things causing this behaviour I assume.

    Another thing I have noticed is that if patterns have different lengths in Koala and you skip between these patterns, sometimes (or always) playback will continue from the middle/somewhere in the pattern to which I have changed (not sure if that makes sense). Would be great if there was an option to always start pattern from the beginning when changing patterns, if that is possible

    If anyone is interested I can upload the Audiobus/Xequence 2 template I am using. I have midi mapped the sequences in Koala to a drum template in Xequence 2 as well.

    Koala is awesome, thank you!

    I use an extremely similar setup, but yeah I don't think there is a quantized clip launch option to start a sequence from the beginning in koala yet, you just gotta time it for right at the end I think.

    My workaround is I just compose everything in xequence and route the midi to koala, bypassing the koala sequencer altogether. It's not a bad sequencer, but if I'm using xequence for other stuff anyways, why not...

    This works great for me if I'm using koala as mainly a drum machine for one shots but I don't think you can route both midi for the pads and chromatic stuff at the same time from xequence.

    For what it's worth though, this setup turns koala into one of the most varied and versatile pallets of drum sounds I could add to a song because you can do so much with all the banks and effects and resampling, and trigger what? Like 64 different samples via midi or something like that. That is some huge drum variety with a very low cpu footprint! It's been my go to if I need a million one shots in a track, which I always do...

  • [Deleted User][Deleted User]
    edited February 2021
    The user and all related content has been deleted.
  • reasOnereasOne

    The main reason i want auv3 is to sample a pad or sequence made in koala, from koala, thru my fav effects and directly back into a pad on koala.
    So much better results than sampling to something else just to import that sample back into koala.

  • manaftermidnightmanaftermidnight

    I got set back with uploading the template because my iPad updated to iOS 14 and now the mozaic script code is not working suddenly :|

  • PxlhgPxlhg

    I still get a lot of "Bounce" crashes. I now have gotten the habit to press "Save" before I bounce anything, and that usually works fine but now I have worked with some longer, well 8-16 bar loops, and had some too frequent crashes. [Air3 iOS14.4]. @elf_audio

  • elf_audioelf_audio

    @Pxlhg ah sorry about that - do you mean the Bounce in the TOOLS menu? And also are you bouncing a sample that has been stretched with the modern mode? Any details would be great - if I can replicate it, I can fix it, and I’ll have it out early next week, or earlier if I can sneak in a few hours this weekend

  • PxlhgPxlhg

    @elf_audio said:
    @Pxlhg ah sorry about that - do you mean the Bounce in the TOOLS menu? And also are you bouncing a sample that has been stretched with the modern mode? Any details would be great - if I can replicate it, I can fix it, and I’ll have it out early next week, or earlier if I can sneak in a few hours this weekend

    Yes, the one in the TOOLS menu, wasn't aware of any other way? I don't always choose a mode but I think, if I do: MODERN is what I use the least and probably BEATS and REPITCH the most. Guess MODERN is default state then(?). If you're not saving regularly your guaranteed a crash after a few bounces. I do like to have clean clips (red crop area from end to end). I seldom use normalize ... hmm, just realizing there is a crop tool at the top ... maybe should use that instead of bounce ...

  • xraydashxraydash

    @manaftermidnight said:
    I got set back with uploading the template because my iPad updated to iOS 14 and now the mozaic script code is not working suddenly :|

    That sucks that the update broke your workflow. I didn’t realize mozaic was part of the equation. Interesting! No worries or hurries. Keep us in mind when you are hopefully able to get it worked out again.

  • OscarSouthOscarSouth
    edited February 2021

    Jumping into on this thread at this point because I'm an instant Koala convert. This app is amazing -- didn't even know that I needed this but and in 24 hours I've picked up the technical details and now it's the heart of my workflow.

    Question to the experts -- any way to synch Koala's tempo to either Audiobus or to an incoming MIDI clock? It seems to respond to incoming transport synch data, but not the clock tempo. Link is not a viable option in this workflow.

    Cheers!
    Oscar

  • manaftermidnightmanaftermidnight

    @xraydash said:

    @manaftermidnight said:
    I got set back with uploading the template because my iPad updated to iOS 14 and now the mozaic script code is not working suddenly :|

    That sucks that the update broke your workflow. I didn’t realize mozaic was part of the equation. Interesting! No worries or hurries. Keep us in mind when you are hopefully able to get it worked out again.

    Yeah, it's strange. I am using a simple Mosaic code just to reset the performance effects in koala so that don't get stuck when playback stops. After the update it seems like only one midi cc message is received by Koala when using the @onhoststop and @onhoststart events. If I also try to send several notes using the note event only note seems to be received. Not sure what is causing this and if it is Mozaic or Koala that is the culprit :)

  • manaftermidnightmanaftermidnight

    Im > @OscarSouth said:

    Jumping into on this thread at this point because I'm an instant Koala convert. This app is amazing -- didn't even know that I needed this but and in 24 hours I've picked up the technical details and now it's the heart of my workflow.

    Question to the experts -- any way to synch Koala's tempo to either Audiobus or to an incoming MIDI clock? It seems to respond to incoming transport synch data, but not the clock tempo. Link is not a viable option in this workflow.

    Cheers!
    Oscar

    If you enable inter app audio sync in both koala and Audiobus the tempo should sync. Transport is handled by Audiobus.

  • OscarSouthOscarSouth

    @manaftermidnight said:
    Im > @OscarSouth said:

    Jumping into on this thread at this point because I'm an instant Koala convert. This app is amazing -- didn't even know that I needed this but and in 24 hours I've picked up the technical details and now it's the heart of my workflow.

    Question to the experts -- any way to synch Koala's tempo to either Audiobus or to an incoming MIDI clock? It seems to respond to incoming transport synch data, but not the clock tempo. Link is not a viable option in this workflow.

    Cheers!
    Oscar

    If you enable inter app audio sync in both koala and Audiobus the tempo should sync. Transport is handled by Audiobus.

    Ah excellent -- thanks. I'd not enabled it in Audiobus (usually just clock everything by MIDI so it's not necessary).

    Cheers!

  • GeorgeL909GeorgeL909

    @Samu said:
    I think the most fun I've had with the latest Koala update is to take a very short sample and stretch it to 8bars for some insane granular mayhem :)

    Dude, that's such a good idea! Honestly didn't even think to try this. This could turn koala into an exceptional drone generator. With some distortion and deep reverb... Such a good idea...

  • elf_audioelf_audio

    @Samu @GeorgeL909 Yeah I def recommend trying that and all 3 stretch modes will give you different results.

    If you’re in MODERN then technically it’s not granular but SPECTRAL! One day it would be awesome to make a whole app about that.

    RETRO is actually a synced granular effect (technically called PSOLA) - this ones cool because the pitch knob is a bit more interactive.

    I decided against putting more sliders in for the stretch algorithms in favour of simplicity but they have a lot of interesting parameters internally.

  • KmaticKmatic

    Samurai a fantastic update now koala is unbeatable number 1

  • wimwim

    @manaftermidnight said:

    @xraydash said:

    @manaftermidnight said:
    I got set back with uploading the template because my iPad updated to iOS 14 and now the mozaic script code is not working suddenly :|

    That sucks that the update broke your workflow. I didn’t realize mozaic was part of the equation. Interesting! No worries or hurries. Keep us in mind when you are hopefully able to get it worked out again.

    Yeah, it's strange. I am using a simple Mosaic code just to reset the performance effects in koala so that don't get stuck when playback stops. After the update it seems like only one midi cc message is received by Koala when using the @onhoststop and @onhoststart events. If I also try to send several notes using the note event only note seems to be received. Not sure what is causing this and if it is Mozaic or Koala that is the culprit :)

    Try adding a small random delay to your send midi events. Sometimes hosts can't process a lot of simultaneous midi events. It does seem that a Mozaic or AUM update somewhere made this issue more pronounced. I don't think it's iOS version related because I'm on 13.7.

    If I'm sending multiple events at once, I add a small delay between them. Something like:

    SendMidiNoteOn 15, 36
SendMidiNoteOff 15, 36, 5
SendMidiNoteOn 15, 37, 10
SendMidiNoteOff 15, 37, 15
  • SamuSamu
    edited February 2021

    @elf_audio I think I just had by first crash when doing bounce (tools menu).

    I admit it was 'bounce abuse', pitch up 12, bounce, pitch up 12, bounce, pitch up 12 bounce crash but it doesn't happen every time, this could eventually be memory related? (it was a 4 bar sound that I pitched up a few times with stretch disabled) pitch down would double the size of the sample so that 'gotcha' I'm aware of...

    My iPhone 8 is set to automatically send the crashlogs to developers thus there's nothing left on my device :(

    What about adding a +/-24 (Or even more 36-48?) range to the pitch knob?
    It's a very good 'feature' for creative tuning/transposing.
    (Turn a short nail-clipper sound to gong from hell or snapped toothpick to broken bone)

    Sometimes I play the 'grid' and think, hmm, this is the note I need to bounce the sample to and with +/-12 avail I need to do it multiple times.

    I can imagine the stretch things having more parameters under the hood, for the 'retro' it would definitely be handy with 'more intervals' for grain control :)
    (It's the classic 'Tracker Trick' to scan thru the sample by re-triggering the sound at increasing offset, anything from 1/4 to 1/128 notes).

    The range of the 'Vol Knob' could also be increased to heavily clip/saturate the sample for creative purposes?
    Go crazy +100db :D (Or add an additional 'Gain/Saturate' knob to keep levels under control).
    https://socalabs.com/developer-tools/hugegain/

    But stay true to Koala Spirit by keeping things simple!
    (My brain goes on overdrive when I bump into apps that inspire me).

    Cheers!

  • manaftermidnightmanaftermidnight

    :# > @wim said:

    @manaftermidnight said:

    @xraydash said:

    @manaftermidnight said:
    I got set back with uploading the template because my iPad updated to iOS 14 and now the mozaic script code is not working suddenly :|

    That sucks that the update broke your workflow. I didn’t realize mozaic was part of the equation. Interesting! No worries or hurries. Keep us in mind when you are hopefully able to get it worked out again.

    Yeah, it's strange. I am using a simple Mosaic code just to reset the performance effects in koala so that don't get stuck when playback stops. After the update it seems like only one midi cc message is received by Koala when using the @onhoststop and @onhoststart events. If I also try to send several notes using the note event only note seems to be received. Not sure what is causing this and if it is Mozaic or Koala that is the culprit :)

    Try adding a small random delay to your send midi events. Sometimes hosts can't process a lot of simultaneous midi events. It does seem that a Mozaic or AUM update somewhere made this issue more pronounced. I don't think it's iOS version related because I'm on 13.7.

    If I'm sending multiple events at once, I add a small delay between them. Something like:

    SendMidiNoteOn 15, 36
SendMidiNoteOff 15, 36, 5
SendMidiNoteOn 15, 37, 10
SendMidiNoteOff 15, 37, 15

    Yes! I think that maybe solved it. I did try adding a delay earlier, but I set the delay to the same time for each event :#

  • wimwim

    @manaftermidnight said:
    :# > @wim said:

    @manaftermidnight said:

    @xraydash said:

    @manaftermidnight said:
    I got set back with uploading the template because my iPad updated to iOS 14 and now the mozaic script code is not working suddenly :|

    That sucks that the update broke your workflow. I didn’t realize mozaic was part of the equation. Interesting! No worries or hurries. Keep us in mind when you are hopefully able to get it worked out again.

    Yeah, it's strange. I am using a simple Mosaic code just to reset the performance effects in koala so that don't get stuck when playback stops. After the update it seems like only one midi cc message is received by Koala when using the @onhoststop and @onhoststart events. If I also try to send several notes using the note event only note seems to be received. Not sure what is causing this and if it is Mozaic or Koala that is the culprit :)

    Try adding a small random delay to your send midi events. Sometimes hosts can't process a lot of simultaneous midi events. It does seem that a Mozaic or AUM update somewhere made this issue more pronounced. I don't think it's iOS version related because I'm on 13.7.

    If I'm sending multiple events at once, I add a small delay between them. Something like:

    SendMidiNoteOn 15, 36
SendMidiNoteOff 15, 36, 5
SendMidiNoteOn 15, 37, 10
SendMidiNoteOff 15, 37, 15

    Yes! I think that maybe solved it. I did try adding a delay earlier, but I set the delay to the same time for each event :#

    With note on/off messages it's trickier because they need to occur in the right order. If you're sending cc's and the order doesn't matter it can be a bit more elegant: SendMidiCC 15, 20, 127, (Random 0, 10)

  • steve99steve99
    edited February 2021

    @RajahP said:
    A ‘Back’ button (to AUM) would be nice.. IAA..😃

    +1 on that for me as my one and only frustration. I’m finding Koala so inspiring that I need to get back fast to AUM to pile in more stuff (on the fly).

  • israeliteisraelite

    I have built a pretty complex sequence in koala and wanted to export it to Cubasis or NS2 for further processing, but haven't found a way to do it.
    Is it even possible? I need samples separately and most optimally the midi file with the sequence.

  • SamuSamu

    @israelite said:
    I have built a pretty complex sequence in koala and wanted to export it to Cubasis or NS2 for further processing, but haven't found a way to do it.
    Is it even possible? I need samples separately and most optimally the midi file with the sequence.

    You can export the sequences as stems.

    Exporting midi is kinda redundant since you'd have to re-build all the instruments in NS2 and Cubasis 3 and the samplers in them are not up to the task especially if time-stretching is used...

    Export stems from Koala and in NS2 you can load the samples into slate pads and trigger them from a pattern.
    In Cubasis drag the stem files to audio tracks.

    That's one way to do it.

  • robklotzbyrobklotzby

    What would be the easiest way to sample GarageBand sounds into Koala?

  • SamuSamu

    @robklotzby said:
    What would be the easiest way to sample GarageBand sounds into Koala?

    Create a mixdown in GarageBand and use ‘Open In’ to send it to Koala...
    ...or go the lo-fi route, bump up the speaker volume, turn on background audio in both apps and sample the speaker output into Koala ;)

  • elf_audioelf_audio

    Or screen record garage band and import the video into koala

  • OscarSouthOscarSouth
    edited February 2021

    @elf_audio said:
    Or screen record garage band and import the video into koala

    Quality workflow! Koala always seems to cut to the core of exactly what you want to do. It’s not ‘theoretically possible’ — it’s logically accessible and really flows!

    Got to unlearn that iOS ‘workaround’ thinking mentality :D

Sign In or Register to comment.

© Vanilla Keystone Theme 2024