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 don’t think that workaround will work for me, I need to move the whole event back half a bar. Is there a way to do this?
@richardyot only by actually entering the pianoroll editor, double-tapping the background to select all, and then moving the selection half a bar back. (the part has to have enough room to the left).
So on the whole, the best approach is probably to first move the part a WHOLE bar back in the arranger, then entering the editor, and then move everything half a bar FORWARD.
Thanks, that worked OK. Overall there's a lot of nice things about the app, the on-screen keyboard and piano roll are both excellent, so I will be patient and wait for finer-grained editing of the regions.
Thanks!
Is it possible to see the effect of PolyHymnia settings and edits with the interface open?
It blocks the piano roll while open. Maybe being able to drag it around, or an X-ray mode toggle or momentary button could help?
Having been using PolyHymnia a lot this week, I'd love to hear if this is possible in future.
BTW Anyone on the fence about the PolyHymnia IAP should definitely dive in. It's an incredible source for generating ideas. I've found myself hitting "Shuffle All" (randomise) a bunch of times for a 4 bar phrase and when hearing something I like, tweaking the hell out of it for melodic goodness using the Pitch, Length and Distance tabs. Love it!
Absolutely facepalming on my end. I think the first time I tapped it I didn't get it to register and wrote it off as just an icon.
Also thanks for addressing everything else, it's good to know why things are the way they are and how best to work with that.
If I could offer one more bit of feedback, and it's such a minor one because everything else is pretty great as is, the color selection plays such a big part (it colors the keys, the created scenes, etc) more options, or even better a color selector would be a really cool addition down the line. It's a great looking app and I would love to have some softer more neutral colors to stare at.
@lairdhenn good idea. Though instead of a color selector or more colors, I think a "Muted instrument colors" toggle in Settings would be the better way to implement it, i.e. next to the "Color Theme" selector.
@CracklePot an X-Ray button is a fantastic idea -- could be added next to the "Pitch, Length" etc. tabs, and while touched, it would just hide the entire PH popup so you can take a quick glance by just touching and releasing the button again.
I kind of find this too limiting as well. I guess for now I'll be back to using modstep till you implement finer editing. I still love the app though
^ I also find this limiting but to be fair in modstep you also have to go into the pianoroll to shift the sequence.
Xequence seems much simpler to use and its editing of automation/ cc data is the best. I love Modstep but it is a bit clunky in editing cc data, you know, IMHO
Xequence has "undo".
Still waiting for Modstep 2 to bring us this "feature".
Simple, really. Just don't make mistakes.
OR, for the fallible among us, you can go into the Session Autosave and revert to one of the previous versions in its memory. So, strictly speaking, Modstep does have undo. But yes, that's a pain. And a simple "back arrow" would be a much more elegant fix for my timing errors. (Which, you know, are incredibly rare. Goes without saying.)
Yea. I pretty much use the multi autosave as my undo. I just jump back in time to more or less where I was before the mistake. If I want to "version" my projects I just use "save as" and call it with a suffix of _2, _3 etc. So I get both versioning and still can jump back to correct mistakes this way.
Regarding modstep if you speed up the segments you can basically make it so each "part" is 1/4th of a bar. And you can also enable and disable parts to completely rejig melodies. So it's not as limiting as you might think.
Hello there!
As i understand it is impossible to record animoog’s poly aftertouch at the moment?
But i hope it will be implemented someday in the near future? It would be reeeally great, even without ability to edit aftertouch data.
Hello... that's correct unfortunately, but at least recording it is high on the priority list. Hope to get that implemented soon!
Don’t know if this has ever been requested @SevenSystems but an interesting selling point would be the possibility to convert the view from standard piano roll to sheet music. At the moment there’s an app called stavesntabs that does a great job but it lags behind xequences advanced editing. Basically suggesting not a full blown notation software but a module that allows people to read their compositions after programming it.
An interesting feature to look at for sure -- the only problem is that the last time I used standard musical notation was in highschool
if I can someday find the Mozart in me... (didn't that guy invent the notation system?)
I tend to think in terms of a score, and I use the Score Editor in Logic at least as much as the piano roll. I think MultiTrackStudio on iOS has a rudimentary score editor. But I'm sure that is no small thing to code, graphically, and to make it useful for non-quantized parts, you have to negotiate between literal and interpreted representations of the music. Probably not worth it considering how many users don't read music anyway.
I like Xequence now that I read the manual. It wasn't that hard to do, so I'm not complaining in the end, but it was a real turnoff in the beginning to figure out how to access and use the Polyhymnia function I'd just bought. I think the UI could still use more transparency (better symbols? I dunno what I'm no expert), but that's all bygone since I read the manual. It's the best contained MIDI sequencer I've used.
And the real reason I made this post was to praise the Polyhymnia randomizer. It is the king of generative stuff on iOS. It's very smart at creating 3-note polyphonies, for example. They almost always have something musical about them, a recurring theme of sorts that is very pleasant. In comparison, the brambos Rozeta generators are fun at first but get old really fast...
Thanks very much for your positive remarks. Yes, maybe some decisions about Xequence's architecture were just too "over the top" in hindsight. It's difficult to make a perfect design for what might evolve into a very large beast. Ideally, you would be able to use the app without reading the manual, and that was the intention when all the little one-off "hint" popups were added, but yes, that doesn't cover everything. But you can be sure that lessons were learned and will be applied for potential future music-sequencer-workstation things
I had to giggle a bit when I read this:
because making PH as musical as possible by fiddling and tweaking with the algorithms was what 70% of development time was spent on... roughly.
Have you read the patents registered by Stephen Kay (Korg Karma algorithms)?
Very interesting stuff with lots of knowledge behind.
One could spend a lifetime on research on this subject
@rs2000 now you're quoting me, and I had removed the TOP SECRET code snippet!
I surely hope I'm not using any patented stuff
No worries, your code is clean, I can clearly see it
Well but this was a spot with a particularly good comment - to - code ratio 😂
You've got style 👍🏼
@SevenSystems a really nice app, I like it so far ... just got it yesterday.
Does Xequence accept input / recording of notes from an external Midi keyboard? I have not been able to get this to work so far so I would like to know if it is possible at all before I try some more
and where is the panic button for stuck notes?
edit: found it (needs to be turned on in settings / midi)
Hey Nick. You may need to make sure that your midi keyboard is explicitly chosen as a source. MIDI/Recording tab > Sources > (tap keyboard name).
Beyond that, make sure you've set up the midi source on the track you're recording via the cog wheel icon.
Let us know how you get on.
Glad you like the app. As @SpookyZoo already mentioned, please make sure that your keyboard / MIDI interface is enabled in "..." -> MIDI / Recording -> MIDI Input -> Sources. If it doesn't appear there, please enable "Xequence Destination" instead and try to setup your keyboard / interface to point to Xequence.
Also, unless you're planning to record from multiple sources simultaneously onto separate tracks, the track input settings can be ignored. Xequence will by default always record all received MIDI onto the selected track.
^^ What he said!
Hi @nick
As @SpookyZoo and @SevenSystems already mentioning...
You need to go to the midi setting page. Here you can set your keyboard as a midi source, in my screenshot Arturia Minilab MK II.
On the same page (Midi Output) you can also switch the Panic Button on or off. If on, you will find the Panic Button on the top of the screen next to the circle button.
By the way...
I just had problems to connect my Bluetooth Keyboard in the standalone Xequence.
May I miss some Bluetooth switch within xequence @SevenSystems ?