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 Sampler update!

12357

Comments

  • db909db909

    @Nasatyuana said:
    AAAAh that makes sense, thanks very much! I am partly embarassed for not spotting this, and excited to try it! Love this forum!

    Those are export stems. I thought you wanted the split stems feature which is not that

  • NasatyuanaNasatyuana

    @espiegel123 said:

    @Nasatyuana said:
    I cannot unlock the stems, using an up to date version of Koala, samurai version. I go into the 'extras' tab, hold the button down and nothing, this is the same on both my ipad and iphone. Has this been removed? Thanks all.


    Sorry, is this the way to split an pre existing audio file into individual stems? Just to be sure?
    Thanks.

  • db909db909

    @Nasatyuana no. Read the info I have posted for you

  • NasatyuanaNasatyuana

    @db909 said:
    @Nasatyuana no. Read the info I have posted for you

    Think we posted at the same time. That's why I missed.

  • sigma79sigma79

    @espiegel123 said:

    @sigma79 said:
    Dont really need to midi map apart from trigger pads via launchpad but not map in Koala. Just use external octave.

    The first pad is a number of keys away from all other keys.

    Its been like this for a while.

    I guess nobody triggers koala via midi to notice.

    I could map in Koala but can remember what midi it listens to.

    My mapping area is just in octaves like a keyboard. So not sure why any button triggers the same pad.

    Hence just using external octave

    but the first pad isnt anywhere near the rest of the octave which triggers the other pads.

    The default midi setting in Koala is that the pads — in portrait orientation - are triggered by consecutive midi notes. With the lower-left pad as the first. The lower-left pad’s note is the note displayed as the offset.

    Thanks.

    The first pad is say q on keyboard. Then consecutive notes u,i,o etc.

    The offset moves the 2nd note and notes.

    The first note is still about 12 keys away.

  • sigma79sigma79

  • espiegel123espiegel123

    @sigma79 said:

    @espiegel123 said:

    @sigma79 said:
    Dont really need to midi map apart from trigger pads via launchpad but not map in Koala. Just use external octave.

    The first pad is a number of keys away from all other keys.

    Its been like this for a while.

    I guess nobody triggers koala via midi to notice.

    I could map in Koala but can remember what midi it listens to.

    My mapping area is just in octaves like a keyboard. So not sure why any button triggers the same pad.

    Hence just using external octave

    but the first pad isnt anywhere near the rest of the octave which triggers the other pads.

    The default midi setting in Koala is that the pads — in portrait orientation - are triggered by consecutive midi notes. With the lower-left pad as the first. The lower-left pad’s note is the note displayed as the offset.

    Thanks.

    The first pad is say q on keyboard. Then consecutive notes u,i,o etc.

    The offset moves the 2nd note and notes.

    The first note is still about 12 keys away.

    As I said the arrangement I describe is based on portrait orientation. When you switch to landscape you have to adjust accordingly.

  • sigma79sigma79

    @espiegel123 said:

    @sigma79 said:

    @espiegel123 said:

    @sigma79 said:
    Dont really need to midi map apart from trigger pads via launchpad but not map in Koala. Just use external octave.

    The first pad is a number of keys away from all other keys.

    Its been like this for a while.

    I guess nobody triggers koala via midi to notice.

    I could map in Koala but can remember what midi it listens to.

    My mapping area is just in octaves like a keyboard. So not sure why any button triggers the same pad.

    Hence just using external octave

    but the first pad isnt anywhere near the rest of the octave which triggers the other pads.

    The default midi setting in Koala is that the pads — in portrait orientation - are triggered by consecutive midi notes. With the lower-left pad as the first. The lower-left pad’s note is the note displayed as the offset.

    Thanks.

    The first pad is say q on keyboard. Then consecutive notes u,i,o etc.

    The offset moves the 2nd note and notes.

    The first note is still about 12 keys away.

    As I said the arrangement I describe is based on portrait orientation. When you switch to landscape you have to adjust accordingly.

    Cheers.

    How to adjust?

    I can just not map.

    It isnt really an essential mapping.

  • sigma79sigma79
    edited March 2023

    Ah maybe offfest the 2nd note to match the first note.

    Na.

    It moves the first note also. Some octaves away still.

    Sure I can map via koala, whilst in Drambo.

    But doubt I will bother.

    Remember mapping via Drambo it were hassle before and it were hassle now.

  • espiegel123espiegel123

    @sigma79 said:

    @espiegel123 said:

    @sigma79 said:

    @espiegel123 said:

    @sigma79 said:
    Dont really need to midi map apart from trigger pads via launchpad but not map in Koala. Just use external octave.

    The first pad is a number of keys away from all other keys.

    Its been like this for a while.

    I guess nobody triggers koala via midi to notice.

    I could map in Koala but can remember what midi it listens to.

    My mapping area is just in octaves like a keyboard. So not sure why any button triggers the same pad.

    Hence just using external octave

    but the first pad isnt anywhere near the rest of the octave which triggers the other pads.

    The default midi setting in Koala is that the pads — in portrait orientation - are triggered by consecutive midi notes. With the lower-left pad as the first. The lower-left pad’s note is the note displayed as the offset.

    Thanks.

    The first pad is say q on keyboard. Then consecutive notes u,i,o etc.

    The offset moves the 2nd note and notes.

    The first note is still about 12 keys away.

    As I said the arrangement I describe is based on portrait orientation. When you switch to landscape you have to adjust accordingly.

    Cheers.

    How to adjust?

    I can just not map.

    It isnt really an essential mapping.

    Change the window size so that you have 4 rows. The bottom left pad is triggered by the MIDI offset indicated in settings. Remember that your host may use different octave number.

    The midi note is the note for the bottom left pad when there is a 4 row arrangment. The notes to the right are consecutive.

    Lets say the lower left is note 36. The bottom row is 36, 37,38,39. The next row up is 40, 41,42,43, etc

    If you change the size so that you have two rows of 8, the pads are triggered by the same notes. So, pay attention to where the pads moved when you changed the size.

  • sigma79sigma79
    edited March 2023

    @espiegel123 said:

    @sigma79 said:

    @espiegel123 said:

    @sigma79 said:

    @espiegel123 said:

    @sigma79 said:
    Dont really need to midi map apart from trigger pads via launchpad but not map in Koala. Just use external octave.

    The first pad is a number of keys away from all other keys.

    Its been like this for a while.

    I guess nobody triggers koala via midi to notice.

    I could map in Koala but can remember what midi it listens to.

    My mapping area is just in octaves like a keyboard. So not sure why any button triggers the same pad.

    Hence just using external octave

    but the first pad isnt anywhere near the rest of the octave which triggers the other pads.

    The default midi setting in Koala is that the pads — in portrait orientation - are triggered by consecutive midi notes. With the lower-left pad as the first. The lower-left pad’s note is the note displayed as the offset.

    Thanks.

    The first pad is say q on keyboard. Then consecutive notes u,i,o etc.

    The offset moves the 2nd note and notes.

    The first note is still about 12 keys away.

    As I said the arrangement I describe is based on portrait orientation. When you switch to landscape you have to adjust accordingly.

    Cheers.

    How to adjust?

    I can just not map.

    It isnt really an essential mapping.

    Change the window size so that you have 4 rows. The bottom left pad is triggered by the MIDI offset indicated in settings. Remember that your host may use different octave number.

    The midi note is the note for the bottom left pad when there is a 4 row arrangment. The notes to the right are consecutive.

    Lets say the lower left is note 36. The bottom row is 36, 37,38,39. The next row up is 40, 41,42,43, etc

    If you change the size so that you have two rows of 8, the pads are triggered by the same notes. So, pay attention to where the pads moved when you changed the size.

    Potrait works as a consecutive octave ( so ok )

    I just wont map as some apps need to be visible to sample and need landscape.

    Or try mapping via Koala

    Cheers though.

    I can just resize to potrait. When I need midi.

    It would be same grid as controller setup anyway.

  • espiegel123espiegel123

    @sigma79 said:

    @espiegel123 said:

    @sigma79 said:

    @espiegel123 said:

    @sigma79 said:

    @espiegel123 said:

    @sigma79 said:
    Dont really need to midi map apart from trigger pads via launchpad but not map in Koala. Just use external octave.

    The first pad is a number of keys away from all other keys.

    Its been like this for a while.

    I guess nobody triggers koala via midi to notice.

    I could map in Koala but can remember what midi it listens to.

    My mapping area is just in octaves like a keyboard. So not sure why any button triggers the same pad.

    Hence just using external octave

    but the first pad isnt anywhere near the rest of the octave which triggers the other pads.

    The default midi setting in Koala is that the pads — in portrait orientation - are triggered by consecutive midi notes. With the lower-left pad as the first. The lower-left pad’s note is the note displayed as the offset.

    Thanks.

    The first pad is say q on keyboard. Then consecutive notes u,i,o etc.

    The offset moves the 2nd note and notes.

    The first note is still about 12 keys away.

    As I said the arrangement I describe is based on portrait orientation. When you switch to landscape you have to adjust accordingly.

    Cheers.

    How to adjust?

    I can just not map.

    It isnt really an essential mapping.

    Change the window size so that you have 4 rows. The bottom left pad is triggered by the MIDI offset indicated in settings. Remember that your host may use different octave number.

    The midi note is the note for the bottom left pad when there is a 4 row arrangment. The notes to the right are consecutive.

    Lets say the lower left is note 36. The bottom row is 36, 37,38,39. The next row up is 40, 41,42,43, etc

    If you change the size so that you have two rows of 8, the pads are triggered by the same notes. So, pay attention to where the pads moved when you changed the size.

    Potrait works as a consecutive octave ( so ok )

    I just wont map as some apps need to be visible to sample and need landscape.

    Or try mapping via Koala

    Cheers though.

    I can just resize to potrait. When I need midi.

    It would be same grid as controller setup anyway.

    The midi mapping doesn't change when you change the orientation. The same sounds are triggered by the same midi no matter what. It is just harder to visualize the order when you change the orientation.

  • sigma79sigma79

    @espiegel123 said:

    @sigma79 said:

    @espiegel123 said:

    @sigma79 said:

    @espiegel123 said:

    @sigma79 said:

    @espiegel123 said:

    @sigma79 said:
    Dont really need to midi map apart from trigger pads via launchpad but not map in Koala. Just use external octave.

    The first pad is a number of keys away from all other keys.

    Its been like this for a while.

    I guess nobody triggers koala via midi to notice.

    I could map in Koala but can remember what midi it listens to.

    My mapping area is just in octaves like a keyboard. So not sure why any button triggers the same pad.

    Hence just using external octave

    but the first pad isnt anywhere near the rest of the octave which triggers the other pads.

    The default midi setting in Koala is that the pads — in portrait orientation - are triggered by consecutive midi notes. With the lower-left pad as the first. The lower-left pad’s note is the note displayed as the offset.

    Thanks.

    The first pad is say q on keyboard. Then consecutive notes u,i,o etc.

    The offset moves the 2nd note and notes.

    The first note is still about 12 keys away.

    As I said the arrangement I describe is based on portrait orientation. When you switch to landscape you have to adjust accordingly.

    Cheers.

    How to adjust?

    I can just not map.

    It isnt really an essential mapping.

    Change the window size so that you have 4 rows. The bottom left pad is triggered by the MIDI offset indicated in settings. Remember that your host may use different octave number.

    The midi note is the note for the bottom left pad when there is a 4 row arrangment. The notes to the right are consecutive.

    Lets say the lower left is note 36. The bottom row is 36, 37,38,39. The next row up is 40, 41,42,43, etc

    If you change the size so that you have two rows of 8, the pads are triggered by the same notes. So, pay attention to where the pads moved when you changed the size.

    Potrait works as a consecutive octave ( so ok )

    I just wont map as some apps need to be visible to sample and need landscape.

    Or try mapping via Koala

    Cheers though.

    I can just resize to potrait. When I need midi.

    It would be same grid as controller setup anyway.

    The midi mapping doesn't change when you change the orientation. The same sounds are triggered by the same midi no matter what. It is just harder to visualize the order when you change the orientation.

    Mapped via koala.

    I got screen keyboard midi.

    Controllers midi.

    Global init folder.

    Init host template.

    Track saves folders.

  • solncekreezesolncekreeze
    edited March 2023

    Can you tell me why aum recordings are not imported into Koala via Audioshare? Other samples are loaded but there are no Aum records.

  • sigma79sigma79

    Can you sample with gain/vol full?

    Or do you add gain after sample?

    Need to sample scratches. So need the volume gain to be true.

  • solncekreezesolncekreeze

    @sigma79 said:
    Can you sample with gain/vol full?

    Or do you add gain after sample?

    Need to sample scratches. So need the volume gain to be true.

    What does it mean - “with gain/vol full"? They just don't load.

  • espiegel123espiegel123

    @solncekreeze said:
    Can you tell me why aum recordings are not imported into Koala via Audioshare? Other samples are loaded but there are no Aum records.

    Can you explain more about what you mean and/or show screenshots of your process? I have no trouble importing AUM recordings into Koala.

  • sigma79sigma79
    edited March 2023

    @solncekreeze said:

    @sigma79 said:
    Can you sample with gain/vol full?

    Or do you add gain after sample?

    Need to sample scratches. So need the volume gain to be true.

    What does it mean - “with gain/vol full"? They just don't load.

    Monitoring whilst recording.

    It dials back volume?

    Which you add after sampled?

    Need to check app but seems like as described.

  • solncekreezesolncekreeze

    @espiegel123 said:

    @solncekreeze said:
    Can you tell me why aum recordings are not imported into Koala via Audioshare? Other samples are loaded but there are no Aum records.

    Can you explain more about what you mean and/or show screenshots of your process? I have no trouble importing AUM recordings into Koala.



    It is difficult to demonstrate this with screenshots. But I'm not the only one with such a problem. A friend wrote to me and said that he wanted to use Audioshare for this, but it didn't work out. Asked to check. And indeed the Aum records are not corrupted. I contacted the workers-they said that everything was fine. But the import with AS disabled works fine. I tried to convert files. Nothing changes. It doesn't work on i-hone or ipad. The latest versions of the system and applications are installed.

  • espiegel123espiegel123

    @solncekreeze said:

    @espiegel123 said:

    @solncekreeze said:
    Can you tell me why aum recordings are not imported into Koala via Audioshare? Other samples are loaded but there are no Aum records.

    Can you explain more about what you mean and/or show screenshots of your process? I have no trouble importing AUM recordings into Koala.



    It is difficult to demonstrate this with screenshots. But I'm not the only one with such a problem. A friend wrote to me and said that he wanted to use Audioshare for this, but it didn't work out. Asked to check. And indeed the Aum records are not corrupted. I contacted the workers-they said that everything was fine. But the import with AS disabled works fine. I tried to convert files. Nothing changes. It doesn't work on i-hone or ipad. The latest versions of the system and applications are installed.

    I recommend turning off Enable Audioshare. All of the files in Audioshare including the AUM recordings are available to you even with it off.

    If you haven't reported the issue to @elf_audio , I recommend doing so also.

  • espiegel123espiegel123

    @sigma79 said:

    @solncekreeze said:

    @sigma79 said:
    Can you sample with gain/vol full?

    Or do you add gain after sample?

    Need to sample scratches. So need the volume gain to be true.

    What does it mean - “with gain/vol full"? They just don't load.

    Monitoring whilst recording.

    It dials back volume?

    Which you add after sampled?

    Need to check app but seems like as described.

    I just did a quick test, it looks like Koala applies 3.7 db of gain reduction to the input.

  • solncekreezesolncekreeze

    @sigma79 said:

    @solncekreeze said:

    @sigma79 said:
    Can you sample with gain/vol full?

    Or do you add gain after sample?

    Need to sample scratches. So need the volume gain to be true.

    What does it mean - “with gain/vol full"? They just don't load.

    Monitoring whilst recording.

    It dials back volume?

    Which you add after sampled?

    Need to check app but seems like as described.

    I just record with instruments and that's it. When recording the microphone, I turn down the sound or connect our headphones;) I don't do anything with the file.

  • solncekreezesolncekreeze

    @espiegel123 said:

    @sigma79 said:

    @solncekreeze said:

    @sigma79 said:
    Can you sample with gain/vol full?

    Or do you add gain after sample?

    Need to sample scratches. So need the volume gain to be true.

    What does it mean - “with gain/vol full"? They just don't load.

    Monitoring whilst recording.

    It dials back volume?

    Which you add after sampled?

    Need to check app but seems like as described.

    I just did a quick test, it looks like Koala applies 3.7 db of gain reduction to the input.

    Just the import works. But I am interested in the question precisely for the reason that AS is enabled. I informed the developer.

  • espiegel123espiegel123

    @solncekreeze : FWIW, i just tried and can import AUM recordings when enable audioshare is selected. I was able to import 16 and 24 bit audio at 44.1 and 48 kHz. I am running ios 16.2 on an iPad 6.

    The whole audioshare import thing is outdated. Audioshare implemented this at a time when iOS had nothing like Files app and so it was a workaround for an OS limitation that is long gone.

    Does import from AUM recordings work if you turn off enable audioshare?

  • solncekreezesolncekreeze

    @espiegel123 said:
    @solncekreeze : FWIW, i just tried and can import AUM recordings when enable audioshare is selected. I was able to import 16 and 24 bit audio at 44.1 and 48 kHz. I am running ios 16.2 on an iPad 6.

    The whole audioshare import thing is outdated. Audioshare implemented this at a time when iOS had nothing like Files app and so it was a workaround for an OS limitation that is long gone.

    Does import from AUM recordings work if you turn off enable audioshare?

    With AS disabled, everything works. I understand that you can do all this through files. But if the import function is declared via AS, then it should work. Otherwise it is misleading. I have ipad pro 2021, se3 and ipad9 devices. And it doesn't work anywhere on the latest systems. I did the conversion and it doesn't do anything.

  • sigma79sigma79

    Whats the deal with disk streaming samples vs not?

    Can you use samplers ( ideally Koala )

    Within a DAW and song which uses resources. With loads of triggered samples and multi koalas?

  • sigma79sigma79

    Can anyone say if triggering 64-128 samples in koalas plus synths, would consume ram.

    More than a synth instead of koalas?

  • wimwim

    @sigma79 said:
    Whats the deal with disk streaming samples vs not?

    Can you use samplers ( ideally Koala )

    Within a DAW and song which uses resources. With loads of triggered samples and multi koalas?

    Koala doesn't do disk streaming. Everything is in RAM. Managing the size of samples in use at one time is important. RAM usage for individual instances do add up.

  • wimwim
    edited May 2023

    @sigma79 said:
    Can anyone say if triggering 64-128 samples in koalas plus synths, would consume ram.

    Of course it would. How many samples you can get away depends on the size of them and the resource requirements of the synths.

    More than a synth instead of koalas?

    That question is too ambiguous to answer. It depends on the samples and the synths. Every synth has different resource requirements. Some will be light on RAM but bring a device to its knees for other reasons.

    There's no way to determine how much ram and other resources will be consumed by apps on iOS. iOS doesn't have the tools. The only way to estimate is to experiment by loading things up until you have problems.

  • sigma79sigma79

    @wim said:

    @sigma79 said:
    Whats the deal with disk streaming samples vs not?

    Can you use samplers ( ideally Koala )

    Within a DAW and song which uses resources. With loads of triggered samples and multi koalas?

    Koala doesn't do disk streaming. Everything is in RAM. Managing the size of samples in use at one time is important. RAM usage for individual instances do add up.

    Cool.

    Cheers wim.

Sign In or Register to comment.

© Vanilla Keystone Theme 2024