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.

D-1 Hybrid Synth from the AudioKit Team.

12729313233

Comments

  • @analog_matt said:
    Automation will be fixed

    Is the 'all IAP's free' offer still valid, or did I miss the boat? Serves me right if that was the case!

  • @EyeOhEss said:
    The length of time that this AU conversion took and the severity of the reported bugs (lost patches, broken automation...) give me bad vibes about the death of IAA...

    I reckon we’ll be lucky if even like 50% of devs have the motivation to follow along and convert IAA apps to AU...

    Guess it won’t matter cos there’ll be other new AU apps out by then. But still...

    Keep in mind that this started a Swift based app. Swift and AU have been problematic from the start so AudioKit is breaking new ground here that will benefit all future Swift based AU plugins.

  • @ExAsperis99 said:

    @Martinj said:
    First try at an ambient generative setup with D1 as AUv3....what a lovely way to spend my morning (iPad Air 2 running 3 instances and some effects)

    Nicely done, Martin.

    Thank you 😊

  • @EyeOhEss said:

    @espiegel123 said:

    @EyeOhEss said:
    The length of time that this AU conversion took and the severity of the reported bugs (lost patches, broken automation...) give me bad vibes about the death of IAA...

    I reckon we’ll be lucky if even like 50% of devs have the motivation to follow along and convert IAA apps to AU...

    Guess it won’t matter cos there’ll be other new AU apps out by then. But still...

    Keep in mind that deprecated APIs sometimes stick around for many years. Sometimes, they don't. I suspect that IAA will be around for a while since it is an obviously non-trivial task to convert IAA apps to AU.

    Fingers crossed 🤞

    I suspect that rate of adoption will have a big impact. There is code that Apple deprecated in 2004 that still runs (but won't in the next OS release which finally pulls support for all non-64 bit code)

  • @EyeOhEss said:

    @analog_matt said:
    Automation will be fixed

    Cool. Thinking about buying it in the sale but automations a must for me so hoping it won’t be months away? Do you have a rough ETA or is it likely to be a long wait?
    Thanks

    Could be a couple of days. Could be a couple of weeks. I don't have an ETA.

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

    @analog_matt said:
    Automation will be fixed

    Is the 'all IAP's free' offer still valid, or did I miss the boat? Serves me right if that was the case!

    IAPs currently listed as £0.00 in the App Store...

  • The user and all related content has been deleted.
  • edited July 2019

    Some info:

    As many of you know, AUv3 Plugins have a limitation where they can't directly access the data of a parent/standalone.

    You'll need to open the stand alone version first in the update (as the AUv3 instructs if you try to open it first). The standalone then attempts to create a shared folder that the AUv3 can see.

    I'd highly recommend exporting your Users/Custom presets when you open the Stand Alone the first time.

  • @espiegel123 said:

    @espiegel123 said:

    @analog_matt said:
    If folks can email their bugs to [email protected] (with as many details as possible) it will help us keep track and expedite the updates. 👍

    Matt, I've just sent an email with more details about this. But wanted to mention this here in case other people have run into this. A custom bank that I started in November is missing the 12 or so presets that I had created and put there. And my favorites list is also now empty.

    How do we import banks into D1? I found the json file for my bank in a recent iMazing backup and have put it on my iPad but when I choose import and choose the file, the bank doesn't import. If I tap on the bank in Files and try to Open In, Digital D1 isn't an option.

    If anyone else runs into this problem, it looks like D1 creates a folder in the iTunes File Sharing called Backup that contains a backup.

    If you rename the banks from something like
    "MyName.json" to "MyName.bank.json" then D1 should be able to import it using the "Import" button.

    You'll need to add a ".bank" before the ".json"

    Hope that is helpful. 🤞

  • edited July 2019
    The user and all related content has been deleted.
  • @MonzoPro said:

    @analog_matt said:
    Automation will be fixed

    Is the 'all IAP's free' offer still valid, or did I miss the boat? Serves me right if that was the case!

    "Platinum" mode offer has passed. But, there will still be some future free PCM updates

  • edited July 2019

    @EyeOhEss said:
    Might be worth adding something to the release notes with a warning for people that aren’t on the forum ;)

    Duh, man! 😋 The app notifies and instructs users. And, won't let them use the AUv3 until they do that.

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

    @analog_matt said:

    @EyeOhEss said:
    Might be worth adding something to the release notes with a warning for people that aren’t on the forum ;)

    Duh, man! 😋 The app notifies and instructs users. And, won't let them use the AUv3 until they do that.

    Haha :) nice one :) Surprised it’s an issue then!? Haha

    Haha. Well, you're right. The issue is that the file system between AUv3 and Standalone is still sketchy.
    TBH, I'm surprised AUv3 on iOS works as well as it does.

    Our next apps will start out as AUv3, and they shouldn't have this issue as much as apps that started out StandAlone and added AUv3 later...

  • @lukesleepwalker said:
    You probably think it's sheer coincidence that the AUv3 of D1 arrived on my birthday but I prefer to think that the heavens are smiling upon me. Thank you, @analog_matt and the whole D1 team!

    Happy birthday you ancient vestige of civility. Doubles all round!

  • @JohnnyGoodyear said:

    @lukesleepwalker said:
    You probably think it's sheer coincidence that the AUv3 of D1 arrived on my birthday but I prefer to think that the heavens are smiling upon me. Thank you, @analog_matt and the whole D1 team!

    Happy birthday you ancient vestige of civility. Doubles all round!

    Thank you kindly!

  • @analog_matt said:

    @espiegel123 said:

    @espiegel123 said:

    @analog_matt said:
    If folks can email their bugs to [email protected] (with as many details as possible) it will help us keep track and expedite the updates. 👍

    Matt, I've just sent an email with more details about this. But wanted to mention this here in case other people have run into this. A custom bank that I started in November is missing the 12 or so presets that I had created and put there. And my favorites list is also now empty.

    How do we import banks into D1? I found the json file for my bank in a recent iMazing backup and have put it on my iPad but when I choose import and choose the file, the bank doesn't import. If I tap on the bank in Files and try to Open In, Digital D1 isn't an option.

    If anyone else runs into this problem, it looks like D1 creates a folder in the iTunes File Sharing called Backup that contains a backup.

    If you rename the banks from something like
    "MyName.json" to "MyName.bank.json" then D1 should be able to import it using the "Import" button.

    You'll need to add a ".bank" before the ".json"

    Hope that is helpful. 🤞

    That worked!

  • @realdawei said:

    Keep in mind that this started a Swift based app. Swift and AU have been problematic from the start so AudioKit is breaking new ground here that will benefit all future Swift based AU plugins.

    Thank you. This is true. It's very difficult to make an AU in the native programming language Swift that Apple Recommends. We will be releasing source code later this month showing developers how they can make AUv3 Synths with Apple's tools.

  • @espiegel123 said:

    @analog_matt said:

    @espiegel123 said:

    @espiegel123 said:

    @analog_matt said:
    If folks can email their bugs to [email protected] (with as many details as possible) it will help us keep track and expedite the updates. 👍

    Matt, I've just sent an email with more details about this. But wanted to mention this here in case other people have run into this. A custom bank that I started in November is missing the 12 or so presets that I had created and put there. And my favorites list is also now empty.

    How do we import banks into D1? I found the json file for my bank in a recent iMazing backup and have put it on my iPad but when I choose import and choose the file, the bank doesn't import. If I tap on the bank in Files and try to Open In, Digital D1 isn't an option.

    If anyone else runs into this problem, it looks like D1 creates a folder in the iTunes File Sharing called Backup that contains a backup.

    If you rename the banks from something like
    "MyName.json" to "MyName.bank.json" then D1 should be able to import it using the "Import" button.

    You'll need to add a ".bank" before the ".json"

    Hope that is helpful. 🤞

    That worked!

  • edited July 2019

    I’m crushed, its not working at all for me in NanoStudio 2. It completely crashes the app. iPad Pro 2017 12.9. iOS 11.4.1 (I really don’t wanna update). I launched d1 standalone first, then tried uninstalling and reinstalling d1 and still no luck, any ideas?

  • Oh sorry.

    iPad Pro 11 inch latest iOS not beta Pad os
    Latest version of D1.

    AUM and aMatrix are not able to use their onboard keyboards with it. And on AUM as i Said fugue machines midi was not recieved by D1

    I am super sure this will be sorted out ;)

    @espiegel123 said:

    @david_2017 said:
    Hmmm mine is not responding to midi. AUM keyboard, fugue machine...

    But thanks for the update! Awesome to have D1 as a plugin 💪🏼Au<3 yeah!

    What OS, etc

  • @david_2017 said:
    Oh sorry.

    iPad Pro 11 inch latest iOS not beta Pad os
    Latest version of D1.

    AUM and aMatrix are not able to use their onboard keyboards with it. And on AUM as i Said fugue machines midi was not recieved by D1

    I am super sure this will be sorted out ;)

    @espiegel123 said:

    @david_2017 said:
    Hmmm mine is not responding to midi. AUM keyboard, fugue machine...

    But thanks for the update! Awesome to have D1 as a plugin 💪🏼Au<3 yeah!

    What OS, etc

    Working fine in AUM with its keyboard for me in 12.3.1 on iPad 6th gen. If you haven't, try shutting down your iPad (complete power off and not just sleep).

  • @david_2017 said:
    AUM and aMatrix are not able to use their onboard keyboards with it. And on AUM as i Said fugue machines midi was not recieved by D1

    Did you check D1's MIDI channel settings?

  • We pushed an update that will help MIDI tremendously. Now waiting for Apple's approval.

    Thanks everyone for your patience. And, thanks especially to those that sent detailed bug reports. We're committed to keep improving D1 ASAP!!!

  • @analog_matt said:
    We pushed an update that will help MIDI tremendously. Now waiting for Apple's approval.

    Thanks everyone for your patience. And, thanks especially to those that sent detailed bug reports. We're committed to keep improving D1 ASAP!!!

    Hey @analog_matt I don’t know if you saw my prior post:

    @ipadbeatmaking said:
    I’m crushed, its not working at all for me in NanoStudio 2. It completely crashes the app. iPad Pro 2017 12.9. iOS 11.4.1 (I really don’t wanna update). I launched d1 standalone first, then tried uninstalling and reinstalling d1 and still no luck, any ideas?

  • Oh Boy this is embarrassing... i checked it and saw it’s sending on Ch5 I was expecting Ch1 and/or Omni - I add synths in AUM, connect midi on screen keybaord and start playing. It’s now working as expected. Thanks for the tip🙈

    @jipumarino said:

    @david_2017 said:
    AUM and aMatrix are not able to use their onboard keyboards with it. And on AUM as i Said fugue machines midi was not recieved by D1

    Did you check D1's MIDI channel settings?

  • @david_2017 said:
    Oh Boy this is embarrassing... i checked it and saw it’s sending on Ch5 I was expecting Ch1 and/or Omni - I add synths in AUM, connect midi on screen keybaord and start playing. It’s now working as expected. Thanks for the tip🙈

    I'm glad it worked. Same thing happened to me because I always ran it on channel 8 while it was standalone. No need for that now :)

  • Thank you for such an awesome Synth!!!

  • Hey @analog_matt I don’t know if you saw my prior post:

    @ipadbeatmaking said:
    I’m crushed, its not working at all for me in NanoStudio 2. It completely crashes the app. iPad Pro 2017 12.9. iOS 11.4.1 (I really don’t wanna update). I launched d1 standalone first, then tried uninstalling and reinstalling d1 and still no luck, any ideas?

    That's a super bummer, we've been working with Matt @ NS2. Looks like we might have to get his assistance some more to see what's going on. If you'd like to help, feel free to email me directly: [email protected]

    Thanks for letting us know. I want to get it working for you in NS2 as well!

Sign In or Register to comment.