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
Hey Cambler, thanks for giving Prism a go! This is the first I'm hearing of this behavior. I had a few beta users who were using Cubasis and they never mentioned anything. They are two hosts I don't have and was never able to personally test on so strange behavior isn't unthinkable. More likely than you being daft at least. I'll do a little digging on my end.
**If anyone else has Cubasis or Logic and can confirm this behavior on their end that would be a huge help.
**
Generally though, you need the host playhead running to press play in Prism, but it shouldn't have any impact on your ability to playback notes with the keypad.
Yes you can, in a limited sense. You can [peek] at any other seq (track or drum pad) from the Fuse menu. In your case you'd want to
1) make sure you have the drum pad you want to edit selected.
2) Next go to fuse.
3) Then press peek.
Once the peek method is selected you can select a track to watch/monitor/peek (whatever makes the most sense to you) by
4) [LONG PRESSING] the source track on the seq
because you want to see the same track, but a different drum pad, you'll want to -
5) long press the current track
You'll see the right keypad change to "[WATCH] Source Pad"
6) press the pad you want to see along side the pad you're editing
7) go back to 'SEQ' to see the changes apply and edit the track
Note - This process always works to monitor the laid trigs across tracks. Step 6 only applies if you want to peek at a drum seq
As I type this out I'm thinking you have too common a use case for this to be so many steps. In fact, I added a shortcut for layering drum pads (effectively the echo functionality) to speed things up in just this situation. I think I'll do the same here.
@A_Mortal_Mage you're a total gem. Thanks so much for the quick and full response and for looking into those things. I'll continue playing and if I come across some glaring self daftness on my behalf, I will, without a pause for personal pride, let you know
@A_Mortal_Mage Something I’m curious about… how do you go about developing the app itself? Xcode, SwiftUI/UIkit? Any other embedded languages or frameworks? How do you exercise the app as you go? Is the iOS emulation sufficient to test touch gestures, and how do you drive a synth? Or do you do a bunch of work, compile, load to the pad, and test, lather rinse repeat?
A manual is ok, thanks.
I like the videos on YT, the content, the background, the tone… but the hat is in the way! 🤭
Congrats on the release.
Cool, I'll get to work on that and update the forum as parts are available.
Haha too much hat. In the most endearing way possible this is the hat reaction so far:
Hey Garden, there are a lot of options here. Because I originally built this thing on an Arduino microcontroller the entire background library is in C++, which is generally recommended for Audio Units because efficiency. There are a lot of frameworks to speed up the process (Juce, Audiokit, etc.). For flexibility and to support future developments I decided to keep things as simple as possible and cut out any middle men. Right now it's C++ as background, objective C file as a bridge, and SwiftUI for everything else.
For emulations, I could never get the audio units to play on iOS's simulator well. You need to add a host to the simulator to test but as far as I can tell Apple doesn't provide this. There were a few outdated libraries and I ended up writing my own. But, in the end it was easier to do the 30 second compile and push to my physical device. From there I tested and checked it all in AUM. Lather and rinse x 10,000.
Happy to answer any other questions to help you or anyone else jumpstart their journey.
Hey Gaga, find this fixed in the latest update. Thanks for catching and bringing it to my attention
As promised here's the start to a "Getting Started Guide". Right now it covers the layout of Prism. Still very much a work in progress, but better than nothing.
https://sites.google.com/view/prism-midi-sequencer/getting-started
Navigating the UI is taking some work, but I’m beginning to understand why people like the Elektron workflow so much.
I’d like to request more contrast in the UI. On the iPhone 12 my old eyes have a hard time with the various shades of grey in Night Mode; Day Mode is considerably easier but I can’t read the keypad labels at all. Some of the icons are also very very tiny. As well, Prism seems to be defaulting back to Night Mode when I reopen Loopy Pro. I’d prefer the theme change to persist.
Nice app overall, congrats on the release.
I can’t figure out how to change midi output for making new drum maps. There is much about the UX that I don’t find intuitive and the lack of mapping for Bram Bos apps brought some sorrow.
Prism ❤️ Koala. It’s a really nice combination.
@ahallam thanks so much for the feedback. This is really helpful! Thanks for the kind words too.
I hear you on the coloring. This is one of those I can't know until worse eyes than mine see. I'm hitting the books to learn more about ergonomic color schemes to solve this. In the mean time I'll fix it so that the Night/Day mode setting persists across restart.
Also, for the keypad labels in Day Mode, what you're seeing is a small bug. I'll fix this too, but if you exit device settings the keypad coloring will reset to a darker tone that works better with Day Mode.
Please please please poke me with the parts that you find unintuitive. I'll do my best to build more clarity into the design. And thank you for doing so with the drum profiles. I'm going to try and make the functionality more obvious but in the meantime you can update the drum pads midi output when you select the drum profile. If you drag the box that says "output" you'll see the corresponding MIDI number displayed. Select another drum pad to update its MIDI. When you're done press "Save" to save it as a new drum profile.
Finally, I can add the Bram bros profile with your help. I've got a running sheet people can post desired profiles for the apps I don't have and I'll include them.
https://docs.google.com/spreadsheets/d/1qa7ehZVBxxxiQMrME2W2OwuL0j4Db-KAwCK2IhasMXE/edit?usp=sharing
I feel like you sold me the gateway drug to a Digitakt for 12 bucks.
Hopefully Loopy Pro/Prism/Koala/Patterning won’t overheat my iPad, cuz it seems like a really good combo.
I feel like it would also be a good addition to BAM if they implement internal midi routing and recording midi fix to the piano roll.
That’s great. Loving this app!
This is a great start, thank you. Also for your description of your development process. It’s interesting to learn how this kind of thing comes together.
I actually had a digitakt for a little while. Hated it, sold it. Something just… didn’t fit. I certainly see its influence here, but this is very much on its own trajectory, and I’m glad for that.
It’s been a good time for interesting sequencers lately and I’m glad that Prism has joined the fold. I ran through the YouTube playlist yesterday and it’s obvious that it’s quite deep and a lot of love has gone into bringing it together.
Every sequencer I have outside of Drambo has left me wanting more options for per-step parameters. I haven’t touched that aspect of Prism yet.
@A_Mortal_Mage does it do ratcheting? I haven’t stumbled on that yet either.
@A_Mortal_Mage Just updated Prism to 1.02 and lost all my project settings inside the AU version loaded in AUM controlling 3 instruments.
Did the update break state saving ? Now nothing is playing and I get the start up menu again welcome to Prism.
Bit of a non starter for me if the app can’t state save after updates.
Hey @Jumpercollins, that shouldn't be happening. It sounds like a bug I need to get to the bottom of. I'm taking a look now. Could you help me out and provide a video or some screenshots of what project settings your missing. Unless you mean entire songs are missing, in which case how are you saving and loading them?
@ahallam no ratcheting yet. I have a pretty major update planned down the road for step or trig fx. It'll come as part of that.
I'm struggling to reproduce this on my end so any extra details you can provide would be so helpful. Can anyone else confirm if they saw saved settings / data drop between builds?
I just saved my Drambo session, closed Drambo, upgraded Prism, opened the saved Drambo session, and Prism retained my settings. 👍
@A_Mortal_Mage I had 3 instruments playing fine. Saved the session in AUM. Done the update a hour later reopening my AUM session with Prism in and now the session won’t play and all my trig positions that I inserted into the sequencer appeared to have dropped out just X in the positions. The instrument names are still there.
When I opened Prism I was presented with the thank you for buying Prism screen and help was on. Which I never left in that state. Also the AU window size was larger than what I left it.
As the session was saved in AUM is it a problem between the 2 apps. Do I need to save the project in Prism itself ?
Annoying I lost a hours work but it’s early days and will try again.
@Jumpercollins
Not commenting specifically on your current problem, I’m sure that’s being looked at, but I have found it works well to first set up the project in AUM as something like “Prism Template”. Then, working in Prism I would start from New Song, set up my tracks as Drum or Tone and then save that in Prism with a name such as “template”. Then I save the “Prism Template” project in AUM. You only need to do all that once but you’ve now got your starting point saved and synced in AUM and Prism so you can start new projects with everything set up.
When I start a new song I load the “Prism Template” in AUM then save it as the song name. In Prism I then load the saved “template” and save as the song name and finally save again in AUM so that AUM and Prism are synced with same starting point. I then carry on working in Prism. I will save periodically in Prism, especially if I add a track or create new arps or harmonizer pools. If I make changes to the instruments or effects outside Prism, I save it in AUM and if I’m leaving AUM I save it in AUM. I’m not suggesting this is the best way or only way but I’ve recovered from a lot of my mistakes and a couple of bugs, using this method. As I’m gaining more confidence in Prism I make less mistakes and don’t feel the need to save so much but it is a new app after all so there may be the odd problem. I’ve even saved a song in Prism in AUM then opened it in loopy pro and vice versa and it works fine. Prism seems to be very self contained.
Hey @Jumpercollins, thanks for posting the photos. I've got a few questions and an ask that will help me narrow this down.
1) Any chance 1.02 was an update from the beta, or any mix of beta stuff going on (you had beta right?). I ask because this was exactly something that happened between some of the final beta versions and the live.
2) If not, and either way, would you mind exporting the AUM project and sharing it with me. I should be able to open up your Prism session and poke around for answers. You can send it to [email protected]
3) I posted 1.03 for apple to approve last night. Should be up soon. Before installing could you do a little test on your end to confirm if the save behavior worked as expected.
Saving sessions from AUM should be rock solid, it's the only way I've been saving. We'll definitely get to the bottom of this.
Does Prism support step input? I mean that whenever you enter a note (or chord) via the pads or an external keyboard, they will be recorded into the current step and the cursor advances to the next step, ready for the next note.
@A_Mortal_Mage I was wondering if it was a beta problem but I’m pretty sure I went over to the store version before starting the project as flipped over on day of release. See below , however that may of what caused it. Currently I’m on 1.02 with the update 1.03 sat there. However the beta retired version does still say open.
I emailed you the session file from AUM not much in it as lost my trig steps. The 3rd instrument I was just starting on before this happened so didn’t have any midi data to send.
@Jumpercollins I'll take a look, thanks. Glad too much wasn't lost but zero is the only acceptable answer.
P.S an update is now live. Try saving a test project with 1.02, updating, and reloading. Crossing my fingers
Not yet, but it's on the list.
Hey @ahallam, I played around with the contrast following some accessibility standards. The latest update should be much easier to read. Feel free to put Prism on the proverbial washing machine and circle any areas in red that you find difficult still.