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
And with AL disk streaming I can run 6-10 AU AudioLayer instances in AUM and not worry about the dreaded 340 shared RAM limits for AU instruments. Anyway, I just think it has a lot of untapped potential. Using the newly updated SynthJacker app I made 10 new AL instruments today.
Not sure if you are aware that BeatHawk also does disk streaming of its velocity-layered multisamples and that you can load 16 of their multisample instruments into one BH instance which can be set up as an easily recallable project. Perhaps, you know this already but thought I'd mention since many are unaware of this.
I wasn’t aware of this! Cool!
Took a look this morning to see if I could figure out how to tweak the Salamander Piano translation so that it plays more closely to how it was intended.
There seem to be two main issues (well it sounds pretty great even without fixing them).
One issue is that there is a layer that is for the hammer noise. I don't understand enough about sfz. There is a "group" for hammer noise. In the sfz file, this text appears:
Followed by the samples in the group (one for each note of the keyboard). In AudioLayer, this layer plays pretty loudly for every note struck. My workaround was to set the layer's volume as low as possible.
There are some other layers labeled like this int he sfz:
I've also made them inaudible. I am not sure how they are supposed to work.
Lastly, there are layers for the pedal noise which don't seem to work:
I am not sure if EXS24 supports the features or not.
I am not sure if these are are features supported in sfz but not EXS and not AudioLayer or if they are features supported in sfz and EXS but not supported in AudioLayer. Or if they just didn't get translated right.
Any ideas?
@xmortenx , @Audiojunkie , @Lithalean , @jonmoore
I hope you don't mind if I answer your questions.
First of all, what SFZ and EXS support doesn't matter much, in the end AudioLayer will be the limiting factor.
Your first SFZ line requires a release trigger which you have to set for that layer in AL, so these samples are played when releasing the key.
In addition to hammer noises you apparently also have release samples which are triggered by key release as well.
The idea is to simulate A. the mechanical noise when releasing the piano key and B. to simulate the sound generated when the damping felt touches the strings to silence them after key release.
So far so good.
The problem starts to become obvious when you actually use the release-triggered samples for natural (sampled) instruments with a naturally decaying tone like Piano, EP, Guitar, Bass, Strings, ... well, most acoustic instruments.
After an update, AudioLayer has learned to choose release samples depending on the initial velocity, so the harder you hit a key, the higher the velocity chosen for release samples.
Unfortunately this is not enough when trying to build e.g. an acoustic piano sample set: If done correctly, AudioLayer would not only choose the release sample depending on initial velocity but also depending on how long the note was held before release.
You don't want a loud release sample after the note has almost faded to silence, do you?
I have yet no idea how to work around this because applying an envelope won't work, as it's only triggered by key release and therefore will start at zero.
The only hack I can think about is to use a MidiFire script to add the "intelligence" that cannot be put into the AudioLayer program.
Pedal noises are a bit easier to handle by just mapping the respective samples to very low keys and translate pedal values to MIDI notes in order to trigger them. The pedal messages could also be mapped to control the level of a sympathetic resonance layer.
@rs2000 : thanks very much.
What about the pedal noise? I don't see a pedal up/down modifier the way that there is for mod wheel. Am I overlooking it?
One minute before you posted I've added exactly that
@rs2000 : Tx
@rs2000 : is the AudioLayer release feature you mention, in the current version or something in the beta?
@rs2000 : re pedal. Could one also set the pedal layers to be triggered by mod wheel (which AL supports) and use MIDI Fire to translate from sus pedal to cc1?
You're welcome!
If you ask me, AL development is dead already. Harry might fix really severe issues coming up in the future but he hasn't answered a single question here since months (afaik), that tells me how much he cares.
Wait, by "trigger", do you mean crossfading between layers?
There are several ways to re-map pedal messages, even mapping to a different MIDI channel could be an option. I'm currently trying to get my head around how to build a better AL piano without all the features I'm used to from using NI Kontakt in the past.
@rs2000: while Harry seems very rarely to answer emails, I had a response to an email reporting the bug of AL crashing because it sometimes searches in its trash for samples. While the response was short, it gave me the impression that he has been working on AudioLayer and doing more than just bug fixing.
By trigger, I meant that if I understand correctly, one could mark the pedal noise layesr with the articulation, "mod wheel up" and translate sustain pedal on off to CC#1 so that the layer would get triggered when the pedal is down...or do I misunderstand how this all works?
If you put a folder that has an EXS file and the samples in AudioLayer's public folder (this is for people not using the cloud storage option), Audio Layer seems to create copies of the sample files in its private storage.
Is it safe to delete the files in the public folder? Or are the copies in the AudioLayer's non-public directory just aliases to the ones in the public folder?
That would be great indeed!
Yes, you could do that. For each layer, you can adjust if it's audible with modwheel up, modwheel down or both.
I did not know this. Thank you for slipping me another clue. I discovered the BeatHawk User's Manual a week or so back and intend to read up on it's capabilities at some point.
I think of BeatHawk and Gadget as lovely walled gardens. Nice to visit but I don't want to live there. You just can't add Apps and Samples to them if you start creating there. I just keep firing up AUM and building "sound creation environments". I made this complex set of tracks driven by Aphelian and sent it all into a track with the Enso Looper and recorded
it and killed all the other tracks and kept the Enso Loop. I was doing it before making AUM files.
So now, I can use SynthJacker to extract some of the "flowers" from the BeatHawk Garden
for light weight instances in AUM w/ AudioLayer. I could run Gadget on an iPhone and sample with an audio interface I think. But maybe SynthJacker will add IAA or AB next to it's hosting features.
The fun is in solving problems and glueing things together with a pay back in constructed sound canvases.
Considering that on desktop systems, everything is so much more advanced and refined (and not much left to improve upon), it sometimes seems o me like we men simply needed a new challenge that we found in iOS music making
I recently rediscovered Audiolayer as I realized its EXS import capability. My main goal is to import a few multisampled acoustic drum libraries (I have some DrumDrops libraries and the sampler patches that come with the library).
I have a light (100+ samples) Drumdrops library which imported successfully, but the purchased ones, with samples in excess of 1500 wav files will not import. I have experimented with keeping the original folder structure of the drum library intact (placing it in the Audiolayer import folder) and also moving all samples + EXS files to one folder which I place in the Audiolayer import folder. Having all files+samples in a single folder makes the initiation of the importing faster, but the import always gets stuck at apparently the same wav file, and the result is 43 out of 1671 wave files imported into the Audiolayer samples folder for. After a while being stuck, the importing just stops as if the process is ready. There is no error message. When I start the import again by tapping the EXS file the import folder, the same thing happens again: the import is stuck at the same sample (so it does not e.g. continue from where it got stuck the previous time, as I was hoping).
Is there anything I could try before I abandon the idea of using Audiolayer? Are there limits to how large sample libraries can be imported into Audiolayer? I have the latest iPad Pro 12.9 with a lot of free storage space. thanks in advance to any advice you can offer!
My experience with EXS24 files is full of surprises, also in other apps. Often, the EXS files contain absolute sample paths that lead to missing samples, then there are version differences etc.
My best experience with importing samples into AudioLayer is to give the samples names that will let AL map them to the correct key and velocity zones. I don't use EXS import at all.
That's how I'm creating instruments and I've just finished one with many layers and almost 1000 samples overall.
To rename samples, I'm using batch scripts on the desktop.
You can also import layer by layer in AL and change the velocity or key ranges afterwards.
thanks @rs2000 - the samples are named as follows:
"DD018_Tambo Hit_V01_RR01.wav", where V01 refers to velocity and RR01 refers to round robin.
What kind of naming convention will work for Audiolayer? Sorry, I'm a complete beginner in building sampled instruments myself - how do I let AL map a set of wav files to the correct key and velocity zones?
You'll have to rename the samples to include a velocity value between 001-127 and a key name like A3, C#4 or B5.
Just tap on the keymap area, import samples and AL will tell you how the file name should look like.
Alternatively you just import a bunch of drum samples and move them to their good positions afterwards.
thanks again @rs2000! - I also just found this discussion: https://forum.audiob.us/discussion/32001/audiolayer
The released version has some problems importing large instruments. The beta version addresses many of those perhaps @VirSyn will get you a beta copy. I'd recommend sending him an email via his website and explaining and asking if you can get a beta.
I'm already in and indeed the beta version works well so far!
I like this news! Thanks! Larger instruments.