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.

Nanostudio 2 removed from app store? (Solved)

1356

Comments

  • The user and all related content has been deleted.
  • edited January 2023

    @tja said:

    @jwmmakerofmusic said:
    "AUv3 over Audio Tracks is a fail"? I made this in NS2 without audio tracks, and the original artist was pleased and released it.

    Just to repeat this, I did not say this - I was wrongly remembering that the iPhone version was done before and over audio tracks. And this would have been an epic fail for me.

    AUv3 host vs audio tracks is a much more difficult question 😉

    Then again, I would make the argument that while FLSM has audio tracks, it lacks AUv3, and lots of folks have written it off (myself included in the past) because of lack of AUv3 compatibility. Of course Imageline are working hard now to implement AUv3 into FLSM, and it's not "too little, too late" as I enjoy making Lofi and such in FLSM. In many ways, I could live without NS2 once FLSM can host PSP2, Saga, VHS, etc. And being on the beta team does have its advantages to squash bugs and make sure things are running as smooth as possible.

    EDIT: My point in all that blather is - I enjoy NS2 because I can use AUv3 smoothly and enjoy a great piano roll. FLSM's piano roll is my other favourite. Never dove into AEM before, and I might give it a whirl on my next EP.

  • I believe it’s a case of Apple pulling it out because the lack of updates. I got an email from them on an older app of mine and they pulled it out although it was fully functional

  • The user and all related content has been deleted.
  • @tja said:

    @alecsbuga said:
    I believe it’s a case of Apple pulling it out because the lack of updates. I got an email from them on an older app of mine and they pulled it out although it was fully functional

    Apple is a bunch of creepy idiots.

    Yeah. I have a calorie counter app which I built mainly for myself when I lost weight. Haven’t updated in 5 yrs. Suddenly on dec 31 it got 200 downloads. Apple sent me an email threatening to close my account because I forged downloads :) mind blowing

  • @tja said:

    @anickt said:

    @tja said:
    iPhone version over audio tracks was an epic fail.

    If Matt had followed the original roadmap, he wouldn’t have gotten bogged down adding AUv3 which is what killed the project. iPhone version was not an issue.

    Ah, Ok.
    I remembered this wrongly ... second time already

    Thanks for the correction!
    Need to store this :-)

    As I remember it wasn’t specifically an issue with adding AUv3 support but with the fact that Matt implemented it “by the book” which exposed issues with existing AU’s that were not “by the book”.

    I remember reading that he spent a lot of time helping other devs correct these issues which apparently was taking too much of his time. That along with slower than expected sales shut things down.

    This is all as I remember it but also at one point I went back through emails on the NS forum which pretty much confirmed what I remembered.

    Now I just want to get my audio tracks and forget all the rest! 😭

  • @alecsbuga said:
    I believe it’s a case of Apple pulling it out because the lack of updates. I got an email from them on an older app of mine and they pulled it out although it was fully functional

    Yah it is pretty sad. Even if if you have a simple app that is selling IAP, if you don't update the executable they will eventually kill it.

  • @AudioGus said:

    @alecsbuga said:
    I believe it’s a case of Apple pulling it out because the lack of updates. I got an email from them on an older app of mine and they pulled it out although it was fully functional

    Yah it is pretty sad. Even if if you have a simple app that is selling IAP, if you don't update the executable they will eventually kill it.

    I wonder how it really works; I have a single app for sale at $0.99, and haven't updated it in 5 years. I have not received any takedown notices.

  • edited January 2023

    @jwmmakerofmusic said:

    @tja said:

    @jwmmakerofmusic said:
    "AUv3 over Audio Tracks is a fail"? I made this in NS2 without audio tracks, and the original artist was pleased and released it.

    Just to repeat this, I did not say this - I was wrongly remembering that the iPhone version was done before and over audio tracks. And this would have been an epic fail for me.

    AUv3 host vs audio tracks is a much more difficult question 😉

    Then again, I would make the argument that while FLSM has audio tracks, it lacks AUv3, and lots of folks have written it off (myself included in the past) because of lack of AUv3 compatibility. Of course Imageline are working hard now to implement AUv3 into FLSM, and it's not "too little, too late" as I enjoy making Lofi and such in FLSM. In many ways, I could live without NS2 once FLSM can host PSP2, Saga, VHS, etc. And being on the beta team does have its advantages to squash bugs and make sure things are running as smooth as possible.

    EDIT: My point in all that blather is - I enjoy NS2 because I can use AUv3 smoothly and enjoy a great piano roll. FLSM's piano roll is my other favourite. Never dove into AEM before, and I might give it a whirl on my next EP.

    Like so often with DAWs, features are a very personal thing and there's no right or wrong.
    When the audio tracks vs AUv3 discussion was still hot on the blip forum, AUv3s weren't yet as relevant as they are now and if I had to choose again, it would still be AUv3 over audio tracks without a doubt.
    I'm used to record and arrange audio in MPC style so dedicated audio tracks wouldn't make much of a difference to me, even if that would include free routing between tracks and instrument track freezing.

  • What is going on?! It's still not in the store. Any explanation anyone?

  • @anickt said:
    I used it for something the other day. IMHO it’s still the best DAW on iOS other than the omission of audio tracks. We’ll see where it’s going! 😎👍🏼

    Amen.
    I don't think the app is disappearing. It is bringing money for the dev ;)

  • @Grandbear said:

    @AudioGus said:

    @alecsbuga said:
    I believe it’s a case of Apple pulling it out because the lack of updates. I got an email from them on an older app of mine and they pulled it out although it was fully functional

    Yah it is pretty sad. Even if if you have a simple app that is selling IAP, if you don't update the executable they will eventually kill it.

    I wonder how it really works; I have a single app for sale at $0.99, and haven't updated it in 5 years. I have not received any takedown notices.

    Interesting! I am working on an app that was last updated two years ago and Apple told us get on it now and we have a real deadline to update it or it is toast. Who knows it could be related to price/market/popularity/size etc. I wager they have some algorithm for who to bug.

  • @AudioGus said:

    @Grandbear said:

    @AudioGus said:

    @alecsbuga said:
    I believe it’s a case of Apple pulling it out because the lack of updates. I got an email from them on an older app of mine and they pulled it out although it was fully functional

    Yah it is pretty sad. Even if if you have a simple app that is selling IAP, if you don't update the executable they will eventually kill it.

    I wonder how it really works; I have a single app for sale at $0.99, and haven't updated it in 5 years. I have not received any takedown notices.

    Interesting! I am working on an app that was last updated two years ago and Apple told us get on it now and we have a real deadline to update it or it is toast. Who knows it could be related to price/market/popularity/size etc. I wager they have some algorithm for who to bug.

    I think it's security related. They prob. want them to be built with the latest SDKs.

  • edited January 2023

    I think in this thread is everything what is bad about iOS for music production.

    1. The need to rely on software that suddenly can become unavailable
    2. A popular DAW that hasn’t been updated for years
    3. Indie dev DAWs not delivering professional features like audio tracks, multi-core rendering, etc.
    4. Apple being the gatekeeper for what you can install on your device.
    5. Apple taking down apps although they are still working with the latest OS and customers paid for them
    6. Apple‘s behavior often being arbitrarily and intransparent for developers
    7. The need to use 3rd party tools that use undocumented procedures to backup your applications

    On top of all that it is rather unlikely that you get refunded if these troubles happen to you. We all must be mad. But I must admit that it’s such a fun to make music on my iPad that I don’t care.

  • Looks like my musical task list has been re-ordered. Item 1: Export all Nanostudio projects!

    Do hope it’s not dead though.

  • This is very worrying, fingers crossed there's a simple explanation and a quick fix

  • @tja said:

    @OnfraySin said:

    @tja said:
    iPhone version over audio tracks was an epic fail.

    The ultra overhype from betatesters was the epic fail

    Hmm.
    Why?

    The hype is true and valid, I think.
    Only we are missing audio tracks ;-)

    And i need to rephrase my sentence:

    AUv3 host over audio tracks was an epic fail, as this was the alternative.

    But then, I can understand that this question is difficult.
    NS2 would be much less attractive without being an AU host... do audio tracks out-weight this?

    It was so irritant from betatesters the "this is magic, this is THE game changer, this is perfect, the problem is the user, you're a fool if don't understand NS2 features, blablablablablabla" moto

    And I suspect that Matt was swayed by this opinion.

  • @krassmann said:
    I think in this thread is everything what is bad about iOS for music production.

    1. The need to rely on software that suddenly can become unavailable
    2. A popular DAW that hasn’t been updated for years
    3. Indie dev DAWs not delivering professional features like audio tracks, multi-core rendering, etc.
    4. Apple being the gatekeeper for what you can install on your device.
    5. Apple taking down apps although they are still working with the latest OS and customers paid for them
    6. Apple‘s behavior often being arbitrarily and intransparent for developers
    7. The need to use 3rd party tools that use undocumented procedures to backup your applications

    On top of all that it is rather unlikely that you get refunded if these troubles happen to you. We all must be mad. But I must admit that it’s such a fun to make music on my iPad that I don’t care.

    This post is a perfect illustration of why I would like to have a like button on this forum. 👍

  • edited January 2023

    @AudioGus
    Interesting! I am working on an app that was last updated two years ago and Apple told us get on it now and we have a real deadline to update it or it is toast. Who knows it could be related to price/market/popularity/size etc. I wager they have some algorithm for who to bug.

    @alecsbuga
    Yeah. I have a calorie counter app which I built mainly for myself when I lost weight. Haven’t updated in 5 yrs. Suddenly on dec 31 it got 200 downloads. Apple sent me an email threatening to close my account because I forged downloads :) mind blowing

    Unfortunately, Apple evolved into incredibly retarded company ... instead of supporting developers and making their life easier, they are hard working on making developers life more complicated ..

  • @OnfraySin said:

    @tja said:

    @OnfraySin said:

    @tja said:
    iPhone version over audio tracks was an epic fail.

    The ultra overhype from betatesters was the epic fail

    Hmm.
    Why?

    The hype is true and valid, I think.
    Only we are missing audio tracks ;-)

    And i need to rephrase my sentence:

    AUv3 host over audio tracks was an epic fail, as this was the alternative.

    But then, I can understand that this question is difficult.
    NS2 would be much less attractive without being an AU host... do audio tracks out-weight this?

    It was so irritant from betatesters the "this is magic, this is THE game changer, this is perfect, the problem is the user, you're a fool if don't understand NS2 features, blablablablablabla" moto

    And I suspect that Matt was swayed by this opinion.

    So often things go this way with beta testers. Frustrating for sure.

  • edited January 2023

    @BroCoast
    So often things go this way with beta testers. Frustrating for sure.

    I can ensure you this was not the case with NS. Regarding me i was always more for finishing audio tracks with highest priority , before iPhone version. I was even doubting priority of AUv3 support before audio tracks ... Matt has always strong vision about where he wants move his app, what features move forward in priority list, he was listening to our opinions but at the end he always decided on his own. And even through he wasn't that active here, be sure he always did read all people opinions on forums. It's really not fair call him like he was some kind of puppet influenced by beta team - this was absolutely not the case.

  • @dendy said:

    @BroCoast
    So often things go this way with beta testers. Frustrating for sure.

    I can ensure you this was not the case with NS. Regarding me i was always more for finishing audio tracks with highest priority , before iPhone version. I was even doubting priority of AUv3 support before audio tracks ... Matt has always strong vision about where he wants move his app, what features move forward in priority list, he was listening to our opinions but at the end he always decided on his own. And even through he wasn't that active here, be sure he always did read all people opinions on forums. It's really not fair call him like he was some kind of puppet influenced by beta team - this was absolutely not the case.

    It’s nice to hear from someone who was “there” and is not just guessing. Thanks @dendy

  • @ervin said:

    @krassmann said:
    I think in this thread is everything what is bad about iOS for music production.

    1. The need to rely on software that suddenly can become unavailable
    2. A popular DAW that hasn’t been updated for years
    3. Indie dev DAWs not delivering professional features like audio tracks, multi-core rendering, etc.
    4. Apple being the gatekeeper for what you can install on your device.
    5. Apple taking down apps although they are still working with the latest OS and customers paid for them
    6. Apple‘s behavior often being arbitrarily and intransparent for developers
    7. The need to use 3rd party tools that use undocumented procedures to backup your applications

    On top of all that it is rather unlikely that you get refunded if these troubles happen to you. We all must be mad. But I must admit that it’s such a fun to make music on my iPad that I don’t care.

    This post is a perfect illustration of why I would like to have a like button on this forum. 👍

    Yes, I think it's an indication of why allowing developers and users to have more options is going to be a good thing :)

  • @dendy said:

    @BroCoast
    So often things go this way with beta testers. Frustrating for sure.

    I can ensure you this was not the case with NS. Regarding me i was always more for finishing audio tracks with highest priority , before iPhone version. I was even doubting priority of AUv3 support before audio tracks ... Matt has always strong vision about where he wants move his app, what features move forward in priority list, he was listening to our opinions but at the end he always decided on his own. And even through he wasn't that active here, be sure he always did read all people opinions on forums. It's really not fair call him like he was some kind of puppet influenced by beta team - this was absolutely not the case.

    I understand and did not mean to imply it was the case. Just that a few apps with great potential went in the wrong direction due to bad advice from beta testers.

    NS2 was/is pretty brilliant.

  • @OnfraySin said:
    It was so irritant from betatesters the "this is magic, this is THE game changer, this is perfect, the problem is the user, you're a fool if don't understand NS2 features, blablablablablabla" moto

    All true though.

  • Not even showing in purchased apps any more.

  • Please secure Drambo!!!...in some way!

  • edited January 2023

    @BroCoast said:

    @dendy said:

    @BroCoast
    So often things go this way with beta testers. Frustrating for sure.

    I can ensure you this was not the case with NS. Regarding me i was always more for finishing audio tracks with highest priority , before iPhone version. I was even doubting priority of AUv3 support before audio tracks ... Matt has always strong vision about where he wants move his app, what features move forward in priority list, he was listening to our opinions but at the end he always decided on his own. And even through he wasn't that active here, be sure he always did read all people opinions on forums. It's really not fair call him like he was some kind of puppet influenced by beta team - this was absolutely not the case.

    I understand and did not mean to imply it was the case. Just that a few apps with great potential went in the wrong direction due to bad advice from beta testers.

    NS2 was/is pretty brilliant.

    I agree that more often than not beta testers tend to ask for more and more features which lead to over complication of the original design from the developer. The best beta testers just find bugs.

  • Word of warning to the not so wise - I backed up NS2 from my ipad, restored it to my iphone, which is now in a state of redownloading every app I had installed and has forgotten much of my data, jeez what a silly palaver...

  • Update from Matt today at 1.15pm

    There seems to be a problem with Blip's Apple Developer licence which means that NS2 has temporarily been removed from the App Store.

    I'm trying to sort out the problem now and things should be back to normal once Apple has processed the application. Apologies for the inconvenience.

    Thanks to those of you who let me know via the contact form!

    Cheers

    Matt

Sign In or Register to comment.