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
The general idea is to have a container where you can drag the 8 bottom scenes in any order and any repetitions. Similar to the song mode of EG Pulse
In this case, please allow us to save the state of each node in the scene (toggled on/off)
@cuscolima it’s already working on this way, mode state, including toggle on/off, is saved into scene
@ElliottGarage Cool! Thank you for letting us know!
Yes but the problem is that if you use the same pattern in different scenes, then the state of the node will have impact on every scenes. Ex. with two nodes and one pattern on each node. Scene 1 = node 1 on, node 3 off, scene 2 = node 1 on, node 2 on. If I play scene 2 then scene 1, scene 1 will have the two nodes on
Cool!
Is this scene behaviour a bug?
I have four scenes that I work through to switch on particular nodes. All is fine pressing in ascending order 1,2,3,4. If I then go back down the scene numbers, the last node switched on in scene 4, remains switched on in scene 3 and 2, then goes back off in scene 1. This behaviour does not happen with all projects, just the occasional one.
Yes, I know I should be posting this on the other site, but it won't let me log back in again.
EG Nodes 1.0.8 UPDATE availble in the store
Mixdown - Added individual tracks export
Mixdown - Added 24 bit option
Added Mute/Solo buttons state
Sequencer - Fixed hold issue on last step
Sequencer - Options in settings to always show notes
MIDI Learn - Added midi channel support for midi learn
Added search in saved nodes list
Auto close keyboard on scroll after a search in plugin, node or parameters
Fixed Generative node not recalling pattern speed
Stability & Audio engine improvements
Fixed audio not playing after project loading
Fixed Mute/Solo not working on some devices
Fixed Slider/XYPad menu not working on some devices
Fixed bug with presets saving (memory limit)
Fixed scene not recalled correctly when blank
Thanks.. digging in..
@ElliottGarage is on a tear with this one. Another update dropped this morning. I’m really happy with the app, and the way the developer has been consistently fixing, updating, improving. Already fixed like 4 requests I mentioned. There’s a reason it’s been in the top 10 paid music app in the States since it’s release.
BOOM!
been following the thread and watching the YT videos and this looks like a wonderful app. Kudos @ElliottGarage. My mode of composition and production has always been timeline based (I still have AUM sitting here gathering dust!) so not sure I would have a lot of use for this in standalone however I love the idea of using it as an auV3 in a daw. So for anyone who is currently doing this can I ask what the CPU usage is like in this configuration? I realise it depends on how many nodes are being used and which auV3s are being used inside each node (I assume this is possible when used as an auV3 inside a daw?). Also am I right in thinking that more than 1 instance of Nodes can be used in a (daw) project? Thanks gang!
iOS doesn't enable hosting AUv3's when an app is itself being hosted in another app. So, no, this isn't a possible configuration. However, Nodes does work well as a midi sequencer within other DAWs. Most allow you to record the midi output to their timeline based clips, so this could be a way to generate patterns for further arrangement in a a timeline based DAW.
I've not measured CPU usage, which is close to impossible to do in a meaningful way in iOS, but it feels light to me.
Thanks so much Wim. Bummer. I think my use case may have flown out the window
Just on this can anyone who is using Nodes as a midi auv3 inside a DAW comment on their experience?
What DAW(s) did you have in mind. I'm up for some testing if I have them.
Bless your socks Wim! I’m principally using Logic but also still dabbling in Cubasis if you have either. Thanks so much.
Sure, I'll mess around with Cubasis this evening. I'm on Node's beta so that's the kind of thing I should be doing anyway.
You’re a gem. Thanks so much.
meh. So far not encouraging at all due to midi routing limitations in Cubasis. MIDI FX work best in Cubasis controlling just the channel they're loaded on. Nodes can be used that way, but that isn't its strength. Its strength is providing a centralized place to flip between sequencers that match up well with the apps you're using and what you want to do with them.
For a simple setup you'd add a separate instance for each instrument you want to control. There's little benefit in that if you ask me.
I tried using midi out track routing but it isn't practical. I set up a midi track with no instrument. Then I set up a couple of midi tracks with instruments on them. Cubasis only lets you route out to a single other track, but if you "chain" tracks using midi thru, you can pass midi through from one track to another so that they all get a copy. It's a little cumbersome to set up, but I've used it before with multi-out plugins and it's been OK.
However, it doesn't work for multiple plugins because Cubasis doesn't filter the incoming midi by channel. I set up a couple of nodes and set them to output on different channels. Then I routed to the first instrument channel, engaged midi thru, set the output channel for the second, etc. But, the first channel receives all the output, and so on down. You can't filter each instrument channel. I tried using mfxStrip instance to filter by midi channel, but it had no effect.
Sorry, but I don't see any way to use EG Nodes effectively in Cubasis. I suppose you could use it standalone to send midi out to cubasis channels, but you'd be flipping back and forth between Cubasis and Nodes all the time.
Wim you are incredibly generous to not only test this out but also for your detailed commentary. Really do appreciate you taking the time to do this my friend. It’s a pity. I really wish there was some way to use it as an auv3 instrument but I understand the iOS limitations. I may still dive in and use it standalone but I’ve never really gelled with clip based sequencers. Maybe this’ll be the one that changes all that
Hey, no problem. I enjoy trying things out, and often something I'm checking out because of a forum post becomes the starting point for a great evening of music making. And I like trying to explain things, so posting isn't work, it's a form of relaxation.
All I can say about Nodes is that I didn't see anything I needed from it and was going to pass it over because I already have way more sequencers than I need. I especially didn't need it as a standalone host. But I got it out of curiosity, and I'm very surprised at how much I like it and how much I use it. And I'm also surprised to enjoy it as an AUv3 host as well.
There's something about the way it flows that has been helping me get out fun ideas quickly. Not the way I usually create, but in a more "try this and see what happens" kind of way. I actually like most of what comes out, and that isn't often the case.
So I'm having fun with this one. Is it going to become the cornerstone of my workflow? No. But I'll be reaching to it often for inspiration. Probably mostly as a sequencer in Loopy Pro, but also quick for standalone sessions on the couch (I call 'em throw away sessions, because I rarely even bother to keep them).
Great to read this as I think I'll probably be in the same boat as you. It intrigues me and at the very least looks like a lot of fun. I've started to think it may be interesting for more experimental or even ambient work and also for creating textural and melodic "chunks" to bring into a DAW project. I've got a birthday coming up and my family know that an app store card or two will make birthday boy happy so I think I know what I'm going to blow that on
Interested to hear you talk about using Nodes as a sequencer in Loopy Pro. Not across Loopy Pro but I assume you are not using it as a midi auv3 in LP? Or are the issues you mentioned above in regards to Cubasis an issue with that DAW in particular?
@Cambler : Cubasis has midi routing limitations that Loopy Pro and AUM don’t.
The issues I related earlier are specific to using Nodes as a MIDI effect in Cubasis. I tried to work out a way to set up routing to make use of a single instance of Nodes to play more than one track in Cubasis. I couldn't find any. I've not tried in other similar DAWs.
In Loopy Pro, EG Nodes can be used as a MIDI effect to drive synths hosted in Loopy. Each node can send on a separate midi channel, so all you have to do is set your synths to receive from Nodes on only that channel. It works well.
I had settled on using Drambo for midi sequencing duties in Loopy before this. It works well too, and probably will remain the main tool, but Nodes adds access to more creative tools in one package, so it's a great addition. Anything to break up creative blocks sometimes eh?
Awesome, thanks for the explanation Wim and also @espiegel123 !
Just picked this up and it's awesome sauce. One Q: when using Nodes with a hosting app (like AUM), is there some trick to getting more than 3 nodes loaded? On my iPhone, after the 3rd node the "+" button disappears/is covered up. Not a problem in standalone mode - the nodes instances just shrink enough to leave the button exposed.
Scroll down to a new row to see the plus button.
@Tspae
On iPhone just scroll the screen up to show a new row with the plus button available
Boy, I should’ve seen that coming. Thanks!