Hi all,
thank you very much for your feedback! Good to know that there is interest
for this feature outside of my particular use-case.
I've decided to go the route Tom suggested: concentrating on the samples
first and leaving the "structural" information loading unchanged for now.
That will bring
Hello,
Just wanted to add a positive thought.
Soundfont editor developper could benefit of this "memory economic" feature as
this kind of application needs often to avoid memory wasting.
A part theses many others (off line) applications that must care with memory
usage, the one that Marc
>
> I would really like to get your thoughts on this. Do you think it's a
> feature that other Fluidsynth users could benefit from?
>
Great work! Yes, this would be something the Radium music editor would
benefit from.
Radium uses libfluidsynth a as softsynth and not as a MIDI player. This
feature
Thanks for the proposal.
Let me add my two cents. Memory usage is not only an issue on embedded
systems but also for operating systems like Windows. People simply load
soundfonts no matter how big they are. The Musyng Kite old soundfont is a
very good example. In these days soundfonts of up to the
Tom,
Thanks a lot for that :). I want to use this in my android app using
JNI/NDK. Do you know of any definitive guide that helps me integrate
fluidsynth with android. I have come across a github project
https://github.com/VolcanoMobile/fluidsynth-android and it seems that I can
use this in my and
