Hallo,
Brice M�alier hat gesagt: // Brice M�alier wrote:
> With iiwusynth, the problem is that the sound seems to
> be read with a variable speed (like before I passed
> the option dxs_support with the wave), so it crackles.
> I have the following output when I start the program:
>
> iiwusynth: warning: Couldn't set high priority
> scheduling for the audio output
> iiwusynth: warning: Failed to disable paging of sample
> data
> iiwusynth: warning: Couldn't set high priority
> scheduling for the MIDI input
iiwusynth is called fluidsynth now. Bug in iiwusynth will thus not get
fixed there anymore.
> With fluidsynth it's worst: the cpu power used raises
> up to 100% and sometimes the system hangs!!! (I have
> an AMD Athlon XP 2200+ with 256 MB Ram!!) and only a
> part of the instruments in the soundfont is loaded.
This probably is a fluidsynth problem, so you might want to ask this
on the fluid-dev mailing list. Is your soundfont available for
testing? Is it very large?
> PS: How can I automatically force the sampling rate to
> 48000 Hz with alsa (I know how to do that with artsd &
> esd but, as you know, arts & jackd & iiwusynth aren't compatibles...)
Either use an ~/.asoundrc that automatically converts to 48 kHz or
start the application with 48 kHz samplerate. With fluidsynth this
goes like this:
$ fluidsynth --help | grep sample
-r, --sample-rate
Set the sample rate
ciao
--
Frank Barknecht _ ______footils.org__
-------------------------------------------------------
This SF.net email is sponsored by OSDN developer relations
Here's your chance to show off your extensive product knowledge
We want to know what you know. Tell us and you have a chance to win $100
http://www.zoomerang.com/survey.zgi?HRPT1X3RYQNC5V4MLNSV3E54
_______________________________________________
Alsa-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/alsa-user
