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.

Auria Pro Update 2.30

The user and all related content has been deleted.
«1

Comments

  • Boom! thanks!

  • Very happy to see Auria Pro updated! I haven’t checked anything yet but I’m glad to see this get some love.

  • @NoiseHorse said:
    Very happy to see Auria Pro updated! I haven’t checked anything yet but I’m glad to see this get some love.

    So am I.

    When I need a good solid DAW this is my go to.

  • Wow ! Happy to see the update landing 🥳.
    I can't wait to try it out.

  • I´we alway tried to love Auira, due to the plugin delay compensation but on my IPAD it has always been quite buggy Hope it has gotten more stabile. Cubasis 3 is pretty perfect for me, but the lack of Plugin delay compensation is just such a bummer, so Auria will always be lurking in the back of my mind....

  • I have not done extensive testing but so far it seems good. That non critical crash when project opened seems to be gone.

  • edited May 2021

    I purchased it in the past and use it regularly. When I saw this message, I went to the App Store. There were two Auria Pros, one appeared to be the one I had with an Update button. The other showed a purchase price of $24.99USD. Are they different?

    They sure look the same. The version history shows them both at 2.30. If they are the same, I wonder how many refunds they'll have to process because folks think this is a new paid version?

  • One is for people who had version 1, it’s just an upgrade.

  • @motmeister said:
    I purchased it in the past and use it regularly. When I saw this message, I went to the App Store. There were two Auria Pros, one appeared to be the one I had with an Update button. The other showed a purchase price of $24.99USD. Are they different?

    They sure look the same. The version history shows them both at 2.30. If they are the same, I wonder how many refunds they'll have to process because folks think this is a new paid version?

    Perhaps you saw Auria (audio only version) which is $24.99 and Auria Pro?

  • I was doing some testing last night to see what might have changed. I seem to recall needing to route a track with Atom in its channel strip to a second instrument track in order to hear the Atom notes. Now I can host Atom with the instrument track and use it as a direct piano roll replacement. MIDI chaining within the channel strip also works well enough to accurately record between plugins and do Atom pattern switching.

    I still can’t route an Atom in the channel strip to the input of another Atom on a different track channel strip so still need MIDI Bus. Mixdown with Atom in the MIDI chain still hangs. Still cannot accurately print the output of Atom to the hosted track piano roll. Now that everything else seems to be running pretty well I think I’ll take the time at some point to report these on the Auria forum.

  • If anyone can make a video of MIDI processors working within Auria it would be much appreciated.I must be doing something wrong. Thanks in Advance😊

  • edited May 2021

    Has MIDI note entry with an Apple Pencil been improved yet? When I last tried it a while back, behaviour was not as you would expect in terms of how this worked with entry and editing with the Pencil, unlike Cubasis.

  • Audio is Auria’s strength. For doing midi stuff your are probably better of in another DAW. (NS2. CB3)

  • @Gasman50 said:
    If anyone can make a video of MIDI processors working within Auria it would be much appreciated.I must be doing something wrong. Thanks in Advance😊

    Here is a screengrab example of running Atom 2 as a MIDI generator:

    You select the plugin from the channel strip as the input and the output goes to the instrument for that track. What sort of processor were you thinking of using? Things like Mozaic and StreamByter should work in the same way.

    If you are lucky then you should also be able to record the output of the MIDI from plugins in the chain directly to the piano roll. Some however, such as Atom, need a workaround by sending them using the MIDI Route tool to a different track as the notes do not record correctly.

  • @Gasman50 said:
    If anyone can make a video of MIDI processors working within Auria it would be much appreciated.I must be doing something wrong. Thanks in Advance😊

    It might be easier for us to see why your setup isn't working if you post screenshots of you setup. The previous version had a bug that caused s channel's audio not to play if there was a MIDI plugin in the effect chain which has been fixed.

  • @MisplacedDevelopment said:

    @Gasman50 said:
    If anyone can make a video of MIDI processors working within Auria it would be much appreciated.I must be doing something wrong. Thanks in Advance😊

    Here is a screengrab example of running Atom 2 as a MIDI generator:

    You select the plugin from the channel strip as the input and the output goes to the instrument for that track. What sort of processor were you thinking of using? Things like Mozaic and StreamByter should work in the same way.

    If you are lucky then you should also be able to record the output of the MIDI from plugins in the chain directly to the piano roll. Some however, such as Atom, need a workaround by sending them using the MIDI Route tool to a different track as the notes do not record correctly.

    What goes wrong if you try to record from Atom to the internal piano roll?

    Please report to Auria's developer. You might also see if he will add you to the beta list. I think the beta list is light on people doing much with MIDI

  • @ecou said:
    I have not done extensive testing but so far it seems good. That non critical crash when project opened seems to be gone.

    Well I spoke to fast. The non critical crash at project opening is back.

  • edited May 2021

    @espiegel123 said:

    What goes wrong if you try to record from Atom to the internal piano roll?

    Please report to Auria's developer. You might also see if he will add you to the beta list. I think the beta list is light on people doing much with MIDI

    Here is what it looks like when recording directly:

    Edit: just noticed the missing note is actually missing from the next beat but the point stands :)

    Here is what it looks like when sent to another track using MIDI Route:

    The initial note is missing and the timing is off but it does at least record something. Adding an empty copy of Atom to the destination channel strip causes all of the notes to be recorded correctly, which is odd.

    I will create an account on the Auria forum now and report the issues as the team appear to be giving Auria a bit of love at the moment.

  • @MisplacedDevelopment said:

    @espiegel123 said:

    What goes wrong if you try to record from Atom to the internal piano roll?

    Please report to Auria's developer. You might also see if he will add you to the beta list. I think the beta list is light on people doing much with MIDI

    Here is what it looks like when recording directly:

    Here is what it looks like when sent to another track using MIDI Route:

    The initial note is missing and the timing is off but it does at least record something.

    I will create an account on the Auria forum now and report the issues as the team appear to be giving Auria a bit of love at the moment.

    I just did a little testing and the problem is that Auria is not correctly treating midi note on with velocity 0 as a note off when recording to the piano roll from MIDU Aus. As a workaround till they fix it, you can use a mozaic script that sends out a midi note off when a midi note off is received.

    i've reported that issue to them.

  • @espiegel123 said:

    I just did a little testing and the problem is that Auria is not correctly treating midi note on with velocity 0 as a note off when recording to the piano roll from MIDU Aus. As a workaround till they fix it, you can use a mozaic script that sends out a midi note off when a midi note off is received.

    i've reported that issue to them.

    Wow, thanks for that! I will take a look at that workaround. Thank you as well for reporting it. I have registered for an account on the forum but it looks like a manual acceptance process so may need to wait a while.

  • @MisplacedDevelopment said:

    @espiegel123 said:

    I just did a little testing and the problem is that Auria is not correctly treating midi note on with velocity 0 as a note off when recording to the piano roll from MIDU Aus. As a workaround till they fix it, you can use a mozaic script that sends out a midi note off when a midi note off is received.

    i've reported that issue to them.

    Wow, thanks for that! I will take a look at that workaround. Thank you as well for reporting it. I have registered for an account on the forum but it looks like a manual acceptance process so may need to wait a while.

    if you have streambyter, a one line script would do the trick, too.

  • edited May 2021

    @espiegel123 Works like a charm, thanks again :)

  • 2.3 used 43% battery last night and the app was closed. Anyone else?

  • @Ailerom said:
    2.3 used 43% battery last night and the app was closed. Anyone else?

    Are you sure it was closed as in force-closed by swiping up on the app in the task switcher, or just put into the background by returning to the home screen?

    Even if it was force-closed, it's definitely possible for apps to leave "ghost" processes that suck your battery down. This can happen with any IAA app or app that hosts IAAs, not just Auria Pro.

    If your device has a home button it's very easy to reset RAM and clear out ghost processes without a reboot. Force close all apps, then from the home screen hold down the power button until the power-off slider comes up, but don't slide it. Instead, hold down the home button until returned to the password lock screen.

    Without a home button it's a bit more involved, but still worth it. Resetting RAM after ever music session avoids tons of problems.

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

    @motmeister said:
    I purchased it in the past and use it regularly. When I saw this message, I went to the App Store. There were two Auria Pros, one appeared to be the one I had with an Update button. The other showed a purchase price of $24.99USD. Are they different?

    They sure look the same. The version history shows them both at 2.30. If they are the same, I wonder how many refunds they'll have to process because folks think this is a new paid version?

    Perhaps you saw Auria (audio only version) which is $24.99 and Auria Pro?

    Yes. So the purchase one is Auria, not Auria Pro, which I owned. Still, I think that will confuse some.

  • @wim said:

    @Ailerom said:
    2.3 used 43% battery last night and the app was closed. Anyone else?

    Are you sure it was closed as in force-closed by swiping up on the app in the task switcher, or just put into the background by returning to the home screen?

    Even if it was force-closed, it's definitely possible for apps to leave "ghost" processes that suck your battery down. This can happen with any IAA app or app that hosts IAAs, not just Auria Pro.

    If your device has a home button it's very easy to reset RAM and clear out ghost processes without a reboot. Force close all apps, then from the home screen hold down the power button until the power-off slider comes up, but don't slide it. Instead, hold down the home button until returned to the password lock screen.

    Without a home button it's a bit more involved, but still worth it. Resetting RAM after ever music session avoids tons of problems.

    Yes, definitely closed. I updated it to 2.3, installed the rock drum kit for the sampler (Lyra or something), had a kit jam and closed it. 8 hours later, sleeping ipad. AP was open for 4 minutes. never experienced this before but will use your method. Hoping it is a bug that will be fixed though.

    Was just thinking about using it a little more but not if it is like this.

  • @tja said:

    @Ailerom said:
    2.3 used 43% battery last night and the app was closed. Anyone else?

    Classical problem of a hanging IAA App.
    Did you load something like this?

    Nope, only the internal AP sampler.

  • wimwim
    edited May 2021

    @Ailerom said:

    @wim said:

    @Ailerom said:
    2.3 used 43% battery last night and the app was closed. Anyone else?

    Are you sure it was closed as in force-closed by swiping up on the app in the task switcher, or just put into the background by returning to the home screen?

    Even if it was force-closed, it's definitely possible for apps to leave "ghost" processes that suck your battery down. This can happen with any IAA app or app that hosts IAAs, not just Auria Pro.

    If your device has a home button it's very easy to reset RAM and clear out ghost processes without a reboot. Force close all apps, then from the home screen hold down the power button until the power-off slider comes up, but don't slide it. Instead, hold down the home button until returned to the password lock screen.

    Without a home button it's a bit more involved, but still worth it. Resetting RAM after ever music session avoids tons of problems.

    Yes, definitely closed. I updated it to 2.3, installed the rock drum kit for the sampler (Lyra or something), had a kit jam and closed it. 8 hours later, sleeping ipad. AP was open for 4 minutes. never experienced this before but will use your method. Hoping it is a bug that will be fixed though.

    Was just thinking about using it a little more but not if it is like this.

    I doubt very much it's an Auria Pro specific bug. More likely it's iOS at fault. I don't think there is anything an app can do if iOS doesn't release processes when an app is force closed.

    I'm assuming when you say "closed" it, you mean that you brought up all the running apps and then swiped up to get rid of Auria Pro from there. If you didn't do specifically that then you didn't really "close" it.

  • @Ailerom said:
    2.3 used 43% battery last night and the app was closed. Anyone else?

    No problems here with battery or the app not really quitting when force-quit.

    Did you launch Auria directly (by tapping its icon) or indirectly via AUM of Audiobus?

Sign In or Register to comment.