63
edits
Changes
Jump to navigation
Jump to search
Line 20:
Line 20: + + + + + + + +
Refactoring Zynthians factory soundfont library (view source)
Revision as of 20:41, 26 February 2026
, 26 Februaryno edit summary
====Pro pulling upstream====
====Pro pulling upstream====
There are well maintained libraries already on Github. Fixes can be exchanged both ways. It doesn't add to the storage capacities of Zynthian.org.
There are well maintained libraries already on Github. Fixes can be exchanged both ways. It doesn't add to the storage capacities of Zynthian.org.
====Current direction of the discussion====
It seems to be the preferred option to follow a hybrid approach:
"I think we should avoid forking or storing big soundfonts that are already well maintained and available in Internet. Of course we would want to customize some of them, modifying the SFZ files or adding the YML files. I propose we do something similar to what we currently do with LV2 plugins and custom TTLs:
We would have an install script for each soundfont or group (bank) of soundfonts. The script will download the samples, custom SFZ and YML files and will setup everything in the soundfont directory so the installed soundfonts are ready to play." (Jofemodo)
Where available, we pull sample data from public repositories, but store zynthian customized scripts and UI integration files ourselves. This keeps the storage overhead low, but gives the flexibility for customizations. The distribution process is still not clear, but there is a tendency to single download scripts which might be triggered also by a webconf interaction.
==Licenses: What are issues with script and sample licensing?==
==Licenses: What are issues with script and sample licensing?==