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.
Auria pro au glitch?
Imported tracks into ap to mix and when i added ddmf reverb in aux 1 nothing sounded. After verifying that all was as it should (send set up correctly etc) i replaced it with one of the ap reverbs and it worked immediately. Tried with another au and same deal. Anybody getting a similar issue?
Comments
I cannot test it, because all my AUs are instruments, and all of them work like a charm. But I'm interested in knowing if this is a bug as well.
Yes, there is a bug I think. I see it when trying to use Korvpressor. The AU appears to load, but silences Auria Pro. Closing Korvpressor and reopening it can also result in a blank controls for the AU. As soon as I set that effect slot back to none, sound returns.
In settings try to use 512 buffer size and all will fine )
>
Eureka! Problem solved, at least for me. Thanks for the post.
So only 512? Not more or less? Hmmm. Will give that a shot as soon as i can. Thanks.
Yes, not more )
>
So what is the point of greater buffer sizes, if they can't be used with AU, where more space would be helpful?
We need to be sure it isn't a weird Apple restriction for the AU-X, just as they did for MIDI. If not, better tell @WaveMachineLabs about it in the Auria forum.
That's why I invested a lot in Auria plug-ins and nothing in AUs that are not instruments (P.S.: almost nothing: I do have Frekvens): Auria plug-ins just work, someting Apple used to advertise in the good old Steve Jobs' days.
tested it and yes, au stops working after 512, works with 128, 256 and 512. major issue as any session with a healthy dose of fx is probably going to hit the wall soon with 512. was workable for me since my song had most processing done before importing into auria and all i really needed was a reverb, delay and dynamic processing.
on a pretty "unimportant" tangent though....a lot of the auria plugins are ugly.
Such as... ?
WTF?
Please, mention one example of your opinion...
Especially Fabfilters plugins is gorgeous!
Please, change this thread name to SOLVED...
>
Respectfully, @ErrkaPetti, it's not solved. There is a workaround. Obviously, those wanting to use more AU would befefit from a higher buffer rate.
Indeed!
A pretty simple test would be to test the same FX at higher buffer sizes in Cubasis or AUM. That should establish whether it's an Auria problem or not.
This has nothing to do with Auria, as Auria can use buffer sizes up to 4096. But in my testing, most AUs aren't equipped to handle buffer sizes larger than 512. I suggest asking the developers who make those AUs to add support for larger buffer sizes.
By the way, iOS doesn't support MIDI with buffer sizes larger than 512, so that might be why the AU developers chose not to support it.
Rim
Apple, Apple... how hard will you keep on trying to do it wrong?
Gorgeous, but a year later and Timeless 2 still reverts back to the default patch when I reopen Auria. I reported that as a bug and it still ain't fixed.
Are you sure it's the default patch, or is it only shown as it was it? Because the bug happens here as well, but without any reverting of the actual patch: only the name of the patch reverts to "default", which can be a little annoying if I used a preset and want to copy it to another track, but no deal breaker or workflow killer, and my workaround is to save to auria any FXs I use. This way, if I use a preset or program a sound in a music called "Some Music" to a track called rhythm guitar, I save it as "Some Music rhythm guitar".
This is a half truth only...
It maybe shown Default Patch in the UI but it's the right patch that Auria loads when reopen the project...
yup, just tried it. works in aum at 1024 and cubasis (unless i didn't look in the right place) doesn't state the number but i tried it in medium which seems to be the most and it works.
If you have saved your used preset it is pretty easy to reuse that specific patch again... You don't loose your settings then...
yup, not solved.
In Cubasis, I think "medium" equals 512, and the others are 256 and 128.
But, at least change the threadname so it's cleared that IT'S NOT an Auria Pro bug...
Officially blame specific apps for the glitching is unfair to many hardworking developers...
It's an limitation that you should blame Apple for...
some of the fabfilters are nice, and the psp channel strip look great. but the stock reverbs, especially the convolution, aren't to me, and the delay and chorus. piano verb and spring verb are fugly. the resolution seems to be off on some. but anyways, splitting hairs, just that i'm getting spoiled by some fx that are way prettier (to me).
did you not read that it works in aum at 1024?
Interesting thing this in AUM: isn't it perhaps letting you set it to 1024 but internally changing it to 512 to let the AU to work?
I am almost redownloading AUM just to check how it goes with Frekvens at higher buffer sizes, performance-wise, to see if what's reported corresponds to what is being actually used by the app.