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
That would have been me, and yes I was really surprised but they brought out an update in September. Which includes ducking for voice overs and "improvements to the video plug in"
The ideal solution, in fact, would be the one used by logic and GarageBand: overlapping notes does nothing to any of the notes. No trimming, no deletion, nothing.
but then playback of the notes does not happen the same as they are displayed ?? Remember these overlaps are on the exact same note.
If you have an overlap then the midi messages would look something like
Note C2 On, Note C2 On, Note C2 Off, Note C2 Off.
The C2 note will start on the first Note On, and end on the first Note Off, with maybe a reitrigger of envelopes and stuff on the second note on depending on the MIDI Destination. You would hear nothing between the 2 note off messages, but on screen there would be a displayed note.
This is why Auria does what it currently does when an overlap occurs in Transpose, it means the displayed MIDI shows what will actually be played.
I think the second Note On command acts as a Note Off for the first note both in Logic Pro and in Garageband.
Auria 2.07 is under way! It will fix the MIDI panic bug. Should be released to Apple later this week. http://auriaapp.com/forum/viewtopic.php?f=20&t=14753
Does anyone else have issues loading DrumPerfect Pro as an IAA in Auria? I'm getting really high cpu spikes (up to 600%) on 128 buffer. It used to work fine before. Latest iOS. iPad Pro 12.9
I am just updating to 10.1 and going to test this soon afterwards.
Thanks
Just did the following: created 16 audio tracks, each one with a Drum Perfect Pro instrument as insert, and armed all of them. Then I created a MIDI track routed to channel 10/Drum Perfect Pro, and put a 12-bar blues drum loop in this track. The buffer was set to 128. During the recording, the Max CPU meter never got higher than 55%.
My iPad is the smaller Pro, 256GB, iOS 10.1.
P.S.: not that there wasn't any other issues: in fact, all the audio was record a 1/24 note (that is, a triplet semiquaver) late, at 120 BPM. Nothing too bad, but still not something that I could left as is, was it a real recording session. I assume it's an iOS issue, one of its many limitations left unsolved with iOS10, but only @WaveMachineLabs could tell us for sure.
Mmh. Looks like it's either my copy, or a 12.9 issue. Thanks for testing. Also, when I load it as an IAA (in Auria, as that's my main workflow), it quite often reverts to default. I need to reload all kits and patterns etc.
Is it Auria or Auria Pro? Though Rim said that both share the same exact code, so this should no be relevant at all, I tested in Auria Pro.
I tried it with both. Same issues. And Cubasis too. I could see the cpu jumping around. But not in AUM, although I wonder if it measures it differently.
Interesting.
Today I discovered something interesting concerning Auria Pro 2.06...
I have two instances of Auria Pro on my iPad Pro 12.9", one upgraded Auria (to Pro version) and one bought as Auria Pro...
I discovered that I can run both simultaneously on my iPad Pro...
As a test I run both thru Audiobus and did a mixdown of a track from the first Auria Pro into a audiotrack in the other Auria Pro... Great result!
What's good with that? I don't know, but, some perhaps could see any advantage of the possibility to run them both at the same time?
I also found a nice trick, in fact a thing that is not quite practical even in, say, Logic Pro X, albeit possible with advanced routing. I am talking about recording soft synths real time in Audio, using the built-in keyboard, just by inserting them in Audio tracks.
Most Desktop DAWs and all other iOS DAWs require you do use a MIDI or "instrument" track, or use AudioBus/IAA on iOS.
For recording simpler stuff, like drums, and as long as I don't use the built-in FF synths - which do require a MIDI track - that's the way I'm going: record the synth/drum - turn on Warp - apply Audio Quantize.
That's how I usually record soft synths, using IAA instruments as inserts on audio tracks. The new keyboard does make this more convenient though, in the past you had to switch to the instrument and play its keyboard, whereas now you can play from within Auria.
Warning: the latest version of Tonebridge equals Auria poison:
http://auriaapp.com/forum/viewtopic.php?f=20&t=14786
Perhaps this should be added to known issues, although I'm not sure it's Auria's fault?
An update with important fixes is out. Changelog in the first post.
Done!
Have there ever been any rumors or discussion around Auria Pro getting melodyne style pitch correction? Is it on @WaveMachineLabs so called "wish list"?
There's a Retune plugin in the Auria store, it's OK on ocasion but it's not Melodyne. There's also VoiceRack which can be usedan an AU effect, and a couple of others that can be used as IAA effects (Auto-Tune, Singaling).
Melodyne is not coming to iOS sadly.
Always great to get updates (and free ones at that), I should say I'm looking forward to the day when you can draw in volume / pan / automation envelopes in Auria much easier than the current (pretty slow and clunky) way.
Please correct me if I'm missing something here.
You can write them in real time by moving knobs in write mode, if you don't like Auria's way of drawing automation.
Agreed. This is a case of the app behaving like a desktop application rather than being optimised for touch. At least the MIDI automation editing is more fluid, would love the audio automation editing to be changed to match it one day.
Yes Richard, I thought it wasn't just me. Sure, you can use write mode, but that's not the way everyone does things - particularly with editing automations.
Indeed!
It seems Tonebridge advertises itself as an AU effect despite not being one. I guess this causes Auria's crash-on-launch issue.
Thanks Bram! Deleting Tonebridge solved the crash problem
I think this whole tonebridge thing will go to the first page.