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 Store

Loopy Pro is your all-in-one musical toolkit. Try it for free today.

Tutorials on sampling a piano and making a soundfont?

DavDav
in Other Music Content

Lately I’ve been contemplating sampling a piano. I have access to a beautiful sounding high-end grand piano at one of the upscale communities I gig at, and am toying with the idea of trying to sample it to make a soundfont.

I’ve watched a few videos on doing it. Are there any tutorials around here using apps like AudioLayer to make a piano virtual instrument? Or if you have any advice for a novice at all on this I’d appreciate it. Talk me out of it if that sounds smarter…

Thanks!

Comments

  • wimwim

    Making an instrument out of the recorded samples isn't too difficult. I prefer making sfz instruments because no software other than a text editor is needed, and making changes and adjustments is just editing text. Sf2 is another widely used format. Polyphone is a free Windows/Mac/Linux software that can create sf2 sound fonts. KQ isfizz and KQ Sampei are good players for these two formats.

  • DavDav

    Thank you @wim. I will look into polyphone.. I have both the KQ apps for iPad, making a SFZ sounds good too.

  • wimwim

    @Dav said:
    Thank you @wim. I will look into polyphone.. I have both the KQ apps for iPad, making a SFZ sounds good too.

    I had an easy workflow going using a plain text editor (Textastic) and SFZ player (sforzando) on MacOS. Changes made in Textastic showed up almost immediately in sforzando. Once the sfz file was as I liked it, I would transfer the whole folder over to iOS devices using Air Drop.

    You could eliminate the air drop step by placing files in iCloud, but KQ isfizz warns that loading from cloud storage could come with issues, so I've kept the files local.

  • McDMcD

    I was curious to see if Google’s Gemini agent had some advice on SF2 creations. It did and I can ask for additional info if anyone has a good additional prompt. I asked:

    How do you make an SF2 sound font?

    Creating an SF2 soundfont involves several steps, and here's a breakdown of the process:
    1. Planning and Preparation:
    * Define your sound: What kind of instrument or sound are you trying to create? This will guide your sample selection and editing.
    * Gather your samples: You can record your own samples, use existing ones (with proper licensing), or a combination of both. Ensure the samples are high-quality and in a suitable format (WAV is common).
    * Organize your samples: Arrange your samples logically, considering factors like pitch, velocity layers, and articulations. This will make the editing process much smoother.
    2. Choosing a Soundfont Editor:
    * Polyphone: A popular and user-friendly open-source soundfont editor. It offers a good balance of features and ease of use.
    * Swami: Another option, particularly if you're comfortable with a more technical interface.
    * Extreme Sample Converter: A powerful tool for converting between various sample formats, including SF2. It can be useful if you're working with samples in different formats.
    3. Creating the Soundfont Structure:
    * Presets: Soundfonts are organized into presets, which are essentially different instrument patches. You can have multiple presets within a single soundfont.
    * Instruments: Each preset contains one or more instruments. An instrument defines how the samples are mapped to MIDI notes and how they are played.
    * Samples: These are the actual audio files that make up the sound. You'll import your organized samples into the instruments.
    4. Mapping Samples and Setting Parameters:
    * Key mapping: Assign each sample to a specific range of MIDI notes. This determines which note triggers which sample.
    * Velocity layers: If you have samples at different volumes (e.g., for different playing strengths), you can map them to different velocity ranges. This allows for dynamic expression.
    * Looping: Set loop points within your samples to create sustained notes. Proper looping is crucial for realistic instrument sounds.
    * Envelopes: Adjust the attack, decay, sustain, and release (ADSR) envelopes to control how the sound changes over time.
    * Modulation: Use modulation settings to add vibrato, tremolo, or other effects to your sounds.
    5. Testing and Refining:
    * Play your soundfont: Use a MIDI keyboard or software to test your soundfont in different contexts.
    * Adjust parameters: Fine-tune the key mapping, velocity layers, looping, envelopes, and modulation to achieve the desired sound.
    * Iterate: Soundfont creation is often an iterative process. You may need to go back and adjust your samples or settings multiple times.
    6. Saving and Exporting:
    * Save your work: Regularly save your progress to avoid losing any work.
    * Export as SF2: Once you're happy with your soundfont, export it as an SF2 file.
    Tips and Considerations:
    * Sample quality is crucial: Start with high-quality samples to ensure a good-sounding soundfont.
    * Pay attention to detail: Small details in key mapping, looping, and envelopes can make a big difference in the overall quality of your soundfont.
    * Experiment: Don't be afraid to experiment with different settings and techniques to create unique sounds.
    * Learn from others: Explore existing soundfonts and tutorials to learn from experienced soundfont creators.
    By following these steps and paying attention to detail, you can create your own custom SF2 soundfonts.

  • McDMcD
    edited February 14

    I then asked:

    Is there a sound font editor for the IOS devices?

    While creating SF2 soundfonts is generally more common on desktop platforms, there are some options available for iOS devices that allow you to work with soundfonts:
    1. SoundFont Pro:
    * This app focuses on playing and customizing SoundFonts, particularly piano sounds.
    * It allows you to import your own SoundFonts and provides some built-in synthesizer tools for editing.
    * While it might not have the full range of features of a desktop editor, it's a good option for those who want to work with SoundFonts on their iOS device.
    2. bs-16i:
    * This app is a SoundFont player that can be used standalone or as an Audio Unit Extension.
    * It supports large SoundFont files and has been tested with various SoundFonts.
    * You can import SoundFonts via iCloud or other locations on your device.
    3. JamKoo:
    * This app is a SoundFont player and recorder built with AudioKit.
    * It comes with a selection of instruments and Chinese musical instrument packages.
    * It's a user-friendly option for loading samples and recording on the go.
    4. SoundFonts app:
    * This app acts as a polyphonic audio synthesizer that uses SoundFont files.
    * It can be used as a standalone app or as an AUv3 plug-in in other music apps like GarageBand or Logic.
    * It also includes reverb and delay effects.
    Important Considerations:
    * Limited Editing Capabilities: iOS apps might not offer the same level of detailed editing as desktop soundfont editors.
    * Performance: Older iOS devices with limited RAM might struggle with larger SoundFont files.
    * File Management: Importing and managing SoundFont files on iOS might require some workarounds.
    Recommendations:
    * If you primarily want to play and customize existing SoundFonts, SoundFont Pro or bs-16i are good options.
    * If you need a SoundFont player that integrates with other music apps, consider the SoundFonts app or bs-16i as an AUv3 plugin.
    * For a simpler option with a focus on recording, JamKoo might be suitable.
    Remember to check the app descriptions and reviews on the App Store to see which one best fits your needs and workflow.

  • DavDav

    Thank you , @McD. That’s some info to go on.

  • Robin2Robin2

    @Dav said:
    Lately I’ve been contemplating sampling a piano. I have access to a beautiful sounding high-end grand piano at one of the upscale communities I gig at, and am toying with the idea of trying to sample it to make a soundfont.

    I’ve watched a few videos on doing it. Are there any tutorials around here using apps like AudioLayer to make a piano virtual instrument? Or if you have any advice for a novice at all on this I’d appreciate it. Talk me out of it if that sounds smarter…

    Thanks!

    It’s quite easy to make your own sfz instruments using Versilian Studio’s ‘Folder to SFZ Converter’ (free). Well worth checking out.

  • rs2000rs2000

    If you want a great sounding and playable instrument in the end, I would highly recommend to prepare for your sampling session in some way.
    From my own experience, these are the questions I would ask myself:

    • Is the piano tuned well?
    • Is it worth to place multiple microphones at different positions, to get different sound characters? (A piano would mean a resounding "yes" to me)
    • How will you record different velocity levels and make sure there are no obvious jumps while playing?
    • How will you cut, name and store your samples before packing them into an SF2, SFZ or whatever?
    • Do you want sympathetic resonances in your piano bank? I did it once in a huge AudioLayer piano and I found it worthwhile
  • DavDav
    edited February 15

    Thank you very much @Robin2 and @rs2000. Thanks for the tips/questions to consider, rs2000. The piano is well maintained and tuned often. I also tune pianos on the side, even slightly out of tune notes I notice. Not fully decided to do this yet, but I will experiment with mic placements and listen to some sample recordings to figure out a good sweet spot. I like the sound of that piano and the environment it’s in. Play gigs on it weekly and can get maybe 1-2 hours a week to record samples. Looking ahead, I’m thinking a SFZ would be the easiest way. But I also have AudioLayer. Is there a particularly good naming method for samples that fits AudioLayer?

  • rs2000rs2000

    @Dav said:
    Thank you very much @Robin2 and @rs2000. Thanks for the tips/questions to consider, rs2000. The piano is well maintained and tuned often. I also tune pianos on the side, even slightly out of tune notes I notice. Not fully decided to do this yet, but I will experiment with mic placements and listen to some sample recordings to figure out a good sweet spot. I like the sound of that piano and the environment it’s in. Play gigs on it weekly and can get maybe 1-2 hours a week to record samples. Looking ahead, I’m thinking a SFZ would be the easiest way. But I also have AudioLayer. Is there a particularly good naming method for samples that fits AudioLayer?

    Sounds good. Since room ambience can be added easily using convolution reverbs and loading IRs from the venue where the piano is, I'd personally prefer a more dry recording so you can have both a lively and an intimate sound character.

    I've written the specs of Audiolayer sample name format a long while ago, but since AudioLayer has been updated several times and the manual seems like a hidden secret, I'll rather link to a slightly more recent thread:
    https://forum.loopypro.com/discussion/49138/audiolayer-sample-name-mapping-issue

    I'd love @VirSyn to update us with the latest information about the exact file name syntax. Thanks! 😃

  • Robin2Robin2
    edited February 15

    @Dav, here’s a video walkthrough of Folder to SFZ. Once you’ve named your files according to the Audiolayer naming convention you should be able to get Folder to SFZ to understand and use the same conventions (using a custom notation directory if necessary) to save you renaming everything.

  • telechargetelecharge

    Here's a good place to start - https://www.macprovideo.com/article/audio-software/understanding-the-architecture-of-sample-based-virtual-instruments

    Then see - https://www.pianobook.co.uk/resources/how-to-sample
    (They use Logic, but it's the process that matters. AudioLayer is compatible with the EXS24 format, though there are some gotchas with it IIRC.)

  • wimwim
    edited February 15

    @Dav said:
    Thank you very much @Robin2 and @rs2000. Thanks for the tips/questions to consider, rs2000. The piano is well maintained and tuned often. I also tune pianos on the side, even slightly out of tune notes I notice. Not fully decided to do this yet, but I will experiment with mic placements and listen to some sample recordings to figure out a good sweet spot. I like the sound of that piano and the environment it’s in. Play gigs on it weekly and can get maybe 1-2 hours a week to record samples. Looking ahead, I’m thinking a SFZ would be the easiest way. But I also have AudioLayer. Is there a particularly good naming method for samples that fits AudioLayer?

    I recommend using AudioLayer's auto sampler to sample an app and create an instrument on your device. The resulting file names should tell you exactly what AudioLayer wants.

    (btw, I recently tried the auto sampler again and found that it didn't work if I had AudioLayer set to use cloud storage. Changing it to local storage fixed that.)

  • DavDav
    edited February 16

    @rs2000, @Robin2, @telecharge, thanks for the links! @wim, thanks a great idea. Thanks.

    I will keep you all posted how it’s coming.

  • rs2000rs2000

    @Dav said:
    @rs2000, @Robin2, @telecharge, thanks for the links! @wim, thanks a great idea. Thanks.

    I will keep you all posted how it’s coming.

    Looking forward to it!
    A little side note regarding the diy sampling recommendations on pianobook: Better forget these immediately if you want a quality piano sound in the end. These might work well for synths but definitely not for a grand piano ;)

Sign In or Register to comment.

© Vanilla Keystone Theme 2025