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.
IAA's that stay in memory after being closed. Reboot?
Hi. Some questions about IAA's, RAM and rebooting.
a) If I close a project in Cubasis that contained IAA synths, are those synth apps still somehow taking up RAM and possibly lessening the amount of memory available for whatever I'm going to do next on the iPad?
b) If that's true, does that mean that when I'm finished with a project in Cubasis I should then (i) open a blank document and then (ii) reboot the iPad?
(Note: I suggest action (i) to avoid Cubasis automatically reloading the old project when I start Cubasis again).
c) If all the above is true, then I guess I have to take the same precautions whenever I use Auria or any other sequencer with IAA's, correct?
d) If the synths are loaded into Audiobus, this issue doesn't apply, correct?
e) If the synths are AU's, this issue doesn't apply, correct?
f) Can rebooting too often be bad for an iPad?
Comments
You can do a soft boot: hold down the power button until the "Slide To Power Off" message comes up, and then press and and hold the Home button until you return to the Home Screen. That will kill all the ghost IAAs without doing a full reboot.
And yes, this issue only affects IAAs, AB and AU don't have the problem.
Thanks @richardyot . So I gather your answers to my questions are
a) Yes
b) Yes
c) Yes
d) Yes
e) Yes
f) ?
That was the kind of reboot I was talking about.
I can't see why doing a soft boot would harm an iPad.
hey Markk,
you can also try switching to each IAA app once after opening your project. That way, you have no ghosts and you can close the apps without rebooting. I found that works best for me.
Asking f) is like asking if using a light switch often is bad for your light bulbs
. Most probably (definitely) not.
Edit: or rather extremely unlikely. I'd expect that soft boot is part of the code it's just not one of those things Apple would put in the manual as it isn't 'Apple sleek'.
That sounds like a good isea, thanks @nick.
What @richardyot said is the current preferred reliable way.
Doing what @nick said is also workable, BUT, you have to remember to do it. You cannot now find out what IAA apps are ghosted in the background easily, and if you forget one with the open-and-close method, it'll still hang around eating memory at least and potentially CPU too.
One workaround is to use something like MIDIBridge to see what apps are still presenting a MIDI interface, but that involves extra steps of course.
@richardyot's suggestion is what I now have been using for some time to clear things out without having to do a complete reboot. It has worked since 8 reliably.
Who are we to meddle with the forces of the supernatural? Who gave us power to decide which ghosts live and which ghosts die?
What about creating ghost notes in DrumPerfect?
Someone needs to make an Exorcist app then!.......
With a Seance Fx AU unit.........
With a Ouija midi controller......
I noticed I close AUM and tonestack is still on but in the background even though I can't see it How is that possible?
Just one of those things Apple hasn't gotten right yet with the IAA implementation from what I've read. I do the what @richardyot describes below after every music making session routinely. If not I notice battery drain and other weirdness sometimes.
Yeah, but what if you just, for instance, opened ToneStack and then closed it properly? Just as effective? Definitely faster.
Not if you opened up a bunch of apps while you were working. Plus I still wouldn't trust it. Takes less than a minute to do the soft boot thing, and it always works. But to each his own...
Yep, that's a good idea.
I don't like the soft boot method, It can clear stuff you do not want cleared (cached website logins, and temporary files for other apps)
What I do if i suspect i have a ghost is start ModStep and look at the available MIDI out ports, this usually tells me which apps are ghosted, well those with midi ports anyway
midi included in the next version of the moz ouija board.
I assume you are talking about @richardyot's method that I also indicated I use too.
Never seen that happen. Do you have an example of the temporary files issue?
If I'm not in the mood for doing the power->Swipe->home method, I use MidiBridge for the same purpose. Takes longer usually once I've located all my apps, opened and closed them. ( @markk )
Almost but not all apps present a MIDI interface. Since doing this does not catch apps that don't, the soft "reboot" as you called it (it isn't rebooting) of getting to the "Swipe to close" screen and then holding the home key down instead, seems to be a foolproof method.
It is not an issue as such, as the apps will recreate the temporary files when they are needed, it can affect first use performance, by that i mean first use after the 'reset' (the action formerly known as soft reboot
)
It happened to me with a large video project in pinnacle studio (At least I think it was pinnacle, I have tried a few different video editors so cannot be 100% sure), where the first time I tried to play the project afterwards, it took ages and got me wondering why ? Then i realised it was rebuilding all the preview temporary files that it had previously built.
It was the website logins being wiped that was the biggest pain.
Well, that I can understand. Sure. If it's actually being caused by the process under discussion.
I'm not entirely sure we're talking about the same thing
as I've done this a good number of times and never had any issue with website logins or cached information in the browser.
Can you describe the exact actions you are taking that have led to the above two concerns. Just for clarity
in case we're talking at crossed purposes.
Following the soft boot, that richardyot suggested.
And just to clarify, they are not concerns, they are things that happened to me that have resulted in me not following that procedure again.
I prefer to use the Find the Midi Interface method, as I then know which apps it is that hang about regularly, meaning that when I use those apps I close through swipe up in multi-tasking.
Prevention rather than cure.
My choice entirely
Semi-related, my iPad battery was draining in a matter of hours (no apps open when double clicking home button).
I looked at the battery in settings, and sure enough, the mighty Thor had been opened for 12 hours in background and had killed over 50% of the battery. I opened Thor, and there were notes being held out lol.
Good shout ! using the battery in settings can tell of apps that are ghosted and still using CPU
Why isn't there an app with Taskmanager-like functionality for IOS?
In part, because Apple removed the underlying functionality in iOS 9 citing security concerns. sysctl() is no longer accessible by sandboxed apps.
Now I understand why my battery is draining so fast. I open up an AUM session with Tonestack, BS16i, Z3ta ,guitarism, Cubasis, and Roland SC. I proceed to close AUM first, then all the other apps. But for some reason TS or Z3TA stay as ghosts.
So there ought to be a utility in IOS providing this information. And of course the means to purge unwanted running apps. But that will probably never happen.
Indeed - because that would give us "too much" control - control that Apple in their wisdom doesn't think we should have in a locked down environment. It "makes sense" for the average user, information consumers, but not for "power users" but, I doubt that power users were or have been considered. After all, beyond pencil use for things like artists and architecture etc., we are are a unique and distinct set of users as music producers on the iPad. We use it like it was never "designed" to be used - running multiple apps together in parallel that strain the CPU and memory use.