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
AB beta, I know that AU user presets was quite a recent addition to AB3 but thought it'd already been released.
Thanks - I’m hoping to get the AB TestFlight invite soon. -cheers.
Please help, how do I get Photon to start playing the midi sequencer on pad 1 when I press play in AUM?
Set the pads option to “start on bar”. Press the pads play button. It will start playing when AUM’s transport starts. Btw, the Photon manual is worth a read. If you launch Photon as an app, it presents the manual for reading.
Thanks 😊👍
Is a loop record with overdub on the roadmap?
It would also be a super popular feature if it had a Loopy like mode where the recorded part defines a loop quantum not tied to the host tempo. I.e if you record a loop while host is not playing. Even better if it would then tell you what the tempo is for what you just recorded. (Maybe with user input as to length of what was recorded in beats/measures)
A lot of people have clamorous for a Loopy for MIDI
It is. I've only put in a basic record->playback for the moment. The loopy bit still needs one tap to continue atm, so next step is to offer more post options to continue recording - and simplify the screen so this is all more natural.
I can work out the recorded tempo from the time taken & the length of the recording. How do you see it being used?
This thread is loooooong which is good.
But I’m just curious what this app does looks like it plays records and sends midi ?
And you can send a synth creating audio to it and it captures midi from that ?
Send midi into it, record, loop. Limited editing (quantize, loop crop and trim). Six independent loops possible with options for looping to host tempo (bars or beats) or free. Transpose by semitones, change loop start and number of beats, chain loops together with number of repeats for each. Import and export midi loops. Apply the “groove” of one midi file to loops (can’t say I really get this one yet).
That’s just a quick rundown from memory. The manual does a much better job: http://amssoftware.org/manual/PhotonManual.pdf
No.
Thank you @wim ! Very cool, I'll read that url too looks like something I could use 😎 as do most apps right now haha
How is state saving coming? Can you tell I have a one track mind when it comes to this feature?
I’m not sure if it was noticed in the bazillion of messages in this thread, but there’s a little quirk in relation to this. Pressing stop when recording doesn’t stop recording instantaneously. It quantizes to the next beat (or maybe fraction of a beat) of the host tempo. This happens with or without the host running. For seamless looping independent of host tempo, immediate mode recording and dump to pad needs to be independent of any host influence.
I can see no other way of calculating the tempo other than the user inputting the number of beats or measures. I think the hope was that it could be automatic, but I don’t see how that could be.
The other thing asked for was for the saved midi files to not adjust to the tempo of other hosts when imported. I don’t know if this is even possible. Can you save a midi file without tempo information? But for sure, it’s important in this scenario that the calculated tempo, not the host tempo, be saved in such a loop export.
Applying a 'Groove' literally means changing the timing of the midi notes in one file(your recorded buffer say) buffer to match another(groove file) - it changes all the timing.
This means the groove midi file can be thought of as a template - its normally a simple few notes (including rests) that is short - this short template is repeatedly applied to the buffer notes - so you get pitch, velocity etc just not the timing of the buffer mixed with the timing from the groove.
I've added options to apply this to timing, velocity or both, and you can also dial in a strength (0-100%) to lessen the effect.
My video explains how this could be used to change Mozart's All Turka (a noticeable rhythm) into Bach(no rhythm - not that Bach lacked it of course - just sounds more his style!)
I’ve tried this with an 8 bar loop, applying a 1 bar shuffle groove drum loop. Every time the 8 bar loop turns into a 1 bar loop speeded up. It has the groove, I assume, but it’s way too fast.
I couldn’t figure out what I was doing wrong.
getting to it soon - its top of my list to do on Photon now after some testing Auria Pro's new midi fx.
Photon attempts to round up recordings because normally you want to loop it using some sort of tempo sync (eg host bar/beats). I will look at how I've done this to see if a)there is no delay in press stop to actually stopping b) If I can offer an option to work with non-integer beat length recordings(they could be something like 1.9877876 beats!)
Doesn't Loopy calculate the bpm from the recording? I may be wrong need to test this out with Loopy/Enso etc
Each host may interpret the midi file tempo (there is a tempo track) differently. I do detect changes in tempo & write them but each host may or may not use this.
send me the 1 bar groove & 8 bar loop - just to be sure its working as expected.
You add rests in a groove to slow the final result down, add notes to have notes played.
Maybe spend some time with Loopy. Typical usage is to not preset a tempo. You start recording and the instant you stop, loop playback starts. In essence your playing defines the quantum. With photon, you would need an option to ignore host tempo. And have an option that the recording stop point defines what the loop point is.
Loopy is like magic. And after you have recorded, you can tell it to sync to host and it stretches/condenses to match the host.
Sent.
As I understand the requests, this is not what is wanted. The requester wants to be completely independent of the host tempo, controlling the loop point manually without any relation to the host tempo. The point is to play freely and worry about the tempo later.
It was also hoped that this would then calculate the bpm automatically, and even to set the host tempo to match. The former seems to me like it would need the user to put in the number of beats or measures. The latter would be impossible from an AU, I believe.
So, the user would have to input the length of the loop, the app would calculate the tempo and tell the user the bpm, then the user would need to set that in the host without altering the recorded loop tempo.
I hope that makes sense.
@wim but Photon allows you to dial in a loop length before recording.
Whilst recording at one tempo I can of course allow you to change it or have Photon auto-size it say.
Will look at Loopy some more to capture this magic
I think what you aren’t understanding is that the great thing about Loopy is that yo7 can record without knowing the tempo ahead of time. You get a Groove in your head. Tap record to start recording and tap again when your phrase is done and it loops seamlessly without your having had to figure out the tempo, etc. or even having needed a click. You don’t even have to have known your loop length.
Maybe there are some short demo videos someone can post.
It is a deservedly legendary app. People keep asking when there will be something MIDI-based with that same approach. It seems like Photon could be that app with just a few tweaks.
That’s the opposite of what I’m describing people want.
It’s simple really. Play something, not worrying about what the tempo is or how long the part will be. Hit stop when you (not the host) want the loop to end. Start looping. Come back later and sort out what the tempo was.
This works just fine and dandy with Wait on Key, Send to P1, and Start Immediate. Except that you quantize the record stop to the host beat, which throws the loop off. The other problem is the host tempo being saved in the loop, since the host tempo wasn’t used. Unless there is some way to figure out what the host tempo should be changed to in order to match the loop ... without changing the loop tempo in the process.
thx, let me work on this then
Awesome, but not before state saving!
Have I mentioned how great Photon is lately? Thanks for this really great app.
thx - I'm working on state saving now
@midiSequencer : yes, Photon is great. I am finding it superuseful as a notebook/sketchbook for capturing ideas.
I haven't been following the whole thread....I've just been checking in occasionally (because I use just an iPhone), but am I right that Photon is not yet universal? Thanks in advance!
@midiSequencer : it would be great if the edit buffer's length dial were sensitive to the length of the buffer. I was just recording something that ended up being 37.3 measures long. I wanted to trim to 36 measures but the length dial maxed at 24. Maybe, the dial's range can be shifted to account for the buffer's length?