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
What is the state of the state as it relates to plugin-delay compensation in Auria? I'm not referring to bouncing/rendering issues here just basic PDC "live" in the DAW.
Do effect plugins report their latency to Auria so it can compensate on playback? If so, is this also extended to AUv3 effects?
cc:
@WaveMachineLabs
Interesting question indeed...
The AUv3 standard supports it. There's a 'latency' property which can (in theory) communicate a plugin's built-in processing latency to the host. I'm not sure if any host implements it.
^i believe that Mr. Kymatica has used this in AUM. It has some sort of latency adjustment for IAA and AU apps.
Not me....I spend half my time building bi-lingual websites!
Is state saving working on Timeless 2 in this version? It's never worked for me, and always reverts to the default patch.
@sirdavidabraham , The state of state savings, from my limited testing, seems to be better in Auria Pro than any other app I've tried, but timing still varies from app to app. For instance, every test I've done with RuisMaker and RuismakerFM are sample perfect on the timing.1 But different apps like iSEM and Funk Drummer had small amounts of delay.
IMO, this is just something to accept and deal with. There doesn't appear to be any magic bullet that is going to make PDC work across the board without having to check/fix. Fortunately, with Auria this is a breeze. Just turn off snap, zoom all the way into the beginning of the clip, adjust the start point, turn snap back on, and move it into place. It's very easy to set the start point to the exact beginning of the audio. One suggestion, though is to turn off auto crossfade so that you don't lose any of the first transient.
(At least one other poster has reported different results with RuisMaker, but it works perfectly for me every time.) ↩︎
The name of the preset always reverts back to "default" but the settings should stay as they were set. So it is an annoying bug since you can't reference what preset was selected, but at least it shouldn't actually change the sound.
Oh ok thanks. Time to update to 10 I guess...
I just updated to 10: until now, no surprises - everything is working just as before.
Okay good to know the spec supports it. One thing, if future DAW updates finally support it then suddenly everyone's mixes will sound different. So I'd say the hosts need to get this out of the way soon
The problem perhaps isn't at the host, but the AUs themselves. Otherwise ones wouldn't have sample accurate timing in Auria (Ruismaker!) while others slip a few milisseconds (iSem).
Having a feature available in the AU standard doesn't necessarily mean the developers knowing (or caring about) how to implement it, @sirdavidabraham.
Oh to clarify I'm not talking about the render timing issues here. It's PDC in the mixing environment. Particularly with effect plugins
Say for a lead vocal you add EQ, plus compressor, plus phaser etc. in this chain the latency from each plugin is cumulative. So the vocal is heard later and later relative to the time of the project based on the latency introduced by each plugin.
With PDC the host will take the latency from each plugin into account and start to play the vocal track earlier to offset the cumulative latency. Something that I believe all desktop hosts implemented at least a decade ago.
If it's not yet implemented on iOS, it eventually will and when that happens all those vocal tracks will sound slightly earlier than expected.
Auria has delay compensation in its settings. Perhaps this is it?
I never really notice latency at playback with Auria, unless while playing live with a buffer larger than 256 - and this cannot be solved either in iOS or Desktop, because it's physical, roundrip latency, unless some genius coder develops a psychic algorythm that can actually predict the future.
P.S.: just took a look at Auria>settings, and it has record latency adjustment, which is definitely not what you're talking about. So we'll have to wait for @WaveMachineLabs to answer, because you raised an important question, @sirdavidabraham.
Yeah I haven't really looked deeper into on iOS because I've been afraid finding out the truth would put a damper on my enthusiasm
Hopefully PDC is already there.
However I did notice some lag build up once when I tried the TC Voice Rack AU in Cubasis. I immediately closed the project...because I definitely can't handle the truth.
Auria has had a complete PDC implementation since the beginning. Every channel, bus, aux and plugin is fully compensated for latency. And now with AUx as well.
Rim
Thank you very much, Rim! As I thought, because as I said before, I really never noticed any timing inconsistency during playback.
All the best!
Huge! Thanks!
While AU is nice in theory, it's very flaky at the moment. Reminds me of the early days of IAA when nothing worked reliably. Tried loading DDMF Envelope and it was insta-crash, tried using Micswap Pro and it reverts back to the default SM58 mic every time the project is loaded. Give it a year or two and maybe things will get better, but at the moment AU doesn't seem reliable enough to use in a project.
In my experience IAA is still very flaky and worthy of eternal damnation
I am nice in theory but am very unreliable and prone to crashing also. Live in fear of being deleted or replaced.
Indeed!
About the MIDI panic with the FabFilter synths, while Rim doesn't release a fix, the workaround is to open the piano roll, and using the piano roll's keyboard, to play the note that is stuck.
Just find out you can save AU presets in Auria the same way you do with the FabFilter synths. Very good!
No probs! Will share anything I find useful
Been floating around these forums for ages and have learnt a lot from everyone here!!
With the most recent update, Auria really is definitely the best DAW on iPad - it's midi timing is tight and doesn't flake unlike Cubasis....the AU update has totally changed the game, poison synth is great now with AU! Was stress testing the iPad Pro at throwing as many instances of AU synths and effects at it (including fabfilter plugins) and had enough to work with without freezing any tracks! I'm so bloody relieved we're heading towards desktop level.
Agree to 100%...
iPad Pro (big one) has a lot of CPU power...
We have come a long way with the software to iPad since 2010...
What about the smaller Pro? It should perform about the same, since it also has an A10X CPU... Right?
P.S.: if any owners of 9.7 iPad Pros do any stress tests with Auria, please share results!
Got to say, my Air2 still isn't too bad. But as they say - things don't stay still in the computer world.
Air 2 is fine for me.
Are Apple not announcing any new iPads this October?