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
See my note above: use the Save to Files option instead and save into Audioshare that way.
Audioshare only accepts one clip at a time with the Open in action. The same is true from any app to Audioshare.
I understood. Thank you very much.🙌
The updated version now works with iOS v12 and v13. I just installed it on my iPad Air 1. No testing yet, but very excited. I've been using Loopy and Loopy HD since iPad 2.
Loopy Pro is:
That’s very interesting - it looks like your iMac isn’t announcing itself properly over Bonjour. Are you positive the network session is enabled and setup on the mac?
FWIW: I just checked and I see Network MIDI Sessions fine in Loopy Pro. (MIDI Fire not needed despite implication of my previous post).
Here’s your issue I think – pretty sure you need to fill this in
True, now working.
(And finally I get control over network session midi, I mean I have now two pipes between iPad and mac)
Thank you and sorry for lame question.
But I have next , can I ask?
Playback colors mixer volume sliders - I can Midi learn them and its working with feedback to controller. the same with donuts - everything working with midi mapping.
But somehow Input hardware audio sliders didn't respond to learned MIDI commands.
Is there a known issue?
Can you explain more or demonstrate what you mean about sliders not responding to midi?
I'll allow it.
In the mixer
BUS strips offers no midi mapping.
COLOR offer volume mute solo bal and send - all midi mappable and with midi feedback.
HARDWARE INPUT and AUDIO UNIT INPUT - here the same, but volume is not responding to MIDI.
Can you explain more (or post pictures/video) about what this means: "HARDWARE INPUT and AUDIO UNIT INPUT - here the same, but volume is not responding to MIDI."
Do you mean that Audio Source->Adjust Parameter->Gain is not working when midi mapped?
If that is the case, does the action work if you map it by hand in the MIDI Control manager in Loopy?
@espiegel123
thanks! as you suggested , MIDI mapping is working (via widgets)
If you could tell me about what didn't work, I'll try to reproduce and let Michael know -- if there are little details not working as expected he'll doubtless want to know.
I’m still stumbling over this one shot issue…is there any way to not sync to a BPM?
Can a pad in Loopy Pro function like a file player set to one shot does in AUM, ignoring the clock and tempo settings?
Currently, changing a project’s tempo time-stretches all clips. But you can import so clip okays unchanged as long as you don’t subsequently change the project tempo. Turn off time-stretch in that import dialog and the clip will play at its original speed as long as you don’t change the project bpm after you import.
That time-stretch switch tells Loopy Pro to time-stretch on import.
This app is awful in handling AUs. I have yet to have an instance where I didn't run into problems. Latest one was a set up where I took the time to assign some controls to FabFilter's Saturn, only to have Saturn not load when I opened up the app again, so all work lost.
How does this make it past testing?
Is the issue repeatable?
What other AUs did you have problems with?
What hardware are you running on and what OS?
If you’ve a project that won’t load correctly, Michael would probably want to look at it.
A manual is coming. There is some useful information on the wiki (including a pdf of the tutorial).
Ask questions, and I am sure someone will answer your questions.
https://wiki.audiob.us/doku.php?id=tag:loopy_pro&do=showtag&tag=loopy_pro
That’s the constraint that’s complicating things for me, because I’m working with live tempo changes in a performance while sampling from multiple one shot sources of varying native tempos.
In my case the workarounds are either to add follow actions on specific pads to set the master BPM for each one shot, or to use instances of Auditor AU File Player in place of one shots. The former doesn’t work for live recording because the speed transitions aren’t seamless in Loopy Pro yet and cause audible glitches in playback, the latter is ok for live performance but requires some creative follow actions and bus routing to do things that could be less complex with one shot pads grouped by color.
Hopefully in future updates this can be addressed, ideally by allowing one shots to optionally ignore the clock completely.
I was sleeping on beta and jumped on the train this Friday. And what can I say besides "gamechanger"?) I came for the super looper, instead got super-duper ableton alternative with retrospective looping, classic loop grid, timeline, performance layout, and godsend cpu efficiency. I don't know how it's even possible on iPad, elven magic no more, no less.
One thing I didn't understand is the logic behind adding new colors. Looks like my mind is hardwired to the grid so I'm trying to make a few identical rows of circles and colors in the mixer - from red kicks and orange claps to blue synths and purple bases. But as I see new colors are added randomly and I'm unable to move channels in the mixer.
Annoyingly I’ve found another problem with my new-ish iRig HD2, in that it disables the internal microphone (as well as the speakers) when it is plugged in. I much prefer how my old Apogee Jam worked, allowing you to monitor guitar through the speakers while playing.
Anyway, I believe this is down to iOS seeing it as an audio interface and therefore disables the internal mic and speakers completely, so depending on how you connect your headphones this might be good to be aware of.
Making unused AU apps ‘idle’ is the secret sauce for the CPU greatness, I think.
Adding new loops goes by the last colour, so if you want different ones, swipe up on a loop and choose a new colour, and then subsequent ones will add in that colour. (EDIT: Or you can select the pencil tool and then the colour selector icon in the middle - I think this is the quickest way to change colours. Just add a bunch of loops and then go colour diving). Hmmm, I’ll suggest to Michael that holding on the loop add button could reveal a colour selector, and also ask him about adding an ‘add loop’ button to the colours screen to speed up workflow there. Options!
Yepp! That is an iOS issue...
If the iRig HD2 only had an input you would be able to monitor thru the iPad but since it also has an output it's a no-ca-do.
For example if I connect my classic iRig Mic HD I can monitor thru the iPad speaker or Headphone jack...
Hopefully iOS16/iPadOS16 will add support for using multiple audio-interfaces at the same time but that's a long-shot...
Arro... I mean Self-confidence - Reality 1:1. The match is becoming more interesting.
(Snark aside, Saturn loads smoothly for me as well.)