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.

Midi sequencer to record automation

Hey guys im looking for an Auv3 plugin that records automation with faders or knobs that has visual live feedback of what automation values that have been changed. I have LK which works great for recording automation but the faders dont have any feedback of automation curves so I dont know what fader etc is doing what to the sound. Im not sure if there is a way to make this work in LK or if there is any other app like cykle or thesys that work like this. Also LK doesn't have the ability to name faders to my knowledge. This is also a must have

Comments

  • Ha! Been thinking the same for many years. iOS for this type of automation it’s as much as you put in. In my experience anyways. I always revert back to AUM with the usual suspects, CB3 of course, and Logic all of a sudden. For me to really get stuff done a with a high fun factor it always ends up in Cubasis. I suppose I’m just used to it even though I’ve been a logic user since the E-Magic days. CB when I first got into iOS music just gave me great results. Imma full on automation type and like tweaking everything when it makes sense. I like Thesys and Brams apps and cycle as well. The limitations are part of the magic of iOS music creation. Let me know if you find your solution please.

  • @Morgman73 said:
    Ha! Been thinking the same for many years. iOS for this type of automation it’s as much as you put in. In my experience anyways. I always revert back to AUM with the usual suspects, CB3 of course, and Logic all of a sudden. For me to really get stuff done a with a high fun factor it always ends up in Cubasis. I suppose I’m just used to it even though I’ve been a logic user since the E-Magic days. CB when I first got into iOS music just gave me great results. Imma full on automation type and like tweaking everything when it makes sense. I like Thesys and Brams apps and cycle as well. The limitations are part of the magic of iOS music creation. Let me know if you find your solution please.

    I'm using loopy pro for live stuff and would love to control butter synth in a way where I can record automation and delete automation easy like I can on the Ableton push 3. Ive contacted the dev from LK so if I get an answer il let you know

  • edited March 15

    Here you go, it even records mpe https://apps.apple.com/se/app/midi-tape-recorder/id1598618004?l=en-GB

    Sorry, did a lazy read. This will only ply back what you record. Not much control

  • This app isn't AUv3, and may not be exactly what you're after. But if you enjoy automating MIDI, this is a pretty damn fun and visual way of doing it:

    https://apps.apple.com/gb/app/ribn/id1413777040#:~:text=Ribn is a MIDI controller,kind of like complex LFOs.

  • I also recorded a quick video of an extreme way of using it a few years back:

  • If you can scratch the AUv3 requirement, Xequence is very capable at recording and editing (and playing back) automation, including per-note MPE and setting custom display ranges and units per controller. It also supports 16-bit controllers via (N)RPNs.

  • @theinfinate said:

    @Morgman73 said:
    Ha! Been thinking the same for many years. iOS for this type of automation it’s as much as you put in. In my experience anyways. I always revert back to AUM with the usual suspects, CB3 of course, and Logic all of a sudden. For me to really get stuff done a with a high fun factor it always ends up in Cubasis. I suppose I’m just used to it even though I’ve been a logic user since the E-Magic days. CB when I first got into iOS music just gave me great results. Imma full on automation type and like tweaking everything when it makes sense. I like Thesys and Brams apps and cycle as well. The limitations are part of the magic of iOS music creation. Let me know if you find your solution please.

    I'm using loopy pro for live stuff and would love to control butter synth in a way where I can record automation and delete automation easy like I can on the Ableton push 3. Ive contacted the dev from LK so if I get an answer il let you know

    Why don't you just record your knob movements in butter synth directly with your DAW?

  • Drambo works fantastic with recording or editing automation.

  • @theinfinate said:

    @Morgman73 said:
    Ha! Been thinking the same for many years. iOS for this type of automation it’s as much as you put in. In my experience anyways. I always revert back to AUM with the usual suspects, CB3 of course, and Logic all of a sudden. For me to really get stuff done a with a high fun factor it always ends up in Cubasis. I suppose I’m just used to it even though I’ve been a logic user since the E-Magic days. CB when I first got into iOS music just gave me great results. Imma full on automation type and like tweaking everything when it makes sense. I like Thesys and Brams apps and cycle as well. The limitations are part of the magic of iOS music creation. Let me know if you find your solution please.

    I'm using loopy pro for live stuff and would love to control butter synth in a way where I can record automation and delete automation easy like I can on the Ableton push 3. Ive contacted the dev from LK so if I get an answer il let you know

    I also use loopy pro, and am also waiting for automation.
    Midi loops are coming to loopy some time this year which should hopefully solve this issue.
    Until then for automation in loopy i use follow actions on a clip.
    Basically you create a knob that is cc mapped to the parameter you want to control, then create a new donut that has i bit of silence recorded in it. On that donut you set a follow action to turn the knob up or down as needed and and a ramp to it for smooth motion. Then you add the donut clip to the timeline wherever you want the automated action to happen.

    It's a little Clunky, a little imprecise, a little limited, but it keeps everything in Loopy Pro and is very visual, once midi loops arrive it should be a non issue.

  • I don't have an example of something that records the MIDI and shows visual feedback on knobs/sliders, but here's a demo of a combination of two apps that work together to do it. In the video, there's a copy of BeatHawk and 4Pockets Surface Builder, and BeatHawk has a pattern with MIDI CC automation recorded (drawn in actually here, but it could be recorded in too), and sending the output to Surface Builder, where there's a knob that visually moves with the CC12 MIDI input and a slider bar that moves with the CC 13 input. I should have shown how they looked side by side so you could see the transport moving across the MIDI graph alongside the knobs and sliders moving with them.

    Surface Builder MIDI visual feedback w BeatHawk

    I know this isn't exactly what was requested, but I hope that it might be helpful in general to see what these apps can do together. Loopy or Drambo (both of which I love) might actually fit the bill, but there are others here who are much more knowledgeable that can speak to possibilities with those.

  • Besides those mentioned…

    ddtctmcc

    And the free version

    ddtctmcc-ff

  • @Tentype said:

    @theinfinate said:

    @Morgman73 said:
    Ha! Been thinking the same for many years. iOS for this type of automation it’s as much as you put in. In my experience anyways. I always revert back to AUM with the usual suspects, CB3 of course, and Logic all of a sudden. For me to really get stuff done a with a high fun factor it always ends up in Cubasis. I suppose I’m just used to it even though I’ve been a logic user since the E-Magic days. CB when I first got into iOS music just gave me great results. Imma full on automation type and like tweaking everything when it makes sense. I like Thesys and Brams apps and cycle as well. The limitations are part of the magic of iOS music creation. Let me know if you find your solution please.

    I'm using loopy pro for live stuff and would love to control butter synth in a way where I can record automation and delete automation easy like I can on the Ableton push 3. Ive contacted the dev from LK so if I get an answer il let you know

    I also use loopy pro, and am also waiting for automation.
    Midi loops are coming to loopy some time this year which should hopefully solve this issue.
    Until then for automation in loopy i use follow actions on a clip.
    Basically you create a knob that is cc mapped to the parameter you want to control, then create a new donut that has i bit of silence recorded in it. On that donut you set a follow action to turn the knob up or down as needed and and a ramp to it for smooth motion. Then you add the donut clip to the timeline wherever you want the automated action to happen.

    It's a little Clunky, a little imprecise, a little limited, but it keeps everything in Loopy Pro and is very visual, once midi loops arrive it should be a non issue.

    yeah same, I use many follow actions. I saw a cool little follow action thing on YouTube yesterday. I made a sampler instrument by recording into a single one shot clip and having follow actions create an entire keyboard scale of the one clip. So cool

  • @rs2000 said:

    @theinfinate said:

    @Morgman73 said:
    Ha! Been thinking the same for many years. iOS for this type of automation it’s as much as you put in. In my experience anyways. I always revert back to AUM with the usual suspects, CB3 of course, and Logic all of a sudden. For me to really get stuff done a with a high fun factor it always ends up in Cubasis. I suppose I’m just used to it even though I’ve been a logic user since the E-Magic days. CB when I first got into iOS music just gave me great results. Imma full on automation type and like tweaking everything when it makes sense. I like Thesys and Brams apps and cycle as well. The limitations are part of the magic of iOS music creation. Let me know if you find your solution please.

    I'm using loopy pro for live stuff and would love to control butter synth in a way where I can record automation and delete automation easy like I can on the Ableton push 3. Ive contacted the dev from LK so if I get an answer il let you know

    Why don't you just record your knob movements in butter synth directly with your DAW?

    Cause loopy pro doesn't record midi or automation yet.

  • @SevenSystems said:
    If you can scratch the AUv3 requirement, Xequence is very capable at recording and editing (and playing back) automation, including per-note MPE and setting custom display ranges and units per controller. It also supports 16-bit controllers via (N)RPNs.

    No I cant scratch that idea as I use Loopy pro for live shows. Otherwise im using ableton in my studio with heaps of vst's

  • @hghon said:
    Drambo works fantastic with recording or editing automation.

    does it work inside of Loopy?

  • @SpookyZoo said:
    This app isn't AUv3, and may not be exactly what you're after. But if you enjoy automating MIDI, this is a pretty damn fun and visual way of doing it:

    https://apps.apple.com/gb/app/ribn/id1413777040#:~:text=Ribn is a MIDI controller,kind of like complex LFOs.

    does look cool but yeah I need an auv3 plugin inside of Loopy pro

  • @theinfinate said:

    @hghon said:
    Drambo works fantastic with recording or editing automation.

    does it work inside of Loopy?

    it does. but i am not sire that anything provides the controller animation that it sounds like you want.

  • @theinfinate said:

    @SevenSystems said:
    If you can scratch the AUv3 requirement, Xequence is very capable at recording and editing (and playing back) automation, including per-note MPE and setting custom display ranges and units per controller. It also supports 16-bit controllers via (N)RPNs.

    No I cant scratch that idea as I use Loopy pro for live shows. Otherwise im using ableton in my studio with heaps of vst's

    I hear you. I use Xequence 2 with Loopy Pro in just that way. It works great, effectively replacing Loopy Pro’s sequencer with one that is more editable and can do automation. But because it’s not an AUv3, you have load a separate song file in each app. I can see why you would not want that extra complication in a live show.

  • I did an experiment to use Loopy Pro clips to record automation. It takes advantage of the fact that Loopy Pro clips are “DC coupled”, so you can store all kinds of values if you convert them to “audio”. The experiment went well, I was using a Drambo patch to convert between CC values and Audio.
    https://patchstorage.com/loopy-pro-parameter-automation-with-drambo/

  • @theinfinate said:
    Hey guys im looking for an Auv3 plugin that records automation with faders or knobs that has visual live feedback of what automation values that have been changed. I have LK which works great for recording automation but the faders dont have any feedback of automation curves so I dont know what fader etc is doing what to the sound. Im not sure if there is a way to make this work in LK or if there is any other app like cykle or thesys that work like this. Also LK doesn't have the ability to name faders to my knowledge. This is also a must have

  • Perhaps map LK midi bidirectional to some Loopy midi faders.

  • @Shabudua said:

    @theinfinate said:

    @SevenSystems said:
    If you can scratch the AUv3 requirement, Xequence is very capable at recording and editing (and playing back) automation, including per-note MPE and setting custom display ranges and units per controller. It also supports 16-bit controllers via (N)RPNs.

    No I cant scratch that idea as I use Loopy pro for live shows. Otherwise im using ableton in my studio with heaps of vst's

    I hear you. I use Xequence 2 with Loopy Pro in just that way. It works great, effectively replacing Loopy Pro’s sequencer with one that is more editable and can do automation. But because it’s not an AUv3, you have load a separate song file in each app. I can see why you would not want that extra complication in a live show.

    Note that if you have Audiobus (which you should!), there is no need to load two separate project files, as you can just load Loopy Pro + Xequence into an Audiobus session and then save / load that session.

  • @SevenSystems said:

    @Shabudua said:

    @theinfinate said:

    @SevenSystems said:
    If you can scratch the AUv3 requirement, Xequence is very capable at recording and editing (and playing back) automation, including per-note MPE and setting custom display ranges and units per controller. It also supports 16-bit controllers via (N)RPNs.

    No I cant scratch that idea as I use Loopy pro for live shows. Otherwise im using ableton in my studio with heaps of vst's

    I hear you. I use Xequence 2 with Loopy Pro in just that way. It works great, effectively replacing Loopy Pro’s sequencer with one that is more editable and can do automation. But because it’s not an AUv3, you have load a separate song file in each app. I can see why you would not want that extra complication in a live show.

    Note that if you have Audiobus (which you should!), there is no need to load two separate project files, as you can just load Loopy Pro + Xequence into an Audiobus session and then save / load that session.

    I don' think that is possible. Loopy Pro standalone isn't IAA/Audiobus compatible.

    If I understand the original post, the issue is not so much the recording and playback of the controller data -- which they say LK does fine. The issue seems to be seeing realtime visualization of the fader levels.

  • @espiegel123 said:

    @SevenSystems said:

    @Shabudua said:

    @theinfinate said:

    @SevenSystems said:
    If you can scratch the AUv3 requirement, Xequence is very capable at recording and editing (and playing back) automation, including per-note MPE and setting custom display ranges and units per controller. It also supports 16-bit controllers via (N)RPNs.

    No I cant scratch that idea as I use Loopy pro for live shows. Otherwise im using ableton in my studio with heaps of vst's

    I hear you. I use Xequence 2 with Loopy Pro in just that way. It works great, effectively replacing Loopy Pro’s sequencer with one that is more editable and can do automation. But because it’s not an AUv3, you have load a separate song file in each app. I can see why you would not want that extra complication in a live show.

    Note that if you have Audiobus (which you should!), there is no need to load two separate project files, as you can just load Loopy Pro + Xequence into an Audiobus session and then save / load that session.

    I don' think that is possible. Loopy Pro standalone isn't IAA/Audiobus compatible.

    But you can load Loopy Pro into Audiobus as an AUv3 I think?

    If I understand the original post, the issue is not so much the recording and playback of the controller data -- which they say LK does fine. The issue seems to be seeing realtime visualization of the fader levels.

    Xequence will update its internal faders based on incoming MIDI and internal sequencer data. But maybe I'm understanding the whole thing wrong :/

  • @SevenSystems said:

    @espiegel123 said:

    @SevenSystems said:

    @Shabudua said:

    @theinfinate said:

    @SevenSystems said:
    If you can scratch the AUv3 requirement, Xequence is very capable at recording and editing (and playing back) automation, including per-note MPE and setting custom display ranges and units per controller. It also supports 16-bit controllers via (N)RPNs.

    No I cant scratch that idea as I use Loopy pro for live shows. Otherwise im using ableton in my studio with heaps of vst's

    I hear you. I use Xequence 2 with Loopy Pro in just that way. It works great, effectively replacing Loopy Pro’s sequencer with one that is more editable and can do automation. But because it’s not an AUv3, you have load a separate song file in each app. I can see why you would not want that extra complication in a live show.

    Note that if you have Audiobus (which you should!), there is no need to load two separate project files, as you can just load Loopy Pro + Xequence into an Audiobus session and then save / load that session.

    I don' think that is possible. Loopy Pro standalone isn't IAA/Audiobus compatible.

    But you can load Loopy Pro into Audiobus as an AUv3 I think?

    If I understand the original post, the issue is not so much the recording and playback of the controller data -- which they say LK does fine. The issue seems to be seeing realtime visualization of the fader levels.

    Xequence will update its internal faders based on incoming MIDI and internal sequencer data. But maybe I'm understanding the whole thing wrong :/

    Loopy Pro as an AU can't (true of all AU) can't load other AU. OP's use case is Loopy Pro as a host for other AU.

  • @espiegel123 said:

    @SevenSystems said:

    @espiegel123 said:

    @SevenSystems said:

    @Shabudua said:

    @theinfinate said:

    @SevenSystems said:
    If you can scratch the AUv3 requirement, Xequence is very capable at recording and editing (and playing back) automation, including per-note MPE and setting custom display ranges and units per controller. It also supports 16-bit controllers via (N)RPNs.

    No I cant scratch that idea as I use Loopy pro for live shows. Otherwise im using ableton in my studio with heaps of vst's

    I hear you. I use Xequence 2 with Loopy Pro in just that way. It works great, effectively replacing Loopy Pro’s sequencer with one that is more editable and can do automation. But because it’s not an AUv3, you have load a separate song file in each app. I can see why you would not want that extra complication in a live show.

    Note that if you have Audiobus (which you should!), there is no need to load two separate project files, as you can just load Loopy Pro + Xequence into an Audiobus session and then save / load that session.

    I don' think that is possible. Loopy Pro standalone isn't IAA/Audiobus compatible.

    But you can load Loopy Pro into Audiobus as an AUv3 I think?

    If I understand the original post, the issue is not so much the recording and playback of the controller data -- which they say LK does fine. The issue seems to be seeing realtime visualization of the fader levels.

    Xequence will update its internal faders based on incoming MIDI and internal sequencer data. But maybe I'm understanding the whole thing wrong :/

    Loopy Pro as an AU can't (true of all AU) can't load other AU. OP's use case is Loopy Pro as a host for other AU.

    Ah alright, sorry then! I'm no AU expert as is blatantly obvious 😂

  • edited March 17

    @theinfinate said:
    Hey guys im looking for an Auv3 plugin that records automation with faders or knobs that has visual live feedback of what automation values that have been changed. I have LK which works great for recording automation but the faders dont have any feedback of automation curves so I dont know what fader etc is doing what to the sound. Im not sure if there is a way to make this work in LK or if there is any other app like cykle or thesys that work like this. Also LK doesn't have the ability to name faders to my knowledge. This is also a must have

    Just want to clarify what you are looking for. Here's what I understand so far - I'll just use faders as examples:

    "faders or knobs that has visual live feedback of what automation values that have been changed.

    Would the faders in question be controlling the behavior of another instrument or app during the recording process, and then moving of their own accord on the display during playback of the recorded automation? Or would the automation be recorded elsewhere and then the faders would be only providing feedback on the MIDI automation data that has been recorded?

    Would the faders be pre-configured to received certain values before recording and playback, for example, CC 15 on one fader and CC 10 on another, etc.? How many faders and knobs would be needed? Will the faders be receiving on different MIDI channels?

    Would it be acceptable to have the faders available in one app and displaying activity during playback of recorded automation but have the recording being done by another app? In other words, one AUv3 module loaded for the faders, and another AUv3 module loaded in Loopy for the recording?

    **Edit: Quoted text was too large - had to change formatting."

  • @theinfinate Thanks man. I haven’t been on here much lately but yes please keep me in the loop.

Sign In or Register to comment.