Help us improve the sounds in MuseScore

• Feb 27, 2018 - 17:33

Hello fellow MuseScorers! This is S. Christian Collins, virtual instrument designer and creator of the GeneralUser GS SoundFont. I have been asked by MuseScore to make some major upgrades to the default SoundFont for the next version of MuseScore (and beyond).

My goals for the new SoundFont include:
1. Improve the quality of the instrument sounds, starting with those most frequently used in scoring.
2. Address known issues with the current SoundFont, including notes that are out of tune, and the extreme volume difference between PP and FF dynamics.
3. Only freely-licensed samples will be used (e.g., MIT, CC0, CC-BY)

The plan is to gradually replace the instruments from the current FluidR3Mono SoundFont with higher quality samples and better programming. Instruments that continue to use FluidR3 samples will be updated to scale better with velocity changes (both volume and tone).

Development versions of the SoundFont will be shared on this forum to get feedback from the community regarding any changes we might make. I would like to avoid any functional regressions with the new sounds.

Ways that you can help:
1. Testing: Test out the instruments as they are developed, and let me know of any problems you encounter.
2. Create / Suggest Instrument Samples: One of the problems with using only free samples is that the available options can vary widely in quality. I will be posting to this message board with requests for samples as they are needed. We already have one generous user (ericfontainejazz) who has offered to record his saxophones.

I cannot guarantee that we will be able to use every sample we are sent. For every user-submitted sample included in the new SoundFonts, those users will be credited in the documentation that will accompany the release of the new SoundFont. The new SoundFont will published under a CC-BY-SA license, but many of the contained instruments will be usable under a less restrictive license. This licensing has no bearing on scores or recordings made with MuseScore, but only applies to those who want to redistribute the samples in some way. We are encouraging users to submit their samples under the CC0 license so that we can make as much of this "culturally free" as possible.

I will be posting a new SoundFont for you to try very soon, so keep your eye on this thread. I am very excited to be able to work with MuseScore--a project that I have long been passionate about--and I look forward to working with all of you along the way!


In reply to by s.chriscollins

That's what i am looking for : per-note expression !
and, is it possible to add the spiccato channel for strings in the instruments.xml distributed file ?
are ther plans to add more channels by default also for timpani (tremolo (roll)) ? all are in VSCO2 CE samples.
Thank you for your work.

In reply to by brouits

It is possible to modify the amount of channels for an instrument in that file, but personally I find it tedious. This was my struggle with that but I found that you can't program another channel to have an extra sound from, say an extra soundfont listed after whatever GM soundfont you're using. I don't think spiccato is any of the 128 OG midi sounds so that might not work right now. But hopefully these new extension packs will allow us to change the xml files with ease when they come. I'm not sure about more channels by default. Maybe Marc Sabatella or lasconic would have those plans.

In reply to by fernandoamartin

Nice :) When I implement legato, I plan to use a modulator to adjust note attack & sample offset in response to a MIDI Control Change (e.g., CC21), so separate presets won't be necessary. Then we can have MuseScore send CC21=127 when under a slur (except for the first note) for a more natural legato, and CC21=0 when outside a slur for normal note attacks.

In reply to by s.chriscollins

That's a very nice idea! You say "I implement legato". Are you a developer? If Musescore could play legato automatically under every slur that would be wonderful. In default midi, attack controller is on bank 73. But changing the attack time right to 127 may have an unpleasant effect and fast passages may become hard to hear, depending on the attack of the original samples.
When I use Rosegarden I move attack controller from 64 (the default value) to 74 or 84, depending on the soundfont I use.
When you implement legato, can you, please, leave an option where we could set different attack values for different staves?

In reply to by fernandoamartin

Yes, I am a developer working on the SoundFont. A convincing legato will be more about the use of sample offset than note attack speed, so it might not be possible for the attack to be user adjustable without creating undesirable side effects. My goal would be to get the legato behavior good enough that users wouldn't need to bother with adjusting it manually.

In reply to by s.chriscollins

While I ask about this here, I thought I might as well pitch another request I have. Let's say you load 'strings' in as an instrument (with the grand staff and using soundfont patch strings fast). When I set the strings to pianissimo, I find that it feels (or sounds to me) more like the upper strings are playing at a mezzo forte and the celli and basses are playing the desired dynamic. May it be readjusted? I'm not sure if this sort of thing would be a difficult modification, or if you're planning on readjusting levels on everything later (although this is the only patch I've found be less to my personal preferences) but if you could consider looking at that when you have time, I'd be grateful. [Also I'm not sure if I have the latest version of this or not, so it may be something you've already done [Considering I'm using musescore general full from late december]

Now my question about the legato...

So, would you have different legato settings for different types of instruments (in a way that would make more convincing legatos for most soundfonts of a given instrument (or family), or maybe just for this soundfont) or is it planned to be one size fits all legato for the whole soundfont player?

Thanks! really appreciating the work you've been putting into this

In reply to by s.chriscollins

I don't understand fully how it's going to work but I hope you succeed. When you implement this, please, let us know. (Currently I have been writing for keyboard instruments only because no matter how realistic soundfonts are I can't reach a convincing legato.) That feature will be very helpful.

Is there a way to hear or have play back scoops and gliss and fall offs. Also a better way to notate them such as like sqwigally line for a fall off like in jazz music. Another thing I would love to be fixed is A way for play back with sfz, and Fp and etc. where it should hit hard and get soft and then crescendo up. I have tried to do this with dynamic and crescendo markings but it doesn’t do this with the play back. And lastly just dynamics play back needs to be better there are drastic differences then subtle depending on certain instruments and almost no changes on others causing me to sometimes have to have multiple dynamics in 1-2 measures to get the desired playback sound for MP3 files. Then have to go back and change them to have it look professionally correct to print the music off. Also with play back some instruments can not be heard at all or will get drowned out from the mass of the rest of the ensemble despite turning volume up on the mixer. For example the mellophones in my marching band music can’t be heard that I have them turned all the way up on th mixer and have them on FFF dynamic wise and their part tends to be covered or hard to hear and in reality that’s a very audible instrument in marching band. I’ve even tried playing with the pan options and reverb and chord options and it still isn’t quite heard. But just a few of my observations I’m sure you will give everything you do your best. And good luck to you and thank you for doing this.

In reply to by devon.mcdonald.779

You can fudge the dynamics by using the inspector to change the velocity values for that symbol, so that you can have the correct symbol for print-off but with the velocity adjusted to give the best available balance for the .mp3 rendering. You can also introduce additional "invisible" dynamics as may be needed for the playback, but again using the inspector to mark them "not visible" (they will be grayed out on screen).

I agree, the lack of dynamic modulation on individual notes is a major shortcoming of MS's synthesis model. You can try to fake it by using multiple notes, but each note may then sound with a separate attack. It works on tympani rolls using tremolo, breaking the rolled note up into shorter notes. Then you can use two voices - one for playback with the notes set "not visible", the other for print-off and marked "do not play".

I've been seeing more about 3.0 lately so I was wondering if this soundfont is still under development (more like making sure haha). I haven't seen any news about it in a while, but I'm still looking forward to it, whenever it comes.

In reply to by speedmeteor101

The SoundFont development took a back seat for a bit while I created the MuseScore DrumLine (available through Help -> Resource Manager). I'm also in the process of moving to a new home, so after that, development will pick up again. Thank you all for your patience!

A new version of MuseScore_General will be coming out soon that will feature fixes to reported issues (e.g., out of tune choir) and updated marching percussion sounds backported from MuseScore DrumLine. This will be followed by some delicious new ensemble strings with individual Violins, Violas, etc.

In reply to by s.chriscollins

The marching snare has never worked. I have musescore installed on Windows and Linux and it works in neither case. I do hope this gets fixed.

Sounds aside, one of the worst problems is not particularly with the single basic soundfont, but the synthesiser. It has the capacity to add soundfonts alongside the pre-installed one (which is VERY necessary for particular tailoring of output, but the handling of these is frankly atrocious.
They all end up in one giant, unwieldy list which turns your brain to mush when trying to find things. Plus setting the order via the arrows is slower than watching paint dry and makes my i7 (yes really!) with 16GB of RAM unresponsive. That should not be happening.

Every time an update arrives it just wipes out all those soundfonts leaving a carefully constructed score playing a bank of 'grand pianos'. It's impossible. To counter this I have to run up scores on a laptop not connected to the internet with an untouched copy of Musescore and instruments.

The support for sfz files via zerberus is generally problematic. Having these loaded into zerberus drastically delays startup and on linux causes me to have to restart again before any scores will even play.
I posted this to musescore forum some time ago, but the two permanent, voluntary oracles there, whose knee-jerk response is to ask for files, don't realise that almost everyone personalises musescore and, importantly, by using the features intended for doing so; or they wouldn't be there for that purpose. I admit I gave up on that forum because of this issue.

I see it thus: musescore is designed primarily for use with one, single soundfont bank, which is not, and never has been, satisfactory for a good number of users. Many improvements have been made (some regressions). With that design the ability add further soundbanks appears as an afterthought. Some more ability to organise these soundbanks would be greatly appreciated.

In reply to by Roger v.d Velde

Marching snare should work fine in the default soundfont, it certainly does for me. Probably the issue is with some non-standard customization you have done, either via a template, a style file, a drumset definition, or your instruments.xml. In order to assist you better, please start a new thread and attach a sample score to demonstrate the problem you are having, and we can go from there.

In reply to by Roger v.d Velde

Absent a specific example, my guess is that you are being fooled by the normalization that is applied. That is, MuseScore is probably applying the soundfont just fine and using the pianissimo sample correctly, but if there is no louder passage in the score to set a peak level, then the exported mp3 is getting its peak from "pp". This is, well, normal, as it is consistent with how audio is ordinarily produced, but if you need a quieter mp3, you can always reduce the volume in an audio editor.

In reply to by Marc Sabatella

Your unwavering belief in the total infallibility of musescore's operation is admirable, but misguided. Using regular sf2 violins, which are more stable, but inferior-sounding, the dynamics can be exported perfectly fine. If you take the trouble to see what is said about the support for sfz in the musescore user-guide you'll see that it is only supported as an afterthought, not as a stable system. The dynamics applied in the score do not export. Unless you've actually tried this you cannot know and can't have a useful opinion regarding it.

Having it as an option under those circumstances is frustrating. It's like being told you can bring your own sandwiches to a concert, only to find you have to eat them in the toilets. You may feel that I am rather brusque when addressing you, but the only issue is that you seem to think that attaching sample scores is somehow the solution to every issue. It may be for some, but issues like limited support for sfz, it most certainly isn't. Someone at musescore central - and you yourself if you care to - could try it out and figure out the problem. That, after all, is what the software developers there are meant to be doing right? Or is partially-functioning software okay now?

In reply to by Roger v.d Velde

Actually, I've fixed enough bugs in MuseScore to know very well it is anything but infallible. But I've also helped enough users here in the forum to know that often people are just confused about how things work. And the particular issue of dynamic / audio normalization is one that does sometimes catch users by surprise.

So, as I said, absent a specific score and steps to reproduce a perceived problem, it's hard to know if there is a bug or just a point of confusion. So we are limited to just guessing based on prior experience. And since export of dynamics work fine for me whether using SF2 or SFZ, and I've heard enough examples from others to know it seems to work fine in general, and this normalization thing is a pretty common misunderstanding, I made my best guess.

Now, I'd much rather fix problems and/or truly help people than guess. Which is why I am so often encouraging people to provide the sort of additional information we'd need in order to do either.

So, again, if you believe there is a problem here, I'd love to help. Which is why I continue to urge you to post to an appropriate thread (eg, the one you started some time ago) with the requested info - a sample score and precise steps to reproduce the problem. Because I have tried it, and it does work fine in general. I even tried it again just now, and it worked as it always has.

BTW, while it is true than in older releases SFZ support was limited (to just what was needed for the Salamander piano), this has improved gradually since then to the point where we now can do considerably more with SFZ than we can with SF2.

In reply to by Marc Sabatella

The 'customer service' tone is quite annoying. the problem isn't 'perceived' or one I 'believe' I have, it is a reality. There is no 'confusion'; not from me at least. Please stop asking for a sample score, you don't need it, it will do you no good.

I will however post to another thread and conduct my own survey concerning dynamics applied to sfz instruments specifically - and the ones in question - and their output to mp3. I would like to see if, and how many, other people actually have a similar issue. Perhaps these people will also be able to offer some useful insight into it rather than asking for sample scores.

In reply to by Roger v.d Velde

If the developers can't reproduce the problem, how do you expect them to fix it? If they had a copy of the problematic score, perhaps they might be able to trigger the bug and find out what is going wrong. Also, if you haven't already, you should report this bug on the issue tracker:

The developers will want to know info about your system (OS, MuseScore version), etc. to hopefully help narrow down the problem.

In reply to by s.chriscollins

They can easily reproduce the problem by running a clean copy of musescore like I did, with only the solo strings from virtual orchestra added alongside the standard soundfont then applying dynamics and seeing if they output to mp3. Very, very simple. I've set it out several times in plain English.

I don't see what's difficult to understand about this.

In reply to by Roger v.d Velde

The difficulty, again, is that we have done this many times, and it works fine for us and for everyone else. In order to understand what is different in your case, we really do need your help, as we quite simply have been unable to reproduce any sort of problem. So thanks for starting the new thread where we can discuss this issue further.

BTW, note I didn't say you were confused, I said many users do find this normalization to be confusing. I'm glad you understand it, though!

In reply to by Roger v.d Velde

Roger, thought I would jump in here and help to clarify a few things.

Historically, the priority of the MuseScore development team has been to create an incredible solution for engraving. MuseScore does allow you to create beautiful scores for print and MuseScore 3.0 will do this even better and faster, with some great auto-layout capabilities.

Now that the software is becoming much more mature and capable, and now that there are many additional resources available, playback is becoming much more of a priority.

The current playback limitations are not only well known, but very clearly defined, and there is a plan to continue to expand this capability as we move forward.

To address the issue of SFZ playback, specifically, Zerberus currently supports a very limited number of opcodes in the SFZ spec. Many new ones were added since 2.1 and many more will continue to be added in the future. As additional opcodes are added, this changes the way MuseScore is able to essentially "drive" the specific soundfont.

As each unique soundfont may utilize different SFZ opcodes, a very wide range is needed to support more than the most basic aspects of SFZ (ex: to utilize the full range of expression/articulations for strings could require supporting a considerable number of opcodes).

In addition to this, performance is also greatly affected by the ability to support disk streaming vs. storing all samples in memory. This is also something planned to be addressed in the near future.

Specific SFZ opcodes currently supported in Zerberus vs. Linux Sampler or Aria Engine -…

The next wave of improvements in SFZ support will be for opcodes that will specifically expand capabilities for percussion, as this is a near-term priority. Many of these improvements may also be relevant to supporting other publicly or commercially available SFZs.

The most constructive way to get involved and the most productive way to encourage support for specific SFZs is to identify the specific opcodes required that are not currently supported and make a feature request to add specific support.

Here are examples of what those might look like:

In reply to by Daniel

Not to qualify the compliment I want to give to those responsible for MuseScore_Generalsf3, but I freely admit I am new to soundfonts, notation software,extensions,imports and all the rest which trifles with my sanity, but I have been in music for 5 decades and know sound. These fonts are much better than I expected. For my own work I have explored many sounds. For classical music brands like Vienna Symphonic seem to stand out. There are others which seem to be popular with film score fans, but these are lacking in bringing forth the relatively more subtle string techniques found in classical writing. All brands seem to have serious limitations (thus far). However, with my limited experience, I still feel yours stand out. Now,I have yet to have utilized MuseScore fonts for symphony orchestra having not scored here for more than 15 parts. So my observation is limited.... I'm sure others will differ.

I'll offer a few examples. I've just completed a song cylce which I've played back. The piano sounds like a piano. The dynamics and articulations work out. (The lows are penetrating.) The voice (mezzo) sufficed, though "she" was flat on high sustained notes, which rather makes the composer reach for the aspirin. (on the few notes just below middle C, she becomes a he.)
A ballet score is almost completed, one for 6 players. The sounds are fine with some suggestions I'll note. Once I played with the mixer, to distribute the instruments as they would be in the stage/pit setting, the playback was true.

The suggestions, which I'm sure you are aware of: Straight (and other) mutes for brass.
I've already mentioned the voice tuning.The marcato attacks of winds and brass could be sharper, especially the trombone. While the clarinet's chalameau is awesome, the upper register lacks some of the brilliance one would expect from a f or ff passage. The flute is perfectly malleable and the breathy lows surprised me. Of course, during slow, long notes the vibrato does wobble a bit, but I realize it is engineered sound.
The violin surprised me, too. The legatos are fine. As with all string attacks in fast passages, they are not as clear as we would like. I also noticed that during passages where the violin is solo, the sound is true, but when other instruments join in there is sometimes that "sameness" sound which I've noticed in MIDI instruments, as though it takes on the character of others. Of course it is difficult to temper the high notes (harmonics) to keep them at a pp.

I do not know how you reproduce these sounds, but I think your efforts pay off handsomely.
There is a particular joy for a composer to hear a work not yet performed played back with virtual fidelity. And I realize improvements are forthcoming.

And, like the MuseScore notation's free.


The new MuseScore_General soundfont version 0.1.3 has now arrived in Debian unstable and the official PPA.

The soundfont is now split into two, the normal MuseScore_General (musescore-general-soundfont in Debian) which has become even cooler, even more featureful, with not just the new piano (from 0.1.1) but also new strings, and, more importantly, ensemble strings (to avoid the sample doubling effect)… unfortunately this means it’s now about four times the size the old Fluid (R3) Mono soundfont (fluidr3mono-gm-soundfont) was, so there’s now also a MuseScore_General_Lite (musescore-general-soundfont-small) which has comparable sizes (on-disc and, more importantly, in RAM and startup times) to Fluid (a bit smaller actually) while being of the same quality of the full-featured font, carrying the same presets, banks, etc. — the difference is that the light version does not actually ship distinct samples for the ensembles (so second violins sound exactly the same as first violins), and that it uses the piano and string samples from Fluid, not the new ones.

However, the light soundfont contains all the improvements (such as the Choir Aahs and some other instruments being slightly better in-tune) from the full soundfont, and the Fluid piano and strings also got improved. Furthermore, the MuseScore_General soundfont contains some stereo samples (yes, even the light version, which is impressive, as it’s smaller than Fluid (R3) Mono which was made mono to save space).

I’ve created the Debian packages (all three of them: Fluid and the two MuseScore_General ones) in a way that makes them installable on all kinds of Debian-based distributions, even positively ancient ones, so feel free to install them. (Do not, however, install packages from one distribution or version on another normally, and especially do not use the PPA on Debian. The soundfont packages are the only exception, because they basically only ship data.)

Non-Debian-Linux users can go to and download the individual soundfonts for a sneak preview. Symlink or copy either of the three to MuseScore_General.sf3 (in /usr/share/sounds/sf3/ on Debian, /usr/share/mscore-2.3/sound/ on stock installations) to use it as default soundfont.

In reply to by mirabilos

Thank you!

This sounds good, but...

Can I install on my ver. 2.3.2? I saw a few unpleasant words in the description like "unstable" and in the PPA like "unsupported" and "untrusted"....and, of course, I have no idea what "debian" means.

But I would like a mezzo (choir aahs), etc, who stays in tune on high notes and a string ensemble, etc...

Also...would the new MuseScore general replace the old so the old should be deleted from the synth?

In reply to by penne vodka

OK, let me walk you through a few of the “scary words”:

“Debian” is a kind of Linux. It has a “staging area” called “unstable”, in which packages get uploaded and stay there for a couple of days, until they migrate to “testing”, which is what will eventually be the next “stable”. This is mostly a process depending on time, and new stuff always goes to “unstable” even if it is stable, it will just migrate smoothly; this gives users the chance to test and report bugs. (This has no bearing on the soundfont, more on real software).

So, yes, you can download and use this on your version 2.3.2 — if you want the full experience, just go to and download the MuseScore_General_Full.sf3 file.

Then copy that into your MuseScore sounds directory as MuseScore_General.sf3 replacing the old one. This way, you will not have to change anything in the synth; it’s a drop-in replacement.

In reply to by mirabilos

By suggestion of S. Christian Collins, the SF2 of the full soundfont is now also included. It’s huge, but it completely eliminates the long startup times and possible audio compression artefacts. This is now also in Debian (as musescore-general-soundfont-lossless); I’ll update the PPA later.

The musescore-general-soundfont-small package also finally entered Debian today, so we can have these in backports in another fortnight or so (plus backports-NEW queue waiting time).

In reply to by penne vodka

I think it's always possible to use the former soundfont from here: (or should be possible).
I don't think the updated soundfont is available with the actual release or actual nightly at present (I didn't check it, but I don't see a difference concerning the size of the file) - maybe in future. And I can confirm, that I don't notice a long startup with the actual soundfont so far.

In reply to by kuwitt

@penne vodka: the SF2 is the same as the SF3, except for three things:

  1. It takes up about six times as much disc space (almost ½ GiB)
  2. It makes MuseScore start up instantly, instead of having to wait for sample decompression
  3. It avoids compression artefacts that some audiophiles may hear

So, for the average user, they want the SF2 if the SF3 makes MuseScore too slow to start for them, or the MuseScore_General_Lite.sf3 (1/20th the size of the SF2!) if they have small hard discs, but the Lite one lacks the new piano and strings.

@kuwitt: This is version 0.1.3 of MS_General; the page you link has only version 0.1.1 which lacks the new strings, but also many bugfixes, such as slightly less out of tune instruments and choir, and other improvements.

Yes, it’s true that the MuseScore 3.0 release ships with the older soundfont. That’s why I’m uploading the latest soundfont at in the first place, so users can get it if they want.

In reply to by mirabilos

I'm using the 2.3.2 rev 4592407 AppImage in Linux Mint. When I view the Fluid tab in the synthesizer, it tells me MuseScore_General.sf3 is being used. My question is: is this the 0.1.1 0r the 0.1.3? Is there a way to tell? I can't see inside the AppImage file to get the size of the .sf3 file. Or does it even matter?

You say that "the MuseScore 3.0 release ships with the older soundfont" - does "older" refer to 0.1.1 as opposed to 0.1.3?

In reply to by mirabilos

I’ve updated the site with the latest soundfonts:

  • FluidR3Mono_GM.sf3 is (still, unchanged) fluidr3mono-gm-soundfont version 2.315-5, SF3 compressed (lossily)
  • MuseScore_General_Full.sf2 is now musescore-general-soundfont version 0.1.7-1, upstream name MuseScore_General_HQ, SF2 uncompressed (lossless)
  • MuseScore_General_Full.sf3 is now musescore-general-soundfont version 0.1.7-1, upstream name MuseScore_General_HQ, SF3 compressed (lossily)
  • MuseScore_General_Lite.sf3 is now musescore-general-soundfont-small version 0.1.6-1, upstream name MuseScore_General, SF3 compressed (lossily)

The *.copyright files can easily be mapped by the Debian package names shown above. The individual soundfonts also contain full version and copyright information thanks to a small script I wrote that patches the RIFF INFO chunks at package build time. (Do remember that, while, as it comes under the MIT licence, it can be used in most settings, waveforms generated using this soundfont are “copies or substantial portions of the” soundfont.)

Important: MuseScore_General_Full now maps to MuseScore_General_HQ, the old “MS_General”. This is now an optional download for MuseScore otherwise. MuseScore 3.1 will ship with the newly-renamed MuseScore_General, formerly MuseScore_General_Lite, by default. (However, due to package naming and other constraints, Debian users will, by default, get the SF3 version of the HQ soundfont, unless they already have a suitable soundfont installed. I could only change this by shuffling things around I’d rather not touch, plus we’re in deep freeze and about to release the next Debian stable 10 (“buster”) any moment, so I refuse to follow this latest renaming.)

It should be noted that Debian 10 will not contain these new versions of the soundfont (but I’ll most likely provide them via backports), as it’s simply too late to bring in a new upstream version (Debian stable release policy). I am currently updating the PPAs, though.

I'm a jazz drummer and noticed that I can't create any scores which use sweeping brushes - there is just no percussion font that includes that. It is very common instrument for slow ballads and tunes. I'm very surprised no one notices this, I'm guessing it's because vast majority of MuseScore users are classical musicians.

I did create sound brushes samples using my drum kit and incorporated it into standard .sf2 font
supplied with MuseScore. I have ability to record samples and willing to provide them to your team for free to all's benefit (I think it's CC0 license).

If MuseScore team is interested getting this flavor of percussion into the soundfont, let me know what do I need to do. At this point I just have sound samples. If there are special requirements to record them, I'd like to read more on this (provided, currently lacking sustained brushes sound is something desired/needed for updated MuseScore fonts, else if there is no plan to consider this, it's just waste of time recording them).

Please let me know!


In reply to by VT

Hi Victor. Thanks for offering to help out with this! As you may have noticed, the FluidR3 brush samples in MuseScore_General.sf3 sound very little like brushes. The sample for "Brush Kit" MIDI note 40 (brush swirl) sounds more like a hit than a swirl, and MIDI note 38 (brush tap) and 39 (brush slap) sound more like stick hits than brushes.

I would be interested to hear the samples you have created. The CC0 license would be perfect. Ideally, we would like to have the following samples at soft, medium and loud dynamic levels to replace the current brush kit, but we might be able to make good use of what you've already recorded:

  • Snare Brush swirl (single) - a single swirl of the brush. If you can get multiple samples of this at each dynamic level, that will allow us to potentially use round-robin to keep the sound from being too static. Optionally, also record a sustained swirl pattern at a slow tempo, and I might be able to chop it up for round-robin sample triggering.
  • Snare Brush stir (sustained) - I can create a loop. Try to avoid rhythmically pulsing the swirl so that it will work at all tempi.
  • Snare Brush tap - produced by making a quick down-up stroke, playing off the drum head.
  • Snare Brush slap - produced by playing the brush flat, striking down into the drum head
  • Hi, mid and low toms - brush hits on all tom toms
  • Cymbals - if possible, brush hits on crash, ride and hi-hat cymbals along with a sample of closing the hi-hat with the foot pedal

The most important of these would be the snare samples, but it would be nice to have toms and cymbals as well to complete the set.

Another thing to consider in all of this is the way that brush "stirring" is typically notated. If I recall, often text such as "stir continuously with left hand" or simply "stir" will appear over the drum staff. I'm guessing that in MuseScore, one would need to enter and then hide notes to trigger the stir/swirl samples, as there is no system in place that can create an automatic stirring effect with rhythmic, BPM-synced circular motion. Being that you are a jazz drummer, perhaps you could shed some more light on brush notation conventions, as my own drumming experience doesn't feature much jazz.

In reply to by s.chriscollins

Hi Chris, sorry for delay with this. I've recorded a few samples of brush sounds. How do I submit the file to you? It's 5.9 MB file in .mp3 format, OK for an email attachment or I can upload it to any specified location. I'll provide more details about the sounds in a readme file sent together with it.

So please let me know what do you want me to do next, how to proceed at this point.


In reply to by VT

Excellent! Do you have the audio in WAV or FLAC format rather than MP3? I'd like to avoid the lossy compression if possible. E-mail attachment should be fine. If the WAV/FLAC is too large for e-mail attachment, do you have a Google Drive or Dropbox account to upload it to?

In reply to by s.chriscollins

I got original .wav file, it's recorded at 48kHz bitrate 24 bit resolution by Zoom Q2n recorder. I don't have a dropbox ir google drive account, I suppose I can create one, but then I have to send you credentials to grab the file, do I? Sorry, never had need to use these tools, so don't know much about how this works in detail.

In reply to by Louis Cloete

Also, both Dropbox and Google drive offer the ability to share the file with another person. You won't need to give your credentials for me to access the files, just a sharing link/e-mail. Both services offer enough storage space for free for you to be able to share large files, and you can always delete the files from the service after the person you are sending them to has downloaded them, which will free up space for other files in the future.

In reply to by shoogle

I found the original poster of the soundfont, he sampled his own instrument and posted it for free in his site and on a facebook group but it has no particular licence i think, if you write to him he will surely allow its use for musescore. The soundfont is great, its better than many paid vsts out there.… (this is where it was originally posted) (this is the posters personal facebook page)

In reply to by Federico Butera

People are very busy these days, so it's worth sending another message just in case he missed the first one, or saw it and forgot to reply. Just say something along the lines of "Hi, I was just wondering if you saw my first message about licensing your soundfont for use in open source programs like MuseScore? Doing so takes minimal effort on your part and it would make a lot of people very happy, but it's totally up to you and I understand if you don't want to.".

In reply to by Federico Butera


I fear you explained it wrong. CC0 does also allow usos comerciales, and it means the author gives up the right to collect money for it, it does not prohibit others from doing so.

Judging from the answer, though, Adrian seems to only be interested in people just using it without annoying him, so… it’s a very weak permit.

In reply to by mirabilos

I don't think this is correct. Under CC0, the author still could make money off of it if he wanted to, but so could anybody else. It's essentially in the public domain, and anybody can use it pretty much however they please, except to restrict others from doing so.

In reply to by Federico Butera

I see, i dont see how anyone would spend money on something on public domain they could get for free... Except they want to donate or something, i didnt say commercial use is prohibited. I can write back to him but as you can see its unlikely i even get an "ok" as answer. If this permit doesnt do it i think thats it. Maybe you can list it in the soundfonts page as alternative third party soundfont.

In reply to by Federico Butera

A better idea is to pick a license for him (e.g. CC0) and say:

Sorry but we need you to explicitly place it under one license or another. What about CC0? This will allow MuseScore (or indeed anyone) to ship it for free. Full terms are at If you are happy with this, all you need to do is type "I release this soundfont under CC0" and then we can use it. Thanks!

In reply to by mirabilos

A concise way to explain CC0 in simple terms is that it releases the creative work to the world to use without restriction. Many SoundFont designers essentially are intending to do this with the samples they share--they simply don't care what people do with them. This will often be evident in the language they use when sharing it, or they will say it is "public domain". Having a sound designer agree to use CC0 makes these terms unambiguous, and we can avoid any misunderstandings down the road. In addition, we credit all known SoundFont contributors in the documentation accompanying MuseScore_General, even though this is not a requirement of the CC0 license.

Here is version 0.1.4 of MuseScore_General. Please note that I have changed the bank assignments for the new ensemble strings. This affects all ensemble Violas, Celli, and Basses presets. Any scores using these strings with version 0.1.3 will need to re-assign the presets in the mixer upon switching to 0.1.4. I apologize for the inconvenience. This was done to better accommodate future expansion, such as the upcoming "expressive" presets that support single-note cresc. and dim.

Features of this release:
* Fixes the following issues: #281732, #280907, #280904, and #272992.
* Improved the dynamic response of the acoustic pianos.
* Re-numbered ensemble strings bank numbers to make room for future expansion.

In reply to by s.chriscollins

Thanks very much! I had a quick listen and it sounds great!

Forgive my ignorance, but could you please confirm or refute the following statements:

  1. Your soundfont (MSG 1.4) preserves the distinction between singular (solo) and plural (ensemble) instruments (i.e. "viola" uses a different sound to "violas").

  2. You added new instruments, but all of the old instruments are still included, and are in the order prescribed by the General MIDI standard.

  3. If we stick to using the old instruments then our scores will render as expected with any soundfont, but we are limited to what is specified in General MIDI (i.e. we must use generic "Strings" instead of "Violas").

  4. If we "opt-in" to using the new instruments (such as the separate sounds for Violas, Celli and Basses) then we gain better sound with your soundfont, but we lose compatibility with other soundfonts. (I understand that this is inevitable because those instruments do not appear in the General MIDI standard).

Is there any agreed (or de facto) standard for instruments beyond those defined in General MIDI?

Edit: so those are pretty basic requirements and having checked a second time I see that they are indeed all true. I must have done something weird the first time around because it looked like some of them were not true, hence I felt it necessary to ask.

In reply to by shoogle

All are true except for #4. If you use any of the new ensembles (Violins Fast, Violas Slow, etc.), they will render according to GM bank fallback when using a different SoundFont.

Let me explain how this works. All of the "fast" string section presets, for example, are on different banks but using the same preset number, which is 48. Currently it looks like this (bank:preset):

000:048 Strings Fast
020:048 Violins Fast
025:048 Violins2 Fast
030:048 Violas Fast

If MuseScore tries to play 020:048 (Violins Fast), but that preset is not in the SoundFont, it will instead play using 000:048 (Strings Fast in GM standard). This of course also applies to the ensemble instruments using presets 44 (Strings Tremolo), 45 (Strings Pizzicato) and 49 (Strings Slow).

It is in this way that the new instrument sounds will be backwards-compatible with other GM banks.

In reply to by s.chriscollins

The highest bank number is 48 in the Roland's Sound-Canvas bank list.
For this reason, it's better to start the banks from the 60th number (instead of 20th).
Otherwise, banks 20., ..., 30., ..., 40., ... in other sound-fonts, will clash with the sounds in the MS-General's banks.
It's also not possible to replace the already existing banks with new ones in other sound-fonts (Because we can only do a two-dimensional definitions: bank-number:preset-number.)
I think: Bank 60 and above is ideal.

Some examples:
020:48 Orhestra4 *
024:48 Velo Strings
032:48 OctStrings1
033:48 OctStrings2
034:48 Contrabass Sect.
040:48 60s Strings *

024:50 Tron Strings
025:50 Noiz Strings *

024:52 Chorus Lahs
032:52 Chorus Aahs
033:52 Male Aah+Str

020:53 to 40:53 Voice Oohs variations * * (eg: 20:53*, 40:53*)
00:56 to 32:56 Trumpet variations (eg: 025:56 Warm Trumpet *)

Including Brass, Pan Flute, Synth Lead, Saw Wave variations and more.

In reply to by s.chriscollins


I'm curious of what samples you'll be using for the solo strings. For violin I actually like the idk1609 samples that were posted for free by the user... and were actually used in the Alpine violin set. (Although the attack isn't the greatest on notes around middle C). I haven't really explored other samples, but a lot of cellos sound decent in my opinion and there's always a good bass out there. (I don't really know how a good viola sounds hahaha)

As for other specific ones, I don't have any in mind. I know that with the current solo violin in 1.4 and with aaviolin for example, that there are some overtones/ frequencies in there that just irk me a bit as they sound either too electronic, or too wet, or... well I think you get it. I have FL studio, so I was experimenting with the parametric EQ 2 (to target the freqs) and Maximus (compression), and actually did see strong improvement with the samples tone-wise. However, I'm no sound engineer so I don't know exactly what to look for to get it just right.

Even though I was applying it to the whole soundfont through the soundfont player/ mixer, I was thinking the same could be done for the samples themselves to build even more on the soundfont. I'm not sure if you do equalization and compression or if you know anyone who does, but I think it could GREATLY help the tone quality of the samples just from my experimentation to add even more.. I guess I wouldn't say realism but... [insert word] to the soundfont.

You've done amazing work with everything so far, and honestly I don't know if you've been doing this already, but I just wanted to let you know what I found through this experimentation.

Sample rate

Which sample rate do the individual samples use? Is it the same for all of them, or do they all differ, and if so, do they have a common divisor (e.g. 22050 and 44100) or not (e.g. 44100 and 48000), and what’s the most common sample rate?

Or perhaps: would it make sense to add a “sample rate” column to the CSV table listing the sample sources? Assuming that, at the very least, within one instrument the sample rate does not differ.

I’m asking because I just noticed that MuseScore offers changing the output sample rate at two places, and that they have different defaults: playing on the speaker from the application defaults to 48 kHz (with ALSA), while MP3 export defaults to 44100 Hz… (and WAV, FLAC, OGG Vorbis export either uses what is configured for MP3 or is not configurable at all?)

I assume it would be best to use the same sample rate for the output that my input samples have (with the table, I could see what the instruments my score uses have).

In reply to by mirabilos

There are different sample rates used within the SoundFont, most commonly 22050, 32000 and 44100, but others exist as well, including a handful at 48000. You won't gain anything by attempting to match output rate to sample rate, though, since samples are frequently not played at their recorded pitch anyway. Most instruments use a single sample to span more than one note, and only one of the pitches in that span will actually play at 44100 Hz (assuming it isn't also fine-tuned within the instrument). Fluidsynth's high quality interpolation avoids any aliasing effects from these sample rate changes. As long as your output sample rate is sufficiently high (44100 Hz or higher), it should all sound good.

I've started working on some SFZs for use in Musescore. I'm testing the new single note dynamics feature in the nightly build. However it seems that zerberus doesn't support the xfin_loccN and xfout_loccN opcodes so how does one create an SFZ that can make use of the single note dynamics?

Please can you load a sample soundfont that shows us how to make the definitions for CC02 and CC11 in a soundfont.
for example: Only with sine wave sound, and only with modulator parameters.
Because someone who wants to make a soundfont compatible with MS3.x needs this.
Because the current soundfonts (General and HQ) are very complex, I think that such a simple definition is necessary.
(The tests also give different results. I'm confused)

In reply to by Ziya Mete Demircan

Here is the simple way to make your own SoundFonts work with MuseScore's expressive mode:

  1. Edit your SoundFont in version 2.1.1 or later of Polyphone.
  2. Within each instrument (not preset), add the following modulators:

The first modulator disables the default velocity-to-attenuation curve (notice the text saying "disabling default mod."). The second modulator recreates that curve with MIDI controller #2 as the source.

I used a more complicated variation of this technique in MuseScore General that uses a different attenuation scale and allows CC2 to affect the filter as well. In the strings, I even use CC2 to crossfade between the forte and piano samples for a more natural change in tone across the dynamic range.

In reply to by bottrop

Thank you, bottrop! I know what you mean, but the PC is my stereo.

What I was referring to was a review of desktop speakers w sub-woofer which were designed for classical music, but I could no longer find the article on the net. So...I got stuck with Logitech speakers which might be fine for games and rock, but not for what I do. After fussing with mixer and synth I get a good sound on my headphones, which are good, but now and then I want to be free from the confinement of headphones.

I could spend the bucks and get Bose or Klipsch, I suppose.

In reply to by jotape1960

You can make "normal" SoundFonts use single-note expression by setting MuseScore to use CC11 only. However, this will affect all loaded SoundFonts--you can't select different methods per-SoundFont, and will reduce the quality of the dynamic expression of the default SoundFont (MuseScore_General).

Please do not ignore the different possibilities that the classical guitar with nylon strings has.

It is not necessary to sample different models (the difference between those guitars that have a spruce soundboard instead of a cedar one may be important).

But the most important thing in terms of sound quality is that when you play a piece on the classical guitar you can produce different types of sound.

List the most important:
Related to the right hand:
1) typical touch of flamenco (toque apoyado): the finger that plays the string leans on the upper string
2) free fingernail touch: the standard way of arpeggio
3) fingertip; consists in not using the nail

    Related to the left hand

4) Legato: the finger of the left hand that begins the sound is changed with another (lower or higher in the handle) or ... also you start by playing the string empty and then you lowers a finger to change the frequency of vibration
5) Glissando: the finger of the left hand slides down or up on the handle while the string continues to vibrate

Then they can follow other features more common in soundfonts, but less important, such as stopped sounds, muted harmonics etc.

I am available to help, so when you want to contact me.

If there is a need for a more detailed outline, I can do it quickly.

In reply to by speedmeteor101

I can reproduce these sounds, but I have no experience on how to sample professionally.

I am equipped with a HP laptop with lots of memory and a good CPU.

If you know how to do it, explain it to me or give me a good link for this: I will try to organize myself by contacting a recording studio is needed.

I enclose the "instrument" file that I use;

I also tried to attach the AcousticGuitar.sf2 file but I couldn't; this file contains the sounds reported in instruments2.xml, sounds that I tried to create starting from public samples, which, however, were not really the ones I wrote you; in fact I am not satisfied with the result; if you want me to send you that file give me an e-mail address

NOTE: if you look at my instruments2 file you will notice that I use an "8-string guitar" to create my scores (so my basses that also come to A1 as in baritone guitars).

See you soon.

Attachment Size
instruments2.xml 2.59 KB

In reply to by gualtiero.chiapello

Honestly, I'm not the one to do send them to. Perhaps S. Chris Collins will see this and give you instructions... It's good that you have the instruments layout set up, though. That would make it easier to implement in theory. The way midi currently works, you'd probably have to set it up with multiple channels all using midi default sounds and then change the presets anyways if it became part of the release. Also about the sf2, it's not so much about the fact that an sf2 exists, but whether or not it's legal to include (the samples) in this larger soundfont.

In reply to by s.chriscollins


the samples I currently use are those of
and precisely

Acoustic Guitars JNv2.4.sf2

where I made expressions associations with the following presets

           // preset nylon2

           // preset modified by me (see note 1)

              // unused guitar smooth preset - portamento required

             // preset modified by me (see note 2)

              // open muted preset

             //expressive nylon 2 presets

            // preset Spanish you can hear the sound of the soundboard

Note 1
I took preset 1 and removed attack and decay

Note 2
I took rol steel 1 (preset 9) and removed attack and decay and increased (a lot) sustain

It is obvious that I am not happy with what I have.

Do you still want to put the file on google drive or what I wrote is enough for you?


In reply to by gualtiero.chiapello

Hi, I rewrote the excerpt from the instruments2 file because it wasn't clear

«program value="16"/> preset nylon2

«Channel name="legato">
«program value="20"/> preset modificato da me (vedi nota 1)
«Channel name="glissato">
«program value="1"/> preset guitar smooth non usato – necessario fare portamento
«Channel name="armonico">
«program value="11"/> preset modificato da me (vedi nota 2)
«Channel name="muto">
preset open muted
«Channel name="polpastrello">
«program value="17"/> preset nylon 2 espressive
«Channel name="appoggiato">
«program value="22"/> preset Spanish si sente il rumore della tavola armonica

In reply to by gualtiero.chiapello

... and finally in english version :-)))

«Program value =" 16 "/> // preset nylon2
'/ Channel>

«Channel name =" slur ">
«Program value =" 20 "/> // preset modified by me (see note 1)
'/ Channel>
«Channel name =" glissato ">
«Program value =" 1 "/> // preset guitar smooth not used - portamento required
'/ Channel>
«Channel name =" harmonic ">
«Program value =" 11 "/> //preset modified by me (see note 2)
«Channel name =" mute ">
// open muted preset
'/ Channel>
«Channel name =" fingertip ">
«Program value =" 17 "/> // expressive nylon 2 presets
'/ Channel>
«Channel name =" apoyado ">
            «Program value =" 22 "/> // preset Spanish you hear the sound of the soundboard
'/ Channel>

Note 1
I took preset 1 and removed attack and decay

Note 2
I took rol steel 1 (preset 9) and removed attack and decay
i increased (a lot) sustain

It is obvious that I am not happy with what I have.

Do you really want me to put the file on google drive?

In reply to by gualtiero.chiapello

Those unfortunately do not come under a suitable Open Source licence (ideally MIT, to match the rest of the soundfont) we’d require for use.

“The acoustic steel guitar was made by Keith Smith ( who graciously allowed me to use it.” is a restricted usage permit only for the person behind “Soundfonts 4U” and does not transfer to us. “Other sounds are the pick of the best that are freely available on the net” is not even a proper indication of source, let alone a licence. And the soundfont itself has “Copyright Information Not Present” and “Thanks to Keith Smith ( for the main samples used.
Presets and modifications by JN”. That’s it. Sorry, not suitable. (In fact, one probably cannot even legally do a derivative of it like you did.)

I am relatively new to MuseScore and have just completed a full arrangement for Gabriel’s Oboe for my Brass Band. I look forward to a new sound font for brass. I do not know how to create sound fonts, having access to all the instruments may be useful. Is it something I can create for each instrument? Good luck with the project.

How about a good tympani roll? Doing it with tremolo gives a weird effect sounding like repeated single beats, each one chopping off the decay envelope of the previous instead of blending with it.

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