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.
iOS 7: really bad as you told us?
![[Deleted User]](https://secure.gravatar.com/avatar/9ef6d0eb0160d6fc751629ca2893b346/?default=https%3A%2F%2Fvanillicon.com%2F97e1dd38a3b5c862e3e656328498999c_200.png&rating=g&size=200)
Howdy, audiobus team,
Well, what about the message you sent out to us about the bad behaviour regarding iOS7 within music applications? I don't really see many issues mentioned here in the forum, please tell us more why we should wait to update.
To be honest, I don't feel nice about your mail. If there is any real issue about you should have told us and not just only "hey, stop". Take me as a serious partner not as a dumb user. Thanks.
Comments
Yikes.
Thomas, they couldn't say what the issues were before it came out due to NDA. After it came out, the issues discussed were some apps running poorly (or crashing on launch) and a bug where notifications and phone calls would lock up the audio system. That could happen in the middle of a recording (and still can). Plus, other stuff. The truth is out there.
I, for one, appreciated the forewarning. If you depend on your device for music production, which I don't, I can't see AB's approach being a bad thing at all. Also, it was a recommendation, not a dictate. They couldn't know if there was a real issue, since they don't have the code for all the audio apps out there, but to alert us that they had noticed some areas in iOS7 that could pose problems was very considerate, especially since they had no mandate to do so.
Chiming in as well--on the side of Sebastian and Michael (who just wanted us to have caution, rather than regret).
^ What Audiojunkie said. Caution > regret.
So, thomas, you would rather not have been warned, updated your device, and potentially had your apps start crashing etc. than be warned of such potential before you updated? You're throwing sound advice you got for nothing back in people's faces.
I have updated and experienced zero issues, but I was aware of the risks of updating and was able to make a conscious decision thanks to the advice the AB team and others put out there.
.
I took the warning seriously, and am grateful for it. I sympathize with the frusration re lack of reliable info. I definitely look to the Audiobus community to get the scoop on the current status of iOS. The confusion arising from "don't do it," and/or "everything works fine," inevitably results in feeling jerked around. But it's really Apple that's doing the jerking. That said, I would appreciate a word or two from the AB team re what they think is going on at this point.
.
Sure, you're right. I've been doing music production on Apple computers since 1986, so I've been thru good times and bad with OS upgrades. Never used PC never will. What I mean by being jerked is often beta testing an OS that's not ready for prime time. Mostly though, I'm just say'n if folks need to play the blame game it ain't AB.
When AB was released,Seb and Micheal allowed devs to add their apps in a slow,steady stream.Any app that had conflicts with AB could be fixed/updated and users were not confronted with multiple issues from lots of apps.It was cautious but gave us users a seamless,issue free environment to work in....(The SDK was not made public till months later)
They are in a unique position of having hundreds of apps and thousands of (dumb?)users relying on AB working properly.
These guys are German...when they make things,they want to make sure they work properly:)
I'm german as well.... However I don't want to be misunderstood. A warning is ok, no problem with it and in one way I'm happy to get it. But the warning was blown out the world without any more information. No comment about "locks up when a phone call comes in" or similar. The warning was also took over by other journalists uncritically which cumulates to a complete shitstorm-like reaction. Google for it. A product like AB is worth to get a better and more professional shape in communication.
I didn't realize they were such a big deal in Germany
(I joke)
Personally I agree with several others on here. I think it was a helpful message. I also have a hard time understanding how it could have caused much of an uproar elsewhere and not really one at all here. There was a kind warning from some developers. Everyone here certainly heard it. At least half of them felt like I did and said "meh, shiny" and upgraded anyway. And there are bugs. I don't think anyone on either side hold the Audiobus guys responsible. I don't anyway.
You have a point Thomas.
It can't be easy tho..being in a position where you know you need to say something but you have your hands tied.
Hopefully a lesson learned,but I'm still happy I was given the 'warning'
I still updated within a few hours of release.
Sebastian did mention that IPhone users should be aware of the incoming call bug which would not effect Ipad users.
It was also just a 'wait' message.
We could have all waited because ,the thing we were all 'waiting' for......IAA,still isn't ready to use.
Updating to 7 hasn't given us any benefits yet.
@commonstookie
Well, except for all the benefits of iOS 7
Which are?
IAA is tightly integrated into iOS core audio, so no latency issues as you'd get with using 3rd party apps like Audiobus or Jack etc. Also, uses less ram if the node app can be used without switching to it (which will load the node apps user interface into RAM). Obviously it'll take a while for all this to come together. And if Apple continue to do their 1 or 2 updates to iOS per year, it'll take a loooong time for IAA to reach all the needed functionality like switching presets and parameters data etc. So Audiobus and multi effect routing capabilities with whatever else they cook up are probably not going anywhere anytime soon
That's what I figured, problems now, debatable benefits at some point in the future. I'm quite content with the current capabilities of my iPad 2 with iOS 6.1.3. I shall embrace iOS 7.x.x if I ever buy a replacement iDevice that comes with it preinstalled.
...indeed... i have the bug with the call since ios 6. So it's not a new bug for me
What people don't understand is that because of the nature of Audiobus we're getting support requests about ALL the apps. Sometimes even though Audiobus isn't being used in the setup at all.
I've got about a few emails from users that didn't read our 'Wait' message and now cannot use their apps in iOS 7 because they're buggy. And then a few dozen more from people thanking us for it.
And then another email from a user that cannot use his favourite apps anymore that reads:
warn their customers(me) about this problem. How hard is it to send your
customers an email? DUH!
I also think the original poster is a troll.
We've had enough drama about this and if we didn't genuinely think there were enough problems out there to warrant a warning, we wouldn't have done it.
Here's a list of the bugs with my personal rating of how important they are:
And finally, it wasn't just us. Native Instruments warned a day earlier than us, same message. If you read the discchord blog post about it other developers are saying the same thing.
We take musicians very seriously. A warning was in order.
'Troll' might be being a bit harsh. I looked at his comment history earlier and it seems to be genuine, if infrequent, forum participation. One thing is certain, however, your warning was appropriate. I, for one, am very grateful.
Yeah that might be right. I apologize.
I just have a hard time grasping how a warning issued by two guys who make an app to wait until updating to a new operating system could be perceived as anything but prudent.
We didn't even tell anyone NOT to update. We just said wait.
What's the worst that could have happened if everyone heeded our advice? Users waiting for 2 or 3 weeks to update to iOS 7?
What's the worst that could have happend (and is happening) for users that didn't?
People not able to use their apps.
Questioning this obvious choice (us warning people) just feels weird to me.
Even though I updated, I still appreciated the warning. At least I was prepared to blame myself if something went wrong. On the other hand if their was no warning, I might have questioned why the Devs who had prior access to IOS 7 didn't warn us if they saw the issues. So, I appreciate the warning Thanks @Sebastian.
@Sebastian: Your warning was completely appropriate. I applaud and thank you for it. Ignore any dissenters. It's not your fault if a some folk over-react to sage words of caution.
Re SoundPrism: is an update due any time soon?
+1000000
for the warning
-1000000
fuer die komische klage
please, don´t shitstorm me for my critical view. If you don´t feel well with it you should say that and that´s enough. I am Audiobus user from the first hour and still very keen on any news and updates but there is no reason to make a personal thing out of it. I´m neither a troll nor doing bad jokes here, okay? Keep calm now.
I think the OP was legit. ... just a bit less civilized compared to how we usually interact on this forum. No offense, Thomas.
and I think Sebastian gave a useful, concise answer with his "list of the bugs," which is nice to have in one place. Can we really expect anyone less than a highly dedicated Audiobus forum member to sift thru 124 posts on a thread titled "Do we have a volunteer?" in order to find out iOS 7 problems?!
;-) just sayin'