Open spessasus opened 1 month ago
I think that there's a slight misunderstanding w.r.t. the versioning system. While the legacy SF file structure isn't violated with this proposal, we've done a feature freeze for 4.00, so it would have to be included in 4.01.
This means that we've defined a set of features that will be in 4.00 (the "initial version"). This is not done because we don't want to immediately implement the feature, but rather because if we were to release features too quickly, then it could overwhelm SFe program developers. This may change when we add the ISFe chunk feature flag system.
In fact, SFe64 4.x and all SFe32 versions are planned to be completely compatible with the legacy file structure.
Therefore, this feature has been planned for 4.01.
I see, but what are your thoughts on the actual proposal?
So, I've taken a look at your NRPN proposal for SF and here's my thoughts:
PNMM
stands for "parameter-number-modulator-map", maybe it would be more clear for prospective developers if the fourcc name contained "RPN" or "NRPN" in it. DMOD
fourcc, but I'm not sure whether this was intended, or if you meant to say PNMM
.These concepts make you ponder about the missing MIDI 1.0 features in SF2.04. A future version of SFe64 is likely to be designed to run in MIDI 2.0, or at least allow bank developers to use MIDI 2.0, but this is likely not going to be a thing for a very long time.
The example shows a
DMOD
fourcc, but I'm not sure whether this was intended, or if you meant to sayPNMM
.
Nice catch, fixed, thanks!
https://github.com/spessasus/soundfont-proposals/blob/main/nprn_mod_sources.md
Can be merged into the first version as it doesn't violate the current file structure.
thoughts?