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.
A tip for devs…
I’ve been buying music apps for iPad since there were iPads. I’ve got hundreds of apps now, literally. They are not all on my current 1TB iPad Pro. And Apple’s search algorithm for apps sucks, of course. So I’ve just spent about 45 minutes running through my purchases by year to track down one app I wanted to use, whose features I could recall, but whose name escaped me.
I knew it was a reverb. It turned out it was Velvet Machine.
Great app.
But, you know what, devs? If you are making a reverb, give it a cool name, fine, but maybe also include a clue to what it is or does? Like if it is a reverb, maybe put ‘reverb’ in its name? Sure makes finding it again easier. (Quickly found all my reverbs that had ‘reverb’ in their name.) Ditto anything ‘MIDI’, ‘Delay’, ‘Distortion’ etc…
Comments
Well for this you have Aube...
Sure, AUBE is alright but I agree with S, apps should be better tagged. The app store search engine must be one of the worst ever and I can only think that for some reason they (🍎) want it to behave like that.
Yes, the App Store search engine won’t even return something as the first result if you type its name exactly. I have lost count of the number of times I have had to scroll down pages of results that aren’t even remotely similar to the term I searched for.
I keep forgetting to use AUBE. Should.
I concur with @Svetlovska’s comment, though. It gets pretty weedy. I hate trying to figure out which Korg Gadget I’m looking for, for example.
iPads come in terabytes? Damn.
Yup, and only the 1 or 2 TB options have 16GB of RAM.
I got the 12.9” M1 with 1TB. I have pretty much every app I’ve ever purchased installed, and I’m just over half full.
Devs can name their apps whatever they want. Velvet Machine is a great and memorable name, and an awesome reverb. This is more an issue of having too many apps which we all have here, and Apple's own limitations with searching and characterizing.
Of course they can, and they have my money, so they don’t care, I guess. But, if they want any app enthusiast to find and use their apps again a year or two down the line, well… it’s a suggestion, not a commandment.
No suggestion, no matter how humble or gentle, will not merit a sharp retort.
imo any "app enthusiast" already has AUBE installed and doesn't have this problem
Whelp, @Goldiblockz, I think it’s hard to deny I am an ‘app enthusiast’, (343 on this iPad, more on the big one, 110 current tracks on SoundCloud using them back me up, and several hundred before those, removed when I took a hiatus from SoundCloud, I have a rule which says if I buy an app I have to use it in a track immediately).
I have Aube, but honestly don’t use it, (mainly because I have so many apps that Aube, great idea though it undoubtedly is, doesn’t find, and I can’t be arsed to add them all manually) so… tl:dr: I guess you are wrong.
IMO.
Sounds like the enthusiast needs an enthusiast organization that is all their own. I don't think this is on the devs
I don't want every app to have their category added to the name, that's ugly
Maybe when you make a track with the new plugin, keep a note on the side containing all the plugins used / added to your repository when you upload it?
@Svetlovska
Try https://synthyfrog.com/
iOS apps organised by " updated: released: App name: Author name: Rating: Price dropped: Price "
This is a good point.
The best way is to keep the original files which would normally have all of the effects/instruments saved with it.
This is something that I had done for many years when
I worked as a producer/engineer so that when a client asked for a recording of the track
I could recall it almost instantly or with the minimum amount of fuss.
Great feedback. And I agree @Svetlovska
Keep it simple, and straight to the point.
I personally hate reading manuals, or having to circle around the mountain to get a simple answer. Life is too short to read stuff. I'd rather figure stuff out.
I'm of the design philosophy that the design needs to explain what it does, simply by looking at it.
Simple. Clean. Elegant.
Personally, I just render my projects to audio stems. I can’t be bothered to edit MIDI 5 years down the line. My plugins will undoubtedly break.
Sadly, it’s the one thing GarageBand is GarageBAD at.
Audio stems are a good idea.
You never know if and/or when something will break.
Fair enough.
Then let's remove all the manuals from the apps and why don't you have a conversation
with the dev's about simplifying their apps even more to suit your design ethos.
Which makes the difference between an amateur and a professional.
If you can't be bothered then why should someone be bothered to create something that will assist you.
Learn the basics, read the manuals, remember what you do and if you can't remember
make notes in a way that works for you, no one is going to be holding your hand forever.
Ohhh and I do agree that the search engine for music apps on the AppStore is not the greatest.
What works for some, will not work for others.
I never said we should remove manuals. I said “I personally hate reading manuals…”. I’ve always been an anti-manual person. But it doesn’t mean I don’t write manuals.
Why do I personally hate manuals? Because they become outdated quickly. Once an update launches, engineers and developers add new features, and we have to update it. We add a patch, we have to add it to the manual. That’s time taken from development, and we have to re-read the entire thing so it makes sense.
Manuals are a necessary evil…I just wish there was a better way to solve that problem.
Here’s the full quote…
“ Personally, I just render my projects to audio stems. I can’t be bothered to edit MIDI 5 years down the line. My plugins will undoubtedly break.”
My plugins have been updated so many times, and they no longer work. I need to print them in audio so that they maintain their integrity.
Everyone has their own way of doing things…
I’ve learned from Timbaland, Ken Lewis, and many more producers, and mixing engineers in the business on how they do their workflow.
Yes, experience is essential. But sometimes hearing the challenges, and how they solve it offers a different way of solving the problem.
Apologies for the late response. Just came from a gig with Bethel Music.
Agreed.
Hate is to strong a word.
Always bear in mind that what you hate will come across when you do similar for someone else.
If one hates reading a book then expect someone to hate reading your book.
That is part and parcel of writing apps that continue to grow.
Though you may not see the connection manuals need to be there because of
"What works for some, will not work for others."
and writing manuals is part of the development.
There is no way around the manuals except video tutorials and video tutorials cannot cover an app in depth
unless you've got a full blown series of video tutorials explaining every detail and judging from the
responses from my thread and a couple of other threads, some viewers would like the tutorials even shorter.
At some point you're going to have to read the manual.
At some point you're going to have to think for yourself.
Wow. Snark, snark, and snark again. So community. Such accommodating.
I’ll be honest, I’d rather someone tell me they hate my book and tell me the reason why, as opposed to being lukewarm or not sharing their opinion.
Why I have huge respect for @Gsus and @sigma79 is because when they shared their opinion and griveances, it was valid feedback about one of the ways I’m perceived. It’s not very often you get the chance to ask how your work is perceived.
My design ethos is my design ethos. Every app developer has their design ethos. When I make my app, I’ll design it based on my ethos.
There are many ways to solve an app run through of information without a chunk of text. It’s important for a designer to remember that other languages exist. Some things need to be explained visually. A switch is a switch. A knob, is a knob.
I’m just using this thread to gain other ideas on how to make an interactive application, without necessarily reading manuals. Yes, I will write a manual, but it cannot be the only way.
A huge chunk of the world cannot read English. Or have accessibility requirements. I, myself, am colour-blind. Part of the reason I’m wearing glasses a LOT more.
@seonnthaproducer
I focused on "I can't be bothered" because that is what is coming across, apologies for not including the full quote.
That's why pro's keep everything.
I've just been asked for the stems for a track I produced and engineer 26 years ago.
All I have to do is look at my hard drive when I get the chance.
All good. I did say we don’t always agree on our philosophies. Which is perfectly fine. What works for one, will not work for the other.
Very true.
No argument there.
Honestly, it’s a weird place but there’s a lot of humour within the snark. And it is less snarky than reality.
Literally had a event manager acting like a bigshot, preventing me from doing my job. Chatting with forum members taught me how to stand my ground to music types.
And I’ll say this about my teaching style…I’m trying to prepare people for Today’s Reality, not Tomorrow’s Fantasy. Because, no one is promised tomorrow.
Agreed.
For sure.
I'm guilty of that.
I see the ‘Off Topic Twins’ are attempting to make another thread all about them! What the hell has any of this got to do with the OP’s original point?!
We're having an argument.
I think that's clear to see.
My apologies @Svetlovska for hijacking your thread.