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.
AUM causing Reason 10 Midi Overflow?
Hello all,
Anyone here picked up Reason 10?
I was doing some experimenting today and discovered a weird issue.
When I try to send AUM midi out via the midi routing, midi notes will trigger Reason instruments. However, as soon as I try to record I get an error in Reason that reads "Midi input about to overflow! Your computer isn't fast enough to handle MIDI input at this high rate.
Initially, I thought it might be one of the Rozeta apps causing the issue, but I get the pop up even if I simply use the AUM keyboard.
To make sure it wasn't an issue with the Bluetooth Midi or the computer, I tried Fugue Machine, as well as Audiobus Midi, and it recorded no problem. This makes me think it is an issue with AUM.
Anyone had this problem? Any suggestions for a fix? Are the AUM folks active on this board?
Thanks
Comments
Do you have something active that may be sending midi clock and/or active sensing messages? Not that those should overload a properly designed midi handler...
I'm here. Please email me the details and let's have a look at it! (info at kymatica dot com)
Perhaps you have some feedback routing happening? You could check with some MIDI monitor software on your computer to see if it actually receives a lot of messages or not.
I had the same message with my LPK25 wireless but not Model 15, which is bizarre because the LPK only sends note data whereas Model 15 was simultaneously sending notes, pitch/mod, aftertouch, and cc messages.
I would guess that it’s an issue with Reason 10 but I don’t know what it is or why it’s happening. I’ll try using AUM tonight and report back.
Thanks for the feedback folks. It was a late night session so I had to give up testing. I will try again over the weekend and report back.
@j_liljedahl I will contact you via the email address above. Thank you.
Just a heads up, I was able to record Rozeta over a Network MIDI connection but not over Bluetooth. I'm using my phone so I couldn't check Fugue Machine, but it seems that Reason 10 has trouble with Bluetooth.
@jrjulius Thanks for the test. I wonder if that is why my Bluetooth Korg Keyboard was disconnecting constantly as well. Will test more.
I also wonder why I was able to record over bluetooth with Fugue but not via Bluetooth in AUM. Is it possible that AUM has bluetooth issues? Not sure, but I really appreciate your help.
From the perspective of an app, there's no difference between a bluetooth endpoint and any other endpoint. Bluetooth connections are presented as standard virtual midi endpoints by iOS, so from AUM it looks exactly like sending MIDI to another app via virtual midi.
Maybe try sending to something other than Reason and see if you get the same error. If not, it is most likely Reason I would guess.