You're welcome, glad to have fixed this bug and again, thank you for
reporting it. The lack of a return value resulted in essentially an
uninitialized variable situation, which produces the "works for me"
scenario depending on what system is being used. I've used the FluidSynth
server in the past
Apologies, my mistake. I was running the new executable locally but it
was still pulling the old libfluidsynth. The problem is indeed fixed
with the new version.
Many thanks for your help!
Regards,
Mark
At 12:39 on 19 Jan 2015, Element Green wrote:
>Are you sure you don't still have another lib
Ohh, another thing that may be affecting you, is that if FluidSynth gets
interrupted with CTRL-C it leaves the server port 9800 in TIME_WAIT state,
which takes a little while to timeout. FluidSynth may want to use
setsockopt SO_REUSEADDR to prevent this. FluidSynth does report though in
the termi
Are you sure you don't still have another libfluidsynth hanging around on
your system? That was the problem I had at first when testing this
change. So do a 'which fluidsynth' to find out where the executable is and
then do ldd `which fluidsynth` to see which libfluidsynth it is pulling in
and th
Thanks for your help. I've pulled this from git and built, however I
still see the same behaviour. Attempting to debug it now, I see lots of
logging references in the code such as
FLUID_LOG (FLUID_DBG, "New client connection");
but it's not immediately apparent where these logging messages go
Hello Mark,
Thank you for reporting this. Looks like it was an issue
with fluid_server_handle_connection() not having a return value, which
meant undefined behavior, since the return value was getting checked for a
success value in fluid_server_socket_run(), but the return value was not
getting p
Hi Element,
Thanks for your reply.
>When I encounter network related issues like that, it can sometimes be
>helpful to get a network traffic capture with an application like
>Wireshark. When testing connections to FluidSynth you'd want to
>capture on the lo loop back interface.
Wireshark shows
Hello Mark,
2015-01-19 10:59 GMT+01:00 Mark Knoop :
> I'm having a problem on Fedora 21 where fluidsynth rejects any server
> connection. [...] Has anyone experienced anything similar? [...]
Sorry, no solution, but only a quick note that I see the same
behaviour on an embedded system (ARM Coretex
Hello Mark,
When I encounter network related issues like that, it can sometimes be
helpful to get a network traffic capture with an application like
Wireshark. When testing connections to FluidSynth you'd want to capture on
the lo loop back interface. I'd also check to make sure you don't have a
Hi list,
I'm having a problem on Fedora 21 where fluidsynth rejects any server
connection. This always worked without problems on Fedora 20 and
earlier which leads me to suspect that it might be related to some
distro change or update (e.g. compiler version).
Has anyone experienced anything simi
10 matches
Mail list logo
