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
Thanks. I hadn't even considered this. Sounds kinda obvious - just automate the Wobulator controls. I'll have a play....
I’ve been dawless for too long - forgot you can just click automation and pick a parameter 😂
Bugger. Wasn't able to automate the Wobulator controls. Filter cutoff etc etc was fine (although I still find Cubasis automation a P.I.T.A!)
Back to square one. Anybody else gonna use this in a traditional, finished song DAW type way with different sections on the timeline having different wobbles?
Just going to bump this thread in case anyone in a different time zone can help.
Are you able to automate program change? Seems a bit heavy handed but should work?
This is one of my greatest annoyances with software / iOS. Music software with a reasonable amount of parameters should have pre-designated CCs. Without pre-assigned CC’s it’s extremely problematic to share (and create) controller templates.
The old Arturia iSEM is a great example of how to do this right. When you click the midi-learn icon, the pre-assigned CC number of each parameter is displayed, and by pressing a parameter you can reassign it. This allows you to download a controller template and be assured that it will work immediately. And it gives you the flexibility to customize the CCs based on your needs.
If I wanted to share a controller template on [beatstep pro, lemur, sensel morph, drambo, etc] that I made for FRMS or Mela, it seems like that wouldn’t be easy to set up for the end user.
If I’m being frank, mapping exposed parameters in Aum is a PITA also.
Last sentence - too true.
@Gavinski Yep, I forget how many precise taps it takes, and then finding the right track module, then the parameter list, then oops, if you press a key or anywhere outside the menu you’ve gotta start again. I love AUM, but the midi control section could use a major UX overhaul.
Yes I'm sure that will work. This is what i ended up having to do with PureAcid. It was a royal pain in the arse. Getting Cubasis to send a +1 program change was like threading a needle with gloves on.
Rant time: to me this is real problem with AUs in iOS land. I'm a "finished song" in DAW kinda guy.
I want my drum machine and sequencer AUs to dump their info on the timeline. I then expect to go back into the AU in question, make changes and then dump this to the piano roll too.
Thank god for Drum Computer as it does this flawlessly.
As a workaround you could always just duplicate the track and change the settings in each instance to suit each section. When only one track is playing at a time the CPU shouldn't take too much of a hit (and you an bounce them all to the same audio track once you've finalised it anyway).
Hey thanks that's not a bad idea. I never really understood CPU usage and how it is affected by multiple instances.
I'll give this a try, cheers.
Great news here.
I have 3 Agonizer codes to give away - check out my Robots & Vampires video to enter. Robots & Vampires was made entirely with sounds from Agonizer synth in Cubasis 3. The only additional apps used were reverbs. Link in 1st comment.
Has anyone been able to fully turn off the portamento in Agonizer?
Even at 0 setting there's always some portamento present which is very noticeable when jumping one octave up/down.
(Just downloaded the latest update and it's still there and I do consider this as a bug).
Also both the 'preset' and 'settings' windows end up behind the keyboard when using it in perform mode.
I'm on an iPad Air 2, iPadOS14.2
Here's a quick vid showcasing the issues mentioned above...
https://www.dropbox.com/s/w4tzs4mfwsutbk4/Agony.mp4?dl=0
@jakoB_haQ This might be something to look at and hopefully fix at some point?
(If you agree they are bugs and will be fixed I'll remove the link).
Cheers and keep up the good work, left a 5-star thingie to keep the motivation up instead of doing like some others do and give 1-star when bugs pop up
/Samuel
All of this is so true I feel like going into a year long coma just reading about it. And the talk of the town among developers is that midi mapping is the job of the host. I don't know how anyone can look at AUM and think "yeah, I'll let that program handle one of the most important and intimate aspects of my synth". So exhausting. It's 2020, can developers get with the MIDI program already??!! As bad as it is though, it's still better midi implementation than Ableton.... a situation so exhausting I might just put myself in a decade long medical induced coma.
Agonizer is pretty great though if you consider that basically no one gets it right. I love the broken glass on the UI and the glitch display.
The true midi heroes of 2020 are SonalSystem's Continua presets. Seemingly the only artists to give a shit about the macro section with their presets (ie the main part of the synth that makes it great). It's such a let down every time I open a new synth and ask have to myself 'is after touch broken on my keyboard, or is this synth just a lazy bones?'
I can't tell you how many hours I've wasted in various synths because they don't have a 'global cc settings' option so my pitch bend ranges don't change every time I switch presets
If I already have Cyclop, do I still need Agonizer?
Yes
I have both. I'm not the greatest sound designer so your results might vary but I haven't found a sound Agonizer makes that Cyclop can't. Agonizer for me feels more streamlined. If you want to make a quick dirty bass Agonizer will get you there. Cyclop is deep. Its filter section dwarfs Agonizer's and it has a greater variety of effects that can be step sequenced. If you want to lose an afternoon sculpting the perfect sound, Cyclop has you covered. As far as Wobble knob versus Wobulator I thought that the Wobulator would be an easier hands off approach, but in practice I find Cyclop's Wobble knob with an lfo assigned to it gets me what I want. As far as user interface goes, Agonizer is far more approachable. Less is more definitely applies here for me. And when you're using an iPad mini like I am, Cyclop's tiny controls can be frustrating without a stylus. So all that said, if you are happy with Cyclop's interface and sounds you probably don't need Agonizer. But if you feel like Cyclop is overwhelming , Agonizer is a good choice for bass sounds . I also like to support people like Jakob who have shared so much with the IOS music community so I don't mind having multiple choices on bass synths.
Havent really tested but now looking for other wub style bass. Not sure if I like the sound of cyclop. Im sure you can program synths etc. Shockwave for example. The envelopes etc lol but not sure how Id also shape sound within that etc.
Think Agonizer would be better if the wobulater parameters could be exposed.
You see oscilater A and b?
The arrow thing to switch shape can be mapped in Drambo.
But the wobulater cant. It would need shape, rate and maybe repeats which share the same arrow to be seperated ( the arrow be able to have a mapped knob appear in drambo for each of the shape, rate and repeats )
Not sure how it might be with higher rates than 1/16th also.
Seems like a missed oppurtunity to get most out of wobulater.
Automated and step recorded variation.
Unless can be programmed the same not using wobulaters and on any synth. Wiyh lfos, envelopes etc ( but not sure about that )