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 do you report/read crashes?
They happen randomly and I wonder how do you distinguish in between the components of a specific setup ( ex. Aum/Audiobus plus auv channels and midi ).
It is really disappointing when starting working and after 10 min something goes mute or it just disappears ...
How do you avoid these scenarios?
How you report/read them?
Comments
With no specifics about what you are doing when you get crashes, there is no way to fruitfully advise. One needs to track the steps preceding the crash and report them to the developer--usually through their web site. Crash logs are found in the Analytics section of the Settings -> Privacy section.
iOS isn't as open or predictable as other operating systems. There's nothing the equivalent of Windows event viewer or Linux log files. There's no visibility into resource usage. Even CPU usage indicators in host apps can be misleading because they don't have complete data to report on. iOS does its own thing for memory management, so it can just arbitrarily decide to unload an app, or just simply let it or the host crash. It throttles CPU when it decides it wants to in order to run with less battery consumption.
It's also almost never certain whether a problem is a host problem, app problem, iOS problem, or some background process like checking for app updates or email, or getting a text message. Some apps are especially unpredictable and can run great for a long time then become crashy for no apparent reason (Thinking of Enso here), then work great.
You just have to experiment, get a feel for what is stable and what isn't. If I run into an issue I first try to see if I can reproduce it, and whether it goes away with a reboot. I always check if the behavior is the same in different hosts. Then, if I can, I see if it happens on another device. At that point, I check here to see if anyone else can reproduce the issue. If they can, then I do the best job I can reporting it to the developer.
Sorry, that probably isn't what you wanted to hear. But it's the nature of the beast. We give up a lot of predictability to gain all this low cost fun and mobility.
Thank you, I appreciate your input. I suppose this great online community is a good way of giving such sort of feedback.
It definitely is an amazing resource! If you get stumped by a problem, it's virtually guaranteed that there will be someone who has been through it already, or can figure it out, or confirm that it's a problem, or can explain to you why it's unsolvable and suggest a workaround.
It's never failed me yet when I've been stumped about something. And there are plenty of things to get stumped about in iOS music making.