> Hello, excuse me, what is the issue with the dsound driver?
No, dsound driver is fine and works well. Simply a bug was introduced by
changes on reverb initialization. This bug caused a side effect on audio output.
The culprid wasn't dsound driver but this wrong reverb initialization. This bug
Hello,
excuse me, what is the issue with the dsound driver?
Sincerely.
> Il 27 settembre 2019 alle 9.11 "Tom M. via fluid-dev"
> ha scritto:
>
>
> FYI: #562 was merged and will be part of 2.0.7 . There currently is an
> issue with the dsound driver on windows, so the release of 2.0.7 needs
>
FYI: #562 was merged and will be part of 2.0.7 . There currently is an
issue with the dsound driver on windows, so the release of 2.0.7 needs
to wait.
Tom
___
fluid-dev mailing list
fluid-dev@nongnu.org
https://lists.nongnu.org/mailman/listinfo/fluid-de
PR opened, to be merged soon.
https://github.com/FluidSynth/fluidsynth/pull/562
Tom
___
fluid-dev mailing list
fluid-dev@nongnu.org
https://lists.nongnu.org/mailman/listinfo/fluid-dev
>Also, as far as I can tell, this approach is still not a proper solution on
>Windows, since modules may have their own heaps
Comfirmed, this is a bad approch. I had stumbled on the same problem in the
past; I forgot about that !
Thanks for raising this.
jjc
_
I'm just using the build from the Arch repos right now, but I don't have
a problem with building it from source to test this (in fact, I already
did to debug something).
Pieter-Jan Briers
___
fluid-dev mailing list
fluid-dev@nongnu.org
https://lists
Pieter is raising a good point. Exposing a fluid_free() is no problem.
Just let me know pls.: Are you using fluidsynth from recent git or
some stable release? Because if you are using recent git anyway, I
would just commit the change to master and not release a 2.0.7 for the
moment.
Tom
Hi,
> In this case you could write and build a new C shared library that
contains the C functions you need.
I could do this, but this would require an extra shared library which
would be a pain to manage. Ideally I really shouldn't need any extra
native binaries outside of a normal libfluids
Hi,
>I am trying to use the library from C#,
I guess you use the fluidsynth shared library, and you have a way to bind your
C# code to C fluidsynth API.
In this case you could write and build a new C shared library that contains the
C functions you need.
For example, let the following
Hi,
The documentation for fluid_settings_dupstr() says to use free() to free
the string given by the function. I am trying to use the library from
C#, and while .NET does have equivalents to malloc/free, there is no
guarantee this matches the free() used by Fluidsynth. (At least with
Linux Co
10 matches
Mail list logo
