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 StoreLoopy Pro is your all-in-one musical toolkit. Try it for free today.
MIDI SENDER on iOS
Hey Folks and Developers,
I would like to discuss the MIDI SEND problem on iOS. Am I the only one who want a MIDI SEND to my Hardware Sequencer Controller LEDs? Or knobs and faders send from Apps (like AUM or Drambo) back to my Controller? If this comes true , I would have no intention to produce my music with an laptop. So this Thread should be More a mindmap of what is possible now and in the Future. Like to read your opinions.
Comments
Today's MIDI spec has everything it needs to do that, yet only very few developers see the need to support parameter feedback.
If more people asked for it, it would be higher priority but most people are fine with using touch screens. Especially when chilling on the couch.
It's more complicated than that. There is no standard for what does turn lights on and off, etc. Take a look at the Launchpads, which use a different channel and midi messages to interact with their lights. It's not always just a matter of feeding back the value of a control to update the LED ring on a rotary encoder. Some hardware will even create a midi loop if you attempt to feed back MIDI.
Not to mention that the majority of controllers don't even have any indicators that would respond to feed back or have rotary encoders that would make sense with it. Most don't have encoders at all, but fixed range potentiometers. You can feed back all you want to a controller that doesn't use encoders or motorized faders/knobs. Nothings gonna move that knob.
@Frühstück, what controller do you have?
The visual part I cant say, there are apps that do things that maybe addresss that. Midi out to controllers and hardware works ace for me on a semi old iPad. I think if you said I want to control my ms2000 synth with example ideas we can help more.... Cheers mate.
Look at Mixxx, the open source DJ software. They have an open config file format that lets you adapt your own MIDI controller to work with Mixxx. I would say that's the way to go because asking an iOS developer to support 20 or 30 different MIDI controllers is unreal.
I wish every software worked that way. I tried like hell to get the FL Studio developer to make such a thing. But more than a decade later they continue to only provide proprietary support profiles for the hardware they deem worthy. I don't get it. They almost surely have some equivalent of what you described internally, but would rather go to the bother to write the mappings themselves.
@Max23 's comment intrigued me. I need to do some more reading up on MIDI 2.0.
Yeah, that‘s right. For me It would be easier to play live with different apps and did not hang on multi windows in AUM. It is a bit hard to change drum sequences on the fly, when you have to change quickly windows of apps. Response on Encoders when I change Presets/Program Changes would be really nice. Also for the Future would it be really interesting to Send MIDI back to different Controllers (visual, physical, hardware, sensorics etc.)
@wim I use three Livid Controllers. Two Livid Codev2 and One Livid CTRL. I know that Livid don’t update these Controllers anymore. So I would like to buy some yaeltex Controller. What do you use to control some parameters?
Those are beautiful controllers. I only use a NanoKEY Studio and a Sensel Morph, neither of which would benefit from feedback, but I'm interested in the topic for a couple of reasons. First, I'm considering a Launchpad XL as now a couple of key apps are building direct support for it. Second, as a hobby, I'm messing around with making my own small controllers, and am trying to come to grips with how to make them responsive to feedback.
@wim MIDI 2.0 specifies how an app can communicate with a controller to find out what it supports and the idea is to make the whole mapping process a lot easier. It cannot change the fact though that the developer has to feed that API which is even more work than the config files I've mentioned because users will expect a guided process. Good luck.