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 DAW

191012141548

Comments

  • @dwrae sorry to spam. Last request re:midi. It would be extremely useful to have a ‘refresh midi connections’ button (or some automated way of doing this). Right now if you launch an app after you’ve launched AEMS you have to save the project, quit, restart and the load the project just to get the new app show up in the list of available midi connections.

    Not a huge deal, but with midi debugging the less restarting the better!

  • edited August 2018

    @Matt_Fletcher_2000 said:

    @Littlewoodg said:

    @Matt_Fletcher_2000 said:

    @Littlewoodg said:

    @Janosax said:
    How do you compare GB to AEM on iPhone?

    What seems to me the most interesting is full automatation including AU parameters, AU midi support, fast GUI without animations, greater midi editing capabilities, lot of tracks visible at the same time... what else?

    What misses is only loop mode. Even loop import with timestretch capabilities with snap to grip etc could be good enough.

    Is there any freeze/merge feature in AEM?

    I love GB but recent undo/redo bug kills it, and they’re too slow to fix anything.

    AEM dev seems much faster and reactive, this is very important for iOS apps.

    Now that virtual midi is implemented, it’s possible to use a midi controller that uses midi cell/loops like Genome or modstep to add a clip launch performance dimension to AEM...

    Only AEM doesn’t have Link so this might be tricky? Have you tried it with midi sync? Or just pressing play at the right time :)?

    So far I’ve tried only Genome, and used the “1, 2, 3, go” method

    It occurs to me now that Genome has clock in, as well as clock out, not sure if AEM plays with others clockwise

    need to do some more goofing...will check in here if something clicks

    Personally I think DAWs should take Gadget’s approach to Link and just add it anyway and to hell with rendered audio not timestretching if you change the tempo. I’m sure mostly in ‘production’ using a DAW you have a set tempo for your project so you’re not going to be wanging the tempo around!

    Worked nicely in BM2...and 3
    Link here too would be sweet.

    So far hitting the record in AEM at the right time is as good as sync gets (and dragging the tracks’ midi notes to the right place after).
    Hosting in AB3, the two apps can sit in input slot (to use the control panel with go and Rec near each other when in the AEM or genome gui). Audiobus “play” syncs starts Genome via Link, so its the same number of buttons to hit at once but with AB they’re on the same screen

  • @Matt_Fletcher_2000 said:

    @Littlewoodg said:

    @Matt_Fletcher_2000 said:

    @Littlewoodg said:

    @Janosax said:
    How do you compare GB to AEM on iPhone?

    What seems to me the most interesting is full automatation including AU parameters, AU midi support, fast GUI without animations, greater midi editing capabilities, lot of tracks visible at the same time... what else?

    What misses is only loop mode. Even loop import with timestretch capabilities with snap to grip etc could be good enough.

    Is there any freeze/merge feature in AEM?

    I love GB but recent undo/redo bug kills it, and they’re too slow to fix anything.

    AEM dev seems much faster and reactive, this is very important for iOS apps.

    Now that virtual midi is implemented, it’s possible to use a midi controller that uses midi cell/loops like Genome or modstep to add a clip launch performance dimension to AEM...

    Only AEM doesn’t have Link so this might be tricky? Have you tried it with midi sync? Or just pressing play at the right time :)?

    So far I’ve tried only Genome, and used the “1, 2, 3, go” method

    It occurs to me now that Genome has clock in, as well as clock out, not sure if AEM plays with others clockwise

    need to do some more goofing...will check in here if something clicks

    Personally I think DAWs should take Gadget’s approach to Link and just add it anyway and to hell with rendered audio not timestretching if you change the tempo. I’m sure mostly in ‘production’ using a DAW you have a set tempo for your project so you’re not going to be wanging the tempo around!

    +1000

  • Ok. So I’ve now done some rather extensive MPE testing...

    For testing I’ve got a Roli Lightblock and also the ‘Aftertouch’ app (Aftertouch • 3D MIDI Controller by Kevin Nelson - https://itunes.apple.com/gb/app/aftertouch-3d-midi-controller/id1133701231?mt=8)

    What I’ve found is (basically we’re nearly there - but not quite!)

    1. ‘Midi Instrument Tracks’ are not recording multi-channel midi. Only ‘Midi tracks’ are. This explains why those hosting MPE AUs in AEM like Roli Noise are not hearing the Seaboard playing / recording correctly.
    2. For some very annoying reason both my Lightblock and the Aftertouch app are not having their midi notes heard or recorded when AEM is connected to their ‘Lightblock Bluetooth port’ or ‘Aftertouch Source port’ respectively. Pitchbend, Aftertouch and cc74 (slide) are all being picked up and recorded. But just not the damn notes!
    3. The fix to 2 is to route through the Midiflow app, by having midiflow listen to the Lightblock or Aftertouch and then creating a custom midiflow output port and having AEMS then connect to the custom midiflow output port. This then means notes, velocity, ccs and pitchbend get sent through and recorded in AEMS. But - even more annoyingly - for some unknown reason this means channel pressure gets lost somehow and isn’t heard or recorded by AEMS! So currently, with the midiflow workaround, channel pressure gets lost.
    4. The new ‘virtual midi input’ port for AEMS (it now has its own port that other apps can connect to) doesn’t record midi as far as I can make out. It listens for it, and you can hear the midi being played by the instrument assigned to the track. But after you check what’s been recorded - no midi is there in the midi clip.

    Hope the above is helpful. (iPhone 6s plus iOS 11).

  • edited September 2018

    @dwrae Further digging around...

    It seems that ‘channel pressure’ (per channel) is actually different to ‘polyphonic key pressure’ (per key). Apps like Roli Noise and Volt appear to respond to both.

    Usefully, the ‘Aftertouch app’ allows you to send either (although you can only send ‘polyphonic key pressure’ if you restrict it to be sending on 1 midi channel).

    I would guess that AEMS is listening for ‘polyphonic key pressure’ rather than ‘channel pressure’ because when I send the former to it from the Aftertouch app it works, and the latter doesn’t. But something else might of course be responsible for this.

    I don’t know what the Roli Lightblock is sending, perhaps ‘polyphonic key pressure’ because it shows up in the midi clip when AEMS connects directly to it. But unfortunately a side effect is that notes seem to get filtered out when a direct connection is made. (Just an idea, but maybe this is to do with the order things are sent in? Eg Roli might be sending pressure and CC’s before notes, and AEMS might not like this and is therefore dropping the notes?)

    Finally I would guess that somehow going via midiflow corrects the dropped notes issue (maybe down to my order idea?) but introduces a problem receiving ‘pressure’. I’m pretty sure MidiFlow converts ‘polyphonic key pressure’ into ‘channel pressure’ and thus this is no longer picked up in AEMS.

    Here’s some more details on the differences between the two types of pressure:

    http://www.audiomasterclass.com/newsletter/the-difference-between-channel-aftertouch-and-polyphonic-aftertouch

    The solution would seem to be to get AEMS to record, per midi channel, both ‘channel pressure’ (per channel) and ‘polyphonic key pressure’ (per key) if possible.

    Hope the above is useful and appologies if ive got anything wrong!

  • @Matt_Fletcher_2000 said:

    @DCJ said:
    Anyone else got MPE working after the latest update? I got channel pressure active, but Roli Noise isn’t responding in true MPE fashion. No glide and definitely not responding per note.

    On a positive note, I’m loving seeing the development of this and will purchase the Pro extension to support.

    Out of interest are you using Roli Noise hosted as a AU?

    Yup.

  • wimwim
    edited September 2018

    @ExAsperis99 said:

    @Audiojunkie said:

    @ExAsperis99 said:
    OK, forgive me, but I read this thread early on and decided it didn't apply to me. Now, a gazillion pages later, I'm feeling like I need to catch up. But do I?

    • Is this DAW a contender with Cubasis and BM3?

    Absolutely! It is very similar to Auria.

    • Is it especially lightweight/nimble/inexpensive?

    It is not only lightweight, but very inexpensive. Also, it is the only DAW in its class that supports iPhones.

    • Is it a disaster that has infuriated forum members?

    Not that I've heard of.

    • Is it super innovative?

    Not necessarily innovative. Everything it has has existed before. The key phrase would be: Very well laid out. Or possibly: Very easy to get work done in.

    Thank you.
    So to simply glide over ten pages of comments, this seems valuable to someone who isn't already invested in a DAW or as a DAW for iPhone use?

    That's seems like it sums it up from my perspective. I don't see anything major that it brings if you're already happy with Cubasis or Auria. But, having something for iPhone is a big deal.

    If someone didn't already have a DAW it certainly is no slouch, and is worth considering.

  • @Matt_Fletcher_2000 said:

    @Littlewoodg said:

    @Matt_Fletcher_2000 said:

    @Littlewoodg said:

    @Janosax said:
    How do you compare GB to AEM on iPhone?

    What seems to me the most interesting is full automatation including AU parameters, AU midi support, fast GUI without animations, greater midi editing capabilities, lot of tracks visible at the same time... what else?

    What misses is only loop mode. Even loop import with timestretch capabilities with snap to grip etc could be good enough.

    Is there any freeze/merge feature in AEM?

    I love GB but recent undo/redo bug kills it, and they’re too slow to fix anything.

    AEM dev seems much faster and reactive, this is very important for iOS apps.

    Now that virtual midi is implemented, it’s possible to use a midi controller that uses midi cell/loops like Genome or modstep to add a clip launch performance dimension to AEM...

    Only AEM doesn’t have Link so this might be tricky? Have you tried it with midi sync? Or just pressing play at the right time :)?

    So far I’ve tried only Genome, and used the “1, 2, 3, go” method

    It occurs to me now that Genome has clock in, as well as clock out, not sure if AEM plays with others clockwise

    need to do some more goofing...will check in here if something clicks

    Personally I think DAWs should take Gadget’s approach to Link and just add it anyway and to hell with rendered audio not timestretching if you change the tempo. I’m sure mostly in ‘production’ using a DAW you have a set tempo for your project so you’re not going to be wanging the tempo around!

    And MIDI clock sync in and out, which is just as important when working with non-Link-compatible hardware or software.

    But it's not easy to implement in a DAW. Ableton and Logic do it quite well, but there are limitations that everyone should be aware of when using LINK and/or MIDI Clock in a DAW with audio tracks.

    MIDI tracks are simple: Every event has a clear timestamp and the number of events are very limited compared to audio samples. Stretching or compressing the event grid with tempo changes is a natural thing and the audio that is produced from them will still remain in correct pitch.

    Audio tracks are a completely different story.
    "To hell with rendered audio not timestretching" does not mean you can ignore the audio tracks. Most people will expect the tracks to not drift off-beat and to be played at the correct pitch. Some people also expect the slave-clocked DAW to follow tempo changes "immediately" which is even harder.

    With both LINK and MIDI Clock you could of course pre-set a tempo in the DAW that follows LINK/MIDI Clock in the case you don't have major tempo changes and have the DAW only accept minor drifts of MIDI clock, ignore sporadic clock pulses too far away and interpolate them using an internal, phase-locked clock generator which is what some of those "magic MIDI Clock processors" do.
    Still, you have to find a solution for the audio tracks to play in an acceptable way.
    As re-pitching usually isn't an option (except for drums, fx and non-tonal sounds), you'll be forced to do some kind of time-stretching/compression.
    In the case of a relatively steady clock without major tempo changes (and that's 99.9% of the songs today), time corrections can often be done by rather simple, transient-aware algorithms.

    Anyway, both the clock smoothing and the time correction of audio tracks have to be done properly or people will either complain or just not use the sync features.

    Gadget is a bad example because it does not touch the audio tracks at all, effectively making rhythmic audio tracks unusable at different tempi.

  • @Audiojunkie said:
    I don't believe the Mute function in this case suspends the CPU and releases the RAM. I think that the CPU/RAM using instrument itself must be removed in order to reduce the CPU/RAM footprint. That's why I recommended a "Silent" Soundfont in my instructions above. :smile: Maybe @dwrae can correct me if I'm wrong? Testing should also confirm this. :smile:

    No, mute won't help since it must be instantly possible to unmute.

  • @rs2000 said:

    On a positive note, I’m loving seeing the development of this and will purchase the Pro extension to support.

    Given that @dwrae has just recently ordered a Seaboard just for the sake of adding MPE, I wonder how he managed to add it so fast at all.

    In all honesty, I ordered it because it didn't work at all (no events were coming in), but now I have it, it's worth looking into MPE. :)

  • @tja said:
    Yes, i only played around with the GM, not with other Apps.

    Ok, and which buttons are you referring to? You indeed cannot use the mixer channel at the left while playing notes. But I haven't come across any noticable delay when playing the keyboard, chords or not, so I'm not sure what to fix here.

    I use "Edit" from the menu and then select a red range in the upper track.

    Ah, you are actually drawing a new clip that way, so it's not a range (which what caused the confusion with me).

    More clear?

    Yes, now back to your original problem:

    " but the former selection does not seem to play a role anymore ... i would expect the Piano Roll to be the number of bars i selected initially. Also this initial selection is not visible as range or as markers at all! And finally, even as you cannot see such things, it seems to be a problem when you then add notes outside of the original selection"

    When you create a clip like that, you enter the piano roll. The bars/clip you have created is visible with a white background. When you scroll right, you will see that the part outside the clip is drawn with a red background.

  • @Matt_Fletcher_2000 said:

    @dwrae said:

    @Matt_Fletcher_2000 said:
    If you have time, maybe check the ‘split midi tracks’ function. It basically sort of works, but some resulting ‘split’ midi tracks seem to have notes/automation of more than one colour. Denoting that they are on different midi channels. But then surely they should have been split into different tracks? So I think there maybe be a few bugs there.

    If you have a project file or MIDI file that reproduces this, please let me know.

    I will send you the project in question. Do you have a support email I should use?

    Please send it to [email protected], thanks!

  • @dwrae said:

    @Audiojunkie said:
    I don't believe the Mute function in this case suspends the CPU and releases the RAM. I think that the CPU/RAM using instrument itself must be removed in order to reduce the CPU/RAM footprint. That's why I recommended a "Silent" Soundfont in my instructions above. :smile: Maybe @dwrae can correct me if I'm wrong? Testing should also confirm this. :smile:

    No, mute won't help since it must be instantly possible to unmute.

    And changing the instrument to be a ‘silent soundfont’ doesn’t really help either because it means you lose all the settings (the patch) on the actual instrument/AU - and have to remember them somehow.

  • @dwrae said:

    @rs2000 said:

    On a positive note, I’m loving seeing the development of this and will purchase the Pro extension to support.

    Given that @dwrae has just recently ordered a Seaboard just for the sake of adding MPE, I wonder how he managed to add it so fast at all.

    In all honesty, I ordered it because it didn't work at all (no events were coming in), but now I have it, it's worth looking into MPE. :)

    Cool!

    To summarise my overly long emails above on MPE.

    • you need to rectify the problem that seems to be AEMS listening for ‘polyphonic key pressure’ but not ‘channel pressure’
    • Currently only ‘midi tracks’ are recording multi-channel midi. You need to enable this for ‘midi instrument tracks’
    • When using the new AEMS midi port nothing seems to get recorded
    • Midi notes seem to be being filtered out when AEMS connects directly to the Lightblock
  • The user and all related content has been deleted.
  • The user and all related content has been deleted.
  • edited September 2018

    @tja
    If I draw outside the white area I get:

  • The user and all related content has been deleted.
  • @Littlewoodg said:
    @tja
    If I draw outside the white area I get:

    Just say "Yes".

  • The user and all related content has been deleted.
  • How do you delete a track?

  • @Janosax said:
    How do you delete a track?

    Long press on the track and more options come up :smile:

  • edited September 2018

    @Audiojunkie said:

    @Janosax said:
    How do you delete a track?

    Long press on the track and more options come up :smile:

    Thanks you!!

    Is it possible to copy paste automation?

    I want to duplicate those 4 bars on 32 bars.

  • @tja said:
    @rs2000 We seem to missunderstand.

    I think so ;)

    This question comes, when you quit the Piano Roll.

    While editing, the situation is as i wrote - you can edit notes outside the original region but cannot play them.

    It does not help to be forced to exit, expand the region, just to enter again repeat the same.

    So, i am asking, what the goal of that construction is.

    And if there is no real goal, why it could not be changed - for a better thing to all.

    What's wrong with that?
    You're not forced to exit the piano roll, that's why you're asked when done editing, and usually you'd create longer clips in the first place: EDIT > Tap and drag to the length you want > The piano roll opens automatically. (make sure the grid is enabled)
    Let's suppose we have a number of clips of same or different length within one MIDI track and you're editing the first of two adjacent clips.
    When you enter notes in the red area showing the range outside the clip, would you expect AEM to extend the clip length automatically so the clips overlap?

  • The user and all related content has been deleted.
  • edited September 2018

    I wish someone made some better videos for this thing, I.e. “One foot in front of the other” style. I find the existing ones a bit hard to follow.

  • Just started playing around with this. As usual when trying a new DAW, everything is a bit weird (no back button from the piano roll, just the next button?)

    However it didn’t take long to get used to the basics. I love it’s simplicity and focus on supporting au, IAA etc.

    One thing - all my drum apps are IAA I think, apart from BeatHawk which doesn’t seem to load properly. What is everyone using?

  • @rs2000 said:

    @Littlewoodg said:
    @tja
    If I draw outside the white area I get:

    Just say "Yes".

    I usually do :)

  • @Janosax said:

    @Audiojunkie said:

    @Janosax said:
    How do you delete a track?

    Long press on the track and more options come up :smile:

    Thanks you!!

    Is it possible to copy paste automation?

    I want to duplicate those 4 bars on 32 bars.

    @dwrae do you think it’s possible to add selection and copy paste features to automations?

  • Also, can you automate AU instrument knobs? Is that possible on any daw at the mo?

Sign In or Register to comment.