[fluid-dev] FluidSynth 1.1.3 has been released!

FluidSynth 1.1.3 is a bug-fix release, containing no new functionality compared to 1.1.2. At a glance, builds with LADSPA enabled, multichannel output with 64-bit doubles, and Mac OS X builds with CMake are now working correctly. For more information, see https://sourceforge.net/apps/trac/fluid

Re: [fluid-dev] fluidsynth with realtime kernel

On 2010-10-08 23:15, Pedro Lopez-Cabanillas wrote: Anyway, even if you use the same operating system, kernel version, priority settings, environment, processor, etc. a critical factor is the audio hardware device. Professional or good quality audio interfaces typically allow much smaller buffers,

Re: [fluid-dev] FluidSynth backend for SDL_mixer

> Is anyone going to step up and try this? I could have a go but I'll > probably have to change the way things currently work a little. > I'll have a go at writing a void* memory loader into FluidSynth. I've been meaning to do some hacking for awhile (which is why I've been hanging around this mai

Re: [fluid-dev] FluidSynth backend for SDL_mixer

On Sun, 10 Oct 2010 13:08:42 +1100 Matt Giuca wrote: > OK, well it would be exceedingly good to avoid duplicating all the > MIDI event loading code. I don't think passing a file handle to > FluidSynth would work in this specific case (or in several other > general cases), because while SDL's RWop

Re: [fluid-dev] Imminent 1.1.3 release?

On Sunday 10 October 2010, David Henningsson wrote: > First, so far we have not released windows .exe or .dll files, but > released source code only. FluidSynth is a free software project; our mission should be to release the source code, and support the distributors in their mission of releasin

ASIO (was Re: [fluid-dev] Imminent 1.1.3 release?)

On 2010-10-10 11:58, Pedro Lopez-Cabanillas wrote: On Sunday 10 October 2010, Bernd Casper wrote: It is just important to remember not to link to anything released under GPL at the same time that we link to ASIO.< Does that mean, a chain jOrgan (GPL) --> FS (LGPL) --> Jack --> ASIO raises

Re: [fluid-dev] Imminent 1.1.3 release?

Hi Pedro, thank you, this confirms what I suspected from my understandings. Then this also is the case with PortAudio, since this is released under GPL, too. Cleaning this up, prevents me from wasting time with this anymore. Regards Bernd. - Folgende Nachricht wurde empfangen - Abs

Re: [fluid-dev] Imminent 1.1.3 release?

On Sunday 10 October 2010, Bernd Casper wrote: > >It is just important to remember not to link to anything > released under GPL at the same time that we link to ASIO.< > > Does that mean, a chain jOrgan (GPL) --> FS (LGPL) --> Jack --> ASIO raises licensing problems, in your eyes? Absolutely.

Re: [fluid-dev] Imminent 1.1.3 release?

Hi David, >It is just important to remember not to link to anything released under GPL at the same time that we link to ASIO.< Does that mean, a chain jOrgan (GPL) --> FS (LGPL) --> Jack --> ASIO raises licensing problems, in your eyes? Regards Bernd. - Folgende Nachricht wurde empfangen

Re: [fluid-dev] compatibility version problem

On Saturday 09 October 2010, James Le Cuirot wrote: > On Fri, 8 Oct 2010 19:34:12 +0200 > "Pedro Lopez-Cabanillas" wrote: > > > The autotools build system uses libtool, and these funny numbers are > > a consequence of the libtool numbering scheme. The numbers are > > absurd, BTW. What means the c

Re: [fluid-dev] Imminent 1.1.3 release?

Hi David, Thanks for the reply. In regard to ASIO, I believe the PortAudio drivers have ASIO capabilities if PortAudio is configured with the correct headers, so 'native' ASIO would probably not be needed as we can get ASIO via PortAudio or Jack for Windows (only available in 32-bit)... If one w