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
I tried following the instructions to download and load the demo projects for Gadget 2:
http://seven.systems/xequence2/en/downloads/
I then turned on Background Audio for Gadget 2.
I loaded the corresponding Xequence2 demo project (Alpha or Beta).
I don't hear any sound.
I'll try creating a new Xequence project from scratch and try following the masterclass videos for Xequence 1.
I had an issue loading the alpha project. I deleted it and tried again and for some reason it worked. I followed the instructions to the letter. It does work
@GovernorSilver, @tja and @Steaders
You have to restart Gadget after enabling background audio.
Also make sure that in Gadget, Midi Input is set to Advanced and the bottom left button on each mixer channel is set to receive on the correct MIDI channel like configured in Xequence 2.
Oh man I'm having the same sort of problems I had with the original Xequence. This is the super basic scenario that should work, right?
Am I right in thinking that I can’t draw/edit/add sustain in Xequence unless I first record sustain CC with a foot pedal? I see pitch and velocity options in the data type menu but not sustain.
Also, I’m not a great piano player so I always add sustain after i’ve recorded the midi notes. Something I’ve always wished for is some sort of intelligent on/off auto sustain/hold which occurs while playing.
Is this an impossible dream? Some apps have always on sustain/hold but that’s not what I’m taking about.
This is a really old vst but I think the description of it comes close to explaining what I mean
“S-CC Sustain-Lite - Simulate the function of a Sustain-Pedal, controlled by a CC message. Optionally limit midi polyphony or enable to "kill" older notes automatically if the polyphony limit is reached.”
http://www.s-production.de/index_vst.html
Thank you! At least I can confirm that Beta project now works for me.
Ok, I figured out that in the Instrument popup, I have to set the MIDI Destination to Cassini. Simply setting the MIDI channel to match Cassini's input channel (MIDI ch. 3) was not enough.
I also tried testing with Galileo but it died. Same with Kauldron.
I don't know how I missed that there should be a MIDI destination set and it is next to the instrument name. I did watch two masterclass videos.
At least I got Cassini and AUM to both be sequenced as expected.
In the Gadget project, double-check that:
If you just choose the midi destination first, you won't need to type the name of the app - xequence just does it for you as soon as you choose the midi destination. And as soon as you record, it will fill in the track name as well.
@Steaders the DATA TYPE menu only shows controllers that have already been configured (or auto-added) to the instrument. You can add the sustain controller at any time by going to the Instruments screen (MIDI icon at the top left), opening the instrument's settings (...), and then selecting "Sustain" for any free controller slot.
You can then for example draw the sustain automation in using the Draw tool (anything below 64 is "off", anything above is "on").
You can also record sustain automation easily while or after recording by adding the controller to the keyboard screen (enable the "Keyboard" icon next to the controller in the instrument settings popup), then setting the controller ribbon to "Gate" mode (pulse icon), and then just tapping and holding the ribbon in its upper half while you want sustain.
(I've made a video but "Google can't verify that the account belongs to me" anymore, so unfortunately I can't upload it to YouTube, err, right now.)
Would be grand if the forum allowed attaching videos! 😉😉😉
Thanks! Wow! That’s awesome!
I’ve been working my way through the manual but I couldn’t figure sustain out.
Things are definitely falling into place for me with Xequence 2. It truly is a fantastic app with loads of potential.
It’s the thought that counts. That said, I would love to see that video. 😀👍🏻
Couple of other questions.
I can’t load apps inside Xequence right (like Aum)? I have to open them outside of Xequence before Xequence sees them?
Other than state/preset saving, Why would I use Audiobus with Xequence?
I am unable to sync start stop fugue Machine and Xequence. Is this where Audiobus comes in?
Sorry if the answers are obvious.
Hi, can someone quickly explain to me why I might want this? I mean no disrespect, just that I never grabbed V1 because I didn't really understand what it was good for either.
from the manual
@Steaders, here's the video, I hope (but I guess you already figured it out) :
No, Xequence itself is a pure MIDI sequencer, but the beauty of using a separate app for hosting is that both apps can do at what they do best each.
Regarding Audiobus, there's lots of other advantages. Being able to use MIDI processors in any spot in the routing, seeing the MIDI routing visually, switching between any two apps with a single tap, remote-controlling Xequence's or any other app's transport without switching apps, etc. etc...
Regarding Fugue Machine, unfortunately it doesn't support start/stop sync via Ableton Link. It may support start/stop sync via Audiobus though (which Xequence also supports), though I'm not entirely sure. Maybe someone else?
Thanks royer. I read the manual and wouldn’t ask if I understood it all. I think I’m trying to imagine practical applications where I would need/use it.
Can’t thank you enough for answering my questions and especially the video. 👍🏻👍🏻👍🏻👍🏻👍🏻
The Audiobus applications make perfect sense.
If you don't know why you would need a standalone linear MIDI sequencer, you probably don't need it. It fits a niche as an efficient composition environment for working with MIDI apps.
IMO, state-saving is huge plus the remote transport and app-switching available from the floating palette. That palette is handy even when state saving not needed.
...or hardware, of course