MIDI note #94 does not play in FluidR3_GM.sf2

• Nov 22, 2010 - 20:55
Type
Functional
Severity
S4 - Minor
Status
closed
Project

Sorry, that I'm still finding some bugs. I really like your program.

To be seen in attached file.
I use 0.9.6.3 stable, Windows XP.

George Vysata

Attachment Size
Bug report.mscz 1.44 KB

Comments

Odd, since "FluidR3_GM.sf2" plays the same note correctly using Viena SoundFont editor. And MuseScore plays the note correctly using the default SoundFont "TimGM6mb.sf2". It looks like it is just the combination of MuseScore and FluidR3_GM.sf2 that has a problem.

(Tested using 0.9.6.3 stable, Windows 7)

Title Bb 3 does not play - violin solo (FluidR3_GM.sf2) B♭ 3 does not play in FluidR3_GM.sf2

Still reproducible.

Is B♭ 3 the right name?

Using MuseScore 2.0 Nightly Build (7c8fbda) - Mac 10.7.4.

There are unfortunately no standards for for the naming of octaves - or more particularly, there are several competing / conflicting standards. The note in question is the Bb a full octave above the treble clef staff. Depending on which standard you prefer, I believe that's either bb''', bb3, Bb5, or Bb6

Title B♭ 3 does not play in FluidR3_GM.sf2 MIDI note #94 does not play in FluidR3_GM.sf2
Status (old) needs info active

I suggest we refer to it as such - amended title accordingly.

It seems related to the specific instrument, as changing it to "piano", "organ"or "violins 1"; moreover, that note doesn't even play when coming from MIDI input. I can add that notes from 102 to 108 do not play too - beside those I have no more keys on the piano :)
Apart from #94, are the others expected not to play, or should they too?

Just been testing this again.

It seems to be specifically violin which has this problem.

All the other instruments I have tried (not many but a representative cross section) play this note.

On checking in Viena that note is missing from the violin instrument in the soundfont itself.

How should we proceed on this? It's not a MuseScore issue - but one for the Fluid soundfont people to sort out - it's easy enough to change, but what is the copyright status of the Soundfont? My Google search on this has yielded only ambiguity.

The Fluid soundfont also does not play the full professional range for the violin.

Marking as "won't fix" for the time being.

As MuseScore Version and OS information is irrelevant here am not adding it.

Seems we are already shipping our own variant (sf3 format), so if there were issues with our modifying the soundfont, we'd already be running against them.

Status (old) won't fix active

In which case Marc, I will amend the soundfont when I have a minute or two spare.

I'll also extend the range to encompass the entire professional range of the violin while I'm at it.

Status (old) active patch (ready to commit)

OK it's done.

Am uploading the commit to GitHub as we speak.

Is there a compiled copy of Werner's sf3 conversion tool - preferably for Windows?

Currently it is still in SF2 format and is consequently adding 144 MB to the commit size.

In case you still need a Windows binary of Werner's sftools, here it is (compiled with gcc-4.8.0, Qt 4.8.4).

https://docs.google.com/file/d/0BxjayMZiuupOSHdSdFRVOXQ0M1U/edit?usp=sh…
(File -> Download it is roughly 2.7 MB)

If you want to compile it by yourself, just download the folder sftool (or clone with git) and use the same steps as for MuseScore compilation (in particular, the dependencies, which should already be OK for the usual MS compilation, the settings for the PATH and the use of "mingw32-make Makefile.mingw").

Ciao,
ABL

Yes I tested with the nightly using the standard soundfont which is fluid.sf3

Thanks to ABL I now have a copy of the conversion tool

So provided I can get it to work I will convert to sf3

It would be a good idea to retain a copy of the SF2 file at Github however
So I'll leave the current pull request intact.

Status (old) active patch (ready to commit)

OK Werners conversion tool worked fine

I now have an SF3 version of the fixed SoundFont

How do you want me to proceed Nicolas?

Adding 144Mb to the github repo would be a pain for anyone cloning it... If you could prepare a zip file like this one http://prereleases.musescore.org/soundfont/fluid-soundfont.zip appending to the README what you did, it would be great. We will have a backup of the SF2 file then.

For the SF3 file, a pull request if fine. You could add the README file next to the SF3 file as well in this pull request. I think I will rename the SF3 file as well... to match the name of the sf2 one.