Re: [fluid-dev] --no-shell option causes crash

[Pedro Lopez-Cabanillas]

On Friday 04 March 2011, Nuzhna Pomoshch wrote:
> I tried to search for this, but couldn't locate anyone else
> having this problem.
> 
> Any soundfont, any midi file.
> 
> $ fluidsynth /path/to/some/soundfont /path/to/some/midi/file
> FluidSynth version 1.1.3
> Copyright (C) 2000-2010 Peter Hanappe and others.
> Distributed under the LGPL license.
> SoundFont(R) is a registered trademark of E-mu Systems, Inc.
> 
> fluidsynth: warning: Failed to pin the sample data to RAM; swapping is 
> possible.
> fluidsynth: warning: Requested a period size of 64, got 940 instead
> fluidsynth: warning: Requested 16 periods, got 8 instead
> Type 'help' for help topics.
> 
> > fluidsynth: warning: Failed to set thread to high priority
> fluidsynth: warning: Failed to set thread to high priority
> 
> [plays midi file]
> 
> But:
> 
> $ fluidsynth -i /path/to/some/soundfont /path/to/some/midi/file
> 
> FluidSynth version 1.1.3
> Copyright (C) 2000-2010 Peter Hanappe and others.
> Distributed under the LGPL license.
> SoundFont(R) is a registered trademark of E-mu Systems, Inc.
> 
> fluidsynth: warning: Failed to pin the sample data to RAM; swapping is 
> possible.
> fluidsynth: warning: Requested a period size of 64, got 940 instead
> fluidsynth: warning: Requested 16 periods, got 8 instead
> *** glibc detected *** fluidsynth: double free or corruption (out): 
> 0x00007f1268000af0 ***

I think that this may have been fixed recently, after the 1.1.3 release. Can 
you please try the current  Subversion trunk?

[...] 
> Also (sorry, I am a complete newbie), any thoughts on the warnings?
> I have gigabytes of unused RAM, I don't understand the period
> warnings, and I don't know how to make sure threads get "high
> priority."

The period warnings mean that FluidSynth has a default settings of 16 periods x 
64 bytes, which is not supported by your soundcard, and has been adjusted to 
the nearest supported values.

There are two mechanisms to give high priority to FluidSynth. One is the PAM 
based set_rlimits() method, editing the file /etc/security/limits.conf and 
raising the priority limits to your user or a group you belong to. The second 
method involves using RealtimeKit (rtkit), which in turn depends on PolicyKit 
and dbus. These are the same two methods used by PulseAudio.

Regards,
Pedro