[fluid-dev] A question of memory

Hi all, I've written (what I hope is) a minimal, functioning test code for running fluidsynth, linking against libfluidsynth. Its available from: http://ppewww.physics.gla.ac.uk/~paul/fluidsynth/simple-fluidsynth-test.c Running this test test through valgrind's memcheck tool is quite interesti

[fluid-dev] Changes checked into CVS

I just checked in some changes into CVS. Including: - Dithering now performed for 16 bit output (thanks to Zenkov Mihail) - Bug fix to 100% CPU consumption problem with "default" ALSA device - Some minor bug fixes to ALSA sequencer code - Other minor stuff not worth mentioning Some info/question

Re: [fluid-dev] ALSA driver consuming too much CPU

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,

[fluid-dev] Pitch problems with certain instruments

Hi. When I was testing fluidsynth with different soundfonts, I noticed a very odd behaviour. I'm not very familiar with soundfont's terminology, I hope you can understand my problem nevertheless: Certain instruments don't work as expected. At the border of a keyrange, there's one key (usually

Re: [fluid-dev] Dither

On Thu, 16 Nov 2006 20:44:36 + Josh Green <[EMAIL PROTECTED]> wrote: > Thanks for the links, I have a better understanding of dithering now :) > FluidSynth really needs a new release, I'll make it a priority. Best > regards, > Josh Green > I fix fluid_aufile.c to use dithering. fluid

Re: [fluid-dev] fluidsynth_lib

I'm going through old emails now, so sorry for the late response. It seems there were some changes between 1.0.6 and 1.0.7 related to the hinstance stuff. I'm no windows programmer, so I'm not exactly sure what the issue is here. From looking at the code though, I can see that the error messag

Re: [fluid-dev] ALSA driver consuming too much CPU

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

[fluid-dev] Crash in delete_fluid_audio_driver( NULL)

Hi all, Sorry, another quick one.. If you call delete_fluid_audio_driver() with NULL, libfluidsynth crashes the code with a seg-fault, presumably trying dereferencing the NULL ptr. The other functions I tried (delete_fluid_synth() and delete_fluid_settings() ) don't suffer from this. Trying

Re: [fluid-dev] ALSA driver consuming too much CPU

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 >

Re: [fluid-dev] A question of memory

Hello Paul, I wouldn't be surprised if there are some leaks. Doesn't mean it shouldn't be fixed of course though! The valgrind output would be more useful if FluidSynth had debugging support enabled, but I could get this output myself too, which I will probably do when I get around to axing the

Re: [fluid-dev] A question of memory

On Tue, 21 Nov 2006 19:45:57 + Paul Millar <[EMAIL PROTECTED]> wrote: > Hi all, > > I've written (what I hope is) a minimal, functioning test code for running > fluidsynth, linking against libfluidsynth. Its available from: > > http://ppewww.physics.gla.ac.uk/~paul/fluidsynth/simple-fluids

[fluid-dev] Re: Changes checked into CVS

On Tue, 21 Nov 2006 21:36:16 + Josh Green <[EMAIL PROTECTED]> wrote: > I just checked in some changes into CVS. > > Including: > - Dithering now performed for 16 bit output (thanks to Zenkov Mihail) > - Bug fix to 100% CPU consumption problem with "default" ALSA device > - Some minor bug fixe