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
Is there a YT tutorial that covers all the features of Pure Acid?
Thanks! Even more excited now.
Doug and Jakob both have videos about it but I haven’t watched them yet. Well I watched Jakobs like 3-4 years ago.
I don’t think that the two following drummachine tricks are in the youtube tutorials..
1: Enter your steps on the drummachine. Hold down a step and turn the data knob to set step conditions or probabillity.
2: When step programming, hold down the step button. Now you can enter 32th notes.
Thanks! Great if ppl can add anything else that's missing. Or do you think the rest is covered in Jake and Doug's vids?
I don’t know. The 32th note trick was posted on this thread by the man Jim Pavloff himself. I don’t remember how i picked up the other one. Maybe i read it in a release note or something….
I’ll see if i have some tips somewhere. I’m a HUGE fan of this app so I like to take notes 😉
Here are the Midi CCs if anybody need them. Got them somewhere of the internet, maybe even this awesome forum :-)
Pure Acid MIDI CC:
7 = Master Vol
8 = Bass Vol
9 = Drum Vol
12 = Env Mod
16 = Accent
17 = Distortion
18 = Drive Bass
19 = Drive Drums
91 = Bass Send FX A (?)
92 = Bass Send FX B
93 = Drums Send FX A
94 = Drums Send FX B
71 = Resonance
74 = Cutoff
75 = Decay
76 = LFO Rate
77 = LFO Depth
85 = FX A Param 1
86 = FX A Param 2
87 = FX A Param 3
88 = FX B Param 1
89 = FX B Param 2
90 = FX B Param 3
102 = MFX X
103 = MFX Y
106 = MFX ON/OFF
104 = Pitch
Maybe some people could take a few minutes and adc tips and tricks to the wiki article where they’d be easily yo find:
https://wiki.audiob.us/doku.php?id=pure_acid&s[]=pure&s[]=acid
I see that the condition tip has been added to the wiki. Thanks 😊
I also found this one in my notes but i can’t get it to work from this explanation. It was originally posted by @jolico. If someone can get it to work i would love it if you let me know 😊
“At the moment I am copying to another pattern, hold shift and up/down arrow to transpose the copy.
This way you can live transpose to greater levels without stepping through each semitone. “
But this one is handy.
You can silently select a drum ( without sounding it ). To do so, hold down either “Trigger”
or any drum select button, andt then tap the desired drum pad.
Edit
I can’t update the wiki. It is read only.
I can’t believe I didn’t think of using program change for the patterns lol
This might be referring to these arrows. They will transpose an entire pattern. The shift isn’t needed, I think you only see that on the sequencer page.
This would really make him THE MAN - should anyone have to go fishing through a forum to learn how to use an app? 🤔
|
Should anyone earn less from writing a sophisticated great,sounding audio tool and earn less than minimum wage?
Having manuals would be lovely -- but the over the top rhetoric that doesn't recognize why it isn't really feasible seems to ignore certain realities.
This plugin sold well! Very very well, judging by the length of the thread. And a release that has a manual that teaches people how to use it to its full extent will likely sell even better, via people being able to use it to its full, and youtubers being able to make informed and informative videos on it that will in turn encourage users to use it to its full, and buy future releases from said dev. This whole 'devs don't earn enough to make manuals' spiel that you often trot out is very tedious to my ears at this point Ed. You're entitled to say your piece, as I am, but we'll have to agree to disagree on it.
Jep got it. But i think that the idear is that that you can transpose a copied pattern “silentley” without stepping through the semitones. But maybe om wrong 😊
Or ... maybe his country is at war and he has just a few other things to worry about.
Now yes... But not then. Of course, I heavily sympathise with the current state of things in Ukraine
I'll start by saying I wish that all apps had comprehensive manuals. I'll also say, who knows the app better than the designer to be able to do so? If I was capable of releasing an app, there is no way I would release it without a comprehensive manual. But I think we're all guilty of framing this from our own self-interested perspective.
Just as being an excellent musician doesn't mean that person is disposed to or has the temperament to teach others, being a coder doesn't mean that a person is skilled or motivated to write a manual. It isn't an easy skill and it's really time consuming. Coders can be totally into writing programs but hate trying to write documentation. I can imagine that having most manuals expected to be in English when that may not be the developers' first language adds to the difficulty, time, and intimidation factor.
Add to that the fact that writing a comprehensive manual is basically time spent working for free - and maybe on a task one feels terrible at or doesn't enjoy at all. Some will argue that it helps sell more product. That may be true but I doubt the payback is enough to justify the cost if you figured it on an hourly basis. Considering most iOS music app developers are basically doing it in their free time I can understand why some aren't motivated. Which of us would prefer to spend our precious free time cleaning the house vs. spending a day at the beach?
It's real easy for us, who have time to piss away for hours each day on a music forum debating the even nook and cranny of the app subscription model, or speculating about Logic Pro features for weeks before the app even comes out, to think "Why didn't the guy just write a manual?"
Sorry. But this pisses me off. If the developer doesn't want to, or doesn't feel good at, or doesn't have the time to write a manual, that's their business. We drop the price of a Big Mac or maybe a decent lunch on something that took someone literally hundreds or thousands of hours to create and feel like we're in a position to complain that they didn't donate even more of their time? Argh.
How about this? Since we all have so much time on our hands that we have the luxury to hang out here, why don't we each pick an app and write a manual for it ourselves? Shit. We can't even get many people to take a few minutes to contribute to the wiki!
Sorry. I just had to get that off my chest. Rant over.
(And yes, this rant is as much or more directed at myself as anyone.)
I can definitely dig a rant with a bit of humour thrown in, and you make some good points Wim, as you always do, and in a very gracious way.
I'll add though that as creatives we all have to do stuff we don't enjoy if we want to get our stuff out there. I certainly don't enjoy all the admin that goes with my channel like adding detailed text reviews, timestamps, cards and endscreens for YouTube, posting to a myriad of Facebook groups, giveaway admin etc. But I know my vids won't maybe perform as well if I don't.
At the end of the day, each to their own, but I always feel that at least a tip sheet with the main non-obvioua points wouldn't be that hard for any dev to make! If it is, they probably always have a few hardcore beta tester fans who would happily help with this kind of cheat sheet of the main tricky points.
That's very good point. It does puzzle me that someone would take the tremendous time and care it takes to build features they're proud of and not be driven to at least briefly present them.
@tja - I'm not going to get into a debate about Ukraine with you. Not here. Not anywhere.
I have edited my post to remove the content you find objectionable. Perhaps you could do the same to avoid further distraction.
"Sold well! Very very well...." But you have 0 knowledge about how much money was earned, how much time went into the development or what expenses the developer has. Some very popular apps generate relatively little money compared to the time that went into the development.
Like I said, I'd love for it to have a manual -- I just hate the judgey attitude expressed about the lack of the manual and the lack of acknowledgment/awareness of the factors that figure into a developer's decision.
It's one thing to say "I wish this had a manual." It's another to act like a developer is being a jerk or remiss for not having written one. They earn far less than you seem to think. I just think people can back off on the attitude.
Sure I don’t have that knowledge, but I think my points in that last reply to Wim are still valid. No need for a huge, fancy manual, if the dev is not capable, for whatever reason, but even a rough manual is better than none, imo
Totally off topic but ...
If I was thinking about writing a user contributed manual for some app but wanted to have it open enough that it could be contributed to by someone else, or perhaps be passed along to someone else altogether would Google Docs be a good choice? The publicly published format would be PDF, not HTML or the doc itself.
Wiki's don't really do it for me as the mechanics of uploading and positioning graphics on the page, etc. are too clunky. I prefer something with better compositional tools but that is still accessible and shareable in a controlled fashion to others.
As I said, I wish they had manuals -- I just am not going to be judgmental about the lack of manuals and shame devs that don't have them.