On Fri, 18 Mar 2011, Edenyard wrote:
[...]
>
> One last question (for now!): assuming Fluid is given the command to
> listen to a network port so that netcat can be used to send reverb
> settings to it, doen the same thing also apply to MIDI data? Or, to put
> it another way, could I send a stream
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
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
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:
On Sat, 29 Jan 2011, Matt Giuca wrote:
[...]
>
> So it seems like when you use Fluid's network interface, it *doesn't* quit
> * itself*. It closes the socket. This seems sensible to me. FluidSynth is
> acting as a network service. It's giving the client the illusion of being
> at a FluidSynth cons
I'm starting fluidsynth as a python subprocesss like this:
subprocess.Popen(["fluidsynth", "-sli", "-g0.5", "-C1", "-R1","-a", 'alsa', "-
j", '/usr/share/sounds/sf2/FluidR3_GM.sf2'])
communicating like this:
s= socket.socket()
s.connect(('',9800))
and I want to stop it like this:
s.send('quit\
Hi,
I'm using fluidsynth in server mode on a Debian system to play numerical data
produced by a Python program. I'm starting it like this:
fluidsynth -sli -a alsa -j "path/to/my/soundfont"
and sending the midi noteon strings and so on via a socket. This works nicely
but I'm getting a lot of id
On Tue, 14 Oct 2008, John O'Hagan wrote:
> On Mon, 13 Oct 2008, you wrote:
> > John O'Hagan wrote:
[...]
> >
> > Note that FluidSynth doesn't follow strictly the telnet protocol, so you
> > can use something simpler. The command line utility netcat(1) (o
On Mon, 13 Oct 2008, you wrote:
> John O'Hagan wrote:
> > Great! I'm using Python, and this is how I did it in my program (Python
> > code follows):
> >
> > from telnetlib import Telnet
> > fluid = Telnet("localhost","9800"
Ben Leggett wrote:
>[...]
>Currently, I start fluidsynth in a shell script in conjunction with
>Dosbox, as opposed to systemwide, since the soundfont I use makes
>fluidsynth take up quite a lot of memory.
>
>Because this soundfont is large, fluidsynth startup time can take quite
>a while, and can
John
> On Sun, 2008-10-12 at 12:50 +, John O'Hagan wrote:
> > Hi,
> >
> > I'm writing an algorithmic music program which generates lists of numbers
> > representing notes and durations. The results can be printed as scores
> > and played as midi files
On Sun, 12 Oct 2008, Pedro Lopez-Cabanillas wrote:
> John O'Hagan wrote:
> > Hi,
> >
> > I'm writing an algorithmic music program which generates lists of numbers
> > representing notes and durations. The results can be printed as scores
> > and played as
my data into a text-to-midi program, then
piping that to, say, pmidi, which plays via fluidsynth, but that seems very
roundabout.
Any advice?
Regards,
John O'Hagan
___
fluid-dev mailing list
fluid-dev@nongnu.org
http://lists.nongnu.org/mailman/listinfo/fluid-dev
13 matches
Mail list logo
