On Mon, 31 Jan 2011, Matt Giuca wrote:
> > > So when you
> > >
> > > disconnect, suddenly all the music will come rushing out (do they get
> > > played in the correct time, or do you hear all the notes literally at
> > > the same time?).
> >
> > All at once.
>
> OK, so FS is probably trying to
> > So when you
> > disconnect, suddenly all the music will come rushing out (do they get
> > played in the correct time, or do you hear all the notes literally at the
> > same time?).
>
> All at once.
>
OK, so FS is probably trying to play all the notes at a certain time offset
from the start of
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
> 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
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:
