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.

AUM session: AKAI controlling GeoShred, tap the Geo UI, Geo become unresponsive

Dear all,

I never manage to spend an evening and actually achieve what I set out to!
-this eve, I wanted to try n map Expression (within GeoShred) so that it’s controlled by my AKAI MPK MKIII midi controller.

I didn’t get that far….

Basicallly, I have an AUM session which I load in, where the AKAI controls MIDI, and I want to proceed to map CCs..

But tapping a control element on the GeoShred UI (tap screen) causes the app to be unresponsive/slow, laggy. The AKAI no longer triggers a sound (although you can see the on-screen keyboard registering key presses).
I also notice the GeoCello preset text turn red, indicating a problem?

I have no idea why/what is going on. (Included a short video to show you)..

I’m basically stuck at the gates here. I have no choice but to completely reboot AUM. (Close app, launch again) to regain control of Geo), AUM will largely remain responsive as it should.

All I wanna do here is map my AKAI joystick!

-can anyone advise what’s going on here? 🙏🏻

https://youtu.be/qQpgjz6sAPw?si=q7uTOKU5ag0VYmuY


Problem#2: erratic slider when midi-mapped

I get strange behaviour when I try to map the joystick of the AKAI to control the Volume or Expression in GeoShred.

Basically, I bring up the Surface Control editor, hit MIDI learn (on Vol or Expr), move AKAI joystick (like you should). But when I return to the main UI of GeoShred, I notice the slider is jumping up and down erratically.

I thought maybe my controller was sending glitchy messages.. so I checked MidiWrench, moved the stick (in any and all directions), and it's reading in just fine within there.. so something is wrong within Geo or AUM I feel.

Can anybody advise?
🙏

https://youtu.be/OK0ZtLmPt5c?si=vQFQnPKoAry2RXwB

Comments

  • Can you post a screenshot of the AUM routing matrix?

  • Hi 👋🏻
    Shall do in the morning.
    Thanks 👍🏻

  • If I artificially route GeoShred to itself I get exactly the results you are experiencing in problem 2 @SkillipEvolver so I think @wim is right to suggest looking at the midi routing.

  • Hey y’all, thanks for chipping in with this.

    ‘I’m at work right now so haven’t got the whole midi kitted rigged up but AUM saves the midi routing session so here’s a screenshot:

    I’ve probably got more plugged in that necessary.. does any of this look like a problem?

  • Hi… you have an immediate loop with GS > Keyboard > GS
    If I map the above I get both of your issues.
    It needs to be just Keyboard > GS if indeed you need the keyboard.
    There may be other loops / issues but need to do something else 😊

  • Hmm. You should remove both the input connections to the AUM keyboard. Remove the connection from the AUM keyboard to MIDI Control. Remove the connection from AUM Destination to MIDI Control, unless you're running another app (not AUv3) that sends MIDI to "AUM". ADD a connection from MPK to GeoShred; that will let you play notes.

  • edited April 2

    Ah! thanks a lot for the input here folks!
    cleaning up the MIDI matrix sorted it out a treat 🙏

    I've got Expression mapped to the Y axis on the AKAI joystick now 👍

    it's quite effective, although it could do with tweaking a bit.

    Volume/Expression curve:
    -basically when the stick is neutral, there seems to be a deadzone(?)- if I push the stick vertically, it takes until about 10% travel (of that vertical tilt) before Expression gets triggered.
    In effect, the 'volume' makes a jump from near-silent to about 10% volume at that point.

    The more I continue to tilt, the Expression climbs gradually as you'd expect.
    But that first 10% or so, it's near-silent (the stick is ineffective).

    https://youtu.be/mGG3nmsfK9U?si=jfd3WWgdSqhCSYG6

  • Is there maybe a curve (exponential) on the Expression input?

  • edited April 3

    Hiya,

    Digging into Settings, I found Key Y Velocity, which has an editable curve.
    the default seems to have a certain shape to it which looks like the behaviour I’m hearing 👍🏻, however, I drew a custom curve and it seemed to take no effect.

    Although tbh I’m not entirely sure this is the correct item to tweak anyway?
    Because.. isn’t Velocity curve more to do with pressure sensitivity of the physical keys (of midi keyboard) ?
    **
    Anyway, while I was there I noticed something else I’d like to try and iron out if possible:**
    When transitioning from 1 key to the next on the keyboard, he volume is not reflective of the current position of the stick

    • to explain, let’s say the joystick is neutral and i hold a C note down, slide the stick up so that it’s full volume/expression,,
      And then i release C and hold the D note next to it,
      the volume is at the same level (ie no change 👍🏻).
      But let’s say I then move the stick back down towards neutral (what you’d expect to be low volume)….
      The volume output actually inverts itself. ie, as the stick descends back to neutral, the volume climbs from near silent, up to full volume!

    I can’t work out why this is happening.

    I’ve recorded a video to demonstrate what I mean:

    https://youtu.be/gQRtS1GSFBk?si=6FOC2jUnyAHei_qy

    https://youtube.com/shorts/gQRtS1GSFBk?si=TrxgYCQJ-4RIcROA

  • HI, I’m pretty sure that Key Y Velocity applies only to the GS touch interface.
    To see what the stick is doing I suggest switching the trace on in GS.
    You can do this by clicking on the three dots at the top right of GS, then Show Trace, Options, MIDI Channel Voice Messages, All, Back, Done
    If you move the stick you will see what messages GS is receiving.
    Don’t forget to switch tracing off when you have finished… just use None instead of All.

  • edited 6:12AM

    Thanks, yeah it seems to be receiving the correct messages

    i.e. 0,1,2,3,4,5 etc (up to 127) in the gradual way that it should 👍
    I also used MidiWrench to double-check.

    I replicated the steps I mentioned above, and kept it as light as possible with the filters I chose to log (toggles), so I (hope) the readout here includes the data I need.
    My brain is fried just now.

    Roughly:
    Hold a note > tilt stick upwards quickly to full extent (vol is now max)
    keep stick held > release note > hold next note up > slowly move stick from top back down to neutral > let go

    Here is the result:

    https://pastebin.com/wigfmCVD

    https://pastebin.com/wigfmCVD

  • edited 6:36AM

    ☝🏻 I'm not sure what's going wrong here, I'm trying to link to my trace log (Pastebin link)
    but the forum fails to parse it for whatever reason.

    I'm trying another site in my next post 👇🏻

Sign In or Register to comment.