Customisation of Jeux pipe organ Soundfont
As a result of the uncertainty regarding the inclusion of Aeolus in MuseScore 2, I have approached John McCoy, the author of the Jeux pipe organ soundfont to ask for permission to customise Jeux for use with MuseScore.
Here is my email to him:_
Greetings John,
We have not met, but I have been very aware of your Jeux Soundfont for many years, first coming across it while I was programming backing tracks for a living in the late 90's/early 2000's - mercifully I have now been able to semi-retire and concentrate on organs and church music :)
It has certainly improved ernomously over time :)
Early in 2011, when I was considering whether I should pony up the ridiculous amount of cash required to upgrade Finale from it's geriatric Finale 2003 state, I decided to see whether the Open Source world had anything to offer instead, which was when I first came across MuseScore. As a test I decided to write a transcription of the Regina Caeli with it. By the end of that process I was hooked, and decided to keep the £400 I would have had to spend on upgrading Finale in my wallet :)
As time has progressed I have become involved with the development of the project itself, particularly with the management of instrument sound provision and development.
Pipe organs are always really badly represented in all GM soundfonts, and this is no exception in the psrt of the FluidRS soundfont which is the default to be supplied with the upcoming MuseScore 2.0.
I would, therefore, like to produce a customised version of Jeux 1.4 which organists could download to use with MuseScore 2's new multiple soundfont capablity.
If you have any objections to this, please don't hesitate to say, but if not - do I have your blessing? You will, of course, have access to the customised soundfont to incorporate into Jeux or not depending whether you would think it was useful. You would also retain your copyright on the samples used, but I would be planning to release the soundfont under a Creative Commons Attribution-NonCommercial-ShareAlike 3.0 Unported Licence.
Looking forward to hearing from you about this.
Regards
Michael Cowgill
Director of Music,
St Michael's Retford, Notts, UK
and John McCoys reply:-
Thanks for your message!
Yes, what you propose sounds very sensible. I know from past adventures that it is sometimes very difficult to convert "stops" to another format. The way the SoundFont "standards" were implemented sometimes turns out to be different from the way those standards were written, for some parameters. I have never heard any explanation of why the standards didn't match the implementation. And because the implementation protocol isn't available to the public, we have to rely on reverse engineering to estimate the algorithms that were actually used.
The other difficulty that can be anticipated is that every time I install the soundfont on a new SoundBlaster card, a few of the "stops" get corrupted -- loop points are lost! Again, I have no idea why this happens to a few samples and not to others. Finding these problems takes a lot of time!
But if the open source environment has progressed far enough, perhaps these problems have already been solved. I wish you good luck in your project!
With best regards,
John McCoy
So this has opened the way for us to customise the soundfont how we want it.
It would be helpful for anyone interesting in using this to give input on what we actually need to do to the soundfont.
If you don't already have the original you can download it here: http://www.realmac.info/download.htm I would ignore the Hammersound link - it is quicker to use the download links directly from the page. Unless of course you are looking for more sounfonts.
Comments
Does it particularly need customizing?
If we're going to be limited to one instrument per bank&preset (ie no clashes allowed), then it would be nice to move the preset numbers to a different bank, so the font can be used in conjunction with General MIDI. That's something I could do actually. Otherwise it would be interesting to know what the differences are between the various GeneralUser Soundfont editions? As that might indicate what needs customizing for FluidSynth use.
In reply to Does it particularly need by TavyMusic
it would be nice to move the preset numbers to a different bank,
Well that is one area where it will need customising if we are going to use it in conjunction with a GM soundfont.
There are also many presets which are designed for use with a Midi organ setup which would assign different presets to different stops.
These would be useless in MuseScore, and would need replacing with other presets.
...in which customisation could be needed are stop names: all non-ASCII characters (as in Neuvième, Spitzflöte, Holzflöte, ...) appear as garbage in my Linux Mint 14. Linux installations usually assume UTF-8 as default character set, as does Windows (no idea about Mac's)
M.
In reply to A small detail... by Miwarre
Is that in MuseScore or Swami?
In my Ubuntu Studio 12.04 installation Polyphone and MuseScore 1.3 show the patchnames correctly but Swami doesn't, which suggests it's more about applications not reading unicode characters properly rather than a fault in the Soundfont itself.
In reply to Is that in MuseScore or by ChurchOrganist
In MuseScore 2.0 (yesterday commit), under Linux Mint 14 64-bit:
NOT FOUND: 1
M.
In reply to In MuseScore 2.0 (yesterday by Miwarre
Ooer :(
All I can say is they're UTF-8 characters :)
I'll try a nightly on my Ubuntu Studio machine
See if it does the same.
If not it looks as though it could be a Mint thing - which desktop environment is it?
ISTR Mint uses KDE????
In reply to Ooer :( All I can say is by ChurchOrganist
I believe the names are read here https://github.com/musescore/MuseScore/blob/master/fluid/sfont.cpp#L989
And Qt should convert the char to QString using UTF-8 http://qt-project.org/doc/qt-5.1/qtcore/qstring.html#operator-eq-5 (or not and it uses latin1? since it's not a const?)
In reply to I believe the names are read by [DELETED] 5
I checked the Linux nightlies with a view to installing on my Ubuntu Studio machine last night, only to find that they are all now marked 64bit.
Unfortunately I have Ubuntu Studio running on a 32 bit machine - presumably a 64 bit build won't run on that?
Maybe I will have to look into setting up for custom building, but it depends on how much space is required - currently the machine shares an 80gig hard drive with Windows XP.
In reply to Ooer :( All I can say is by ChurchOrganist
Mint is available both with KDE, Gnome 2 and its own desktop Cinnamon. I use Gnome 2.
M.
In reply to Ooer :( All I can say is by ChurchOrganist
Ok, indeed Musescore 2 is not displaying unicode characters properly in the Soundfont patchnames list in the mixer in Ubuntu Studio.
Any top bit set characters are appearing ? same as in Miwarre's Mint installation.
I'll open an issue.
In reply to Ok, indeed Musescore 2 is not by ChurchOrganist
Issue #23191: Unicode characters not displayed in mixer patch list on Linux opened.
Beta Version just completed.
Available from my DropBox Account:
https://www.dropbox.com/s/zggl3pnndeqmxor/MSjeux14-0-6-beta-SoundFont.z…
Please put this through its paces and let me know of any problems, suggestions for improvement etc.
In reply to Beta Version just by ChurchOrganist
Congratulations Michael.
Regards,