Re: [fluid-dev] Stopping fluidsynth via a socket

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

Re: [fluid-dev] Stopping fluidsynth via a socket

I've never used Fluid with sockets, so I'm trying it out now. What you're doing really is nothing to do with Python (I don't think), so we can simplify it just by running it on the command-line, and using netcat(or telnet) to communicate over the socket: $ flu

Re: [fluid-dev] Stopping fluidsynth via a socket

On Sat, 29 Jan 2011 02:44:51 + "John O'Hagan" wrote: > Is there something else I need to send fluidsynth via a socket to > make it quit? This is a complete guess since I'm not a Python coder or a FluidSynth expert but are you closing the socket afterwards? James __

[fluid-dev] Stopping fluidsynth via a socket

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\