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.
how to filter out midi signals ‘254’ / ‘FE’ in AUM from external midi keyboard?
My midi keyboard recently started sending jitter signals, resulting in tons of stuck notes in AUM (but not on other hardware synths) and I used midiflow to determine the signal was ‘254’ or ‘FE’ which seems to be ‘active sensing’… I don’t know how to get the keyboard to stop sending it and don’t know why it started doing it (it’s really old so it could be all kinds of reasons)…so anyways, it seems like the simplest way to get it to stop would be to just filter out that signal, but despite all of AUM’s nice midi signal routing capabilities there doesn’t seem to be a way to filter out that message… does anyone know of some kind of app or some other way I could filter out that signal? I am using a pretty simple midi-to-usb midi interface to connect the keyboard, but haven’t had this issue in the 7 or so years I’ve used this setup, so I don’t think anything changed there.. I am ready to resign to the facts that my old 1988 Roland piano might just be shitting out but if there’s a way I can put a band aid on it using a midi filtering solution I’m all ears. Any advice would be great 😅 thanks for reading my rant - if you made it this far, you’re a saint. Cheers
Comments
One more thing: in googling this issue, I did find some folks with similar issues and it seems like sometimes midi controllers can get put into a setting where it constantly sends ‘active sensing’ midi cc’s (even after powering off and restarting the device / etc) and there’s a way to send a universal midi ‘stop / 0’ type of signal to the device which might fix it, but I cannot figure out how to send that midi message… I actually do think the problem started when I sent one of my sequencers into the midi-in on my keyboard to control a different drum machine via the midi thru… so hopefully it is just some type of setting that can be changed via a program change or CC type of signal? Idk… I did look at the midi chart in the manual for the device but most of that is pretty basic and not helpful. Either way, it seems like something I could hopefully just filter out because my hardware synths don’t seem to care about that midi message, it only just creates an issue in AUM with stuck notes when it is routed to control something like Module or a soft synth, etc.
Just hoping there’s some kind of more advanced midi processor that can filter the ‘254’ active sensing message out (without me having to do any special Sysex / programming coding type stuff)
Thanks again
Streambyter is a free app that can do this for you with just one line of code:
FE = XX +BJust type that into the interface and hit "Install Rules". Route your keyboard to Streambyter, then Streambyter to where the MIDI needs to go.
But, have you tried turning off Sys. Real-time (Clock) messages in the channel routing? The FE (Active Sensing) message is a MIDI clock message.
FE shouldn't be being sent unless your keyboard is sending MIDI Clock. Do you have a way of checking to see if you have clock sending enabled from the keyboard?
It's odd that the active sensing message would trigger the kind of behavior you're seeing.
Streambyter can filter it out.
There is no midi clock in the midi implementation chart that I saw… I thought that was weird too! I did have a midi clock going into it and thru before it started giving me issues…so I wonder if somehow it ‘wrote’ that into the hardware? Idk…. I mean, I am dealing with hardware that is nearly 40 years old at this point lol so who knows
I will def try the streambyter solution - thanks all!
When I get a chance I also will try to plug my sequencer back into it and turn the sequencer on and off again to maybe ‘stop’ it?
Turning off Sys. Real-time (Clock) messages in AUM's channel routing may do the same without using Streambyter. It's worth a try.
Def gonna give that a shot too. Thank you!
FWIW, some devices (particularly ancient ones) that don’t have MIDI Clock send out active sensing—particularly early ones. I am pretty sure OG DX7 did.