The Sforzando Sampler


#62

There are not too many SFZ format mappings, because most of the creators of piano libraries here on Pianobook use Kontakt for library creation. It’s understandable, because it’s a de-facto standard and library creation is relatively convenient in Kontakt, since you have a graphical interface to drag and drop sample files available.

That being said: SFZ is a perfectly suitable format and has been used (mostly by non-commercial and small “boutique”) library creators for quite some time now. While you can easily create smaller SFZ libraries using a text editor (see @dhilowitz his video, he showcases an efficient workflow template for SFZ creation) , there are also graphical tools and auto-creation tools (the latter require proper file naming of the recorded and edited samples).

I’m really looking forward to more developers supporting the SFZ format hopefully, since it’s really useful to have if you don’t own Kontakt already.

I don’t really get your point.


#63

I think it just comes down to time. I’ve done a few translations from Kontakt to SFZ, (including Flute+Violin which has yet to make it onto the site), but my harddrive is quite full, and I just don’t need any more pianos (not that I mind creating translations for you all).

I’m basically done with the “Max’s Bentley” that JustLisa et. al. are working on, but I usually upload as a translation, and I believe the official page for that piano has not been created yet.


#64

Cool. My point is that it seems like it would be fairly easy to write a tool to automatically generate an SFZ config file from the underlying assets and given that others have already hand written these files, I’m wondering if I’m missing something or whether I should just go ahead and write the tool.

I’m absolutely new to all of this, so I’m fishing for input before I spend time getting up to speed with the various formats and tools. I think from what I’ve seen so far, it’s at least worth spending a few evenings trying to write such a tool if one doesn’t already exist…


#65

Awesome - I’m not looking for someone to create translations for me, rather I’d like to write a tool that automatically creates SFZ config files from the instrument assets.

I’m new and shiny in this area (composition, virtual instruments, SFZ, DAWs, …), so I’m just trying to get a feel for whether it’s likely to be trickier than it seems.

What might end up being very useful is some guidance with the SFZ format as I get into it…
I’m thinking that I might knock together a very basic tool that just takes an instrument file name stem and creates a simple working SFZ file that just maps the keys to the samples and, assuming that works, start to add support for the optional mappings.

I haven’t got very far yet - I’ve created an SFZ file with a mapping to a single note for a note range, but haven’t managed to get the Plogue player to emit any sound yet, so I might be back on the forums in a few days once I’m clearer on how things work!


#66

If you read further up this thread, One of the posters has such a tool on github (https://github.com/kevinjwalls/CreateSFZ/). Also there is this https://www.bjoernbojahr.de/bjoerns-sample-mapper.html and this https://vis.versilstudios.com/sfzconverter.html and this
https://github.com/sgossner/VCSL/tree/sfz/Scripts

So you might want to have a look at those first. You have probably found the SFZ spec here https://sfzformat.com/

The issue I have had with auto generators is that they are all created with a set of basic underlying assumptions about the sound files they are dealing with. These include naming conventions, offsets, mapping ranges, etc. Generally, the creators of pianobook sample sets have not done so with an SFZ auto-generator in mind.

Since my goal when creating a translation is to be able to drop the SFZ file into the folder of the original without changing anything else, and to get as close as possible to the intent of the creator of the original, I have found auto-generators to be of limited value when working with sample sets not created with an auto-generator in mind. I have found a good text editor to be faster.

So with all that in mind, I look forward to anything you come up with in this area. I’m happy to test anything and bounce ideas around.


#67

Ah, interesting.
I had assumed that the assets in pianobook samples were consistent in their layout.
I suspect that if others have worked on conversion utilities, I’m unlikely to add much beyond what’s already supported. I’ll definitely check out the projects you linked.

Thanks for the response - very useful (and will save me a lot of needless digging around!).


#68

Yes, I doubt there is currently a need for another conversion / auto-mapping tool. As @Sid correctly mentioned, already a number of such tools have been mentioned in this thread.

Another one that has been mentioned before on the forum: https://www.polyphone-soundfonts.com/en/

If you want to help and encourage the creation of SFZ libraries, you could make an in-depth check of the pros and cons of the various available tool and post your conclusions and experiences in a seperate thread on the forum. This could help those who want to create SFZ mappings to streamline the creation process.

We don’t have to reinvent the wheel. Again, I will highly recommend you the video that explains the basics of creating a SFZ mapping. After watching it, you shouldn’t struggle with creating a basic mapping in a text editor. It’s quite easy actually. https://www.youtube.com/watch?v=gmTmy6Byx6g