On Tue, Jul 5, 2016 at 1:19 AM, Element Green
wrote:
>
> As Hamish mentioned, DirectSound does not perform very well when it comes
> to low latency. You may want to look into other supported audio drivers
> such as Jack Audio Connection Kit (which appears to be available on Windows
> now)) or pe
Hello Martiniano,
If you're just trying to set a couple of parameters in the FluidSynth
command line interface, you could execute "fluidsynth --help". You'll find
there is a "-o" option which allows for setting option values, such as
audio.periods
and audio.period-size. Running "fluidsynth -o he
Hi people,
I've been following the last discussions. I know most anything of
programming codes and actually did not understand what has been said. I've
tried to visit the listinfo site but it did not help. Is there any file
that I can read to know the basics of FluidSynth? One first questions: is
Hi Hamish,
The bad new:
From my experience, (as i am using Windows too), using dsound driver (i
assume you are using this default driver too) it is not possible to get
low latency response.
This is inherent to dsound as it require multiples buffers to do its
jobs. Anyway the big advantage, it
Is there any harm in reducing audio.period-size on Windows? It's a lot
bigger by default on Windows than Mac/Linux. Should I increase
audio.periods to compensate?
Background: I have my own timing loops and I'm outputting events by
calling fluid_synth_noteon/noteoff() just in time (or with
flu