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
All I know regarding GarageBand is that it internally runs at 44.1k (don't know the exact buffer size but I suspect it's 128 or 256 but could be a dynamic buffer size until automatic 'track freeze' is triggered) and uses Core Audio to up-sample to target sample-rate (48k on 'locked' devices). Export is always at 44.1k.
As for AUM and other hosts, the buffer-size the plug-ins use is controlled by the buffer-size set in the host.
Some hosts can optionally force plug-in re-sampling (ZenBeats has an option for this).
I have no clue whether SM2 uses a fixed internal sample-rate and up/down-samples to the host-sample-rate?
This could potentially explain the buffer-size related issues especially of audio and UI is handled in the same thread.
There's quite a bunch of plug-ins that miss-behave when buffer-size is >512 (some even totally crash is buffer-size is set to 2048). In those cases contacting the developer and make them aware of the issues is the only thing one can do.
Same goes for sample-rate related timing issues which do affect some apps...
Hopefully this issue can be sorted out as even on faster devices larger buffer sizes can sometimes be quite handy.
(I've still not managed to get stuck keys with SM2 on the 11" M1 iPadPro regardless of buffer-size).
Cheers!
Appreciate the additional insight.
It sure is.
Yes I'm following this thread, we will check this issue further and will release a fix for it.
Thanks. I'm just very happy Samu was able to narrow down the problem to something I could use to fix it today.
@Samu for PRESIDENT!
The system works!
+1 👍
@NeuM Do you think you could be a good audiob.us citizen and update your very first post with your findings? This would help a future user out.
Thanks, but honestly I do prefer to 'stay in the background'
The suggestion to try alternate buffer-sizes was a real long-shot but considering that many apps fail or behave weirdly when using 'larger' (>256) or 'smaller' (<128) buffer-sizes I thought it was worth a shot.
Without @NeuM 's video with audible crackles I would likely not have suggested trying to use alternate buffer-sizes as the crackle was never mentioned as one of the issues combined with the stuck keys.
Thankfully the issues is resolved for now and everyone can enjoy SM2!
Cheers!
Ahhh… going for Illuminati head then. Wise choice.
It's part of my free preset pack - you can download some of them from within SM2 in the online section, but there is a more extensive version available here:
https://richardyotmusic.gumroad.com/l/synthechoes
Yes, thanks for making those free presets Richard.
My pleasure, I should make some more sometime.
flagged...