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.
Geoshred and hanging notes in loopy
I have been playing with geoshred inside loopy. Now that elastic OSC has mpe they form a great combo. (Geoshred is in au mpe mode). I am still using an iphone 6s for its touch force sensor.
Now Geoshred does sometimes loose the noteOff. The red button on the right side works for geoshred but it does not stop elastic osc.
When you go into the midi source in loopy you see all the hanging notes in geoSynth.
When you use the panic button in loopy for the geoshred instance it stops the sound but it does not release the keys.
My question @moForte is: can you make that red button send all notes off to all the connected synths. And can you find that bug that causes the missing noteOffs in the au mpe mode?
Comments
Can you make a screen recording demonstrating the situation happening? It should include playing before you start getting stuck notes.
Please reach out to us with a video so that we can try to reproduce the problem and fix it.
Note that if Elastic OSC is not responding to the red panic button, that likely means that it did not implement the MIDI controller messages for Panic. All notes off, all controllers off, all sound off. It's very common for synth creators to only implement a small subset of the MIDI spec, ignoring the panic messages, the pitch-bend range messages, other important messages. There is a brute force solution for synths that don't properly implement the panic messages. If you look at the MIDI configuration that you're using, It's possible to get the panic button to send note-offs for all 127 notes, all 16 channels. It's really more like a sledgehammer, but if the target synth doesn't implement the basic MIDI panic messages, that may be all that you can do. The switch to do this is called "Force All noteOffs on panic". It may swamp the target synth because its lots of messages.
This is described in the reference manual under "Menu> Help> MIDI" and also online here:
https://www.moforte.com/geoShredAssets7000/help/midi.html
Force all noteOffs on panic - Off by default. Send note offs on all MIDI channels (1-16 )for all keys (1-128) Only enable this if a synthesizer your are controlling is having problems with stuck notes.
I am not super familiar with Loopy Pro. It would be great if you could have the video show the setup so I can reproduce exactly the steps. You can reach us at [email protected].
@moForte elastic osc reacts to the panic button inside loopy pro. To get to the panic button in loopy open the plugin and then tap the cog wheel next to the plugin name.
I tried many other synths that are renomated like korg m1 and swam variflute. All do not receive any panic midi from the little red button in Geoshred.
I have a seabord block. Only recently it has been updated, the firmware. There was a bug that caused hanging notes...
Now in loopy when you connect your midi source to your synth when youtap on the geoSynth midi source you see a keyboard where you can adjust the playing range. Great feature that you see the active notes.
I will see how I get along with screen recording.
Ah cool midi engeneering, the send cc123 on 0 voices. My korg prophecy does that
How do I get to that mpe channel mode screen?
Send CC 123 on zero voices - Off by default. Send CC 123, All Notes Off, when no voices are left running. This is CYA for synths that don't properly handle noteOffs. Usually caused by incorrect Legato handleing. Use with caution.
As I said earlier it's a wild world out there. I'd say that about 1/2 the synths I have evaluated don't implement the minimium MIDI Spec, or implement it incorrectly.
The image I posted earlier is from the "MPE Channel Mode" MIDI Configuration. MIDI Configurations are found under "Menu> MIDI".
Note that some presets are linked to a specific MIDI configuration so don't assume if you edit the currently selected MIDI configuration that it's the active one. Look at the Presets in the Setlist (bank) "MIDI Out". They are bound to a specific MIDI configuration. The binding is set in :
"Menu> Performance Settings> Control> Preset's MIDI Configuration"
If there is no binding in the current Preset, then the MIDI Configuration selected under "Menu> MIDI" will be the current configuration.
All of the MIDI Configuration parameters are explained in the reference manual under "Menu> Help> MIDI" or online here:
https://www.moforte.com/geoShredAssets7000/help/midi.html
Finally the GeoShred video "User Manual" and all the "Application Notes" are found under "Menu> Help> Video Manual ... " or here online:
And don't forget the FAQ under "Menu> Help> FAQs" or online here:
https://www.moforte.com/geoShredAssets7000/help/FAQs/index.html
The Prophecy has such a great arpegiator that I would send it to some other synths . After some realy fast sequences there were bound to be some stuck notes. This midi trick makes it possible to play without bother.
Elastic OSC also has a great arpegiator, such that I am wishing for a midi output. Maybe this trick can also cover their ass.
Now the great news I was able to reproduce the missing noteoff bug.
It seems to be specific to the au mpe keyboard mode. (Was using theGeoTrumpets and GeoTenors).
When you play a note and then bend it, then play another note and then release the first note it gets stuck.
I guess with not resetting the pitchbend on release the noteoff got lost...
Now after some more testing it seems specific to the older iPhone 6s.
On my iPad air with m2 it works like it should.
Are you running the same version of GeoShred on both devices?
Yes running the latest version on all.
It does not make sense that this problem would be just with the iPhone 6. It'd be great to know what version of iOS you're running on the phone. And certainly since iOS 13, Apple's fixed a lot of bugs with Core MIDI that might be contributing to this.
Can you make me a video so that I can see what's going on? Send a link to the video to [email protected]