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

1181921232440

Comments

  • @janpieter said:

    @dwrae said:

    @ipadbeatmaking said:
    Funny enough I shout that IAP out specifically on every recent AEM video I do. I really love that Vocal Tune Pro!! Ever considered releasing it also as a separate auv3? I need it in my life, name your price!!

    including MIDI input..

    will formant shifting be possible?

    No, this is exactly the same as the integrated Vocal Tune Pro.

  • @dwrae said:

    @janpieter said:

    @dwrae said:

    @ipadbeatmaking said:
    Funny enough I shout that IAP out specifically on every recent AEM video I do. I really love that Vocal Tune Pro!! Ever considered releasing it also as a separate auv3? I need it in my life, name your price!!

    including MIDI input..

    will formant shifting be possible?

    No, this is exactly the same as the integrated Vocal Tune Pro.

    Ok thank you!

  • @dwrae said:

    @bargale said:

    @bargale said:

    @dwrae said:

    @bargale said:
    I just got to realize by @ipadbeatmaking that aem works on osx
    This is crazy and unreal at this price

    Yes, that's probably why I'm not going to let VT Pro be universal. Regular prices on OSX for VST/AU's are 10 to 20 times higher.

    Get the bag, you deserve it

    Maybe it would be better to implement 2 different iaps? One for desktop and a different one for iOS?
    This way, it uses the same Id for the plugin on both systems and makes loading projects from iOS to osx not lose the auv3 when recalling it

    Just to avoid confusion, AEMS IS already universal and available on OSX. I was just talking about Vocal Tune PRO.

    Me too, I don’t know how it actually works in the backend but I meant to able to do what @ipadbeatmaking asked for.
    The ability of it to be able to recall the plugin+state from iOS to desktop version
    MTS allows it if the plugin is being identified as the same plugin on both os’s

  • @bargale said:
    MTS allows it if the plugin is being identified as the same plugin on both os’s

    That should work in theory, since it just offers a base64-encoded XML string to the host.

  • @dwrae said:
    When I changed the price 'tier' from $9.99 to $7.99 on the 9th of October, sales and total profit has gone up. So, it's the poor man's solution with equal or more features than higher priced products, just because it's not from a known company.

    Totally agree... it would be against the law for me to say what I think needs to happen with audio app prices 😉> @dwrae said:

    @bargale said:
    I just got to realize by @ipadbeatmaking that aem works on osx
    This is crazy and unreal at this price

    Yes, that's probably why I'm not going to let VT Pro be universal. Regular prices on OSX for VST/AU's are 10 to 20 times higher.

    ...which is completely ridiculous if you think of it -- it should be the other way around as proper touch interfaces are much harder to design than mouse based ones. Not even talking about all the other constraints.

  • @dwrae :Has the user manual been updated? From what I can see it’s still version 1.0.

  • @Telstar5 said:
    @dwrae :Has the user manual been updated? From what I can see it’s still version 1.0.

    The Android version has been updated to include the multi-instrument drum pattern track feature (assigning your own samples to a drum 'lane'). This feature hasn't been ported yet to iOS (and I took a heavy loss on acquiring the drum sound pack that is optionally sold with it, since alsmost nobody seems to use the feature).

  • @dwrae

    Is it possible to use this drum grid layout with our own auv3 (Sitala for example) with our own custom note mapping (example: kick on C1, Etc etc)

    And is multi-out auv3 possible? I’ve been looking for some videos but no luck

  • @ipadbeatmaking said:
    And is multi-out auv3 possible? I’ve been looking for some videos but no luck

    On Android, every drum lane has its own fx grid and instrument in multi-instrument mode. There is no custom note mapping, it all adheres to the GS/GM standard.

  • @dwrae said:

    @ipadbeatmaking said:
    And is multi-out auv3 possible? I’ve been looking for some videos but no luck

    On Android, every drum lane has its own fx grid and instrument in multi-instrument mode. There is no custom note mapping, it all adheres to the GS/GM standard.

    Is it possible to use the drum grid mode with an auv3 like Sitala? Or it reserved only for the internal instrument?

  • @ipadbeatmaking said:

    @dwrae said:

    @ipadbeatmaking said:
    And is multi-out auv3 possible? I’ve been looking for some videos but no luck

    On Android, every drum lane has its own fx grid and instrument in multi-instrument mode. There is no custom note mapping, it all adheres to the GS/GM standard.

    Is it possible to use the drum grid mode with an auv3 like Sitala? Or it reserved only for the internal instrument?

    You can select any instrument currently for the drum pattern track, but that instrument must adhere to the GS/GM standard and you cannot select different instruments per 'lane' (like on Android).

  • @dwrae said:

    @ipadbeatmaking said:

    @dwrae said:

    @ipadbeatmaking said:
    And is multi-out auv3 possible? I’ve been looking for some videos but no luck

    On Android, every drum lane has its own fx grid and instrument in multi-instrument mode. There is no custom note mapping, it all adheres to the GS/GM standard.

    Is it possible to use the drum grid mode with an auv3 like Sitala? Or it reserved only for the internal instrument?

    You can select any instrument currently for the drum pattern track, but that instrument must adhere to the GS/GM standard and you cannot select different instruments per 'lane' (like on Android).

    Gotcha. If it isn’t too much trouble on the programming side, and doesn’t take up to much time, resources etc, It might be worth considering a ‘custom drum map’ cheap IAP. It’d be nice to make, save, and import mappings. Because most iOS drum auv3 don’t adhere to GM, and instead use kick c1, etc. (Sitala) and/or custom mapping from midi controllers (such as koala for instance).

  • @dwrae said:

    @ipadbeatmaking said:

    @dwrae said:

    @ipadbeatmaking said:
    And is multi-out auv3 possible? I’ve been looking for some videos but no luck

    On Android, every drum lane has its own fx grid and instrument in multi-instrument mode. There is no custom note mapping, it all adheres to the GS/GM standard.

    Is it possible to use the drum grid mode with an auv3 like Sitala? Or it reserved only for the internal instrument?

    You can select any instrument currently for the drum pattern track, but that instrument must adhere to the GS/GM standard and you cannot select different instruments per 'lane' (like on Android).

    Edit: I’ve found a valid workaround to this functionality with Polybeat midi Fx, so no big deal to incorporate it, although it’s still be cool to see in AEM natively at some point.

  • edited November 2022

    @dwrae

    Davy many thanks for all these awesome improvements, really hot stuff! And I can't wait to see (and buy) the "secret" IAP function! (I don't know if I'm the only one to miss it but I'd <3 to have the new "midi rec" button on plain MIDI tracks as well, thank you!)

  • @dwrae

    Also, can we get the ability to merge/glue midi tracks together without the ‘overlapping’ requirement?

  • edited November 2022

    @dwrae said:

    @Telstar5 said:
    @dwrae :Has the user manual been updated? From what I can see it’s still version 1.0.

    The Android version has been updated to include the multi-instrument drum pattern track feature (assigning your own samples to a drum 'lane'). This feature hasn't been ported yet to iOS (and I took a heavy loss on acquiring the drum sound pack that is optionally sold with it, since alsmost nobody seems to use the feature).

    @dwrae : Well I for one will be buying the drum sound pack as well as the other fonts you have in the AEM store . Perhaps this post will help I.e. bringing certain features to light and yes, the ability for each drum sample having their own lane is key .. It’s a matter of letting people know these features exist . I hope other readers beside iPad Beat Making who are interested in assigning your own samples to a drum lane chime in here so that hopefully we can see this implemented in the iOS version. Thanks again for responding so promptly.

  • @ipadbeatmaking said:

    @dwrae said:

    @ipadbeatmaking said:

    @dwrae said:

    @ipadbeatmaking said:
    And is multi-out auv3 possible? I’ve been looking for some videos but no luck

    On Android, every drum lane has its own fx grid and instrument in multi-instrument mode. There is no custom note mapping, it all adheres to the GS/GM standard.

    Is it possible to use the drum grid mode with an auv3 like Sitala? Or it reserved only for the internal instrument?

    You can select any instrument currently for the drum pattern track, but that instrument must adhere to the GS/GM standard and you cannot select different instruments per 'lane' (like on Android).

    Gotcha. If it isn’t too much trouble on the programming side, and doesn’t take up to much time, resources etc, It might be worth considering a ‘custom drum map’ cheap IAP. It’d be nice to make, save, and import mappings. Because most iOS drum auv3 don’t adhere to GM, and instead use kick c1, etc. (Sitala) and/or custom mapping from midi controllers (such as koala for instance).

    you could do it with a midi plugin maybe

  • @ipadbeatmaking said:

    @dwrae said:

    @ipadbeatmaking said:

    @dwrae said:

    @ipadbeatmaking said:
    And is multi-out auv3 possible? I’ve been looking for some videos but no luck

    On Android, every drum lane has its own fx grid and instrument in multi-instrument mode. There is no custom note mapping, it all adheres to the GS/GM standard.

    Is it possible to use the drum grid mode with an auv3 like Sitala? Or it reserved only for the internal instrument?

    You can select any instrument currently for the drum pattern track, but that instrument must adhere to the GS/GM standard and you cannot select different instruments per 'lane' (like on Android).

    Edit: I’ve found a valid workaround to this functionality with Polybeat midi Fx, so no big deal to incorporate it, although it’s still be cool to see in AEM natively at some point.

    Thanks for the Polybeat tip..

  • @ipadbeatmaking said:

    @dwrae said:

    @ipadbeatmaking said:

    @dwrae said:

    @ipadbeatmaking said:
    And is multi-out auv3 possible? I’ve been looking for some videos but no luck

    On Android, every drum lane has its own fx grid and instrument in multi-instrument mode. There is no custom note mapping, it all adheres to the GS/GM standard.

    Is it possible to use the drum grid mode with an auv3 like Sitala? Or it reserved only for the internal instrument?

    You can select any instrument currently for the drum pattern track, but that instrument must adhere to the GS/GM standard and you cannot select different instruments per 'lane' (like on Android).

    Gotcha. If it isn’t too much trouble on the programming side, and doesn’t take up to much time, resources etc, It might be worth considering a ‘custom drum map’ cheap IAP. It’d be nice to make, save, and import mappings. Because most iOS drum auv3 don’t adhere to GM, and instead use kick c1, etc. (Sitala) and/or custom mapping from midi controllers (such as koala for instance).

    @ipadbeatmaking said:

    @dwrae

    Also, can we get the ability to merge/glue midi tracks together without the ‘overlapping’ requirement?

    +1 for both suggestions

  • edited November 2022

    @dwrae
    The IAP idea makes the most sense . I’d buy it for sure .

  • @ipadbeatmaking said:

    @dwrae

    Also, can we get the ability to merge/glue midi tracks together without the ‘overlapping’ requirement?

    I don't understand. If you use the track pop-up menu and select 'Merge all clips', then they will be merged, overlapping or not.

  • @dwrae said:

    @ipadbeatmaking said:

    @dwrae

    Also, can we get the ability to merge/glue midi tracks together without the ‘overlapping’ requirement?

    I don't understand. If you use the track pop-up menu and select 'Merge all clips', then they will be merged, overlapping or not.

    Maybe the user just wants to merge a few selected clips, not all clips on the track? (I do that in Logic all the time).

  • @dwrae said:

    @ipadbeatmaking said:

    @dwrae said:

    @ipadbeatmaking said:
    And is multi-out auv3 possible? I’ve been looking for some videos but no luck

    On Android, every drum lane has its own fx grid and instrument in multi-instrument mode. There is no custom note mapping, it all adheres to the GS/GM standard.

    Is it possible to use the drum grid mode with an auv3 like Sitala? Or it reserved only for the internal instrument?

    You can select any instrument currently for the drum pattern track, but that instrument must adhere to the GS/GM standard and you cannot select different instruments per 'lane' (like on Android).

    @dwrae : So will ios AEM ever get this ability to select different instruments per lane , even if via IAP?

  • edited November 2022

    @ipadbeatmaking said:

    @dwrae said:

    Edit: I’ve found a valid workaround to this functionality with Polybeat midi Fx, so no big deal to incorporate it, although it’s still be cool to see in AEM natively at some point.

    Did that workaround involve something like:

    -setting up a midi channel on track 1->

    -assigning a sequencer to ‘AU MIDl’ on the midi channel->

    -pointing the midi output of the channel to the input of a seperate midi instrument channel on track 2 (via network session 1)?

    I’m getting odd behaviours using Drambo/Atom 2 as the AU MIDI sequencer, both setups play the instrument on track 2 but:

    • drambo playhead doesn’t return to t=0 on AEM stop, it just stops at whatever point (t=x) and plays from there on AEM start

    • atom playhead stops at t=x on AEM stop and returns to t=0 in the atom window on AEM start but the synth on track 2 just gets stopped as if atom began at arbitrary t=x on AEM start (ie, synth continues to play on AEM start as if starting from t=x, not t=0)

    Noting that, if I load up drambo or atom as the AU MIDI control for a given midi instrument track, all settings the same, the sequencers sync with host as expected…

    Or was your workaround something else?

  • @Kewe_Esse said:

    @ipadbeatmaking said:

    @dwrae said:

    Edit: I’ve found a valid workaround to this functionality with Polybeat midi Fx, so no big deal to incorporate it, although it’s still be cool to see in AEM natively at some point.

    Did that workaround involve something like:

    -setting up a midi channel on track 1->

    -assigning a sequencer to ‘AU MIDl’ on the midi channel->

    -pointing the midi output of the channel to the input of a seperate midi instrument channel on track 2 (via network session 1)?

    I’m getting odd behaviours using Drambo/Atom 2 as the AU MIDI sequencer, both setups play the instrument on track 2 but:

    • drambo playhead doesn’t return to t=0 on AEM stop, it just stops at whatever point (t=x) and plays from there on AEM start

    • atom playhead stops at t=x on AEM stop and returns to t=0 in the atom window on AEM start but the synth on track 2 just gets stopped as if atom began at arbitrary t=x on AEM start (ie, synth continues to play on AEM start as if starting from t=x, not t=0)

    Noting that, if I load up drambo or atom as the AU MIDI control for a given midi instrument track, all settings the same, the sequencers sync with host as expected…

    Or was your workaround something else?

    Polybeat is a midi au drum sequencer, just load it on the midi au insert of the instrument

  • @bargale : Thanks for that tip.. My first reaction was “Whoa , this person is ALL IN the iOS game!”.. lol

  • @bargale said:

    @Kewe_Esse said:

    @ipadbeatmaking said:

    @dwrae said:

    was your workaround something else?

    Polybeat is a midi au drum sequencer, just load it on the midi au insert of the instrument

    But can you run multiple midi instruments on seperate tracks using a single AU sequencer instance?

    I don’t have polybeat but…

    -If I load up drambo as a midi instrument, I can’t point the output to other instrument tracks, only to ‘master’

    -If I load up drambo via the ‘au midi’ insert on an instrument track, I can only use that instance to control that track, other tracks would get seperate instances in the insert

  • @Kewe_Esse said:

    @bargale said:

    @Kewe_Esse said:

    @ipadbeatmaking said:

    @dwrae said:

    was your workaround something else?

    Polybeat is a midi au drum sequencer, just load it on the midi au insert of the instrument

    But can you run multiple midi instruments on seperate tracks using a single AU sequencer instance?

    I don’t have polybeat but…

    -If I load up drambo as a midi instrument, I can’t point the output to other instrument tracks, only to ‘master’

    -If I load up drambo via the ‘au midi’ insert on an instrument track, I can only use that instance to control that track, other tracks would get seperate instances in the insert

    Nope, aem doesn’t have midi routing(dunno if it’s planned for the future)

  • @bargale said:

    Nope, aem doesn’t have midi routing(dunno if it’s planned for the future)

    I see… annoying though, it sort of almost works using drambo as an au midi sequencer inside a midi track… then you can point several midi instrument tracks to your sequencer track…

    Apart from the sequencer transport/ AEM sync issue, the routing works

  • @Kewe_Esse said:

    @bargale said:

    Nope, aem doesn’t have midi routing(dunno if it’s planned for the future)

    I see… annoying though, it sort of almost works using drambo as an au midi sequencer inside a midi track… then you can point several midi instrument tracks to your sequencer track…

    Apart from the sequencer transport/ AEM sync issue, the routing works

    How are you sending from drambo to multiple midi tracks? I don’t see any aem midi input on midi instruments tracks…

Sign In or Register to comment.