On 2011-01-29 21:01, jimmy wrote:
--- On Fri, 1/28/11, David Henningsson wrote:
On 2011-01-28 23:07, jimmy wrote:
Here's the revised patch file for the new channel
field "is_drum_channel".
Thanks, but you're missing the patch :-)
// David
Oops, here it is.
Thanks. I've fixed a few bu
On 2011-01-29 20:54, jimmy wrote:
--- On Fri, 1/28/11, David Henningsson wrote:
In think you missed my original comment:
Can you elaborate on where/why this is useful? These are
not public API
functions and aren't used anywhere. I was thinking of
removing the ones
not starting with _LOCAL.
/
As I mentioned in a recent post ("Stopping fluidsynth via a socket"), I'm
starting fluidsynth as a python subprocess and sending midi commands via either
a socket or stdin. In either case there is a lot of unwanted screen output
interspersed with my input, which I have tried to pipe like this:
> subprocess.Popen(["fluidsynth", "-sli","-a", 'alsa', "-j",
> '/usr/share/sounds/sf2/FluidR3_GM.sf2'], stdout=subprocess.PIPE,
> stderr=subprocess.PIPE)
>
> This renders the screen output invisible, but if I have a number of
> simultaneous connections sending commands, after a short time the audio
On Mon, 31 Jan 2011, Matt Giuca wrote:
> > subprocess.Popen(["fluidsynth", "-sli","-a", 'alsa', "-j",
> > '/usr/share/sounds/sf2/FluidR3_GM.sf2'], stdout=subprocess.PIPE,
> > stderr=subprocess.PIPE)
> >
> > This renders the screen output invisible, but if I have a number of
> > simultaneous connec
