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
I'm not sure actually. The plugin doesn't currently have direct support for MIDI input. The way to control it from outside is through AU3 parameter change requests from the host app. Those are not limited or rounded.
Are you wondering about a configuration where the plugin itself accepts MIDI input? or is it something where the MIDI goes to the host app and the host translates it into AU3 parameter change messages?
When the plugin receives a parameter change message, either from the host app or from its own built-in UI, it moves smoothly to the new setting over the space of a few milliseconds. If you were doing a filter sweep on something that has only 128 values available, hopefully that smoothing would help a little bit.
I haven't heard other reports. But most people don't report bugs. So it's entirely possible that you are not the only one.
Have you noticed anything predictable enough to tell us how to replicate these bugs on our own iPad or iPhone?
Ah man, don’t really need this, but the waveform visualizer makes a huge difference for me.
Bought, waiting for update.
After a quick test I already like it more than ZMors. Funny how a cleaner sleek UI makes such a difference.
Also all the AU parameters are exposed in AUM so this will be very easy to set up with my MIDI controller.
Technical question:
The AU parameters for filter frequencies are specified on the range between 20 Hz and 20 KHz, with linear scale, because there apparently isn't any AU parameter for logarithmic scale.
This seems bad to me, because if you wanted to do a filter sweep via MIDI or by drawing automation values into a DAW, you would get a linear frequency sweep, which would sound terrible. To solve that, I have put in a work ticket to have the AU3 filter frequency controls work on a scale of [0,1], with 0 meaning 20 Hz and 1 meaning 20Khz, but moving between them on a logarithmic scale.
Is that the right thing to do?
We’re just a bunch of dumb musicians.
You should try the developer forum. That’s where the real geniuses hang out.
@CracklePot right. Sorry about that. I'm afraid that even though my question looks like gibberish to some readers in this forum, they might actually have a strong opinion when it comes into action. I think I will just go ahead and put the frequency controls between 0 and 1.
In case you need the cheat codes, these guys already beat all the levels
😂 so funny
The update with the visualizer is out
Although it does not seem to match the graph. A 440Hz peak is showing at around 130Hz.
Yeah I just saw the update go up on the App Store. The graph isn’t aligned properly. I filed a bug report. Hopefully we can get it fixed by this weekend.
Please consider this version a preview of what the visualizer will look like when we get it aligned properly
So true.
The update has wiped out my presets!
It’s because of that change to log scale frequency. Hopefully that is the last time we update the exterior control interface.
Whoot! Automation works like a charm!
Woo7!
I’ve bought this for the lightweight visualiser. To support what was said before; as a beginner I don’t have the knowledge or experience to eq what to cut from where, especially across a complex track, so a visualiser is a massive help . Add to that the majority of tutorial vids I’ve seen use a visual guide while they’re going through eq demos and it’s a far faster reference point for me.
Short version: the low weight au visualiser could be a hidden gem for you guys = $$
Hope the update comes through soon, gonna be a great help, thx devs.
@EDB
Thanks for the input. We corrected the visualiser alignment problem yesterday. If the review process goes as quickly as it did the last few times, the update will be available in 1-2 days
Great @Blue_Mangoo looking forward to it, gonna helps lot
The visualiser is great fun.
Very useful EQ, Im going to use this on every track. What great value. Keep up the great work @Blue_Mangoo
Thank you for the update!!
we submitted the alignment fix update to the App Store review team. I hope to see it on the store soon
@Blue_Mangoo I just installed the updated version and found a problem with AU automation in AUM crashing the whole audio system.
1) On channel 1 use a AUM file player playing any loop
2) Add a Blue Mangoo EQ with default settings, raise bell 1 q to enable the bell 1 filter
3) Setup Blue Mangoo EQ to receive the bell 1 freq AU parameter on midi ch 1, CC13
4) On channel 2 add a Rosetta LFO
5) Press play - loop is playing through EQ, spectrum graph is visible in EQ
6) Now open the midi connection matrix by tapping midi route and connect Rosetta LFO to midi control
=> The audio system crashed
AUM will no longer produce any sound, even when loading a new session, removing it from memory and restarting it. I had to open up a standalone audio app and play some a sound, close the audio app and then reload AUM to get sound.
Sorry for ruining your weekend
I’m having similar issues as well. Just having it on a channel strip in BM3 causes the sound to not work at all. Once it’s bypassed, the sound comes back
@_ki thanks for making such a detailed bug report. I’ll put in a work order to get this fixed.
Thanks for reporting it. We will look into it.
I found another problem with the EQ in AUM - sound cuts out after about 1:30 of play.
No automation involved, just playing a synth through the EQ in AUM.
@Blue_Mangoo
I had this happen to me as well but I was not using any automated parameters. Audio just suddenly cut out no clipping or anything. Just totally dead and it was all audio not just that channel. I closed AUM and reopened and all was fine. I never sent a report as I didn’t think I had detailed enough information. One thing I do know is I was dramatically moving one of the EQs around manually as if it had automation. I tried to repeat it and could not.
@tja Thanks for the feedback, that the second problem i posted might need more investigation and does not happen to all EQ users.
Perhaps it depends on the ipad: 8 am on IOS 11.4, iPad Pro 10.5. Or on my Redshrike-Preset, which might be too hot in some frequencies in the output.
I will redo my test with just an AUM file-player and identical EQ settings tomorrow.