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
It’s in video 4. You have to open the in app keyboard, it then shows a few more buttons one of which is deleting last step. See bottom left of screen.
The left and right arrows move the keyboard up and down octaves but the ones above the arrows, I think the undo looking one is the one that does it.
Thanks
Got it. Haven’t used the in app keyboard as I’ve been working on the iPhone and space is limited. Will give it a look.
Pipe it to Atom2 and use that app’s awesome swing and quantize.
Getting tons of stuck MIDI notes in cubasis 3 can't really make use of it like this
Lovely!.👏
Are you doing chords here or single notes?.
I do wish you could see and edit notes in a step. I don’t think you can. Can you?.
OODA sends Note On, velocity 0, instead of Note Off. This is a valid alternative, but could it be a problem for CB3, or maybe for the synth app?
Edit: Are you using more than one voice? If so, how does it work with only one voice?
Chords. 1 chord for each of the 4 steps. Basically followed the devs recipe in the voices video. One voice devoted to bass (pace=whole, rule=lowest), Sync voices=on. The rest flavored to taste.
You can’t see the notes in a step but you can re-record (see @CracklePot’s and @Poppadocrock’s notes above). Being able to hear the notes in a step by double tapping or some such would provide nice feedback when tweaking a sequence
Not sure I get what you mean by "Note On, velocity 0", I'm still a noob in understanding MIDI. I'm just using one voice, just a sequence of 4 notes like a simple arpeggio. The notes get stuck on different synths inside cubasis (animoog z, synthmaster and micrologue (cubasis own internal synth)), so I don't think the target synth is the problem. Also I launched OODA as a standalone app and sent midi to cubasis and in this way the notes do not get stuck, so the the issue seems to be in how OODA as auv3 inside cubasis is producing the midi. I do not get stuck notes from other auv3 midi generators, even when playing absurd amounts of notes very fast (fugue machine, rozeta collider ).
Or displaying the notes on the keyboard… I usually just noodle around and just lay down whatever. End up with some bad notes that need corrected, but now I have no idea of what the original chord was.
This has been raised with the dev, and he's looking into it. It gets worse as buffer size increases.
I'm wondering if the stuck notes might be device-specific. I was using Ooda in Cubasis 3 last night with no problems, sending Oodas voices out to 4 separate midi channels, recording midi, etc. This was on an ipad Air 2
Have you tried running it fast? I was getting much more stuck notes at 160bpm with 8th and 16th pace voices.
Can you show me how you set it up? Maybe if I replicate your setup it works better.
I'm on an ipad pro 2020 (IpadOS 15.4.1), also I'm still on cubasis 3.4.1 (I was afraid of the folder deleting bug of the last update). My setup was just creating a midi track, loading an auv3 synth (synthmaster 2 or animoog z) or using cubasis micrologue. Then simply inserting Ooda as a midi effect on that track and playing a simple 4 note arpeggio at pace 8th and 120bpm.
This are my cubasis audio settings (just in case latency or multicore processing has something to do with it)
Hopefully some of this info helps the dev find a fix.
>
Yes, I ran the project @ 240 bpm and all worked fine
Track 1 hosts Ooda
Track 2 (microsonic) input=Ooda 2
Track 3 (synthmaster 2) input=Ooda 3
Track 4 (microsonic) input=Ooda 4
Track 5 (neosoul keys) input=Ooda 5
Screenshots:
You can set the Action buttons to Latch Mode, and use the Hold Action to keep the play head on a specific step while playing back. You can then pick which node you want to listen to, hit the Record button (select your node again if you see a different node marked red, so you are editing the node you are hearing), then just enter new notes and hear the node update.
It works pretty well for editing by ear. You can step through your nodes and edit any that sound bad or have errors. You can engage/disengage the record button while the sequence is playing. Just make sure to align the record (red) marker with the play (orange) marker to edit the node you are hearing. The record marker advances with each edit, but the play marker stays where you tap when in Hold mode. Also, if you press Stop while in Hold mode, you have to toggle Hold mode off to get the Sequence to start playing again after you press Play.
That works great @CracklePot . Thanks.
So I tried this and surprisingly sometimes it works fine even at high speeds, but then I start the playback again and it gets tons of stuck notes again, it's unreliable. I also attempted to record automation and it also kind of works and kind of doesn't, for some parameters at least, but for most it does not work at all.
Here I recorded the MIDI in 2 different takes with the with the exact same setups, ooda controlling 4 MIDI tracks. Ooda is on the second muted track as a midi effect and the midi is routed to synthmaster, microsonic piano, microsonic bass and magellan 2. They should all be getting the same notes. You can see that in one take 3 notes got stuck all the way through, but on the other one it played the 4 note arpeggio just fine.
Strange. Not seeing that here. Hope you get it sorted out
Using OODA with Eurorack is a lot of fun.
Great tip. That “latch” setting is very useful. Thanks!
I still wish there was a way to see the notes on a node, though.
BTW. Is there a way to delete a single node?. Sometimes with the “auto advance” of the record playhead you get an unwanted extra node and I can’t seem to find a way to remove it.
To get rid of the extra node, stop the sequencer and be out of record mode. Activate record mode, and you get the red marker on the node just after the extra one. Hit the circular arrow key on the built in keyboard (on the left side). The red marker moves back onto the extra node. Exit record mode, and the extra node should be deleted.
You can delete any node you want while in record mode by placing the red marker on the node after the one you want to delete, and tap the circular arrow.
For seeing what notes are recorded in a node, I would just try using a midi monitor. But I have been getting by with just my ears and haven’t monitored the nodes yet.
Giveaway+demo video
Good call!
Definitely, or Mozaic as a workaround. I requested a global swing, and developer liked the idea. Could take some time to implement though, we shall see.
So this DOES have a “hold” option to hold notes across multiple steps?
Or no.
+1 on this. I was about to ask whether there was a way to midi control hang, bump, flip and shift
I will buy when there midi also.
I’m not sure if it’s user error or the app, but I’ve been having trouble recording in steps starting at 1, and going consecutively. For some reason it jumps to 4, 8, 12, 16. After I mess with it for awhile I get it to work, but I’m not sure why it’s not starting at step 1 and going in number order from the start. Here’s a photo to show you what I mean. Trying to record in step one, just kept jumping to step 4. Anyone else noticed this? Or know what I’m doing wrong here.