Hi Mihail,
On Tuesday 21 November 2006 15:16, Mihail Zenkov wrote:
> > I can set the sample rate to 48kHz in fluid_settings_t. But, when I
> > start the audio output, it falls back to 41.1kHz. Setting the ALSA
> > device to "default" still gives 100% CPU usage, but "hw:0" works fine.
>
> Please,
I just found and fixed the bug that was causing the 100% CPU usage
problem with the "default" ALSA device (now in CVS). As for the sample
rate, I suspect your sound card doesn't support anything other than
48000 (yes they exist). There is an option with ALSA to turn on
re-sampling, but FluidSynth
On Tue, 21 Nov 2006 16:14:25 +
Paul Millar <[EMAIL PROTECTED]> wrote:
> Hi Mihail,
>
> On Tuesday 21 November 2006 15:16, Mihail Zenkov wrote:
> > > I can set the sample rate to 48kHz in fluid_settings_t. But, when I
> > > start the audio output, it falls back to 41.1kHz. Setting the ALSA
>
Hallo Paul,
On Thu, 2006-11-16 at 22:02 +, Paul Millar wrote:
> Josh, Garett,
>
> Thank guys for the quick reply.
>
> Yes, the work-around worked fine: when setting "audio.alsa.device" to "hw:0"
> I see the CPU usage drops to far more modest values.
> Setting "audio.alsa.device" to "defa
On Thu, 16 Nov 2006 22:02:45 +
Paul Millar <[EMAIL PROTECTED]> wrote:
> Josh, Garett,
>
> Thank guys for the quick reply.
>
> Yes, the work-around worked fine: when setting "audio.alsa.device" to "hw:0"
> I see the CPU usage drops to far more modest values.
> Setting "audio.alsa.device"
Josh, Garett,
Thank guys for the quick reply.
Yes, the work-around worked fine: when setting "audio.alsa.device" to "hw:0"
I see the CPU usage drops to far more modest values.
Setting "audio.alsa.device" to "default" (fluidsynth's default value, I
believe) recreates the problem. [as an asid
It is indeed known about, but should have been fixed a while ago.. I'll
do my best to fix this issue and get a release out soon. Best regards,
Josh
On Thu, 2006-11-16 at 11:50 -0700, Garett Shulman wrote:
> I believe that this is a known glitch between fluidsynth and alsa plug.
> Check
I believe that this is a known glitch between fluidsynth and alsa plug.
Check out:
http://www.mail-archive.com/fluid-dev@nongnu.org/msg00183.html
Paul Millar wrote:
Hi all,
Inspired by Nathan Harrington's article on monitoring computers with
FluidSynth (recently linked to from Slashdot), I've
Hi all,
Inspired by Nathan Harrington's article on monitoring computers with
FluidSynth (recently linked to from Slashdot), I've started coding against
FluidSynth's C-library: libfluidsynth.
I'd like to say first how easy it was: libfluidsynth is a very nice library!
The main reason for writin
