Hi Element,
2017-06-01 21:27 GMT+02:00 Element Green :
> Sounds good to me. I have had very little time for FluidSynth or my other
> free software projects and I haven't heard much from other maintainers as
> of late, so it seems to make sense to make things easier for collaboration
> and contri
Sounds good to me. I have had very little time for FluidSynth or my other
free software projects and I haven't heard much from other maintainers as
of late, so it seems to make sense to make things easier for collaboration
and contribution.
Unfortunately I don't currently have a lot of time to ev
Am Donnerstag, 01. Juni 2017 19:48 CEST, "Tom M."
schrieb:
> Sadly, fluidsynth's upstream is basically dead. There are so many custom
> fluidsynth forks floating around (esp. on github) that it's really hard to
> find and choose an update-to-date one. Personally I'm currently very
> demotiva
Sadly, fluidsynth's upstream is basically dead. There are so many custom
fluidsynth forks floating around (esp. on github) that it's really hard to
find and choose an update-to-date one. Personally I'm currently very
demotivated to look through any recent patches, because I know they wont
make it i
Hi, Marcus
>I'm not quite sure I understand what you mean here. The default_mod list is a
>member of the fluid_synth_t struct and as such will only get allocated when a
>new object of >that type is created (via new_fluid_synth). The reason it's in
>the fluid_synth_t struct and not a private
Hi Jean-Jacques,
thanks a lot for your feedback!
2017-06-01 1:54 GMT+02:00 Ceresa Jean-Jacques :
> After a glance to your patch example in ticket 166 , to avoid memory leak
we need to somes minor changes
> [...]
> fluid_synth_add_default_mod(synth, mod, FLUID_SYNTH_ADD);
>> fluid_mod_delete (mod)
