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.

Thoughts for Devs: Please design around biggest constraint holding IOS synths back…

MonkeyDrummerMonkeyDrummer
in General App Discussion

I’ve been wanting to rant about this for a while…

So many iOS synths sound so damn good, and when paired with a hardware controller are as good or better than just about every “VST in a box” hardware synth out there these days.

But… you still have to rely on fiddly touch interfaces, or you have to rely on encoders or pots on your controller that immediately become useless if you change patches.

Why in the world are devs not supporting relative CC’s for midi mapping and relying on endless encoders?!!

This one simple change would allow midi mapping to flow freely from app to app, make hardware interfacing and knob twiddling sooooo much more intuitive, and basically drive a stake through the heart of all the vst in a box digital synths out there once you have a killer midi controller/interface.

So… Why?

I begged for AUM to support relative cc modes a few years ago and was told, “meh… no”

But supporting rel cc in the apps themselves would make it more universal.

Relative cc is basically a standard on desktop, but seems like taboo on iOS… I just don’t understand…

Comments

  • wimwim
    edited June 2

    Two words: Loopy Pro.

  • wimwim
    edited June 2

    Or: Drambo

    AUv3, and using the host as the control middleman for their parameters is the way forward. If your host doesn't support encoders, then maybe it's time to consider a different host.

  • MonkeyDrummerMonkeyDrummer

    @wim said:
    Or: Drambo

    AUv3, and using the host as the control middleman for their parameters is the way forward. If your host doesn't support encoders, then maybe it's time to consider a different host.

    Ha! Yes, the thing that brought this up to top of mind is that I’ve been messing with running some stuff in standalone…

    I wasn’t aware loopypro supported rel cc… Learning LoopyPro is next up on my iOS todo list, sooooo…

  • GavinskiGavinski

    @MonkeyDrummer said:
    I’ve been wanting to rant about this for a while…

    So many iOS synths sound so damn good, and when paired with a hardware controller are as good or better than just about every “VST in a box” hardware synth out there these days.

    But… you still have to rely on fiddly touch interfaces, or you have to rely on encoders or pots on your controller that immediately become useless if you change patches.

    Why in the world are devs not supporting relative CC’s for midi mapping and relying on endless encoders?!!

    This one simple change would allow midi mapping to flow freely from app to app, make hardware interfacing and knob twiddling sooooo much more intuitive, and basically drive a stake through the heart of all the vst in a box digital synths out there once you have a killer midi controller/interface.

    So… Why?

    I begged for AUM to support relative cc modes a few years ago and was told, “meh… no”

    But supporting rel cc in the apps themselves would make it more universal.

    Relative cc is basically a standard on desktop, but seems like taboo on iOS… I just don’t understand…

    Did Jonatan reject this idea? Was there a reason given for it? Would be useful in AUM, I agree.

  • FastGhostFastGhost

    I have a request for devs too: please don’t bury all your presets behind artists’ names. I have no idea who most of these people are so it’s the worst possible filing system.

  • MonkeyDrummerMonkeyDrummer

    @Gavinski said:

    @MonkeyDrummer said:
    I’ve been wanting to rant about this for a while…

    So many iOS synths sound so damn good, and when paired with a hardware controller are as good or better than just about every “VST in a box” hardware synth out there these days.

    But… you still have to rely on fiddly touch interfaces, or you have to rely on encoders or pots on your controller that immediately become useless if you change patches.

    Why in the world are devs not supporting relative CC’s for midi mapping and relying on endless encoders?!!

    This one simple change would allow midi mapping to flow freely from app to app, make hardware interfacing and knob twiddling sooooo much more intuitive, and basically drive a stake through the heart of all the vst in a box digital synths out there once you have a killer midi controller/interface.

    So… Why?

    I begged for AUM to support relative cc modes a few years ago and was told, “meh… no”

    But supporting rel cc in the apps themselves would make it more universal.

    Relative cc is basically a standard on desktop, but seems like taboo on iOS… I just don’t understand…

    Did Jonatan reject this idea? Was there a reason given for it? Would be useful in AUM, I agree.

    I don’t recall the exact series of events beyond me begging, him saying no, me begging more then giving up… 😀 Considering the age of AUM I figured he probably would add to AUM Part Deux if there was an update so not worth being toooooo much of a pest.

Sign In or Register to comment.