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.

Audio Evolution Mobile Studio

13840424344

Comments

  • The darker interface for midi edit is great. As is the multi instrument drum sequencer. As is the select all button. Brilliant! Thanks.

  • @Cambler said:
    Kudos @dwrae ! Just a note that I just had a quick play on my iPhone and loaded an auv3 synth and it’s invisible. I say invisible as touch interactions still seem to work (ie. I can hear the synth when I blindly waggle my fingers over the screen!). I don’t usually use iPhone for production but had it near me and wanted to check out the update. Will test the iPad in a second.

    Also I tried a restart of the phone as well but no difference.

    Edit: actually it’s the AEM keyboard that’s invisible. Sorry I’m not versed in the iPhone version and it seems one needs to click the AU button on the top left to make the plugin interface visible.

    Thanks for reporting this. Found and fixed. Version 6.7.4 is submitted for review.

  • @dwrae said:

    @Cambler said:
    Kudos @dwrae ! Just a note that I just had a quick play on my iPhone and loaded an auv3 synth and it’s invisible. I say invisible as touch interactions still seem to work (ie. I can hear the synth when I blindly waggle my fingers over the screen!). I don’t usually use iPhone for production but had it near me and wanted to check out the update. Will test the iPad in a second.

    Also I tried a restart of the phone as well but no difference.

    Edit: actually it’s the AEM keyboard that’s invisible. Sorry I’m not versed in the iPhone version and it seems one needs to click the AU button on the top left to make the plugin interface visible.

    Thanks for reporting this. Found and fixed. Version 6.7.4 is submitted for review.

    Thank you for the excellent update!

  • What is the name of the new Drum pack IAP?

  • @NoiseHorse said:
    What is the name of the new Drum pack IAP?

    Ehm.. please create a drum pattern track, select Multi-instrument, Ok, then you are asked to download the free pack. Then press the instrument button for a drum lane and collapse/open the tree view to Samples. You will see the option there to 'Purchase the drum sounds pack'. It doesn't really have a name.



  • @dwrae wow brilliant new update Thanks for all your work on this excellent DAW
    If possible can you fix saved internel fx presets and au presets are not saving in alphabetical order
    Cheers

  • edited January 2025

    I noticed that if you change page when playing a keyboard note on screen the note will became stuck

    also the BPM dialog brings up the whole keyboard, can you make it numeric at least?

  • @stormbeats said:


    @dwrae wow brilliant new update Thanks for all your work on this excellent DAW
    If possible can you fix saved internel fx presets and au presets are not saving in alphabetical order
    Cheers

    Solved, thanks!

  • @cokomairena said:
    I noticed that if you change page when playing a keyboard note on screen the note will became stuck

    Ah, thanks, solved.

    also the BPM dialog brings up the whole keyboard, can you make it numeric at least?

    There were problems in the past with JUCE and keyboard displays. The comment in the code I once wrote was concerning iPhones and not being able to leave the keyboard display, but I tested it on 3 iPhones now and it seems to work. It will bring up the whole keyboard though, but switched to numeric.

  • @dwrae said:

    @stormbeats said:


    @dwrae wow brilliant new update Thanks for all your work on this excellent DAW
    If possible can you fix saved internel fx presets and au presets are not saving in alphabetical order
    Cheers

    Solved, thanks!

    @dwrae thanks :)

  • @dwrae said:

    @cokomairena said:
    I noticed that if you change page when playing a keyboard note on screen the note will became stuck

    Ah, thanks, solved.

    also the BPM dialog brings up the whole keyboard, can you make it numeric at least?

    There were problems in the past with JUCE and keyboard displays. The comment in the code I once wrote was concerning iPhones and not being able to leave the keyboard display, but I tested it on 3 iPhones now and it seems to work. It will bring up the whole keyboard though, but switched to numeric.

    that's better, if you could select the bpm so I could directly write what I want would be even better. Of course the ideal would be a something to drag

  • @dwrae hi I just updated to latest update 6.7.4 . Trying to work out what’s been updated from 6.7.3?

  • @stormbeats said:
    @dwrae hi I just updated to latest update 6.7.4 . Trying to work out what’s been updated from 6.7.3?

    The AUv3 display bug for iPhones that was reported earlier.

  • @dwrae said:

    @stormbeats said:
    @dwrae hi I just updated to latest update 6.7.4 . Trying to work out what’s been updated from 6.7.3?

    The AUv3 display bug for iPhones that was reported earlier.

    @dwrae ok thanks

  • edited January 2025

    Thanks for the iPhone fix @dwrae . Also did you see my post above in regards to auv3's on Apple Silicon desktop?

    Initially it seemed as if auv3's (synths, fx etc) on desktop were not able to be edited (trying to alter knobs and values seemed to do nothing). Had a bit more of a play and it seems that the active area for each knob etc is offset, eg, clicking and dragging a few centimetres or more to the left of knob affects it. To be more precise it's actually about an inch to the left and half an inch up.

  • @Cambler said:
    Thanks for the iPhone fix @dwrae . Also did you see my post above in regards to auv3's on Apple Silicon desktop?

    Initially it seemed as if auv3's (synths, fx etc) on desktop were not able to be edited (trying to alter knobs and values seemed to do nothing). Had a bit more of a play and it seems that the active area for each knob etc is offset, eg, clicking and dragging a few centimetres or more to the left of knob affects it. To be more precise it's actually about an inch to the left and half an inch up.

    I have a Mac Mini M2 Pro and did not experience and offset when using two AU instruments. I have heard of this problem before with 1 Android user where JUCE did not initialise the screen width/height correctly. I solved that problem, but that code is not relevant for iOS unfortunately. Did you perhaps resize the dialog?

  • edited January 2025

    @dwrae said:

    @Cambler said:
    Thanks for the iPhone fix @dwrae . Also did you see my post above in regards to auv3's on Apple Silicon desktop?

    Initially it seemed as if auv3's (synths, fx etc) on desktop were not able to be edited (trying to alter knobs and values seemed to do nothing). Had a bit more of a play and it seems that the active area for each knob etc is offset, eg, clicking and dragging a few centimetres or more to the left of knob affects it. To be more precise it's actually about an inch to the left and half an inch up.

    I have a Mac Mini M2 Pro and did not experience and offset when using two AU instruments. I have heard of this problem before with 1 Android user where JUCE did not initialise the screen width/height correctly. I solved that problem, but that code is not relevant for iOS unfortunately. Did you perhaps resize the dialog?

    Thanks for getting back to me on this. No I haven’t resized the dialog box, it’s just as it is when I open it. This is on a MacBook Air M1. I also have an M4 Mini so will try it on that next to see if it’s specific to the laptop.

  • @Cambler said:

    @dwrae said:

    @Cambler said:
    Thanks for the iPhone fix @dwrae . Also did you see my post above in regards to auv3's on Apple Silicon desktop?

    Initially it seemed as if auv3's (synths, fx etc) on desktop were not able to be edited (trying to alter knobs and values seemed to do nothing). Had a bit more of a play and it seems that the active area for each knob etc is offset, eg, clicking and dragging a few centimetres or more to the left of knob affects it. To be more precise it's actually about an inch to the left and half an inch up.

    I have a Mac Mini M2 Pro and did not experience and offset when using two AU instruments. I have heard of this problem before with 1 Android user where JUCE did not initialise the screen width/height correctly. I solved that problem, but that code is not relevant for iOS unfortunately. Did you perhaps resize the dialog?

    Thanks for getting back to me on this. No I haven’t resized the dialog box, it’s just as it is when I open it. This is on a MacBook Air M1. I also have an M4 Mini so will try it on that next to see if it’s specific to the laptop.

    Do you have the app in full-screen expanded mode? I found that I can edit parameters fine on an AUi - I used Lorentz to test - but as soon as I expanded the app (green button) the controls were way off. I'm on an M1 MacBook, by the way.

  • @purpan2 said:

    @Cambler said:

    @dwrae said:

    @Cambler said:
    Thanks for the iPhone fix @dwrae . Also did you see my post above in regards to auv3's on Apple Silicon desktop?

    Initially it seemed as if auv3's (synths, fx etc) on desktop were not able to be edited (trying to alter knobs and values seemed to do nothing). Had a bit more of a play and it seems that the active area for each knob etc is offset, eg, clicking and dragging a few centimetres or more to the left of knob affects it. To be more precise it's actually about an inch to the left and half an inch up.

    I have a Mac Mini M2 Pro and did not experience and offset when using two AU instruments. I have heard of this problem before with 1 Android user where JUCE did not initialise the screen width/height correctly. I solved that problem, but that code is not relevant for iOS unfortunately. Did you perhaps resize the dialog?

    Thanks for getting back to me on this. No I haven’t resized the dialog box, it’s just as it is when I open it. This is on a MacBook Air M1. I also have an M4 Mini so will try it on that next to see if it’s specific to the laptop.

    Do you have the app in full-screen expanded mode? I found that I can edit parameters fine on an AUi - I used Lorentz to test - but as soon as I expanded the app (green button) the controls were way off. I'm on an M1 MacBook, by the way.

    Excellent detective work @purpan2. I did indeed have the app in full screen when encountering the issue. Just tried in the default scaling and the auv3 controls all work fine. @dwrae is there a way to make it work in full screen?

  • @Cambler said:
    Excellent detective work @purpan2. I did indeed have the app in full screen when encountering the issue. Just tried in the default scaling and the auv3 controls all work fine. @dwrae is there a way to make it work in full screen?

    I'll investigate it soon.

  • @dwrae said:

    @Cambler said:
    Excellent detective work @purpan2. I did indeed have the app in full screen when encountering the issue. Just tried in the default scaling and the auv3 controls all work fine. @dwrae is there a way to make it work in full screen?

    I'll investigate it soon.

    Bless your socks @dwrae ! Your efforts with AEM are top notch.

  • @Cambler said:

    @dwrae said:

    @Cambler said:
    Excellent detective work @purpan2. I did indeed have the app in full screen when encountering the issue. Just tried in the default scaling and the auv3 controls all work fine. @dwrae is there a way to make it work in full screen?

    I'll investigate it soon.

    Bless your socks @dwrae ! Your efforts with AEM are top notch.

    I don't think I can do anything about this. I set a breakpoint at the highest level where mouse events come in and the breakpoint doesn't get hit,meaning that the events go straight to the Audio Unit. So this sounds like an Apple bug. Do you have any other iOS hosts that can run on the Mac desktop?

  • @dwrae said:

    @Cambler said:

    @dwrae said:

    @Cambler said:
    Excellent detective work @purpan2. I did indeed have the app in full screen when encountering the issue. Just tried in the default scaling and the auv3 controls all work fine. @dwrae is there a way to make it work in full screen?

    I'll investigate it soon.

    Bless your socks @dwrae ! Your efforts with AEM are top notch.

    I don't think I can do anything about this. I set a breakpoint at the highest level where mouse events come in and the breakpoint doesn't get hit,meaning that the events go straight to the Audio Unit. So this sounds like an Apple bug. Do you have any other iOS hosts that can run on the Mac desktop?

    I have Drambo, which I admit I never use but did manage to load an auv3 synth (Dagger, which I'd also use in the AEM test). I went full screen and all controls were targeted as normal and then I also sized the window down to see if scaling it changed anything, but again it all worked perfectly. Hope that helps.

  • @dwrae said:

    @Cambler said:

    @dwrae said:

    @Cambler said:
    Excellent detective work @purpan2. I did indeed have the app in full screen when encountering the issue. Just tried in the default scaling and the auv3 controls all work fine. @dwrae is there a way to make it work in full screen?

    I'll investigate it soon.

    Bless your socks @dwrae ! Your efforts with AEM are top notch.

    I don't think I can do anything about this. I set a breakpoint at the highest level where mouse events come in and the breakpoint doesn't get hit,meaning that the events go straight to the Audio Unit. So this sounds like an Apple bug. Do you have any other iOS hosts that can run on the Mac desktop?

    Sorry, also realise I have Nanostudio 2 as well which loads on Mac. This suffers from the same problem as AEM. So I guess somehow Beepstreet have made it work with Drambo? What could their trick be?!

  • @Cambler said:
    Sorry, also realise I have Nanostudio 2 as well which loads on Mac. This suffers from the same problem as AEM. So I guess somehow Beepstreet have made it work with Drambo? What could their trick be?!

    It probably depends on whether the host is made in JUCE or native iOS and the mixture of things messes things up.

  • @dwrae said:

    @Cambler said:
    Sorry, also realise I have Nanostudio 2 as well which loads on Mac. This suffers from the same problem as AEM. So I guess somehow Beepstreet have made it work with Drambo? What could their trick be?!

    It probably depends on whether the host is made in JUCE or native iOS and the mixture of things messes things up.

    Fair enough. I appreciate you having a look at this regardless. Thanks @dwrae

  • edited January 2025

    @dwrae Trying to rename tracks in arrangement view is unresponsive (Long hold on track name)
    Works fine in mixer view. Can you confirm ?
    Also can you add the following option for audio editing
    “ convert mono audio to stereo “ and vica versa or “convert mono track to stereo” vica versa

  • @stormbeats said:
    @dwrae Trying to rename tracks in arrangement view is unresponsive (Long hold on track name)
    Works fine in mixer view. Can you confirm ?
    Also can you add the following option for audio editing
    “ convert mono audio to stereo “ and vica versa or “convert mono track to stereo” vica versa

    True, although you can long-press an empty spot on the track in the arranger part and select 'Rename track' in the pop-up menu.

    You can select 'Split into two mono tracks' in the track pop-up menu. It's on track level because you cannot mix and match mono and stereo on one track.

    I don't think there is a point converting a mono track to stereo, please let me know your reasoning. Note that the output of a mono track always becomes stereo after the Vol/Pan block.

  • edited January 2025

    @dwrae said:

    @stormbeats said:
    @dwrae Trying to rename tracks in arrangement view is unresponsive (Long hold on track name)
    Works fine in mixer view. Can you confirm ?
    Also can you add the following option for audio editing
    “ convert mono audio to stereo “ and vica versa or “convert mono track to stereo” vica versa

    True, although you can long-press an empty spot on the track in the arranger part and select 'Rename track' in the pop-up menu.

    You can select 'Split into two mono tracks' in the track pop-up menu. It's on track level because you cannot mix and match mono and stereo on one track.

    I don't think there is a point converting a mono track to stereo, please let me know your reasoning. Note that the output of a mono track always becomes stereo after the Vol/Pan block.

    @dwrae thanks for reply and track naming alternatives. I forgot I can rename in arrangement view with your suggestion. Reason for mono to stereo is some fx plugins are stereo and won’t auto convert mono audio to stereo. (stereo reverbs , delays etc) My way around this currently is to route the mono audio track to a group track. Then becomes stereo.
    The volume pan block suggestion is perfect . I can put that first in the chain . Thanks

  • I may have found a bug or two related to using MIDI plugins on a track. It appears the MIDI plug-in is not saved with the track at least Octachron is not saved but also some of Brambos midi plug-ins, all the ones I’ve tried so far are not saving. Also when you record Midi from these plugins, you can see the recorded notes in the timeline but when you click on the track to go into the piano roll there are no notes there to edit. You can hear the notes playing but you can’t edit anything. Very possibly user error so I’m happy to learn. Thanks.

Sign In or Register to comment.