Re: [fluid-dev] Fwd: Re: [LAU] Fluidsynth, soundfonts, jack, and latency

Quoting David Henningsson : S. Christian Collins wrote: j...@resonance.org wrote: The voice stealing algorithm also needs improvement. I just updated ticket 27 with an improvement to the voice-stealing method. It's a very minor code ch

Re: [fluid-dev] Fwd: Re: [LAU] Fluidsynth, soundfonts, jack, and latency

Quoting "S. Christian Collins" : j...@resonance.org wrote: The voice stealing algorithm also needs improvement. I just updated ticket 27 with an improvement to the voice-stealing method. It's a very minor code change, and might be worth adding

Re: [fluid-dev] Thread safety long-term thoughts

Quoting David Henningsson : Ebrahim Mayat wrote: Currently, fluidsynth has five threads. 5 process 6014 thread 0x6f03 0x936a11f8 in mach_msg_trap () 4 process 6014 thread 0x6703 0x936a1278 in semaphore_timedwait_signal_trap () 3 process 6014 thread 0x6203 0x936a11f8 in mach_msg_trap () 2

Re: [fluid-dev] Fwd: Re: [LAU] Fluidsynth, soundfonts, jack, and latency

S. Christian Collins wrote: j...@resonance.org wrote: The voice stealing algorithm also needs improvement. I just updated ticket 27 with an improvement to the voice-stealing method. It's a very minor code change, and might be worth adding to t

Re: [fluid-dev] Thread safety long-term thoughts

On Nov 18, 2009, at 2:13 AM, David Henningsson wrote: // I'm not sure about the fifth (I/O procs) thread, is that something used internally by libraries we use? What does it do? My sketchy idea about this is that this thread is kernel-related (at least on OS X); it is created by the hard

Re: [fluid-dev] Fwd: Re: [LAU] Fluidsynth, soundfonts, jack, and latency

j...@resonance.org wrote: The voice stealing algorithm also needs improvement. I just updated ticket 27 with an improvement to the voice-stealing method. It's a very minor code change, and might be worth adding to the pile for 1.1.1. Obviously