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.

How do I trigger Koala pads via another MIDI app? FIXED

[Deleted User][Deleted User]
edited April 2023 in General App Discussion

I’m trying to trigger individual Koala sample pads via MIDI sequencer apps in AUM, but having no success.

I’ve tried Stepopolyarp, Brambos’s, Riffer, Atom etc. but all they do is to trigger a single pad. I’ve tried every setting under the sun, MIDI mapped the pads to Atom for example, and followed a few threads on here, but nothing works….just a single pad being triggered.

The weird thing is, one of my Koala songs triggers correctly and works as I want it to, but none of the others do - despite all the settings being identical!!

This seems so much more difficult than it should be.

Any help gladly received, maybe an idiots guide to getting say Riffer to trigger pads most welcome.

Cheers!

Comments

  • [Deleted User][Deleted User]

    Update - sorry, after over an hour of trial and error I got it working about 30 seconds after posting this!

    For future reference, in Settings > MIDI, I just switched everything off and it worked automatically. I’m 100% certain I tried this several times before and it didn’t work, but working now!

  • espiegel123espiegel123

    @monz0id said:
    I’m trying to trigger individual Koala sample pads via MIDI sequencer apps in AUM, but having no success.

    I’ve tried Stepopolyarp, Brambos’s, Riffer, Atom etc. but all they do is to trigger a single pad. I’ve tried every setting under the sun, MIDI mapped the pads to Atom for example, and followed a few threads on here, but nothing works….just a single pad being triggered.

    The weird thing is, one of my Koala songs triggers correctly and works as I want it to, but none of the others do - despite all the settings being identical!!

    This seems so much more difficult than it should be.

    Any help gladly received, maybe an idiots guide to getting say Riffer to trigger pads most welcome.

    Cheers!

    Are you sure that you are sending the right notes and on the right channel?

    check with a midi monitor to see the note numbers being sent. koala may use different octave numbering from your sequencer.

  • wimwim
    edited April 2023

    Make sure the keyboard / grid isn’t opened in the sequence view.

  • [Deleted User][Deleted User]

    @espiegel123 @wim thanks for the replies!

    @espiegel123 said:
    Are you sure that you are sending the right notes and on the right channel?

    check with a midi monitor to see the note numbers being sent. koala may use different octave numbering from your sequencer.

    Yeah they were fine, I even mapped each pad to corresponding notes in Atom, but:

    @wim said:
    Make sure the keyboard / grid isn’t opened in the sequence view.

    Flipping heck, I reckon that's the culprit! Bingo! That explains why songs weren't triggering pads correctly even though the MIDI settings off. Didn't think to check the keyboard...cheers Wim - I've written that down for future reference!

  • wimwim

    That one catches a lot of people out.

  • [Deleted User][Deleted User]

    @wim said:
    That one catches a lot of people out.

    Fooled me!

    Handy to know actually, as I’m using Koala more these days, in that setting I can use it as a default single sample player.

  • musikeermusikeer

    Still a problem with Koala not recalling chosen pads when using as AUv3 in Cubasis…

  • espiegel123espiegel123

    @musikeer said:
    Still a problem with Koala not recalling chosen pads when using as AUv3 in Cubasis…

    Can you describe the problem in more detail?

    Are you sure everything is set up correctly?

  • GdubGdub

    I have Xequence mapped to koala all pads on page A in AUM
    When I open my project it seems to activate some pads on koala page B
    I have to open up koala and then start stop the project, then it all starts correctly
    Strange but caught me out at 1st
    But as long as I remember to open koala av3 in AUM my project works

  • musikeermusikeer

    When using Koala as an AUv3 in Cubasis, accessing a particular pad, (in this case a drum sample), triggering it as MIDI, saving the project, randomly the project will open with the incorrect pad/note triggered. The fix is to select/open Koala, within Cubasis and close it with no changes, within Cubasis. The correct note is then triggered. This is using a Koala "song" (I'd refer to it as a "project", or something other than "song"), with four banks of individual wav samples.

    This is without setting any MIDI mapping in Koala, just triggering/tapping a chosen pad/sample. I've MIDI mapped a sample to a specific keyboard key in the past, I believe the same incorrect sample at times still plays. I'd prefer not to have to MIDI map, just open Koala and choose a pad and record it by tapping it.

    I believe it's set up correctly, have been using it for quite awhile, unless there's a more solid approach. And have read about the same situation from other users. Seems to be a known issue. Perhaps I'm hijacking this thread, there may be an exclusive one for this situation.

  • musikeermusikeer

    @Gdub said:
    I have Xequence mapped to koala all pads on page A in AUM
    When I open my project it seems to activate some pads on koala page B
    I have to open up koala and then start stop the project, then it all starts correctly
    Strange but caught me out at 1st
    But as long as I remember to open koala av3 in AUM my project works

    Exactly this.

  • espiegel123espiegel123

    @musikeer said:
    When using Koala as an AUv3 in Cubasis, accessing a particular pad, (in this case a drum sample), triggering it as MIDI, saving the project, randomly the project will open with the incorrect pad/note triggered. The fix is to select/open Koala, within Cubasis and close it with no changes, within Cubasis. The correct note is then triggered. This is using a Koala "song" (I'd refer to it as a "project", or something other than "song"), with four banks of individual wav samples.

    This is without setting any MIDI mapping in Koala, just triggering/tapping a chosen pad/sample. I've MIDI mapped a sample to a specific keyboard key in the past, I believe the same incorrect sample at times still plays. I'd prefer not to have to MIDI map, just open Koala and choose a pad and record it by tapping it.

    I believe it's set up correctly, have been using it for quite awhile, unless there's a more solid approach. And have read about the same situation from other users. Seems to be a known issue. Perhaps I'm hijacking this thread, there may be an exclusive one for this situation.

    If you haven't done so, you might want to make a video demonstrating the entire sequence of events, posting unlisted to YouTube and sending a link to Marek ( @elf_audio ). It might make it easier for him to track down and address.

  • attakkattakk

    @musikeer said:
    When using Koala as an AUv3 in Cubasis, accessing a particular pad, (in this case a drum sample), triggering it as MIDI, saving the project, randomly the project will open with the incorrect pad/note triggered. The fix is to select/open Koala, within Cubasis and close it with no changes, within Cubasis. The correct note is then triggered. This is using a Koala "song" (I'd refer to it as a "project", or something other than "song"), with four banks of individual wav samples.

    This is without setting any MIDI mapping in Koala, just triggering/tapping a chosen pad/sample.

    The same happens for me in NS2.

  • KashiKashi

    Dumb question alert! : how do I know which notes in Polybud will trigger which sample, in Koala?

  • musikeermusikeer

    @musikeer said:
    When using Koala as an AUv3 in Cubasis, accessing a particular pad, (in this case a drum sample), triggering it as MIDI, saving the project, randomly the project will open with the incorrect pad/note triggered. The fix is to select/open Koala, within Cubasis and close it with no changes, within Cubasis. The correct note is then triggered. This is using a Koala "song" (I'd refer to it as a "project", or something other than "song"), with four banks of individual wav samples.

    This is without setting any MIDI mapping in Koala, just triggering/tapping a chosen pad/sample. I've MIDI mapped a sample to a specific keyboard key in the past, I believe the same incorrect sample at times still plays. I'd prefer not to have to MIDI map, just open Koala and choose a pad and record it by tapping it.

    I think this may be an instance of operator error. When checking the Koala MIDI settings, “Use MIDI Mapping” was selected, when no mapping was desired, just accessing/recording the pads/samples. Seems all OK now, I’ll keep an eye (ear) on it, and espiegel123 was on to something when suggesting things may have been set incorrectly. Sorry for the hubbub.

Sign In or Register to comment.

© Vanilla Keystone Theme 2024