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.

Creating a DIY MIDI control Surface

PetersMusicPetersMusic
in App Development

Hey Everyone! Me and some friends, are in the early stages of designing and building a control surface to work with the major, DAWS and most likely going to use MCU (Mackie Control Universal ) Or Mackie Control. We most likely are leaning towards MCU with its combined abilities. We are all from different backgrounds which, means we have to learn a lot of information about this, more specifically what MIDI data is needed to control specific parameters within the DAW I've backwards mapped it so far that to control the volume you hit (for example) G#6 plays at 127 velocities, THe pitch wheel controls where the volume is (Between 0-127) then G#6 is released I was wondering if anyone has any thoughts on this and/or any information on where I can find more information like this that will help us develop the device further. Cheers

Comments

  • u0421793u0421793

    I just want to tell you both good luck. We're all counting on you

  • RetroNewbRetroNewb

    This helped my battles with MCU, assuming link works
    http://www.midibox.org/dokuwiki/doku.php?id=mc_protocol_mappings

  • wimwim

    @RetroNewb said:
    This helped my battles with MCU, assuming link works
    http://www.midibox.org/dokuwiki/doku.php?id=mc_protocol_mappings

    Thanks for that link! I spent so much time trying to find information like that a few years ago. It was ridiculous.

  • SevenSystemsSevenSystems

    @u0421793 said:
    I just want to tell you both good luck. We're all counting on you

  • HotStrangeHotStrange

    @u0421793 said:
    I just want to tell you both good luck. We're all counting on you

    Surely you can’t be serious

  • HotStrangeHotStrange

    I’m not a coder but good luck! Sounds interesting :)

  • u0421793u0421793

    What’s afoot, regarding this

  • PloePloe

    @PetersMusic said:
    Hey Everyone! Me and some friends, are in the early stages of designing and building a control surface to work with the major, DAWS and most likely going to use MCU (Mackie Control Universal ) Or Mackie Control. We most likely are leaning towards MCU with its combined abilities. We are all from different backgrounds which, means we have to learn a lot of information about this, more specifically what MIDI data is needed to control specific parameters within the DAW I've backwards mapped it so far that to control the volume you hit (for example) G#6 plays at 127 velocities, THe pitch wheel controls where the volume is (Between 0-127) then G#6 is released I was wondering if anyone has any thoughts on this and/or any information on where I can find more information like this that will help us develop the device further. Cheers

    Hi,
    7bit resolution (0-127) is definitely not enough for smooth fades or smooth filter sweeps.
    MIDI Pitch Bend has 14bit resolution (0-16383). Much smoother.
    The MIDI 2.0 specification uses 32bit resolution for CCs. Even smoother.
    Good luck!

  • rs2000rs2000

    @PetersMusic
    https://www.jjlee.com/qlab/Mackie Control MIDI Map.pdf

Sign In or Register to comment.

© Vanilla Keystone Theme 2024