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.

MODSTEP TUTORIAL - Template editor + Bonus automation tips.

2»

Comments

  • aplourdeaplourde

    @hightunnels said:
    @gonekrazy3000 - just discovered this--extremely helpful! I can't figure out how to make it work with an au synth (mood, for instance) hosted in AUM however. Any hints?

    Actually, this is somewhat dependent on the app in question.

    In some cases if you have set up a MIDI assignment in the app, that is used by the AU automatically.

    For example, Ripplemaker. You don't need to go through the process of learning the MIDI control in AUM. Just use the correct controls (template available here) in ModStep and point it at the AUM channel that is hosting the AU. The controls will automatically work.

    This is also the case with IceGear's Laplace (template available here - but right now Laplace seems to be crashing on me when I try to load it as an AU in AUM....)

    Not all apps work this way. Arturia's iSEM needs to go through the process @gonekrazy3000 outlined even if you have set up the MIDI mapping in iSEM and are using those correct controls.

  • aplourdeaplourde

    @hightunnels said:
    That's awesome, thanks! So the channel and cc numbers are arbitrary as long as they match in modstep and aum?? I think that was tripping me up.

    Depends on the app. For something like iSEM it's arbitrary.
    For something like Ripplemaker or Laplace it works with the MIDI mappings you you setup in those apps.

  • aplourdeaplourde

    @ExAsperis99 said:
    This is the last frontier for me in Modstep, these modulations. (I know. It's the whole point of the app.)
    This can't be easily done hosting an AU or IAA within Modstep, can it?

    Using modulations? It's really easy. In fact, if you host an AU it will create a template based on the AU parameters that the AU reports ModStep.

    The only issue is that audio in ModStep is a bit, uh, idiosyncratic - half of the time when I try to use ModStep in AB or AUM, I find that it has directly connected to the audio device instead of routing through those apps and so I can't route it in those apps through effects, busses, etc. Also, there's no audio panning.

    Like several others here, I just use ModStep for MIDI and host my audio elsewhere (for me, in AB, routed to AUM, as I use AB Remote + State Saving for a lot of IAA-only apps)

  • hightunnelshightunnels

    @aplourde said:

    @hightunnels said:
    That's awesome, thanks! So the channel and cc numbers are arbitrary as long as they match in modstep and aum?? I think that was tripping me up.

    Depends on the app. For something like iSEM it's arbitrary.
    For something like Ripplemaker or Laplace it works with the MIDI mappings you you setup in those apps.

    Cool-thanks for the additional tips--am currently experimenting with several different synths.

  • gonekrazy3000gonekrazy3000

    @ExAsperis99 said:
    This is the last frontier for me in Modstep, these modulations. (I know. It's the whole point of the app.)
    This can't be easily done hosting an AU or IAA within Modstep, can it?

    From what I've seen modstep cannot automate the Aux effects. But hosted in AUM everything is automatable per channel. Plus in the parameter settings In Aum (the last picture) you can even adjust the min and Max values the modulation can affect changing the (range) setting. Something modstep can NOT do reliably.

  • gonekrazy3000gonekrazy3000

    @hightunnels said:
    That's awesome, thanks! So the channel and cc numbers are arbitrary as long as they match in modstep and aum?? I think that was tripping me up.

    Yup. Totally arbitary :)

  • gonekrazy3000gonekrazy3000
    edited June 2017

    @aplourde said:

    @hightunnels said:
    @gonekrazy3000 - just discovered this--extremely helpful! I can't figure out how to make it work with an au synth (mood, for instance) hosted in AUM however. Any hints?

    Actually, this is somewhat dependent on the app in question.

    In some cases if you have set up a MIDI assignment in the app, that is used by the AU automatically.

    For example, Ripplemaker. You don't need to go through the process of learning the MIDI control in AUM. Just use the correct controls (template available here) in ModStep and point it at the AUM channel that is hosting the AU. The controls will automatically work.

    This is also the case with IceGear's Laplace (template available here - but right now Laplace seems to be crashing on me when I try to load it as an AU in AUM....)

    Not all apps work this way. Arturia's iSEM needs to go through the process @gonekrazy3000 outlined even if you have set up the MIDI mapping in iSEM and are using those correct controls.

    It's easier to just follow this method since then you don't need different procedures per Aux. I've done it so often now that it's second nature for me. Don't have to bother with learning the inapp assignments. Also. Since you can assign any number it basically means you have upto 128 automatable parameters for all your Aux instruments and effects sent on just 1 midi channel. (In my case all automation go over Aum channel 16).I just start at cc0 and go up as I automate more things. I just name the cell whatever it is. I almost never cross 50 automated things in 1 project. Also. Using aums min/max setting inside the range gives you control over modulations modstep doesn't usually have.

  • hightunnelshightunnels

    @gonekrazy3000 said:

    @aplourde said:

    @hightunnels said:
    @gonekrazy3000 - just discovered this--extremely helpful! I can't figure out how to make it work with an au synth (mood, for instance) hosted in AUM however. Any hints?

    Actually, this is somewhat dependent on the app in question.

    In some cases if you have set up a MIDI assignment in the app, that is used by the AU automatically.

    For example, Ripplemaker. You don't need to go through the process of learning the MIDI control in AUM. Just use the correct controls (template available here) in ModStep and point it at the AUM channel that is hosting the AU. The controls will automatically work.

    This is also the case with IceGear's Laplace (template available here - but right now Laplace seems to be crashing on me when I try to load it as an AU in AUM....)

    Not all apps work this way. Arturia's iSEM needs to go through the process @gonekrazy3000 outlined even if you have set up the MIDI mapping in iSEM and are using those correct controls.

    It's easier to just follow this method since then you don't need different procedures per Aux. I've done it so often now that it's second nature for me. Don't have to bother with learning the inapp assignments. Also. Since you can assign any number it basically means you have upto 128 automatable parameters for all your Aux instruments and effects sent on just 1 midi channel. (In my case all automation go over Aum channel 16).I just start at cc0 and go up as I automate more things. I just name the cell whatever it is. I almost never cross 50 automated things in 1 project. Also. Using aums min/max setting inside the range gives you control over modulations modstep doesn't usually have.

    Ok let's see if I understand this--each one of your modstep tracks has a corresponding automation track containing automation clips. And instead of loading up templates per instrument you just assign your own parameter numbers as needed, everything on Channel 16? Sounds pretty straight forward!

  • gonekrazy3000gonekrazy3000
    edited June 2017

    @hightunnels said:

    @gonekrazy3000 said:

    @aplourde said:

    @hightunnels said:
    @gonekrazy3000 - just discovered this--extremely helpful! I can't figure out how to make it work with an au synth (mood, for instance) hosted in AUM however. Any hints?

    Actually, this is somewhat dependent on the app in question.

    In some cases if you have set up a MIDI assignment in the app, that is used by the AU automatically.

    For example, Ripplemaker. You don't need to go through the process of learning the MIDI control in AUM. Just use the correct controls (template available here) in ModStep and point it at the AUM channel that is hosting the AU. The controls will automatically work.

    This is also the case with IceGear's Laplace (template available here - but right now Laplace seems to be crashing on me when I try to load it as an AU in AUM....)

    Not all apps work this way. Arturia's iSEM needs to go through the process @gonekrazy3000 outlined even if you have set up the MIDI mapping in iSEM and are using those correct controls.

    It's easier to just follow this method since then you don't need different procedures per Aux. I've done it so often now that it's second nature for me. Don't have to bother with learning the inapp assignments. Also. Since you can assign any number it basically means you have upto 128 automatable parameters for all your Aux instruments and effects sent on just 1 midi channel. (In my case all automation go over Aum channel 16).I just start at cc0 and go up as I automate more things. I just name the cell whatever it is. I almost never cross 50 automated things in 1 project. Also. Using aums min/max setting inside the range gives you control over modulations modstep doesn't usually have.

    Ok let's see if I understand this--each one of your modstep tracks has a corresponding automation track containing automation clips. And instead of loading up templates per instrument you just assign your own parameter numbers as needed, everything on Channel 16? Sounds pretty straight forward!

    Yep.

  • gonekrazy3000gonekrazy3000

    @hightunnels 15 channels for other instruments is plenty for me :) and if I'm doubling say 2 bass synths they're listening to the same Aum channel so theoretically it's 15 layers. Plus my ruismaker rack is completely separate since it's using the aum ab3 midi ports which are separate from Aums ports.

  • KühlKühl

    @gonekrazy3000 said:

    @Kühl said:
    Just wish the rest of society was as Amazing as people in this forum... smart and helpful.
    Let's be proud.

    And thanx for the Modstep guide.

    You're welcome :) you should checkout some of my other threads. The multichannel Ruismaker is my favourite experiment so far. And it has ready made ab3 presets so that you use the drumrack I built immediately :)

    I like Ruismaker and have both versions. I find it strange that they won't p,at a midi track where I wrote the drumtrack in standard score notation. If I use a drum plugin from Auria Pro or Cubasis, the notes okay as I have written them... to the last cymbal shiver. I'm university educated in music, so writing notes is like writing a letter for me... that's why I write my sequences in Symphony Pro or Notion. Everything works fine until I try ruismaker as a plugin. I have even set it to midiGM mapping, but still no sounds... so here I am. The fool on the hill :)

  • gonekrazy3000gonekrazy3000

    @Kühl said:

    @gonekrazy3000 said:

    @Kühl said:
    Just wish the rest of society was as Amazing as people in this forum... smart and helpful.
    Let's be proud.

    And thanx for the Modstep guide.

    You're welcome :) you should checkout some of my other threads. The multichannel Ruismaker is my favourite experiment so far. And it has ready made ab3 presets so that you use the drumrack I built immediately :)

    I like Ruismaker and have both versions. I find it strange that they won't p,at a midi track where I wrote the drumtrack in standard score notation. If I use a drum plugin from Auria Pro or Cubasis, the notes okay as I have written them... to the last cymbal shiver. I'm university educated in music, so writing notes is like writing a letter for me... that's why I write my sequences in Symphony Pro or Notion. Everything works fine until I try ruismaker as a plugin. I have even set it to midiGM mapping, but still no sounds... so here I am. The fool on the hill :)

    Ruismaker doesn't use standard gm midi. It uses all the black notes from c3# onward. What my rack does here is convert gm midi to the ruismaker notes while sending to each instance hosted in Aum.

  • KühlKühl

    @gonekrazy3000 said:

    @Kühl said:

    @gonekrazy3000 said:

    @Kühl said:
    Just wish the rest of society was as Amazing as people in this forum... smart and helpful.
    Let's be proud.

    And thanx for the Modstep guide.

    You're welcome :) you should checkout some of my other threads. The multichannel Ruismaker is my favourite experiment so far. And it has ready made ab3 presets so that you use the drumrack I built immediately :)

    I like Ruismaker and have both versions. I find it strange that they won't p,at a midi track where I wrote the drumtrack in standard score notation. If I use a drum plugin from Auria Pro or Cubasis, the notes okay as I have written them... to the last cymbal shiver. I'm university educated in music, so writing notes is like writing a letter for me... that's why I write my sequences in Symphony Pro or Notion. Everything works fine until I try ruismaker as a plugin. I have even set it to midiGM mapping, but still no sounds... so here I am. The fool on the hill :)

    Ruismaker doesn't use standard gm midi. It uses all the black notes from c3# onward. What my rack does here is convert gm midi to the ruismaker notes while sending to each instance hosted in Aum.

    But you can map it to midi GM in the settings... so I don't know

  • gonekrazy3000gonekrazy3000

    @Kühl said:

    @gonekrazy3000 said:

    @Kühl said:

    @gonekrazy3000 said:

    @Kühl said:
    Just wish the rest of society was as Amazing as people in this forum... smart and helpful.
    Let's be proud.

    And thanx for the Modstep guide.

    You're welcome :) you should checkout some of my other threads. The multichannel Ruismaker is my favourite experiment so far. And it has ready made ab3 presets so that you use the drumrack I built immediately :)

    I like Ruismaker and have both versions. I find it strange that they won't p,at a midi track where I wrote the drumtrack in standard score notation. If I use a drum plugin from Auria Pro or Cubasis, the notes okay as I have written them... to the last cymbal shiver. I'm university educated in music, so writing notes is like writing a letter for me... that's why I write my sequences in Symphony Pro or Notion. Everything works fine until I try ruismaker as a plugin. I have even set it to midiGM mapping, but still no sounds... so here I am. The fool on the hill :)

    Ruismaker doesn't use standard gm midi. It uses all the black notes from c3# onward. What my rack does here is convert gm midi to the ruismaker notes while sending to each instance hosted in Aum.

    But you can map it to midi GM in the settings... so I don't know

    The setting only applies to the first instance. 2+ revert to Black keys only. The multi out uses 8 instances.

  • KühlKühl

    The setting only applies to the first instance. 2+ revert to Black keys only. The multi out uses 8 instances.

    Aha, I see. I'll have to use it in another way than I thought then... I though it was an off the shelf drum machine

  • gonekrazy3000gonekrazy3000

    @Kühl said:

    The setting only applies to the first instance. 2+ revert to Black keys only. The multi out uses 8 instances.

    Aha, I see. I'll have to use it in another way than I thought then... I though it was an off the shelf drum machine

    i built this rack to make it work easily. not sure what the problem is. its not like you have to work and figure it out either lol. the preset is already ready. just look at my other thread:- https://forum.audiob.us/discussion/19510/ruismaker-multi-out-drumrack-auria-pro-cubasis-edition#latest

  • KühlKühl

    i built this rack to make it work easily. not sure what the problem is. its not like you have to work and figure it out either lol. the preset is already ready. just look at my other thread:- https://forum.audiob.us/discussion/19510/ruismaker-multi-out-drumrack-auria-pro-cubasis-edition#latest

    Can't wait to try it
    I wish the world was more like this forum :)

  • bleepbleep

    @gonekrazy3000: You say you send all automation over channel 16. Are you able to to modulate two different apps at the same time with this setup? I guess you are, as long as you keep things tidy and don't assign the same CC number to different paramters in different apps :) So for instance, instead of having reverb send as (CC 74, channel 1) for app A and as (CC 74, channel 2) for app B, you just set them to say CC 10 and CC 11 in channel 16 and let AUM do the mapping?

    Btw, I have often wanted to let the two XY pads in Modstep modulate two different tracks at the same time (two different apps). But that is not possible, as far as I can see. Perhaps doable in the new beta?

  • bleepbleep
    edited June 2017

    ... ah, by putting all modulations on channel 16, you can indeed use the two xy pads to change 8 16 different parameters across apps at the same time. Sweet. Now we only need all IAA to become AU.

  • gonekrazy3000gonekrazy3000
    edited June 2017

    @bleep said:
    @gonekrazy3000: You say you send all automation over channel 16. Are you able to to modulate two different apps at the same time with this setup? I guess you are, as long as you keep things tidy and don't assign the same CC number to different paramters in different apps :) So for instance, instead of having reverb send as (CC 74, channel 1) for app A and as (CC 74, channel 2) for app B, you just set them to say CC 10 and CC 11 in channel 16 and let AUM do the mapping?

    Btw, I have often wanted to let the two XY pads in Modstep modulate two different tracks at the same time (two different apps). But that is not possible, as far as I can see. Perhaps doable in the new beta?

    yep. as long as its tidy, you can automate upto 128 parameters irrespective of whether it is different apps or even different channel controls in AUM. thats plenty of control for me lol. i dont think i automate more than 100 parameters in a project usually. regardign the xy pads you can theoretically have it modulate 2 by having the x axis control 1 app's parameter in Aum and the y-axis control a different apps parameter. its the main reason i host in AUM and not modstep. since the track is sending to a single channel (Aum channel 16) this is easily possible.

Sign In or Register to comment.

© Vanilla Keystone Theme 2025