On 19/10/15 16:42, Lasconic wrote: > It's for this reason that the translation updater is called "Resource > manager". The plan was to extend it to more resources such as plugins, > soundfonts, palette, styles and so on. However, it still means we need > to package the soundfont with released versions of MuseScore. >
Hi! If I may, yet another option, more suited to a source code repository way of working, could be having all the WAV files separated, plus some kind of text description file a la SFZ and then using a build system to generate the SF2. Maybe something based on libInstPatch Python bindings? http://sourceforge.net/p/swami/code/ci/master/tree/libinstpatch/examples/create_sf2.py Other possible sources of GPL SF2 code that I know of are awesfx and Polyphone: http://manpages.ubuntu.com/manpages/precise/man1/sf2text.1.html http://www.polyphone.fr/ This way of managing a sample library would allow easy substitution of samples for others of better quality or less dubious licensing and the ability to output to different formats (GIG, SFZ...) Cheers, Luis ------------------------------------------------------------------------------ _______________________________________________ Mscore-developer mailing list Mscore-developer@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mscore-developer
