FluidR3.sf3 is an heresy !
On Tue, Apr 24, 2018 at 11:54 PM, Marcus Weseloh wrote:
> Hi Philippe,
>
> 2018-04-24 21:32 GMT+02:00 Philippe Simons :
> >> So I think I'm probably the best placed to speak since I'm using
> fluidsynth both as a MIDI player and as a real-time synthesizer on Android.
>
Hi Philippe,
2018-04-24 21:32 GMT+02:00 Philippe Simons :
>> So I think I'm probably the best placed to speak since I'm using
fluidsynth both as a MIDI player and as a real-time synthesizer on Android.
> Obviously I didn't wait for this feature to be implemented to create my
applications, so I can
Hi again,
just out of curiosity, I analysed a large library of MIDI files with regard
to the number of program change events that they contain. I downloaded the
geocities collection from
https://archive.org/details/archiveteam-geocities-midi-collection-2009,
containing around 51000 MIDI files that
Hi all,
So I think I'm probably the best placed to speak since I'm using fluidsynth
both as a MIDI player and as a real-time synthesizer on Android.
Obviously I didn't wait for this feature to be implemented to create my
applications, so I can say that I don't them... like at all.
for the player,
Hi Tom,
yes, it's a little hackish... but not the part you mention, I think.
Overriding the "authority" of the synth over when and which samples to load
is perfectly valid, in my opinion. Yes, those functions would also need to
be exposed to the user via the shell and API, but that would actually
Sorry, I think it's a hack. Dynamic sample loading is implemented in a way to
allow the synth to control when to load or unload presets and samples.
Introducing this fluid_defpreset_t::loaded_manually flag overrides the synth's
authority. Instead the midi player gets in charge of that.
If sampl
