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.
[ ONE IMPORTANT QUESTION ABOUT IAA ]
Now when you open an App with IAA and don't go on this app, it remain in background but it there isn't in background because you can't see it....I can see that there is only when I use Lemur and I connect a midi app, in list there is the other too...
My question is this:
- how can I close an app open with IAA but not visible?
- this app keeps me busy CPU?
Comments
Hi yes I experienced the same problem yesterday. After using Tabletop IAA via the new controller Mastermind with Galileo and NLog I closed all apps. A hour later opened midi bridge and nothing else and found Galileo and NLog showing a active within Midibridge even though the apps where closed and not back grounded. So I like answers to the same question as it's a CPU hog. Apart from doing a ipad shutdown or a hard reset is there a way to clear the IAA connections as they appear invisible. Maybe we need to wait for Apple to bring out a fix.
It should close once you boot it out of the host (if Apple did it right). Another thing you can do is to switch to the app from the host app and close it the old fashioned way I guess? I did notice that Alchemy got stuck in the background one time even though everything was killed from the task manager. I had to do a hard reset to kill Alchemy, and yes it was draining the battery slowly. So there are issues.
Edit: And what Collins said above only adds to that it doesn't really work that well yet (I thought it was an isolated issue with alchemy and MMS, but apparently not)
Download any of the thousands of system monitor apps that shows you what processes are running. Use that to see if the IAA apps really are closed or not. You can't shutdown processes but it helps to at least know if you need to do a hard reset or not.
All the reports about iAA make me think that audiobus doesn't have to worry much about the new competitor in iOS7.At least for a longer time.Such a shame because the specs of IAA looks SO promissing on the paper...Btw,anybody out there with an iAA node that runs as a midi sync slave and an IAA host that sends midi sync?i'm most interested in the"sample accurate"sync...
Did you notice background audio does not need to be on with IAA.
Also try switching out of the audio track before closing the app. The audio track seems to want to keep the app alive.
All the reports about IAA i saw let me think it's another apple half backed thing
.... like iOS 7 itself. They better get their things together.... competition is on the way...
This may be a host app issue. We'll have to wait and see.
There is a System Monitor App for see the Apps are working and close it if you want???
Ok I found a solution: You need to physically open the App you want to close and after close it!
ok,so just like before with audiobus.Except the apps are not showing up in the task manager?Anyway,not dealbreaker for me although something that needs to be fixed.
Can anyone recommend a System Monitor app. Sinapsya got your solution, but a bit of a pain to do. A bit like shutting a closed door!
I use this one. Don't remember what I paid, if anything.
https://itunes.apple.com/us/app/system-status-activity-monitor/id401457165?mt=8
There are no apps that can kill processes a la your typical PC task monitor, but they can be useful when troubleshooting... This one is free https://itunes.apple.com/us/app/sys-activity-manager-for-memory/id447374159?mt=8
Some ram "cleaners" might kill a bunch of old unused processes if iOS allows it.
For Looptical, when you connect to an IAA node, it automatically opens and show that app.
This is because during the beta SDK I quite frequently found issues with iOS connecting in some hidden way to a Node so that it was running, but not visible in the task bar, because it hadn't fully started up. This meant you could never connect to that node again without rebooting, because you could not close that node app and yet iOS thought the node was still in use and refused further connections.
As a workaround I decided to force the OS to start up the Node app so it was in the task bar and could be removed manually if necessary. And this is very similar to the Audiobus workflow where connecting an app opens that app up, so it seemed reasonable.
Perhaps you are seeing a similar problem to this? In which case you should take care to open the node app as soon as you connect to it. Your chosen host should provide a way to do this.
As to your question on CPU usage: if a node app is running in the background then it is almost certainly using CPU / memory. If that node app is not on the task bar but you can't connect to it with IAA then it may still be running (in some respect) and using CPU, but that's down to Apple's internal implementation of IAA.
It's very early days for IAA. Developers who took the risk of implementing from Day One have literally only just seen what everyone else is doing with it, and we need to collaborate on where it goes in the future and how apps interact meaningfully. So there is huge potential, but lots of hurdles to overcome.
@MooCowMusic I've been doing some testing for the Dev of Beat Vibe. I was having a problem opening the app in Looptical. He sent me a test flight build where he made adjustments because he thought the timeout was too short in Looptical. All is working fine now. Do you think this may be the case with Alchemy also?
I really hope Apple can fix this issue, preferably before iOS 8. Not loading a node do have the benefit of having more ram available (the node apps graphical assets etc doesn't need to be loaded). And ram is something Apple always seems to skimp out on for some reason.
I don't know where you get the idea that graphics aren't loaded just because you don't see them. It's not like apps have a headless mode. They still initialise like they would if they'd be launched stand-alone.
Something Rolf from Tempo Rubato said (if I remember correctly, could have been the Auria dev)
Why would graphical assets HAVE to be loaded btw?
Yeah, think it was Rolf on Twitter.
Well... maybe I'm wrong (or Rolf does something special in Nave/Nlog... he is after all one of the best iOS devs I know).
Time to break out XCode and actually test for this now that I'm curious.
The best I know is Rim from Wavemachine Lab...
I post now this dicussion on his forum, I'm curous too.
"Time to break out XCode and actually test for this now that I'm curious."
Me too. And just to add to my above comment, I really don´t remember anything else then reading some small twitter (from Rolf) saying the above. So it might have been out of context, and he was talking about how it would work later down the road when things mature. Or perhaps he just found a magic formula, since he is a wizard with iOS synths and all!
Sinapsya, yea i know Rim mentioned something about using less RAM, but I think that was in response to using 3rd party apps/solutions in general when compared to using an integrated system like IAA.
@ChrisG yes, but his working on it now, and when he make one thing he make it good
I could have sworn that I read about this somewhere, but I don't see it in the comments:
http://momupro.com/inter-app-audio-in-ios-7/
Sinapsya: Yes he does make good things.
About graphical assets in general..., 4pockets DAW have an option that will unload all graphical assets when switching to a new screen/tab and reload em back into memory when switching back. This gives the DAW and your project more RAM to work with, but makes it slower navigating the app. And vice versa, it can keep the gfx in RAM making the app feel faster at the cost of less recourses available for the actual project. I don't know how big of an impact it really does have inside ONE app using graphics from the same pool, but maybe some devs could try implementing something like that (like certain apps that are very prone to crashes and prone to deleting your work). Anyway, just something that came to mind when talking about graphics and ram
That's another thing I really like about Meteor--VERY efficient! If they only fixed their GUI, I'd likely be very happy with their product...
@Audiojunkie That's only a handful of his tweets tho (and he tweets a lot!:)
That makes sense. :-)
When a host loads an IAA node, it launches the app into the background (if it's not already loaded). Because all IAA nodes need to have background audio mode enabled, this means they are now running and consuming CPU in the background. But this is really no different from the way you use Audiobus right now. It just means you'll need to kill apps you're not using any more after you're done recording.
Due to a bug in the current iOS, you also need to make sure you unload your IAA node from the host before you kill it. Otherwise you'll have the issue MooCow was referring to.
Rim
@Sebastian: Actually, on iOS7 graphics does not seem to load in the background. That was the reason AudioShare's audiobus REC trigger stopped working in iOS7: it depended on the presence of the visual record-button, but "viewDidLoad" was never called while the app was backgrounded, only when it was brought into foreground.
And regarding IAA, I think it's one of the very nice things with IAA that it can launch an app in the background without switching to it! If host and node are implemented correctly, the node will start running audio in background, and it will stop after being disconnected from the host. If you wish to force close it, just open it the usual way (tap the icon in the home screen) and then force close it.
However, iOS7 has bugs and IAA is very new, it will take a while for things to get sorted out and stabilize. Also we need more documentation and "best practices" to avoid a lot of badly implemented hosts and nodes.