On Sun, 12 Oct 2008, Josh Green wrote:
> Hello,
>
> As Pedro suggested, you could control FluidSynth via TCP/IP. If you
> want finer grained control over FluidSynth and don't mind writing C
> code, then you could use FluidSynth as a shared library. This is how
> Swami and QSynth use FluidSynth.
>
On Sun, 12 Oct 2008, Pedro Lopez-Cabanillas wrote:
> John O'Hagan wrote:
> > Hi,
> >
> > I'm writing an algorithmic music program which generates lists of numbers
> > representing notes and durations. The results can be printed as scores
> > and played as midi files using lilypond, and to play the
Hello,
As Pedro suggested, you could control FluidSynth via TCP/IP. If you
want finer grained control over FluidSynth and don't mind writing C
code, then you could use FluidSynth as a shared library. This is how
Swami and QSynth use FluidSynth.
Best regards,
Josh
On Sun, 2008-10-12 at
John O'Hagan wrote:
> Hi,
>
> I'm writing an algorithmic music program which generates lists of numbers
> representing notes and durations. The results can be printed as scores and
> played as midi files using lilypond, and to play the results as they are
> generated (i.e., bar by bar), I'm using t
Hi,
I'm writing an algorithmic music program which generates lists of numbers
representing notes and durations. The results can be printed as scores and
played as midi files using lilypond, and to play the results as they are
generated (i.e., bar by bar), I'm using the sox synth.
That's pretty
