Chris, I have taken this advice and have done just that in both the
Customizer and the Fluidsynth Sound Polyphony rate. What I have yet to
figure out is why the choice of portaudio driver (which
worked flawlessly for multiple instances of Fluidsynth/Soundfonts and
multiple devices) now shows an immediate red "x" on the Fluidsynth Icon and
I can not use portaudio as a driver at all.
I have no problem with dsound (driver) at all and can use multiple instances
and multiple devices.
Thanks for your input.
From: Chris P
Sent: Wednesday, January 3, 2018 11:32 AM
To: [hidden email] Subject: Re: [jOrgan-user] Leeds Minster Sound always on
I'm not an expert on this, but I have found this advice posted by Graham G.
/Generally you need to balance the number of notes of polyphony with
the buffer size and buffer count for the sample rate of the soundfont.
Lower buffer sizes decrease latency, but can introduce stuttering
depending on the speed of your hardware. Try decreasing the buffer
size and keeping the same (or increasing) the buffer count./
You may also consider adjusting the number of "cores" to suit your computer
as well as the polyphony in multiples of 256.
> now shows an immediate red "x" on the Fluidsynth Icon and
> I can not use portaudio as a driver at all.
Have you made sure that there is no sample rate conflict occurring? Check,
for example, what the Fluidsynth Property is set at, (44.1, 48?) and see
whether the soundcard has the same setting. Or if the latter is difficult,
simply change the Fluidsynth to the other rate and see what happens.
John R. , Thanks for the information. After making the necessary
adjustments and agreements between the settings, I now find that portaudio
does, indeed, work, however, with
significantly higher buffer size and polyphony size (matching) of 1024, as
compared with 128, 256 or 512 for dsound. At least, it does work and the
lesson is that there must be
that agreement of both buffer size and polyphony and 44,100 for the sample
rate in Fluidsynth Sound.