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.
Xequence driving Gadget: can you export stems?
I'm thinking about buying xequence with all IAP to use Gadget without the terrible sequencer. (I spent about 45 minutes copying and pasting last night.)
I'm wondering, however, is it possible to export stems this way? Seems Gadget would need notes in the sequencer.
If I have to record midi into Gadget from xequence that's fine, providing it is not too difficult.
Comments
Xequence+Gadget is a great combination, but you can't export stems. There are a few ways to work around that:
Yes you can export stems in one go. Export > iTunes > All Tracks. The files end up in the files app > on my iPad > Gadget.
But if all your MIDI is in Xequence, not Gadget, won’t you just get empty stems if you try exporting the Gadget song?
Stem exporting only works if you are sequencing in Gadget. My understanding was that he wants to sequence in Xequence. If you sequence with another app, you have to capture audio since there is no 'project' to capture.
I suppose you could try recording the MIDI into Gadget from Xequence and then export, but unexpected things can happen when you do that in my experience since Gadget will break up the incoming stream into 16 measure chunks.
Doh! Sheesh. What wuz I thinking?
I remember now. Indeed,when I did that, I had recorded the Xequence midi into Gadget, then exported.
I wish multi-port audio out was a more common feature. If Gadget had it, you could just run Xequence and record the Gadget output into multiple tracks in AUM or Auria. Alas...
Did that too and that worked great. But I suppose this can be issue with some long Xequence notes recorded over two Gadget patterns...
How complicated is getting the midi from Xequence into Gadget sequences?
I’ll edit my note and add it (with a YMMV note).
Exporting / importing midi is impractical due to Gadget’s goofy import behavior. With link enabled and both apps loaded in AudioBus, it worked well for me. AudioBus global transport works great for this.
I have tried recording any long sequences iinto Gadget, though. That could be an issue. If I have time, i’ll Try.
If remember correctly, just use midi clock to sync Xequence and Gadget transport. Then create enough patterns scenes in Gadget and arm its record button and play Xequence song. Everything will be recorded on individual Gadget tracks in one pass. Then export stems
No need for midi clock if you use Link and AudioBus. Perfect sync and start/stop.
I just tested, and as long as you set up enough 16 bar scenes, longer recording will just continue until it runs out of places to put the midi.
It was just a light test, but it worked flawlessly with four midi channels recording simultaneously. Automation recorded too. I didnt do an a/b comparison for playback accuracy.
You’re right first time I’ve used that trick Xequence didn’t have Audiobus support, so this is why I remembered using midi clock. I think it’s the best way to do stems really with even some Ableton Live export capabilities (copy paste parts from session to arrangement view).
Btw, I posted a recording I made using > @wim said:
Did you have held notes that cross scene boundaries? I seem to recall that was a problem for me and necessitated my use of other methods.
ewps
?
Oh i'd made a post, figured out I was wrong in what I was saying, but couldn't delete it. Thus: "ewps".
Nope I didn’t have any of that. You’re right, that would probably be an issue.