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
This is working very well for me. 😎
I got some nice guitar and bass files from https://freepats.zenvoid.org. Once I worked out how to decompress them and I placed them on a folder I created for sfz files on my device, they loaded quickly and sounded great. I was sure I'd hate the acoustic guitars, but they actually sound really good.
Then I tried out the 600mb Salamander FLAC sfz. It loaded in seconds and works great.
I couldn't make any sense out of the guitar sound font from the unreal instruments site discussed above, but don't need it. I only use app based guitars when I'm in a rush, and then only temporarily.
I'm super happy with the app though. Lightweight, distraction free, and purpose built. Thanks @RyoutaKira !
300 mb piano with wav samples loaded instantly. Love the app and the logo! Thanks!
@RyoutaKira
Everytime I come back to the standalone app from the background, it crashes or simply gets stuck on a black screen.
Another issue is I go and select a patch and it always asks me to select the sfz folder and in some cases(unreal instruments standard guitar as an example) I have to actually select the parent folder and not the sub folder with the sfz file.
Is it possible to change the behavior to simply select a source folder for all my sfzs at once as a default location and to be able to create categories for the instruments so that when I tap on the patch name it’ll open a menu with categories which lead to sub menus with the instruments?
Same with the arrows by the way, them being able to switch patches back and forth according to the category structure would be amazing.
But that’s a mere suggestion, I think the highest priority would be to be able to select a default folder for all my sfzs at once.
I hope it’s possible to add these features.
Besides that, I’m happy to finally have a sforszando alternative on iOS as I contacted them a few months back about an iOS port and they replied it’s not going to happen.
@RyoutaKira Could we get sfz support for KQ Sampei? I'll get this to support but it would be preferable to use sfzs there.
I found that sfz files which has unmatched case sensitivity caused a crash or it crashes when the sound files aren't in the specified folder.
I'll fix the bug soon.
You can put all sfz sets into a folder and specify the folder. Then you are never asked again.
I have no plan now. Excuse me.
@RyoutaKira
Trying to play this library using the latest version produces a lot of random crackles while playing- https://shop.karoryfer.com/pages/free-black-and-blue-basses
Tried standalone, hosted, multiple buffers and preload sizes, different max voice settings nothing helps
On buffer 512 it’s even worse and becomes completely unusable.
I just tried the sound with both isfizz version 1.2.10 and 1.2.9 on iPad mini 5.
but it works normally and I cannot find the issue.
could you tell me the email address via DM and I'll invite you for TestFlight, then you can test the older versions.
@bargale
Did you update the iPadOS?
It might be possible that the OS writes/reads the disk a lot so the crackles occur.
I’m on 17.2
M1, 16gbs of ram
@bargale
I have found that the sfizz engine has a bug that affects performance especially when note-on.
I believe the problem has been fixed in the isfizz version 1.2.11.
Thank you for reporting!
It seems to be using a lot less cpu for me than it was, thanks for the update!
I will try it again later on today and will report again if I see any changes for better or not.
Your hard work is much appreciated by me, thank you.
Really great to have access to SFZ libraries! I’ve already found some good ones shared on this thread.
It seems that @bargale 's issue still exists...
I found another bug in my app and I will fix it soon....
Not sure if it’s 100% resolved but I think I’m trying to tracking down on what is causing it and it feels like an iOS issue.
I can say that the latest beta version is a big improvement.
I’m finding isfizz to be the only worthwhile sfz player on iOS, can’t wait to see how well it works with a midi 2.0 controller
Big improvements are coming, isfizz is very underrated, just saying.
@RyoutaKira Any plans for envelope controls?
I will do after the main branch of the original sfizz supports them. I think it is near future.
Oh I mistook it for curveCC.
isfizz already supports ampeg_attack_ccN, pitcheg_attack_ccN, fileg_attack_ccN, etc..
But can you modify them using a user interface?
With the following sfz example, CC1 appears. The CC1 can control amp eg attack time.
<region>sample=*sine
ampeg_attack=0.02 ampeg_release=0.1
ampeg_attack_cc1=1
Oh that's very cool. Does this mean I need to do some sort of global search and replace on all my sfz files to get this happening across all my patches?
there is a <global> section. in that section, all regions are affected.
@jebni
You have to do this on all your sfz files currently.
I started editing my sfz files but got errors about unrecognised opcodes when previewing in Sforzando. I removed the last underscore, so it was "ampeg_attackcc1=1" and it seems to be working. So I take it that the value being specified is the number of seconds, which the CC value attenuates proportionally?
I'm sorry.
ampeg_attack_onccN or ampeg_attackccN should be correct.
The attack value is the number of seconds. The value can be negative or decimal.
I think it is proportional but I am not sure.
Fantastic. I have to say, this is a lot of fun — thank you. It seems that the SFZ specification would stop you as a developer from overriding these CC designations in favour of a default global ADSR system, which would be the most user friendly thing to do, but the nerdiness of this is very enjoyable.
although I think most of people just use given sfz files
or most of people are not interested in sfz.
Tweaking is really fun!