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
Like many I think this is a great (except for the sync problems I’m having) and much needed app. From a user interface and workflow perspective there is room for improvement though, it feels unnecessarily complex while missing some key aspects. As others have also expessed, I find it hard to understand the need for a separate buffer. I made a sketch of an idea on one alternative layout :
Here I called the buffer Pad0, because it could more or less behave just like the others. You would select the Pad to work with to the left. Arming playback and recording would always be visible (for selected Pad), while more detailed controls could be selected using tabs. Copy and Paste buttons are used to copy from one pad to another..
Would something like this make sense and be feasible (som time in the future) ?
@NoonienS not sure what you mean by seperate buffer?
buffers are really midi files - so could be multi track data with meta data, time signatures etc. Its just at the moment Im using just one track with midi notes, ccs, pitchbend etc.
As this app matures it can draw on those features more, but yes it may seem strange when all you see are notes.
The main screen of Photon is laid out more as a data flow reminder (eg load button has a line from the midi files to the buffer box). I think that worked well when it was less cluttered, but may just confuse people more?
if i add more pads(which i intend to do) then data flow is replaced by a more streamlined design.
When i start the ui for the phone this will be especially true, and that could replace what you see now.
I think what he means is why can’t the pads be buffers too.
In your app the buffer is the “live” one being recorded into and you copy the buffer contents to the pads.
So good to have this, Looking forward to full statesaving.
I'd personally like to see at least 8 pads or more on an instance so you can have more sections/parts per instance, as chaining multiple instances will be difficult. So more parts to build with and chain together. I'm using this more as a session recorder/arranger as in Ableton Live rather than a looper. So other types of follow actions on the pads would also be great
.
Drag and drop the midi files to the pads would be one way to not always use the buffer, when you don't need to edit the files.
Being able to refresh the file list in each instance would be good if possible, when you record in one it doesn't show up in the other instances yet.
some kind of file/folder organisation too is something that I hope will happen.
But this is already making iOS Dawless music much more productive now
This
Exactly. I should have said that I don’t see the point of making this separation between buffer and pads in the interface. Having to do all recording and editing in the buffer while playback can only be done in pads is just a workflow killer. I dont’ think we need this concept of a buffer at all, acting as an intermediary- having selectable pads is sufficient and a simpler model to wo work with, I also think the interface would be much simpler if you center it around the pads (select which one to work with) and then use the well known copy paste model instead of having all these arrows that just clutters it and making the workflow less intuitive.
All my saved midi files seem to come back blank. What am I doing wrong?
so, changing to this should help?
make the internal buffer just another pad
groove is just another pad
load/save /share/copy/paste/rec/clear/edit/apply groove on each pad(with drag n drop too). have icons rather than words too
make more room for pads so i can increase the count!
statesaving your arrangement for a better pickup where you left off.
@Carnbot you should be able to see saved files in any instance but it does need a manual refresh. I can autodetect this though.
folders are planned, gets difficult with large list otherwise true. drag n drop within this file list makes sense then.
whats the best implementation of folders? AUM?
I have to agree with this.
It seems overly complex in the video.
Yes drag and drop midi onto pads if that’s possible now on iOS would be a good option or touch the midi file you want to use and a list of pads appear next to it and you tap the one you want.
@midiSequencer "load/save /share/copy/paste/rec/clear/edit/apply groove on each pad(with drag n drop too). have icons rather than words too"
The UX people at our place strongly recommend that you use words rather than icons. They say that icons are often too difficult to fathom their meaning.
On the other hand, words only work if they are in your language..
all good ideas folks! thx for the feedback.
Developers dont make the best designers, which is why my ui reflects internals rather than usage.
drag n drop should improve this alot, and i want to make the controls less clunky especially as I need to consider iphone sizes.
performance wise Im pleased with the low cpu overhead on record & playback so extending the number of pads is also possible. More pads means a better layout is a must so its worth doing this now.
Good on you Tony for taking all the suggestions in good spirit. I’ve had great fun with the app as I have (too) many midi files on my hard drive and this really opens up many creative possibilities. Looking forward to seeing its progress.
Top Dev!
off to the app store :)
cool - if it makes the app more useable I'm for it!
Great attitude. Thank you!
Amazing work, @midiSequencer. Just start diving into this, agreed re: state saving and folder support for midi files. Files app or Dropbox support would be great for cross device workflow, using this conjunction with Ableton or other iPads.
I like NS2 for files, very simple. AS also of course....
I’m having trouble clearing the midi from a pad. This thread is a bit long, so I’m not sure if this has been addressed. I hit the “Clear” button, but do not seem able to clear the midi from the selected pad. Is there a way to do this?
Thanks! I figured I was missing something!
UI/UX nitpick regarding the "Clear Pad Buffer" dialog: the destructive action "Clear" should be labelled in red, not "Cancel".
@midiSequencer thank you so much for this
it offers so many playful possibilities :)
and thanks to the UI tweekers too - my monkey mind have found it rather puzzling in places
Well, I have it pretty much figured out, and it makes sense to me.
I hope it doesn’t change completely.
Thanks for this amazing app! Can’t wait for all the upcoming updates!
Thanks for the video. I’m on the verge of buying this. Anyone have any other videos to push me over the edge? ⛰😮⛰
Tried this couldn't get to work.
Moved on
Will return.
@midiSequencer
Stayed up all night mocking this up for no apparent reason other than I wanted to. LMK what ya’ll think.
A few notes
The idea is the black button act like toggles (like Tony’s original) cycling through options
The lower section has an arrow/carrot on the left that switches out the pads for the groove
The play in free button acts as a normal play normally as in when each pad is triggered independently.
Two other sub options for that are pads play as a linear sequence from 1-8 and parallel play which acts the same as just pressing the big stop/start play head at the end.
similar to Tony’s original you select whether you want to record real-time or step wise and the rotary dials change out respectively to what he had mocked up.
I added an area that tells you the name of a loaded and saved midi file because I got frustrated trying to figure out what pad had what.
if you were to press view the interface of the recorded buffer would show in the pads area with the appropriate editing UI