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 __

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] Revised patch for allNotesOff, allSoundsOff

--- 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. > > // David > Sorr

Re: [fluid-dev] Revised patch for new channel field is_drum_channel

--- 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. Jimmy diff -pur fluidsynth.svn399.201

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