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
Hey @wim, I dove into the sfz like you suggested. There were notes in there on how to change the release time. I changed the setting from 1 to 0.7, now the notes can be played more staccato to my liking. Thanks!
Edit: looks like 0.8 is the sweet spot for me..
I'm able to get a new UI element to show up that I think is bound to amp_veltrack, but doesn't appear to be dynamically modifying that setting when I move the dial...It may be due to not understanding exactly what the settings in the "control" section do, ie: set_cc7=100 ... I think that may be setting the default but also may be more about the min/max, so need to do more research.
If you have any insight, @wim, I'm all ears (and I'm actually pretty happy with just setting the amp_veltrack to a low number and leaving it at that)...but do want to try to figure this UI piece out so that I can complete the bonus round! :-)
Yes,
set_sets the default. But, you probably want to choose another CC. CC 7 is generally used for volume. You're looking for something to control the amp_veltrack value.I've got a little time to look into this. I'll get back to you soon.
You can hook this up to a parameter so that it shows up on the controls page, defaults to 0.7, and is adjustable to suit other pieces. I'll detail how to do this in a bit.
@danm - look for the relevant sections in the code and modify as follows:
Assign a CC to use. Note that CC 7 is already used for
Volumeso don't use that. I'll use CC 23 as an example.This line sets the defaults for each control.
Append
set_cc23=64to that line (or whatever default 0-127 that you want).Right after that comes one line each to label the controls add something like:
The control won't show up yet. Controls don't show up until they're used for something. There is a line in the script that will be similar to
amp_veltrack=80.0, probably the one you edited before. We want to augment that line with one that responds to the CC 23 we defined.It's a little complicated to explain how this works, but basically, the CC 23 knob now scales the line above it. Fully increased the velocity sensitivity is greater. Fully decreased there's no velocity sensitivity.
Anyway, now your control should appear and you should be able to try it out. You may need to play around with the default setting (
set_cc23=64) and theamp_veltrackline to get a combination that works as you like. Leaveamp_veltrack_oncc23=100.0as is.I liked
set_cc23=64andamp_veltrack=100.I was able to globally raise the overall volume of the instrument without going into the red by adding
to the
<global>section to apply a 12.0 db boost. ymmv.Got it! All your steps were the same as what I'd tried except, instead in my experiments, instead of adding an add'l line:
amp_veltrack_oncc44=100.0 to the existing line of "amp_veltrack=80"
I had replaced "amp_veltrack=80.0" with "amp_veltrack_oncc44=100.0" (or rather just added the cc info that line).
Having both those lines in there, as you suggested, works.
Also, are you saying that by adding "volume=12.0" to the global section that it gave a volume boost of 12db, eh? Would have expected that to set the Vol param (ie: the one on cc7) down to 7, but apparently that's not what you found...interesting.
Did you find this documented somewhere or just trial and error?
Thanks!
Hey @danm , how do you like that novation launchkey? The shop I bought my zoom mic last week had 3 used notation launchkeys for sale, size 25,49,61. Was thinking of getting the 25 for travel composing. It was only $47, which I could haggle down a bit lower probably. Have you had any trouble using/connection it with iPad apps? I mostly use AUM and MultiTrackStudio.
Ahh. Shades of meaning are at play.
amplitudeis a 0 to 100 value that represents the percentage of the total volume.amplitude_onCCnscales that. Think of a a stereo's volume knob. It doesn't control the maximum output of the stereo, it scales it between 0 and the maximum output.volumeis like an amplifier. At 0.0 the samples sound at their recorded volume. At 12.0 they all get a 12db boost. There's a small risk in boosting the volume if the sample set was properly recorded so that the very loudest samples are close to 0db. Those would be pushed over 0db. I checked the lowest notes at high velocity and didn't get clipping, but it is possible there are samples in there that would be pushed over 0db.But that's probably not something to worry about too much. Clipping is less likely in apps and hosts that use 32bit internal processing.
Yes on both counts. The documentation is extensive but ... uh ... scattered (for lack of a better word). It's like a big box of puzzle pieces. You kind of have to assemble its knowledge by looking for pictures and patterns to help you piece it together. 😂
What text editors are you using to view and modify the *.sfz file(s) provided with this instrument.
I have Textastic and it won’t open a *sfz file unless I drag and drop the contents into an open session.
Changing the extension to .txt for editing helps and then putting back the sfx extension for loading
is useful and maybe essential for many text editors without drag and drop.
Looking at the 1800+ line file I can see that Dave Hilowitz used it for the creation of Decent Sampler metadata files with fewer options and some additional synth oriented options like MPE settings,
“note patterns” associated with a single note input, background image files and User Controls.
The required text input is rather daunting if considered from scratch but less so when editing an existing file with new samples… a powerful text editor with search and replace features is really helpful
to swap folder names and other bulk changes.
It occurs to me that the provided (and exposed samples) could be massaged into Decent Sampler format to test in that free instrument loader. There are many Decent Sampler pianos but Salamander seems to be in class by itself with 16 layers of volume distinct samples for A-C-Eb-Gb across all 7 octaves.
Hi @McD. I’m using a text editing app called Monote which was free last month. I have to change the file extension to .txt before it will open it however, and then change it back after.
isfizz has its own basic editor that is serviceable for small modifications.
Textastic on the iPad? I use Textastic on the Mac for editing SFZ files. I did add an SFZ grammar extension for it. I haven't looked into doing that on the iPad. Maybe I will, though I don't think I'd use it on the iPad. I don't think there's anything you can do on iOS if a file extension isn't registered with an app. The developer would have to do that.
General editing of SFZ files should probably be taken up in a separate thread though.
Hi @Dav,
I got the Launchkey Mini 37, the mini meaning it does not have full size keys but is also very lightweight and portable.
No trouble at all using/connecting with iPad apps, seems very plug and play.
It appears to have a built-in mapping to Ableton Live, so if you use that it may have even more out-of-the-box appeal, but I do not, rather am using it with Loopy Pro at the moment and it works great.
OK @McD - since it's a one-off quick help, here's what you can do to improve Textastic's SFZ handling on iOS. Download the
sfz.sublime-syntaxfile from GitHub: https://github.com/sfztools/syntax-highlighting-sublime-text. Make a folder namedsfztheTextastic/#Textasticfolder on your device, and place that file there. Restart Textastic and you should have syntax highlighting for sfz files.You'll still need to drag files from the Textastic sidebar into the editing area I think. Adding the syntax doesn't modify iOS file associations.
Thanks for the info, @danm.
I’ve been playing with the other 3 piano versions today, twilight, moonlight and Noct. They are really nice on more delicate/soft pieces. I’ll be keeping one of them on my ipad for soft songs. The people behind this project really did a professional job making these soundfonts.
A mind-boggling free contribution. A huge amount of probably very tedious work that went into these.
Thanks. The syntax highlighting is nice.
Th “A-Shell” (Unix tools environment) has a diff command to compare the small changes made between the 8 provided sfz files. Hmm… diff shows hundreds of line edits between sfz files. So, a bulk find and replace tool or “sed” scripts might be needed.
I think looking into pulling the samples into a Decent Sampler metadata file might be
an interesting (and time consuming) experiment.
There’s been a little update to the sfz files last week for the accurate salamaner piano, now at v6.1beta4.
In this beta update “Damper Pedal Resonance" and "Half Pedaling" have been implemented. A new sfz version was added called “sfz_minimum” to use with players with limited resources. You can read all about it and download the new sfz files on the same project page here:
https://ir.isas.jaxa.jp/~cyamauch/AccurateSalamander/
NOTE: You will have to download and install v6.0 first to get all the wav files for the sound font if you dont have them already. This v6.1beta4 download is just updating the sfz files to use with them.