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.
Comments
Thank you, the CC guru. We have your prosperity. Without you, we can not survive the CC.
Our president @JohnnyGoodYear says, we can publish Amozon ebook series.
I guess I know what happened: did you tick "run in background" on Sunrizer(top left corner)?
Makes note in file (in big writing)....
This is at once an incredible relief, since I was trying to find the one and only right way to make things work. And assuming that once ONE setup worked, it would apply to other apps. But this is also sort of alarming that midi seems to observe the rules of string theory.
So what you're basically saying is:
Actually, I do have a very basic question that I have resisted asking because it seems so stupid and SO basic. But here goes:
What does "midi in" mean? What does "midi out" mean? I think, after these helpful posts from GoneKrazy and Wim, that those definitions are fluid?
Does midi out control the sound that emerges finally? And mid in relates to the directions on how to achieve that sound?
For example: Xynthesizer is making the pattern I'd like to use. But iSem has the sound I want. So....
In Xynthesizer's midi settings, iSem is the virtual ouptut? Notes out? And there is no input?
I promise that once I grok this concept, I will compose a clearheaded primer so no one else has to explain it.
MIDI is simply instructions: "Start playing this note", "Stop playing this note", "Turn the filter frequency down" ... etc. The app that is creating these instructions is the sender. The instructions go out of it. Such an app should have a MIDI output setting. That's the one you want to focus on in that app. Turn off the input sources if there are any.**
The app responding to the MIDI instructions and generating the sound is the receiver. Here you focus on the MIDI input settings. Turn off any output settings here.
The next key is to get the output of the sender and the input of the receiver set properly so they can talk. This is where it can get confusing because of the ways ports are named, the difference between "Virtual Out", "Direct Out", "Network Session", etc. But if you keep in mind simply that you have a sender and a receiver and you need to get each one to play their role and talk to each other it's usually not too hard.
One thing you do not want to do is create a loop. So, in your receiver, don't set it up to send MIDI out to the sender! In your sender don't set it up to accept MIDI from the receiver. That be bad juju.
** (There are some cases where you might receive and send in the same app, but best to keep it simple at first.)
That is the clearest definition yet.
And then if I want that iSem sound played by Xynthesizer into Cubasis, I load only Xynthesizer in AB, for example. As for how to get Xyntheseizer into ModStep, I'll go trawl through Kaikoo's tutorials that until recently looked like Sanskrit to me....
Thanks again.
In your scenario above, you would want iSem in an AB input slot, controlled by Xynthesizer (which doesn't need to reside in AB at all, but it can if you want to control it from other locations than directly within Xyenthesizer), and Cubasis in the AB O/P slot. Remember that AB is only routing audio.
Ah, right, of course.
But I could route midi with AUM, yes?
Thanks to @ExAsperis99 for starting this thread, you are not alone mate, this has cleared up quite a few things for me too.
Even bigger thank you to the guys answering the questions.
@ExAsperis99 - yes, you can use AUM to route midi to IAA sound sources.
Dare I?
I put Xynth and Patterning in AUM, channels 1 and 2, respectively. And then? I route those in AUM's midi routing menu into modstep.
In Modstep, the IAA instruments I have as AUM Port 1 and AUM Port2. That seemed reasonable? Midi is definitely being recorded, but it will not play back. Obviously, I have the wrong instruments in the Modstep channels. (Also, the midi scroll seems to reflect only Xynthesizer, which started first; the midi didn't alter when Patterning started.)
You should target AUM midi ports, not IAA which are just for audio. You can find the input/output config tapping the IO button on the right bottom corner. Then you'll have to route midi to instruments in AUM midi config. But it will be easier just to route midi to your sound modules, without having to do double routing(or triple if you have to set your sound module midi anyway)
He wants to fly like a young bird. It takes time otherwise driving himself nut.
I was afraid you'd say something like that. Which I don't really understand! Not your problem! Thanks for trying. I'll go back to crawling and revisit this in a while.
Maybe it's best to understand what you're trying to accomplish first. What is your sound source(s), what controls it/them, what do you want to do in Modstep, what are you wanting to do with the output?
Smart approach.
Want to record editable midi (from apps whose presets I can automatically recall later) into ModStep, where I can arrange and tweak into a song structure. From there, export into Cubasis or Auria for final tweaking.
I'm really enjoying working in ModStep (after many maddening evening and MUCH patient assistance from this board). I wish I cold work in the apps themselves, rather than use the MS keyboard or drumpads; I was hoping AUM would solve this problem.
What midi app would be used for the control and what audio source? I'll give an example of what I think you're after...open a midi sequencer and press play on a sequence. Open Modstep, and add a track.. Add an instrument to the track then open the I/O view and set the midi source (input...this should be the sequencer opened earlier.). Create a clip in Modstep and arm it to record. Once it's armed you should hear audio if all your midi channels are the same...you should also see midi activity in the I/O window. Press Rec in Modstep to start recording (the default clip length might cause it to record more than one loop, but that's fine just to test.). You will probably need to tap the clip again to start it. After a few seconds you can stop recording, and you should see midi data in the clip.
You know what? I'm overwhelmed by possibilities. I've gotten so far away from my original query. I want to be able to play an external synth in Auria! Let me take what I've learned and try to make that work first!