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 just realized it seems to happen with Tonality Chord Pads AU and Tonality Circle of Fifths AU. I just did a session with scalebud2 and it recorded into the steps in order as expected…
@rygrob
@rygrob any update on fixing the ooda stuck midi notes in cubasis 3?
Problem solved. Thanks for the fix @rygrob
Just a heads up There was an update to the beta that stops redundant midi messages which fixes the issue I was having from Tonality Circle of fifths. Cheers.
@Nimgwen i wonder if this might help fix ur issue as well. Hopefully.
I love this app!. Such a pleasure to play with, the UI is simple and elegant.
I do have one request, one of those where you think “why isn’t everyone else demanding this?”.
I’d love/need to be able to edit the chords!. It’d be as simple (ehem) as showing the notes on the keyboard when selecting a step.
When I play with kind of apps I don’t what the hell im doing, end up with something I quite like but there’s obviously some wrong notes. As I don’t what the initial chord is I have no way of fixing it.
@rygrob would this be complicated to implement?.
We mentioned this at the release and were throroughly shot down. Apparently, the uncertainty is part of the fun.
Wow 😮
I strongly disagree. As I said it’s all about improvising and certainly uncertainty. BUT at some point you want to fine tune or fix (in order to make it usable ) what you did. And I haven’t got a clue of what I did. I’m not talking about a sus7 11th, I don’t know what the root note was. I don’t see any added fun or immediacy in not being able to see what you did.
So we’ll have to use Atom, Drambo, stepchords or whatever to do the chords, then record them into OODA. Talk about immediacy and fun!.
@uncledave Linking to my post explaining why the dev might not be so quick to implement your request is far from being “thoroughly shut down”? I’m flattered you think my argument was so strong though 🤓
I was merely trying to point out that it may not be as easy to implement as you think and your way stating how inconvenient the app was came across, in my opinion, as a bit entitled and snarky all things considered so I thought it might help to give my thoughts on why things don’t work as you’d like.
I have zero involvement with the app so you might want to reconsider how thoroughly you feel like you’ve been shut down? It’s not like I ever had a say I it no if I did, I actually agree that it could be a helpful feature so I’d be on your side. Not everyone is actively out to get you and shut you down, some people just want to try and show a different side to the story ❤️
Edit: for what it’s worth I really like Tahiche’s idea of the in built keyboard to displaying the notes of a cell.
@rygrob (I think you're the OODA developer, sorry if not)
One change I'd really like, which would improve OODA's useful as part of a live/improvised workflow.
It's possible to select a cell and re-record its contents, but if the app is in PLAY mode, this selection is immediately deselected, since the playhead moves to another cell and erases it. I'm guessing the playhead marker and the selection marker are the same?
I'd love to have a persistent selection so we could re-record the selected cell during playback, rather than having to stop playback and break the flow.
Unless this is currently possible?
+1
I've also suggested the same thing to developer during pre release beta, showing and editing notes on in-app keyboard. Hope it could be implemented at some point
I'm also loving this app. I'm using it to sequence a polyphonic module in my Eurorack case. OODA's wormholes are great for programming repeats, bridges, and other structural elements into a song (which are quite difficult to do in the modular).
Late to the Ooda game and liking the concept but a question:
Is it possible to transpose the sequences from an external MIDI keyboard?
You can load OODA as an AUv3 plugin. For every voice you have an "Offset" parameter that transposes the notes +- 24 semitones (2 octaves). You can then use your plugin host (AUM etc.) to map this parameter to a specific note range.
Yep, using it as AUv3 and I know I can map offsets to MIDI cc. But I want to transpose my sequences using MIDI notes, as can be done with Zoa.
I was rather surprised that this is not implemented in Ooda.
Am I missing something?
Mapping the parameter to Midi notes can be done in the host. For example both AUM and Loopy-pro allow you to choose the MIDI message type for a mapping.
Unfortunately, AUM maps notes sort of like CCs. It sends the velocity of the selected note as the parameter for Note On, and sends zero for Note Off. So that's not very useful for setting transpose intervals.
I've made a StreamByter script that converts note values over a 4-octave range into a CC that will set the Ooda Offset parameter to values in the range [-24,+24]. Copy the script into a StreamByter window and remember to Install Rules. You can save it in StreamByter for future use.
Awesome @uncledave
There’s a cool new Mozaic script on Patchstorage that allows you to mess with the midi channels. Can be used with several apps but specifically mentions working well with Ooda and zoa.
Sequential Channel Switch for Mozaic
That is a amazing! Thank you very much!