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
Thanks for the info!
I watched over Mitch's video
controllers/cc's and I see he used a separate track for cc's automation...is that a general rule? I thought i could record automation over the actual notes inside a track.
Mitch also didn't use a midi controller for it, he did everything manually .
You can have controllers and notes on the same track. Many prefer to have them on different tracks.
Gosh....I must be missing something here big time...I tried again and no effect on that data I wrote in...manually. Is it the fact that Im using it as a virtual source? and not inside Aum?...idk anymore
OK>>>>>>> got it...inside Aum( midi sources )....I only selected my midi controller and not Xequence Source. Both selected !!!!!! Thank you all...sometimes it takes me more time to comprehend things out...but...hey I really like Xequence.
Maybe put a midi monitor on the receiving end to see what is going on. Perhaps you have a mapping issue in AUM?
****> @espiegel123 said:
Yeah...it works now. I should have also selected Xequence Source inside Aum's midi source and not only my midi controller.
Thank you all!!
Happy to hear it is working now! I swear I have seen "Xequence Source" selected in AUM in your video, so I didn't mention that!
Let me know if anything else is unclear.
Also, as others have said, you can either have all notes and controller data in a single clip, or all in separate clips and on separate sub-tracks... however you prefer to work.
How do you guys map/connect Patterning 2 with Xequence?
@Sergiu are you recording Patterning in Xequence or driving Patterning from Xequence?
From X, create new instrument and set destination to P. The MIDI channel and note assignments are adjustable per instrument and patch in P (see MIDI output settings) but channel 1 is default and there is a Patterning drum map in X that is configured with the default note assignments.
For recording, you can select P as MIDI source in X. You might want to configure each instrument in P to send to a separate channel - to record on a separate track. You will want to set each instrument in P to send both audio and MIDI, or just MIDI. This setting is per instrument per patch.
To record Patterning 2 MIDI output into Xequence? Or to play Patterning drum sounds from Xequence? Or to sync Patterning 2 to Xequence? Or? ...
@SevenSystems I'm having an issue with the internal keyboard jumping position when trying to lock it.
It varies between a jump of ~half a note, or to root0.
Often preceded by a screen flash.
I'm using latest OS and app updates.
Cheers.
Hi, yes, this is a known problem since iOS 13 (which forces momentum scrolling for the keyboard without an easy way to turn that off). I was still waiting for a potential fix from Apple, but it seems that will not arrive in time so the scrolling will have to be re-implemented. I hope to get this fixed during the next 1-2 weeks in an update!
(this would also fix the "Undo/Copy/Paste" menu popping up under certain circumstances when playing chords in "Scroll" mode.)
Thanks for the quick reply!
If re-implementation is on the cards, could I also request you look into the key size-snapping?
It's just a visual thing, but I'm often forced to live with half-keys on my iPad 10.5".
Could I propose a "show X number of keys" (that adapts to show/hide of CC ribbon), as opposed to "width X"?
I have discussed this with another user -- am I correct in assuming that this ONLY happens if the CC ribbons are visible? Because their width is not taken into account when calculating the correct key width. However, if the CC ribbons are hidden, then there should never be "half keys" (but there might be a bug in the calculation somewhere).
That certainly sounds like an interesting idea!
BTW, thanks for the heads up on the scrolling problems. I've just bumped the priority for this fix, and the problem is already solved for the next update.
Thank you ! Record patterning in xequence> @mojozart said:
If I understand what you would like to do correctly, this should be as simple as making sure Patterning 2 is enabled in the Midi Sources in X2, and making sure that Link and Link Start/Stop are enabled in both apps. Then just press record in X2.
I'm experiencing the "half keys" in both scenarios.
Thanks for the quick response and wonderful app!
Basically, i would like to use a drumkit from Patterning inside Xequence.
I want to insert/record those drum parts inside Xequence...so sequence them with Xequence ( I would use Patterning just as a drum module )> @wim said:
Ok, so I didn’t understand you correctly. You want to place midi notes in X2 and have those notes play Patterning then. So @mojozart’s answer is what you need.
Thank you...it's a bit tricky since Paternning is not Auv3...I would have liked to be able to use it inside Zenbeats
Hello @SevenSystems
A new feature demand...
I'd like to have the option to mute/unmute (as for clips) program change.
Purpose of this ?
1.Stability ! As every time you sending this to synths at reload into AUv3 to AUM, you may have some crash (loading 10 patch at the same time...) Of course you can load each PC one by one on the timeline, that reducing the risk of crash, but still, if your track is loaded and your initial presets are loaded, no need to send a reload for PC every time it plays...
2.It takes time to load (particularly for a sampler, here EG pulse) so while loading your "loosing" sound of first bar. In my case, the sampler is starting the track...
Of course I may add a blank bar with just the PC, then start the track, but as I'm using 3 instances of X2, and as I'll get lots of tracks, well...mute/unmute seems the simplest option...?
Thanks for considering
Well, creating a first bar with all PC, then starts at bar 2 seems a better solution in fact and not very hard to organise...Writing this down helps me finding the more easiest solution...
Forget it...
@crony haha okay. It would be quite easy to add support for muting PCs, but yeah, I supposed there would not really be many real-world use cases for it and it might be confusing.
@SevenSystems okay, I finished this program change organisation, works perfectly fine with my "init" bar...
Here are 2 (again...) questions, maybe a feature request ? (but I may haven't find this ?)
I don't understand the setting : "prevent display lock" and there's no documentation on this button...Could you explain this feature ?
Also, is there a setting to follow the running cursor while playing ? (hope it won't consume too much ressources while moving, but maybe it could be defined by a number of bars , like 16, 32, 64 etc... depending of the size and scale ?)
This cursor would also follow back to initial position while stopping X2.
Once again: 1 billion thanks
Hi, no problem, both questions can be answered easily
= "Prevent Display Lock" does what it says: it prevents the display from locking. i.e., if you have your device set (in the Settings app) to automatically turn off (lock) the display after, say, 5 minutes, enabling "Prevent Display Lock" will keep it from locking / turning off while Xequence is running.
= Yes, in the "View" menu, enable "Follow".
@SevenSystems great...First time I see the view menu !!! (how ironic
)
Ok, now I'm going on automation, all works really good... I'd love to see the a pulse blinking on the instruments but also in the timeline view while X2 is receiving midi (and no only while playing.)
Maybe there could be 2 dots into the instrument view ?(to see the difference with in/out)
And on the timeline view on the left (as it is now) midi playing from X2, blinking, on the right, blinking for midi coming in ?
Does that make sense ?
That theoretically makes sense. Until that's available, the "MIDI In" button on the settings screen will flash when receiving MIDI
(sorry, bit frustrated... just spent 2 hours waiting for my shitty 2012 Mac Mini. Half an hour to boot, another half hour to launch XCode, another half hour to "Install device support", and the final half hour for building... I'd really desperately need a new Mac but the cheapest one is $800 nowadays, and I can't really justify spending that much money on a shitty computer with a shitty OS when for the same amount of money I can build a Windows 10 or Linux box that is 5 times as powerful...)
Of course you can justify it ! All our musical workflow depends on it now !!!
Do yourself a favor ! Organise an IAP in X2 with changing tempo, sell it 10€...
Or even better, organise a collect, 200 people giving you 10€, makes 2000€ and your good to go for 5 years with it
I, personally would give 20€ without any problems and keep thinking this is a steal...
Honestly, I jumped to the Mac world 4 years ago, never regretted it...At work it's Ubuntu, and to me Mac OS is just an Ubuntu more classy and stable...
Also true that my last PC 4 years ago, I've builded myself, under win 7 pro 64 bits at the time, slowly upgraded every year, selling/buying devices was super stable and powerful...But hey, no X-code, no musical apps...It's that simple...
I just got a warning from Xequence about excessive CPU usage in the latest ios. Does this extend to ipados as well?
Yes... iPadOS is iOS, just with a cooler name. But thanks for the heads up, I have to remember now that I always have to say "iOS / iPadOS" thanks to Apple's marketing department 😁