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.

Genome Sale: GR8 Buy if you don't have

In my opinion.

I strictly use this for my iPad production. I find it the easiest and most intuitive for my brain and workflow style.

Sale price and it is so worth it if you need a sequencer that records know animation for iPad.

I use Infinite for iPhone FYI.

https://itunes.apple.com/app/id450475494?mt=8&ign-mpt=uo=8

Comments

  • Genome is a tool that seemed to have so much promise. It has sat unused on my 3rd iPad Music Apps screen for a few years now, I refused to delete it since I paid full price. shrug Any tutorials or other walkthroughs that you found particularly helpful that got this app to click for you?

    Some of the difficulty with it seems to be navigation -- pinching, zooming, panning around etc.

    Again, an app with a ton of promise for creating a song and then just hitting play and getting to muck around with the connected apps sounds while it triggers MIDI notes.

  • edited July 2017

    @fprintf said:
    Genome is a tool that seemed to have so much promise. It has sat unused on my 3rd iPad Music Apps screen for a few years now, I refused to delete it since I paid full price. shrug Any tutorials or other walkthroughs that you found particularly helpful that got this app to click for you?

    Some of the difficulty with it seems to be navigation -- pinching, zooming, panning around etc.

    Again, an app with a ton of promise for creating a song and then just hitting play and getting to muck around with the connected apps sounds while it triggers MIDI notes.

    Here is one walk through from Tim at disccord, it's a pre- AB version of Genome, (AB is useful for the control panel and app switching, even if you aren't using ithe audio from Genomes onboard instruments...) if you have workflow questions beyond this video there is YouTube or ask here

    Another from Sweetwater

    There's more on the Devs own channel, Dave Wallin: (the above 2 are included with 19 other shorter clips, demos with hardware etc.)

  • I have no trouble using it, I just never found it got in the way of my ideas. Once I got Modstep (thanks to the recent videos) and setup a template in AUM and Modstep with all my defaults set up, I find that I'm really fast in Modstep.

  • edited July 2017

    @cian said:
    I have no trouble using it, I just never found it got in the way of my ideas. Once I got Modstep (thanks to the recent videos) and setup a template in AUM and Modstep with all my defaults set up, I find that I'm really fast in Modstep.

    I'm all over Modstep, (it the hub of my multi-app thing, and I'm in it as an all-in-one too per the modstep challenge.https://forum.audiob.us/discussion/19720/modstep-challenge#latest)

    Not yet using Modstep with AUM, have heard a lot about AUM workflows with Modstep on the forum, haven't got a handle on it, curious how you're using it. There's probably a thread.

    But contra AUM and even AB, my tendency with Modstep - and Genome - is on the simple tip, avoiding moving parts. Host instruments in DAW or Modstep, sequence in Modstep, record audio in DAW.

    Genome the same, host instruments in DAW, record in DAW...use core midi, apply AB (2) just for its appswitching and side control panel. Core midi implementation in Genome and this devs apps is very reliable, the thing that AB3 fixes in many apps is not broken in Genome.

  • @RustiK said:
    In my opinion.

    I strictly use this for my iPad production. I find it the easiest and most intuitive for my brain and workflow style.

    Sale price and it is so worth it if you need a sequencer that records know animation for iPad.

    I use Infinite for iPhone FYI.

    https://itunes.apple.com/app/id450475494?mt=8&ign-mpt=uo=8

    How do you compare (pros vs cons) between Infinite Looper and Genome?

    Thanks.

  • @Littlewoodg

    So I realized a while back that if I was to get songs written I had to work fast with a minimum of distractions. Consequently I've gradually built a workflow that prioritizes getting notes down quickly, and the flexibility to manipulate ideas once they're in the editor. So I have three stages:
    1. Sketching - this needs to be fast, and I need to be able dial good enough sounds in quickly. Effects are used to do things like give the Kick drums enough punch, or to play around with delay on the hi hats. I aim to be finished with MIDI editing in this stage
    2. Recording - I treat this as if I'm recording live. I fuss over getting the synth sounds right (and typically will swap in instruments), I may add in extra parts to bulk out the arrangement. I only use effects at the channel level, and do very little MIDI editing. When finished I export each channel as Stems. The idea is that each stem should be 'perfectly' recorded.
    3. Mixing - This occurs on the PC (though I'm hoping that Beatmaker may play a role here) in reaper. This is where I worry about buses, master effects, levels, EQ, etc.

    So for me Modstep and AUM are key for stages 1 and 2 (though I'm hoping Beatmaker may take over for 2, and maybe 3).

    All instruments and effects are hosted in AUM. All MIDI is sourced from ModStep (my controllers send MIDI to modstep). For AU instruments AUM handles the MIDI. For IAA and Audiobus I send MIDI directly to the synth/effect from ModStep. I haven't really worked out a good workflow for IAA and Audiobus in AUM. IAA is easier, but crashy. Audiobus requires messing around with another application which is a minor annoyance.

    Another subtlety is that I've set up a drum rack using Ruismaker. Each drum (except for hi-hats which share) gets a separate AUM channel. This means that I can add effects to them individually, and also that they can be exported as individual stems. However I've setup Modstep so that drums are programmed on a single track (similar to the video that somebody posted, only it can be done without Audiobus) using the drum sequencer. This also makes it super easy to swap out individual drums later if I need to.

    For stage 1 I have templates for AUM and Modstep that have the following setup:

    • Ruismaker rack.
    • Bass, lead, pads (Each gets a named Modstep track which routes to a predefined AUM midi port). I have AUM setup so that Ruismaker is loaded by default, then for the others I quickly choose from a small set of reliable AU synths (Poison, Pads, iSem, Viking, Troublemaker, Phasemaker) that I've already made sure have MIDI templates in AUM. And then I just drop the relevant synth on the right channel and dive straight into Modstep.

    For stage 2 I will tend to bring in different synths and worry about setting up IAA/Audiobus, MIDI. But not until then. The rule is no messing around with configuration until I'm thinking about arrangement.

    It's not perfect, but it seems to be working for me. And of course sometimes I'll start sketching by playing round with a more unruly synth (iVCS3, modulars, Amazing Noises, ApeSoft, etc). But the beauty of AUM is that you can just hit record and then edit the good stuff later in AudioShare...

  • great write up @cian. I reallllllllly need to drink this kool-aid as of late:

    The rule is no messing around with configuration until I'm thinking about arrangement.

  • edited July 2017

    @cian said:
    @Littlewoodg

    So I realized a while back that if I was to get songs written I had to work fast with a minimum of distractions. Consequently I've gradually built a workflow that prioritizes getting notes down quickly, and the flexibility to manipulate ideas once they're in the editor. So I have three stages:
    1. Sketching - this needs to be fast, and I need to be able dial good enough sounds in quickly. Effects are used to do things like give the Kick drums enough punch, or to play around with delay on the hi hats. I aim to be finished with MIDI editing in this stage
    2. Recording - I treat this as if I'm recording live. I fuss over getting the synth sounds right (and typically will swap in instruments), I may add in extra parts to bulk out the arrangement. I only use effects at the channel level, and do very little MIDI editing. When finished I export each channel as Stems. The idea is that each stem should be 'perfectly' recorded.
    3. Mixing - This occurs on the PC (though I'm hoping that Beatmaker may play a role here) in reaper. This is where I worry about buses, master effects, levels, EQ, etc.

    So for me Modstep and AUM are key for stages 1 and 2 (though I'm hoping Beatmaker may take over for 2, and maybe 3).

    All instruments and effects are hosted in AUM. All MIDI is sourced from ModStep (my controllers send MIDI to modstep). For AU instruments AUM handles the MIDI. For IAA and Audiobus I send MIDI directly to the synth/effect from ModStep. I haven't really worked out a good workflow for IAA and Audiobus in AUM. IAA is easier, but crashy. Audiobus requires messing around with another application which is a minor annoyance.

    Another subtlety is that I've set up a drum rack using Ruismaker. Each drum (except for hi-hats which share) gets a separate AUM channel. This means that I can add effects to them individually, and also that they can be exported as individual stems. However I've setup Modstep so that drums are programmed on a single track (similar to the video that somebody posted, only it can be done without Audiobus) using the drum sequencer. This also makes it super easy to swap out individual drums later if I need to.

    For stage 1 I have templates for AUM and Modstep that have the following setup:

    • Ruismaker rack.
    • Bass, lead, pads (Each gets a named Modstep track which routes to a predefined AUM midi port). I have AUM setup so that Ruismaker is loaded by default, then for the others I quickly choose from a small set of reliable AU synths (Poison, Pads, iSem, Viking, Troublemaker, Phasemaker) that I've already made sure have MIDI templates in AUM. And then I just drop the relevant synth on the right channel and dive straight into Modstep.

    For stage 2 I will tend to bring in different synths and worry about setting up IAA/Audiobus, MIDI. But not until then. The rule is no messing around with configuration until I'm thinking about arrangement.

    It's not perfect, but it seems to be working for me. And of course sometimes I'll start sketching by playing round with a more unruly synth (iVCS3, modulars, Amazing Noises, ApeSoft, etc). But the beauty of AUM is that you can just hit record and then edit the good stuff later in AudioShare...

    Beautiful thing.

    Thank you so much for spelling this out in detail!

    I'm actually such a simpleton I will have to sit with this and absorb...

  • @cian said:
    @Littlewoodg

    So I realized a while back that if I was to get songs written I had to work fast with a minimum of distractions. Consequently I've gradually built a workflow that prioritizes getting notes down quickly, and the flexibility to manipulate ideas once they're in the editor. So I have three stages:
    1. Sketching - this needs to be fast, and I need to be able dial good enough sounds in quickly. Effects are used to do things like give the Kick drums enough punch, or to play around with delay on the hi hats. I aim to be finished with MIDI editing in this stage
    2. Recording - I treat this as if I'm recording live. I fuss over getting the synth sounds right (and typically will swap in instruments), I may add in extra parts to bulk out the arrangement. I only use effects at the channel level, and do very little MIDI editing. When finished I export each channel as Stems. The idea is that each stem should be 'perfectly' recorded.
    3. Mixing - This occurs on the PC (though I'm hoping that Beatmaker may play a role here) in reaper. This is where I worry about buses, master effects, levels, EQ, etc.

    So for me Modstep and AUM are key for stages 1 and 2 (though I'm hoping Beatmaker may take over for 2, and maybe 3).

    All instruments and effects are hosted in AUM. All MIDI is sourced from ModStep (my controllers send MIDI to modstep). For AU instruments AUM handles the MIDI. For IAA and Audiobus I send MIDI directly to the synth/effect from ModStep. I haven't really worked out a good workflow for IAA and Audiobus in AUM. IAA is easier, but crashy. Audiobus requires messing around with another application which is a minor annoyance.

    Another subtlety is that I've set up a drum rack using Ruismaker. Each drum (except for hi-hats which share) gets a separate AUM channel. This means that I can add effects to them individually, and also that they can be exported as individual stems. However I've setup Modstep so that drums are programmed on a single track (similar to the video that somebody posted, only it can be done without Audiobus) using the drum sequencer. This also makes it super easy to swap out individual drums later if I need to.

    For stage 1 I have templates for AUM and Modstep that have the following setup:

    • Ruismaker rack.
    • Bass, lead, pads (Each gets a named Modstep track which routes to a predefined AUM midi port). I have AUM setup so that Ruismaker is loaded by default, then for the others I quickly choose from a small set of reliable AU synths (Poison, Pads, iSem, Viking, Troublemaker, Phasemaker) that I've already made sure have MIDI templates in AUM. And then I just drop the relevant synth on the right channel and dive straight into Modstep.

    For stage 2 I will tend to bring in different synths and worry about setting up IAA/Audiobus, MIDI. But not until then. The rule is no messing around with configuration until I'm thinking about arrangement.

    It's not perfect, but it seems to be working for me. And of course sometimes I'll start sketching by playing round with a more unruly synth (iVCS3, modulars, Amazing Noises, ApeSoft, etc). But the beauty of AUM is that you can just hit record and then edit the good stuff later in AudioShare...

    Each of us have our twisted method of madness.

    I would actually love to hear some of the finished goods from this .......system of creation.

    Did you always keep one foot in the PC/MAC world with music production or have you found yourself returning to it?

    I am THIS close to getting the grand daddy ABLETON SUITE most expensive model upgrade due to my frustration of IOS compatibility of apps.

  • edited July 2017

    I bought Ableton Suite on sale a few years ago. (From lite/into to suite) And since then I have gone around and around and keep coming back to Ableton. There is so much in there that really works for me. I have even given up on using any external plugins and concentrating on just the built in ones. You can make some amazing sounds with just layering things in racks/groups. And for me I can go between my Mac and PC without worrying about plugin compatibilities or if I need to install on a new system, everything is just ready to go. I find that I hate fiddling around when I want to get something down or when I come back to work on it.

    @RustiK
    Have you used an intro version of Ableton to make sure the work flow is right for you? It was such a large investment for me and I made sure it worked with me before buying.

  • @Telengard said:
    I bought Ableton Suite on sale a few years ago. (From lite/into to suite) And since then I have gone around and around and keep coming back to Ableton. There is so much in there that really works for me. I have even given up on using any external plugins and concentrating on just the built in ones. You can make some amazing sounds with just layering things in racks/groups. And for me I can go between my Mac and PC without worrying about plugin compatibilities or if I need to install on a new system, everything is just ready to go. I find that I hate fiddling around when I want to get something down or when I come back to work on it.

    @RustiK
    Have you used an intro version of Ableton to make sure the work flow is right for you? It was such a large investment for me and I made sure it worked with me before buying.

    Oh yeah, been using the Lite version for 4 years now.

    Acid and Reaper and Max before that.

    And of course ios......................since the early music app days........

  • I still 90% of the time perform all of my iPad apps straight to my Macs - Reaper / ProTools - audio & midi .
    Sometimes get some ideas happening quickly - then get off the iPad asap.
    I just find all of these app different setups/ compatibility kills my workflow.
    I still love Kontakt and all of the insane libraries that exist, and Reaktor is amazing, I still use Maschine, plus all of the killer VST's in DAW's, outputs can go anywhere (including back into my iPad).
    About to get Push and Live soon - I still don't gel with glass as a expressive playing medium.
    But I love my 2 iPads, but don't ever attempt to finish anything on them.

  • Talking about Modstep and Live isn't really as much of a highjack of the thread as it first seems, Genome for 10 bucks is an impressive tool for clip launch work flows (that include fullon cc control of instruments including saving templates) with robust core midi implementation and onboard subtractive and drum synth. Learning curve wise I'd say it's not as steep as Modstep...

  • It has gown back up to $9.99
    Not so GR8 Buy no longer

  • I would say even at $10 it's a bargain...

  • @cian said:
    @Littlewoodg

    So I realized a while back that if I was to get songs written I had to work fast with a minimum of distractions. Consequently I've gradually built a workflow that prioritizes getting notes down quickly, and the flexibility to manipulate ideas once they're in the editor. So I have three stages:
    1. Sketching - this needs to be fast, and I need to be able dial good enough sounds in quickly. Effects are used to do things like give the Kick drums enough punch, or to play around with delay on the hi hats. I aim to be finished with MIDI editing in this stage
    2. Recording - I treat this as if I'm recording live. I fuss over getting the synth sounds right (and typically will swap in instruments), I may add in extra parts to bulk out the arrangement. I only use effects at the channel level, and do very little MIDI editing. When finished I export each channel as Stems. The idea is that each stem should be 'perfectly' recorded.
    3. Mixing - This occurs on the PC (though I'm hoping that Beatmaker may play a role here) in reaper. This is where I worry about buses, master effects, levels, EQ, etc.

    So for me Modstep and AUM are key for stages 1 and 2 (though I'm hoping Beatmaker may take over for 2, and maybe 3).

    All instruments and effects are hosted in AUM. All MIDI is sourced from ModStep (my controllers send MIDI to modstep). For AU instruments AUM handles the MIDI. For IAA and Audiobus I send MIDI directly to the synth/effect from ModStep. I haven't really worked out a good workflow for IAA and Audiobus in AUM. IAA is easier, but crashy. Audiobus requires messing around with another application which is a minor annoyance.

    Another subtlety is that I've set up a drum rack using Ruismaker. Each drum (except for hi-hats which share) gets a separate AUM channel. This means that I can add effects to them individually, and also that they can be exported as individual stems. However I've setup Modstep so that drums are programmed on a single track (similar to the video that somebody posted, only it can be done without Audiobus) using the drum sequencer. This also makes it super easy to swap out individual drums later if I need to.

    For stage 1 I have templates for AUM and Modstep that have the following setup:

    • Ruismaker rack.
    • Bass, lead, pads (Each gets a named Modstep track which routes to a predefined AUM midi port). I have AUM setup so that Ruismaker is loaded by default, then for the others I quickly choose from a small set of reliable AU synths (Poison, Pads, iSem, Viking, Troublemaker, Phasemaker) that I've already made sure have MIDI templates in AUM. And then I just drop the relevant synth on the right channel and dive straight into Modstep.

    For stage 2 I will tend to bring in different synths and worry about setting up IAA/Audiobus, MIDI. But not until then. The rule is no messing around with configuration until I'm thinking about arrangement.

    It's not perfect, but it seems to be working for me. And of course sometimes I'll start sketching by playing round with a more unruly synth (iVCS3, modulars, Amazing Noises, ApeSoft, etc). But the beauty of AUM is that you can just hit record and then edit the good stuff later in AudioShare...

    Really interesting - thanks. What sort of music? Any examples?

Sign In or Register to comment.