-
I apologize as I know very little about this.
I have seen these mentioned in soundfont spec but have not been able to get them to work
For example I tried an application called LMMS that contains an instrument called SF2 Player which I believe uses FS. This application provides you with a graphical MIDI CC array of knobs 0-127 On FS wiki I saw these on the list, did not see the other two decay & sustain, but regardless these parameters show X icons meaning they are not supported. I tried them in LMMS as well but same result
So does this mean that these parameters in the way I am looking for are not supported?
Do you basically have to assign a "modulator" for each of these 4 parameters which get added inside the soundfont and then the CC numbers mentioned get linked to them somehow in the soundfont which then let MIDI access them? If anyone has any information they could share about this, I would appreciate it. Again I apologize for this question, I am just confused. Thank You Actually, one more thing
I am assuming all items like this are for if someone is actually coding a FS based player, am I correct? |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments
-
A default behavior for soundcontroller 3 and 4 is not defined by the soundfont spec. Hence, you need to apply modulator as you already mentioned. And yes, these modulator have to be applied to any soundfont and every instrument in that soundfont where you want to use it. That's not our invention, that's the standard way of how Soundfont was designed. Yet, because this approach sucks, fluidsynth provides an API that would greatly simplify things:
Yes. Polyphone is the right tool for that. Start with a modulator that manipulates a generator that's easily audible, like
That's not possible, because nobody know how you personally want the knob to behave: Linear, convex, what's the minimum, maximum, etc. - There's no standard or convention which defines that (to my best knowledge).
This API is used for manipulating destination generators directly via NRPNs. Using this API directly is not suitable for your use-case. Ofc, you're free to use NRPN MIDI events to manipulate generators. I cannot recommend this for you currently. You should first make some initial steps to setup modulators, understand how they work and influence the various destination generators, before you step over to NRPNs. |
Beta Was this translation helpful? Give feedback.
-
@derselbst Just a clarification / slight follow up question, I think it is because phrased it like this
that lead to your response
I was referring to instrument players for the any of these formats SF2, SFZ, GIG, DS do not contain players that provide these types of envelope parameters in Linux. In Windows there are many, but do not want to use WINE. SF2 SFZ Thank you again for answer each one of my questions |
Beta Was this translation helpful? Give feedback.
A default behavior for soundcontroller 3 and 4 is not defined by the soundfont spec. Hence, you need to apply modulator as you already mentioned. And yes, these modulator have to be applied to any soundfont and every instrument in that soundfont where you want to use it. That's not our invention, that's the standard way of how Soundfont was designed.
Yet, because this approach sucks, fluidsynth provides an API that would greatly simplify things:
fluid_synth_add_default_mod()
. Whether or not this API is adopted by the programs you're using is beyond my knowledge.