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.
audiobus2
I have some fx apps that won't work in audiobus2 such as crystalline, echo pad and flux fx. I don't know why they won't work in audiobus2. I am on the latest os update (ios 11, ipad air2).Would these apps work in audiobus3? Does anyone know why these apps don't work in audiobus2. Does anyone else have this problem? Thanks for any help.
Comments
Strange after reading your post I decided to check. I have both audiobus 2 & 3 and presently use 3 all the time and the above mentioned apps work fine in it. However after reinstalling audiobus 2 nothing seems to work. ( ios 11, ipad air1)
Thanks for your comment Lowetone. Can anyone else add to this? I can get silq to work okay in audiobus2 but as far as those other app are concerned I get nothing. I can't get some of these apps to work in AUM either (silq is okay in both AUM and audiobus 2). Is the problem Audiobus2 or OS11 or the apps themselves or a combination of all 3. If you have AUM would you try those 3 apps to see if they are okay. Thanks.
@chasbee: i just tried. Flux:fx doesn‘t work in AB 2 or 3, only as an IAA plugged into AUM. Silq needs to be started first, then is working inside AB2/3. I did get some crackling inside AB3 lately (same setup working fine with AB2 still), but nothing of great importance... . All else seems to work nicely (tried with Air2 just now, otherwise all seems samey with Pro 9,7“ so far...), good luck!, t
Just tried the above apps in AUM, no problem.
I don’t have AB3, only 2 and it seems that apps that run on AB3 don’t run on AB2 for whatever reason, not being listed or compatible or updated.
Audiobus 2 is probably abandonware in a sense that new apps won’t be compatible with both.
Ah! I'm wondering if this is an iOS 11 bug I've seen with a few others. What happens if you delete & reinstall the apps that aren't working with Audiobus? Do they then work?
If yes: this is a bug in iOS 11 that I'm still trying to nail down well enough to bring to Apple. It seems to have something to do with a corruption in the Inter-App Audio registry - at least, that's the current theory, given that these apps don't work in any Inter-App Audio host (Audiobus, AUM, GarageBand, etc) until they're deleted and re-installed, and then they work.
>
Might have nothing to do with this, but Sensual Sa recently insisted it was not installed when loading a Garage Band file that referred to an older version. Deleting the old rack and making a new track solved this.
However, if I want to make a new track using an AU, taping the GB AU button brings up IAA apps. Tapping IAA brings up the AU List. I am assuming it is a minor glitch which will be fixed in due course.
I use crystalline (current version) and AB2 (old version 2.3.9) without any issues. iOS version 10.3.3.
My theory is: 2.3.9 would cooperate with crystalline and iOS 11 - just a theory, sorry.
That’s not been my experience - there seems to be an issue right now on 11
Thanks for all comments. Echo pad, Flux:fx and Crystalline won't run in Garage band (on my ipad at least). It seems that Audiobus 2 is now no good for effects (except silq which seems to run in everything). I think os 11 is mainly to blame. I've tried re-installing these apps. Crystalline worked once but not second time. What with re-installing, switching the ipad off and on, waiting for this, that and the other, and hoping apps are going to talk to each other, I will probably not buy any more fx apps until this problem is sorted, if ever. I'm very disappointed with Apple for allowing this to happen and it will affect my future spending plans. There is no point in chucking good money after bad. music apps on PC or Mac do not inflict these problems on us. There is no guarantee that this won't happen again with os 12 or 13 or whenever. It is not good enough. Apple take note.
I've just tried those 3 fx apps in my ipad 3, which does not go higher than about os 9 and all three apps work fine in audiobus 2 and in AUM. This means of course that os 11 is to blame for the problems with these apps. Anyone who didn't update still has the benefit of these fx apps with audiobus 2. If only I could go back to os 9, or thereabouts at the flick of a switch. Perhaps I can work out something using both ipads (ipad3 and ipad air 2) and some wiring but what a pain.
Have you tried deleting and reinstalling those 3 apps, @chasbee? Others seem to have resolved the issue by doing this. Let me know how you go, because I want to pass the result onto my contacts on the audio team at Apple. They'll be as keen to diagnose and fix the issue as you are to have it fixed!
Also: a sysdiagnose would be really helpful too - the guys at Apple have asked me to pass these along to help diagnose the issue, as none of us have seen the problem personally. If you’re interested in helping, here’s how:
Notes:
The file is quite large so I recommend doing this on wifi. If your email setup won’t let you send the file, we might need to work out an alternative, like using Dropbox instead.
I have been in touch with Christopher Rice of Holderness Media who makes two of the aforementioned apps, Echo Pad and Crystalline. A couple of days ago, Christopher Rice said to me and I quote. “and my apps are working correctly on all versions.” Following this exchange of views, I got in touch with Apple support. They suggested that I restored my ipad (air 2, ios 11.1). This I did. It took over an hour and for anyone who is new to this (I’m no expert), a restore deletes all apps and data and puts a fresh operating system on the ipad, then re-installs all the apps from a backup on your PC or Mac. This restore made no difference. Just as before, I could open AUM, then load a synth such as Animoog into it. Then I could load an fx app such as Crystalline into it. This worked okay the first time, but if I then tried to close AUM and then open it again with Animoog and Crystalline, The fx app would not load. Whatever I did, I could not load the same fx app a second or subsequent time. Following this, I restored my ipad a second time. This time I deleted everything, including all my apps and I was left with a fresh operating system and an empty ipad, no apps, no nothing (except those apps which are automatically installed along with the new operating system). I reasoned that this was the freshest os in factory state I was likely to get and this os could not have been corrupted by anything that I had done, because I hadn’t done anything. Then I installed just three apps, AUM, Animoog and Crystalline. Then I did the same as before. I could not get Crystalline to open more than once in AUM. This behaviour applies to other fx apps. It is not just apps by Holderness Media. I told all this to Holderness Media but they seem unwilling to reply to me now. However, I know they follow (or he follows) this Audiobus forum because this particular post was mentioned by Holderness Media. Holderness Media will hopefully do something about this situation. If anyone else has the same problem with os 11 or 11.1 would you please say so. Thank you.
os 11.1.1 update out now. Please add this to comment above.
Again, @chasbee, I'd love to see a sysdiagnose. This is a known iOS 11 bug, and we need data to provide to Apple so they can begin addressing the problem.
Again: this is an iOS 11 bug. It is not a Crystalline bug, or an AUFX/etc bug. It's Apple's issue to fix.
I must say, I am becoming increasingly annoyed with the tone of your comments towards me here and in the emails we’ve exchanged.
Like many other iOS developers I am a one person company, not some giant corporation with an evil plan conspiring against you personally in order to screw you out of what ultimately amounts to a few bucks.
I can’t always respond immediately to every request I get, but I try to respond within 24-48 hours. So far we’re a little over 24 hours since your last email.
Whenever someone has issues with my apps I try my best to help, and as any other iOS app developer knows, this is an ecosystem of music apps and we all regularly help users with issues that aren’t even related to our own apps.
I try to help educate people about iOS music production wherever I can, but when people come at me with a bad attitude straight away such as you did, I have zero patience for it.
Perhaps it goes against conventional business wisdom that says the customer is always right no matter what, but I don’t play that game.
(Chalk it up to past experience in customer service, it isn’t difficult to tell when someone feels entitled to treat you poorly simply because they’ve purchased something from you.)
For contrast, I have now had two other users who contacted me about the same bug, for a total of 3 people. The other two had a completely different attitude and although experiencing the same problem as you, remained friendly throughout and were able to communicate back and forth with me without any rudeness whatsoever.
One of them was able to fix the problem by simply deleting and reinstalling the apps, as has been mentioned several times. For the other, I guided him through various steps to try replicating the bug in hopes of finding the root cause, but unfortunately thus far we were unsuccessful in finding a solution for his system.
The fact of the matter is that right now no one is sure exactly what is causing this bug but it is affecting multiple manufactures, and the developers of the impacted apps are all coming to the same conclusion that this is a bug in iOS 11 itself, the reason(s) for this are so far unknown.
As Michael pointed out, If affected users are able to provide as much detail as possible about the bug it will help speed up the process of finding a fix, which is why I was trying to get more specific details from you regarding the nature of the bug.
Your responses to me via email each time have a tone that insinuates that I surely must know exactly what the bug is, that my apps alone are to blame, and that I’m somehow trying to pull one over on you.
I am sorry that your system isn’t working as it should right now, but perhaps being a little more reasonable to those trying to help you would be a better approach to getting the problem solved.
In the meantime, if you wish to continue receiving any help from me on this, you’ll need to show some respect.
Seconded
@chasbee New operating system version means apps get broken. Troubleshooting these problems between multiple devices and operating system versions while Apple keeps throwing monkey wrenches into the mix (without much worry about music making) it gets pretty overwhelming.
It drives all of us nuts everytime apple comes out with a new OS but it's very frustrating for the developers (who want their apps to be stable) as well.
honestly I'm greatful whenever I actually get to talk to a developer instead of a tech support desk clerk.
Have I told you a lie? The answer to that is no. I have written proof of everything I say. I'm afraid your arrogance and your ego may be your downfall. You have said a lot more to me than the few words I quoted. Would you like to see more of your words in print? These apps are still being offered for sale by you and by others, even though there is a fault. If this were eventually to come to court you would lose. At the moment, (to use a legal term) these apps are not fit for purpose so climb down off your high horse. My first question to you was not in anyway rude or abusive. I simply asked you if you had any plans to fix this problem. The trouble is you didn't think there was a problem and you said so. I'm afraid it went downhill from there. I have never been rude or abusive towards you, and this you know.
Dude