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.
Midi remapping
My controller keyboard uses note on velocity 0 instead of note off to stop notes.
I think this is clogging up my midi channels and creating hung notes.
What midi app would you recommend to remap midi note on velocity 0 to note off ?
Here's the screenshot of midi wrench to show the midi note information.
Comments
There is something strange in the midi monitor, all your notes are doubled . Maybe checking a midi feedback loop first ? (Hardware set to thru and somehow you accidentally send the notes back to the controller?)
@Korakios
I didn't notice that.
Here's another screen shot with the current setup.
My keyboard is a M-Audio Keystation 49e So no midi thru
The usb interface is a generic model,
wired to midi in midi out,
the midi thru is not being used.
BM3 is running in AUM.
Midimttr is providing the midi out to the usb interface to my microKorg
Ah tested it, found the reason for the double notes.
The Midimttr routing was set to send midi information
to both the usb out and midi wrench.
Corrected for that
Here's a screen shot now without the double note routing
Midimttr is sending midi notes directly to the usb interface
Streambyter, MIDI Fire and Mozaic can all be used to convert the messages if you want to do that. FWIW, it is a pretty common thing for controllers to use velocity 0 instead of note off.
@espiegel123
I realised that when I was doing some research into Bluetooth midi between iOS devices.
Thanks for the pointers.
All I need is that function, I'll have a look at all three.
I've had a look at midifire and most probably I'll go for that one.
Before buying, check with an iOS virtual keyboard if the microkorg is working properly
@Korakios
Definitely checked that.
It's a solid little workhorse.
The keystation only sends midi out
The microKorg is set to receive only
Local Control is switched off
It's also set to receive external midi clock
which I'm not transmitting at the moment
as can be seen by the screen shot.
@Korakios
The hung notes happen via both Bluetooth and the usb interface
hence why I took the microKorg out of the equation.
Then I tested Bluetooth, discovered the latency problem,
went down that rabbit hole, resurfaced and went looking
to see if it could be the Keystation.
That's when I ran some research and found that it was
in common usage to use midi note velocity 0 rather than note off
and for some reason desktop D.A.W's have no problem with it.
I've had both keyboards for quite awhile now and physical midi instruments
tend not to have problems except for when the cmos battery goes and
they lose memory, I still have a Casio CZ1000 which still works to this day.
I ran midi wrench and saw that my Keystation also did send
midi note velocity 0 which had plagued another Keystation user
who managed to fix the problem by remapping the midi note
information hence my request.
He did that on a desktop which is easy enough.
On iOS it's not so obvious.
I've already had a look at midifire but I also
needed to see if there were any alternatives.
Thanks dude.
If you have patience I could try on the weekend to make a patch in PureData and load it via MobMuPlat app.
@Korakios
I definitely have the patient.
That would be awesome.
My next question was going to be what is MobMuPlatt then I had a look.
That would be mega dude.
Thank you.
FWIW, here is the StreamByter/MIDIFire code that converts velocity 0 note on events into note off events
9X X2 00 = 8X X2
In the process of testing this, I noticed that velocity 0 as note off is pretty common. AUM's keyboard uses it as does Velocity Keyboard
So, velocity 0 notes might be not be the cause of the stuck notes.
Note ON at zero velocity and Note OFF are technically both admissible per the MIDI specification. But of course can be confusing, and if a synth is poorly coded could cause those issues. But not with most. I agree with @espiegel123 that it may not be the cause of the stuck notes.
StreamByter as @espiegel123 says is the most streamlined “one line of code” answer.
Mozaic automatically coverts zero velocity Note ON to Note OFF messages. But blocks midi through unless allowed, so it takes three lines of code rather than one.
I've been experiencing hung notes for almost
all of the synth apps and my external synth.
This has mainly been with Auria Pro which
I've stopped using for the interim as I've had
a second project go bad on me.
A crash reload loop.
Not really cool.
Waiting for a reply at the moment to see
if the project file can be rescued but as
I haven't heard from them as yet
I wanted to eliminate any other variables.
I've been using both keyboards and countless synths
on desktops even on Atari with not a hung note in sight
so this for me is new territory and before I say ,
'well it was this app or that app', I need to make
sure I know what are the errors that I'm making.
Okay, talking abut setups.
What I'm going to do over the next few days is to take my usb hub out of the equation.
I'm using a Behringer usb mixer to get audio into the iPad
and using both Bluetooth for midi to my iPhone or the generic usb midi interface
to my external midi modules etc.
The usb interface and the mixer both go through a usb hub to the iPad using
a Lightning to USB3 adapter.
So I'm going to take both the usb hub and the audio interface out
and plug the usb midi interface directly and use the headphone out
of the iPad to monitor audio.
If I don't experience any hung notes that way then it means that
I may need to get an audio interface with both audio and midi.
Thanks for your assistance so far guys.
Okay for me to have both the Keystation
and the external midi to be happening I need
the usb hub to be connected.
Though virtual keyboards are fun,
I need to feel the keyboards beneath my fingers.
Also this maybe of interest.
I disconnected the audio interface
(same DAC as the Behringer UCA202 and UCA 222 by the way)
plugged in the usb interface directly to the
Lightning connector adapter and the audio out via the inbuilt headphones.
Increased crackles and clicks when switching between apps
and whilst I'm typing with the track running in the background which
wasn't there before so I'm going to connect the audio interface again
as it's not useable.
The fix that @Korakios is doing I think will smooth things
until I get a combined audio+midi interface.
I'm currently running
Auria Pro to mix using AUM to host the AUX effects.
@Gravitas: using an audio interface and MIDI interface into a hub should not be a problem. I've done it a fair amount and not had issues with doubled or stuck notes.
You might look at your routing on the iPad to make sure that there isn't something about how it is set up that is resulting in duplicated messages.
You might need to use a different MIDI Monitor app/plug-in to figure out what is app or device is responsible for the duplication. I find the AudioVeek MIDI Monitor and the Monitor in StreamByter handy.
Are you able to open the Auria Pro project enough to be able to choose a snapshot? (AP creates snapshots or backup snapshots pretty frequently). If you aren't able to get that working, here is a procedure you can use to fix things. I've only ever had to do this once:
https://wiki.audiob.us/auria_pro_-_recovering_projects
It can be useful to post about frequent crashes on the Auria Pro forum in the Bug Reports discussion. There are some helpful users over there that can sometimes spot things -- it also is sometimes useful for figuring out what the cause of instability.
I find Auria Pro pretty stable, but there are some AUs (and this is true for all DAWs, fwiw) that seem to be problematic for it. Figuring out what the trigger is will be helpful, RIM is gearing up for a development pass to iron out these glitches -- and the more information the user community can provide the better.
@espiegel123
I tracked down the duplication with @Korakios assistance last night
when he noticed the duplicated notes in the first screenshot.
I went through the midi routing and found the culprit.
Second screenshot.
I'm patiently waiting for Korakios to write the midi patch.
Until then I'm sharing some other stuff I've discovered.
On route to sorting out the midi side of things
I've been using midi wrench, web midi browser, midi scope and MIDISpy
to look at the midi information going in and out.
Ah yes, in regards to Auria Pro.
I posted up on the forum there about two weeks ago now.
No response so waiting until the next update to see if
it sorts out the Auv routing and midi problems.
It's a lot of code to rework so I don't want to disturb Rim at all.
The project that went into the crash reload loop had all of the AUv3's
stripped out before it went doolally.
No Au's, no effects other than the inbuilt ones,
no routing in or out.
This is the second project to go like that.
I've had projects go down and I've managed to get them back up
using snapshot but I have lost one track before which
I had to rebuild from scratch and the recent one
which I'm going to the same for.
I try to kept the bugs that I find in Auria Pro over at the Auria Pro forum
but as the same users are here as well and this is the largest repository
for iOS devices and us nutters who like making music with them
then I'm certainly going to voice it here as well.
Because when Auria is working the sound is quite something.
The eq's are the sweetest sounding and the bus compression
is awesome especially with the parallel compression stuff.
I love parallel compression for some of my mixing and mastering.
Can you PM me or post here a link to your AP forum posting. It is actually probably more likely to result in issues being discussed on the AP forum now (with as much depth as possible) rather than waiting until he is deep into the actual development or has released the next version.
The more information he has as he prepares to address the issues the better. That way he knows what there is to address and can plan accordingly. If he has the info now, he may see patterns that can be globally fixed rather than patched one at a time.
Here's the link I posted.
http://auriaapp.com/forum/viewtopic.php?f=20&t=16157
By the way ModernDayBlue is my art pseudonym.
Gravitas is my forum name to avoid any confusion.
@Gravitas bad news my friend, it can't be done with PureData via MobMuPlat. I am looking now at PdParty that can also load PureData patches , but I need to spend time to learn how to build GUI.
But I don't think it would work
I tried using the MidiOut object ,it's working on PC , I made a patch and tested it , but in iOS it's broken.
NoteOut object works as usual, meaning sending NoteOn with zero velocity ...Also both apps rely on libPD so I don't think it's possible for now (meaning months or years)
I really think it's not a true noteOff vs NoteOn-zero-velocity issue. The later was introduced ages ago (RunningStatus) and it's within the Midi Specs.
I have a feeling that the KeyStation is the issue. Try
1. Different USB cable
2. Powering the KeyStation via the 9 Volt input
3. Use a powered USB-Hub (It doesn't always make a difference if the interface has separate power input such as Zoom H2)
4. Using the physical Midi Out directly to MicroKorg (without USB) and see if you have any hanged notes by abusing the polyphony on the KeyStation
@Korakios
Dude, thank you making the attempt and once I get a desktop again
I'm going to try my hand at MobMuPlat as it seems to be quite accessible.
Once again thank you.
If the main goal is MIDI filtering, I suspect that both Mozaic and Streambyter will be lighter-weight and better supported -- as both are actively developed and supported. Mozaic is probably easier to learn. About 20 minutes with the manual is probably sufficient to learn everything that you need to know.
I looked at github for MobMuPlat and someone had the same technical issue .
https://github.com/monkeyswarm/MobMuPlat/issues/23
The dev asked ,back then if it was a hardware or virtual port, so it may make a difference.
So, download the patch and open in MobMuPlat app
On settings "Audio/Midi" pre-select the buffer because if you launch any other audio App later ,you will not be able to change the buffer. If you have already launched other audio app don't bother
Important : check background setting and set it to 'enabled'
Make the MidiIn/Out routings (keep only one input and output).
Now on 'Select Document' make sure 'Show All Files' and 'load on start' is enabled. Scroll to find the patch. You don't need to touch anything ,I was too lazy to make a blank GUI
Play some notes to see if anything is heard on microKorg
https://my.pcloud.com/publink/show?code=XZIlFG7ZdzTDfwXqtl0fDbPyYn33fuvhByXy
@Korakios
Dude,
Loaded it up into MobMuPlatt,
No other apps running except Midimttr to route the midi
Keystation input => usb midi interface => microKorg
Okay, going to be testing this during the week.
So far so good.
Awesome.
Why Midimttr ? Haven't really understood the routing you use!
Midimittr can be used as a midi patchbay.
I have no other apps running so that means it eliminates
possible midi problems going through any other app.
Here's a screenshot.
So, (continuing my quest understanding the midi routing) , the “USB Midi Interface” is a separate hardware (hoping not the classic super cheap ones ) or it’s the usb shown by the KeyStation with the “ MIDI Out from USB” mode activated ? (had a keystation ,first versions, first midi keyboard )
@Korakios
Exactly, it's separate hardware going through a usb hub.
It's a generic class compliant usb midi interface.
Bear in mind the hung notes have been right
across the board not only via the usb midi interface.
Bluetooth midi, usb interface, internal synths as well.
As they happen at random I need to use the whole system
for a few days to see what is function properly and what isn't.
Bluetooth would be my first suspect.
From the manual of KeyStation
MIDI Out
On the back of the keyboard you find the MIDI output port, which you can connect to an external sound module or MIDI keyboard. By default (when you switch the unit on), all controller data is sent out via the MIDI output as well as the USB out.
If you want the MIDI output to act like a traditional USB-to-MIDI interface, engage “MIDI Out from USB” mode by carrying out the following instructions:
Press the Advanced Functions button to get the keyboard into Edit Mode.
Press the black key above D2 (named D# 2), representing “MIDI OUT FROM USB.”
Edit Mode will finish.
The keyboard is now able to send data received from the computer out of its MIDI OUT jack to whatever device is connected. You need to select the Keystation 49e USB MIDI Out as the MIDI output device in your sequencer to use the MIDI output.
So to take out and the usb midi device you could
@Korakios
Annoyingly my Keystation is the model without midi 5 pin din ports.
I looked into that right at the beginning.
Yeah, I agree, bluetooth is looking like it is the culprit.
Still the patch that you sent through seems to be doing the do.
Awesome.
We shall see by the end of next week.
Thank you.