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
Yes, "nudge" buttons can be useful... regarding screen space though, please remember that Xequence also runs on the smallest iPhone (SE / 5s), which has a 4" display. Many users tend to forget (even I do sometimes!), but the portability is one of the "landmark features" of the app, so every feature addition has to be checked for compatibility with all screen sizes...
😀🙌
Thanks! I'd seen it doing that for me, but didn't know how I got there, ie. process/loop on
It also looks like there's some time-stretching going on in the second half of your video... is that correct?
wim had a good response, which I copied for future reference. Atom for him is convenient to have inside of AUM for quick capture of MIDI events while jamming. Then he exports MIDI from Atom to Xequence for further MIDI editing. Photon could probably do the same job... except it doesn't run in iPhone!
While Xequence can obviously control synth apps by sending MIDI out to the synths, I am unclear as to whether it can capture incoming MIDI in real time. I think this is why wim and others are using the likes of Atom in AUM.
I'm still a bit unclear on why Audiobus is being used, but the manual says it's good for "fast switching between apps, for central transport control, and storing and recalling the entire project from a single location." This is from the Example Setups section: http://seven.systems/xequence2/en/manual/
Yes, Xequence 2 supports interactive timestretching on all levels from the whole song to individual notes or controllers
Yes, Xequence has sophisticated support for recording MIDI from external (hardware or virtual) sources, including fully automatic multitrack recording (there's no need for manually creating or assigning tracks), automatically separated by sources and MIDI channels.
Ah... I see. I couldn't figure out how you were doing it, but it looks like you're holding the middle section of the slider thingy as it turns into a clock/time icon. Got it. Cool. thx
Yes, you can just hold one of the handles (left/right), and then tap the clock toggle in the middle with another finger to toggle between the two modes
Regarding Audiobus. Could someone tell me if I’m doing this right?
If I load pure synth into Audiobus, I also need to open it outside of Audiobus to hear sound in Xequencer.
Is this the right way of doing it? Feels like I’m doing something wrong.
The problem with this configuration is that I can hear the Midiflow scales sound and the pure synth sound together when I play and they clash on notes out of the chosen scale. Man, why is this so complicated? Is not a Xequencer issue. I had the same problem in Aum. I know I’m doing something dumb but It’s frustrating nevertheless.
Update: the only way I see of fixing the double sound issue is to change the midi channel of the Pure Synth that is loaded outside of Audiobus. My Arturia MiniLab is on channel 1 in Audiobus and Pure Synth is on channel 2 outside of Audiobus. Sound right?
@Steaders
You need to host Xequence in AB3
In Audiobus you need to put Xequence Midi In channel 1, your synth in the output
Then in Xequence instead of selecting virtual midi in the midi, select Audiobus ( your second screenshot) and make sure it’s the same channel as you selected in AB (ie 1)
It’s all the midi piping involved, it’s not that we’re dumb; it’s complicated piping.
That’s why I like AUMs graphical piping layout which shows where everything is coming from and where it’s going to. Really wish X2 had something similar but what we have is good enough as long as we keep it simple. Add one thing at a time and think about the flow. What is sending what and where do you want it to go. Is it audio? Is it midi?
Remember, X2 only handles the midi part; AUM only routes midi but handles the Audio part.
Thanks for the support Tones4Christ. The problem for me is I really only use the right side of my brain when I’m writing and it’s such a disruption to head over to the left side to figure problems out.
I’m trying this but not getting anywhere. Will keep trying.
Nope. No luck. Would you mind showing me visually?
This is how I’ve set it up
Hi, there’s one really simple thing you’ve done wrong. Select “Audiobus” as the output for the track and not “Audiobus 3”. Then you will not need to load the standalone app.
The “Audiobus 3” destination would be used if you weren’t loading Xequence into Audiobus.
Here’s a preset that will work to get you started.
http://preset.audiob.us/AxCYhuTbLSwzphr
[edit] whoops. Gimme a second to include external controller and midiflow scales.
Thanks as always wim
Also note that what you select under "Multitrack Recording Source" is only taken into account when you actually have Multitrack Recording enabled (the "Two Arrows" toggle at the top right). If not, then ALL enabled MIDI In sources are always merged onto the CURRENT track.
Got it. Thanks!
Audiobus has a floating palette that lets you switch with one tap to any other app loaded in your session and offers transport controls for all the apps loaded in your session. So, if you are in Animoog for instance, you can click Xequence's record button so that you can record your Animoog performance without switching back and forth from Xequence to Animoog to get the transport started and stopped.
Also, if you have IAA apps that support Audiobus state-saving, their settings can be saved in your session. AUM supports AB state-saving. So, you don't even need to save a separate AUM sesssion. The AUM setup will get stored in your AB preset if AUM is in the AB preset.
I almost have it using your method wim, I just can’t hear the notes I’m playing on my external controller (MiniLab). I can hear the pure synth piano on the recorded midi though.
I was listening to the song, again, and noticed the drum sounds are present. Seems Recife is not an IAP. I’ve only purchased Kamata. Does Beta use the same Gadget project file as Alpha? It sounds good using it.
Are there any built-in Midi instruments or does iOS have any?
Also, why would song loop be greyed out? I can not select Song Loop, Selection, or Clip. I’ll check out the manual for this one.
OK, here’s a configuration that should work with Midiflow Scales. The controller is sending to Midiflow scales, which is sending to Xequence MIDI In 1. Xequence is then outputting that to puresynth via MIDI Thru. The key (pun intended) is to be sure that a) Xequence isn’t accepting MIDI in from your keyboard because Audiobus needs to in order to send through Midiflow Scales, and b) Xequence is configured to send MIDI Thru.
Normally routing is simpler than this with Audiobus, but since you want to play through Midiflow Scales, it requires using the in / out / thru setup.
http://preset.audiob.us/t991ims5PX6Cbq8
You probably just need MIDI Thru enabled in Xequence.
Midi Thru was it wim!!
Thanks SO Much!
I couldn’t get your second preset to work though. Probably me. 😢
I was setting up a project when this first came out and was having issues with an external controller
Was trying everything
All I had to do was hit that midi thru option haha
It’s usually something small or “stupid” you missed in the end
New problem. With midi thru on, I lose velocity sensitivity on my MiniLab? Why me?
If you would like to provide further details we can probably work it out. Perhaps setting up from the screenshot instructions rather than with the preset is better.
It’s important to DISABLE the midi controller as an input in Xequence MIDI settings for this setup. Otherwise it and Audiobus fight for who is going to process the notes.
The input in Xequence needs to be Audiobus Midi In 1 This is set with the ... next to the track in the timeline view. The Output in Xequence needs to be set to Audiobus (ch. 1). This is set in the Instrument settings.
It’s ok. I don’t think I need to get the second preset working as your original method is working well.
This may have been a glitch. I closed and reloaded everything and I think it’s ok now.