> what do you think about the idea of a "fluidsynth core" type of build config?
> ie. It just builds the bits required to synthesize the sample data, and no
> audio drivers.
If cmake doesnt find ALSA, OSS, JACK, etc. it wont build any audio drivers.
There are even cmake options like -Denable-ja
It's great that fluidsynth provides audio drivers, but for those of us who
want to take care of actually playing the audio ourselves (in my case I'm
mixing in other waveforms) what do you think about the idea of a
"fluidsynth core" type of build config?
ie. It just builds the bits required to synt
Hello,
I was wondering if somebody ever made some combinations of chorus and reverb
for emulating an environment, like "small room", "theatre", "cathedral", etc...
Sincerely.
___
fluid-dev mailing list
fluid-dev@nongnu.org
https://lists.nongnu.org/mail
> I read http://fluidsynth.sourceforge.net/api/ and basically understand how to
> set the synthesizer up, but unfortunately I don’t have a clue what to send to
> fluid_synth_write_s16 if I don’t have a driver.
You would use fluid_synth_write_*() to pull synthesized audio from the synth
and man
