>
> In the meantime, I'm glad to see that (thanks to Sven Meier and Alessio
> Treglia) that 1.1.2 of FluidSynth will reach Ubuntu Maverick! (And yes, it
> will build with CMake :-) )
>
That's excellent, because it seems 1.1.2's new threading code fixed a lot of
random issues, like my "everything i
Hi David,
Bernd is testing on Windows using the dsound driver. I've done some
testing of 1.1.2 in Puppy Linux (using the Jack driver) and it seems
that I don't have the same issue.
GrahamG
___
fluid-dev mailing list
fluid-dev@nongnu.org
http://lists.no
Hi David,
jOrgan is developed in Ubuntu. Since it's a Java application, it runs on all
major OS's. Some of us use Windows XP and Win7 (don't know if someone has
running Vista yet), some Ubuntu, some Puppy Linux. Someone managed SuSe last
week. There are people who managed OSX, too.
It seems th
Okay, cool that things appear fixed. But may I ask - what OS are you
jOrgan guys running? It could be that the thread synchronisation
overhead varies much between operating systems. As for now, I've just
set it to "8" which means that if there is less that 8 active voices,
there is no use waki
Hi David,
you hit the point exactly. After Sven compiled the latest svn, all the
crackling has gone completely, as confirmed from both the other testers who had
the crackles too. Also memory usage and latency seem much improved. So much
thanks for the changes. So far, it seems not to have somet
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
