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.
anyone experiencing crashes with Pure Synth Platinum 2?
I am. Crashes when I try to start stand alone version using my Scarlett 2i2 as audio source.
and
When running more than one instance of PSP in AUM. If I run more than one PSP slot in AUM, it does OK for a few minutes, then all instances of PSP crash, then AUM crashes.
Not having crashes with any other apps
Thinking about requesting a refund. The sounds and interface are great but the app itself seems buggy, at least for me
Comments
You may be simply running out of resources in AUM. If you have Keystage, AUM, PSP, and possibly other apps running, you may just be out of RAM. IOS does arbitrary things when that happens.
Also, different patches can be super heavy in PSP. Check if the convolver reverb is being used. If so, switch it out for a lighter cpu reverb if you can. That convolution reverb is great, but really heavy on the CPU.
For the standalone issue ... the only thing I can think of is to check carefully that there are no midi loops going on.
PSP is a great app, but definitely consumes some serious resources. On my Air 2 I can get two instances plus some lighter apps going. Three is pushing it.
Great information. Thanks!
So, if I'm running just AUM with 2 instances of PSP and Keystage, I have about 25% free memory. If I'm running that plus other apps I usually run for a Keystage performance, it may drop down to 11%, no lower. I don't know how interpret these numbers, but surely at least the first (25%) should not be low enough to cause crashes.
How are you measuring memory use? I don't know of any reliable way to do that. I can't say I trust any third party memory measurement tool, but maybe they are somewhat accurate.
But it's not as simple as just measuring available ram. There are different types of memory resources. For instance, there are limitations on the total memory that all instances of a single AU app can use. These are independent from overall RAM usage.
But the real issue is Apple has it's own way of managing memory. It can decide all on its own to shut something down if it thinks it needs the ram for something else. You might think from experience with other operating systems that you can reliably predict behavior based on some amount of available RAM. You can't.
Sorry, trial and error is the only way to determine what works or not. I suggest trying different hosts to see if you fare better in them. Each host can have different ways of handling resource allocations within themselves. If you think there's a problem with a particular app or host, its best to reach out to the developer.
For instance, if you can run four instances of PSP in Audiobus but only two in AUM, with the same patches, that would be useful information for the AUM developer. If you can only run two instances in any host, that's useful information for the PSP developer. If you can run five instances without Keystage and only two with Keystage, that's useful information for yourself and/or the Keystage developer.
Lots of craches in the same context - two instances and boom. No interface, just headphones.
FYI. I'm using a free app called CPU Monitor
https://drive.google.com/file/d/1nsZqgmmn0O4DUfCfdgEOjEWeU2BGywlA/view?usp=sharing
Hallo, Ich habe das Problem das Pure Synth Platinium als Auv3 .. in AUM / Zenbeats abstürzt sobald man mehr als eine Instanz öffnet …….. IPAD PRO M2 2022
Hat noch jemand das gleiche Problem???
Sporadic crashes and failure to load as AUv3, Cubasis 3.5, Air 5, iOS 16.3.
@GospelMusicians
Just tested on my iPad Pro 10.5 running IOS 16.2:
Loading a second AUv3 instance of Pure Synth Platinum crashes in AUM, apeMatrix and AudioBus. Only used the default Init Preset, no other plugin loaded in the host. No other app running in the background. The Init preset uses only a single sine osc, it doesn‘t load big samples.
.
From the crash log in systen diagnostics:
I know for sure that on this iPad three AUv3 instances of PSP (with loaded presets) were possible some time ago.
I haven't experienced a crash yet on my M1. Then again, not everyone can afford an M1 (let alone an M2), and so hopefully by tagging @GospelMusicians we can get a fix on the way.
And there's this contact form as well. https://gospelmusicians.com/pages/contact-support They can definitely help.
My M1 was in fact having problems with Pure Synth Platinum, but the fix was to download the current Beta version. It now works.
The Air 5 also has an M1 chip.
I’m getting the same behavior on my iPad Pro. 2018, latest iOS version.
This was discussed in another thread and @GospelMusicians was tagged.
Hopefully they’ll sort it out.
They’re usually pretty good.
Contact them via their website. They have often mentioned that is the most reliable way of getting their attention
So far no crashes or oddities with PureSynth Platinum on my 11" M1 iPadPro, iPadOS16.3.
Granted I only have the 'factory content' IAP and none of the other bigger libraries yet.
I know that Cubasis can be a bit 'shaky' when using multiple instances of AUv3's that require lots of RAM.
Most of the time it's the iPadOS that will jettisons those apps/plug-ins from ram due to excessive memory usage...
Sometimes it doesn’t load for me in NanoStudio 2 and I have to reload and then my preset is gone, so I started writing my preset in my notes so I know what I had chosen
I’ve seen people on discord and facebook mention that the last update messed up PSP. I’ve told them to contact Gospel Musicians so that they are aware of it. It’s good to post on here about it, but contacting them directly is the best way to get it fixed. Luckily I haven’t update because I use it on everything. Usually 2 to 3 instances of it.
The failure to load, and also corrupted sound/patch was when using one instance of AUv3 in Cubasis.
@GospelMusicians
Contact them through their website. They only check here sporadically but keep on top of things reported to them directly.
An update has been released.