On 30/10/20 10:57 pm, Tom M. via fluid-dev wrote:
I would need to compile with Visual Studio
Pls, why do you *need* to compile with that ancient Microsoft product?
Couldn't you use MinGW, CygWin, Clang or ICC?
To be precise I need to compile my app with MSVC, but I can compile
Fluidsynth to
Hi all,
JJC has recently proposed a new feature that would allow more control
over the external and internal audio routing. You can find the
proposal and subsequent discussion in the following issue and
pull-request:
https://github.com/FluidSynth/fluidsynth/issues/669
https://github.com/FluidSynth
> So in my opinion, doing the work to make the sample cache and maybe
even the whole soundfont loading mechanism work in parallel seems like
a good idea and worth the effort.
We need to be careful, as the soundfont loading is exposed via the API.
Breaking changes should be avoided. Also, we could
Hi,
Am Fr., 30. Okt. 2020 um 02:09 Uhr schrieb Hamish Moffatt
:
> Beautiful! Over 6 times faster.
Great, thanks for testing it.
> In order to get the best out of modern CPUs we have to use
> more threads as the cores aren't getting much faster.
I think this is probably the best reason to consi
> 1) Not enough loud:
It's not clear what you mean by "artifacts". Is it clipping?
Interruptions? Distortions?
Ideally provide the broken audio rendering. But without the soundfont
and a test MIDI it's very hard to tell what's wrong. Try a different
audio driver. Or use the file renderer to write
