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 StoreLoopy Pro is your all-in-one musical toolkit. Try it for free today.
Koala (auv3) reacting to different midi notes depending on window layout?
Hi there,
not shure if it's a bug or a feature or if I'm missing something...
when Koala displays a 4x4 sample grid, the first pad in bank A reacts to C3.
when I stretch the window so that Koala displays a 2x8 grid, the first pad reacts to G#2.
I find this confusing. Am I missing something or is this intended behavior?
cheers
p.s.: its not a host thing, I tested in AUM and LoopyPro with Drambo and KB-1 sending out midi
Comments
That’s a long term known Koala issue and I don’t really think it will be sorted out (since it’s been that way for ages and I’m certain the dev knows about it), I’ve resorted to using it in one layout per project.
ah, ok. thank you.
Perhaps you can make a mozaic or midi converter patch that will re~route the notes until it matches with reality. Or in KB1 when using pads you could make a preset that sends other notes out for any pad you want. Assuming It’s just for triggering. Not for chromatic playing.
Check to see if this happens with midi learned mapping. I vaguely recall (but might be misremembering) that if you midi learn the pads, the orientation doesn’t change the mapping.
When you say “the first pad in Bank A,” which pad do you mean? Top left or bottom left?
@mistercharlie : top left
@espiegel123 : THAT sounds interesting. I'll check.
Koala thinks of bottom left as the first pad.
Yes, this. I think the bottom left is always C1 (or whatever, depending on your settings). Even if the layout changes when you move from landscape to portrait, the hardware keys should still map to the same sounds. I think.
Raised this here, it’s a long standing issue that everyone has given up on.
https://forum.audiob.us/discussion/comment/1303479/#Comment_1303479
@elf_audio Never even bothered acknowledging nor responding. No support. Another absent developer who only drops in here to flog his wares.
We just have to live with two different mappings. One for portrait and one for landscape - it’s a bit of a joke.
And people wonder why iOS isn’t taken seriously.
That's my understanding too. The position of the pads changes, but the content of those pads follows, so the mapping stays the same if you're using the midi learn mapping.
I just did a very quick test with a custom mapping. It looks like what @espiegel123 said does the trick: just map a pad to a midi note of your choice and you‘re good.
What others said makes sense as well: when you start counting bottom left the pad that I thought is number one is actually 13 in portrait and 9 in landscape mode…(hope that makes sense).
Anyway, as always: thanks for your help, folks!
If you set up a midi mapping, you only need one. It only changes behavior when using automatic mapping.
As for "Never bothered acknowledging nor responding". This is is just another music forum. One can’t expect developers to keep up with every social media platform. I can't say I remember any "flogging" of wares, but I also can't say I'd mind that if they did.
Elf Audio is active on their official support platform, the Koala Discord channel, and has an official contact form on the website. I have gotten a timely response to every issue and bug report I’ve submitted there.
The default midi changing with pad layout thing is just something they've so far declined to change. It's cool if anyone feels better remaining outraged about that. I've offered the official contact routes are above if anyone would feel better expressing that more directly.
This dev is actually one of the good guys, considering ease of use and capability Koala is probably pound for pound the best iOS music app. Requests may be hard to implement or would change some foundational infrastructure. Koala also gets massive updates every now and then with more features for free, when I would have gladly paid. I really can’t ask more.
Well said @wim and @hghon . Koala is incredible. People are allowed to be upset about issues that affect them, but it doesn't change the fact that Koala is incredible and that the dev is actually quite responsive on certain channels.
AND as had been pointed out, there's a workaround to this midi issue that takes one time to set up. Make a custom midi map. Ideal? No. But immediate. 👍🏽
If I remember.
Different Midi channel cant be saved within a Koala projects for different midi channel saves/koala templates.
So you cant load a koala save. Then use multiple instance and it be different midi channels as to not trigger multple koala from a controller.
I think you could maybe host state save.
Mapping on different midi channels then host save but then have to have koala always in project template.
Because you would be mapping to koala and not using hosts per track switch functionalit. keyboard/pads or a controller.
I think.
What im saying is.
If using multi koala and want to launch a koala project save ( midi mapping ) at any time to any host project.
You cant save a different midi channel within a koala save.
It would also switch midi channel. When you go to set the midi channel ( of the next save ) Hence all saves would be the same midi channel.
So you cant map multi koala to pads.
edit.
You could save on same midi channel but different key/notes per koala ?
Good to point out though. If its how it works.
Were frustrating.
Midi mapping pads. Save in Koala.
Midi mapping another Koala. Changing midi channel though and it then altering the midi channel of the previous save.
I think that would be true for any plugin that has internal midi mapping. There could be some plugins that save midi mappings within a preset, though I can't think of any off the top of my head. So, I don't think what you're describing is a problem specific to Koala. Audio units just don't work that way.
They can be instantiated any number of times, but they don't have a mechanism to keep track of individual midi mappings per instance except through presets. I don't really think many people would like to have to re-map all their controllers per preset.
There are ways around such things in most hosts. There are apps such as mfxStrip that can alter the midi channel of messages passing through. AUM has its midi bus system that can help with such situations too.
Thats what I thought really.
No apps save different midi channels ( in own app presets )
Aha, my bad. Can't make a universal template for koala auv3 with remapped midi. Definitely unfortunate.
I don't understand. When you set up midi mapping it "sticks" so that the pads are mapped the same the next time you start a project doesn't it?
I don't know if it's any help to you, but you can map the pads on different banks with different midi channels. So, depending on the number of samples you use, you could accommodate four channels of midi in a single Koala instance.
Create a > @Tentype said:
You can set up an empty project as you want and use that as a starting point -- or if you are using it in a host, save your empty set-up template as a preset that you can call up as your default.