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.
sfz files in Audiolayer
Has anyone here been successful importing sfz files to Audiolayer? I’ve tried following their tutorial exactly but Audiolayer does not open and import the samples. My sfz files just open to the regular file info when I click on them inside the Audiolayer import folder. I’ve imported exs files with no problem but can’t figure out the problem with sfz.
Comments
There's some advice on importing sfz on page 38 of this thread.
https://forum.audiob.us/discussion/27726/audiolayer-by-virsyn-the-mobile-sampling-solution-for-ios/p38
As I recall the directory you place the *.sfz file and the related "./samples" folder is key to success. I know most sfz'es come packed as zips but unzip is probably required and then
the relative locations of the files and the sfz parameters file is key. The path used specifically in the sfz file must also match the installation. Hopefully, it show a relative
path or else you might have to edit the path names.
Excellent, thank you! I'll check the file paths.
Works fine for me. Are you using cloud storage or On My IPad. I use the local storage option.
See: https://wiki.audiob.us/audiolayer
Make sure that your sfz file is in a folder that contains the folder of samples it needs.
Someone posted videos showing the process.
Yes... that's another important tip to insure successful SFZ importing. Move the *sfz and ./samples folder to the "On My iPad/AudioLayer/import" folder.
There isn’t an import folder in On My IPad (at least on mine). I just put the folder with the sfz and it’s samples in the AudioLayer folder.
I just tried importing samples I have in the Nanostudio2 "Obsidian Synth" format. They are all in a single folder and the Note names are embedded in the files so they import very quickly and create full coverage of the keyboard. None I've found yet have any distinct velocity information tho' one had "MF" (Mezzoforte) in the names. I'll see if any have more than one layer. It's another source for easy to import quality audio samples for AudioLayer.
Nice tip about Obsidian files. I got it fixed somehow. I offloaded a ton of apps I'm not currently using and now it's working fine. I'm not sure what might have caused some kind of conflict with sfz files. I think the only sfz capable app I offloaded may have been Audio Evolution Mobile (great app, just not in the rotation currently).
Yes, Zenbeats ended up being the problem for me
Zenbeats is the only app that’s ever caused OS level changes for file types that are shared by other apps for me. I think Apple should prevent this from even being possible for developers to do. I ended up backing up and restoring my iPad as I initially thought it might be an iPadOS bug as before when my iPads were on iOS I didn’t encounter the problem. You don’t even have to open up Zenbeats, just downloading it is enough.
This seems to be a "plist" setting that shocks me even exists. When declaring a file type that an app uses, it can be set to be the owner of that file type, or can be just one of the apps that uses that type of file. As soon as I saw that setting I thought "wow, that is an accident waiting to happen".
I'm just a rank beginner at learning iOS development, so I could well have the wrong information, but this does seem to bear that out.
I would think the App Store screeners would keep an eye out for this.
My basis (emphasis added):
If that's the case, would a re-install of AudioLayer help?
At least its .plist would be registered again.
Maybe.
I think this may have fixed similar errors with other apps if I remember correctly.
Good suggestions, unfortunately—
If Zenbeats is installed on the iPad with iPadOS, deleting AudioLayer and reinstalling it doesn’t fix the problem. Deletion of Zenbeats does. I’m disappointed to be stuck between Apple, the Zenbeats developer, and the AudioLayer developer who haven’t fixed the problem so I can have both apps installed on the same iPad running iPadOS and import SFZ files into each app. Isn’t the ability to use SFZ instruments in multiple apps one of the strengths of SFZ after all?
@Paulinko
Oh my, I'm surprised something like this can happen at all.
Thanks for trying it though!
Have you reported the issue directly to Roland tech support? If you've already reported it then I won't bother, but if you haven't, I will go through the (considerable) effort of seeing if I can replicate and document the problem. I don't want to go to the trouble if you've reported it and they haven't addressed it.
... or maybe I could bypass the trouble and see if @MatthewAtZenbeats might take five minutes and check the document
declaration in the info.plist. Should be super quick to check.
I’ve let him know about this issue from the get go. Perhaps you have more pull?
Well, we'll see if he responds here or if I need to do a full bug report. Reporting issues on this forum isn't a supported route and I can't really say I'm entitled to a response, especially when it's just a wild guess by a novice programmer at what the problem might be. ✌🏼
I pinged Matt and let him know about this....
@onerez @wim @rs2000 Matthew has communicated with me so hopefully he’ll be able to trace the source of the issue. Unfortunately Zenbeats is the only app I have that uses sfz files that changes the sfz file icons on iPadOS. AudioLayer did that on iOS, but it just uses a generic blank icon now on iPadOS.
I’ve also communicated with the AudioLayer developer about this ongoing issue too.
If Apple were really on top of things, they wouldn’t allow developers to even get in this sort of mess by being able to automatically prevent them from doing this at the OS level or catch it during App Store reviews.
In previous versions of iOS, users once upon a time, had access to plist files for apps via iTunes and could presumably fix this sort of problem themselves. Now we’re at the mercy of app developers and Apple to resolve it for us.
Apple’s Support system is useless for these sorts of issues as you can’t contact anybody at Apple who might actually be able to do something to resolve the issue.