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.

How to get Midi cc values ........?

reasOnereasOne
in General App Discussion

Is it possible? This would be so Helpful to map in modstep and krft and the others
Gadget has a list, but is there a way with other synths... Like zeeon???

Comments

  • TheAudioDabblerTheAudioDabbler

    That would be nice if the developers would put out a default midi cc list. That would make it easy to make presets in rozetta or other midi apps.

  • AndyPlanktonAndyPlankton
    edited November 2018

    @gmslayton said:
    That would be nice if the developers would put out a default midi cc list. That would make it easy to make presets in rozetta or other midi apps.

    I'm not sure default cc lists will still be a thing now that most AU's are using AU Parameters and leaving the CC mapping up to the host :| ... apparently it's progress !

  • SpookyZooSpookyZoo
    edited November 2018

    @gmslayton said:
    That would be nice if the developers would put out a default midi cc list. That would make it easy to make presets in rozetta or other midi apps.

    +1

    @reasOne

    The midi learn in Zeeon is actually broken. Several of us here have reported it to the dev without word back so he's probably busy on Drambo.

    The Midi Learn between layers 1 & 2 is particularly broken. There's a couple of threads about it on the forum I believe.

  • SpookyZooSpookyZoo

    https://forum.audiob.us/discussion/29233/zeeon-midi-learn-issue

  • SpookyZooSpookyZoo

    and another... https://forum.audiob.us/discussion/28465/zeeon-cubasis-midi-learn-buggy#Comment_542508

  • TheAudioDabblerTheAudioDabbler

    @AndyPlankton Progress is such a funny word. I think they should be able to have an option for standard midi cc or use AU parameters. Maybe have the standard CC values hard coded and then allow for AU parameters to overwrite if implemented.

    Of course good Midi apps like Xequence and rozetta has templates for apps built in. We just need midi apps to implement templates for every app in the world.

  • brambosbrambos

    Preset CC codes for all my apps are available on ruismaker.com (in their respective user manuals). :)

  • AndyPlanktonAndyPlankton

    @brambos said:
    Preset CC codes for all my apps are available on ruismaker.com (in their respective user manuals). :)

    I knew you wouldn't let us down ;)

  • reasOnereasOne

    You are the man!!! That's great! stuff like that really helps us out and shows how much thought you put into your apps and work!
    I'm just trying to do some automation from Mod step to the lfo and it's impossible to know the value of anything in just about every iOS synth that I have!

    @brambos said:
    Preset CC codes for all my apps are available on ruismaker.com (in their respective user manuals). :)

  • reasOnereasOne

  • MonkeyDrummerMonkeyDrummer

    @brambos said:
    Preset CC codes for all my apps are available on ruismaker.com (in their respective user manuals). :)

    BTW, it would be nice if there was a switch to disable those built in MIDI CC's in the midi settings... So many times I'll have wacked out behavior because I'm routing midi in the "top" (vs. the bottom AU mapping in AUM) and CC's are intended to control one thing, but it's also controlling the built in params. It really sucks if using a controller with fixed cc's...

  • ProcessaurusProcessaurus

    +1 for default CC values for apps. This is how the world of music gear has worked for the last 35 years. With default CC's, your midi controller template you slaved away on will ALWAYS work for new presets, other ipads, and for other people with the same controller.

    The worst offenders are the apps that have no default midi cc values, and forget the midi learn, from preset to preset (Sugarbytes!). These are the "uncontrollables".

    As someone who has spent hours and hours making special templates for ios apps, to try to fulfill the promise of knobby midi controllers, here is one midi head's idea of how it should work:

    • There should be default midi cc's. They go in a list at the back of the manual. For standard controls, it is best to follow the numbering of the midi spec (like output volume is CC#7).
    • It is nice to be able to midi learn to override the default cc's.
    • This midi learn should be global, for all presets, and remembered forever. If that doesn't sound good, then some provision for transferring midi settings from preset to preset is crucial for people that have gone to town with mapping a large number of controls.
    • When you are MIDI learning, it is very nice to have a temporary overlay to visually see the CC's that have been assigned to controls.

    • For single channel instruments, it is best to have a way to limit midi cc input to one channel coming in (ignore cc's on all other channels). A channel setting with an option for omni, that is the default, is great. For multi channel instruments (drum machines,
      synths with multiple layers), it is nice to use multiple channels at once, to take advantage of using one midi channel for each instrument channel/layer, reusing the same CC #'s for the controls on each channel/layer.

    • Extra points for having an option to send out CC data from the app back to the controller, to synchronize the software's knob positions with encoders with leds. Extra extra points if
      the app updates CC's to the controller on preset change (Moog apps!).

    @MonkeyDrummer said:

    @brambos said:
    Preset CC codes for all my apps are available on ruismaker.com (in their respective user manuals). :)

    BTW, it would be nice if there was a switch to disable those built in MIDI CC's in the midi settings... So many times I'll have wacked out behavior because I'm routing midi in the "top" (vs. the bottom AU mapping in AUM) and CC's are intended to control one thing, but it's also controlling the built in params. It really sucks if using a controller with fixed cc's...

    Yes, that would be a fine option to have in the settings, but you can usually work around those problems by switching the midi channel, on one of the destinations, unless the thing with default cc mapping is using all 16 channels (like 16 channels on a mixer). Or, if you just don't want to midi control that app, just turn off the controller's entire midi port, in the receive settings in that app.

    I started avoiding using channel 1 for semi permanent, special midi controller setups, because so many things default to 1. It's kind of like the empty visitor parking spot by the front door.

  • reasOnereasOne

    Amen!!!

  • AndyPlanktonAndyPlankton

    @Processaurus said:
    +1 for default CC values for apps. This is how the world of music gear has worked for the last 35 years. With default CC's, your midi controller template you slaved away on will ALWAYS work for new presets, other ipads, and for other people with the same controller.

    The worst offenders are the apps that have no default midi cc values, and forget the midi learn, from preset to preset (Sugarbytes!). These are the "uncontrollables".

    As someone who has spent hours and hours making special templates for ios apps, to try to fulfill the promise of knobby midi controllers, here is one midi head's idea of how it should work:

    • There should be default midi cc's. They go in a list at the back of the manual. For standard controls, it is best to follow the numbering of the midi spec (like output volume is CC#7).
    • It is nice to be able to midi learn to override the default cc's.
    • This midi learn should be global, for all presets, and remembered forever. If that doesn't sound good, then some provision for transferring midi settings from preset to preset is crucial for people that have gone to town with mapping a large number of controls.
    • When you are MIDI learning, it is very nice to have a temporary overlay to visually see the CC's that have been assigned to controls.

    • For single channel instruments, it is best to have a way to limit midi cc input to one channel coming in (ignore cc's on all other channels). A channel setting with an option for omni, that is the default, is great. For multi channel instruments (drum machines,
      synths with multiple layers), it is nice to use multiple channels at once, to take advantage of using one midi channel for each instrument channel/layer, reusing the same CC #'s for the controls on each channel/layer.

    • Extra points for having an option to send out CC data from the app back to the controller, to synchronize the software's knob positions with encoders with leds. Extra extra points if
      the app updates CC's to the controller on preset change (Moog apps!).

    Proper talk right here ;)

  • Aud_iOSAud_iOS

    Or - How about MIDI Capability Inquiry? If we get that on a Host & some plugins - preset mapping would be terrific! Hoping some devs are looking into MIDI-CI.

  • brambosbrambos
    edited November 2018

    @Aud_iOS said:
    Or - How about MIDI Capability Inquiry? If we get that on a Host & some plugins - preset mapping would be terrific! Hoping some devs are looking into MIDI-CI.

    To me it smells like it has a huge overlap with the AU Parameter paradigm, except with more hassle. I'm not a big fan of feature redundancy, quite frankly.

    Perhaps if hosts offer it for MIDI communication with the outside world and translate that internally to the AU world, it could work, but not if it has to be done in every plugin separately.

  • MrBlaschkeMrBlaschke
    edited November 2018

    Also a usable naming convention would be a „nice to have“ :smile:
    At the moment i am trying to map the Audio Damage Plugins - but seems to just be prepared and can freely be assigned. Unlike others.

    Its just the plain numbers...

  • Aud_iOSAud_iOS

    @brambos said:

    @Aud_iOS said:
    Or - How about MIDI Capability Inquiry? If we get that on a Host & some plugins - preset mapping would be terrific! Hoping some devs are looking into MIDI-CI.

    To me it smells like it has a huge overlap with the AU Parameter paradigm, except with more hassle. I'm not a big fan of feature redundancy, quite frankly.

    Perhaps if hosts offer it for MIDI communication with the outside world and translate that internally to the AU world, it could work, but not if it has to be done in every plugin separately.

    @brambos Yes - outside world communication would be ideal - I’m not sure if it would overlap - or just be a separate function, tho I could see utility in an app like Midi Designer where it could possibly map up parameters to a layout quickly, or in apps that have differing parameters depending on the preset like some of the modular synths. I’ve read through the Apple docs on MIDI-CI - not much detail I found but seems to cover the Standard. I remember ther was a MIDI-CI toggle in the iOS dev Settings - but I didn’t find any example projects to test.

Sign In or Register to comment.

© Vanilla Keystone Theme 2025