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.
SOLVED: MidiBus-enabled apps crash on launch with wi-fi but no internet
I have been struggling with a show-stopping bug that is hitting a large number of apps that I use in a live scenario, where I have an iPad Pro and MacBook on the same wi-fi network for LINK, but obviously not connected to the internet for my gig.
All of these apps freeze/crash when attempting to launch when connected to wi-fi but no internet:
iSpark, Infinite Looper, iVCS3, SynthMaster Player, All AmazingNoises apps (Dedalus, apeFilter, GliderVerb, DubFilter, iDensity, Moebius Lab, iPulsaret), Roland Sound Canvas, Frobulator, Muckraker, Nebulizer, Shoom, jgEffects, Amplitube Acoustic, MidiBus
They all freeze/crash in the same exact manner: splash screen freezes for 20 seconds, then it crashes into the background. Then when you navigate to the app it is frozen on the next screen (not the splash screen, but the app's UI), but none of the UI is responsive.
TODAY: MidiBus released an update that corrects this in MidiBus. MidiBus had the same exact freeze/crash behavior, and now it is fixed!!! I assume all of the above apps must use his library, or have a similar bug that Nic can tell them how to fix.
I started a thread on a different topic here that morphed into this, but I thought this deserves its own thread:
https://forum.audiob.us/discussion/comment/264592/#Comment_264592
@SecretBaseDesign @mauriziogiri @lbiyikoglu is the fix for your app as simple as updating the MidiBus library and pushing an update to the store? I can help beta test! (I'm already set up as a beta tester for Infinite).
Can one of you PLEASE appeal to Rolph to fix this for iSpark? This one is mission critical to me.
Comments
I think I've got the latest goodies from Nic (the MIDIbus/MIDI Bridge developer), and should be pushing out an update shortly. I work with Nic and Dan (MIDI Designer) on the music IO project, and we've been working together to try to track down the issue. They seem to have figured it out, and I need to sync up with them to understand their wizardry.
What I think was happening was that if you have a WiFi connection, without internet access, and the router and machine have not cached a DNS address (a combo that's actually tricky to set up), there's a call that can time out, and fail badly....
Its an Apple AirPortExpress that has never connected to internet, so I guess that how it does not have a cached DNS address.
Nic has most definitely fixed the problem with the MidiBus proper app.
Thanks so much for letting me bug you so much about this issue. Seemed to me like there would be lots of people in my boat now using wi-fi for LINK but isolated from the net for a gig, but it seems like I'm the only one! Thanks