[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [fluid-dev] Callback driven rendering?

From: Josh Green
Subject: Re: [fluid-dev] Callback driven rendering?
Date: Mon, 08 Sep 2003 21:47:28 -0700

On Sun, 2003-09-07 at 04:53, David Olofson wrote:
> I just had an idea...
> Does FluidSynth have any API that lets it render into application 
> provided buffers, driven entirely by callbacks?

Yes it does. Have a look at the API documentation, the link to this can
be found on the FluidSynth web site, but here it is directly:

The functions for creating and getting audio from the synth can be found
in the "File List"->synth.h link. This documentation can also be
generated from the FluidSynth doc/ directory in the source, provided you
have Doxygen installed. Just do a "make doxygen" in the doc/ directory
to create the Doxygen API reference (what that link points to). There is
also an developer's overview document which can be found in the doc/html
directory (you may actually want to check that out first to get a

> I'm thinking about routing FluidSynth's output, preferably channel by 
> channel, directly into the FX network of Audiality, and having 
> Audiality's MIDI input and/or internal sequencer drive both 
> FluidSynth and Audiality's internal synth. That is, using FluidSynth 
> to add "structurally clean" SF2 support to Audiality.

Sounds good. I'm not sure if FluidSynth has the channel by channel audio
routing capability that you mention. Do you mean audio or MIDI channel?
Like being able to route the individual left/right audio channels, or
each MIDI channel?

> //David Olofson - Programmer, Composer, Open Source Advocate

I'm currently the maintainer of FluidSynth, but lack much knowledge in
its workings, and I don't see myself adding any new functionality in the
near future, since I'm working a lot on my other projects (Swami -
http://swami.sourceforge.net). So unless someone else steps up to the
plate, or Markus and/or Peter get some free time, there probably wont be
a whole lot of new developments for the time being. Feel free to ask
questions about the current code base and API though. I'm also open to
ideas for new features, but they will probably be placed on a list for
future active development. Cheers.
        Josh Green

reply via email to

[Prev in Thread] Current Thread [Next in Thread]