[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [fluid-dev] question about fluidsynth include statements

From: Josh Green
Subject: Re: [fluid-dev] question about fluidsynth include statements
Date: Wed, 18 Apr 2007 17:49:40 +0200

On Wed, 2007-04-18 at 11:14 -0400, Marcus Planet wrote:
> Hello Josh and others and thank you for the helpful info regarding
> jack setups.  It appears to me that recent faster processor speeds and
> recent kernel developments are having an impact on the importance of
> jack and specialized kernels, but that the jack approach is very
> strong in terms of its ability to link different apps together in a
> reliable and efficient way.
> In this fluid-synth related program I'm working on I am having no
> difficulty using many of the fluid commands, however I'm getting this
> message-- warning: implicit declaration of function
> 'fluid_synth_all_notes_off'-- despite attempting several variations of
> include statements such as '#include <fluidsynth.h>" (which works for
> most) and "#include <fluidsynth/fluid_synth.h>" and several others.
> Could I have a pointer here?
> Let me add that I've recently begun using Subversion and I'm finding
> it much much better than CVS.   Thank you for your advice!
> Marc

Hello Marc,

>From what I can see fluid_synth_all_notes_off() is not declared in the
public headers.  Not sure the reason for this, since it does seem like
it could be useful and doesn't really depend on anything specifically
internal to the synthesizer.  I do see a  fluid_synth_system_reset()
declared public, but that is likely not really what you want (turns off
all voices immediately, resets reverb/chorus and controllers).

There are "all notes off" and "all sounds off" MIDI messages, so it may
be possible to inject a MIDI event into the FluidSynth MIDI router to do
the same thing.  I'm not sure off hand the best way to do that, but
perhaps the functions in public header fluidsynth/midi.h might be

fluid_synth_all_notes_off() should likely be added to the public API


reply via email to

[Prev in Thread] Current Thread [Next in Thread]