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 Store

Loopy Pro is your all-in-one musical toolkit. Try it for free today.

First Impression with Air 2

13567

Comments

  • edited October 2014

    OK, gathering the pieces of information that I've heard, here's what I understand:

    1. The problem will take several months to fix, but it will be fixed. That tells me that the hardware doesn't have to change to fix the problem.

    2. Since NDAs are keeping people who know the issue from saying what it is, we know that it is apple's problem.

    3. Even developers that know what the problem is can't fix it--not because they don't know how, but because they aren't able to.

    4. Since according to Tim the problem is low level, not the fault of the hardware, but still an apple problem that external developers can't fix, I believe the problem is with the OS.

    I believe the problem is rooted in low level coding in iOS 8.x.

    Furthermore, I suspect that the problem has to do with threading management within the CPU cores.

    To add to that, since we know that the problem is with iOS, the only way we will be getting the problem resolved is through a new release of the operating system--whether that is through a point release or a full version release remains to be seen.

    Either way, whether we wait a few months or several months for the upgrade hasn't been announced as far as I can tell, so the big question is: Will it be 8.2, 8.3.....9.0? When???

  • edited October 2014

    @cruise - Are you ok? Did Sebastian's PM include a digital lobotomy?

  • @musicinclusive, you are correct, i was not slamming AB. I was answering the criticism that I rushed into anything with unrealistic expectations.

  • Time to start praying for new iOS updates! :-)

  • Grow up, for God's sake. * Massive facepalm *

  • Um... @Michael_R_Grant Was that directed at me? If so, please explain why...

  • edited October 2014

    @Audiojunkie said:

    Um... @Michael_R_Grant Was that directed at me? If so, please explain why...

    I know very well it was not meant for you. Please read Ringleaders comment just above.

  • Excessive passive-aggressive behavior is a sign of low testosterone levels. Might want to get that checked out, @cruise.

  • Sebastian is too kind. Ban the troll, I say.

  • Whew... I wasn't trying to offend. :-) I feel better! :-) I've been wondering what's up with @cruise too.

  • @Audiojunkie Noooooooo, it wasn't. Sorry if you thought that!

  • @Canis thanks for that breakdown. Would be interested to know how many OSCs you can run before crackles on your older iPad(s).

  • @Audiojunkie said:

    1. Even developers that know what the problem is can't fix it--not because they don't know how, but because they aren't able to.

    This one is the scariest.

  • Well, Tim's (Webb not Cook) post adds nicely to the confirmed paranoia. Sounds like they discovered a crack in the plate but only after sending out the wedding dinner and are now scrambling to fix it having decided to tough it out rather than publicly queering the perception of the new releases (hardware and software). PR SNAFU. I think Tim's exhortation to 'submit a video I can post as news....' was a very interesting shout. What we need is a 'Deep Throat' who can give someone the skinny that can then be shared....shame Ben Bradlee died Tuesday.

  • @Audiojunkie said:

    OK, gathering the pieces of information that I've heard, here's what I understand:

    1. Since NDAs are keeping people who know the issue from saying what it is, we know that it is apple's problem.

    That doesn't necessarily follow, Apple certainly isn't the only company that requires people to sign NDA's. I've signed one, and it sure isn't from Apple. (And it also has nothing to do with this debacle as far as I've seen so far)

  • Can you test it with Auria and some Fabfilter plugins??

  • @Sinapsya said:

    Can you test it with Auria and some Fabfilter plugins??

    yes! Please!

  • @Zymos To be sure I understand what you are saying: Are you saying 1. You know specifically that the problem is not iOS, but you've signed an NDA and can't talk about it, or 2. developers other than apple have people sign NDAs?

    I've signed NDAs as well, but there are app developers that openly state that the problem isn't coming from their apps (and yet the problem continues).

    I still believe the problem stems from iOS 8, and a fix to the problem will need to come from there. Have you read Tim Webb's latest blog posts? He too is under NDA and can't say anything, but reading between the lines of posts from developers and Tim (as well as others), leads me to believe I'm on the right track.

  • edited October 2014

    By the way, @Sebastian is just one of those who've said that the problem is not coming from their app.

  • Very disappointed by this!

    Is this just an audio/music app issue or does it affect other types of apps (photo editing, games, video) as well? That would make it more urgent for Apple to fix!

    Was ready to get an Air2 but have to reconsider now... ;-(

  • @mmp I suspect this will affect motion video editing as well.

  • @Audiojunkie said:

    OK, gathering the pieces of information that I've heard, here's what I understand:

    1. The problem will take several months to fix, but it will be fixed. That tells me that the hardware doesn't have to change to fix the problem.

    2. Since NDAs are keeping people who know the issue from saying what it is, we know that it is apple's problem.

    3. Even developers that know what the problem is can't fix it--not because they don't know how, but because they aren't able to.

    4. Since according to Tim the problem is low level, not the fault of the hardware, but still an apple problem that external developers can't fix, I believe the problem is with the OS.

    I believe the problem is rooted in low level coding in iOS 8.x.

    Furthermore, I suspect that the problem has to do with threading management within the CPU cores.

    To add to that, since we know that the problem is with iOS, the only way we will be getting the problem resolved is through a new release of the operating system--whether that is through a point release or a full version release remains to be seen.

    Either way, whether we wait a few months or several months for the upgrade hasn't been announced as far as I can tell, so the big question is: Will it be 8.2, 8.3.....9.0? When???

    I cant believe what I am reading. All these reason keep me on my ipad4. I like ios but if you read the above I think apple has to do their homework again. It's ridiculous.

  • @Audiojunkie said:

    @Zymos To be sure I understand what you are saying: Are you saying 1. You know specifically that the problem is not iOS, but you've signed an NDA and can't talk about it, or 2. developers other than apple have people sign NDAs?

    I've signed NDAs as well, but there are app developers that openly state that the problem isn't coming from their apps (and yet the problem continues).

    I still believe the problem stems from iOS 8, and a fix to the problem will need to come from there. Have you read Tim Webb's latest blog posts? He too is under NDA and can't say anything, but reading between the lines of posts from developers and Tim (as well as others), leads me to believe I'm on the right track.

    Number 2- I don't have any other information about the issues in this thread. But even Tim said "a pile of NDAs", which to me means they are not (or not all) from Apple.
    Some of the problems may stem from iOS 8, some from Audiobus itself, some from other apps...

  • edited October 2014

    There was never a x.2 version of iOS.... or? 5.1.x, 6.1.x, 7.1.2/3. Now we have iOS 8.1. If that needs bigger improvements we must wait a year perhaps..... ouch!
    Not that Android will catch up really next year ;) I still don't understand why it's such a secret about those issues. 2 step forwards (hardware) but 3 steps back (software).

  • I see a lot of hysteria here, but do we actually have confirmation that there is a problem with the iPad Air 2? iOS 8's problems are well documented, but I'm curious if anything listed here is an issue specific to the new iPads. Thanks. My reading comprehension skills are slightly worse than my skills as a musician, so bear with me if it's already been detailed in the thread.

  • @boone51 said:

    I see a lot of hysteria here, but do we actually have confirmation that there is a problem with the iPad Air 2? iOS 8's problems are well documented, but I'm curious if anything listed here is an issue specific to the new iPads. Thanks. My reading comprehension skills are slightly worse than my skills as a musician, so bear with me if it's already been detailed in the thread.

    I don't believe that anyone is suggesting there is a problem with the iPad Air 2. The problem is with the software it's running -- iOS 8. Since iPad Air 2's come pre-installed with iOS8 and Apple is no longer signing iOS 7 installs, whatever problems you have with iOS 8 are going to carry-over to iPad Air 2's. I don't know that anyone thinks it's the hardware that's the issue.

  • @boone51, I don't think it's a hardware issue.

  • I suspect that because Apple added their pay system as part of iOS 8, they really had to crank down on their security. As a consequence some programming options that developers used before are not available. Since music is real time, it can be very demanding on computing resources so I would think that these low level security motivated changes may effect music apps more than other apps. It's also my understanding that the Audiobus developers (Michael) had to redo the underlying structure of Audiobus using an IAA framework. There are also some orientation of menus and apps when switching between apps.

    The strategy of documenting the screwy behaviors happening with music apps and passing it onto the developers and Apple might be a positive way to show what is happening. In the long run, it might be a way for Apple to reach out more to the user community and developers so that in the future these transitions will be less painful.

    When they've gotten to the point that they don't publish basic specs like ram on iOS devices when a significant proportion of their user base is interested in such information, it seems like they're out of touch.

    Being locked into a certain version of the iOS so everyone is one the same page was Steve Job's vision for iOS, but as the PC world and mobile device world continue to merge, I think this is no longer a viable option. Just like on PCs, people have invested in specific software and hardware setups and being able to choose when and how to upgrade/downgrade the iOS and apps is in their best interest and Apple's way of doing things currently really makes this difficult if not impossible for people to do so legally (terms of service agreements).

    With more powerful and expensive devices, people expect more and invest more. When there's a lack of adequate communication it is really a failure on the part of a company that's sold their product using the idea that the proprietary hardware and OS are made by the same company so "they just work". When they just stop working, people are going to be disappointed, angry, and feel betrayed.

  • edited October 2014

    If you jailbreak, is there a way to downgrade to iOS7.1.2 on an iPad Air 2? And if so, could you somehow install previous versions of apps? Then reverse the jailbreak once this is all fixed? I don't know jack about jailbreaking so please excuse me if these are stupid questions...

    Edit: Looks like you need blobs and shit, probably a no go for most people. http://www.ijailbreak.com/how-to-downgrade/

Sign In or Register to comment.