I understand that FluidSynth primary usage is not a SoundFont editor, but being able to live edit the SoundFonts would be awesome.
On Thu, Jul 11, 2019 at 3:03 PM Tom M. <tom.m...@googlemail.com> wrote: > ATM, you can only get the names of the soundfont presets, see preset > iteration here: > > > https://github.com/FluidSynth/fluidsynth/blob/b8cc5197953f74700feda84b6ade3dc56419978f/src/bindings/fluid_cmd.c#L843-L860 > > Everything below that level, i.e. which samples belong to which > instruments and which instruments to which presets, is currently internal > to fluidsynth. > > What could be implemented pretty straight forward is iterating over all > the samples that a soundfont has. This might also include lonesome samples, > that are not linked to any instrument. Also, you would not know which > samples belong to which preset and the soundfont instrument layer would be > invisible as well. > > Implementing an iteration over all instruments of a preset as well as all > samples of an instrument would need some discussion, but it would make sure > that you only see instruments and samples that are actually used. In this > case it would be good to know what's the benefit you're intending by > displaying sample names to the user and what else you're planning to do > when you have the sample. Thinking of e.g. changing the sample's wave form > and manually spawning voices from it. > > Tom > > > > > _______________________________________________ > fluid-dev mailing list > fluid-dev@nongnu.org > https://lists.nongnu.org/mailman/listinfo/fluid-dev >
_______________________________________________ fluid-dev mailing list fluid-dev@nongnu.org https://lists.nongnu.org/mailman/listinfo/fluid-dev
