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.
Agonizer agonies -- is it just me?
I fired up Agonizer yesterday and again today, and was able to produce nothing other than a rumbling buzz with a fast and muddy staccato flavor. This happened while hosted in both ApeMatrix and AUM. Is anyone else using this app and experiencing this lately? Haven't tried reinstalling it yet, on the theory it might have been corrupted, but I'm wondering if its buggy recently for anyone else. I have a 4th generation iPad pro, running iPadOS 16.1.1. Thanks.
Comments
Did you try to use it as a stand alone ?
Definitely reinstall it and if that don’t fix reach out to dev…last update was 8 months ago
Seems ok on ipad for me… are you just running init patch?
Seems ok for me as a stand-alone
All OK here, AUv3 & stand-alone, iPadOS 16.4.1 (a), iPad Pro 2 Gen 12.9”. Note the iPadOS security update was made yesterday and I see you’re on a much older version.
I’ve had issues in some hosts, not all, Its usually when a set up has a lot of moving parts, in an AUM scene for example. I assumed this was due to dsp issues.
i chalk this up to the usual iOS experience, some stuff doesnt work with othet stuff. I tend to skip the set ups that combine what I have found to be uncombinables…
I use synths, fx, and hosts that i find (currently) stable (or at least the most stable among what I like best). eg. IceGear stuff, Multitrackstudio, some of the self contained things like Gadget, FLSM (which can be quite stable with outside IAA apps, but not all…
my usual general comments i’ve shared a few times, on threads like this.
specifically i will play with agonizer again and report back
No agony here in testing.
I have been having an issue in Cubasis 3 with Agonizer.
I am using one drum track and one Agonizer track.
I have a simple 3 note sequence and Agonizer will skip the note changes
It plays the first note an F but will not A# or A when played back form the sequence in the next measure it plays the F again?
When I wrote this simple piece it worked fine then after I closed Cubasis 3 and then opened it again Agonizer did recall my preset so I have to go into Agonizer select my preset.
Then Agonizer would follow the sequence.
It does this every time
Yeah Agonizer never worked well for me, I only ever host in Cubasis so can't comment on AUM or wherever. The same with the Dev's PD monosynth (name?). State saving issues and other anomalies I think. I gave up with both apps and avoided buying Volt just in case. Shame.
Last update was made 8 months ago , minor bug fixes and new IAP. If I remenber it was created in collaboration with @jakoB_haQ ? I think he should help you at least to report bugs to the dev.
I bought it seeing demonstrations from Jakob on his YT , not pricey but not cheap, I was thinking to use it from Deep house but not yet have create something with it.
Shockwave is the name
I saw the reviews for that and Volt but was planning to get Agonizer anyway because of the esteem I hold Jakob Haq in . Have any of you all contacted the developer Kai about these issues, and if so what was there a response of any sort?
In fairness the dev did ask me to provide more info (in a previous thread on this forum) and I was too lazy - by this stage I think I'd already uninstalled Agonizer.
I use now Cyclop for wub bass.
If you search this forum there's plenty of folks having issues: https://forum.audiob.us/discussion/47600/agonizer-hanging-on-ipad-air-3-ipados-15-0-2
TH> @BerlinFx said:
I did after you brought up that up, and it works without a hitch. Then I discovered that it also works in Audiobus, which doesn't officially support it, so launches it as an app. (Dear Audiobus: I think the possibility you suggest, that perhaps this program hasn't been updated yet to communicate with your esteemed produuct, makes and assumption that is overly optimistic on your part. BTW, I enjoy the forum. And also like Audiobus itself, and use it more than I did a few years ago. It often seems to be able to launch items that others struggle with.)
(Agonizer still acts funky, though, launched as IAA in apematrix and Aum. (And not Brothers Johnson guitar funky. More like Boris Johnson's tennis socks funky.)
You know, It really is a cool looking app in retro-styles app full screen. The AUX is designed to look like a battered plastic faceplate and the wobulater windows have simulated cracks in them, which almost made me soil myself because.. I drop things that belong to me. And I have a 12.9 inch iPad, and a screen that I assume would be considerable more fragile than smaller models.)
thanks everyone's thoughts, it does appear that the AU instantiation is uniquely associated with the malfunction.
Happy That you now you can enjoy it.
That sucks for me, cause I only use AU . IAA is not workable for me since I don’t have an external controller and the few times I tried an IAA in GarageBand I end up missing my cue to begin playing . Going from an AU to an IAA app is like going from 8k to VHS . I wanted to get this but if it doesn’t work as an AU there’s no point for me
I'll reinstall it and see if it's just unique to my setup/system. Probably later today or night I can update. I haven't previously had issuuez with it.
Thanks!
Ok cool…just please keep me posted !
At your service.
I’m disappointed to encounter the same problem after reinstall. It spits out a blur of grindcore riffs. I suppose I’ll contact the dev. I went back thru forum history to see of similar complaints, and I did notice a handful of complaints of midi issues.
Oh well. I’ve rarely used it since buying it at release (for Haq!) so the bright side is I won’t miss like I would some other apps. But I also didn’t get my money’s worth. And so far it still seems good in Audiobus, so — first world problem i guess.
Damn that sucks….hopefully contacting the developer will help
fingers crossed
Update on the Agonizer issue: I learned by posting on another thread that a synth I just purchased and which was crashing was reacting to the host's large buffer setting. Changing that appears to have solved the issue at least for now. Since I recently channged my buffer settings to eliminate crackling, I tested to see if Agonizer was working again correctly: indeed it is.
Smaller buffer, and so far no problems with either app, just so you know. I'm optimistic this will continue to work, even I lose the benefits of a large buffer allowance. Good luck whatever you do!
FWIW, going over 1024 samples rarely pays off...
The latency becomes unbearable, many sequencers become erratic (jitter) and at that point there’s hardly any cpu gains.
Agonizer loading dead for me in AUM. Have emailed the dev. Anyone else getting this? IF so you may also want to contact the dev so he knows the extent of the issue, cheers
That's what it looks like when I'm trying to load an expired beta version of an app. Is that perhaps what's going on (just a shot in the dark)?
Ah - good call, looks like that was indeed the problem, thanks Bram
Agony aunts, please help. I find that in AUM and Loopy I am unable to see my wobulator if I have the keyboard in use and the app doesn’t scroll. Also, if I feed notes in from another app, such as helium, the wobulator doesn’t react and it sits kinda idle when it is set to BPM. I want to like it cos of Jakob but it isn’t playing how I hoped. Any tips would be appreciated. Ta.
You mean the built in keyboard in Agonizer? I’ve got no problems there though I noticed it doesn’t seem to scale properly anymore. You have to expand it to take up most of the screen real estate to see everything which is a massive bummer.
I had this problem. Turning down AUM's sample rate fixed it for me.