Another piano font

• Dec 31, 2011 - 17:44

I mentioned in prevous posts that I am always on the lookout for another good piano font. Having combed through lots and lots of candidates, I came to the conclusion that I'd just have to create my own. Using Viena, I've come up with a font that sounds like this:
http://ormusic.home.comcast.net/ThreeLostBodiesCX.mp3

It's rather large (it is about 256Meg, uncompressed; 73Meg, compressed), so you will need a fairly modern computer to make it go. The font retains all of the high frequencies you would expect if you are standing right next to the instrument, so you have to use a tool like Audacity if an alternate acoustical presence is desired. Contact me through my Musescore address if you are interested in the details about this new font.


Comments

I would be interested in hearing how you went about creating the soundfont? I've seen postings here alluding that creating a soundfont with viena is possible, but not many posts describing how one would go about the task. Did you start by making your own recordings or pre-recorded samples? Also am wondering what you found lacking in the candidate soundfonts you tried and what types of decisions/steps were required to come up with this new one?

In reply to by mtherieau

If there's enough interest, I am proposing to create a home for those wishing to discuss SoundFont creation for MuseScore at my webspace.

This is partyl driven by the desire to produce an organ soundfont by sampling the pipe organ where I am Director of Music - I'm ok with the recording side of it, but Viena is one big puzzle atm :)

In reply to by ChurchOrganist

I'm certainly curious about soundfont creation. After searching for soundfonts and how-to's for creating soundfonts, the thing that strikes me is that most of the resources available seem to be...well, shall we say, somewhat dated? I'm wondering why most of these links & resources are almost a decade old?

In reply to by mtherieau

I'll try to answer your questions, but we need to recognize that Musescore is score writing, not music generation software, so this matter is a bit off topic.

“I would be interested in hearing how you went about creating the soundfont?” The Viena software has some instructions about creating a soundfont from scratch, but I found it best to try editing an existing soundfont first, just to get the hang of the software.

“Did you start by making your own recordings or pre-recorded samples?” I started with public-domain sound samples for the new soundfont. However, many of them needed extensive editing to make them conform to the sound I was looking for.

“I am wondering what you found lacking in the candidate soundfonts you tried and what types of decisions/steps were required to come up with this new one?” Almost all of the published soundfonts contain some degree of reverb (some with a lot), and I wanted a sound font without any reverb so it could be added later, if desired. (Note that the sample contains no reverb.) Also, I wanted to have a lot of “splits” on velocity so notes of different loudness really sound different. And I wanted a soundfont that retained the high frequency components of the sounds, just as if you had your head over the strings. If you consider having four velocity splits per note, that is 88*4*2 (the two for stereo), or theoretically 704 splits that have to be defined. However, many of the very high and very low notes can be defined in groups, or are satisfactory with only a couple of velocity splits. This new font is defined with about 450 splits altogether. You can see that a great deal of patience and perseverance are required to get everything ironed out. And there is the complication that Viena is 0.9 version software, so it is a little buggy. So we are talking about a task that involves many, many hours.

Do you still have an unanswered question? Please log in first to post your question.