On 07/30/2017 08:45 AM, martin wrote:
Hello all, in an instrument definition (idf-file) I can group patches to patch groups. Is a similar thing possible with soundfonts? I know, that (most of) the available soundfonts will not contain any grouping information, but what if I assemble the soundfont myself? I tried prefixing the name with a group name as in "Piano/Grand Piano", but that just displays "Piano/Grand Piano" instead of showing "Grand Piano" in a group "Piano".
Hi Martin. That's an astute observation, one that's probably puzzled other users for a long time. Our instrument definitions are for hardware devices such as our Jack midi or ALSA device drivers. They have no relation to synthesizers such as our fluidsynth implementation. This is because our synthesizer devices define all of those settings themselves. Patch names, numbers, controllers and their names and ranges etc. Over the years I have thought about whether our instrument definition files could assist in any way. But no, they cannot, the synth takes care of all of that stuff. So, here is the issue: For our fluidsynth implementation, unfortunately, you notice that we just lump all the patches into a list with no groups or sorting at all. That is because this is all the fluidsynth library tells us ! There is no more information to be had from that library. However, fear not: You may notice that as of several months ago, I added optional support for a much more powerful library: The libinstpatch library, from the Swami project. That library is how Swami is able to display /everything/ about a soundfont, including groups. So I currently use this library for just one thing: Automatically displaying drum note names, taken from the soundfont, so that the user doesn't have to create a MusE drum map for a soundfont. Yay. You know, it never occurred to me while coding this, that the same library might once and for all allow me to finally display soundfont patch groups and group names. Thanks for bringing this up! It might just happen, if I can find the time to do it... Unfortunately the libinstpatch seems broken right now, it won't compile here without mods. I must contact the author about that. He told me this library is actually obsolete now, he has just added a brand new replacement system which uses something from gtk called "GIntrospection". He advised it is new and not 'officially' in the project yet but it's coming along. Tim. ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Lmuse-user mailing list Lmuse-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/lmuse-user
