> On 20 May 2022, at 03:03, 刘家桐 wrote:
>
> But when I used "fluidsynth -R1nivF/home/parallels/my_music.wav
> /home/parallels/FluidR3_GM.sf2 /home/parallels/MIDI_sample.mid" (enable
> Reverb module), The program just played the music through my computer's
> speaker.
>
> Then I found that afte
I’m guessing that you’re hooking up Synth::seq_callback via
fluid_sequencer_register_client or similar.
It seems like a bad idea to be attempting GUI operations from such a callback,
as GUI APIs generally expect to be driven by a single thread. A quick search
suggests that SDL’s convention is t
I had similar thoughts, re. searching the file system path not being a synth
feature. But simply deferring to the application has other downsides when it
comes to soundfont adoption in general - end users must manually configure each
application and there’s no standard way to do this. Eg. for my
On 21 Sep 2018, at 02:08, Tom M. wrote:
>> Carlo: I have no code duplication here because the C implementation for
>> calculating the tables is gone.
>
> Removing the C implementation means that python would become a required build
> dependency, which is what I want to avoid, because, again,
