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.

What is your ideal features list for iOS DAW ?

2

Comments

    • Ability to save FX chain or FX+instrument as presets
    • For iPad specifically: an expressive, configurable touch keyboard, including MPE support and optional pitchbend and modwheels. Basically Animoog's keyboard.
    • Each track/instrument should remember its keyboard settings, so that I don't have to keep changing octaves or modes if I switch from a bass instrument to lead or drums.
    • Shortcuts to switch across instruments/tracks, ideally MIDI-mappable.
    • Built-in modulators (LFOs, envelopes, envelope followers) that can be connected directly to AUv3 params, no MIDI CC required.
    • Nice-to-have: built-in modular environment like Bitwig's Grid
  • @ecou said:
    Must have:

    • Stability
    • Do what it says on the can without crashing

    Right? Logic Pro is great - until it turns off monitoring and unfreezes all tracks if I hit the “back” button when using my audio interface. That and no AUv3 multi-out fx

  • I started a couple use case specific threads before, so this copy/paste may be a bit redundant.

    My desired DAW supports:
    Timeline w/ audio and MIDI recording tracks
    AUv3 plugin hosting - instrument, effect, and MIDI
    Multi-out plugin support (instruments and effects)
    MIDI routing between tracks
    MPE
    Piano roll
    Mixer

    This was more guitar specific:
    Multi-core audio engine
    Audio tracks + timeline
    Multi-out AUv3 effects
    48 kHz and 96 kHz sample rates
    Buffer size ≤ 128
    Works with MIDI Guitar 2 (low priority)
    Retroactive recording

    I don’t really care about built in instruments or effects, though stuff like Mastering Assistant in Logic Pro are very useful.

  • Sorry for the triple post, but shameless plug for anyone who wants to play DAW feature set Bingo I’d always appreciate help filling in this Google Sheets form:
    https://docs.google.com/spreadsheets/d/1bWcfjLnDrx1lSJHXxEEsxLnEloDUlpTh/edit?usp=drivesdk&ouid=105164582052369675956&rtpof=true&sd=true

  • koala, but with auv3 slots.

  • edited March 30

    Definitely a fun thought experiment, I get to hear about features I didn’t know I wanted.

    My thinking about the iOS hosts has been that it’s a game of rock/paper/scissors, one is better than the other each in its turn with no winner.

    And even though I know this I don’t accept it. Is that unadult?

    And then there is the matter of desktop features, which often has me shunning all of iOS in favor of the pro hosts I have on my touch pc.

    So I use pretty much all of them on both platforms, each in turn. I even bought into Android for the coolshit on there.

    On iOS I would squish at least 4 of them together to get everything I already wanted and throw in a pc host or two

    Yeah having said all that MTS and FLSM cover most stuff I want, and a lot of what people are asking for here. Plus BM3…and I just downloaded Auria Pro the other day and loaded it with the huge EXS piano I love. Damnit I hope I grow up some day.

  • Pretty much everything @vlaoladis said, and I quote:

    Tempo automation
    Variable time signatures (per clip/region)
    AUv3 host (and I don’t need builtin fx, instruments, whatever)
    Xequnce2-style piano roll with convenient grips + Apple Pencil support and overall focus on real convenience
    SAND-like versatile ghost track selection
    SAND-like clip-based arrangement and per-track-per-clip export ability (additionally to regular per-track and mixdown)
    Automation lanes for AUv3 instrument and FX params and MIDI CC
    Copypaste for automations
    Parameter curves mapping for each lane right in the DAW (like in Camelot/SWAM parameter curves, ideally with ability to draw or edit the curve flexible like in Drambo)
    UI controls to record automation on the fly (Ideally several faders with ability to change their behavior and settings like in Xequence2 AU). And with clever overwrite-part-on-the-fly-while-holding-the-fader modes like latches in Logic pro and Loopy pro
    Multi out instruments support
    Logic-like track configuration presets
    MIDI FX with AUM style complex routings, channel filtering, remapping. Ideally if it allows shared FX chain for several tracks
    Sidechains, FX sends, Groups (with fx parameter automations)

    Plus Plugin Delay Compensation, and easy comping of audio tracks (automatic crossfades).
    I don't want built-in instruments as I have already chosen the ones I like. A few built-in staple effects would be fine- EQ, compressor.

  • I know you don't want to hear it, but NS2 with audio tracks that functionally meet the quality and capability of NS2 as we know it would be killer. Maybe a few extras like control of AUv3 FX and I don't know what else. I don't remember what else NS2 is missing. LOL!

  • @anickt said:
    I know you don't want to hear it, but NS2 with audio tracks that functionally meet the quality and capability of NS2 as we know it would be killer. Maybe a few extras like control of AUv3 FX and I don't know what else. I don't remember what else NS2 is missing. LOL!

    BTW, NS2 was my first iOS DAW and it was quite close to what I need, excluding some absolutely unexplainable issues like lack of midi cc support (including the CC64 that was a musthave for piano apps). And I remember some limits with midi routing (that exist everywhere excluding Loopy Pro and AUM)

  • The main feature I would look for in any iOS DAW like experience is great audio and midi export functions. I say this, because, as yet, no iPad DAW has given me what I get from my Mac and controllers experience. So, for myself any audio or midi I make on an iPad will be needed to be sent to my Macs.

    To be fair, Ive pretty much given up on iPads as my main music making devices, as the greatest limiting factor in my opinion is the single USB C port. My iPad is more of a musical playground, sound and idea generator, so personally I'm more interested in 'DAWs' that have features that put invention and creativity above trying to be an all encompasing 'DAW'. I just dont think that iPads are best suited to the usual DAW like experience.

    I think that in the future a creative playground will come along that gives us the best of AUM and other iPad music making experiences that are only possible on a touch screen will really shine a light back here for myself, but as of now my iPad just isnt as great for my needs as my Mac DAWs like Ableton, Bitwig, Fender Studio Pro and Reason.

    Thinking about Reason though, something similar would be fun on an iPad, if it was designed for iPad from the ground up.

  • I’d like to see more Apple Pencil integration and touch controls. Mirack lets you set actions to Apple Pencil - I know one of them is undo. Pen2bow acts like a bow on a stringed instrument. Not Apple Pencil specific but anything taking advantage of the touch screen like TouchScaper, GeoShred, or the touch chords and guitar surface in Logic Pro. Though good MIDI support and my collection of AUv3 controllers would make that redundant.

  • @Samu said:
    Integrated sampler (think Logics QuickSampler, Abletons Simpler or the Cubase Sampler Track) with direct access to any 'audio source' (audio-files, plug-in/track outputs & hardware inputs) being used within the project.

    If Cubasis only add the sample track, would be a game changer on IOS

  • @JuniorPops said:

    @Samu said:
    Integrated sampler (think Logics QuickSampler, Abletons Simpler or the Cubase Sampler Track) with direct access to any 'audio source' (audio-files, plug-in/track outputs & hardware inputs) being used within the project.

    If Cubasis only add the sample track, would be a game changer on IOS

    That is why I have been mentioning it from time to time and hopefully it has by now caught the attention of @LFS and is at least considered for future implementation…

  • edited April 1

    @Samu said:

    @JuniorPops said:

    @Samu said:
    Integrated sampler (think Logics QuickSampler, Abletons Simpler or the Cubase Sampler Track) with direct access to any 'audio source' (audio-files, plug-in/track outputs & hardware inputs) being used within the project.

    If Cubasis only add the sample track, would be a game changer on IOS

    That is why I have been mentioning it from time to time and hopefully it has by now caught the attention of @LFS and is at least considered for future implementation…

    A feature I would love to see in both Cubasis and Auria Pro (it lives, at least on my device)

    I pestered the MTS dev Mr Bremmers to add this and he did. I don’t think I was the only one to pester but I still take full credit. :D His implementation is idiosyncratic as usual but I think it’s very powerful

  • @FizzyLizzy27 said:
    I started a couple use case specific threads before, so this copy/paste may be a bit redundant.
    48 kHz and 96 kHz sample rates

    This is massive problem on iOS and it drives me nuts, cause basically almost all developers of plugins don’t give shit about what sample rate of processing demands host app from them and keep just locked to defaul device sample rate .. so, 96khz possible only if you connect trully 96khz audio card (and even it that case it’s not guaranteed if iOS decides to keep being locked on 48khz)

    So until plugin developers will not start doing their job properly, true internal processing on sample rates like 96khz is no go on this platform.

    Even current hosts which keep you choose “96khz” doesn’t really switch internal processing - they just kindly ask iOS “hey dude, can you set this sample rate plz ?”.. An iOS response is usually “fuck you”

    If any host tries to really natively swich all internal processimg to 96khz (like all big desktop daws are doing it) you notice it quickly - basically 99% of AUv3 plugins will play wrong pitch or other sound artifacts.

    It’s all in there, in Apple API, to do this properly on plugin’s side.

    Plugin developers just don’t give shit :-(

    It’s really frustrating.

  • @anickt said:
    I know you don't want to hear it, but NS2 with audio tracks that functionally meet the quality and capability of NS2 as we know it would be killer. Maybe a few extras like control of AUv3 FX and I don't know what else. I don't remember what else NS2 is missing. LOL!

    I am totally agnostic in this thread, no opinion / no prefference .. i want just hear otherrs .. massive list of requests which 80% will be never realised :-)))) Nice thread, thanks to all participants !

  • edited April 1

    @vlaoladis
    I’m really close to load Claude Code with all modern LLM bells ans whistles and vibecode such thing for myself

    Until you don't have years of deep studying of all iOS api related stuff and DSP coding and at leatt 15+ years of coding experience in large projects (ideally team invloved) then i wouldn't suggest to go this way :-) It's very hard task even with Claude Code .. it's not usual "let's vibe code some small app" to work at such large project - it's more like "agentic engineering" and you need to have really deep understanding what is going on otherwise it's very soon dead end ;)

    believe me, i know what i am talking about, using Claude Code daily on large project ...

  • @dendy said:

    @FizzyLizzy27 said:
    I started a couple use case specific threads before, so this copy/paste may be a bit redundant.
    48 kHz and 96 kHz sample rates

    This is massive problem on iOS and it drives me nuts, cause basically almost all developers of plugins don’t give shit about what sample rate of processing demands host app from them and keep just locked to defaul device sample rate .. so, 96khz possible only if you connect trully 96khz audio card (and even it that case it’s not guaranteed if iOS decides to keep being locked on 48khz)

    So until plugin developers will not start doing their job properly, true internal processing on sample rates like 96khz is no go on this platform.

    Even current hosts which keep you choose “96khz” doesn’t really switch internal processing - they just kindly ask iOS “hey dude, can you set this sample rate plz ?”.. An iOS response is usually “fuck you”

    If any host tries to really natively swich all internal processimg to 96khz (like all big desktop daws are doing it) you notice it quickly - basically 99% of AUv3 plugins will play wrong pitch or other sound artifacts.

    It’s all in there, in Apple API, to do this properly on plugin’s side.

    Plugin developers just don’t give shit :-(

    It’s really frustrating.

    This happened last night with me. I opened AUM, opened FAC Bandit 2, and noticed it was set to 96 kHz but running at 48. Nothing else was running, but I think I had Indian Drummer open prior and Lumbeat apps have given me issue on sample rate before. Had to restart the iPad to get it to reset. I’d rather have a plugin be unable to load at 96 than to force everything else down to 48.

  • @FizzyLizzy27 said:
    This happened last night with me. I opened AUM, opened FAC Bandit 2, and noticed it was set to 96 kHz but running at 48. Nothing else was running, but I think I had Indian Drummer open prior and Lumbeat apps have given me issue on sample rate before. Had to restart the iPad to get it to reset. I’d rather have a plugin be unable to load at 96 than to force everything else down to 48.

    At is is so simple ! It's literally few steps which developers needs to implement properly and their plugin will be totally sample-rate independent from device, ready to listen host's sample rate.. But even after all those years of AUv3 standard developers of plugins are suffering by selective blindness when reading AUv3 specification :((

  • @dendy said:

    @vlaoladis
    I’m really close to load Claude Code with all modern LLM bells ans whistles and vibecode such thing for myself

    Until you don't have years of deep studying of all iOS api related stuff and DSP coding and at leatt 15+ years of coding experience in large projects (ideally team invloved) then i wouldn't suggest to go this way :-) It's very hard task even with Claude Code .. it's not usual "let's vibe code some small app" to work at such large project - it's more like "agentic engineering" and you need to have really deep understanding what is going on otherwise it's very soon dead end ;)

    believe me, i know what i am talking about, using Claude Code daily on large project ...

    I've developed many things in areas from self-driving cars to regular enterprise backend systems in different companies with ~1k developers :) So I know exactly what you are talking about and still the main reason I'm not diving to this idea and iOS field in general is that I'm doing this crap in my daytime job and don't want to do almost the same crap in my free time :smile:

    So believe me, I know what you are talking about as well

  • @vlaoladis said:

    @dendy said:

    @vlaoladis
    I’m really close to load Claude Code with all modern LLM bells ans whistles and vibecode such thing for myself

    Until you don't have years of deep studying of all iOS api related stuff and DSP coding and at leatt 15+ years of coding experience in large projects (ideally team invloved) then i wouldn't suggest to go this way :-) It's very hard task even with Claude Code .. it's not usual "let's vibe code some small app" to work at such large project - it's more like "agentic engineering" and you need to have really deep understanding what is going on otherwise it's very soon dead end ;)

    believe me, i know what i am talking about, using Claude Code daily on large project ...

    I've developed many things in areas from self-driving cars to regular enterprise backend systems in different companies with ~1k developers :) So I know exactly what you are talking about and still the main reason I'm not diving to this idea and iOS field in general is that I'm doing this crap in my daytime job and don't want to do almost the same crap in my free time :smile:

    So believe me, I know what you are talking about as well

    :+1:

  • @vlaoladis said:

    @dendy said:

    @vlaoladis
    I’m really close to load Claude Code with all modern LLM bells ans whistles and vibecode such thing for myself

    Until you don't have years of deep studying of all iOS api related stuff and DSP coding and at leatt 15+ years of coding experience in large projects (ideally team invloved) then i wouldn't suggest to go this way :-) It's very hard task even with Claude Code .. it's not usual "let's vibe code some small app" to work at such large project - it's more like "agentic engineering" and you need to have really deep understanding what is going on otherwise it's very soon dead end ;)

    believe me, i know what i am talking about, using Claude Code daily on large project ...

    I've developed many things in areas from self-driving cars to regular enterprise backend systems in different companies with ~1k developers :) So I know exactly what you are talking about and still the main reason I'm not diving to this idea and iOS field in general is that I'm doing this crap in my daytime job and don't want to do almost the same crap in my free time :smile:

    So believe me, I know what you are talking about as well

    Programming a DAW sounds like a nightmare - especially using Claude. I’ve found autonomous agents work well for starting a project, but maintaining consistency in a codebase isn’t its strength.

  • Maybe I'm a weird person who does things differently, but it seems to me every DAW should already have adjustable limiting/saturation/clipping built into each channel and the master without having to bring that stuff in yourself.

  • @setAI said:
    Maybe I'm a weird person who does things differently, but it seems to me every DAW should already have adjustable limiting/saturation/clipping built into each channel and the master without having to bring that stuff in yourself.

    Cubasis sort of does this by having its Channel Strip preloaded on every channel along with a Studio EQ. Both are off by default.

  • edited April 1

    @FizzyLizzy27 said:

    @vlaoladis said:

    @dendy said:

    @vlaoladis
    I’m really close to load Claude Code with all modern LLM bells ans whistles and vibecode such thing for myself

    Until you don't have years of deep studying of all iOS api related stuff and DSP coding and at leatt 15+ years of coding experience in large projects (ideally team invloved) then i wouldn't suggest to go this way :-) It's very hard task even with Claude Code .. it's not usual "let's vibe code some small app" to work at such large project - it's more like "agentic engineering" and you need to have really deep understanding what is going on otherwise it's very soon dead end ;)

    believe me, i know what i am talking about, using Claude Code daily on large project ...

    I've developed many things in areas from self-driving cars to regular enterprise backend systems in different companies with ~1k developers :) So I know exactly what you are talking about and still the main reason I'm not diving to this idea and iOS field in general is that I'm doing this crap in my daytime job and don't want to do almost the same crap in my free time :smile:

    So believe me, I know what you are talking about as well

    Programming a DAW sounds like a nightmare - especially using Claude. I’ve found autonomous agents work well for starting a project, but maintaining consistency in a codebase isn’t its strength.

    I mentioned this to demonstrate how deeply desperate and frustrated I am about how all iOS DAWs treat things that I value most. Seems like it worked better than I wanted :smirk:.
    I didn't want to trigger dev fellas "AI-native vibecoding" PTSD (maybe... :relaxed:)

  • edited April 1

    @setAI said:
    Maybe I'm a weird person who does things differently, but it seems to me every DAW should already have adjustable limiting/saturation/clipping built into each channel and the master without having to bring that stuff in yourself.

    Drambo has good modules though.

    Not keen on building synths ( apart from a wavetable )

    but so good to add a basic retro anologue looking module of a limiter. Now a shaper module. I use the shaper module instead of punchlab ( Id use punchlab when mastering ) Saves a few dsp/cpi points per track on drums. Yesterday I added shapers and EQ module for bass ( instead of medusa ) I think its where I may of noticed latency ( with fast mpe flicks ) So tried shaper plus EQ. Didnt do a latency test after that. Were just a sound test.

    All these modules look good plus make you feel project has less DSP used.

  • Although you would still need a DAW.

    Does make you feel like a genuine sound engineer.

    Drum track.

    Bass track ( Even a few shapers ) for potential shaper FM timbres lol.

  • edited April 2

    A bonus controller.

    DAW is about control.

    So you got the drum tracks on its own ipad above.

    This controller is from another ipad below.

    None of these buttons are for performance ( theres other controllers for that )

    Its just for drum kit generation.

    In theory. i should have loads of drum banks to offer.

    You just recall and delete any track ( by having an empty track save )

    You got FAC ( Yellow )

    Blipbox ( Dark Green )

    Fractal bits ( Purple )

    Thump one ( Terracota pink )

    Skaka ( Dull green )

    Synth Drum kick ( Light green )

    A bass synth ( Off white )

    Vertical Amen break generator ( Dark grey )

    Vertical Skiiid x 2 ( lighter green/blue )

    The combined track triggers, when samples added to tracks ( Blue )

    Close app.

    Launch a better app for drum performance.

    Would have made a better colour scheme but kept Blip and Fac etc ( as similar to apps )

  • I suppose a multi thread like cubasis.

    Drambo that can switch to a timeline but have the look and functionality of the tracks posted.

  • here we go... ultimate black hole which consumes every thread regardless of original topic - Drambo :-))))))

Sign In or Register to comment.