[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[fluid-dev] Question to fluidsynth specialists - Crash in "new_fluid_set
[fluid-dev] Question to fluidsynth specialists - Crash in "new_fluid_settings"
Thu, 5 Nov 2015 10:52:19 +0100
We at Notation
Software (see www.notation.com) use
libfluidsynth under the LGPL license.
We have created
the libfluidsynth dll libraries for "dsound" and "portaudio" where we use the
Steinberg's ASIO underneath.
setting is with the "dsound" configuration. The customer can optionally select
the portaudio/ASIO settings for e.g. realtime recording.
We have a customer
error report where the software crashes at the very first fluidsynth statement
"settings = new_fluid_settings();"
showed that the customer uses an exotic audio card where the initialzation of
the portaudio/ASIO/card driver software causes a crash for whatever
When using a
libfluidsynth library w/o portaudio support all works
only "dsound" is used, the portaudio software is started
by "new_fluid_settings()" and causes that crash.
When the libs
are statically built with #define PORTAUDIO_SUPPORT, in any case the call
of "new_fluid_settings()" performs an initialization of the
portaudio/ASIO/sound card through "fluid_settings_add_option (settings,
A fault tolerant
solution should activate "fluid_settings_add_option (settings, "audio.driver",
"portaudio")" ONLY when
portaudio is actively selected and not by default when the libs are
statically built at th beginning.
As I have not
found anything in any forum whether an option exist, is there a
possibility to dynamically set the "portaudio"
Such a solution is
trivial but as mentioned we use libfluidsynth under the LGPL license and want to
keep the software unchanged.
Does anybody can
provide an advice what would be the best way to address this
advice is highly appreciated.
- [fluid-dev] Question to fluidsynth specialists - Crash in "new_fluid_settings",
Reinhold Hoffmann <=