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 am not biting on those who wish to (rudely) quibble, when this bloke is busting his impressive gut (metaphorical not actual). Very happy to see song mode. Thank you Mister EG!
While expecting a tiny human! Congratulations @ElliottGarage!
Did anyone figure this out... Help?
Version 1.0.9- Tap on bottom half of the Node button to start node immediately, on top half to enqueue start to the next bar.
Ok. Youre right.
Truth is, when I buy an app, I dont expect any new features. And as anyone can see, eg is adding everyone’s feature requests at an amazing pace. I admit I sound like a jerk most of the time.
Oh. Noticed other comments suggesting i was somehow referring to anything except the app. Thats pretty sick guys but I expect nothing less from you
There's a line in the middle of the rectangle that you tap to start or stop a node. If you tap above the line the node waits until the downbeat of the next bar before it starts or stops. If you tap below it starts or stops immediately.
ok. Thanks. It seems there are options in the settings that can also affect it...
.
Stopping a node is still immediate no matter which side of the line you tap on. But that’s a great idea: top for queued start/stop!
I'm not seeing that behavior. It works as expected for me.
[edit] no wait ... I'm seeing inconsistent behavior on stopping the nodes sometimes it works, sometimes not.
You can add an empty pattern to allow synchronised muting of a node.
Good workaround. But you shouldn't need to. I've reported the bug over on Discord.
What happened to the Master FX Bus in the beta it’s disappeared 🤷♂️
I am very disappointed with the Song node. Maybe I don’t understand how it works (yes, I have watched the video on the previous comment) but I am not sure the dev knows how musicians program a sequence of pattern. Let me try to explain this. I would like to have something like this. Is it possible in the Song node ???
Scene 1. Scene 2. Scene3
Node 1 pattern 1 on Node 1 pattern 1 on Node 1 pattern 2 on
Node 2 pattern 1 off Node 2 pattern 1 on Node 2 pattern 2 on
Node 3 pattern 1 off Node 3 pattern 1 on. Node 3 pattern 2 off
Wasn't working right so it was removed for now.
So, currently Stop is always immediate. Only Play is affected by the top/bottom thing. It was by design, but will be changed so that Stop is affected too.
Good to know. Didn’t see that noted in the Beta notes but maybe I missed them? 🤷♂️
I’d really like to see an option in the Project list to sort projects by latest/date and time as well as the current alphabetical option..it would really help quickly dropping back onto recent sessions.
I don't think it was noted. It came up in the Discord chat though.
👍 Discord isn’t for me, too much of a time drain. Normally Dev’s note such things in the beta release notes - it’s normal good communication practice.
.
It is a little confusing. Within each node the patterns retain their playing state real-time. The song scenes are just combinations of scenes in whatever state they are. So, if a song scene contains node 1/pattern 1, whether it will play or not depends whether the node has been toggled on or off.
If you want to have an always "off" for a node you can use one of the patterns, such as 8 for that and keep it always toggled off.
(At least I think this is right. Took me three times to get the post right. Hopefully no one read the earlier ones. 😂)
Just to add to what @wim has said, the project/song scenes don’t save (or recall) anything that wasn’t already saved in a node scene/pattern…INCLUDING the on/off state. So if you want a node to be off in one scene of your song, you have to first save a node scene where that node is off, then set the node to that scene, then save your project scene.
I don't think the project scenes save the on/off state though, do they?
If you toggle a node off, and save it in a song scene, then toggle it on and save another song scene, you don't end up with two song scenes with different on/off states for the node.
Right. It’s the node scenes that remember if the node is on or off. The song scenes ONLY save/recall which node scenes are selected.
I was enjoying using EG Nodes with my Roland S-1 last night - simply connecting via a USB-C cable (iPad Pro) which meant Nodes could sequence the S-1 and also the S-1’s sound was audible through USB audio on the iPad.
When I tried again today I just couldn’t get the audio from the S-1 to work on the iPad through USB audio. It was definitely sequencing the S-1 as I could see the sequence lighting up the “keys” on the S-1.
Then I tested whether I could hear it using AUM and suddenly the sound was there.
I could then use Nodes standalone (not using AUM but with AUM running in the background) and the USB audio was fine.
I assume this is probably an iOS thing, nothing to do with EG Nodes?
Can anyone advise me on a setting to allow the S-1 to be heard on the iPad using USB audio? Or do I just need to load AUM and use that to kickstart the USB audio, before switching to EG Nodes?
PS - very cool using Nodes to sequence external hardware in conjunction with iOS apps! …and using a single cable for audio and MIDI.
Nodes doesn't have audio input at this time, so yes, you'll need another host to manage that. You won't be able to record Nodes audio output in AUM either, though you'll still be able to hear it.
One "solution" (more a hack) is to dedicate one of the 8 pattern that is recorder as off per node. Anyway this is counterintuitive and having only 8 patterns / 8 scenes is clearly not enough
https://eg-nodes.canny.io/feature-requests/p/more-scenes
Thanks, vote and comment added
I don't know why but I have the impression that it ends up like Auxy...