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
Very cool @brambos!
To be fair as I stated earlier, it's really no more cpu hungry than most AUs out there in my admittedly rough tests
I'm constantly amazed at how much mobile gadgets (or computing devices in general) can pull off these days. There's so much going on in (near) realtime. You can just keep throwing things at it and it's still casually picking its nostrils.
Now let me tell you about my Z80 days yada yada </old fart mode>
@brambos and with this I finally have enough to make an entire track only using your apps. Which is something I intend to do post haste
Well now you have finished that Mr @brambos can you knock up a quick sf2 player AU by tea time?
I have an issue, not sure if it is Phasemaker or Auria Pro.
I have Phasemaker loaded onto a track in Auria Pro, the initial output from Phasemaker is really high, so I drop the gain from the program screen, all is fine again.
If I close and re-open the project the gain is back where it was initially ? Am I doing something wrong or is something (either Auria or Phasemaker) not working correctly ? Should I be saving the preset after adjusting gain for it to remember the change ?
Hmmmm... strange. Gain is just another AU parameter, so if one works, they should all work. And if Gain works in one host, it should function the same in all hosts. So I'm inclined to think it's something on Auria's end (where maybe it didn't save the state correctly after you changed the Gain).
Edit: just tried in Auria and Gain changes are working here across sessions. Which leads me to believe that you probably ran into a situation where Auria did not save the state correctly.
Ok thanks Bram for checking this out for me...I am having other issues with Auria as well with crashes happening randomly, maybe the two are related.
I will be doing more 'work' (it's hard to call it work when I enjoy it so much LOL) on my tune this evening, One thing I will test is whether the gain saves between normal exit of project and if there is any difference when restarting Auria after a crash.
To be honest i was enjoying Phasemaker so much, I just adjusted the gain each time and carried on
OK, I tested changing the gain, exiting Auria, starting auria again and can confirm that the gain is indeed saved, I am now going to wait for Auria to crash again, and see what happens to the gain setting after that,
I now suspect it is something occuring when Auria is in crash recovery/reload that is resetting the gain back to the original preset setting.
EDIT: I also have Ruismaker loaded in the same project, and my level adjustment in that is behaving fine. If it were just Auria causing an issue I would expect all the loaded AU's to behave the same ? Perhaps it is Phasemaker that finally pushed my iPad over the limit and causing the crash in the first place, not because of any fault with it, just that I am pushing the CPU and RAM usage. And I only say this because it is Phasemaker whose setting are being reset. Just thinking aloud
CPU in Auria Meter is at 42% and I also have gadget loaded and using it as a sound source (Not sure if Auria CPU meter only shows Auria usage or total system usage).
I agree, the stand alone is waay cool. I actually wasn't expecting it when I opened the app. I didn't k now it was stand alone. That was exciting.
Great app! I wish it had foot controlled sustain {cc 64} It would be nice if it had on/ off so different instances had an option to hold notes. Using multiple instances is like performance mode on the old TX81X.
Love this idea. Very V.A.S.T./K2000.
Not at all 'needed' but it would be a fun way to make these pads even MOAR BIGGER.
Though I think I would be slightly more interested in a more randomized version where each key-down event puts the note into a random place in the stereo field, perhaps with a single "spread" knob to set a constraint. And/or a clever combination where low notes are constrained around the center of the stereo field and upper notes can move further out at random.
@brambos You're on KVR, bro. Check out the right side-bar (on desktop/laptop).
http://www.kvraudio.com/forum
Someone revived my account? That used to be my mothership a decade ago. Cool beans!
This is one of those cases where I'm actually not sure whether pedals should be handled by the plugin or the host? I know that Cubasis always throws a bunch of CC64 commands my way (hence this command is never used for anything else in my midi implementations) but if other hosts don't support it correctly the plugin will be stuck-note central...
I'll need to investigate.
I'd be more in favor of a simple automatable pan setting for each carrier. IMO all that stuff should be handled through cc automation like anything else.
Just discovered this, instabuy and it's worth every penny. Love it.
Big fun. Thx Bram. Its a good life.
I should have put "pretty well" in quotes. It's usually something like starting with a sound I like the basic shape of and then going batshit on a few of the operators and then changing the algorithm until something good happens. From there, it's either purposeful edit or more focused randomization. Hit and miss, for sure, but it's a lot more fun that programming the thing directly!
OK ignore all of the above
The problem is not a problem, it is because the bram stuff is so good that it shows up other stuff going on.
The change in volume was because of, wait for it, a volume change midi message that was right at the start of the track, and not removed by using the delete controller function in Auria. The midi part was imported, so I don't think Auria put the message in there.
I had to delete the part and replace it with one from later in the track that didn't have the volume message in it.
The reason this didn't happen with other au's is because they don't all respond to cc messages.
The reason I thought something else was going on is that I was using loop mode in the middle of the song making adjustments, which was working fine, then when I was going back to the start to listen to the entire track, the volume message was then played. I hadn't made the connection with the 2 things. Apologies for any work or confusion I caused
@brambos I haven't bought this yet, but I like that it's standalone. What are the chances your other 2 ruismaker apps could be updated to be standalone too? Or, would that cause problems since they're universal for the iphone?
I don' think she likes auria - or auria doesn't like au's.
Had a whole lot of hasle on ipad pro running 5 psms + 1 poison - on ipad pro.
Ran out of power. Fired up the old air 1 and could run almost the same setup
within Modstep - without panning - and the psp strip.
Modstep likes her.
Bram please talk to Rim from Wavelabs about getting your stuff into auria as
plugins - it would be the coolest addon they could have.
Back to 33
Strange. Just did a stress test with iSem on my 9.7" Pro inside Auria, and was able to play with a lot of instances without crashing it. I don't have Phasemaker yet, but @Fruitbat1919 does, and he also did his own stress test on an Air 2, getting good results.
It seems the baseline CPU consumption of Auria (i.e. the load on the CPU before you even start opening AUs) is a bit higher than other DAWs. Therefore the same setup in e.g. Modstep likely runs a bit smoother than in Auria.
That is an interesting thought :-)
If I'm not wrong, Auria Plug-ins are VST. Is there any advantage of VSTs over AU-x, at least from a developer's perspective? Because if not, it would be preposterous IMO.
There is no advantage of doing VST over AUv3. So if there is no special extra-tight integration with Auria then AU is the way to go I guess.
On another note: I wish people would first send me an email before leaving a 1-star review on the AppStore... At least then I'd learn something from the feedback (or help fix whatever their issue was)... sigh
Review trolls, they're everywhere. Going to post a five-star in the Brazilian store. But... You forgot the drum presets, so I'm having to programme my own. You are forgiven!
P.S.: Done. In Brazil, Phasemaker is five-star!
Cheers! Appreciated!
Anyone who could leave a 1-star review for any of your apps is clueless!