Re: [fluid-dev] Question to fluidsynth specialists - Crash in "new_fluid_settings"

I'm not saying it's a good workaround - more of a quick'n'dirty hacky fix while we figure out what to do - but you can compile and ship two versions of the same library. One with and one without portaudio support; and only load the second library in case the customer selects portaudio in your U

Re: [fluid-dev] Question to fluidsynth specialists - Crash in "new_fluid_settings"

Hi David, hi "sqweek", Thanks for the immediate response. That was fast. Definitely, a fix of "portaudio/ASIO" and all those faulty "card drivers" would be better :-) Of course, the trade-off has made sense up-to-date but might be reconsidered now (??). Common to all cases (incl. those links

Re: [fluid-dev] Question to fluidsynth specialists - Crash in "new_fluid_settings"

On 5 November 2015 at 18:57, David Henningsson wrote: > > On 2015-11-05 10:52, Reinhold Hoffmann wrote: >> An investigation showed that the customer uses an exotic audio card >> where the initialzation of the portaudio/ASIO/card driver software >> causes a crash for whatever reason. > > Certainly

Re: [fluid-dev] Question to fluidsynth specialists - Crash in "new_fluid_settings"

On 2015-11-05 10:52, Reinhold Hoffmann wrote: Hi fluid-dev team, We at Notation Software (see www.notation.com ) use libfluidsynth under the LGPL license. Hi Reinhold! We have created the libfluidsynth dll libraries for "dsound" and "portaudio" where we use the Stei

[fluid-dev] Question to fluidsynth specialists - Crash in "new_fluid_settings"

Hi fluid-dev team, 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. Our default setting is with the "dsound" configuration. The c